Run · monthly
We run it with you, and hand it over.
Monitoring, tuning, new modules as the company grows, usage read from the logs, and a quarterly re-diagnosis. Priced on the work, agreed before it starts.
What the run is
A system nobody has to babysit.
A build that nobody runs goes stale in a quarter. The run keeps the modules earning after launch week. The build is the small part. Getting the team to actually use it is the rest, and that is what Run is for.
Every week
Monitoring and tuning
We watch the logs, the override rate and the queue. When an action type drifts, we tune the prompt, the data or the gate.
Weeks 2, 4 and 8
Usage checked from the logs
Adoption is read from what the system did, not from a survey. If a module is not used, we find out why.
Every quarter
Re-diagnosis
The company changes, so the map is redrawn. New modules are scoped and priced the same way.
The price
Priced on the work and agreed before it starts. We carry the AI and tool costs. No per-seat maths.
What you own
The second brain, the code, the dashboards, the runbooks, the logs.
The exit
Access is revocable in one click, and the handover is documented.
FAQ
Running it.
What does the monthly actually cover?
How do we know it is working?
What if we want to stop?
Next step
Talk through the run.
Twenty minutes on what is live, what it costs to keep it live, and what handover looks like.
Priced on the work, agreed before it starts · documented handover · you own the second brain and the code
