The Franchise Test: Would Your Methodology Survive Without You in the Room?

Try this question on yourself before reading further: if you became unreachable for six weeks starting tomorrow, would your clients still receive your full quality of work?

For most consultancies, agencies, and coaching firms, the honest answer is no. Michael Gerber gave that condition both a diagnosis and a cure. The diagnosis: you don't own a business — you're self-employed inside something that looks like one. The cure: the Franchise Prototype. Run your firm as though you intended to replicate it, even though you almost certainly never will.

Ray Kroc understood this better than anyone. His real product was never the hamburger. It was a replication engine — a documented operating system through which ordinary employees, following extraordinary procedures, turned out an identical product at every location. Your version of that engine is a documented methodology that trained practitioners can deliver to the standard you set, whether the client sits in London, Dubai, Sao Paulo, or New York.

None of this means drowning your firm in bureaucracy. The goal is predictability: the same diagnostic depth, the same analytical rigor, the same clarity of recommendation — regardless of which practitioner shows up. Excellence lives in the system, not in any individual's talent.

This issue walks through the franchise discipline in the order you should apply it: the test your methodology must pass, the mindset that produces real systems instead of notes, the seven assets every transferable methodology needs, the fastest way to capture them, the loop that keeps them improving, and the evidence that this path works.

---

01 — The Test Comes First

Ordinary Practitioners, Extraordinary Outcomes

Before any documentation effort, you need to know what standard you're building toward. Gerber supplies it in the form of a question worth revisiting every quarter:

"Can ordinary people produce extraordinary results, predictably, consistently, and at scale?"

Read that as a design constraint, not a slight against the people you'll eventually hire. A well-built system absorbs individual variation: the practitioner who rates a 7 out of 10 on raw talent should land results close to those of the 9 out of 10 — because both are carried through the same rigorous process.

A methodology that only works in the hands of brilliant people isn't a methodology. It's a personality with paperwork. Scalability begins the day competent, well-trained practitioners can deliver good outcomes by following what you wrote down.

Know the failure mode before you start. Gerber names it "management by abdication": pushing delivery onto practitioners without systems behind them, then hoping they work it out. Delegation hands over responsibility together with systems and accountability. Abdication hands over responsibility alone. What follows abdication is always the same sequence — uneven delivery, slipping quality, and the founder dragged back into the exact client work they were trying to exit.

So the test comes first. Everything in the rest of this issue exists to help your methodology pass it.

---

02 — Think Prototype, Not Practice

The 5,000 Rule and Why It Works Even at One Location

Gerber's most provocative instruction: treat the business you own today as the prototype for 5,000 more exactly like it.

You will probably never open 5,000 offices or certify 5,000 practitioners. That isn't the point. The point is what the assumption does to your documentation standard.

Write a process down so that you can remember it, and you produce notes. Write it down so that a stranger on another continent could follow it and get your results, and you produce a system. Same activity, completely different artifact.

That gap — notes versus systems — is also a valuation gap. A firm that cannot function without its founder typically sells for 1-2x annual revenue. A firm built on documented, transferable systems sells for 8-15x. The franchise mindset is how you cross from the first category into the second.

Notice how the framing changes what gets written:

• "How I run a workshop" becomes a complete run-sheet anyone can execute — scripts, timing, materials, and what to do when things go sideways
• "How I deal with a hard client" becomes a catalogue of the five most frequent objections, the response that works for each, and where to escalate when it doesn't
• "My pricing" becomes a pricing framework: how it's presented, how pushback gets handled, and which three alternatives must be offered before any discount is even discussed

"The prototype exercise has nothing to do with actually franchising. It replaces the founder's memory, instincts, and heroics with systems any competent person can run — which is the entire difference between owning a business and being one."

Hold yourself to that six-week absence question from the opening. If the answer is still no, you have a job with letterhead. The prototype discipline is how you turn it into an asset.

---

03 — The Seven Assets of a Transferable Methodology

What Your Operations Manual Must Actually Contain

An Operations Manual doesn't need to cover every edge case. It needs to cover seven core areas well — together they handle roughly 80% of what a new practitioner needs in order to deliver to standard.

1. Client selection criteria.

Start here, because everything downstream depends on it. Define the industries, company sizes, and problem types where your methodology shines — and the red flags that signal a bad fit. Mike Michalowicz's Pumpkin Plan calls the ideal ones your "top pumpkins": the clients who create the most value with the least friction.

2. Methodology steps.

Every phase from first contact to final deliverable: what happens in each, the inputs and outputs, and which decisions belong to whom.

3. The diagnostic tool.

Assessment questions, scoring rules, interpretation guidance, report format — specified completely enough that two trained practitioners on different continents produce the same diagnostic output.

4. The delivery process.

Engagement structure: how many sessions, what each one covers, which materials are used, and what the client walks away with at every stage.

5. Pricing rules.

Fee floors, tier structure, proposal format — always three options, presented top-down — and the protocol a practitioner must exhaust before any price reduction is allowed.

6. Quality standards.

A concrete definition of "good": minimum satisfaction scores, formatting requirements for reports, adherence checklists. These are the criteria you'll use to judge whether a practitioner's delivery meets the bar.

7. Success metrics.

How you prove the methodology worked: the data you collect, how ROI is demonstrated, and the brand promise you make — plus how you verify you kept it.

On that last asset, Verne Harnish adds a requirement most service firms ignore: a brand promise only counts if it can be measured.

"A promise like 'great service' commits you to nothing. 'If we don't respond within 4 hours, we credit your account' commits you to something verifiable. The same logic applies to outcomes: 'we help companies improve' can never be checked — 'your maturity score rises by at least 10 points within 90 days, or we keep supporting you at no charge' can be. That's the difference between a slogan and a promise."

A measurable promise builds trust, creates internal accountability, and separates you from every competitor hiding behind vague language. You don't need all seven assets documented this month. You need one of them documented this week — and the right one to start with is whichever currently exists only inside your head.

---

04 — Capture Beats Perfection

How to Document Fast Without Writing a Doorstop

Knowing what to document is the easy half. Most founders stall on the how — usually because they imagine documentation as a months-long writing project. It isn't. Two techniques get you there quickly.

The first is Gino Wickman's 3-Step Process Documenter:

Identify.

Name your 6-10 core processes — the major repeatable activities that, performed consistently well, produce what clients pay you for. Resist the urge to list twenty or fifty. Six to ten.

Document.

Apply the 20/80 rule to each: capture the 20% of steps responsible for 80% of the results, in 1-5 pages per process. Nobody reads a 200-page manual. People do read a tight process guide they can follow on day one.

Package.

Bundle the guides as "Your Way" — a branded Operations Manual that functions as the single authoritative answer to how work gets done in your firm, not a reference document gathering dust.

The second technique solves the blank-page problem entirely. Mike Michalowicz calls it Live Capture: instead of writing about the work, record yourself doing it, narrate your decisions out loud, and give the recording to the person taking it over.

In practice:

• During your next client engagement, hit record and think aloud: "the client said X, that tells me Y, so I'm switching to approach Z"
• During your next sales call, record and annotate the turning points — where budget resistance appeared, which reframe you reached for
• While building your next deliverable, screen-record the whole thing: how you read the assessment data, structure the recommendations, format the output
• Then hand each recording to your trainee, have them attempt the process alone, and debrief their attempt together

"A 70% complete process document that exists beats a 100% perfect one that lives in your head — by an infinite margin. Ship the rough version, refine it through use, and by the third pass it will be excellent."

Waiting for the polished version is procrastination wearing the costume of diligence. Version one of anything you document will contain gaps and unstated assumptions. Capture it anyway. You can refine what exists; you cannot refine what doesn't.

---

05 — The Loop That Keeps the System Alive

Innovation, Quantification, Orchestration — on a Calendar

Here is the trap waiting on the other side of documentation: a methodology that stops changing starts dying. Markets move, client expectations rise, competitors copy. The system that led its category two years ago can be merely average today.

Gerber's answer is the Business Development Process — a permanent three-beat cycle:

Innovation.

Run small experiments against the existing baseline: a new assessment question, a different way of presenting results, an adjusted delivery format. Innovation here means testing improvements, never reinventing the methodology wholesale.

Quantification.

Put numbers on every experiment. Did satisfaction rise? Did close rates move? Did delivery get faster? An innovation that merely felt better is guesswork; only measured outcomes earn a place in the system.

Orchestration.

Standardize what the numbers validate: update the Operations Manual, retrain practitioners, make the improvement the new default. This step is where most firms break down — endless experimentation, zero formalization. The cost is inconsistency: half the team delivers the new way, half the old way, and the client experience depends on the luck of the draw.

Give the loop a fixed cadence rather than running it on inspiration:

• Weekly: practitioners surface delivery insights — what landed, what failed, what surprised them
• Monthly: the strongest insights get reviewed and trialled at small scale
• Quarterly: validated improvements are locked into the methodology and announced to every practitioner
• Annually: a full methodology review refreshes the manual, retrains the network, and publishes updated benchmarks

The non-negotiable: improvements flow to the center, get validated with data, and roll out everywhere. Local experiments that never get standardized don't improve the brand — they fragment it.

---

06 — Founders Who Were Replaced by Their Own Systems

The Evidence That the Prototype Path Works

If the franchise discipline sounds theoretical, look at the expertise businesses that already ran the play:

• EOS (Entrepreneurial Operating System): Gino Wickman compressed his coaching practice into six components with named tools — documented so thoroughly that certified implementers have carried it into over 200,000 companies. The system made Wickman's personal involvement optional.
• SAFe (Scaled Agile Framework): Dean Leffingwell turned enterprise agile into a framework of named practices, defined roles, and measurable outcomes — with over 18,000 certified practitioners around the world today.
• FranklinCovey: Stephen Covey's 7 Habits grew into a methodology business worth hundreds of millions, because the habits were packaged as workshops, assessments, and certifications that any trained facilitator could run.
• Alan Weiss's licensing model: Weiss licenses his Million Dollar Consulting IP at $490,000-$575,000 per franchise territory — a price that functions as a quality filter, not a barrier.

Strip away the surface differences and one pattern remains: deep personal expertise, codified into a named, documented, testable system, delivered consistently by trained practitioners. And not one of these founders started with a finished system. Each delivered personally first, noticed what repeated, wrote it down, tested it on a small group, and iterated until the system produced reliable results without them in the room.

That sequence — deliver, notice, document, test, iterate — is available to you starting this week. It demands no genius and no luck. It demands documentation discipline.

---

07 — Before Friday

One Imperfect Capture Is Worth More Than a Perfect Plan

If the scope of all this feels heavy, trust that feeling — building a franchise prototype is genuinely substantial work. But the response to overwhelm isn't more planning. It's one imperfect action on the single highest-leverage process you own.

This week's assignment, in four moves:

• Choose one process. Take the engagement you deliver most often — the one you know cold. That familiarity is your advantage: every step already lives in your head; it simply hasn't reached paper.
• Record a full run. Loom, Zoom, or a phone propped on the desk. Narrate every decision as you make it. No editing, no polish — capture only.
• Hand it to a human. A colleague, a virtual assistant, a junior hire. Have them attempt the process armed with nothing but your recording. Every place they stall marks a gap in your documentation.
• Write version 1.0. Not a manual — a named, 2-3 page guide covering the 20% of steps that drive 80% of results. Drop it in a shared folder. Congratulations: your Operations Manual now has its first page.

Repeat with a second process next week, a third the week after. Two months in, your core methodology is on paper. Six months in, you have a working Operations Manual. A year in, you have a business that runs in someone else's hands.

"You will never build 5,000 locations — and you don't need to. You need one system capable of powering 5,000. Designing to that standard is what makes your single location dramatically more valuable."

That is the real payoff of the Franchise Prototype: not a franchise, but freedom — a business that works without you, so you can finally work on it instead of in it.

---