Before you hire your first AE or BDR — the people who close and qualify deals — four things need to be written down: who the deal is really for and what they measure, how a deal moves, which conversations have worked, and the criteria a buyer uses to say yes. Without them, you won't know why deals stall.
Word count: 55
The buyer profile that reflects what you've actually learned
This is not a marketing persona. It is a working description of the specific person inside the buyer's company who will feel the pain your product addresses, the person who will sign the contract (often a CFO or VP of Finance who never saw the demo), and the person who will block or approve it on security or procurement grounds. For each, write down what they are measured on, what a win looks like in their own terms, and what concern they will raise that is not an objection to overcome but a requirement to design for. If you can't write this from memory, you don't yet have enough signal to hand the motion to someone else.
The deal stages you have actually run, not the ones you aspire to
A deal stage is a moment when something real changes in the buyer's commitment, not a task you completed. Write down the stages your closed deals moved through, in sequence, and for each one: what the buyer did or said that told you the deal had moved, and what you did to help them get there. This is your process map. A new hire can follow a process map. They cannot follow a founder's intuition.
The conversations and materials that moved deals forward
Write down the questions you asked in discovery (the early conversations where you learn what the buyer needs before proposing anything) that surfaced the real problem. Write down how you introduced the pilot — the limited, time-boxed test a buyer runs before committing to a full contract — including what success criteria you agreed on and who agreed to them. Collect the emails, one-pagers, and security questionnaire responses that worked. A new hire needs raw material, not advice to be creative.
The criteria the buyer used to decide
For every deal you closed, write down what the buyer said they would measure during the pilot and what they actually measured. For every deal you lost or that stalled, write down the last thing the buyer said before they went quiet. These two lists are more useful than any sales script. They tell a new hire what the buyer is actually deciding, which is rarely what the demo covers.
The format that makes it usable
One document per topic, short enough to read in a single sitting. Use plain language, not sales jargon. Write the buyer profile as a set of questions a new hire should be able to answer after the first discovery call. Write the deal stages as a checklist with a column for "how you know you're here" and a column for "what moves you forward." Write the conversation guide as a list of actual questions, not topics. Attach the real materials — the emails, the one-pagers — rather than describing them. The test: could a new hire run a deal from this documentation without calling you? If not, find the gap and fill it.
What this means for your deals
The concrete moves: write the buyer profile this week using your last two or three closed deals as the source. Then write the deal stages from those same deals, not from a sales methodology book. Then pull the emails and materials into a shared folder. The one move to make first: write down, for your most recently closed deal, who signed it, what they said they needed to be true before they would sign, and whether you ever spoke to them directly. That answer will tell you more about your current motion than anything else.
This advice is most useful when you have closed at least one enterprise deal yourself. If you haven't closed one yet, the documentation you write now will be a hypothesis, not a playbook — and a new hire running a hypothesis without you in the room is a risk worth naming before you hire.
Frequently asked questions
How do I know if my documentation is detailed enough for a new hire to use?
Ask someone who wasn't in your deals to read it and tell you what they would do in the first discovery call. If they ask you questions the document should have answered, those gaps are what you need to fill before you hire.
What's the difference between a sales playbook and a process document?
A process document describes the steps. A playbook includes the reasoning: why each step exists, what the buyer is deciding at that moment, and what a good outcome looks like from the buyer's side. A new hire can follow a process document; they can run a motion from a playbook.
Should I document what didn't work, or only what did?
Document both. The deals that stalled or lost, and the last thing the buyer said before they went quiet, are often more instructive than the wins. They tell a new hire where the motion breaks down and what concerns to take seriously rather than talk past.
One next step this week: Take your most recently closed enterprise deal and write down, in plain sentences, who signed it, what they told you they needed to be true before they would sign, and whether you ever had a direct conversation with them. That single record is the foundation everything else builds on.