From business outcome
to managed operation.
One lifecycle, eight stages and a clear decision at each gate. Nothing moves forward on optimism alone.
The operating lifecycle.
The sequence is the same for every process. The depth at each stage depends on the outcome and the constraints.
- 01UnderstandOutcome, population, constraints and the current baseline.
- 02DesignProcess, dialogue, controls and the measurement model.
- 03IntegrateSystems, data and telephony.
- 04TestQuality, edge cases and escalation paths.
- 05LaunchControlled go-live, not a big-bang switch.
- 06ObserveMonitor the process against its defined result.
- 07ImproveApproved change through the optimisation loop.
- 08ScaleExtend what works to further volume, segments or processes.
Each stage ends at a decision gate.
A gate is a question with an answer, not a status update.
| Gate | Question | What must be true |
|---|---|---|
| Outcome gate | Is the target result measurable and attributable? | A defined outcome, denominator and comparator |
| Design gate | Does the process design meet the outcome? | Approved dialogue, controls and measurement |
| Integration gate | Can the process reach the systems it needs? | Data in, status out, escalation reachable |
| Launch gate | Is the operation safe to run at volume? | Quality thresholds met, escalation tested |
| Scale gate | Does it still hold beyond the pilot? | Stable results across populations |
The boundary is written down.
A managed operation works when everyone knows what they own.
Vee operates
- Process design and dialogue
- Contact execution
- Measurement model
- Improvement proposals
Client owns
- Business objective
- Policy and regulatory interpretation
- Source systems and access
- Approval of consequential change
Shared
- Escalation rules
- Contact strategy
- Definition of a good outcome
- Review cadence
Visibility is built in, not reported afterwards.
The same data that runs the process proves it. Visibility is a design output of the operating model.
Cases covered
100%
Every case the process touches is observable in the operating record.
Changes approved
100%
Share of consequential changes released only after recorded approval.
Escalations with context
92%
Share of escalated cases reaching a human team with full context attached.
Review cadence
Weekly
Operating review; monthly deep dive and quarterly direction.
Time to first change
6 wk
From go-live to the first measured, approved improvement.
Production scale
42.28M
Cumulative customer cases through 31 March 2026, official public baseline.
Scaling is a decision, not a default.
The operating model is designed to extend, but only when the evidence supports it.
A process that works at pilot volume is not automatically ready for national volume. Scale is a separate gate with its own evidence.
Vee extends volume, segments or adjacent processes only after the model holds on the current population.
What scale can mean
- 01More volume on the same process
- 02Additional customer segments
- 03An adjacent process in the same domain
- 04A new market or locale
Where to go next.
The operating model connects to how responsibility is shared, how the work is paid for and how performance is measured.
Evidence and control
Economics
Start at the outcome gate.
Tell us the result you need to improve and we will define the process around it.