Name the progress, not the mood
“Warm,” “working” and “likely” describe how a seller feels. They tell a colleague nothing about what the buyer has done. A useful stage name says something observable: discovery booked, requirements confirmed, proposal sent, decision pending. Pipedrive's own guidance says the same: base stages on each major step a deal goes through, use action-based names such as “Proposal sent” instead of “In progress,” and keep the number of stages low.
Decide when an inquiry becomes a deal. If every downloaded brochure becomes an opportunity, the pipeline looks busy and predicts nothing. A workable rule for a small team: create a deal only when there is a named buyer, a stated problem, a plausible fit and an agreed next conversation. Everything else stays a lead or a contact.
Keep activities out of the stage list. A follow-up call is an action; it does not move the buyer to a new stage. Every open deal needs a next action, a date and an owner, including deals that are waiting on the customer.
| Mood label | Observable stage instead | Evidence on the record |
|---|---|---|
| Warm | Discovery booked | Meeting on the calendar with the buyer |
| Working on it | Requirements confirmed | Scope, budget discussion and decision makers noted |
| Hot / likely | Decision pending | Decision date and participants agreed |
| Stuck | Not a stage | Add a dated next action or close as lost with a reason |
Stage definitions for a small project-based agency
Copy the five stages below as a starting point if you sell projects through a discovery call and a written proposal. A subscription business with a free trial, or a distributor that checks stock before quoting, needs different milestones, but the pattern stays the same: entry evidence, exit rule, next action.
Use the exit rule to stop stage inflation. A proposal does not move to decision pending because the seller wants a stronger forecast. It moves when the buyer has acknowledged the proposal and agreed to a decision step.
| Stage | Entry evidence | Exit rule / next action |
|---|---|---|
| Discovery booked | Buyer has agreed to a meeting | Complete discovery and record need, budget discussion and decision participants |
| Requirements confirmed | The agency can explain the project scope | Prepare a proposal or close the deal as unsuitable |
| Proposal sent | The buyer has received a versioned proposal | Get an acknowledgment and agree on a decision conversation |
| Decision pending | A decision step and participants are known | Record accepted terms or an explicit lost reason |
| Won / lost | An explicit outcome has been recorded | Hand off delivery, or record the reason and any future follow-up |
How many pipeline stages you need
Four to six open stages plus won and lost cover most small B2B sales processes. Fewer than four usually hides the difference between a first meeting and a sent proposal. More than seven usually means tasks have become stages (“Follow-up call 2”) or two different processes share one pipeline.
Test each stage with one question: could a colleague who has never spoken to the buyer verify the entry evidence from the record alone? If not, merge the stage into the one before or after it.
Check how many pipelines your plan allows before you design a second one. Limits vary a lot between CRMs and plans, and on free plans you often get exactly one.
| CRM | Free or entry plan | More pipelines from |
|---|---|---|
| HubSpot | Free tools: one HubSpot-provided pipeline per object, no custom pipelines | Starter 15, Professional 100, Enterprise 350 (total across objects) |
| Pipedrive | Customizable pipelines on every plan, from Lite | No published pipeline count on any plan |
| Zoho CRM | Free plan: default pipeline only | Standard 5, Professional 10, Enterprise 20, Ultimate 50 |
| Freshsales | Multiple pipelines are not included below Pro | Pro 10, Enterprise 25 |
Use fewer fields, but give each one a job
Start with seven fields: owner, value, currency, expected close date, lead source, next action date and loss reason. Add a field only when someone can name the decision or report it feeds. Plan limits are rarely the constraint; discipline is. Pipedrive allows 30 custom fields per company on Lite and 100 on Growth, and HubSpot's free tools allow 10 custom properties.
Make fields required at the stage where the information exists, not on day one. Asking for a close date at discovery produces placeholder dates that ruin the forecast. The table shows a sensible sequence.
Write the allowed values for stage and loss reason. A short controlled list such as “No budget,” “Chose a competitor,” “No decision / went silent,” “Timing: revisit later” and “Not a fit” is easy to report. Add a free-text note only if someone reads it.
Treat probabilities as estimates. Calculate them from your own history: if 12 of the last 40 deals that reached proposal sent were won, that stage's probability is 30%. With fewer than about 30 closed deals, skip the weighted forecast and review the unweighted pipeline instead. In Pipedrive, a probability set on an individual deal overrides the stage probability when both are switched on.
| Field | Required from | Why |
|---|---|---|
| Owner | Deal creation | Every deal needs one person responsible for follow-up |
| Next action date | Every open stage | Drives the daily task list and the weekly review |
| Value and currency | Requirements confirmed | Scope is known, so the number means something |
| Expected close date | Proposal sent | The buyer has a proposal to decide on |
| Decision participants | Decision pending | Shows who must say yes |
| Loss reason | Lost | Feeds the monthly review of why deals are lost |
When a second pipeline earns its place
A separate pipeline makes sense when the milestones are genuinely different. New project sales and renewal negotiations have different stages and often different owners. Two sellers doing the same work do not need two pipelines because each wants a separate view; give them a filter.
Before splitting, check whether a filter, a saved view or an owner field solves the problem. If you do split, define where a deal belongs from the start and how the two pipelines roll up into one report.
Avoid moving deals between pipelines. Pipedrive warns that moving a deal through several pipelines can compromise reporting accuracy in its Insights reports, and the same logic applies in any CRM: a deal that changes process midway distorts both pipelines' conversion rates. Close it in one pipeline and open a new deal in the other.
Run a 30-minute weekly pipeline review
Use the same five checks every week: deals with no next action, next actions that are overdue, deals that have sat in one stage longer than your limit, deals lost since last week with their reasons, and any case where two people recorded the same situation differently. Fix the deal or fix the definition, and move on.
Let the CRM flag stale deals for you. Pipedrive's rotting setting, for example, marks a deal that stays in one stage longer than the number of days you set and sends a notification. A sensible starting limit is your typical time in that stage plus 50%.
After a month, look at stage counts and movement. If deals pile up in one vague stage, or a required field is routinely filled with a placeholder, simplify the design before buying more reporting.
Keep a versioned pipeline definition. When a stage changes meaning, note the date and how existing deals were handled. Otherwise a trend can reflect an admin change rather than a real improvement in sales.
Template and next steps
A pipeline definition with entry and exit rules for each stage, a short list of required fields and a weekly review agenda. Adapt the fields to your own process and keep passwords, card details and other sensitive account data out of shared worksheets.
Frequently asked questions
How many stages should a sales pipeline have?
Four to six open stages plus won and lost suit most small B2B teams. Fewer than four usually hides the difference between a first meeting and a sent proposal; more than seven usually means tasks such as “second follow-up” have become stages, or two different processes share one pipeline. Each stage needs entry evidence that a colleague could verify from the record alone.
What are the stages of a sales pipeline?
A common small-business pattern is discovery booked, requirements confirmed, proposal sent, decision pending, then won or lost. Some teams add a qualification stage at the start or a contract stage at the end. Name each stage after something the buyer has done, such as agreeing to a meeting or acknowledging a proposal, not after how confident the seller feels.
What is the difference between a lead and a deal in a CRM?
A lead is an inquiry that has not been qualified; a deal, or opportunity, is a qualified chance to sell with a value, an owner and an expected close date. A practical rule is to create the deal only when there is a named buyer, a stated problem, a plausible fit and an agreed next conversation. Everything else stays a lead or a contact.
When should I use multiple pipelines in a CRM?
Use a second pipeline only when a second process has genuinely different milestones, such as new project sales versus renewals, or direct sales versus partner deals. Two sellers doing the same work need a filter, not another pipeline. Check your plan too: HubSpot's free tools include one pipeline per object, and Zoho CRM's free plan has only the default pipeline.
How do you calculate deal probability for each pipeline stage?
Use your own history: divide the deals won by all deals that reached the stage over the last 12 months. If 12 of 40 deals that reached proposal sent were won, that stage's probability is 30%. With fewer than about 30 closed deals, skip weighted forecasts and review the unweighted pipeline instead. In Pipedrive, a deal-level probability overrides the stage probability.
Sources
Prices and plan limits come from each vendor's own pricing pages and documentation, checked on the dates shown. Vendors change packaging often, so confirm the final figure in your own quote.
- Pipedrive: how to customize pipeline stages — checked Oct 29, 2026Stage design, stage and deal probability, rotting and the warning about moving deals between pipelines.
- HubSpot: set up and customize pipelines — checked Oct 29, 2026Pipeline limits on the free tools and paid plans.
- Pipedrive: multiple pipelines — checked Oct 29, 2026Customizable pipelines on all plans.
- Pipedrive: usage limits — checked Oct 29, 2026Custom fields per company by plan.
- HubSpot: product and services catalog (free tools) — checked Oct 29, 2026Free-tools limits: reporting history, custom properties, pipelines.
- Zoho CRM: pricing — checked Oct 29, 2026Plan prices, free plan and pipelines by plan.
- Freshsales: plan comparison — checked Oct 29, 2026Multiple pipelines by plan.