Why automations need an owner
An automation is a small piece of software, and software that touches other systems changes when they change. Without someone watching, failures are discovered when a customer complains or month-end does not balance.
A support plan gives every automation a named owner. We watch run history and error rates, respond to alerts, apply fixes, keep platforms and credentials current, and spend the remaining hours making things better: handling a new exception automatically, adding a new supplier format, or extending a workflow to another team.
Support plans
Month to month after an initial three-month term. Prices in USD.
Monitor
For a small number of stable automations.
- Up to 5 workflows monitored
- Failure alerts and next-business-day response
- Fixes for breakages caused by external changes
- Quarterly health report
Operate
For automations your daily operations depend on.
- Up to 15 workflows monitored
- Same-business-day response
- All breakage fixes included
- 6 improvement hours each month
- Monthly performance report
Extend
For teams steadily automating more.
- Unlimited workflows monitored
- Priority response within 4 business hours
- All breakage fixes included
- 16 improvement hours each month
- Monthly roadmap review
Platform subscriptions and AI usage are billed by the provider directly to your account.
How support works
Onboarding review
We document every workflow, its dependencies and its owner, and fix anything fragile.
Monitoring
Failures, error rates and unusual volumes alert us, usually before you notice.
Fixes
Breakages caused by external changes fixed within the response time of your plan.
Improvements
Monthly hours spent on the improvements that save the most time.
Why automations break
Most automation failures come from changes outside the automation itself:
- Vendors change formats. A supplier redesigns its invoice layout or a customer changes its PO template.
- APIs change. Fields are renamed, versions retired or rate limits tightened.
- Credentials expire. Passwords, tokens and certificates expire, often without warning.
- Business rules change. New approval limits, price lists or tax rules that the automation does not know about.
- Volumes spike. Month-end or seasonal peaks push past limits nobody tested.
- People leave. The person who built or owned an automation moves on, and nobody knows how it works.
Which plan fits?
A guide to choosing a support plan.
| Your situation | Usually fits |
|---|---|
| A few automations that rarely change | Monitor |
| Automations your daily operations depend on | Operate |
| Automating steadily across several teams | Extend |
| Automations built by someone else that keep breaking | An onboarding review, then Operate |
Common questions
Do you support automations you did not build?
Yes, after an onboarding review. We audit the existing workflows, document them and fix anything fragile, then they are covered like our own. The review is quoted separately based on how many workflows there are.
What counts as a fix versus an improvement?
A fix restores something that used to work. An improvement changes what it does, such as handling a new case or adding a step. Fixes are always included; improvements use the monthly hours.
Can we cancel?
Yes, with 30 days' notice after the first three months. Everything stays in your accounts and keeps running, with up-to-date documentation.
How fast do you respond to failures?
Next business day on Monitor, same business day on Operate, and within four business hours on Extend. Urgent failures affecting orders or payments are escalated immediately.
Give your automations an owner
Tell us what is running today and what it connects to. We will recommend a plan and tell you what we would fix first.