What is the difference between capacity-based and pipeline-based forecasting?
Capacity forecasting builds the number from the people who sell. Pipeline forecasting builds it from the deals they are working. Capacity asks what this team should produce. Pipeline asks what these specific opportunities will produce.A capacity model multiplies productive reps by quota and by expected attainment. A pipeline model takes open opportunities, applies conversion and timing, and rolls them into a period. The two run on completely separate data, which is precisely why running both is worth the effort.
They also have different useful ranges. Pipeline is sharp inside one sales cycle and blind beyond it. Capacity is vague inside the quarter and the only workable method past it.
How do you build a capacity forecast?
Count the reps who can actually sell in each month, discount the ones still ramping, then apply quota and realistic attainment.The build order matters more than the formula:
1. Start with productive headcount by month, not headcount on the org chart. 2. Apply a ramp curve to every recent hire based on your own time to first closed deal. 3. Subtract expected attrition, spread across the year rather than assumed away. 4. Multiply by quota per rep for the segment. 5. Apply expected attainment, taken from the last several quarters of actual attainment distribution rather than from 100 percent.
Step five is where most models go wrong. Teams multiply thirty reps by a $1M quota and forecast $30M, when their own last four quarters show median attainment well below plan and a long tail of reps landing far under quota. Capacity at plan is not a forecast. Capacity at observed attainment is.
Step two is the second largest error. A rep who starts in the first week of the quarter contributes close to nothing to that quarter when the sales cycle runs longer than a month, and counting them at full quota inflates the plan by their entire number.
When should you use each method?
Use pipeline inside one sales cycle, capacity beyond it, and both at the boundary.| Dimension | Capacity-based | Pipeline-based |
|---|---|---|
| Core inputs | Reps, ramp, quota, attainment | Open deals, conversion, timing |
| Useful horizon | Two to eight quarters out | Current quarter and the next |
| Best for | Hiring plans, annual targets, territory design | Commit calls, in-quarter action |
| Blind to | Whether pipeline exists | Anything past the sales cycle |
| Reacts to | Headcount and ramp changes | Deal movement |
| Failure mode | Assumes plan attainment | Trusts close dates that slip |
The current quarter is the opposite. Once the pipeline is created, the deals contain more information than the headcount does, and a capacity model that says the team should deliver $8M is not evidence against a pipeline that only supports $5M.
What does pipeline coverage tell you that neither model does alone?
It tells you whether the capacity plan has any pipeline behind it. Coverage compares open pipeline against the goal, which makes it the reconciliation point between the two methods.The standard band is 3x to 5x. Across ORM's customer base the range runs wider, with some teams at 1.4x and others at 5x, and most landing near 3.5x. Where your business sits inside that range depends on win rate and cycle length, so the number to target is your own historical requirement rather than a rule of thumb borrowed from someone else's funnel.
Coverage on its own is still a weak instrument. A team can hold 4x and miss badly when the pipeline is concentrated in a few deals, aged, sitting in the wrong segment, or owned by reps who have not closed at that size before. That is the argument in why the 3x pipeline coverage rule is wrong, and it applies with more force here, because a capacity plan validated by a coverage ratio inherits every flaw in the coverage number. Read pipeline coverage as the check that the two forecasts are compatible, not as evidence that either is right.
What should you do when the two forecasts disagree?
Read the direction of the gap, because each direction points at a different fix.Capacity above pipeline means the team is staffed for a number the demand engine is not feeding. Coaching deals will not close that gap. The response is pipeline generation, and it has to start early enough for the deals to age into the period, which means the decision belongs at the start of the quarter and not in week ten.
Pipeline above capacity means the forecast depends on a small group of reps beating quota. That is not automatically bad, and it is always concentration risk. Check how much of the pipeline sits with reps who have cleared that number before, and check whether the deals are large relative to your closed-won average.
The gap is the useful output. Splitting the difference destroys it.
How do you combine both into one operating forecast?
Let capacity set the target and let pipeline set the call.Capacity determines what the business is built to do over a year, which drives hiring, quota setting, and the annual plan. Pipeline determines what happens in the next ninety days, which drives the commit. When you publish one number, publish the pipeline-derived figure for the current period and the capacity-derived figure for periods beyond the sales cycle, with the coverage ratio in between showing whether the handoff holds.
Then track both against actuals. Capacity models drift as ramp and attainment change, and pipeline models drift as win rates and cycle lengths move. Reviewing each against what actually happened is what keeps a sales forecast tied to the business rather than to the plan it was built from a year ago.
Frequently Asked Questions
What is capacity-based sales forecasting?
Capacity-based forecasting builds revenue from selling resources rather than from deals. You count productive reps by month, apply a ramp curve to anyone hired recently, multiply by quota, then apply expected attainment to get a revenue figure. It answers what the team can produce at normal performance, which makes it the right method for planning periods where no pipeline exists yet.
When is capacity forecasting better than pipeline forecasting?
Capacity is better beyond the length of your sales cycle. If deals take five months to close, nothing in the pipeline today tells you much about the quarter starting nine months from now, so annual planning, hiring plans, and territory design all run on capacity. Inside the current quarter, pipeline carries far more information and capacity should not override it.
What should you do when the capacity and pipeline forecasts disagree?
Treat the gap as a diagnosis rather than an averaging problem. Capacity above pipeline means a pipeline generation shortfall, so the fix is demand and prospecting, not deal coaching. Pipeline above capacity means the number depends on a few reps outperforming, which is concentration risk. Blending the two into a midpoint hides both conclusions.
How does ramp time affect a capacity forecast?
Ramp is the largest error source in most capacity models because teams count a rep as full capacity on their start date. A rep hired in month one of the quarter contributes almost nothing to that quarter when the sales cycle is longer than a month. Model each hire against a ramp curve based on your own time to first deal and time to full quota, and forecast the delayed contribution rather than the headcount.
Is pipeline coverage part of capacity forecasting or pipeline forecasting?
It is the bridge between them. Coverage compares the pipeline that exists against the goal capacity implies, so it is the check that tells you whether the two models can both be true. Standard coverage sits in the 3x to 5x band, and a team whose coverage sits far below it is being told that the capacity plan has no pipeline behind it.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo