Stage 5
Activate
Roll the hub out team by team, paired to real work. Most of the edits the hub will ever need surface in these sessions.
Deployment engagement
ControlShift™ Phase 2
Activate & Embed
Phase 1 builds the Operational Intelligence Hub. Phase 2 puts it to work. Stages 5 to 8 of ControlShift, Activate, Amplify, Refine, Oversight, turn the documented asset into a live operating system woven into your team's daily workflow.
What It Is
The deployment engagement.
A hub full of documented process is an asset on a shelf until it's woven into the work. Phase 2 is the engagement that does that weaving.
Phase 1 produced the asset. Phase 2 makes it operate. Stages 5 to 8 of ControlShift, Activate, Amplify, Refine, Oversight, handle the four moves that turn documentation into infrastructure: team adoption, tooling integration, drift detection, and the operational rhythm that keeps it alive.
Scoped to your team size and tooling complexity. When it's done, your operations don't depend on anyone remembering to check the hub because the hub arrives where the work is.
How It Works
Four stages of work, in sequence
Stage 6
Amplify
Integrate the hub with your CRM, project management tool, and field-service systems. Relevant sections surface inline at decision points.
Stage 7
Refine
Install the drift-detection rhythm: a named owner on every section, a monthly review pass, and a "Suggest an update" route on every page so anyone doing the work can flag a divergence in seconds. Divergence surfaces in weeks, not at an annual rewrite.
Stage 8
Oversight
Stand up the operational dashboards and weekly review cadence. Leadership operates the codified asset and the business runs without depending on any single person.
Outcomes
What changes when the hub goes live
Adoption stops being an exercise
When the hub is woven into the tools the team already uses, you stop having to remind people to consult it.
Drift becomes visible
Every section has a named owner, every page has a "Suggest an update" button, and there's a monthly pass through what came in. Divergence surfaces in weeks, from the people doing the work, instead of piling up until someone rewrites everything.
Operations run without you
The pattern of "everything routes through the founder" breaks. Decisions happen where they should, at the documented decision points.
New hires onboard faster
The hub's training module is now the onboarding system, not a document handed out and forgotten. Courses get assigned by person and role, sign-off is recorded, and senior-to-junior knowledge transfer compresses.
Diligence becomes possible
If you ever transact, the operational asset is now demonstrable. Buyers see a working system, not a binder of SOPs.
Ready for the Retainer
Phase 2 sets up the rhythm that the ControlShift Retainer sustains. The handoff is built in.
Pricing
Scoped per business
Phase 2 engagement pricing is scoped per business based on team size and the tooling integration scope. Typically less per week than Phase 1 because the heavy capture and codify work is already done.
We scope Phase 1 and Phase 2 together from the discovery call, so you have a complete picture of the full codification + deployment cost upfront, no surprises midway.
Book a discovery call to get a scoped quote.
Common Questions
Phase 2, answered.
What is ControlShift Phase 2?
The deployment engagement that follows Phase 1.
Phase 1 builds the Operational Intelligence Hub and the underlying Codified Operational Intelligence; Phase 2 deploys that asset into the team's daily work. Covers ControlShift stages 5 to 8: Activate (embed in team culture), Amplify (integrate into tooling), Refine (the drift-detection rhythm: named section owners, a monthly review pass, in-hub update suggestions), Oversight (operational dashboards).
Duration and pricing are scoped per business based on team size and tooling complexity.
Why is Phase 2 separate from Phase 1?
Two reasons:
- Phase 1 produces a tangible asset (the hub) that you can evaluate before committing to deployment.
- Deployment work has a different character than codification work. It involves change management, tooling integration, and habit-building in the team. Compressing both into a single engagement gives the deployment stages too little runway.
The split lets each phase have the focus it needs.
Do I have to start Phase 2 right after Phase 1?
No. Some clients pause between phases to operate with the Phase 1 deliverable for a quarter, find the rough edges, then commit to Phase 2 with sharper deployment priorities.
Most start Phase 2 within 30 to 60 days because the hub's value compounds rapidly once deployed. The gap is up to you.
What does Phase 2 cost?
Scoped per business based on team size and the tooling integration scope.
Scoped at the same time as Phase 1 from the discovery call, so you have a complete picture of the full codification + deployment cost upfront.
Already done Phase 1? Or scoping both?
A 30-minute discovery call ends with a scoped quote for Phase 1, Phase 2, or both as a sequence. Yours to evaluate, no commitment.