How to build a sales pipeline: from the ICP and a prospect list to stages with written exit criteria and a weekly review your team will actually run.

What is a sales pipeline?

A sales pipeline is the list of open deals your team is working, grouped by the stage each deal has reached, from first contact to closed won or closed lost. Knowing how to build a sales pipeline starts there: it is the seller's view of what is in play and what happens next.

Building one means deciding four things: which accounts belong in it, which stages a deal passes through, what written rule moves a deal from one stage to the next, and how often the team reviews it. The CRM holds the pipeline, but these decisions make it useful.

A pipeline that works lets a sales leader answer three questions on any Monday: do we have enough deals to hit the number, which deals are stuck, and which ones should not be in there at all.

Sales pipeline vs sales funnel vs sales process

The three terms get mixed up, and the confusion shows up in bad stage names. Salesforce draws the line this way: the pipeline is the seller's view of deals being worked, while the funnel describes the buyer's journey from discovery through consideration to purchase.

In practice, you design the B2B sales process first, then mirror it in pipeline stages. The funnel is how you report on the flow of leads and deals across those stages over time.

Why a sales team needs a built pipeline

Every team has deals. Not every team has a pipeline, meaning a shared structure where a stage name means the same thing to every rep and manager. Without it, the CRM becomes a list of hopes.

• Forecasting: when stages are defined by buyer actions, the value in late stages is something a manager can plan revenue around.
• Coverage: you can see early whether there are enough opportunities to reach the target, while there is still time to prospect more.
• Coaching: stage-to-stage conversion shows where a rep loses deals, which tells the manager what to coach.
• Focus: reps spend time on deals that are moving and stop nursing ones that died weeks ago.
• Resource planning: the size and shape of the pipeline tells you whether you need more prospecting, more closing capacity or better qualification.

What you need before you build a sales pipeline

Most pipelines fail before the first deal is entered, because the inputs were never written down. Gather these first:

• An ideal customer profile. The firmographic and situational traits of the accounts you win and keep. It decides who gets into the pipeline at all.
• A prospect list. Named target accounts and the people in them, built from that profile, with the data your reps need to start outreach.
• Your real sales process. What actually happens between first contact and signature, taken from recent won and lost deals, not from a vendor template.
• A revenue target. The quota or number for the period, so you can work backward to how much pipeline you need.
• A CRM with deal stages. Or a spreadsheet at first. The tool matters less than the stage definitions inside it.
• The people who will use it. Reps, managers and marketing, who have to agree on what each stage means.

Start with the ICP and a prospect list

A pipeline is only as good as what enters it. Filling the top with accounts that will never buy produces a big, flattering number and a bad forecast. Start with your ideal customer profile: industry, company size, region, the systems they run and the trigger that usually starts a project.

Then turn the profile into a target account list. Pull the accounts that match, add the roles in each buying group, and fill gaps with lead enrichment so reps know company size, tech stack and the right contact before the first touch.

Record the lead source on every deal from day one. After a quarter, source is the field that tells you which of your lead sources produce deals that close, not just meetings.

Sales pipeline stages for B2B

Sales pipeline stages should follow what the buyer does, not what the rep does. "Sent proposal" describes rep activity; "buyer reviewed proposal with the decision-maker" describes progress. Most B2B teams land on five to seven stages between the first conversation and the close, plus closed won and closed lost.

The stage names below are a common B2B pattern written for this page. Rename them to match your sales motion, but keep the idea: one clear buyer outcome per stage.

What happens in each stage

• Prospecting: reps research target accounts and start outreach by email, phone and LinkedIn. Many teams keep this as lead or account activity and only create a deal when a meeting is booked.
• Qualified: a first conversation confirmed the account fits the profile and has a problem worth solving. This is where a lead becomes an opportunity.
• Discovery: the rep understands the pain, the impact, the current approach, who decides and how they buy.
• Solution or evaluation: the buyer sees how you solve their problem through a demo, trial, pilot or workshop, and involves the people who will judge it.
• Proposal: pricing and terms are in front of the buyer, and the rep knows who will review them.
• Negotiation and commitment: commercial, legal and security questions are worked through until signature.
• Closed won or closed lost: the outcome, with a recorded reason either way.

Some teams add a post-sale stage for onboarding and expansion. That works if the pipeline is also used for account management, but keep new business and expansion separate in reporting.

Stage exit criteria: the rule that moves a deal

Stage exit criteria are the written, checkable conditions a deal must meet before it moves to the next stage. They are what make a stage mean the same thing in every rep's pipeline. Without them, deals move on optimism, and the late stages fill with deals that are not late at all.

Good exit criteria are buyer actions you can verify, recorded in the CRM, and few enough that reps actually check them. Two to four per stage is plenty.

This table was written for this page as a starting point. The most useful test for any criterion: could a manager check it in the CRM without asking the rep? If not, rewrite it.

Entry rules and skipping stages

Deals do not always move in order. A buyer who arrives through a referral may already know the problem and the budget. Allow a deal to skip a stage when it meets that stage's exit criteria, and record the skip. Never let a deal jump forward while earlier criteria are still open.

Qualification decides what counts as pipeline

The Qualified stage is the gate. Everything before it is activity; everything after it is pipeline that counts toward coverage and forecast. That makes the definition of a qualified opportunity the single most important rule in the whole system.

Use one framework the team already understands, whether that is BANT, MEDDIC or a simpler list of your own, and turn it into required CRM fields. Our guide on how to qualify sales leads compares the frameworks and the questions behind each letter.

Agree with marketing on the handoff too. A marketing qualified lead is not yet pipeline. It becomes pipeline when sales accepts it and a conversation confirms fit and need.

Deal stage probabilities and weighted pipeline

Most CRMs let you attach a probability to each deal stage. The weighted pipeline is each deal's amount multiplied by its stage probability, added up. HubSpot's documentation, for example, describes its default sales pipeline as seven deal stages, each with a probability used to calculate the weighted amount shown on the board.

Default probabilities are placeholders. Replace them with your own historical stage-to-close rates once you have a couple of quarters of clean data, and review them when your sales motion changes.

Pipeline coverage: is there enough in the pipeline?

Pipeline coverage compares the value of open pipeline for a period with the target for that period. Salesforce describes it as the total value or number of deals in the pipeline, used to see whether there are enough potential sales to meet revenue goals.

The calculation is simple: open qualified pipeline value due to close in the period, divided by the remaining target for the period. The ratio you need is not universal. It depends on your own win rate: the lower it is, the more pipeline each dollar of target requires.

Work the gap backward into activity. If you know roughly how many first meetings turn into a qualified opportunity, you know how many meetings to book, and your sales quota turns into a weekly prospecting target.

Pipeline velocity: the formula, explained

Pipeline velocity, also called sales velocity, estimates how much revenue your pipeline produces per day. Pipedrive's guide gives the standard formula, and it treats the two names as the same measure.

• Number of qualified opportunities: open deals that passed your Qualified exit criteria, not every record in the CRM.
• Average deal size: the average value of won deals over the same period.
• Win rate: won deals divided by all qualified deals that closed, won or lost.
• Sales cycle length: the average days from qualified to closed won.

The value of the formula is diagnostic. Velocity goes up if you add qualified deals, raise deal size, win more often or close faster. When velocity drops, look at which of the four moved, and fix that part of the pipeline instead of pushing for more activity across the board.

How to build a sales pipeline, step by step

These steps take a team from nothing, or from a messy CRM, to a pipeline you can forecast from. Do them in order; each one depends on the one before.

1. Write down the ideal customer profile

   Describe the accounts you win and keep: industry, size, region, systems and the trigger that starts a project. Base it on closed won deals, not on who you wish would buy.

2. Build a target account and prospect list

   Pull the accounts that match the profile, map the roles in each buying group, and enrich the records so reps can start outreach with the right person and a reason to call.

3. Map your real sales process

   Review recent won and lost deals with the reps who worked them. Note what the buyer did at each step, who was involved and where deals stalled.

4. Define the stages and exit criteria

   Turn the process into five to seven stages named after buyer outcomes. Write two to four checkable exit criteria for each, and make them required fields in the CRM.

5. Set up the CRM and the fields

   Create the deal pipeline, the stages, the required fields, lead source, close date and amount. Add a loss reason picklist so closed lost deals teach you something.

6. Calculate the pipeline you need

   Divide the remaining target by your historical win rate to get the pipeline needed, compare it with what you have, and turn the gap into weekly prospecting and meeting targets.

7. Fill the top with outreach

   Run a consistent sales cadence across email, phone and LinkedIn to the target list, and add inbound and referral deals through the same qualification gate.

8. Review the pipeline every week

   Hold a short weekly pipeline review on a fixed agenda: new deals, movement, stuck deals, close dates and coverage. Clean out dead deals as you go.

How to fill the pipeline with qualified deals

Stages and rules do nothing without deals coming in. Most B2B pipelines are fed by a mix of outbound and inbound, and the mix should come from your own conversion data by source.

• Outbound prospecting: reps work the target list with a planned sales cadence of emails, calls and LinkedIn touches. See what prospecting involves for the research side.
• Inbound leads: demo requests and high-intent form fills go straight to qualification; lower-intent leads go to nurturing first.
• Nurtured leads: leads who were not ready earlier come back through lead nurturing when behavior shows interest.
• Referrals and partners: often the fastest deals, which is why they deserve their own source value in the CRM.
• Existing customers: expansion and cross-sell deals, tracked separately from new business.

Whatever the source, every deal passes the same Qualified exit criteria. A shortcut for one channel is how junk gets into the forecast.

The weekly pipeline review routine

A pipeline review is a recurring meeting where a manager and reps go through open deals to check movement, risk and next steps. Weekly is the common rhythm for B2B teams: often enough to catch stalls, rare enough that deals have time to move.

Keep it short and run it from the CRM, not from memory. The rep updates deals before the meeting; the meeting is for decisions, not data entry.

Separate the weekly review from forecasting calls and one-to-one coaching. The review keeps the data honest; the forecast call commits a number; coaching works on the rep's skills in specific deals.

Pipeline hygiene between reviews

• Every open deal has an amount, a close date, a next step and a source.
• Deals with no buyer activity for a set period get a decision: restart or close lost.
• Duplicates are merged, and closed deals carry a reason.
• Close dates are the buyer's date, not the end of the quarter.

Sales pipeline metrics to track

A handful of metrics tell you whether the pipeline is healthy. Track them by rep, by source and by segment, and compare periods, not teams in other companies.

Tools for building and managing a pipeline

This page does not rank vendors. These are the tool categories a sales pipeline runs on:

• CRM: holds accounts, contacts and deals, the stages, required fields and reports. A spreadsheet can stand in for a very small team.
• Sales engagement: runs the outreach cadence and logs emails and calls to the CRM.
• Data and enrichment: fills company and contact data so the prospect list matches the profile.
• Conversation intelligence: records and transcribes calls, which helps managers check exit criteria like pain and decision process.
• Forecasting and analytics: rolls stage data into coverage, velocity and forecast views.

A sales pipeline example

This example was written for this page, and the company is fictional. A software firm selling to mid-sized logistics companies defines its ICP by fleet size and the dispatch system in use. It builds a list of matching accounts and the operations and finance roles in each.

Its pipeline has six stages from Qualified to Negotiation. A deal leaves Discovery only when the rep has written down the cost of the current dispatch problem in the buyer's words and named the person who signs. In the weekly review, deals without a buyer-agreed next step are the first ones discussed.

When velocity dips, the manager checks the four inputs. If the drop comes from fewer new qualified deals, the fix is prospecting; if cycle length grew, the fix is in the stage where deals now wait longest.

Common sales pipeline mistakes

• Stage names that describe rep activity, such as "Email sent", instead of buyer progress.
• No written exit criteria, so every rep uses the stages differently.
• Counting unqualified leads as pipeline, which inflates coverage.
• Close dates set to the end of the quarter instead of the buyer's real timeline.
• Keeping dead deals open because closing them lost feels like failure.
• Using the CRM's default stage probabilities forever instead of your own history.
• Skipping the weekly review when the quarter looks good, then finding the gap too late.
• Building a pipeline for a sales process nobody follows.

The note before a weekly pipeline review

The template below is a short note a sales manager sends reps the day before the weekly pipeline review. It asks for updates in the CRM in advance, so the meeting can spend its time on decisions.

Subject: Pipeline review {{day}}: update these before we meet

Hi {{teamName}},

Before {{day}} at {{time}}, please update every open deal you own in {{crmName}}:

1. Stage matches the exit criteria it has actually met.
2. Next step is dated and agreed with the buyer.
3. Close date is the buyer's date, with a reason if it moved.
4. Deals with no buyer activity since {{cutoffDate}}: restart plan or close lost.

In the meeting we will cover new deals, stuck deals, slipped dates and coverage against {{target}}. Bring one deal you want help on.

{{managerName}}

Frequently asked questions