The Operations Manual Test: Seven Sections to Write Before Anyone Else Delivers Your Work

Here is a test most founders of expertise businesses fail. Imagine couriering your operations manual to a capable professional you have never met, in a city you have never visited. Could they read it, train against it, and deliver an engagement your client could not tell apart from one you delivered yourself? If the honest answer is no — or if the honest answer is "what operations manual?" — you are not ready to hire, certify, or license anyone.

This is the discipline behind Michael Gerber's Franchise Prototype: build your business as if it were the model for thousands of identical operations, even if you never open a second one. His instruction is blunt — pretend the business you own today is the prototype for 5,000 more just like it. Ray Kroc understood this before almost anyone. McDonald's was never really a hamburger company; it was a system for producing the same hamburger through ordinary people, anywhere, every time. An expertise business that wants to scale faces exactly the same design problem.

Compare that to how the typical consultancy, agency, or coaching firm actually transfers the work. The founder hires someone promising, shares a handful of client files, says "shadow me for a few weeks," and declares them trained. Half a year later, quality is sliding, clients are escalating, and the founder is spending more hours repairing other people's deliverables than they ever spent producing their own.

Gerber calls this pattern "management by abdication," and the distinction matters. Delegation hands over responsibility together with systems and accountability. Abdication hands over responsibility with neither. The cure is not standing over people's shoulders. The cure is a manual good enough that you don't have to.

So what does "good enough" mean? It means the manual covers seven specific areas. Treat the list below as an audit: each section your manual is missing is a specific, predictable way your scaling attempt will break.

Section One — Who You Serve, and Who You Turn Away

The Chapter Almost Nobody Writes

Most audits of an operations manual would start with the methodology. Start here instead, because this is the section service founders almost never formalise — and its absence poisons everything downstream. A documented process applied to the wrong client still produces a bad outcome, a frustrated team, and a dent in your reputation.

Mike Michalowicz's Pumpkin Plan gives you the lens. Your "top pumpkins" are the clients who create the most value with the least friction — right industry, right size, right problem, and genuinely committed to changing something. Bad-fit clients are the inverse: they absorb a disproportionate share of your team's energy and return disproportionately weak results. Your manual should make the boundary explicit:

• Ideal client profile: The industries, company sizes, revenue ranges, and problem types that sit squarely in your sweet spot.
• Qualification gates: What has to be verified before anyone invests time in a proposal — budget authority, strategic urgency, willingness to actually do the work.
• Red flags: The observable warning signs of a bad fit. A trail of launched-and-abandoned initiatives. Pushback against following a structured methodology. The expectation that your team performs while the client watches.
• The graceful no: Exact language for declining, and when to refer the prospect somewhere better suited.

Why does this need to be written down? Because without criteria, practitioners default to accepting anyone with a budget. That looks like growth. It is actually the express lane to inconsistent outcomes, exhausted delivery teams, and a brand that means nothing specific to anyone.

Saying no to the wrong clients is what frees the capacity to be extraordinary for the right ones. Put the criteria on paper so your team can make that call without ringing you first.

Section Two — The Engagement, Mapped From First Call to Final Deliverable

Turning Instinct Back Into Process

Next, the full arc of an engagement: every phase, the inputs and outputs of each, the decisions that have to be made along the way, and who owns them. Founders assume this part is easy because they perform it daily. That is precisely the problem. The sequence has never been written down because it has never needed to be — it lives in your head.

Watch yourself in a client session and you'll notice dozens of unconscious moves per hour: choosing when to dig deeper, when to switch approach, when to flag a risk. After enough repetitions, expertise stops feeling like a procedure and starts feeling like intuition. Intuition is wonderful — and completely non-transferable. A business scales on process, not on the founder's instincts.

"Notes help you remember. Systems help a stranger repeat. The difference is not the content — it is the audience you write for. Most founders write for themselves."

This is where Gerber's 5,000-prototype framing earns its keep. Documenting "how I run a workshop" produces a memory aid. Documenting "how any trained practitioner runs this workshop — scripts, timings, materials, contingency plans" produces a system. Likewise, "how I deal with a hard client" becomes "the five objections we hear most, the response to each, and the escalation route when the response fails."

If a blank page paralyses you, use Michalowicz's Live Capture technique. Record yourself delivering the next engagement and narrate the judgment calls out loud as you make them: this answer signals that, so I'm shifting to this approach. Hand the annotated recording to whoever inherits the work. Will the first draft have holes? Of course. A process document that is 70 percent complete and exists beats one that is 100 percent complete and trapped in your skull.

Publish the rough version, run it, and revise. Around the third pass, it stops being rough.

Section Three — A Diagnostic That Behaves the Same in Every City

Questions, Scoring, Interpretation, Report — All of It

If your methodology includes an assessment — and for most expertise businesses it should — the assessment needs its own complete chapter. The standard is strict: a trained practitioner in London, Dubai, Sao Paulo, or New York must produce the identical diagnostic output from the identical client inputs.

Documenting this is usually where founders meet the gap between what they actually do and what they believe they do. Running your own diagnostic, you silently reshape questions based on what the client just said, weight some answers more heavily because of context, and read the scores through the memory of hundreds of prior assessments. Every one of those adjustments is invisible — until someone else has to replicate your results without them.

Five components belong in this section:

• The questions, verbatim — fixed wording on everything that gets scored. Improvisation lives elsewhere.
• The scoring logic — the mapping from each answer to a number, the weighting across dimensions, the aggregate formula.
• The interpretation key — why a 42 is materially different from a 68, and what each maturity band means — for instance Foundational (1-20), Developing (21-40), Established (41-60), Advanced (61-80), and Leading (81-100).
• The report template — the structure of the findings, the required visualisations, the narrative arc the client reads.
• The session guide — how to run the 60-90 minute guided conversation: which probes to use, which follow-ups to ask, what to do with ambiguous answers.

The goal is that a client in any market receives the same analytical rigour as a client in your home market — not because every practitioner is brilliant, but because the instrument they wield is.

Section Four — The Delivery Playbook, at 20/80 Depth

Sessions, Materials, Handoffs — Without Drowning in Detail

The fourth section describes how the engagement is physically delivered: the number of sessions, the agenda of each, the materials in play, what the client walks away with at every stage, and how work passes between phases and people.

The trap here is exhaustiveness. Founders either document nothing or attempt to document everything — and the everything-documenters never finish. Gino Wickman's 3-Step Process Documenter is the antidote:

• Identify the 6-10 core processes — the major repeatable activities your business runs on.
• Document each at 20/80 depth: the 20 percent of steps responsible for 80 percent of the outcome, captured in 1-5 pages per process.
• Package the set as "Your Way" — the branded manual every practitioner is trained on and held to.

The 20/80 constraint is not laziness; it is what makes the project finishable. Training and supervised practice fill in the remaining texture. The target state is structured freedom: a delivery framework rigid enough that a newly trained practitioner can execute it solo, with clearly marked decision points where an experienced practitioner's judgment is welcome.

And do not hold the playbook hostage to perfectionism. Insisting on a flawless manual before transferring any work is procrastination wearing a diligence costume.

Section Five — A Quality Bar You Can Actually Inspect

If "Good" Is Not Defined, Every Practitioner Defines It Themselves

This section is the dividing line between methodology businesses that scale and methodology businesses that scale briefly and then implode. Without a written quality standard, "quality" is a private opinion held separately by each person on your team. One practitioner ships a 40-page assessment with rich data visualisation; another ships a 5-page bullet-point summary. Each is sincerely proud of their work. Your clients, meanwhile, experience a brand that behaves like a lottery.

Standards only function if they are specific and observable. Vague aspirations ("excellent client service") cannot be inspected. These can:

• Deliverable specifications: Required sections, minimum length, mandatory visualisations, formatting templates, branding rules.
• Satisfaction floors: Minimum NPS or client satisfaction scores, with a defined escalation path the moment a score falls below the line.
• Adherence checklists: Phase-by-phase verification — were all required steps completed, the right tools used, the prescribed sequence followed?
• Review protocols: When and how senior practitioners or the central team audit delivered work.

Gerber frames the ultimate quality question this way: can ordinary people produce extraordinary results, predictably, consistently, and at scale? Read that as a design principle, not a slight against your team. A well-designed system compresses the gap between performers — the practitioner who is a 7 out of 10 should land remarkably close to the one who is a 9 out of 10, because both are carried through the same rigorous process.

A methodology that only works in the hands of geniuses is not a methodology. It is a personality with paperwork. If competent, well-trained people following your documents get great results, you have something that scales.

Section Six — Pricing Rules That Survive a Discount Request

Floors, Tiers, and the Protocol Before Any Price Drops

Pricing is where undocumented businesses bleed value fastest, because pricing decisions get made under pressure, in front of prospects, by whoever happens to be in the room. Leave the rules unwritten and three things happen in parallel: one practitioner slashes prices to win deals, another quotes high and loses winnable work, and a third hands out the diagnostic for free hoping it leads to "bigger projects." Margins erode, positioning blurs, and the founder only sees the damage after it has compounded.

The pricing chapter of your manual needs four things:

• Fee floors: A hard minimum for every engagement type, with no practitioner discretion below it.
• Tier architecture: How engagements are packaged — always three options, always presented top-down with the highest-value option first.
• Proposal language: How the investment is framed and presented — value delivered, never cost incurred.
• The anti-discount protocol: The mandatory sequence before any reduction is offered, including the three alternatives a practitioner must put on the table before a discount is even discussed.

Notice the shape of that list. It is not "our prices." It is the framework, the presentation, the pushback handling, and the alternatives — a system rather than a suggestion. That distinction is what holds when the founder is not in the room.

Treat pricing as brand strategy, because that is what it is. An unprotocoled discount does more than shave margin; it announces to the market that your methodology is worth less than your marketing says.

Section Seven — Proof: The Metrics Behind a Promise You Can Be Held To

From "Trust Us" to "Here Is the Data"

The final section answers the question every serious buyer eventually asks: how do you know it works? What you measure, when you measure it, and how you turn measurements into demonstrated ROI.

Verne Harnish sets the bar: a brand promise must be measurable. "Great service" promises nothing testable. "Response within 4 hours or we credit your account" does. "We help companies improve" is air. "Clients lift their maturity score by 10 points or more inside 90 days, or we keep supporting them at no extra charge" is a commitment with teeth — and commitments with teeth sell.

"A promise you can measure is a promise a client can hold you to. The willingness to be held to it is, by itself, a differentiator — because most of your competitors will not offer it."

Build the measurement system into the manual:

• Outcome metrics: The specific, quantifiable change the methodology produces — score gains, efficiency improvements, revenue impact, time recovered.
• Leading indicators: Early signals that an engagement is on course — assessment movement at the 30-day mark, client engagement levels, milestone completion.
• Collection protocol: The cadence of measurement — pre-engagement baseline, mid-engagement checkpoint, post-engagement reading, 90-day follow-up.
• ROI presentation: The formula you use, and the comparisons that make the return concrete for a buyer.

There is a compounding payoff here. EOS, SAFe, FranklinCovey — every scaled methodology business you can name — can produce persuasive case studies precisely because they measured outcomes systematically from day one. Skip the measurement and you are forever asking clients to take your word for it.

The Manual Is Never Finished — and That Is the Point

Innovate, Quantify, Orchestrate, Repeat

One caution before you start writing: a documented system is not a frozen system. Gerber's Innovation-Quantification-Orchestration cycle describes the ongoing rhythm — innovate by testing new approaches, quantify by measuring what the tests produce, orchestrate by locking the winners into the standard. The loop never closes. A methodology that stops evolving starts decaying.

But evolution has to run through the centre. Improvements discovered in the field must be captured centrally, validated with data, and rolled out across the whole network. Letting each practitioner keep their own private improvements is how a single brand quietly fragments into a dozen incompatible ones.

Run the audit honestly. Client selection criteria. The end-to-end engagement map. The diagnostic instrument. The delivery playbook. The quality bar. The pricing rules. The proof. Seven sections, none of them optional — each missing one is a specific failure mode waiting for the moment you scale.

The firms that wrote all seven down before expanding — EOS, SAFe, FranklinCovey, StoryBrand — turned methodologies into industries. The ones that expanded first and documented never became the stories the rest of us learn from. Your manual does not need to be perfect on day one. It needs to exist.