Chapter 3: Designing a sales pipeline that reflects reality
Part of the Small B2B CRM Setup Handbook.
This chapter focuses on turning your pipeline into a reliable map of how customers actually buy, not how sales teams wish they did.
← Back to the handbook overview
Your pipeline is not a to do list
Your sales pipeline is not a wish list of internal activities. It is a map of your customer’s buying journey.
A well designed pipeline allows you to do two critical things. Predict revenue with confidence, and identify exactly where deals are getting stuck.
If your pipeline stages are vague, such as “In Progress” or “Qualified,” you cannot forecast reliably. You also cannot tell whether your team is struggling with discovery, proposal, or decision making.
The most common mistake
The most common mistake is creating pipeline stages based on internal sales activities.
Stages like “Call Made” or “Email Sent” describe what the seller did, not what the buyer decided. The prospect does not care about your internal tasks. They care about their own evaluation and approval process.
When stages are activity based, deals move forward too easily. Forecasts become optimistic guesses, and stalled deals are hidden instead of exposed.
What a good pipeline stage represents
Each stage in your pipeline must represent a significant, verifiable action taken by the prospect that moves them closer to a purchase.
If you cannot clearly answer the question “What did the customer do to earn this stage,” the stage is too weak.
| Stage name (bad) | Stage name (good) | Prospect action or verification |
|---|---|---|
| Qualified | Discovery call completed | Prospect confirmed pain points and a realistic budget range in a meeting. |
| Proposal sent | Proposal under review | Prospect acknowledged receipt and confirmed a date for internal discussion. |
| Negotiation | Contract sent | Legal or procurement received the final contract document. |
How many stages is enough
For most small B2B teams, fewer stages are better.
A simple pipeline with five clearly defined stages will outperform a ten stage pipeline with arbitrary transitions.
As a guideline, aim for:
- 4 to 6 stages total
- Clear exit criteria for every stage
- A probability that reflects historical reality, not optimism
HubSpot guidance
HubSpot’s Deal Pipelines are designed to support this exact approach.
- Stage probabilities: Use realistic probabilities such as 20%, 50%, 75%, 90%, and 100%. A simple model beats a complex one every time.
- Forecast categories: Use forecast categories consistently so leadership can separate early pipeline from near term revenue.
- Stage requirements: Require critical fields before a deal can move forward. This is one of the strongest tools for enforcing discipline without micromanagement.
For example, before a deal can move to “Proposal under review,” you might require:
- Budget confirmed
- Decision maker identified
- Next step date set
This prevents sellers from advancing deals prematurely and protects the integrity of your forecast.
Actionable setup
Review your last ten closed won deals.
Identify the four to six non negotiable milestones the customer reached before buying. Those milestones, not your internal tasks, should define your pipeline stages.
Continue reading the handbook:
← Previous: Chapter 2 – Defining leads, contacts, and companies correctly
Next: Chapter 4 – Required fields, properties, and data discipline →