Sales Forecasting Techniques: 9 Methods and When Each One Works

Sales forecasting methods are the ways a team turns data into an estimate of future revenue. The big four are rep judgment, historical run rate, weighted pipeline, and a statistical or machine-learning model. Most B2B SaaS forecasts rest on one of them. Each needs different data, fits a different time frame, and breaks in a known place. Updated October 2026: one table for all nine methods, sourced accuracy figures, a worked example and a guide to choosing.

The mistake I see most often is not picking the wrong method. It is picking one and treating its output as the whole forecast, when it only covers part of the quarter.

The choice matters more than it used to, because the conditions every technique assumes have moved. B2B new-logo win rates have fallen to 19% (Ebsta/Pavilion, 2025), and sales cycles have lengthened 22% since 2022 (Optifai, 2026). A technique calibrated on conversion rates from two years ago is drifting before the quarter starts, which is why the failure mode below matters more than the method you name.

This page compares the methods. If you want the bigger picture first, from what sales forecasting is to the sales forecasting models behind each method, start with our guide. If you already know the options and need to pick one, the forecast fit test for choosing a method walks through it with a worked example.

All 9 sales forecasting methods in one table

Nine methods cover almost every B2B forecast. The table shows what each one needs, what it suits, how far ahead it works, and where it breaks. These nine fall into a few families. Harvard Business Review's 1971 guide still tops Google for this search. It sorted forecasting techniques into qualitative methods, time series projection and causal models. Sales teams added a fourth family that works from the open pipeline. Rows 1 and 8 are judgment and planning, row 2 is time series, rows 3 to 5 read the pipeline, and rows 6, 7 and 9 are causal models. For the trade-offs between the first two families, see qualitative vs. quantitative forecasting.

What accuracy can you expect from each method?

No neutral study reports accuracy by method. Some comparison pages print a plus-or-minus range for each method with no source behind it. Here is what has actually been measured:

- The median is 70% to 79%. Only 7% of sales teams reach 90% accuracy or better (Gartner). - One company in five gets within 10%. Forrester found that just 21% of companies land that close to the actual result. - Weekly tracking beats method choice. Teams that track pipeline velocity each week report 87% forecast accuracy. Teams that track it now and then report 52% (Digital Bloom, 2025). - Close dates are soft. 36% of deals slipped past their close date in 2025, down from 44% in 2024 (Ebsta, 2025). - Hand-built forecasts land near 90%. Across ORM customers, accuracy on new and expansion revenue usually reaches about 90%, with heavy manual work. ORM targets 95% with no manual changes, from day 1 to day 90.

So judge a method on two things: does it re-fit when conditions change, and how early in the quarter does it become reliable? A number that is right in week 13 tells you what happened. It does not help you act.

When Does Qualitative Forecasting Work?

Qualitative forecasting works when you have too little history to model and enough deal context that an experienced rep's read beats any formula. This is the commit-and-best-case method: reps and managers judge each open deal from the conversations they are having, then roll those calls up into a number.

It is the right tool for a young company with a handful of deals. It also suits large enterprise deals, where the context around one deal matters more than any pattern. A rep who has heard the economic buyer say "this has to be signed before our fiscal close" holds information no model has yet.

Where it breaks is bias and scale. Sellers carry happy ears, managers sandbag to beat the number, and none of it is traceable. The most reliable slip signal we see is a rep moving a close date, and judgment forecasts are where that quiet push hides. Rep calls also fall apart past a few dozen deals.

Judgment still has a job in a mature forecast. The RevOps person who owns the number should talk to sales leaders every day, and always before the weekly forecast call, to test the model's assumptions. Some teams keep the rep roll-up beside a statistical forecast on purpose. That gives leaders two views: what the field believes will happen, and what the data says is likely.

When Is Time-Series Forecasting the Right Tool?

Time-series forecasting works when revenue is stable enough that the past predicts the future, and it fails the moment the market moves. It projects history forward: last quarter's run rate, the same quarter a year ago, the seasonal shape of the business.

Seasonality is where it earns its keep. Across our customers, Q4 is usually the largest quarter, then Q2, Q3 and Q1. Inside a quarter, the third month is always the largest and the first month the smallest. At ORM we break each quarter into 13 weekly weights. One real set runs 0.70, 0.59, 0.63, 0.81, 0.96, 0.73, 0.60, 1.44, 0.84, 0.68, 1.27, 1.47 and 2.27.

Here is what that does to a pace check (illustrative). The 13 weights add up to 12.99, and the first six add up to 4.42. So a team with a $2.0M quarter is on pace at about $680,000 after week six (4.42 / 12.99 x $2.0M). A flat 6/13 split says $923,000. Without the weights, an on-pace team looks $243,000 behind.

The problem is the assumption underneath. A run-rate model believes tomorrow looks like yesterday, and that belief is the most common way a forecast misses. Market shifts break sales forecasts built on old assumptions: a new competitor shrinks your average deal size, or rising rates slow buyers and stretch every cycle. The model keeps projecting the old shape while the ground moves.

What Does Weighted-Pipeline Forecasting Actually Tell You?

Weighted-pipeline forecasting multiplies each open deal by its stage probability and sums the result, which produces a useful coverage read and a poor final forecast. A deal at 60% stage probability worth $100,000 contributes $60,000 to the number. Do that across the pipeline and you get a tidy, defensible-looking total.

The trouble is what the weights hide. Stage probabilities are past averages applied to deals that are nothing like average. Weighted pipeline says nothing about how long a deal has sat untouched or how often its close date has moved. It also cannot tell when the amount is one the buyer will never sign. We routinely see pipelines with an $80,000 average deal size that close won at $40,000. Weight that pipeline and you forecast about twice the revenue you will book.

Timing is the other gap. Across ORM customers, only about 20% of the pipeline value dated to close in the quarter on day one closes in that quarter. The other 80% does not land in that quarter. More than 10% of a typical pipeline has not been touched in 12 months.

This is also where teams confuse coverage with a forecast. Pipeline coverage is a useful input and a poor conclusion. A team can carry 4x coverage and still miss badly when the pipeline is old or rests on a few large deals. The 3x pipeline coverage rule is wrong because a ratio tells you the size of the pile, not the shape of the quarter.

Why do stage weights fail?

Stage weights fail when stage entry is loose and when one set of weights covers every kind of deal. They work only where each stage has strict entry and exit criteria.

The first problem is judgment. When a business is lax about those criteria, the stage becomes whatever each rep decides. Put a fixed number on a subjective stage and you get surprises at the end of the quarter.

The second is sameness. Most companies apply one set of weights to every deal. The weights should differ by deal type, by motion and by product:

They rarely do differ, which is why a single weighted number can look healthy and still miss. More on this in why stage-weighted forecasting misses.

How Does Machine-Learning Close-Curve Forecasting Work?

Machine-learning close-curve forecasting groups open deals that behave alike, then predicts a curve for when each group will close. This is the method we build at ORM, and it holds up across a full quarter.

Instead of one flat stage weight, the model learns a close curve for each group. Our curves run from 1 to 80 weeks. Most of the expectation lands before week 12, and very few groups carry any past week 52. We pair that with a 12-month aging rule. A deal with no change in stage, close date or amount for a year stops counting on its stated close date. The model treats a two-week-old deal and a fourteen-month-old deal as different bets, even when a rep has both marked to close this quarter.

The richest input is the change in the data, not the data itself. ORM snapshots each customer's pipeline every day, so it sees what changed and when. A deal in Proposal is useful to know. Knowing it moved into Proposal yesterday is more useful. The same goes for amount: did it go up or down, by how much, and how late in the cycle?

The cost is setup and volume. We want a couple of hundred closed-won deals at minimum, and thousands are better. We want at least a year of history to measure seasonality, and two to three years is better. A model takes 4 to 6 weeks to train on that history. In return, you get a forecast that updates itself as the quarter moves, instead of a number someone rebuilds by hand every Monday.

Messy CRM data is rarely the blocker teams expect. Every team thinks its data is uniquely bad. Everyone's data is imperfect. If it is messy in consistent ways, the model learns the pattern and predicts around it.

What are the other sales forecasting techniques you will see?

Five more methods show up on most lists. Each is a variant of the families above, with its own data needs and failure point.

Length of sales cycle

This method estimates when a deal closes from how long deals of its type usually take. It is simple and better than a rep's guess at a date. It breaks when one average cycle stands in for deals that follow very different paths. New business timing tracks the last stage change. Renewals close within about 30 days either side of the renewal date.

Lead-driven

Lead-driven forecasts turn lead volume into pipeline, then into revenue, using past conversion rates. The math is leads x lead-to-win rate x average deal size. It works for high-volume motions with short cycles. It breaks when the lead mix shifts, because conversion rates differ widely by source.

Many drivers at once (regression)

Regression fits revenue or win odds to several drivers at once, such as deal size, source, segment and rep. It can beat a single stage weight when definitions are clean and history is deep. It breaks when the meaning of a field changes partway through your history.

Based on usage or consumption

Consumption models need drivers, not extrapolation. In a seat-based business you can usually forecast from contracts, seats, price, renewals and expansion. In a usage or consumption model, revenue depends on customer behavior. Identify what predicts consumption, such as historical usage, customer growth, seasonality, transaction volume or product adoption. Forecast those drivers, then translate the result into revenue.

Top-down capacity plans

A capacity forecast starts from people: how many reps you have, their quotas, and how productive each one is at their stage of ramp. It is the right frame for annual plans and hiring. ORM usually builds three-year capacity models, with years one and two as the planning window. It breaks on blended averages, such as one company-wide ramp curve, when real ramp differs by role and region. Compare the two views in capacity-based vs. pipeline-based forecasting.

How do you choose a sales forecasting method?

Choose by deal volume, history, motion and horizon, in that order. A method your data cannot feed will lose to a simpler one it can.

1. Deal volume. If you close a handful of deals a month, there is too little volume for a model. Forecast deal by deal, with direct conversations and deal reviews. One company we spoke with had three reps, about $5M in ARR and a founder in every deal. Rep judgment was the right call there. 2. History. A year of data lets you measure seasonality. Two to three years is better. Without it, run rate and regression have little to learn from. 3. Motion. Forecast renewals apart from new business and expansion. Renewals carry far less doubt: you know the amount and roughly when it closes. Usage revenue needs its own driver model. 4. Horizon. Use pipeline methods for this quarter. Use run rate and capacity for next year and for hiring plans. 5. Pace of change. If your market is shifting, favor a method that re-fits on recent behavior. A static method drifts no matter how clever it is.

The short version of this test lives in our glossary entry on how to choose a sales forecasting method.

What is the formula for predicting sales?

There is no single formula. Each method has its own, and the best quarter forecast adds up three sources of revenue.

- Weighted pipeline: the sum of each deal's amount x its stage weight. - Run rate: same quarter last year x (1 + growth rate). For example, $1.8M x 1.10 = $1.98M. - Lead-driven: leads x lead-to-win rate x average deal size. For example, 400 leads x 3% x $40,000 = $480,000. - Capacity: sum of each rep's quota x expected attainment. For example, 10 fully ramped reps x $800,000 x 75% = $6.0M a year. - Split quarter: deals in the pipeline that will close, plus deals created and closed inside the quarter, plus deals pulled in from next quarter.

Worked example: one quarter, two ways to call it (illustrative)

A team has a $2.0M new-business target and $6.0M of open pipeline dated to close this quarter. That is 3.0x coverage.

Weighted pipeline. Stage weights turn the $6.0M into $2.1M. The team looks 5% ahead of target. Decomposed forecast.

1. Open deals likely to close: about 20% of the $6.0M, or $1.2M, using ORM's typical day-one close rate. 2. Deals created and closed inside the quarter: $0.6M, from the average of the last four quarters. 3. Pulled-forward deals: $0.1M, with a discount attached.

That adds up to $1.9M, or 95% of target. The decomposed view says the team is $100,000 short on day one, while the weighted view says it is ahead. On day one, the team still has 13 weeks to close that gap.

So which method is the most accurate?

The most accurate forecast is a model that splits the quarter into its real sources of revenue and updates itself as conditions change. No single method wins on its own. A hand-built forecast can reach about 90% on new and expansion revenue, but it takes heavy manual work and goes stale when the market moves. Our model targets 95% without manual changes, from day 1 to day 90 of the quarter. For a realistic bar to aim at, see what sales forecast accuracy you should expect.

Accuracy comes from splitting the quarter. We break it into three sources of revenue instead of one big pile:

1. Carry-over deals already in the pipeline on day one that are expected to close this quarter. 2. In-quarter deals that do not exist yet but will be created, qualified, and closed inside the quarter. 3. Pull-forward 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 rest. They study the deals already in the CRM and never forecast how much will be created and closed inside the same quarter.

A forecast should also be a range, not one number. Show a low case, an on-target case and an upper bound, and ask for the floor, the ceiling and the confidence interval. A board trusts a forecast that is consistent, traceable and framed as a range. Monte Carlo forecasting is one common way to build that range from deal-level odds.

Getting the number right in the final week does not help anyone, because by then the quarter has already happened. The value is knowing the likely shape of the quarter on day one, early enough to act.

What are the steps to build a sales forecast?

Seven steps, in this order:

1. Separate revenue types. Forecast new and expansion revenue apart from renewals, which carry far less uncertainty. 2. Clear out stale pipeline. ORM applies a 12-month rule for most customers: no change in stage, close date or amount for a year means the deal is stale. 3. Choose a technique per motion. Enterprise and commercial motions rarely fit one model. 4. Weight by what closes. Deals usually close for less than the amount entered in the CRM. 5. Apply weekly seasonality. Revenue arrives unevenly across the 13 weeks of a quarter, heavily in the last three. 6. Add in-quarter and pull-forward revenue. Visible pipeline is only one of three sources. 7. Track changes weekly and re-fit. A model built on last year's assumptions misses when the market moves.

What ORM does instead

At ORM a machine learning model groups each deal, and for each group we predict a curve for how long those deals take to close. A curve does something a single close date cannot. It spreads the expectation over time instead of betting on one point, which makes weekly forecasting practical. Combined with the 13-week seasonality weights, it gives a weekly number a team can manage against.

Two things matter more than the method you pick.

Responsiveness. The most common reason a forecast misses is that something in the business or market changed and the model was built on old assumptions. A method that cannot re-fit on recent behavior will drift no matter how clever it is. Timing of accuracy. Accuracy that only arrives in the final week describes a quarter. It does not forecast it. ORM targets 95% from day 1 through day 90, so the forecast is useful while there is still time to act on it.

For the underlying mechanics, see how long deals take to close by group, why stage-weighted forecasting misses and the 13-week quarter. If you run a pipeline review each week, bring the decomposed number as well as the weighted one.