Keep-It-Running Plans

For systems already live — keep them running, and keep improving them. Three plans, so you pay for what you actually use.

From £150 / month · three tiers · 3-month minimum

Perfect for: clients who already have an automation or AI system live and don't want to think about it again.

The three plans

Care · £150/mo — monitoring, error-fixing, and keeping the workflow alive when a tool it depends on updates. No new builds. Up to 2 hours a month.
Active · £450/mo — everything in Care, plus one new or changed automation per quarter and a monthly one-page ROI report. Up to 6 hours a month.
Partner · £900/mo — Active cadence plus one new automation every month, priority turnaround, and a quarterly strategy call. Up to 10 hours a month.

How it works

Hours are capped and stated per plan — no open-ended "reasonable support."
3-month minimum, then cancel with 30 days' notice. Paid monthly in advance.
A 5–10% escalation at each annual renewal, set in the terms up front.
Response within 4 working hours, mon–fri. Not a 24/7 on-call SLA.

Sample month (Active)

Week 1: a Stripe API change broke the invoice sync. Fixed Tuesday, Loom posted. Week 2: nothing broke. Week 3: built this quarter's new "lapsed-customer" follow-up automation. Week 4: one-page ROI report — 12 hours of operator time saved this month, here's the maths.

Why a plan (and not just call me when it breaks)

When your tools update — every few months — the workflows need adjusting. Clients who try to manage that themselves, it breaks at the worst time. A plan covers that, and the monthly ROI report proves the hours you're getting back. You still own the code the whole time; the plan is optional labour, not lock-in.

FAQ

Which plan should I be on?: If your system just needs to stay alive, Care. If you want it to keep gaining new automations, Active. If automation is central to how you run and you want a monthly build plus priority, Partner.
Do the plans include big new builds?: Small ones, within the monthly hours. A larger build is scoped as a separate Single Workflow or AI System job, with the plan covering ongoing care.
Why a 3-month minimum and 30 days' notice?: Because keeping a live system healthy is real ongoing work, and a month isn't long enough to prove it. After the first three months you can stop with 30 days' notice — no long lock-in, just enough runway to do the job properly.
Is the build itself locked to the plan?: No. You own the code outright either way — the plan is optional maintenance, not something that stops working if you cancel.