How to forecast sales revenue (without overpromising or underestimating)
Forecasting is the difference between a business that hires confidently and one that surprises itself. The simplest forecast model that works for Indian SMBs.
Step 1: Define stage probabilities
Lead 5%, Qualified 20%, Proposal 40%, Negotiation 70%, Won 100%, Lost 0%. These are starting numbers — re-calibrate quarterly against actual close rates.
Step 2: Calculate weighted pipeline
For every active deal: deal value × stage probability. Sum across all deals = weighted pipeline value. This is your statistical revenue forecast.
Step 3: Add a confidence factor
For each deal, salesperson assigns 1-5 confidence based on customer engagement. Multiply: deal value × stage probability × (confidence/5). This adds human judgment without overruling the stage discipline.
Step 4: Forecast in 3 numbers: commit, best case, worst case
Commit = sum of confidence-5 deals only (what we PROMISE will close). Best case = full weighted pipeline (everything closes). Worst case = sum of confidence-4-and-5 deals × 0.7. Variance between these three tells you how predictable your sales cycle is.
Step 5: Re-forecast every Monday
Pipeline review weekly. Salesperson updates stages and confidence. Manager checks for deals stuck >7 days (stale = at risk). Forecast refreshes.
Step 6: Measure forecast accuracy quarterly
Actual revenue vs forecasted commit. Within ±10% = good. Above 10% off = either pipeline hygiene or stage probabilities need fixing. Don't blame salespeople — fix the system.
Frequently asked questions
How far out should I forecast?
Next month with high confidence. Next quarter with medium. Next year with broad ranges. Beyond a year is a planning exercise, not a forecast.
What if my sales cycle is longer than 90 days?
Use a longer forecasting window — 6 months — but break it into monthly buckets. Long-cycle deals need extra columns (champion confirmed, budget approved, contract sent) to track stage discipline.
Should the founder forecast or the salesperson?
Salesperson submits, manager reviews. Founder builds the model. Splitting these roles prevents over-promising AND prevents sandbagging.