05 · Monthly care
The same team, after go-live.
System Intelligence (SI) watches the routine checks. The same team still decides the fix, and stays after go-live.
- 01Named team after go-live
- 02Fixes, monitoring, improvements
- 03Human review when SI is in the stack
The gap
A launch with nobody left who knows the system.
Small breaks pile up. Content drifts. An integration fails on a weekend and the people who built it are gone. A roadmap exists in a slide, and the live system no longer matches it.
Systems pay back when the people who designed them stay responsible: for uptime, for small improvements, and for the decisions SI and automation are still not allowed to make alone.
Outcomes
What changes when this is in place.
- 01
Continuity you can name
The team that shipped the work remains the team you call. Context does not reset every month.
- 02
A system that stays current
Fixes, dependency updates, content changes, and agreed improvements land on a rhythm you can see.
- 03
Monitoring with a response
Integrations, workflows, and key journeys are watched. An alert has an owner.
- 04
Judgement stays in the room
Where SI or automation is live, care includes source updates, quality checks, and the human review.
Capabilities
What the work covers.
Care is Run. It covers the websites, integrations, workflows, and Connected SI we put into production — and the human decisions those systems still require.
- 01
Priority rhythm
A monthly list of fixes and improvements, agreed in writing, with room for urgent production issues.
- 02
Production health
Updates, backups posture, performance, and the small breaks that become outages if they wait.
- 03
Integration and workflow watch
Failed syncs and stopped automations investigated by the people who built them.
- 04
Content and conversion
Page, catalogue, and campaign updates that keep the sell-ready website matched to how you sell.
- 05
Human-led SI upkeep
Source refresh, answer review, and guardrail checks so assistants stay inside approved content.
In the programme
Assess, build, then stay.
01
Assess
Define what healthy means for this stack: uptime, content freshness, failed jobs, and the review SI still needs from a person.
02
Build
Care starts from what we shipped. New build work is scoped separately, against the same acceptance bar.
03
Run
Operate, fix, and extend on a retained cadence. Larger changes go through written change control.
What’s included
The delivery, in writing.
- Named team continuity after launch
- A written monthly priority list
- Maintenance, dependency care, and production fixes
- Monitoring response for integrations and workflows
- Agreed content, conversion, and small improvements
- SI and automation review where those systems are live
- Documentation kept current
- A path to pull in another service without re-explaining the business
Outside this service. A ticket queue from a team that did not design or build the system.
What keeps working
Accountability that outlasts the launch week.
The value of care is that the system, the documentation, and the decisions stay with people who already know them.
One team, before and after
Run is a continuation of Assess and Build. You are not introducing the business to a new vendor.
Priorities stay written
Each cycle has an agreed list. Larger work is scoped, so the retainer does not become an unbounded queue.
SI stays human-led
If an assistant or workflow is in production, care includes the review, the sources, and the right to stop it.
FAQ
Practical questions.
Is this hosting support?
It includes keeping production healthy, and it goes further: improvements, content, integrations, workflows, and the human review around SI. It is accountability for the system we design and build with you.
Can we start care without a build?
Sometimes, after Assess. We take on a system we can understand and document. If the stack is a black box, the first step is to map it.
How is scope set each month?
Written priorities for the cycle. Urgent production issues come first. Larger features go through change control so the month stays predictable.
Does care cover SI?
Yes, when Connected SI or an automated step is in the system we run. People still approve what it may use and what it may ship.
Discuss monthly care
Tell us which service the operation needs. We map it into Assess, Build, and Run, and stay responsible after launch.