Mapping Your B2B Sales Stages Without Over-Engineering
A practical method for defining four to seven pipeline stages that reps will actually use in weekly deal reviews.
The most common mistake in sales stage design is building for the CRM admin instead of the rep on the phone. Here is the approach we use in audit workshops.
Start with won and lost deals
Pick three recent wins and three recent losses. For each, write down the actual sequence of events — first contact, discovery call, site visit, proposal, negotiation, close. Do not look at CRM history yet. Talk to the rep who owned the deal.
Patterns emerge quickly. Most B2B deals pass through similar phases even when the CRM says otherwise.
Name stages after buyer actions, not rep tasks
“Sent proposal” is a rep action. “Evaluating options” is a buyer state. Stages tied to buyer behaviour are easier to verify in deal reviews. Ask the rep: “What is the buyer doing right now?” not “What did you send last week?”
Write one-sentence entry criteria
Each stage needs a single sentence that answers: “What must be true before a deal enters this stage?” If you need a paragraph, the stage is too vague or should be split.
Example: Qualified — “Buyer has confirmed budget range, decision timeline within two quarters, and access to the economic decision-maker.”
Limit yourself to seven stages
More than seven stages and reps start skipping or merging them informally. Fewer than four and you lose visibility into where deals stall. The sweet spot for most B2B teams is five or six.
Test in a live deal review before rolling out
Pick one team’s pipeline for a pilot review using the draft stages. Note where reps hesitate or argue. Those hesitation points reveal stages that need clearer definitions.