- You call when
- A program that matters has outgrown its architecture, and the fixes keep losing to the roadmap. Or you know agentic technology should be working for you and nobody can say how.
- First weeks
- We read the system as it is, which is rarely how it is documented. Then we agree the deliverables, the definition of done and the named owners on both sides. That scope is the contract.
- During
- We build against the scope, in an environment you can see into, on tooling you already run wherever it is up to the job. You get progress against deliverables rather than timesheets, and handover starts on day one instead of being a closing ceremony.
- What you get
- Working infrastructure, pipelines your own people operate, documentation that matches what is deployed, runbooks, and teams trained to use what was built.
- Done means
- The deliverables exist, they work, and the people who will run them know how. Whether that is your team or ours is decided in the scope, so nobody discovers a gap at the end.
- After delivery
- Handover to your people is the default, and it is not the only option. If you do not have a dedicated person to take the system on, or you want us close by, we can stay on fractionally to support it or manage it fully. Either is agreed as part of the program.
- If the work needs us inside
- Some programs need our people working inside your teams for a stretch. Where the scope calls for it and we have the capacity, we can do that. It is agreed per program, and it is not the default.