Sales Pipeline Stages: 8 Milestones Small Teams Must Track

A typical sales pipeline has these stages: prospecting, qualification, discovery or demo, proposal, negotiation, close, and post-sale, with some companies using tools like AI-powered discovery and eligibility matching platforms to optimize these early pipeline stages. Using defined stages makes forecasting and follow-up repeatable, because every deal moves through the same checkpoints and everyone on the team knows what “progress” actually means.

---

TL;DR:

• Advance a lead only when at least three of four qualification points, budget, authority, need, and timeline, are reasonably clear, not merely discussed.
• Keep the pipeline to 5 to 8 observable stages, and merge any step that fewer than one in ten deals use distinctly.
• Use pipeline value and stage probability to forecast individual deals; switch to funnel conversion rates when many deals stall at the same stage.
• Review stage conversion and time in stage weekly to catch stalled deals, but assess win rate and sales cycle length monthly.
• Pilot revised stages in one pipeline for a month, then keep only changes the team updates consistently without repeated reminders.

---

Table of Contents

• Canonical sales pipeline stages at a glance
• What to do and record at every pipeline stage
• Sales pipeline versus sales funnel: two different views
• Designing pipeline stages for your business
• Pipeline KPIs that actually tell you something
• What small teams get wrong about pipeline stages
• Running these stages inside one platform
• FAQ
• Sources

Canonical sales pipeline stages at a glance

Industry frameworks commonly describe seven or eight stages, each marking a specific milestone rather than a vague feeling that a deal is moving. Knowing these names helps you compare notes with other teams and set up a CRM that matches how buyers actually behave.

• Prospecting: identifying and researching leads who fit your ideal customer profile, before any contact is made.
• Qualification: confirming the lead has a real need, budget and authority to buy, usually through a short call or form.
• Discovery or needs analysis: a deeper conversation that uncovers the buyer’s specific problem, timeline and decision process.
• Demo or engagement: showing the product or service in action, tailored to what was learned during discovery.
• Proposal: sending a formal offer, quote or contract that reflects the agreed scope and price.
• Negotiation: resolving objections on price, terms or scope before signature.
• Close: the deal is won (signed) or lost (declined), closing the active sales motion.
• Post-sale, onboarding or expansion: handing the account to delivery or customer success, and watching for upsell or renewal opportunities.

Some teams merge discovery and demo into one “meeting” stage when their sales cycle is short, and smaller operations sometimes drop a separate negotiation stage, folding it into proposal. Sales-focused guides from major vendors commonly frame the sequence as prospecting through qualification, meeting or demo, proposal, negotiation, and closing, which lines up closely with the list above. The exact labels matter less than having clear, observable exit criteria for each one.

What to do and record at every pipeline stage

Each stage needs an owner, a goal and a small set of CRM fields that get updated the moment something changes. Vague stage names invite vague data, so the goal is to tie every stage to something you can observe and timestamp.

Prospecting. The goal is building a list of leads worth contacting. This usually sits with a business development representative (BDR), who logs source, company size and a first-touch date. No qualification has happened yet, so nothing here should be treated as a forecastable deal.

Qualification. The goal is confirming fit before investing more time. BANT-style prompts, referenced in Gartner’s guidance on qualification frameworks, ask about budget, authority, need and timeline, and remain a useful short checklist rather than a rigid script. Record budget range, decision-maker name, stated need and an expected timeline in the CRM. A lead only moves forward once at least three of those four are reasonably clear, not just “discussed.”

Discovery or needs analysis. The account executive (AE) usually owns this stage, digging into the specific problem, current workaround and internal process for approval. Capture the pain point in the lead’s own words, the number of stakeholders involved and a target decision date. A copy-ready outcome note might read: “Discovery call held 14 March. Pain: manual scheduling costing 6 hours a week. Decision maker: operations lead, needs sign-off from finance. Target decision: end of April.”

Demo or engagement. This is where the AE shows the product against the exact problem surfaced in discovery, rather than a generic walkthrough. Record which features were shown, who attended and any follow-up questions raised, since those often predict objections at proposal stage.

Proposal. The goal is a sent, dated document with agreed scope and price, which is a far more useful CRM status than “proposal in progress,” because it marks an observable event rather than a vague state. A short follow-up template: “Hi [name], following up on the proposal sent 10 March covering [scope] at [price]. Happy to walk through any part of it this week, does Thursday work?” Record expected close date, proposal value and any conditions attached.

Negotiation. Usually still owned by the AE, sometimes with a manager joining for larger deals. Log every term under discussion (price, contract length, payment schedule) and who on the buyer’s side is pushing back, so the next person on the deal has full context.

Close. Mark the deal won or lost with a reason code, not just a status flip. Losses tied to “budget,” “timing” or “chose competitor” tell you far more over a quarter than a blank field ever will.

Post-sale, onboarding and expansion. Ownership shifts to customer success, who should capture onboarding completion date and any expansion signals (seats added, new use case mentioned) for future upsell conversations.

Sales pipeline versus sales funnel: two different views

A pipeline tracks individual deals through discrete milestones, mainly for forecasting how much revenue is likely to close and when. A funnel tracks aggregate conversion rates between stages, mainly for spotting where leads drop off across the whole process. Organisations typically keep these separate: pipeline data answers “what will we close this quarter,” while funnel data answers “where are we losing people.”

Pipeline views lean on weighted value (deal value multiplied by the probability tied to its stage), while funnel views lean on conversion and drop-off percentages between stages. Switch to the funnel view when a stage-by-stage conversion rate looks unusually low across many deals, since that points to a process problem rather than a single lost opportunity.

Designing pipeline stages for your business

Start from the buyer’s actual journey, not from a generic template. A three-step framework keeps this manageable for small teams:

1. Map the buying journey: list every step a real customer took on your last five closed deals, in their own words.
2. Define milestone and exit criteria: for each stage, write one observable event (a signed proposal, a scheduled demo) that proves the deal has moved, not a feeling that it has.
3. Limit stages to 5 to 8 and name them clearly: collapse any stage that fewer than one in ten deals actually use as a distinct step, since a cluttered pipeline slows the team down more than it helps.

Use parallel pipelines only when deal types genuinely differ, such as new business versus renewals, rather than creating one pipeline per salesperson. Case examples from MuleSoft illustrate that mapping customer buying steps to clear pipeline milestones improves forecasting accuracy and keeps the underlying data clean.

Pro Tip: Pilot a new stage structure on one pipeline for a month before rolling it out everywhere, and only keep changes that the team actually updates without reminders.

Pipeline KPIs that actually tell you something

A handful of metrics cover most of what you need to judge pipeline health. Pipeline value is the sum of all open deal values, often weighted by stage probability. Conversion rate by stage is the percentage of deals that move from one stage to the next, calculated as deals advanced divided by deals entered, multiplied by 100. Deal velocity measures average days spent in each stage. Win rate is deals won divided by total deals closed (won plus lost). Sales cycle length is the average number of days from first contact to close.

Worked example: if 40 deals entered the proposal stage last quarter and 10 moved to negotiation, the conversion rate for that stage is 25%. If those same 10 deals averaged 9 days in proposal before moving, your proposal velocity is 9 days.

Forrester’s objectivity note stresses testing sales workflow changes rather than assuming a new stage structure works, which is a fair caution for any small team adjusting KPIs. Review conversion rate and velocity weekly, since they shift fast and flag stuck deals early; review win rate and sales cycle length monthly, since they need a larger sample to mean anything.

What small teams get wrong about pipeline stages

The biggest mistake is over-engineering the pipeline before anyone has even used it. Twelve finely defined stages look thorough on a whiteboard and get abandoned within a month, because nobody wants to update six fields every time they talk to a lead. Stage discipline exists to make forecasts more accurate, not to monitor every move a rep makes, and the moment it feels like surveillance, data quality collapses.

Expect to tweak stage names and exit criteria at least once in the first quarter. Measure the effect of each change on conversion rates before deciding it worked, rather than trusting a gut feeling that things “seem smoother now.”

— Chris

Running these stages inside one platform

A pipeline only works if the stage updates actually happen, and that is easiest when prospecting, proposals and follow-up communication all live in one place rather than scattered across a spreadsheet, an inbox and a separate quoting tool. We built custom pipelines so you can set the exact stages described above, attach proposals and contracts directly to a deal through our proposals & contracts feature, and automate stage updates from calendar events and signed documents with workflow automation.

Plans are available with features to track lead sources, calls, and emails against each stage. If you want to see how the stages in this guide would sit inside a working pipeline, check our pricing and start a trial with no long contract.

FAQ

What are the main stages of a sales pipeline?

Most pipelines run through prospecting, qualification, discovery or demo, proposal, negotiation, close, and post-sale or onboarding. Some teams merge discovery and demo, or drop a separate negotiation stage, depending on how long their sales cycle typically runs.

How is a sales pipeline different from a sales funnel?

A pipeline tracks individual deals through specific milestones for forecasting revenue, while a funnel tracks aggregate conversion rates between stages to spot where leads drop off. Use the pipeline view to predict what will close this quarter and the funnel view to diagnose a weak stage across many deals.

How many stages should a sales pipeline have?

Most workable pipelines use between five and eight stages, each tied to one observable milestone such as a signed proposal or a scheduled demo. Fewer, clearer stages tend to get updated consistently, while too many invite skipped or inflated statuses.

What counts as qualification in a sales pipeline?

Qualification confirms a lead has genuine budget, authority, need and timeline to buy, often checked with BANT-style prompts referenced in Gartner’s framework. A lead typically only moves forward once at least three of those four points are reasonably clear.

Can a CRM automate pipeline stage updates?

Yes, many CRMs can shift a deal’s stage automatically when a calendar event, call log or signed proposal is recorded, which keeps data more accurate than manual updates. Our own workflow automation feature applies this to stage changes, task creation and follow-up reminders.

Recommended

• Custom Pipelines
• The Complete Guide to Lead Management for Small Businesses
• Proposals & Contracts
• Lead Management