Most operations consulting promises live in the conditional tense.
"It depends on the scope." "Every engagement is different." "We tailor the timeline to your business." Sometimes those statements are honest. More often they're shields. The consultant doesn't actually know how long the work takes because the work itself has never been the same twice.
I get it. Service businesses really are different. A 35-person mechanical contractor isn't a 12-person cleaning company. A multi-site oil and gas service shop isn't a single-location restoration crew. The differences are real and the work flexes around them.
But the shape of the work doesn't change, and when you focus the scope, the timeline becomes predictable. This article walks one specific engagement: the first four stages of ControlShift (Insights, Design, Capture, Codify) applied to the small set of processes that actually drive most of your business. We call that scope your core processes. We do this work in 16 weeks with surprising consistency, because the scope is held.
What you don't get inside the 16 weeks: deployment to the team (Activate), tooling integration (Amplify), drift detection (Refine), or the ongoing rhythm (Oversight). Those are the back half of ControlShift and they belong in a separate Phase 2 engagement once the asset built in Phase 1 has been validated. I'll explain why this split matters at the end.
What "core processes" means
Not every process in a service business is equal. A typical 35-person service company has somewhere between 20 and 50 distinguishable processes, depending on how you count. Eight to twelve of them carry most of the value. Those are the core.
The core processes are the ones that meet three tests:
- They drive revenue or absorb the most cost. The service delivery you sell. The estimating or quoting flow that converts opportunities into work. The client onboarding that determines whether a project starts well.
- They carry the most key-person risk. The work that depends on a small number of senior heads, where a departure would meaningfully hurt the business.
- They shape the rest of the operation downstream. Get them right and the surrounding processes mostly behave. Leave them undocumented and everything else inherits the chaos.
The first stage of the 16-week engagement identifies which processes in your specific business meet those tests. Most owners can name two or three without help; we surface the others through structured diagnostic conversations and a light data pass.
Once the list is named (usually 8 to 12 core processes), the rest of the engagement focuses there. Non-core work stays out of scope. That's the trade that makes the timeline real.
The shape of the 16 weeks
Four stages, four phases of work, each one with its own character.
| Phase | Weeks | ControlShift stage | What it feels like |
|---|---|---|---|
| Diagnose | 1 – 3 | Insights | "We're finally being asked the right questions." |
| Architect | 4 – 6 | Design | "Now we can see the target state, not just the current one." |
| Extract | 7 – 12 | Capture | "There's a lot more in our heads than we realised." |
| Structure | 13 – 16 | Codify | "Now it's an asset we own." |
Different businesses spend slightly different amounts of time inside each phase. The 16-week envelope holds because the scope is held.
Weeks 1 – 3: Insights
The Insights stage is diagnostic. We're answering two questions: which processes are the core ones for your business, and what's the operational gravity inside each of them today?
What happens. Structured conversations with the leadership team and a handful of senior operators. A read of existing documentation (process maps, SOPs, the proposal templates your team uses, the project closeout reports). A light review of the operational data you already have: win rates, utilisation, time-to-onboard, customer satisfaction patterns, project margin variance.
Deliverable. A written recommendation. Twelve to twenty pages. It names the 8 to 12 core processes for your business, ranks them by financial impact and key-person risk, and lays out the specific operational gaps inside each. This is the document that scopes the rest of the engagement.
What the team feels. Most leadership teams describe this stage as "the first time someone's asked the right questions." The right questions aren't about what's broken (everyone has those answers ready). They're about what's working and why, and which of the working parts depends on one specific person staying in the building.
The extra time in this stage (three weeks instead of the two we used to allocate) lets us go deeper into the data and run a second-round confirmation with the leadership team before the scope is locked.
Weeks 4 – 6: Design
The Design stage is where the operational architecture for the core processes gets drawn. Not procedures yet. The system-level shape.
What happens. We work with leadership to decide what each core process should look like once it's working. Inputs, activities, outputs, feedback loops, ownership. Where the process starts and ends. What hands it off to. What signals tell you it's healthy or drifting. For a deeper read on why we separate these layers, see Systems, Processes, Procedures.
Deliverable. A set of design blueprints, one per core process. Each blueprint describes the target shape and names the gaps between current state and target state. A sequencing plan also comes out of this stage: which core process do we capture first, second, third, so the work compounds.
The hard moment. Some of the blueprints will not match the way the process runs today. That's the point. Leadership has to choose which gaps to close inside the 16 weeks and which to defer to Phase 2 or beyond. We help. The calls are yours.
Weeks 7 – 12: Capture
This is the longest stretch in the engagement and the one most operators underestimate. Six weeks, focused on the core processes, surfacing the operational knowledge that currently lives in your senior people's heads.
What happens. AI-structured interviews with the key knowledge-holders in each core process. Walkthroughs of real recent work with the people who did it. Decision-capture sessions where we work through "what would you do if…" scenarios and document the reasoning, not just the answer. Cross-team sessions where two operators with the same job title turn out to be doing similar work differently, and we figure out which version actually holds up.
For a deeper look at how the interviews specifically work, see our methodology piece on AI-structured interviews.
Deliverable. A working library of captured knowledge per core process. Not polished yet. The output of Capture is raw structured information: decision rules with their reasoning, process steps with their inputs and outputs, edge cases with their handling, judgement calls with the senior operator's logic attached.
What the team feels. Mild overwhelm at the midpoint. By week 10, the volume of captured material is large enough that it doesn't yet feel useful. Trust the process. The next stage exists to fix this.
The reason this stage is six weeks (longer than in our older engagement model) is that we're going deeper inside each core process now that we're not trying to span the whole business. The depth shows up in the asset's usefulness later.
Weeks 13 – 16: Codify
Codify is where the captured material becomes a structured, usable Business Playbook for the core processes.
What happens. Structuring, editing, organising. Captured knowledge gets sorted into the right systems, the right processes, the right procedures. (We covered this hierarchy in a previous article.) Decision rules get pinned to the moments in the process where they apply. Edge cases get linked from the main procedures so people find them when they need them, not before.
The Playbook lives in the platform you'll eventually use day to day (most often Trainual or Whale; see our three-way comparison or our piece on AI-native knowledge hubs for the broader options). Even though we're not deploying it to the team in this engagement, the format matches the eventual home, so Phase 2 doesn't need a migration step.
Deliverable. A first version of the Business Playbook for your core processes. Searchable, linked, owned. Plus a handoff document specifying what's needed for Phase 2 (Activate, Amplify, Refine, Oversight).
What changes. Around week 14, leadership starts to see the shape of the asset they've been building. The captured material from weeks 7–12 stops feeling like a pile and starts feeling like a structure. People who were ambivalent in week 10 become believers in week 14.
What you actually have at week 16
Three concrete things. Be clear-eyed about what's in this list, and just as clear-eyed about what isn't.
1. A documented Business Playbook for your core processes. Structured, hosted in a Playbook platform, organised by the system and process hierarchy. The 8 to 12 highest-value processes in your business are now written down in a form that doesn't depend on the specific people who carry the knowledge today.
2. Codified Operational Intelligence for those core processes. The decision rules and operational judgement your senior people were carrying in their heads, now structured, searchable, and transferable. (For a deeper explanation of what this means, see our page on Codified Operational Intelligence.)
3. A Phase 2 handoff plan. A scoped, sequenced plan for the next engagement: which teams to roll the Playbook out to first, which tooling integrations to wire up, how the drift-detection rhythm should be set up, and what the Oversight cadence should look like. Phase 1 is the asset. Phase 2 is the operating system that runs on the asset.
Critically, here's what's not in the deliverable: the Playbook isn't yet live in your team's day-to-day work. People aren't using it. Drift isn't being detected. The Oversight rhythm isn't running. Those things take a follow-on engagement.
Why we split it this way
The older version of our engagement tried to do all eight ControlShift stages inside 16 weeks. We found two consistent problems with that approach.
First, the scope was too wide. Trying to capture and codify every operationally-relevant process in a service business in 16 weeks is genuinely possible, but the depth in any one process is shallower than it needs to be. The Playbook ends up broad and thin. By focusing on core processes only, we go meaningfully deeper in each, and the asset is more durable.
Second, the deployment work needed its own runway. Activate, Amplify, Refine, and Oversight are real stages. They involve change management, tool integration, and habit-building inside the team. Trying to compress them into the last two or three weeks of an engagement gave them too little time, and the Playbook often stalled in rollout. Treating those stages as a separate Phase 2 engagement gives them the focus they deserve.
The split also matches how owners decide. Phase 1 produces a tangible asset you can evaluate. If it's good (and it usually is) you commit to Phase 2 with full conviction. If it surfaces issues that need to be addressed first, you have the asset to plan against without having spent the deployment budget yet. Less risk, sharper decisions.
What Phase 1 doesn't do
Honesty time.
Sixteen weeks of Phase 1 work is not going to fix a business that has the wrong people, the wrong service offering, or the wrong cost structure. It assumes the business is fundamentally sound and is held back by its operating shape. If the underlying business model needs work, that's a different conversation.
It also doesn't replace the leadership work of running a service business. The Playbook is structured documentation. Decisions still get made by humans. Cultures still get shaped by leaders. The Playbook makes those things easier, not automatic.
And: Phase 1 produces an asset. The compounding value of the asset shows up in Phase 2 and beyond, when the Playbook is in your team's hands, drift is being detected, and the Oversight rhythm is running. Phase 1 is the start, not the finish. It's also the thing that makes the rest of the journey possible.
A note on non-core processes
The 8 to 12 processes we capture in Phase 1 cover most of the value in a service business. They don't cover everything. HR onboarding, financial close, certain back-office workflows, the periodic strategic exercises a leadership team runs, these often live outside the core list.
That's by design. Most of the non-core processes can be tackled later with much less effort, because the methodology is established, the team understands the format, and the cultural pattern of working this way is in place. A non-core process that would have been a six-week engagement on its own becomes a two-week engagement once the core is done.
The compounding effect is real. The work to codify your full business eventually happens in cycles, with the core as the foundation. Phase 1 is the foundation cycle. Everything after is shorter, faster, and built on the same patterns.