Documenting the sales process you already have

You do not need to design a sales process; you already run one. Documentation is extraction, not invention: trace how your last few deals actually moved from first conversation to signed agreement, write down the stages and the triggers between them, and you have a document that a hire, a CRM, or an automation can run without you. The firms that skip this step do not lack a process — they lack access to it, because it lives in one person's head.

Why document a process that works fine in your head?

Because "in your head" is the most expensive storage location in the business. While the process lives there, every deal needs you: you decide when to chase, what to send, when a lead is dead, what a proposal says. That is the core mechanism of owner-dependence described in The Founder-as-Bottleneck Report — the business sells only when the founder sells, so revenue is capped at the founder's calendar.

There is also a measurement cost. An undocumented process has no stages, so it has no conversion rates, so you cannot see where deals die. When a quarter disappoints, you get opinions instead of diagnosis. Documentation is what turns "sales feels slow" into "we lose 60% of deals between proposal and decision, so that is the stage to fix" — hedged numbers, but numbers.

What should the document actually contain?

One page, five elements. Resist the urge to write a manual.

• Stages — the five to seven states a deal passes through, named by what has happened, not by mood: enquiry received, call booked, call held, proposal sent, verbal yes, signed.
• Entry and exit criteria — what must be true for a deal to enter and leave each stage. "Proposal sent" means the document is in their inbox, not "I'm working on it".
• Triggers and actions — the when-X-then-Y rules between stages. When a proposal goes out, then follow-up touches are scheduled for days three, seven, and fourteen. When a call is held, then notes are in the CRM the same day.
• Owner per step — a name, even if every name is currently yours. That column is your future delegation plan.
• Numbers — the conversion rate you expect between each stage, even as a rough first guess. Guesses get corrected; blanks stay blank.

What is the fastest way to extract it?

Work from evidence, not memory. The mechanism:

1. Pull your last five closed deals — won and lost — from wherever the traces live: inbox, calendar, proposals folder.
2. Reconstruct each timeline. For every deal, list each touch in order: date, channel, who initiated, what happened next.
3. Lay the timelines side by side. The common spine is your actual process. The variations are either judgement calls worth keeping or inconsistencies worth killing.
4. Convert the spine into rules. Each recurring step becomes a trigger-action pair. When a lead replies with interest, then a call link goes out within one working day. When a deal sits silent for fourteen days, then it gets a named reactivation touch, not silence.
5. Test it on the next live deal. Follow the document exactly. Every place you instinctively deviate is either a missing rule or a wrong one — update the page, not just your behaviour.

Half a day of reconstruction beats six months of intending to write documentation.

What do you do with it once it is written?

Put it to work in three directions. First, install the stages in your CRM so the process runs on triggers rather than memory. Second, run each step through the triage in Delegate, automate, or delete: the triage — most follow-up and admin steps automate cleanly, and the judgement steps become a genuine job description. Third, hand the mechanical upstream work to software entirely; list building and enrichment are already at the point where an agent can execute a documented process end to end, as shown in the build log of an AI agent that builds and enriches a B2B database. A documented process is the prerequisite for all three — you cannot automate, delegate, or delete what you have not defined.

How do you keep it from going stale?

Review it on a fixed trigger, not "when things calm down". When a deal deviates from the documented path and wins anyway, then the document gets updated within the week — the deviation was information. A stale process document quietly returns the business to head-storage, and the gains evaporate. Firms that keep this discipline can grow the revenue side without growing the payroll side, which is the whole argument of Growing revenue without growing headcount.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.