Operational maturity for scaling companies, fixed scope, fixed outcomes.
A productised programme with four variants for four typical life-cycle moments: Foundation, Remediation, Integration, Exit. Assessment, redesign, and compliance overlay bundled, because the clock is running.
One model. Four shapes.
Which shape you need depends on where you are in the life cycle.
Foundation Sprint
Series A–B · 30–80 FTE · laying the operating groundwork before scaling forces it. 6–10 weeks.
The first processes that actually stick. Core operational mapping, baseline RACI, an artefact canon for the next 18 months. You leave with a framework the next twenty hires can grow into.
- Core process map across operations, finance, and HR
- Baseline RACI with clear decision rights
- Artefact register for the next 18 months
- Maintenance cadence so the foundation does not decay
Operating Model Custodianship (SUSTAIN) typically follows while the foundation settles in.
Remediation Programme
Series B–C · 80–250 FTE · for scale-ups that outgrew their processes. 8–16 weeks.
For companies whose growth outran the operation. Gap analysis across operations, finance, customer success, and engineering, prioritised remediation, controlled handover to internal ownership. Not a panic drill, a structured cleanup.
- Maturity assessment across six domains
- Prioritised remediation backlog
- Ownership transfer plan with milestones
- Cross-domain RACI for the next growth stage
Remediation often rolls into Compliance Custodianship (SUSTAIN) so the fixes hold up.
Post-M&A Integration
Post-acquisition · merging two operations · 10–16 weeks.
Comparable diagnosis of both companies. Harmonisation that preserves the best practices on each side, not the loudest ones. We decide with you what stays and what adapts, and build the Day-1 runbook.
- Dual process map with gap analysis
- Harmonised target operating model
- Day-1 runbook and integration governance
- Migration plan prioritised by risk
After integration, many clients shift into SUSTAIN to stabilise the harmonised model over the first quarters.
Exit-Readiness
12–18 months before exit or liquidity event · 8–12 weeks.
The documentation diligence actually asks for. No data-room surprises, no last-minute VDR panic, no price cut because of avoidable gaps. We prepare the material before the first login is handed out.
- Diligence pack with process and role documentation
- Risk register and audit trail
- Readiness assessment with an honest gap analysis
- Management Q&A pack with prepared answers
We can accompany the Q&A phase during the transaction. After closing, the need often shifts to Integration or Compliance Custodianship.
Maturity grid across four domains
Operations, finance, HR, and IT, five levels, current and target side by side. The artefact we deliver at the end of diagnosis.
Operations
L3 → L5Core processes documented, but ownership uneven.
Finance
L4 → L5Month-end works, but the audit trail is still manual.
HR & People
L2 → L4Onboarding is ad-hoc, role descriptions are patchy.
IT & Engineering
L3 → L4Stack in motion, governance not yet landed.
How the programme runs
Four steps that apply to every variant.
Diagnose
Maturity grid across four domains. Shadow days with operating teams. Honest inventory.
Prioritise
Not everything at once. What first, what waits, what we deliberately leave.
Build & embed
Processes and artefacts that actually get used, with ownership transfer and a maintenance cadence.
Handover
We leave. You have what you need. Quarterly check-in optional.
Artefacts that outlive the growth spurt
Three core deliverables produced in every SCALE variant, adjusted in shape and depth to the specific situation.
Maturity grid
Honest inventory across operations, finance, HR, and IT, comparable, versionable, unadorned.
Remediation backlog
Prioritised list of the gaps, with leverage, effort, and owner, what actually has to get done.
Cross-domain RACI
Decision rights across every domain, with named people, no grey zones, no founder bottlenecks.
What typically follows
SCALE is a productised programme with a clear end. What comes next depends on the variant.
Ongoing support (SUSTAIN)
Operating Model or Compliance Custodianship, monthly rhythm so the work does not decay.
To SUSTAIN →Fractional CIO
Senior IT leadership, when the programme surfaces technology decisions as the next hurdle.
To Fractional CIO →Compliance & specialise
When a framework (ISO, SOC 2, NIS2, DORA) is next and processes need to become audit-ready.
To SPECIALISE →