Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Pipeline & Forecasting

Pipeline Forecasting

ORM Technologies
Home/ Glossary/ Pipeline Forecasting
Definition Pipeline forecasting predicts how much revenue a period will close. It uses the deals in your pipeline, their stage close rates and their history. It also counts deals that will be created and closed inside the period.

What Pipeline Forecasting Means

Pipeline forecasting predicts how much revenue will close this quarter from the deals in your pipeline. It uses stage close rates, deal history and how each deal is moving. A good one also counts the revenue you cannot see yet: deals created and closed in the quarter, and deals pulled in from next quarter. Updated October 2026: Pete Furseth's three-part split of the quarter, a table of methods and where each fails, and a worked example.

It is the most direct line between what your sales team is working today and the revenue you will recognize tomorrow. Unlike a top-down estimate built from past bookings, it changes as individual deals advance or stall. Pipeline management builds and cleans the pipeline. Pipeline forecasting calls the number from it.

The core principle is simple: apply historical conversion rates to current pipeline composition and you get a probability-weighted revenue projection. The execution is where most teams fall apart.

Is pipeline coverage the same as a forecast?

No. Coverage tells you how much pipeline you have, not how much of it will close this quarter. "What most of the market gets wrong about revenue forecasting is the belief that pipeline coverage is the forecast," says Pete Furseth, ORM's COO. "It is not."

A team can have 4x pipeline coverage and still miss badly. The deals can be old, stuck in one stage, tied to a few large deals, or built on close dates sellers keep pushing out. Deal size hides a gap too. Pete's example: a pipeline with an average deal size of $80,000, where closed-won deals average $40,000. A forecast that trusts the pipeline amount overstates the quarter before anything slips.

The reverse also happens. A team can start the quarter with thin pipeline and still beat its number if it has a strong in-quarter motion. Coverage is a useful input. It should never be the conclusion.

What are the three sources of a quarter's revenue?

Every quarter is built from three streams, and a pipeline forecast should model each one on its own:

1. Carry-over deals. Deals already in pipeline on day one with close dates in the quarter. This is the carry-over pipeline every review starts with. 2. In-quarter deals. Deals that do not exist yet but will be created, qualified and closed inside the quarter. 3. Pull-forward deals. Deals from future periods that close early, usually with a discount or a cost to next quarter.

"Most teams over-trust the visible pipeline and under-model the invisible pipeline," Pete says. ORM's data shows why that matters. On the first day of a quarter, only about 20% of the pipeline value dated to close in that quarter usually closes in it. The other 80% does not land when the CRM says it will.

Pull-forward has two costs. The discount shrinks deal size, and the deal is no longer there to start next quarter's pipeline. Pipeline for a quarter is often built six to twelve months before it begins, so heavy pull-forward means spending more on pipeline generation later.

The point of the split is timing. Getting the forecast right in the last week of the quarter helps nobody. The value is knowing the likely shape of the quarter on day one, early enough to do something about it.

How is pipeline forecasting calculated?

The standard approach multiplies each deal by its probability of closing based on its current stage:

Pipeline Forecast = Sum of (Deal Value x Stage Probability) for all active deals

Stage probabilities should come from your own historical close rate by stage, not industry benchmarks. This gives you a weighted pipeline; see weighted vs. unweighted pipeline for when each view helps. The decomposition then checks it against the three sources. Layer in deal slippage rates and time-in-stage decay factors for more precision.

A worked example

This example is illustrative. A team has a $3.0M quarterly target. On day one it has $9.0M of pipeline with close dates in the quarter, so coverage is 3x. Here is the stage-weighted view:

StageHistorical close ratePipeline valueWeighted value
Discovery15%$3.0M$450K
Evaluation35%$3.0M$1.05M
Negotiation60%$2.0M$1.2M
Verbal Commit85%$1.0M$850K
Total$9.0M$3.55M
Stage-weighted says $3.55M, or 118% of target. It looks like a beat. Now split the same quarter by source:

- Carry-over: over the last four quarters, 20% of day-one pipeline value dated in the quarter closed won inside it. 20% x $9.0M = $1.8M. - In-quarter: deals created and closed inside the same quarter averaged $900K over the last four quarters. - Pull-forward: $250K of next quarter's deals could close early at a 20% discount. $250K x 80% = $200K.

Total: $1.8M + $900K + $200K = $2.9M, or 97% of target.

The two numbers differ for two reasons. Stage close rates count every deal that eventually closes, including the ones that slip into next quarter, so they overstate what lands now. They also leave out in-quarter deals entirely. The stage-weighted number is right only when those two errors happen to cancel. The split also tells you what to do. The plan is $100K short. $900K of it does not exist yet, so pipeline generation this month matters. And $200K borrows from next quarter, which starts $250K lighter and gives away $50K in discount.

Show it as a range. If carry-over conversion has run between 15% and 25% in past quarters, carry-over is $1.35M to $2.25M, and the quarter is $2.45M to $3.35M. A board trusts a low, expected and high case more than a single number.

Which forecast method should you use?

Use the method that fits your data and motion, and know how each one fails. Most teams get the best read by running two methods side by side and investigating where they disagree.

MethodHow it worksWorks whenFails when
Stage-weightedEach deal's amount x the historical close rate of its stage, summedStages have strict entry and exit criteria and there is one sales motionStages are judged by the rep; one set of weights covers new business, expansion, renewal, enterprise and SMB; stage rates count deals that close next quarter
Historical conversionThe share of day-one pipeline that closed in past quarters, plus usual in-quarter creationPricing, buyers and the sales team are stable from quarter to quarterThe market shifts: a new competitor cuts deal size, buyers delay decisions, territories change
Rep commit roll-upReps call commit and best case; managers roll up and adjustLate in the quarter, on a few large deals the reps know wellOptimism, sandbagging, and close dates that keep moving; quality varies by manager
AI and machine learningModels trained on your deal history and daily changes in stage, amount and close dateYou have a couple of hundred closed-won deals or more and at least a year of historyYou close a handful of deals a month, or the model cannot trace a number back to the deals behind it
Pete's view on stage weights is blunt. They work if every stage has strict entry and exit criteria. When stages are subjective, you are applying an objective weight to a subjective call, and you will miss. The second failure is using one weight for every deal, when new business, expansion and renewals, or enterprise and SMB, convert differently.

Machine learning helps most because it reads how deals move. A deal in Proposal is useful. A deal that moved into Proposal yesterday is more useful. ORM snapshots the pipeline every day for that reason. If you want a range instead of one number, compare Monte Carlo and weighted pipeline forecasting.

Why pipeline forecasting matters for revenue teams

Only 7% of sales teams reach forecast accuracy of 90% or more, and the median is 70% to 79% (Gartner). A pipeline forecast takes out guesswork and puts math in its place. When every deal is weighted by evidence rather than rep hope, leaders can act on the number. ORM targets 95% accuracy with no manual changes, from day 1 to day 90 of the quarter.

A pipeline forecast also shows problems early. If your weighted pipeline drops sharply in a single week, the quarter is at risk long before it shows up as a miss. Track your pipeline coverage ratio next to it, so you always know if there is enough pipeline to hit target.

How to improve pipeline forecasting

- Build stage-specific conversion rates from your own CRM data. Generic benchmarks do not reflect your sales motion. Pull 12 months of closed-won and closed-lost data, calculate the actual conversion rate at each pipeline stage, and use those rates as your probability weights. - Adjust for deal age. Deals that sit too long in a stage slip more. Ebsta found that when the Qualification stage runs 50% longer than average, a deal is 120% more likely to slip (Ebsta, 2024). Apply a decay factor to stale deals rather than weighting them at full stage probability. - Separate new business, expansion and renewals. These motions convert at different rates with different timelines. Renewals have less uncertainty: you usually know the amount and the date, and they tend to close within about 30 days of the renewal date. New business timing follows the last stage change. One model that blends them will be wrong about each. - Model seasonality. Q4 is usually the largest quarter, and the third month of a quarter is always bigger than the first across ORM's customers. Without it, you cannot tell mid-quarter whether you are ahead or behind. - Validate with bottom-up and top-down checks. Run your pipeline forecast alongside a top-down forecast based on historical bookings trends. If the two diverge significantly, investigate why.

Common mistakes with pipeline forecasting

Using the same probability for every deal in a stage. A $500K enterprise deal in negotiation with an active champion is not the same as a $50K deal in negotiation with no executive sponsor. Layer in deal-level signals like multi-threading and executive engagement to differentiate within stages. Not accounting for pipeline creation timing. Deals created this week rarely close this quarter. Your pipeline forecast should weight deals by their creation date relative to your average sales cycle length. Late-stage pipe created late in the quarter deserves extra scrutiny. Trusting close dates. The best slip signal is a rep moving the close date. A deal that slips from one quarter to the next is less likely to close, even in commit. The earliest signal is no signal at all: no stage change, no amount change, no notes. Waiting for clean data. Every company thinks its CRM data is uniquely bad. It is not, and it does not have to stop you. If the data is consistently imperfect, a model can learn the pattern and still forecast well. Predictive data matters more than perfect data.

Frequently Asked Questions

How does pipeline forecasting differ from sales forecasting?

A pipeline forecast projects revenue from the deals in your pipeline, their stages and their history. A sales forecast is the wider job of calling the number. It can add rep judgment, manager overlays, renewals and top-down trends. The pipeline forecast is the part you can repeat and check. It is only complete when it also counts deals that do not exist yet.

What methods do teams use to forecast pipeline?

Four are common. Stage-weighted multiplies each deal by its stage close rate. Historical conversion applies the share of day-one pipeline that closed in past quarters. Rep commit rolls up what reps and managers call. AI and machine learning models learn from deal history and daily changes. Most teams run two side by side and investigate when they disagree.

What are the steps to build a pipeline forecast?

Snapshot the pipeline on day one of the quarter. Measure what share of that dated pipeline closed in past quarters. Estimate in-quarter creation from history and seasonality. List the deals you could pull forward and what they would cost. Add the three. Show a low, expected and high case. Then update weekly and compare the forecast with actuals.

How much pipeline coverage do you need?

3 to 5x is the standard. Across ORM customers most sit near 3.5x, and the real range runs from 1.4x to 5x. Treat coverage as an input, never as the forecast. A team can carry 4x and still miss if the pipeline is stale, sits in the wrong segment or depends on a few large deals.

How often should pipeline forecasts be updated?

At least weekly. Digital Bloom reports that teams who track pipeline velocity each week reach 87% forecast accuracy, against 52% for teams that track it now and then. ORM snapshots the pipeline every day. The change in a deal, such as a stage move, a new amount or a pushed close date, often says more than where the deal sits.

Can you forecast pipeline in Salesforce or your CRM?

Yes. Salesforce, HubSpot and most CRMs roll up deal amounts by stage and forecast category. That gives you a stage-weighted or rep commit forecast. What a CRM report rarely does is model in-quarter deals, seasonality or how deals are moving. Many teams keep the CRM roll-up and add a statistical forecast as a second, independent view.

Put these metrics to work

ORM builds custom revenue forecast models that turn concepts like pipeline forecasting into prescriptive action for your team.

Schedule a Demo