How to build a sales process from scratch
A sales process is the documented, repeatable set of steps that turn a lead into a customer, with clear criteria for advancing at each stage.
The difference between a process and a wish is enforceability: it must live where reps work and be inspected every week.
- 5-7 Stages in a healthy process
- Exit criteria What every stage needs
- Weekly Inspection cadence
Short answer
Build a sales process from scratch by mapping how your buyers actually decide, defining five to seven stages named for buyer commitments, writing objective exit criteria for each, attaching the plays and required fields per stage, and measuring conversion so you can fix the weakest link. Document it in the CRM, not a slide deck.
Step by step
Map how buyers actually decide
Interview recent won and lost deals and write the real sequence of buyer commitments: took a meeting, admitted a problem, looped in budget, agreed on a proposal, signed. Your stages track these, not your internal tasks.
Define five to seven stages
Fewer hides signal, more creates busywork. A common backbone: New, Qualified, Discovery, Proposal, Negotiation, Closed. Name each for the buyer commitment it represents so the pipeline reflects reality.
Write objective exit criteria
Each stage needs a one-line test a deal must pass to advance. If two reps would disagree on whether a deal qualifies, the criteria are too vague. Example: to leave Qualified, budget owner confirmed, pain stated, next meeting booked.
Attach plays, assets, and required fields
Document the exact play for each stage: which discovery guide, which demo path, which proposal template, and the fields that must be filled. Reps should never reinvent the step.
Add conversion rates and time-in-stage
Pull six to twelve months of history and compute the pass-through rate and average days for each stage. These turn your process into a forecast and expose your worst leak.
Measure the weakest link and iterate
Find the lowest-converting stage transition, fix that one thing, remeasure, and repeat. Gains at the constraint beat effort spread everywhere.
Common mistakes
Activity-based stages like "demo scheduled" that describe seller effort instead of buyer intent. They inflate the pipeline and wreck forecast accuracy.
Building the process in a document no one opens. If it does not live in the CRM, it will not be followed.
How Ardovo runs this
Ardovo turns this from a slide no one opens into how the work actually happens. The stages, exit criteria, and plays live in the deal object, and Rook flags any deal that skips a step, drafts the next artifact, and keeps the data honest, so the whole process is enforced in the deal object gets followed instead of forgotten.
Frequently asked questions
What is the difference between a sales process and a methodology?
A process is the ordered steps and criteria a deal moves through (what to do and when). A methodology like MEDDIC or Challenger is how you sell within those steps. You need both: the process gives structure, the methodology gives technique.
How many stages should a sales process have?
Five to seven for most B2B teams. Fewer hides where deals stall; more forces reps to guess which stage a deal is in and creates data-entry busywork. Name each stage for the buyer commitment it represents, not the seller's activity.
How do I know my process is working?
Track conversion between each stage and the time deals spend in each. A working process shows steady pass-through and predictable velocity, and its forecast ties out to actuals. When one transition leaks badly, that is your constraint to fix first.
Where should the sales process live?
In your CRM, as stages, exit criteria, required fields, and per-stage guidance, not in a static document. A process reps have to leave their workflow to consult gets ignored. In Ardovo, the stages and criteria are enforced in the deal object itself.