STAGE THREE: PARTNERSHIP
Then we keep it running. £150 or £500 a month.
Standby keeps what we built alive and watched. Partnership adds us as your ongoing AI adviser: a report every month, a strategy review every quarter, and somewhere to send the question when it comes up.
Stage three
Built, live, and looked after. Two tiers.
Once it is live, somebody has to own it. AI models get retired, the software you rely on changes without warning, and systems drift. One number every month, agreed in writing, with no setup fee and no licence per seat.
TIER ONE
Standby
£150 a month
The system stays alive, watched and patched, and somebody who knows how it was built is responsible for it.
- Hosting, backups and security updates
- Monitoring around the clock by our own AI agents
- Bugs fixed, and changes in the tools we connect to handled before you notice them
- A monthly health report: what ran, what we caught, what we fixed
You do not buy a licence. You buy the people who built the thing staying responsible for it.
What the partnership is
An adviser on the inside, not a support queue
Standby is the floor: it keeps the system alive. Partnership is the part people underestimate, because it is the bit that keeps the business moving after the build is finished.
None of that turns into an open-ended build. If the review or the report points at something substantial, it becomes its own project, scoped and priced up front, and you decide whether it happens.
The monthly AI report
See what lands in your inbox
Every month, one document on how your systems are performing and what could be better. This is the shape of it.
- Written in plain English, and sent to you. There is no dashboard to remember to log into.
- It ends on what we would change next, so the improvement list stays live instead of going cold after launch.
- It is the same document the quarterly strategy review is built on, so nobody arrives at that meeting cold.
How a month actually runs
It watches itself
Our own AI agents monitor what we built, around the clock, against your infrastructure. The monitoring is there so problems are found before anybody in your business notices.
We fix what breaks
Bugs, drift, and changes pushed by the tools we connect to. Ours to put right, rather than yours to report and then chase.
You get it in writing
A report every month saying what ran, what we caught and what we fixed. On Partnership it goes further and says what we would change next.
Anything substantial is its own project
Work outside what is already there gets its own scope and its own price, agreed in writing before it starts, so the monthly never turns into an open-ended bill.
Things people ask before they sign
“What happens if we want to stop?”
It is rolling monthly with thirty days to cancel, in writing, and there is no exit fee. Everything we built is already yours: the code, the data and the prompts. What you keep and how your data comes out is agreed in writing before we start, so leaving is a handover rather than a negotiation. If we host it, moving it onto your own accounts is quoted like any other piece of work.
“What counts as a bug, and what counts as a new project?”
If something we built stops doing what it was agreed to do, that is ours to fix inside the monthly, and so is a change pushed by a tool we connect to. Wording, a field, a tweak to a prompt: also the monthly. A new process, a new integration, or a change to how the work itself is done is a project, scoped and priced before it starts. Where it is genuinely unclear, we talk about it first rather than deciding quietly on an invoice.
“Who actually answers when we message?”
The people who built your system. We are a small team and there is no ticket queue in front of us, which is the point of buying the builders rather than a support contract. We do not publish a response time, because a number we cannot hold to on a bad week is worth nothing to you. What we do instead is tell you when we have picked something up and what we are doing about it.
“What happens when an AI model we depend on is retired?”
Models get retired and providers usually announce it ahead of time. Moving you onto a replacement, testing it against your own work and adjusting the prompts is part of both tiers, and you would normally read about it in the report rather than notice it happening. Because you pay your AI usage directly at cost, any change in what a model costs shows on your own bill, and we tell you before we move you. If a retirement forces a rebuild of something substantial, we scope and price that first.
“Do we have to take Standby before Partnership?”
No. Partnership contains everything Standby does, so it is not a step you have to climb through. You can start on either once something is live, and move between them with a month of notice. The one thing that does come first is the build: the partnership looks after a system, so there has to be a system.
Nothing goes out in your name without a person saying so.
This does not change when the build ends. It is the same boundary every month the partnership runs.
The written boundary
Every agent has a written boundary: what it may do on its own, and what it must always put in front of someone. Sending, spending and deleting always stop and ask.
Access, per person
Access is set per person and per area. The agent’s own database account cannot delete anything and cannot read your stored credentials, because we took those rights away from it rather than trusting it not to use them.
Where your data lives
Hosting is in the EU. Processing is under UK GDPR and the Data Protection Act 2018, with a data processing agreement signed before anything is connected. Your data is yours. We own the infrastructure it runs on, not what is in it.
The partnership starts where the build finishes.
It begins with the Audit, from £2,000. A free call on your business first, and you leave with a plan either way.