How we work
The engagement journey, drawn out.
A visual walk through a Moweb engagement, from the framing week to the day your own team takes the keys. The detailed text version lives on the approach page.
The model
Frame. Design. Build. Operate.
01
Frame
Week 1
A partner-led discovery week. Interviews, data-room reads, stakeholder mapping, and a one-page operating thesis.
02
Design
Weeks 2-4
Solution design, control catalogue, build plan and success metrics, reviewed with risk, security and finance.
03
Build
Weeks 4-16
Joint pods deliver in two-week iterations. Audit-pack evidence accumulates with every pull request.
04
Operate
Quarters 1-3
We co-run the system through three quarters. Handover is a transfer of practice, not just code.
A typical engagement
Six months, milestone by milestone.
Durations vary with scope. This is the cadence of a typical single-system build pod, from kickoff to handover.
- Week 1
Kickoff and framing
Partner-led discovery. Objectives, stakeholders and success metrics agreed. Governance model set with second-line risk.
- Week 4
Design sign-off
Architecture decision record published. Evaluation harness scoped. Cost envelope signed off by finance.
- Week 8
First production release
The first working slice ships to a controlled user cohort, with audit-pack evidence and a tested kill-switch.
- Week 16
Full deployment
The system reaches its full user base. Red-team and security review complete. Observability live.
- Quarter 3
Practice handover
On-call rota co-staffed and then transferred. Exit plan and runbook delivered. Your team owns it.
Governance gates
Nothing ships without passing the gates.
0%
Engagements with a tested kill-switch before launch
0%
Releases shipped with an audit pack
0%
Clients continuing into managed service
At handover
What you own when we leave.
Handover is the goal from day one. You are never dependent on Moweb to keep the system running.
01Source code in your repositories, with full IP assignment
02Versioned evaluation harness with full score history
03Model cards, data sheets and the complete audit pack
04Operating runbook with incident and kill-switch procedures
05Co-staffed on-call rota, transferred to your team
06A documented exit plan, written on day one