How to Map a Sales Process
Why map the sales process
A sales process map shows how a buyer moves from first contact to closed won, and what the selling team does at each stage. The exam tests stage design, exit criteria, roles, and the difference between a documented process and a CRM pipeline. Good maps reduce variability, improve forecasting, and make handoffs and coaching concrete.
Core rules and concepts
- Start from the buyer’s journey, then define seller actions and required evidence.
- Each stage needs entry criteria, exit criteria, owner, key activities, and artifacts.
- Use deal stages in the CRM to enforce the process; stage changes should require evidence, not optimism.
- Keep stages meaningful and few enough to adopt; too many stages create admin work.
- Map exceptions: disqualification, no decision, procurement, and handoff to service.
Worked example
A team has stages “New, Demo, Proposal, Closed.” Reps skip from Demo to Proposal without a documented business case, so forecasts are unreliable. Mapping reveals there are no exit criteria for Demo. RevOps adds: pain, impact, decision criteria, and next step documented. Forecast accuracy improves because stage advancement now reflects evidence.
Traps
- Equating a pipeline with a sales process; a pipeline is one artifact.
- Writing stages around internal activities such as “sent email” instead of buyer progress.
- Designing a perfect process that reps cannot follow in the CRM.
Key takeaways
Map the buyer journey first, then the seller’s actions. Exit criteria make stages and forecasts reliable.