What it solves
Automations break quietly: an API changes, a credential expires, a field is renamed, a vendor changes its pricing. Automation Care watches every covered workflow, fixes breakages, rotates credentials on schedule and reports monthly — so the system you paid for keeps working, and someone is accountable for it.
Typical problems
- A workflow that stopped and nobody noticed for a week
- Nobody knows which automations exist or who owns them
- Small changes waiting months because there is no one to ask
- Vendor pricing and API changes arriving as surprises
- The person who built it has left
What changes
Someone is watching. Breakages are caught by monitoring rather than by clients, credentials are known and current, small changes ship monthly, and you receive a plain report of what ran, what failed and what was fixed. The system you paid for keeps working.
Example workflows
Workflows we build regularly in this service. The “what changes” lines describe the process after the build, not measured results; measured results are published only in case studies, with permission.
API change on a Friday
A connected app changes its authentication; three workflows fail over the weekend and Monday starts with a backlog.
Monitoring raises the failure within minutes, the credential is re-authorised, failed items are replayed from the log and you get a note explaining what happened.
What changes: failures are caught and replayed instead of discovered by clients.
Quarterly access review
Former staff and old integrations still hold credentials to the CRM and email.
Every covered credential is listed with its owner; unused access is removed and rotation dates are scheduled.
What changes: access is known, named and current.
Small change request
Adding a field to an intake form waits three months because nobody owns the workflow.
The change is estimated in hours, approved in writing and shipped inside the monthly allowance.
What changes: small improvements happen monthly instead of never.
What gets automated
- Monitoring and alerting on every covered workflow
- Fixes for breakages and API changes
- Credential rotation reminders and access hygiene
- Up to 4 hours of small changes a month
- Monthly health report
- Integration monitoring and agent maintenance add-ons
Systems we work in
Tools describe the systems we connect; they do not imply partnership or certification.
- n8n
- Make
- Zapier
- your integrations and agents
- HubSpot
- Clio
- Cliniko
- Google Workspace
Human checkpoints and security
The rules that keep this service safe to run in a regulated firm. They are written into the scope, enforced in the build and described in more detail on the security and data page.
- Fixes that change behaviour are approved in writing before deployment
- Replayed items are logged so nothing is duplicated
- Access changes are recorded with who approved them
- The monthly report states what was not covered as clearly as what was
What every build includes
- Automatic retries when a connected app is briefly unavailable, so nothing is silently lost
- A run log for every execution — what came in, what was decided, what went out
- Failure alerts to Slack or email after repeated errors, with a pause switch you control
- Idempotent steps: running twice never creates duplicates
- Written handover: a one-page map of the workflow, its owners and how to change it
- Built in your own accounts — you keep every credential, licence and asset
How the work is delivered
Map
Current process documented with the people who run it.
Scope
Written proposal, diagram, deliverables, fixed price.
Build
Short stages in your accounts, demo at the end of each.
Launch
Monitoring, alerts and documentation before go-live.
Pricing and engagement
Written inventory, risk register and priced options in 5–8 working days. Fee credited against an option accepted within 30 days.
Up to 10 workflows; $900/month for up to 25; larger estates quoted. Monthly in advance, cancel any month. Fixed in writing before work starts; nothing outside scope without your written approval.
Care plus 8–16 build hours, a monthly operating brief, model-cost review and a quarterly roadmap session.
Deliverables
- Inventory of covered workflows with owners
- Alert routing to your named contact
- Monthly health report
- Change-request log with approvals
Questions
What is included and what is not?
Included: monitoring, fixes for breakages and API changes, credential hygiene, up to four hours of small changes and a monthly report. Not included: new workflows, new integrations, agent redesign, third-party licences and platform fees — those are quoted separately.
What are the response times?
Acknowledgement within one working day; critical breakages are prioritised the same day during our overlap hours with your time zone. We do not promise 24/7 response and say so plainly.
Can we cancel?
Any month, in writing. Everything stays in your accounts, documented, so nothing is lost when you leave.
Do you cover automations you did not build?
Yes, after a Reliability Review so we know what we are taking on. The review fee is credited against the first months of Care.
How does pricing work?
Most engagements start with a fixed-price Automation Reliability Review (from $900). You then get priced options in writing with one price and a delivery date each. Ongoing monitoring and improvements are a monthly retainer you can cancel any month. All prices are in USD.
How quickly can something be live?
A first workflow is usually live within two to three weeks of sign-off. Larger builds are staged so something useful ships early and the rest follows.
What happens when a workflow fails?
Every build ships with retries, a run log and alerts. Anything that does not run as scoped in the first 30 days is fixed at no charge; after that Automation Care covers fixes, or we quote a small fix and turn it around quickly.
Who owns the automations afterwards?
You do. Everything is built in your accounts and documented, and your team is walked through it at handover. You can maintain it yourself or keep us on retainer.