/003.
How we work
One loop: understand, propose, build, embed.
We enter the organisation, learn how the work actually happens, propose the systems that should run it, build them inside your environment, and stay until your team runs them without us. Each phase below ends with a deliverable and an exit criterion the sponsor signs before the work advances.
01
Understand
Enter the organisation and map workflows as they actually run, not as the org chart says they run.
- /001. DiscoveryA signed one-page problem statement and scope memo.
02
Propose
Identify which workflows AI should run, design the systems, and present the case in the sponsor's language with explicit scope and exit criteria.
- /002. ArchitectureA signed architecture document and build plan.
03
Build
Construct the systems inside your environment: your data, your infrastructure, your security perimeter.
- /003. BuildWorking code passing acceptance criteria in a development environment.
- /004. DeployA deployed system passing acceptance under representative load, co-signed.
04
Embed
Integrate into daily operations, run under real load, and train your team until they operate independently. You own what was built.
- /005. StabiliseThe client's team runs it independently; runbook complete; sign-off.
- /006. Retain (optional)A rolling relationship; exit by either party per the MSA.