Sales Pipeline Stages:
From Lead to Close

Sales pipeline stages track a potential sale from prospecting to close. Salesforce’s pipeline guide explains how stages show each prospect’s position, the next selling action, and obstacles to purchase.

The seven common sales pipeline stages#

The seven stages in Salesforce’s common pipeline model are prospecting, lead qualification, sales meeting or demo, proposal, negotiation, contract signing, and post-purchase.

The first six cover the path to a sale; post-purchase covers the customer relationship afterward. Stage labels vary with the sales process.

1. Prospecting#

Prospecting identifies people or organizations that could need the product or service. Pipedrive’s pipeline guide describes this stage as finding prospective buyers and recommends minimum qualification requirements before adding opportunities to an active pipeline.

The work includes researching potential buyers, recording the source of an inquiry, and making initial contact. Capture enough information to assess whether further discussion is relevant: the potential need, the contact, and a next action. Finding a name begins the process; qualification establishes whether there is a purchase worth pursuing.

2. Lead qualification#

Qualification assesses whether the offering fits the prospect’s needs and whether a purchase is feasible. One common framework is BANT, as described by Salesforce:

• Budget: Can the buyer afford the offering?
• Authority: Who can make or influence the purchase decision?
• Need: What problem would the purchase solve?
• Timeline: When is a decision expected?

These questions guide a conversation rather than prescribe a rigid script. Record the answers and the questions still open. The purpose is to establish enough fit and buying context to decide whether a substantive sales discussion is appropriate.

3. Sales meeting or demo#

The meeting or demonstration connects the offering to the buyer’s requirements. HubSpot’s stage guide recommends understanding the buyer’s goals, relevant stakeholders, likely objections, and the intended meeting outcome beforehand.

Discovery clarifies what the buyer needs; a demonstration shows how the offering addresses it. HubSpot’s proposed exit criteria include agreed success criteria and a request for a proposal or pricing. Define advancement by the agreed next step after the presentation.

4. Proposal#

The proposal turns the discussion into a specific offer. Salesforce Trailhead’s opportunity guidance describes proposals and price quotes as presenting products or services, benefits, pricing, and relevant terms.

The document should connect the proposed purchase to the requirements established earlier. Define whether the stage begins when the offer is sent or when the buyer begins reviewing it. Record the scope, recipient, and next discussion so the stage’s meaning stays consistent.

5. Negotiation and commitment#

Negotiation resolves the terms needed for an agreement. Salesforce’s negotiation guide covers commercial terms, responsibilities, deliverables, and timelines; the discussion can extend beyond price.

The work includes clarifying objections, reviewing requested changes, and agreeing on acceptable trade-offs. Preparation should establish the seller’s objectives, available concessions, and terms that require approval. Record unresolved issues and who must address them.

For a process with a separate signature stage, define the transition as agreement on the substantive commercial terms and readiness for final review or signing. Negotiation remains active while those terms are unresolved.

6. Contract signing and close#

Contract signing formalizes the agreed sale. Salesforce’s contract guide describes the written agreement as recording the offering and transaction terms, with review before signing and delivery afterward.

At this point, track the agreement version, any remaining approval, and the signature step. Define the event that counts as a completed sale for the business and record it consistently. Preparing or sending a contract is an open selling step; completing the required agreement moves the opportunity to a closed outcome.

7. Post-purchase#

Post-purchase work begins after the initial sale and covers the transition into delivery, onboarding, or ongoing service. HubSpot’s post-sales guidance recommends a documented handoff that includes the customer’s priorities, concerns, and important milestone dates.

Record the next owner and agreed delivery work in the handoff. The seven-stage lifecycle model includes this transition even though the sale has already closed.

Where closed won and closed lost fit#

Closed won and closed lost record the outcome of a sales opportunity. In Salesforce Trailhead’s example, a won sale has agreed terms and finalized paperwork; a lost sale has ended without a purchase.

Closed lost is an alternative outcome to closed won, rather than a step every successful sale passes through. It can occur before the final selling stage. Record the known reason, such as a mismatch in needs, budget constraints, or selection of a competing offering. Post-purchase work follows a won sale.

When does a lead enter the deal pipeline?#

A full sales-process diagram can start with prospecting even when the CRM’s deal pipeline starts later. Pipedrive distinguishes leads from deals: leads are unverified potential opportunities, while deals have been approved for its sales pipeline.

Pipedrive also ties conversion to the first stage defined for that pipeline. This makes the entry rule part of the stage design. Specify what must be known or completed before creating a deal, and keep earlier prospecting or qualification work in the lead workflow where appropriate. The boundary depends on the selling process and the CRM’s terminology.

How many stages should a sales pipeline have?#

There is no fixed stage count. The seven-stage lifecycle model above differs from HubSpot’s default deal pipeline, which also has seven stages but begins with a scheduled appointment and includes separate won and lost outcomes.

The count therefore depends on what the pipeline includes and how finely the process is divided. HubSpot’s stage guide combines proposal and negotiation, while the Salesforce model separates them.

Choose stages around meaningful milestones. Pipedrive recommends giving each stage a clear purpose, exit criteria, and next action. Use those distinctions to decide whether adjacent stages need separate labels.

Separate pipelines are appropriate when selling processes require distinct stages, according to HubSpot’s configuration guidance. Processes sharing the same stages can share a pipeline.

Define when a deal can move forward#

An exit criterion is the requirement for completing a stage. Salesforce’s pipeline management guidance recommends specific, measurable criteria tied to actions, milestones, and qualifications.

Write each stage definition with:

• Entry condition: What places an opportunity in this stage.
• Work to complete: What the seller and buyer need to resolve.
• Exit condition: What confirms readiness for the next stage.
• Next action and owner: Who is responsible for advancing the discussion.

Salesforce’s review guidance uses questions about the buyer’s use case, technical fit, and budget to test readiness for a demonstration. Select the checks relevant to each stage and record what remains unresolved.

Sales pipeline stages versus sales funnel stages#

A pipeline organizes selling work around prospects and opportunities. A funnel describes the buyer’s journey, including awareness, consideration, evaluation, and purchase. Salesforce’s funnel guide distinguishes the two by perspective: the pipeline guides sales engagement, while the funnel follows how the buyer approaches a purchase.

The labels overlap because they describe the same broader buying process. They do not always map one to one. Salesforce also explains that buyers can revisit or skip funnel stages, so a stage diagram should serve as a guide to the process rather than imply that every purchase follows an identical path.

Track stage movement and review stalled deals#

Review conversion between stages, won and lost outcomes, and current deal activity. Salesforce’s management guide recommends combining historical results with current pipeline information to evaluate performance and identify where opportunities stop progressing.

Stage probabilities are a separate setting. In HubSpot’s deal pipeline, weighted amounts multiply deal amounts by the configured stage probability. Treat those percentages as part of the CRM’s calculation, rather than as stage definitions or guarantees of a purchase.

A stalled deal needs a clear next action. Salesforce’s pipeline review guidance recommends identifying obstacles, setting priorities, and assigning responsibility for resolving them. Useful review questions are:

• What requirement is keeping the opportunity in this stage?
• What has the buyer confirmed since the last review?
• What action is needed next, and who owns it?
• When will that action be followed up?

Use the answers to update the deal’s current stage, remaining work, and next step. Review stage definitions when the same ambiguity repeatedly prevents a clear decision about where opportunities belong.