What Is Bottom-Up Forecasting?
Key Takeaways
- Bottom-up forecasting builds a total forecast from granular, operational-level inputs.
- It is generally more accurate than top-down for short-term operational planning.
- The quality of the forecast depends directly on the quality of the underlying data.
- It requires cross-functional input — sales, operations, and finance working together.
Building a forecast from the ground up
Bottom-up forecasting constructs a total revenue or cost forecast by aggregating granular, operational-level inputs. Rather than starting with a market size and working down, you start with individual products, customers, territories, or team members and build up. For revenue, this might mean summing the expected value of every deal in your sales pipeline, plus contracted recurring revenue from existing customers, plus an estimate of new business from outbound activity. The total emerges from real operational data rather than macro assumptions.
Why bottom-up is preferred for operational planning
Bottom-up forecasts are generally more accurate for short-term planning because they are grounded in what is actually happening in the business. Sales leaders know which deals are close to closing. Operations managers know what capacity they have. Finance can see which customers have payment history that suggests they will pay on time. This specificity is bottom-up's great advantage. The downside is that it requires more effort to compile and more cross-functional collaboration — you cannot build a credible bottom-up forecast from the finance function alone.
Common inputs and how to structure them
A typical bottom-up revenue forecast for an SME includes: existing contracted or recurring revenue (high certainty), committed new contracts signed but not yet started (high certainty), pipeline deals weighted by probability stage (medium certainty), and new business development activity assumptions (lower certainty). On the cost side, start with your fixed cost base — payroll, rent, software — then layer variable costs that scale with activity. This structure makes assumptions explicit and transparent, so you can update individual components as information changes without rebuilding the whole model.
Cross-validating with top-down
Once you have a bottom-up forecast, compare it to a top-down market-based estimate. If your bottom-up forecast implies a market share that seems either unrealistically high or surprisingly low, investigate why. Discrepancies often reveal either missing pipeline (the bottom-up is too conservative) or missing competitive context (the bottom-up is too optimistic because it fails to account for deals that will be lost to competitors). Using both methods as a cross-check produces more robust plans than relying on either approach in isolation.