The job isn't done when it ships
A system that quietly stops working in month four was never really delivered. Care plans are how we stay accountable for what we built — monitoring, fixes and iteration, from $150 a month.
01
Why systems break
Your systems depend on other people's software, and other people ship changes.
An API deprecates a field. A rate limit tightens. A model version is retired. A schema gains a column. None of this is anyone's fault, and none of it announces itself. The system doesn't crash — it degrades, and someone finds out three weeks later from a customer.
That's the honest mechanism. It's also why we'd rather you were on a plan than not.
Layer 1 · Attaches to any build
Care Plans
Hosting, monitoring, security patches, backups and a small change allowance.
- Essential$150/moMonitoring, patches, backups
- Growth$350/moAdds a monthly change allowance and priority response
- Priority$750/moAdds same-business-day response and quarterly review
Layer 2 · For n8n, Make and agent systems
Automation-as-a-Service
Monitoring, fixes when someone else’s API changes, and monthly optimization.
- Monitor$500/moAlerting, error triage, break-fix
- Optimize$1,200/moAdds iteration and monthly improvements
- Scale$3,000/moAdds new workflow development each month
Layer 3 · Attaches to CRM builds
CRM & RevOps Managed
Pipeline hygiene, workflow tuning, reporting changes and new automation requests. GoHighLevel sub-account resale sits here where it applies.
- Standard$1,000/moPipeline hygiene and workflow tuning
- Pro$2,500/moAdds reporting changes and new automations
- Enterprise$5,000/moAdds dedicated RevOps capacity
Layer 4 · For teams who want capacity, not a project
Fractional Capacity
A reserved block of senior engineering hours each month.
- 15 hrs$1,500/moReserved senior hours
- 25 hrs$2,400/moReserved senior hours
- 40 hrs$3,800/moReserved senior hours
- 60+ hrsfrom $5,500/moDedicated capacity
05
What’s in every plan
- Monitoring on everything we builtNot just uptime — the failure modes specific to your system.
- We contact you firstIf something breaks, you hear it from us with the cause, the fix, and what we changed so it doesn’t recur.
- A named engineer who knows your systemNot a rotating queue.
- Published response windowsDuring our stated overlap hours: 09:00–17:00 London time (UK) · 09:00–17:00 Sydney time (Australia).
06
Terms
Three-month minimum on Layers 1–2, six months on Layers 3–4.
We ask for a minimum term because month-to-month support gets deprioritized by both sides, and neither of us benefits from that.
Thirty days' notice to cancel. No auto-escalating price.
07
What we won’t do
- Support systems we didn’t build, unless we’ve audited them first and agreed they’re maintainable
- Sell a care plan as a condition of a build. If you’d rather run it yourself, we hand over documentation and monitoring and wish you well
- Promise 24/7 coverage. We publish real hours instead
08
FAQ
- What if we don’t take a plan?
- You get documented handover and the monitoring configuration. You run it. That’s a legitimate choice.
- Can we start a plan later?
- Yes, after a short audit to check nothing has drifted.
- Does a plan cover new features?
- Layers 1 and 2 include a change allowance. Substantial new work is quoted separately.
- What counts as a fix versus new work?
- If it used to work and stopped, it’s a fix. If it never did it, it’s new work. We’ll say which before doing it.