Who buys
- Company: what kind of company, what situation they’re in when they buy.
- Buyer: the person who signs, and the person who uses it every day.
- Not a fit: the companies you’ve learned to walk away from.
Why they buy
In the customer’s words, taken from calls. List the problems they describe and the moment that made them look for a fix.
Stages
| Stage | What has happened | Exit point | Next step |
|---|---|---|---|
| Discovery | First real conversation | Problem confirmed and worth solving | Demo or working session booked |
| Evaluation | They’re testing whether it fits | Decision maker involved, criteria known | Proposal |
| Proposal | Terms on the table | Verbal yes, or a clear list of open questions | Contract |
| Closed | Signed or lost | Reason recorded | Handoff or follow-up date |
Rename the stages to match how your deals move. Keep the exit points: they’re what makes the pipeline readable.
Discovery questions
The questions you ask on a first call that tell you whether the deal is real. Write the ones you ask, in the order you ask them.
Objections and answers
| Objection | What’s usually behind it | What you say |
|---|---|---|
What to record
The few things the system must hold for each deal: stage, next step, amount, close date, the decision maker, and a link to the call recordings. Anything a recording or an email can supply should be filled automatically.
Handoff
What the customer was promised, who they’ll work with next, and what happens in their first weeks.
Tools
Where deals live, how calls are recorded, and how the two connect. Keep it to what you use today.
Related: What should you set up before your first sales hire? and When should a founder hire the first salesperson?