Forecasting playbook · Operator diary · 2026

Sales forecast for your first 10 B2B SaaS deals

Q: Why does standard forecasting fail at fewer than 10 deals?

Statistical variance. When your pipeline is 8 deals at $20K ACV, one $20K deal slipping swings attainment by 30-50%. That is not forecasting error — it is the math of small samples. Standard forecast methods (3-bucket, % attainment vs. target, weighted pipeline) all assume enough deals for the law of large numbers to smooth variance. At N<10, the variance dominates. The 2-bucket method acknowledges this and forecasts what you can predict (this month / not) rather than what you cannot (precise dollar amounts).

Q: How do I forecast accuracy when I have no history?

You do not, for the first 10-15 deals. Forecast accuracy requires history. The honest move is to track the 2-bucket forecast weekly and capture the misses with reasons. Over 6 months, you have enough miss data to calibrate. Until then, accept that you will be wrong frequently and focus on the leading indicators — they tell you more than the forecast itself at this scale.

Q: Should I forecast a quarter or a month?

Month, at pre-revenue. Quarter is too long when your deal cycle is 30-60 days — by the time you can compare forecast to actual, the quarter is over and you cannot adjust. Monthly forecasts let you correct in-cycle. Graduate to quarterly forecasting when your cycle length stabilizes and you have 4+ closed deals per month consistently.

Q: What conversion rates should I use for pipeline weighting?

None, until you have your own data. CRMs ship with default stage probabilities (10% Discovery, 25% Demo, 50% Proposal, etc.) — those are guesses from someone else's data. Using them at pre-revenue produces a forecast that looks precise but is meaningless. Run the 2-bucket method (This Month / Not This Month) without probability weighting. Once you have 30+ closed deals, calculate your actual stage-to-close conversion rates from your data and start using those.

Q: What leading indicators should I track if not the forecast?

Four: (1) pipeline coverage = active pipeline $ / target (target 3-4x); (2) average cycle length (days from first call to close); (3) discovery → demo conversion rate; (4) demo → close conversion rate. Track weekly. Each one points at a specific upstream system that you can act on: low coverage → outbound; lengthening cycle → ICP or pricing; discovery→demo drop → list quality; demo→close drop → pricing or competition.

Q: When do I graduate to the standard 3-bucket forecast?

When you have 30+ closed deals and enough conversion data to build a deal scorer from your own history. Run both methods in parallel for 1-2 quarters. If the 3-bucket forecast produces tighter predictions (10%+ better) than the 2-bucket method, retire the 2-bucket. If it does not, you graduated too early — go back to 2 buckets for another 10 deals.

Q: How does this fit with the founder running discovery calls and pipeline review?

The forecast pulls data from the pipeline (see /pipeline-review-pre-revenue-no-crm). The pipeline pulls data from the discovery calls (see /discovery-call-no-bant-founders). The chain: discovery surfaces qualification data, pipeline review tracks deals against the data, forecast aggregates the pipeline. Break any link and the forecast is fiction.

Q: Where does this fit in the StackSwap Operator Playbook?

The full forecasting-and-pipeline-review skill covers the 9-component framework end-to-end: stage definitions with exit criteria, MEDDPICC-based deal scoring, forecast categories with accuracy targets, 60-minute pipeline review structure for teams, manager adjustment factors, slip detection rules, pipeline health KPIs, and forecast accuracy tracking. The 2-bucket version above is the pre-revenue cut. Graduate when you have 30+ closed deals or hire your first AE.

Standard B2B SaaS forecast methods (3-bucket commit/best/pipeline, % attainment vs. target, weighted pipeline math) all assume enough deals for the law of large numbers to smooth variance. At pre-revenue with 5-15 deals in flight, one $20K deal slipping swings attainment by 30-50%. That is not a forecasting failure — it is the math of small samples. The fix is to forecast what you can actually predict (dollars, this month vs. not) and track the leading indicators that warn you 4-6 weeks before the forecast confirms the problem.

Why small-N variance makes standard forecast math collapse

Standard B2B SaaS forecast methods all assume that the deal portfolio is large enough for individual deal variance to smooth out across the quarter. At 50+ active deals, one slipped $20K deal is 1-2% of pipeline — noise. At 8 active deals, the same slip is 12-15% — signal that the forecast missed. The methods produce the same output (a number) but the meaning is different: at 50 deals the number is a prediction; at 8 deals the number is one slip away from being wrong.

The implication is not that you should skip forecasting at pre-revenue. The implication is that you should forecast what you can actually predict (will this specific deal close this month) rather than what you cannot (precise quarterly dollar amount). The 2-bucket method below does exactly that — and it produces cleaner data than the 3-bucket method until you have enough deals for the middle bucket to mean anything.

The 5-step framework

Step 1 — Forecast in dollars, not in percentages

Standard SaaS forecasts run "% attainment" (Q1 hit 87% of target). That math collapses at N<10 deals. One $30K deal slipping from Q1 to Q2 swings attainment by 30-50% — not a forecasting error, just statistical variance. At pre-revenue, forecast the actual dollar amount you expect to close this month, not the percentage of a target. The target itself is also a guess — board targets at pre-revenue are aspirational, not calibrated. Run two numbers: This Month forecasted dollars + Quarter-to-date actual dollars. Compare quarter-to-date against the prior quarter, not against the aspirational target.

Operator tip: Aspirational targets are useful for runway planning. They are not useful for forecast accuracy because there is no comparison cohort. Run the forecast and the target in separate columns of the same spreadsheet; do not collapse them.

Step 2 — Use 2 buckets (This Month / Not This Month) — not 3

Standard B2B SaaS uses commit / best case / pipeline. At N<10 deals, "best case" is the same thing as "wishful thinking" — you do not have enough deals for the middle bucket to mean anything statistically. Run 2 buckets: This Month (deals you are confident close before month-end, paper in motion, EB committed) and Not This Month (everything else). The forecast equals the sum of This Month dollars. Track it weekly. When This Month drops, ask which specific deal slipped and why — and write the slip reason in the deal record.

Operator tip: The 2-bucket method also forces commitment. A deal labeled "This Month" is a promise to yourself. Track the misses honestly — over 6 months your hit rate on This Month tells you exactly how optimistic you are, and you can calibrate. The reps and founders who improve forecast accuracy fastest are the ones who track misses, not the ones who try to never miss.

Step 3 — Recognize that 1 logo swings the quarter — and plan accordingly

When your quarterly pipeline is 8 deals at $20K ACV, one $20K deal slipping or one $40K deal landing changes the quarter materially. This is not a forecasting failure — it is a statistical reality of small-N samples. The implication: do not over-engineer the forecast process to chase tighter accuracy. Instead, over-engineer the deal-progression process. A deal in Decision stage at $30K should have weekly written updates, dated next steps, and a champion you have talked to in the last 7 days. The forecast tightens by tightening the deals, not by adding more spreadsheet columns. At N<10, deal hygiene beats forecast math every time.

Operator tip: The single biggest leverage at this scale is preventing the slip, not predicting it. Spend the time you would spend on forecast modeling on the 2-3 deals that matter most this month — calls, multi-thread, removing internal blockers. Every saved deal is a 10-15% swing in the quarter.

Step 4 — Track 4 leading indicators, not just the forecast

The forecast is a lagging indicator. By the time it is wrong, you cannot fix it. Track 4 leading indicators that predict the forecast: (a) pipeline coverage — total active pipeline / target = ratio (target 3-4x); (b) cycle length — average days from first call to close (lengthening = pricing or qualification issue); (c) discovery → demo conversion rate (drops signal misfit ICP); (d) demo → close conversion rate (drops signal pricing or competitive issue). Watch these weekly. They warn you 4-6 weeks before the forecast confirms the problem.

Operator tip: Each leading indicator points at a specific upstream system. Pipeline coverage low? Outbound is broken. Cycle lengthening? ICP or pricing is broken. Discovery→demo dropping? List quality is broken. The leading indicators are your diagnostic kit — not just metrics.

Step 5 — Graduate to 3-bucket forecasting at N≥30 closed deals

When you have 30+ closed deals, you finally have enough conversion data to add the middle bucket. Standard graduation: Commit (75+ deal score, paper in motion, EB committed — target 95-105% attainment), Best Case (50-74 score, on track but not locked — target 40-60% close rate), Pipeline (25-49 score, active but unlikely this period — target 10-25% close rate). Build the deal scorer from your actual historical data (MEDDPICC completion + stage + activity + multi-thread + champion verification weighted by what predicts wins in your specific motion). The 3-bucket forecast graduates the 2-bucket method when there is enough data to support it — not before.

Operator tip: The graduation is gradual, not a single moment. Run both forecasts in parallel for 1-2 quarters. If the 3-bucket version produces predictions that are 10%+ tighter than the 2-bucket version, retire the 2-bucket. If it does not, you graduated too early — go back to 2 buckets for another 10 deals.

Three approaches considered

Approach	Structure	Pro case	Why it fails at small N
2-bucket forecast (This Month / Not This Month) + 4 leading indicators Chose this	Forecast = sum of dollars in This Month bucket. Track weekly. 4 leading indicators (pipeline coverage, cycle length, discovery→demo conversion, demo→close conversion). Graduate to 3-bucket at N≥30 closed deals.	Honest at small-N. Forces commitment ("This Month" is a promise to yourself). Leading indicators warn 4-6 weeks before forecast confirms problems. Graduation criteria is data-driven, not arbitrary.	Less granular than the 3-bucket method experienced reps are used to. Requires discipline to track the 4 leading indicators weekly. Loses fidelity above 50 active deals — graduate before then.
Standard 3-bucket forecast (commit / best case / pipeline) from day one	Commit, Best Case, Pipeline categories with default stage probabilities (10% / 25% / 50% / 75%).	Industry standard. Maps to what every sales leader expects. CRM-default support.	Built for 50+ deal portfolios. At N<10, "best case" is wishful thinking with a label. Default stage probabilities are someone else's data, not yours. Produces forecasts that miss by 30-50% and teach the team that the forecast does not matter.
No forecast — track only quarter-to-date actuals	Skip forecasting entirely. Track only $closed this month / this quarter.	Zero overhead. No false precision.	Loses forward visibility. Hiring decisions, budget commitments, and cash-flow planning need some forecast. The 2-bucket method is the minimum honest forecast — anything less is operating blind.

Common mistakes

Forecasting in % attainment at small N. One slip swings attainment by 30-50%. Forecast in dollars, not percentages. Compare quarter-to-quarter, not against aspirational targets.
Using CRM-default stage probabilities. Those are guesses from someone else's data. Producing a "weighted pipeline" with those weights is false precision. Run the 2-bucket method without probability weighting until you have your own data.
Over-engineering the forecast process before the deal process. At N<10, deal hygiene beats forecast math every time. Spend the time saving the 2-3 deals that matter most, not modeling the forecast.
Forecasting quarterly instead of monthly. Quarter is too long when your cycle is 30-60 days. Monthly forecasts let you correct in-cycle. Graduate to quarterly when cycle length stabilizes.
Tracking only the forecast (no leading indicators). The forecast is lagging. By the time it is wrong, you cannot fix it. The 4 leading indicators warn 4-6 weeks earlier.
Graduating to 3-bucket forecasting before you have data. "Best case" without 30+ closed deals is wishful thinking with a label. Run 2-bucket until conversion data exists, then graduate.

FAQ