Operating Model & Scale Readiness
A focused operating reset for companies preparing for their next stage of growth.
Fix the operating model before the milestone, not after it.
Growth milestones expose whatever was already fragile. Investor diligence brings questions into processes nobody had written down. A first enterprise customer brings assurance and delivery expectations the business has never had to meet. Doubling the team turns informal coordination into a bottleneck within a quarter.
This is a defined piece of work to get ahead of that. It clarifies who decides what, where work moves between functions, what data the business actually captures, and what rhythm holds it together. Then it leaves behind a plan the team can execute without external help.
It is a project with an end date. Where the need is ongoing senior ownership rather than a reset, a fractional COO engagement is the better structure.
What usually triggers this work
This work is usually triggered by something specific on the horizon. These are the conditions that make it worth doing first.
A milestone is approaching
Investor diligence, a customer assurance request, a significant hiring wave, or a market expansion. Each one tests the operating model in a way the business has not been tested before.
Accountabilities are ambiguous
Several people feel responsible for the same outcome. Decisions get made twice, or not at all, because the boundary was never written down.
Hand-offs leak
Work loses information moving between sales, delivery, product, and support. The failures are predictable, repeat, and are treated as individual mistakes.
The data does not support decisions
Reporting exists but leaders do not trust it, definitions differ between teams, and the numbers in a board pack take days to assemble by hand.
Planning is disconnected from execution
Quarterly goals are set and then run separately from how the week actually works, so the plan and the business drift apart within a month.
Diligence would be uncomfortable
If an investor or enterprise buyer asked how the business runs, the honest answer would be assembled after the question rather than before it.
What the work covers
Five areas. A typical engagement goes deep on two or three and touches the rest, depending on where the milestone puts pressure.
Operating model and decision rights
Establish who owns which outcomes and who decides what, at which threshold, so decisions stop routing to the founder by default.
- Accountability map
- Decision rights by category
- Escalation paths
- Role boundaries
- Approval thresholds
Leadership cadence and planning
Build the rhythm that connects quarterly intent to weekly execution, and make sure it produces decisions rather than updates.
- Weekly operating review
- Monthly planning reset
- Quarterly system review
- OKRs or equivalent
- Decision and action record
Data capture and reporting
Decide what the business needs to know, define it once, and capture it where the work already happens rather than in a parallel spreadsheet.
- KPI definitions
- Source-of-truth mapping
- Management reporting pack
- Board reporting
- Data capture points in the workflow
Customer and delivery hand-offs
Redesign the points where work crosses between functions, which is where most operating failures actually originate.
- Sales to delivery hand-off
- Onboarding sequence
- Escalation and support paths
- Renewal and expansion triggers
- Closure and offboarding
Customer assurance, risk, and continuity
Prepare the operational evidence and accountability an investor, customer, or partner may ask to see. This is operational readiness, not legal advice, regulatory certification, or an audit opinion.
- Control ownership
- Operational evidence
- Vendor process
- Incident and continuity plan
- Customer assurance and diligence readiness
Ready, and not ready
Scale readiness is not a score, but it is assessable. These are the dimensions the work moves, and the difference between a business that is ready and one that is about to find out it is not.
Most companies are strong in two or three of these and weak in the rest. The weak ones are where the milestone will hurt.
| Dimension | Not ready | Ready |
|---|---|---|
| Accountability | Several people feel responsible | One named owner per outcome |
| Decisions | Escalate to the founder by default | Written rights and thresholds |
| Cadence | Meetings produce updates | Forums produce decisions with dates |
| Data | Numbers assembled by hand | Defined once, captured in the workflow |
| Hand-offs | Failures repeat and are blamed on people | Designed, visible, and owned |
| Documentation | Process lives in senior heads | Core processes written and usable |
| Diligence | Answers built after the question | Evidence already in place |
Diagnose, design, plan, hand over
A defined engagement, typically four to eight weeks depending on the size of the business and how much is already documented.
- 01 · Diagnose
Map how the business actually runs rather than how the org chart says it does. Interview the leadership team, follow real work through its hand-offs, and review the existing reporting.
Typical output- Current-state operating map
- Accountability and decision audit
- Hand-off failure points
- Data and reporting review
- The binding constraints, prioritised
- 02 · Design the target model
Agree who owns what, who decides what, and how work should move. The design is tested against the team and systems that exist, not an idealised version of them.
Typical output- Accountability map
- Decision rights and thresholds
- Redesigned hand-offs
- Cadence design
- KPI and reporting definitions
- 03 · Build the 90-day plan
Sequence the changes so the business can absorb them. A plan that assumes spare capacity nobody has is a plan that will not run.
Typical output- Sequenced 90-day plan
- Named owners per change
- Quick wins in the first fortnight
- Risks and dependencies
- Measures of progress
- 04 · Start it and hand over
Run the first cycles alongside the team rather than handing over a document. A cadence that has never been run is a proposal, not a system.
Typical output- First operating reviews run together
- Reporting pack in use
- Leaders owning their own forums
- Documented operating model
- A review point at 90 days
The engagement ends with the team running the model themselves. Where ongoing senior ownership turns out to be the real need, that is a fractional COO engagement and worth naming as a separate decision.
Five engagements, in outline
Illustrative patterns rather than client work, showing the shape of a typical engagement.
- Ahead of investor diligence
- Core processes get documented, the reporting pack is built from operating data rather than assembled by hand, and key-person dependencies are identified and reduced before diligence begins.
- First enterprise customer
- Delivery hand-offs, control ownership, vendor processes, and incident paths are clarified before a customer assurance review or contract deadline.
- Doubling the team
- Accountabilities and decision rights are written down while the company is still small enough to agree on them, so new starters join a system rather than an oral tradition.
- Reporting nobody trusts
- KPI definitions are agreed once, capture points move into the systems where work already happens, and the weekly pack stops being a manual assembly job.
- Post-reorganisation reset
- After a restructure or a leadership change, ownership and cadence are re-established deliberately rather than being left to settle on their own over two quarters.
Scope and timing
This is normally a defined fixed-scope project of four to eight weeks, priced against the outcome rather than a day rate. Scope names the deliverables, dependencies, acceptance criteria, and end point. Larger or more distributed businesses take longer, and businesses that have already documented a lot take less.
Some engagements continue into a light retainer while the 90-day plan runs, with agreed capacity, priorities, decision rights, and review points.
Engagement Model
Engagements are shaped around the work, not a fixed format. Defined projects set deliverables, dependencies, acceptance criteria, and an end point. Hourly support suits bounded advice or execution. Ongoing retainers set available capacity, priorities, decision rights, cadence, and a review point.
The scope names its deliverables and its end point. If the diagnosis shows the real need is ongoing operating leadership, that is said plainly rather than absorbed into a larger project.
Before and after this work
Fractional COO & Chief of Staff
Owning company-wide operating practices on an ongoing basis, rather than resetting them once, is a role rather than a project.
AI & Workflow Systems
Once the process is clear and stable, the repeatable parts of it are worth automating. That work comes second, deliberately.
Further reading.
What Investors Actually Check in Diligence
Diligence rarely fails on the pitch. It fails on whether the business can evidence how it runs. What gets checked, and where founders get caught.
A Startup Leadership Cadence Template That Creates Follow-Through
A leadership cadence for startup teams that need clearer decisions, ownership, and follow-through.
Founder Bottleneck Diagnostic: Is Your Startup Too Dependent on You?
For founders who suspect their attention, context, and decision-making have become the limit on growth.
Frequently asked questions
How long does an operating model engagement take?
Typically four to eight weeks, depending on the size of the business and how much is already documented. That covers diagnosis, target design, and a sequenced 90-day plan, with the first operating cycles run alongside the team.
What do we actually get at the end?
A documented operating model covering accountabilities and decision rights, a leadership cadence the team is already running, agreed KPI and reporting definitions, and a sequenced 90-day plan with named owners.
How is this different from a fractional COO engagement?
This is a project with an end date that resets the operating model and hands it over. A fractional COO is a role that owns and runs the operating system on an ongoing basis. Companies often do this first and decide afterwards whether the role is needed.
Do we need this before automating anything?
Usually, yes. Automating a process that is unclear or about to change tends to lock in the wrong version of it. Getting the operating model stable first makes the automation work faster and cheaper.
Will this work if our team has no spare capacity?
It has to. The 90-day plan is sequenced against the capacity that actually exists, and the diagnosis usually finds work that can be removed rather than only work to add.
Does this include legal, regulatory, certification, or audit advice?
No. I help leadership teams clarify operational ownership, evidence, processes, vendors, and continuity. Legal, regulatory, certification, security-assessment, and audit work remains with the appropriate specialist advisers.
Get ahead of the milestone.
If something significant is coming and the honest answer to how the business runs would have to be assembled after the question, that is the place to start. The first conversation is about what is approaching and what it will test.
I aim to respond within two business days.