How to Document a Founder's Sales Process

Ask a founder who is selling well to describe their sales process and most will say something honest and unhelpful: it depends on the customer. That is true, and it is also the reason nobody else in the business can sell the way they do. The knowledge is real; it just has not been written down anywhere a second person could use it.

Documenting a founder's sales process is not the same exercise as drawing a generic funnel from a textbook. A generic funnel describes how selling is supposed to work in theory. What needs capturing is how this founder, selling this product, to these buyers, actually gets deals done — including the parts that feel like instinct.

This matters before a first salesperson is hired, not after. A new hire without a documented process is being asked to reverse-engineer the founder's judgement from a handful of shadowed calls, which is slow, inconsistent, and expensive in lost deals while they work it out.

Why undocumented selling cannot be delegated

A founder's sales ability is usually a mixture of product knowledge, credibility, pattern recognition from dozens of past conversations, and small judgement calls made in real time — when to push on price, when to bring in a case study, when to go quiet and let the buyer talk. None of that is visible from outside the room unless someone deliberately extracts it.

The common failure mode is to hire a salesperson and hand them a CRM with three stages and a product deck, and expect them to sell the way the founder does. They cannot, because the founder's process was never separated from the founder. Documentation is what makes the process portable.

Capture what actually happens, not the idealised version

The starting point is observation, not invention. Sit down after a batch of real deals — won, lost and stalled — and reconstruct what happened at each one: how the conversation opened, what was asked, what objections came up, what changed the buyer's mind, what the founder said when the price was queried. This is slower than writing a theoretical process in an afternoon, but it is the only version that is true.

• Review the last 15–20 deals, including losses, not just the wins.
• Note the actual first meeting structure used, not the one intended.
• Record objections verbatim, in the buyer's own words, and what response worked.
• Identify the moments where the founder made an unwritten judgement call.
• Separate what happened because the buyer trusted the founder personally from what would work for anyone.

Define stages and exit criteria

A stage is not a label for how a deal feels; it is a claim about what is known and what has been agreed. Exit criteria force that discipline — a deal cannot move to the next stage until specific, checkable conditions are met. This is what stops a pipeline from being a list of hopeful adjectives.

Qualification: what counts, and what does not

Founders often qualify unconsciously, filtering out weak opportunities through instinct built from experience. That instinct needs converting into a short, explicit standard — the handful of things that have to be true before time is invested in a deal. Without it, a new hire either pursues everything or filters using different, worse criteria.

Discovery questions that actually work

Generic discovery questions produce generic answers. The questions worth documenting are the ones that, in practice, get buyers to say something specific and revealing — a number, a deadline, a name, a frustration. If a question reliably produces a vague answer, it should be dropped rather than kept because it sounds thorough.

Objection handling in the buyer's own language

Objections should be documented as they were actually said, not paraphrased into something tidier. 'We tried something similar before and it didn't stick' is a different objection to 'we're worried about change management', even though a summary might collapse them into the same line. The founder's response — the one that actually worked, in their own words — should sit directly underneath it.

Proposal and pricing rules

Pricing that lives only in the founder's head tends to drift deal by deal, defensibly at the time but inconsistently in aggregate. Documenting it means writing down the standard price, the legitimate reasons to flex it, the limits of that flex, and what is never negotiated. The same applies to what a proposal must contain and in what order, since the structure of a proposal is often doing more selling work than founders realise.

What 'good' looks like at each stage

Beyond the mechanical exit criteria, it helps to describe what a strong version of each stage looks like versus a weak one that technically qualifies. A discovery call that ticks the boxes but leaves the buyer's real priority unclear is weak discovery, even if the CRM field is filled in. This qualitative layer is what separates a document that produces judgement from one that only produces compliance.

Keeping the document alive

A sales process document written once and left untouched goes stale within a quarter, because the market, the objections and the offer keep moving. The document needs an owner, a short review interval, and a rule that new objections or lost-deal patterns get added as they occur rather than being reconstructed from memory months later.

1. 01Reconstruct 15–20 real deals, wins and losses, in detail.
2. 02Draft the stage structure and exit criteria from what actually happened.
3. 03Write the qualification standard as a short checklist.
4. 04Document discovery questions that have proven to produce useful answers.
5. 05Capture objections verbatim with the responses that worked.
6. 06Write down pricing and proposal rules, including flex limits.
7. 07Describe what 'good' looks like at each stage, not just the minimum.
8. 08Set a review cadence and an owner for keeping it current.

CRM versus playbook

The CRM should hold what is structured and comparable across deals: stage, exit criteria met, next action, loss reason, deal value. The playbook should hold what needs judgement and language: how to open a call, how to answer a specific objection, when to bring in a case study, what a strong discovery call sounds like. Trying to force the playbook's content into CRM fields usually produces a system nobody reads.

Done properly, this document is what allows a founder to step back from every deal without the business losing what made those deals work. It is also, in practice, the clearest evidence of whether the sales motion is genuinely repeatable or still dependent on the founder personally — which is the question that determines whether hiring makes sense at all.