How to build a sales forecast from a scenario
Build a sales forecast from pipeline data, weight each deal with explicit assumptions, and show which open deals still need review.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What a scenario-based sales forecast is
A sales forecast estimates how much business may close in a stated period. A scenario makes the assumptions explicit, including which deals qualify, which dates count, and what probability you assign to open deals at each stage. A row-by-row forecast lets you trace the total back to individual opportunities. Keep observed bookings, estimated open business, and deals you cannot yet assess visible as separate parts of the result.
A weighted pipeline is the sum of eligible open deal amounts after each amount has been multiplied by its probability of closing. The total depends on the assumptions and source data you use. A deal without a usable close date or currency can still affect the business, so keep it visible as unresolved exposure, meaning business whose contribution you cannot calculate yet. Use the forecast as a planning draft for review by the sales operations lead or the finance owner responsible for the decision.
What it does for the business
- Focus deal reviews on the decisions that matterA forecast row shows which sales could change the quarter's outlook and what you still need to verify. If a large opportunity hinges on a buyer's procurement date, the manager can ask the owner to confirm that date and agree on a follow-up.
- Plan staffing and spending around specific dependenciesGive finance and delivery teams a view of what's booked, what may close, and what could move into the next period. When a contractor start or onboarding slot depends on a pending deal, the team can agree on a trigger for committing the capacity.
- Find gaps in the way deals are reportedGroup unresolved rows by the information needed to include them. If several renewals are missing close dates after a handoff, the sales operations lead can clarify who updates those dates and check the next export.
- Learn what changed between forecast and actualsForecast variance is the difference between the forecast and what actually closed for the same period and measure. When you keep the source snapshot and assumptions, you can distinguish deals that slipped from changes in deal size or flaws in the probabilities you used.
How to build a scenario-based sales forecast, step by step
Set the period and choose the source snapshot
Every number in a forecast belongs to a specific snapshot and reporting window.
What to do
- Identify the decision the forecast needs to support, such as scheduling implementations for next quarter. Record the person who will review it and the date by which they need to decide.
- Write down the snapshot date, the first and last dates of the forecast period, and the reporting time zone. Decide which close date to use for an open deal and which date counts for a booked deal.
- Choose one reporting currency for the comparison and record the exact source files, export dates, and filters. Make sure the report uses pipeline data for the intended team and period.
- Confirm the amount you will forecast, such as the initial contract value. Use the same definition for deals you compare and document how renewals and amendments enter the report.
Why
The snapshot tells you what was known at the time, and the window tells you which deals may close in the period. Keeping both lets you trace changes such as a deal slipping into the next quarter.
Validate the deals and separate closed outcomes
Every excluded row needs a reason a reviewer can trace.
What to do
- Compare deal IDs across the source rows. Resolve repeated IDs before counting amounts, and keep the original values and row references so someone can follow each decision.
- Check that amounts are finite and nonnegative, that dates can be read, and that stages and currencies have recognized values. Check that supplied probabilities represent values from zero to one after converting any percentage notation.
- Separate open opportunities from closed-won and closed-lost deals. Use the relevant actual close date for closed outcomes and the supplied expected close date for open deals.
- Record missing, invalid, and conflicting values separately. If you cannot tell which of two close dates to use for a deal, record the conflict and the source rows you need to resolve it.
Why
A duplicate can count the same contract twice. A blank amount can hide a real opportunity, while an observed zero may be a valid amount from the source. Checking and labeling these cases before weighting also helps you distinguish deals that are clearly outside the period from deals whose date is unknown.
Weight eligible open deals and record the assumptions
A weighted amount is only as defensible as the probability attached to it.
What to do
- Write down the stage probability for each stage covered by the scenario. Use supplied probabilities and keep their source alongside the assumption. Leave a deal unweighted if its stage has no usable probability.
- Multiply each eligible open deal amount by its stage probability. Keep the full deal amount, probability, weighted value, and inclusion reason on the row. Record a deal owner's commitment separately when the owner provides one.
- Add weighted values only across deals that share the currency and window. Show booked revenue separately and make sure a booked deal appears only once in the reported amounts.
- For scenario planning, build conservative, central, and upside views only when you have stated assumptions for each. If the upside depends on a signed order arriving before the cutoff, record that condition next to the affected deal.
- List unresolved exposure by reason, including any known amounts in their stated currency. When a value or currency is missing, retain the deal and the issue so a reviewer can see the exposure without a guessed total.
Why
Keeping the full amount alongside the weighted value shows where the forecast depends on a single large contract. Recording the assumptions lets managers see which changes in probability or timing account for the difference between scenarios.
Reconcile the totals against the source
A reviewer should be able to rebuild the total from the rows.
What to do
- Rerun the calculation from the same snapshot and confirm that the included rows reproduce the published totals. Check the rule for rounding, especially if the report shows fewer decimal places than the calculation uses.
- Match each source deal to an included, excluded, or unresolved record. Check that any part of the source outside the review scope is accounted for in the coverage note.
- Review deals around the cutoff, duplicate IDs, missing probabilities, conflicting currencies, and unexpected zeros. Trace a few of the largest contributions all the way back to the source and the assumption.
- Check that booked revenue and weighted open business are labeled consistently in both the row-level detail and the summary. Ask the reviewer to record corrections and remaining gaps.
Why
A total can look reasonable even when a deal is in the wrong month or appears on two rows. Reconciliation tests both the arithmetic and the scope. A period with no eligible deals means something different from a period you could not assess because the source was missing or invalid. Make that difference clear in the review.
Hand off the forecast for a decision
A forecast is ready for discussion when the reader knows which assumptions can change it.
What to do
- State the period, snapshot date, and currency in the summary. Present bookings and weighted open business separately, with a short explanation of unresolved exposure and where to find the affected rows.
- Call out assumptions that matter to the decision at hand. For a hiring decision tied to a contract, note the buyer milestone that must be verified and the internal owner responsible for checking it.
- Give the sales or finance reviewer the detailed rows and calculation assumptions. If gaps limit the draft, explain which decisions can still be made with what is known and what needs another source.
- Keep the reviewed snapshot so the next forecast can explain what changed. Record changes in stage, amount, close date, or assumptions when those changes drive the result.
Why
Someone outside sales should be able to see the basis for a staffing or budget decision and find the individual deals that move the forecast. A clear handoff also helps the next reviewer distinguish a change in the business from a change in reporting scope.
Common mistakes
- Mixing reporting periodsAn opportunity expected to close after the cutoff belongs in a later window, even if the sales team is working on it now.
- Copying probabilities from an old exportUse the probabilities supplied for the current scenario, since stages or assumptions may have changed.
- Adding amounts across currenciesKeep different currencies separate unless a defined conversion policy and evidence support a common basis.
- Treating blank fields as zerosKeep an unverified amount or date visible so the deal can be resolved and reassessed.
- Confusing projected sales with cash receiptsIf the decision depends on when cash arrives, check billing and collection terms separately.
What a good result looks like
- The snapshot date, reporting dates, time zone, currency, and deal amount definition are stated.
- Every deal has a stable ID, traceable source, and documented treatment.
- A reviewer can reproduce weighted totals using the included rows and supplied probabilities.
- Booked revenue is visible on its own, and unresolved exposure has a reason for each affected deal.
- Every scenario names the assumptions that drive it and identifies the deals affected by changes.
And then what? Using the result
- Assign missing close dates, amounts, and currency checks to the relevant deal owners before the next forecast review.
- Use confirmed timing to reserve implementation capacity and set conditions for committing additional resources.
- Compare scenarios with finance before scheduling spending tied to open deals.
- Record the actual close dates and amounts when the period ends, then compare them with the forecast snapshot.
- Use recurring forecast variance to decide which stage definitions or supplied assumptions need review.
When to run it
- Before a monthly or quarterly planning reviewGive sales and finance a common snapshot for discussing how much business may close and which deals need attention.
- After a material deal slipsUpdate the close-date assumption and check which other opportunities remain in the current window. Show what moved into the next period.
- Before assigning delivery capacityIdentify which onboarding or delivery commitments depend on contracts still in progress and agree when to confirm those assignments.
- After a pipeline cleanupUse the new export to assess how corrected stages, duplicate IDs, or close dates change the outlook. Keep the prior run so the difference can be explained.
Questions people ask
How do you build a sales forecast from pipeline data?
Choose the source snapshot, forecast window, and currency, then separate booked deals from open opportunities and weight eligible open amounts using supplied probabilities. Document the assumptions, account for each source deal, and show unresolved rows alongside the result.
How do you calculate a weighted pipeline?
Multiply each eligible open deal amount by its supplied probability of closing, then sum the products for that currency and window. Keep the underlying amounts and probabilities so the total can be reproduced.
When should you use conservative, central, and upside sales scenarios?
Use all three when you have explicit assumptions for each and a decision that depends on their differences. If you have one set of probabilities and timing assumptions, report one labeled weighted scenario.
What should you do with deals that have missing forecast data?
Track them as unresolved exposure and give each row a reason for staying out of the weighted calculation. Keep any usable source details so the reviewer can see what needs to be resolved.
What is the difference between booked revenue and weighted pipeline?
Booked revenue reflects observed closed-won business under your reporting definition, while weighted pipeline estimates what eligible open opportunities might add. Accounting recognition and cash collection each follow their own timing.
Can the 10folds forecast use multiple currencies?
A 10folds run uses one currency and one date window. Rows with unknown currency are shown as unresolved exposure so they can be checked against the source.
More jobs in Sales & outbound
Forecast sales from a scenario, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac