Sales Pipeline Stages: 7-Step CRM Template for 2026

Sales pipeline stages should tell your team what has happened in a deal, what evidence belongs in the CRM, and what must happen next. If a stage only describes how optimistic a rep feels, it will not support reliable coaching or forecasting.

For most B2B teams, a practical starting point is seven stages: qualified opportunity, discovery complete, solution fit confirmed, buying process confirmed, proposal submitted, negotiation and approval, and closed outcome. Treat the probabilities below as placeholders. Your own conversion history should replace them once you have enough clean data.

If you are choosing a CRM before designing the pipeline, complete the CRM requirements checklist first. If the product is already selected, include this pipeline work in the CRM implementation checklist before importing active deals.

Sales pipeline stages: quick template

This sales pipeline template is designed for a B2B deal pipeline. It begins when a lead becomes a credible opportunity. Prospecting, lead capture, and early nurture should usually live outside the deal pipeline so they do not inflate the value of active opportunities.

HubSpot's default deal pipeline also associates probabilities with stages, but its exact labels and percentages are product defaults, not a universal sales process. Its documentation confirms that a pipeline needs separate closed-won and closed-lost stages for reporting to work correctly.

CRM pipeline stages, funnel stages, and lifecycle stages

These terms often get combined even though they answer different questions:

• Lifecycle stage: What is this person or company in relation to us, such as subscriber, lead, opportunity, or customer?
• Funnel stage: Where is the audience in its broader journey, such as awareness, consideration, or decision?
• Pipeline stage: What verified milestone has this specific deal reached?

A contact can become a marketing-qualified lead without belonging in the sales pipeline. A company can be an existing customer while a new expansion deal sits in discovery. Keeping these concepts separate prevents the pipeline from becoming a list of everyone sales might contact someday.

Salesforce makes a similar distinction between an early lead and an opportunity. Its training material describes an opportunity as a qualified potential deal with details such as expected revenue, stage, close date, and probability. That is a useful threshold for deciding when a lead becomes an opportunity.

If marketing needs a consistent way to decide which leads sales should receive, define that separately with a B2B lead scoring model. Do not compensate for weak qualification by creating several vague early pipeline stages.

The seven sales pipeline stages

The labels can change, but each stage should represent buyer evidence rather than an internal activity. "Follow-up" is an activity. "Proposal submitted" is a milestone the team can verify.

1. Qualified opportunity

Create a deal only when there is enough evidence to justify sales attention. At minimum, confirm a plausible business problem, basic fit, a contact willing to engage, and a specific next step.

Do not require a fully proven budget or buying committee at this point. Discovery exists to learn those details. This stage separates credible opportunities from raw leads and unresponsive target accounts.

Use a strict exit rule: discovery must be scheduled with a person who can explain the current process and the problem. A rep sending a meeting link does not qualify. The buyer accepting a meeting does.

2. Discovery complete

Discovery is complete when the CRM contains more than call notes. The rep should be able to state:

• the problem the buyer wants to change
• the business or operational impact
• the current process or tool
• the people affected
• the desired result
• the next evaluation step

If the buyer cannot identify a real problem or meaningful next step, close or recycle the deal. Keeping weak deals open makes pipeline coverage look healthier than it is.

3. Solution fit confirmed

Move the deal here when the buyer has evaluated the proposed approach and agrees that it could meet the core requirements. Depending on the product, the evidence may be a completed demo, technical review, trial milestone, sample project, site visit, or requirements workshop.

Record gaps as well as strengths. A deal with an unresolved integration, security, migration, or service requirement is not fully validated. Link those risks to an owner and a next action.

If email, CRM, or marketing automation must work together, the B2B tech stack guide can help map the surrounding systems before the team promises a fit that has not been tested.

4. Buying process confirmed

Product interest is not the same as a buying process. This stage exists to confirm how the customer will make and approve the decision.

Capture:

• decision criteria
• economic buyer or final approver
• other stakeholders
• target decision date
• budget source
• procurement, legal, security, and finance steps
• competing options, including doing nothing

The exit condition is not "good meeting." The exit condition is a documented path from evaluation to decision. If that path is unknown, keep the deal earlier and make identifying it the next action.

5. Proposal submitted

Enter this stage when the buyer has received a proposal, quote, order form, or business case with an agreed scope and price. A draft sitting inside the CRM does not count.

Require the amount, products or services, proposal date, expected close date, and buyer contact. The next step should be a scheduled review or an agreed response date. "Waiting to hear back" is not a useful next step.

The proposal should reflect the requirements and buying process already discovered. Sending it early often turns discovery into unpaid follow-up.

6. Negotiation and approval

Use this stage only when active commercial or approval work remains. Examples include price negotiation, contract review, security assessment, procurement onboarding, or final executive approval.

Record each open issue, its owner, and the date it should be resolved. A verbal indication that the buyer "likes it" is not enough for a 90 percent probability. The deal belongs here when the core solution and commercial intent are accepted and the remaining approval path is visible.

If deals repeatedly stall at this point, inspect the earlier stages. Late security objections may mean solution fit was incomplete. Surprise budget problems may mean the buying process was never confirmed.

7. Closed outcome

Your CRM should use two separate terminal statuses:

• Closed won: The agreement is signed, payment or purchase confirmation exists, and delivery can begin.
• Closed lost: The buyer declined, chose another option, canceled the initiative, or stopped meeting the criteria for an active opportunity.

Require a structured loss reason and allow a short note for context. Useful loss reasons include price, product fit, missing integration, timing, competitor, procurement, no decision, and unqualified opportunity. Avoid a generic "other" bucket becoming the default.

Do not keep a dead deal open because the buyer might return. Close it with an accurate reason, retain the contact, and create a future task or nurture path.

How to build sales pipeline stages in your CRM

The table is only a starting point. Turn it into a working process with five controls.

Define entry and exit rules in plain language

Write one sentence for entering and leaving every stage. Test the rules against five real won deals, five lost deals, and several deals that stalled. If two managers place the same deal in different stages, the rule is still too subjective.

Require only fields that change action or reporting

Required fields should support qualification, routing, forecasting, execution, or analysis. Too many fields encourage fake answers. Too few fields leave managers unable to explain the pipeline.

HubSpot supports conditional properties when a record moves into a stage, while Salesforce Paths can surface key fields and guidance for each step. The exact interface differs, but the design principle is the same: ask for the information when it becomes relevant, not all at deal creation.

For email and calendar activity, use the CRM Gmail integration checklist to decide what should log automatically and what should remain private. Automatic activity capture can reduce admin work, but it does not replace a clear next step.

Give every open deal a next action and date

An opportunity without a scheduled or agreed next action is at risk regardless of stage. Require a next-action field and a date for every open deal. Report on missing and overdue actions in the weekly pipeline review.

Set probabilities from evidence

Stage probability estimates the chance that a deal in a given stage will close. Pipedrive distinguishes between stage probability and deal-specific probability and uses those values to calculate weighted pipeline. Its probability documentation also notes that a deal-specific probability can override the stage value.

Start with simple placeholders, then calculate each stage's historical probability:

Stage win probability = deals won after entering the stage / all deals that entered the stage

Use a consistent time window and exclude test data. Recalculate quarterly or when the process changes materially. Do not raise probabilities just to make the weighted forecast match the target.

Create separate pipelines only for different processes

Use another pipeline when the stages, owners, or reporting logic are meaningfully different. New business, renewals, partnerships, and delivery often deserve separate processes. Two regions selling the same product through the same steps usually do not.

Every extra pipeline adds fields, automation, reporting, and training work. Include that ownership cost when calculating CRM total cost of ownership.

Sales pipeline examples by business model

The seven-stage template fits consultative B2B sales, but the labels should follow the evidence in your sales motion.

B2B SaaS

A SaaS team might use qualified opportunity, discovery complete, technical validation, business case confirmed, proposal, security and legal, and closed outcome. A product-led company may replace discovery with a usage milestone if qualified deals emerge from trials.

Agency or consultancy

An agency might use qualified inquiry, discovery complete, brief confirmed, solution scoped, proposal submitted, commercial approval, and closed outcome. Scope confirmation matters because the service cannot be priced reliably until both parties agree on the work.

Short transactional sale

A short-cycle team may only need qualified, contacted, quote sent, decision pending, and closed outcome. Fewer stages are better when each extra column adds no useful decision or forecast signal.

Do not copy an enterprise pipeline into a three-person sales team. If you are unsure whether a shared contact system or full CRM is warranted, read CRM for small business and compare lighter contact management software.

Metrics that reveal weak pipeline stages

Review the pipeline as a process, not just a total dollar value. Track:

• Stage conversion: What percentage of deals entering each stage eventually move forward?
• Time in stage: How long do won and lost deals remain at each step?
• Stage regression: How often do deals move backward, and why?
• Skipped stages: Are reps bypassing required milestones?
• Data completeness: Are amount, close date, next action, stakeholders, and loss reason populated?
• Stale deals: How many open deals have no recent activity or future action?
• Win rate by source and segment: Which opportunities should enter the pipeline more or less often?

Use these measures to fix the process before adding automation. A low discovery-to-fit conversion may point to poor initial qualification. Long proposal time may indicate that proposals are sent before the decision process is known. Missing loss reasons may mean the team closes deals in batches without useful review.

For the broader rollout and adoption checks around these reports, use the CRM implementation checklist. If the pipeline depends on marketing qualification and sales handoff, pair it with the marketing automation requirements checklist.

Common sales pipeline mistakes

Using seller activity as the stage

"Call made" and "follow-up sent" describe work, not buyer progress. Store them as activities and keep stages tied to verified milestones.

Treating every lead as a deal

Raw leads make the pipeline look large while lowering conversion and forecast quality. Set an opportunity creation threshold and keep early nurture elsewhere.

Allowing deals with no next step

An open deal without a next action becomes stale inventory. Make the next action and date visible in every pipeline view and review.

Guessing probabilities forever

Placeholders are acceptable at launch. They should not survive once the team has enough stage history to calculate actual conversion.

Keeping one pipeline for every motion

New sales, renewals, onboarding, and partnerships may require different evidence and owners. Split materially different processes, but avoid duplicate pipelines for cosmetic reasons.

Refusing to close lost deals

Closing a deal is data hygiene, not an admission of failure. Accurate losses make conversion, cycle time, coaching, and future qualification better.

Actionable takeaways

• Start the deal pipeline at qualified opportunity, not at raw lead capture.
• Give every stage observable entry evidence and exit criteria.
• Require the smallest set of fields needed for action and reporting.
• Keep a dated next action on every open deal.
• Treat default probabilities as temporary setup values.
• Use closed won and closed lost as separate terminal statuses.
• Review conversion, time in stage, skipped stages, and stale deals each month.
• Add a new pipeline only when the underlying sales process is different.

Frequently Asked Questions

What are the seven stages of a sales pipeline?

A practical B2B template is qualified opportunity, discovery complete, solution fit confirmed, buying process confirmed, proposal submitted, negotiation and approval, and closed outcome. Use separate closed-won and closed-lost statuses for the final outcome in the CRM.

How many sales pipeline stages should a CRM have?

Use the fewest stages that capture buyer milestones. A short transactional sale may need four or five stages. A consultative B2B sale may need six or seven open stages plus closed-won and closed-lost outcomes. Add a stage only when it changes the required evidence, action, owner, or forecast meaning.

What is the difference between a sales funnel and a sales pipeline?

A sales funnel describes how a group of prospects narrows across the customer journey. A sales pipeline tracks the specific milestones and actions for individual deals. Funnel stages help analyze audience conversion, while pipeline stages help reps manage opportunities and managers review execution.

Should prospecting be a sales pipeline stage?

Usually not in a deal pipeline. Prospecting belongs in a lead queue or outreach process until a contact shows enough fit and engagement to become a credible opportunity. Putting every target account into the deal pipeline inflates pipeline value and weakens conversion data.

How should sales pipeline probabilities be set?

Use simple placeholders during initial setup, then replace them with the percentage of deals that won after entering each stage. Calculate from your own clean historical data, review the values periodically, and do not confuse rep confidence with stage probability.

When should a company create multiple sales pipelines?

Create multiple pipelines when sales motions have different stages, owners, required fields, or reporting logic. New business and renewals often qualify. Regions selling through the same process usually need one pipeline with regional fields rather than separate copies.

Which CRM is best for managing sales pipeline stages?

Pipedrive is a focused choice for visual deal management. HubSpot fits teams that want CRM, marketing, and service data together. Salesforce fits more complex sales processes that need deeper configuration and governance. Zoho CRM can suit budget-conscious teams that want customization. The best choice depends on the surrounding workflows, reporting needs, and administration capacity.

Next steps

Choose the CRM after the pipeline rules are clear. Compare Pipedrive vs HubSpot for a focused sales CRM versus a broader customer platform. Review HubSpot vs Salesforce when setup speed and usability are competing with enterprise control. Compare Zoho CRM vs HubSpot when budget and customization matter, or ActiveCampaign vs HubSpot when marketing automation is central to the sales handoff.