$1M → $10M

This document has two halves.

The free half is Chapters 0 and 1. It scores whether your business is ready to be systematized at all. Then it replaces your gut feeling about how much of the company is you with two numbers, taken from invoices and task logs. Two instruments, and both produce something written inside a fortnight. If you read only this far, you will still leave knowing your founder-dependence index and which recurring task to write down first. Most founders at this stage have neither, and run the whole year on a hunch.

The paid half is Chapters 2 through 12 plus the template pack. That is the machine. How to rebuild a calendar around the work only you can do. How to write standards someone else can act on, and how to teach judgment by example instead of by adjective. How to review without becoming the queue, and how to automate before you hire. How to price against the client's problem instead of your own cost, and how to move upmarket one honest step at a time. And how to know, from evidence rather than mood, that you are ready for Playbook III.

The decision in this chapter: are you actually ready to systematize, or would this book hurt you?

The thesis, in one page

Belief is what got you here. Somebody believed you could solve their problem, you solved it, and they told someone else. Repeat that forty or fifty times and you have a million in revenue. You also have a founder who cannot take a two-week holiday without the pipeline going quiet.

Confidence is a different thing. Confidence is what a market feels when the promise gets kept whether or not you are in the room. It is made by exactly one process: promise→deliver→promise→deliver, run often enough that the pattern becomes predictable to everyone watching, including you.

That is the whole book. Everything that follows is machinery for running that loop without you as the load-bearing wall.

The PEM Trust Formula says trust multiplies out: Demonstrated Impact × Transparent Presence × Consistent Alignment. At a million in revenue, most founders have decent Impact and decent Presence. What breaks between $1M and $10M is Consistent Alignment, the gap between what was sold and what got delivered. It breaks because the person who used to guarantee that alignment in person is now split across nine deals and cannot be everywhere. The gap opens quietly. Nobody sends an email saying "your integrity trust dropped 30%." Churn rises, referrals thin out, and the founder decides the market got harder.

The market did not get harder. The founder became a bottleneck and mistook the symptom for the weather.

How the chapters work

One decision, one tool, one 90-day move per chapter. No theory without an instrument attached. Any single chapter should read in fifteen minutes and change something in your business the same week.

Each chapter closes with four fixed sections.

• Diagnostic

  Where you actually are, scored or counted, never estimated.

• The 90-day move

  What to run, in what order, with a test for when you are done.

• Bias watchlist

  The specific mental trap that wrecks this chapter's work, and how to block it.

• Annotated example

  One real situation shown three ways, unacceptable, adequate and excellent, with the reasoning that separates them. This is PEM Layer-2 format, and the book practises what it asks of you.

Cases are composites, drawn from businesses I have worked inside or advised, with numbers adjusted and details changed. Where a number is exact, I say so. Where it is there to illustrate, I say that too. The credibility equation applies to the author as much as to you: no claim more than one step beyond the track record.

Read this before the diagnostic

This book will hurt a business that is not ready for it. Standards, review pipelines and partner pay structures are all overhead. Below a certain size and repeatability, that overhead eats the founder's remaining capacity and produces a beautifully documented company with no customers. If you are not at roughly $1M with delivery you can repeat, go back to Playbook I. Nothing here is wasted. It is just early, and early is expensive.

The entry diagnostic

Twenty questions, three sections. Score each 0 (no, never), 1 (partly, sometimes), 2 (yes, consistently). Maximum 40.

Section A — Founder dependence (0–14)

Section B — Standards coverage (0–12)

Section C — Six-domain resource check (0–14)

Scoring

• 32–40 — Ready, and probably late

  You are past the entry gate. What limits you now is execution speed, not readiness. Start at Chapter 3, run the standards work, and come back for Chapters 1 and 2 as a calendar audit.

• 22–31 — The intended reader

  You have belief, you have repeatability, and you have a founder bottleneck you can feel. Run the book in order. Expect Chapters 1 and 6 to be the uncomfortable ones.

• 14–21 — Fragile

  Something is holding, but it is you holding it. Do Chapters 1, 2 and 3 only, for a full quarter, before you touch pricing or hiring. Adding people to an undocumented business multiplies chaos rather than capacity.

• Below 14 — Not yet

  Revisit Playbook I. You want a repeatable channel, three client archetypes, and near-zero gap between promised and delivered over your last ten deals. Systematizing an unproven business locks in the wrong thing for good.

Write your score and today's date somewhere you will find it again. In Chapter 12 you take the same twenty questions a second time, and the change between the two is the only proof that any of this worked.

Tool 0 — the entry diagnostic scoresheet: twenty questions, three sections, scored 0 to 40. Blank version in the template pack.

The decision in this chapter: how much of this business is actually you, counted rather than felt?

There is a sentence I hear in almost every first conversation with a founder at this stage. It always arrives with a slight, tired pride: "Honestly, at this level of complexity, only I can really do this part."

I said it too. For about four years.

It is worth being exact about what that sentence reports. It describes your documentation, not your ability. You are telling me you have never written down what you know well enough for anyone else to act on it, and you are saying it in a tone that sounds like a credential.

PEM puts it bluntly: real mastery can be handed over, and if you cannot hand it over, you may not hold it in the form you think you do. That is the uncomfortable frame for this chapter. The comfortable frame is that a quarter fixes it, and the first step is arithmetic.

The 30-day disappearance test

Take last quarter's revenue and split it into two columns. Column one: revenue that would still have been delivered on schedule if you had been unreachable for thirty days straight. Column two: revenue that would have slipped, gone soft, or died.

Use actual invoices. Not categories, not estimates. Invoices, one line each, with the client name and the amount. Estimating hands you a flattering number every time, which is the tax you pay for rating yourself.

The percentage in column two is your founder-dependence index.

Above 60% is normal at $1M and fatal at $10M. The reason is simple and unforgiving: you cannot buy more of yourself. Temporal resources are the one domain in the PEM stack you cannot build up, only spend. Every growth plan that assumes more founder hours is a plan to hit a wall on a specific date, and you can usually work out that date.

One founder I worked with ran this and got 84%. He had eleven clients. Nine of them had at some point been told "just call me directly if anything comes up." He had built every one of those dependencies himself, then read them back as proof that he was needed.

Sorting the work: understanding-dependent versus execution-dependent

PEM splits execution into two kinds. Understanding-dependent work draws on your own accumulated judgment and loses its value the moment you hand it over: diagnosis, key decisions, the conversation where a client's real problem surfaces underneath the one they described. Execution-dependent work needs skill and effort but not your particular judgment. It needs someone who knows what good looks like.

Almost every founder at this stage puts far too much in the first pile. Functional fixedness locks you into the setup where you do everything, because that setup worked at $200k and nobody sent a memo when it stopped working.

So sort your real tasks, not your imagined ones.

The Task Autopsy. Pull your last 100 finished tasks from wherever they live: calendar, project tool, sent mail, invoicing. Not a sample you pick from memory. The last 100 in order, because memory hands you the dramatic ones.

Put each into one of two columns. The test for column one is not "did this need skill?" It is: would the result have been noticeably worse if a competent person had done this from a written standard I wrote?

Three rules for scoring honestly:

If the task needed a decision you could not explain afterwards, it is understanding-dependent. If you could explain it in under five minutes, it is execution-dependent, and that explanation is the start of a standard.

If you did it because you are faster, it is execution-dependent. Faster is not the same as irreplaceable.

If you did it because the client expects you by name, mark it understanding-dependent for now and put a star on it. Those stars are a Presence problem you will solve in Chapter 8, not a delivery problem.

Typical result at $1M: somewhere between 60 and 75 of the 100 tasks land in the execution-dependent column. The gap between that number and how the founder feels about their week is the whole subject of this book.

Why "only I can do this" survives contact with evidence

Three distortions keep the sentence alive after the arithmetic has killed it.

The illusion of indispensability feeds itself by design. You never let anyone try, so nobody builds the skill, so the record shows nobody else has ever done it well. That proves nothing about you. It only proves the loop is closed.

The IKEA effect inflates the value of anything you built with your own hands. Your onboarding process feels better than a documented one because you assembled it. Measure it against an outside benchmark and the feeling usually does not survive.

The inverted planning fallacy is the least discussed and the most expensive. When founders guess what delegation will cost in time, correction and rework, they overshoot by three to ten times. The same brain that is wildly optimistic about a client project turns gloomy the moment the project is "teach someone else." You will guess that writing down your proposal process takes two weeks. It takes about six hours across three sittings. I have watched that gap play out often enough to state it flatly.

What changes if you accept this

You stop being the person who does the work and become the person who defines what the work is. That is a real loss. The satisfaction of finishing something with your own hands is real, and nothing in Part II hands it back. What you get instead is eight projects at the quality of your best one, rather than one project at the quality of your best hour.

Diagnostic

Complete before moving to Chapter 2:

• Founder-dependence index, calculated from invoices: ____%
• Task Autopsy on the last 100 tasks: ____ understanding-dependent, ____ execution-dependent
• Number of clients who have been told to contact you personally: ____
• Of your execution-dependent tasks, how many already have a written standard: ____

If the fourth number is under 10, Chapter 3 is your next real move, whatever looks more urgent.

The 90-day move

1. Days 1–7

   run the disappearance test and the Task Autopsy, in two sittings, and do not hand the diagnosis itself to anyone.

2. Days 8–30

   take the three most frequent tasks in your execution-dependent column and time-log them for three weeks, because the pricing and hiring decisions later in this book fall apart on guessed numbers.

3. Days 31–60

   pick the single task with the most hours per month that you also dread, and write down how you do it while you do it. Not a polished document. A transcript of your own reasoning, dictated if that is faster.

4. Days 61–90

   hand that task to one person, with the transcript, and accept that the first three attempts will be worse than yours. Time your corrections each round. If correction time is not falling by round three, the transcript is the problem, not the person.

Completion test: one recurring task has left your plate for good, and the founder-dependence index has dropped by at least five points.

Bias watchlist

• Illusion of indispensability

  Ask the closed-loop question: has anyone else ever had a real shot at this, with written guidance and three attempts? If no, you have no data.

• IKEA effect

  Measure one of your processes against an outside one this quarter. Buy a competitor's product. Read a peer's proposal.

• Inverted planning fallacy

  Before you delegate, write down what you think it will cost. Afterwards, write down what it did cost. Keep the log, because two rounds of this fixes most people's estimates for good.

• Self-serving bias in the audit

  Use invoices and task logs. Never memory.

Annotated example: the Task Autopsy

Composite: a 9-person B2B analytics consultancy, $1.4M revenue.

• Unacceptable

  The founder sorts from memory over one evening and gets 78 understanding-dependent, 22 execution-dependent. Every client call is marked understanding-dependent because "each client is different." No hours attached. Why it fails: the input is memory, the categories get defended instead of tested, and the answer was settled before the exercise started. This is confirmation bias wearing a worksheet.

• Adequate

  The founder exports 100 tasks from the project tool and sorts them properly: 41 understanding-dependent, 59 execution-dependent. No time data, so there is no way to know which of the 59 matter. The list gets filed. Why it is only adequate: the diagnosis is honest and nothing is ranked. A correct list with no hours attached produces no decision, and a diagnosis that produces no decision was a way of feeling productive.

• Excellent

  Same export, same sort, 38 against 62, plus three weeks of time logging on the top five recurring execution-dependent tasks. Result: monthly report assembly at 22 hours, proposal formatting at 14, onboarding calls at 11, invoice chasing at 6, scheduling at 5. The founder writes a reasoning transcript for report assembly, the 22-hour item, and hands it to the senior analyst. Round one takes 4 hours of correction, round two 90 minutes, round three 20. By day 90, 22 hours a month are gone, and the transcript has become the first entry in the standards library. Why it works: the sort rests on evidence, hours set the priority instead of irritation, and the handover produced an asset you can reuse rather than a one-time favour.

Tool 1 — the Task Autopsy worksheet: 100 tasks, two columns, hours per month. Blank version in the template pack.