Forecast snapshots: why the number keeps moving

On Monday the forecast call is $4.2 million. On Thursday, the CFO asks why the quarter now looks like $3.6 million, and nobody can say. The CRM shows the pipeline as it is today, and Monday’s version is gone. Someone rebuilds it from an exported spreadsheet, and half the meeting goes on whether the export was taken before or after the changes.

The forecast is where revenue operations answers to the board, and the CRM was built to show the present, not the past.

What are forecast snapshots?

Forecast snapshots are weekly copies of every open deal and every forecast call, taken at the same moment each week and written to a warehouse once, never edited. Each call is compared with what closed, and each week with the one before, deal by deal, so the forecast review can see what moved and why.

Why the number changes after the call

1. The CRM only knows today. Close dates, amounts and stages are overwritten, and the history it keeps is hard to report on.
2. Snapshots are taken by hand. Someone exports the pipeline when they remember, on a different day each week.
3. The call isn’t captured. The pipeline is saved, but each rep’s commit and each manager’s adjustment aren’t, so nobody can measure accuracy.
4. History gets corrected. A snapshot edited later can’t show how accurate the forecast was, which was the point of keeping it.
5. Movement is reported as a total. A forecast down $600,000 tells nobody which deals slipped, shrank or were lost.

What it costs

A forecast nobody can reconstruct gets defended instead of discussed. The review spends its time on what the number was, and none on why it moved.

It also hides who forecasts well. Without the call and the outcome side by side, every rep’s forecast looks the same in hindsight.

What to fix first

1. Take the snapshot at a fixed time. Pick a moment after forecast calls are due and before the review, and keep it every week.
2. Capture the call with the pipeline. Save each rep’s commit and best case, and each manager’s adjustment.
3. Write each snapshot once. Put corrections in the next snapshot, never in an old one.
4. Compare calls with outcomes. At the end of each period, measure accuracy by rep and by manager.
5. Report movement deal by deal. Show what was pushed, pulled in, shrunk, grown or lost between two weeks.

The guide to building a forecast snapshot sync has the prompts for each step.

Where it fits

Snapshots are only as good as the pipeline they copy, which is why CRM data hygiene comes first. When a deal changes after a call, the change should come from the rep, which conversation intelligence can prompt but shouldn’t decide.

For every handoff revenue operations covers, see getting started with RevOps.