P
Profile
The essentials about the business: company history, mission, vision, values, BHAG, market positioning, scope of services. The "what we are and why we exist" section that anchors every other chapter in the Playbook.
Flagship Service
Your Business Playbook
A documented, central source of truth for how your business operates. Every process, role, standard, and decision, in one place your team works from every single day.
What It Is
The operating system for your business.
A Business Playbook is the documented answer to one question: how does this business work? Not "what do we sell", how do we actually run. Every process, role, standard, and decision in one place your team can find, learn from, and improve on.
Done well, a Playbook is the difference between a business that depends on you and one that runs without you in the room. New hires onboard in weeks instead of months. Quality stops being a function of who happened to do the work. Knowledge stops walking out the door when people leave.
We build Playbooks with your team, not for them. The people doing the work know it best, our job is to extract, structure, and document it so the next person doesn't have to re-discover it.
What's Inside
Structured around the 5P Scorecard
Every Business Playbook we deliver is built around the 5P Scorecard, the structural blueprint we capture in Stage 2 (Design) of the ControlShift™ methodology. Five foundational dimensions, each one expanded into a working section of your Playbook and a top-level section of the hub your team works from.
P
People
Org chart, role descriptions, accountabilities, hiring criteria, performance standards, key internal and external relationships. Who does what, to what standard, and how the team is wired together.
P
Policies
Workplace policies, employee handbook, governance rules, decision rights, escalation paths, tool-stack ownership. The rules of engagement that keep the team consistent without the founder in the room.
P
Process
How work flows end to end, as swim-lane maps: enquiry to quote to schedule to job to invoice, with every handoff between roles visible and every decision point marked. The layer that shows where work actually stalls or gets dropped.
P
Procedures
The step-by-step SOP library, organized by department: how each individual task gets done, with owners, inputs, outputs, quality benchmarks, and exception handling. Every step on a process map links to the procedure that performs it.
Process is the map; Procedures are the steps. The 5P Scorecard is the structural foundation, and the Playbook is what gets built on top of it. Full definition in the glossary →
Engagement Timeline
A typical Playbook engagement
Our baseline commitment: your core processes codified inside 16 weeks from kickoff. Most clients then continue on a retainer to go deeper, adding more processes, refining as the business evolves, and running ControlShift's Amplify, Refine, and Oversight stages as an ongoing partnership.
- 1
Discover
Assess current state. Define scope and priorities with leadership.
- 2
Map
Workshop with each team to map their workflows end-to-end.
- 3
Document
Convert maps into SOPs, role docs, and Playbook sections inside your hub.
- 4
Embed
Roll out to the team. Train, gather feedback, iterate. The Playbook becomes the daily reference.
Where It Lives
We build you a hub, and your business owns it.
Your Playbook is delivered as an Operational Intelligence Hub: a web application built for your business, on your terms, owned by your business. Not a template, not a seat rented from someone else's product. Hubs are live today for two clients.
You can walk through a fully populated one before you commit. The demo is built on a fictional company, Alpine Mechanical Systems, with every section filled in the way a real engagement leaves it.
Already running Trainual, Whale, Notion, Confluence, SharePoint, or ClickUp and settled there? We're a Trainual Certified Partner and a Whale Certified Partner, and we'll build inside your platform instead. That's the exception, not the default.
What's in the hub
- Weekly Scoreboard. The KPIs that tell you whether the operation is healthy this week.
- Operational Intelligence sections. Profile, People, Policies, Process, Procedures.
- Clickable swim-lane process maps. Every handoff visible, every step linked to the procedure that performs it.
- SOP library by department. The step-by-step procedures, organised the way the business is organised.
- Training module. Courses assembled from the codified pages, assigned to people and roles, with end-of-course sign-off and an audit record.
- Critical Impact Goals. Annual and quarterly, visible to the people responsible for them.
- Time & Pay. Hours and pay information in the same place as the work.
- Role-based permissions and Google sign-on. People see what's relevant to them, with no extra password to remember.
- "Suggest an update" on every page. The people doing the work flag anything that no longer matches reality.
What you actually walk away with
- Scope
- 8 to 12
- Timeline
- 16 weeks
- Ownership
- Yours
core processes captured and codified in Phase 1
from kickoff to a working hub your team can open
the hub and everything in it belongs to your business
Scope and timeline are our published Phase 1 commitment. See the week-by-week roadmap →
Common Questions
Business Playbooks, answered.
What is a Business Playbook?
A central, documented source of truth for how a service business operates. Every key process, role, standard, decision, and edge case captured in one place that the team actually works from every day. By default we deliver it as an Operational Intelligence Hub, a web application built for your business and owned by your business.
The Playbook is the visible deliverable. The underlying asset is Codified Operational Intelligence, the captured judgement and reasoning that makes the Playbook usable, not just present.
What goes inside a Business Playbook?
Six interlocking layers:
- The operational systems blueprint, how each major function (estimating, delivery, billing, onboarding) is meant to work end-to-end.
- Process maps showing the sequence of activities inside each system.
- Standard Operating Procedures for individual tasks.
- Decision documents capturing the rules and reasoning behind escalations, pricing, scope, and judgement calls.
- Role-based access so each team member sees what's relevant to them.
- Search and inline help embedded in the team's daily workflow, not in a separate destination.
Where does the Business Playbook live?
By default, in an Operational Intelligence Hub we build for you: a web application owned by your business, holding the weekly Scoreboard, the five Operational Intelligence sections, clickable swim-lane process maps, the SOP library by department, the Training module with assignment and end-of-course sign-off, Critical Impact Goals, Time and Pay, role-based permissions, Google sign-on, and a "Suggest an update" route on every page.
Hubs are live today for two clients. You can walk through a fully populated one first: the hub tour shows every section, and the live demo is built on a fictional company, Alpine Mechanical Systems.
If you already run Trainual, Whale, Notion, or Microsoft SharePoint and your team is settled in it, we'll build there instead. That's the exception rather than the default, and we'll say so plainly on the call. (Comparison of the third-party options: Trainual vs Whale vs Notion, and our read on AI-native knowledge hubs.)
How long does it take to build a Business Playbook?
Phase 1 of the ControlShift engagement, 16 weeks, captures and codifies the 8 to 12 core processes that drive most of the business. The output is a working Business Playbook, delivered in your Operational Intelligence Hub, with the underlying Codified Operational Intelligence for those processes.
Phase 2 (deploying it to the team, integrating it into daily workflows, standing up the monthly drift-detection review rhythm) is a separate follow-on engagement. The 16-Week Roadmap walks through Phase 1 week by week.
What's the difference between a Business Playbook and a folder of SOPs?
A folder of SOPs is a collection of standalone documents. A Business Playbook is a working operating system. The difference shows up in three places:
- Structure. The Playbook organises content by the business's systems, processes, and procedures hierarchy, not by document type.
- Reasoning. The Playbook includes the decision layer, why each rule exists, what pattern it's catching, the edge cases.
- Integration. The Playbook lives where the team's work happens, surfaced inline at the moment a decision is being made.
SOPs in a folder get ignored. Playbooks woven into the workflow get used. (More on that here.)
Who maintains the Business Playbook after it's built?
Each Playbook section has a named owner within your business, typically a senior operator or team lead, not the founder. The owner is responsible for keeping that section current.
The people doing the work keep it honest. Every page in the hub carries a "Suggest an update" route, so the moment someone hits a step that no longer matches how the job actually runs, they flag it instead of quietly working around it. Those suggestions land with the section owner, who works through them in a monthly review pass. That is the drift-detection rhythm: named owners, a standing monthly review, and a feedback route the team actually uses. No software watches your operation for you.
Expansive EDGE remains available on a light retainer for ongoing support, but the hub is yours and the maintenance is owned in-house.
Ready to build your Playbook?
Start with a discovery call. We'll scope what your Playbook would look like and what it would take to build it.