The pipeline is the single operational artifact that lets a revenue team see what is in play, forecast what will close, and decide where to spend the next hour.
A sales pipeline is a visual representation of every active deal grouped by stage, showing where each prospect sits in the buying process. Common stages: Lead, Qualified, Discovery, Proposal, Negotiation, Closed Won. Each stage has entry criteria, exit criteria, and expected probability. Sales teams use pipelines to forecast revenue, prioritize deals, and spot bottlenecks. Modern CRMs show pipelines as drag-and-drop boards or tables with filters by owner, segment, and close date.
A pipeline is not a status column on a spreadsheet. It is a scoreboard, a forecasting input, a coaching surface, and a workload map, all read off the same object. The five points below are the ones that distinguish a working pipeline from a decorative one.
Every active opportunity lives in exactly one stage at a time, has an owner, a dollar amount, and a close date. That data model is non-negotiable. Without it a pipeline is a mood board. With it you can forecast, pace, and coach without ambiguity.
Each stage carries explicit entry and exit criteria: the fields, approvals, and buyer actions required to move forward. Qualified means the champion is identified and budget is confirmed. Proposal means the pricing document is sent. Clean criteria make stage data trustworthy enough to forecast on.
Every stage carries a historical conversion rate. Multiply each deal value by its stage probability and you have weighted pipeline, the number most revenue leaders use for a reality-adjusted forecast. Discovery at 20 percent, Proposal at 50 percent, Negotiation at 75 percent is a typical pattern.
A healthy pipeline carries three to four times quota in coverage, moves deals in a predictable number of days per stage, and keeps the average deal age below the length of a full sales cycle. When any of those drift, the pipeline is telling you something before the forecast catches up.
Modern CRMs render pipeline as a drag-and-drop kanban board, a sortable table, or both. The visual lets a rep triage in a glance. The underlying structured data lets the system forecast, trigger automations, and feed revenue reporting without a secondary spreadsheet.
A mature revenue team runs more than one pipeline. New business has one shape. Expansion and upsell have another. Renewals have a third, driven by contract clocks instead of discovery calls. The CRM should let you define each pipeline with its own stages, probabilities, and automations.
There is no universal stage list, but most B2B pipelines converge on a six-to-eight stage pattern because the buying process itself tends to converge. The names change by industry. The shape does not.
A new contact or account that fits the ideal customer profile but has not yet been qualified. The lead stage is a holding area for inbound form fills, outbound targets, and list uploads before a human has worked them. Entry criteria are minimal. Exit criteria is a human-qualified next step.
A rep has made contact, confirmed basic fit, and identified a reason the account might buy. Many teams use BANT, MEDDIC, or GPCT frameworks here. Expected probability is low, often 10 percent, but the deal is now real enough to forecast against the top of pipeline coverage.
A scheduled meeting with a decision maker or champion. The rep uncovers pain, impact, decision process, timeline, and competitive context. Discovery is the stage where most forecast errors are set in motion, because weak discovery produces optimistic probability guesses later in the cycle.
Pricing has been shared in writing, scoped to the buyer problem, with an identified decision maker. Probability typically climbs to 40 to 50 percent at this stage. A deal that has sat in Proposal for more than one sales cycle is one of the strongest leading indicators of a slip.
Terms, procurement, legal, and final pricing. Probability climbs to 70 to 80 percent, but the risk shape changes. Deals in Negotiation lose less often than deals in Discovery, but when they lose they lose late, which hurts the quarter more than an early-stage loss hurts the pipeline.
The deal is signed or dead. Closed Won moves the record to onboarding, kicks off the implementation project, and locks the revenue number for commissions. Closed Lost captures the reason, the competitor if any, and leaves the record available for re-engagement in a future cycle.
Most pipelines break for the same reasons: stages mean different things to different reps, probabilities are made up, close dates are optimistic, and nothing enforces the stage criteria. The checklist below is how a working pipeline is built.
Stages should mirror the buyer, not the seller. A pipeline that reads Email Sent, Meeting Booked, Demo Done is seller-centric and tells you nothing about buying intent. A pipeline that reads Problem Identified, Options Compared, Decision Approved tracks the thing you are actually trying to predict.
For each stage, list the fields that must be populated, the activities that must be logged, and the buyer action that signals progression. Qualified requires a confirmed decision maker and a stated reason to evaluate. Proposal requires a sent document and a scheduled follow-up. Reps enforce the shape, the CRM enforces the data.
Pull six to twelve months of closed deals, group by exit stage, and compute win rate per stage. That is your probability. Over time, Strkr AI can refine these per segment and per rep because the pattern in a 60-day cycle is different from a 180-day cycle.
For each stage, measure median days-in-stage. A deal that sits in Discovery for 45 days when the median is 10 is a flag. Velocity turns the pipeline from a snapshot into a motion study and makes stuck deals visible before the forecast misses the number.
A pipeline is only as clean as the data in it. Required fields on stage advance, close-date reminders, inactivity flags on quiet deals, and auto-moves on signed documents all keep the pipeline true without a weekly nag email. In Strkr the Flows engine handles this on every paid tier.
The pipeline review is a weekly working session, not a status update. Walk the board, challenge the probability on top deals, surface age violations, pull forward committed deals, slip the ones that are not real. The pipeline becomes a coaching surface, not a reporting artifact.
A pipeline you built but never read is just a database. The point of the pipeline is the signals it gives you about the next 30, 60, and 90 days of revenue. Here is what the dashboard should show by Monday morning.
Pipeline coverage is open pipeline divided by remaining quota. Below 3x and the team is unlikely to hit. Above 5x and the pipeline likely contains noise that will churn out in forecast. The right range sits in that band for most B2B motions and tightens as the quarter progresses.
Sum of deal value times stage probability across the open pipeline. A board can see 4 million in pipeline and 1.1 million weighted. The weighted number is what grown-up finance teams run their reforecasts on. The raw number is for internal motivation.
Every stage has a median duration. Deals past 1.5x the median are flagged. Deals past 2x are escalated. Age is the single strongest leading indicator of a slip, because deals rarely close faster than they move through middle stages.
The forecast categories pipeline, best case, commit, and closed trade certainty for upside. Commit is the number a rep will stand behind. Best case is upside with a path. Pipeline is everything else. The gap between pipeline and commit tells you how much of the number is still at risk.
Pipeline by owner shows which reps are over-indexed and which are under-fed. A top performer carrying 40 open deals while a new hire carries 8 is a routing problem, not an execution problem. Fix the inputs and the outputs will follow.
Closed Lost reasons rolled up by stage and competitor tell you where the funnel is actually failing. Losses at Discovery mean a qualification problem. Losses at Proposal mean a pricing or value gap. Losses at Negotiation mean a procurement or incumbent problem. Each one has a different fix.
Drag-and-drop board, forecasting that reads live stage data, multiple pipelines for new business, expansion, and renewal, and the Flows engine to keep stage data clean. All included on every paid tier.
A pipeline is the view sales teams work from, showing active deals by stage with owner, value, and close date. A funnel is the aggregate conversion view, showing how many leads enter at the top and what fraction convert at each stage. The pipeline is operational. The funnel is analytical. Most CRMs render both off the same underlying deal data.
Most B2B pipelines land between five and eight stages. Fewer than five and you lose granularity for forecasting and coaching. More than eight and reps lose track of what each stage actually requires. The right number is the number of distinct buyer actions in your sales cycle, not the number of internal handoffs.
A weighted pipeline multiplies each deal value by the historical win rate of its current stage. If a 50,000 dollar deal sits in Proposal with a 50 percent win rate, it contributes 25,000 to weighted pipeline. The weighted total is a reality-adjusted forecast number, more conservative than raw pipeline and more honest than a rep gut call.
Weekly for reps and managers, monthly for leadership, in-quarter for finance. The weekly review is a working session where stage probabilities, close dates, and risks are challenged deal by deal. Daily is too noisy. Monthly is too late. The weekly cadence catches slips and pulls forward opportunities while there is still time to act.
Pipeline coverage is total open pipeline divided by remaining quota. Three to four times is a healthy band for most B2B motions. Below 3x the team is likely to miss. Above 5x the pipeline often contains deals that are not real and will churn out in the forecast. Coverage ratios tighten as the quarter progresses and more deals convert or slip.
A modern CRM gives the pipeline a drag-and-drop board, a sortable table, forecasting that reads directly off the stage data, and automations that enforce hygiene. In Strkr, Flows triggers kick off on stage changes, Forecast rolls commit and best case into a submit-locked number, and the pipeline, reports, and dashboards all read the same source of truth without a secondary spreadsheet.
Pipeline velocity is a single metric that combines deal count, average deal value, win rate, and sales cycle length into a dollars-per-day number. The formula is deal count times average value times win rate, divided by sales cycle length in days. It tells you how much revenue the pipeline is generating per working day and makes performance across teams or quarters directly comparable.
Yes, once the motion mixes new business, expansion, and renewal. Each motion has a different shape: new business is discovery-heavy, expansion is usage-signal heavy, renewal is clock-driven. Running them on the same pipeline forces every stage to compromise. Strkr supports multiple named pipelines with independent stages, probabilities, and automations on every paid tier.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
