Pipeline and forecast evidence

Give each field one job

Use stage for the buyer milestone reached, forecast category for the seller's expected contribution this period, and close date for the expected purchase timing. Define whether amount means ARR, total contract value, or another measure. For any probability, state which past deals and closing window it represents.

• Agree with Finance on annualized recurring value, bookings policy, recognized revenue, and cash definitions.
• Separate new business, expansion, unchanged renewal, one-time fees, and usage treatment.
• Use a named commercial owner and distinct buying initiatives to prevent double counting.
• Stage weights or category mappings are not automatically calibrated probabilities.

Use observable buyer evidence

Create a qualified opportunity for a real problem and evaluation intent. A signup, score, or first meeting alone does not establish a buying process. Keep a few stages with observable buyer progress rather than seller activity counts.

• Link existing evidence of the problem, evaluation milestone, material blocker, and next commitment.
• Separate progress from timing: a successful trial with procurement next quarter can retain its stage while the close date and category change.
• When the buying process ends, record the actual reason directly. Do not add a duplicate evidence packet or advance closure approval.
• A seller task date alone is not a buyer-supported next step.

Use SPICED to review the buying decision

SPICED is Winning by Design’s framework for situation, pain, impact, critical event, and decision. Use that customer context to investigate a forecast, with evidence already in the CRM or call notes. The review should identify a missing buyer fact or an action, rather than require a second qualification form.

Source: Winning by Design: SPICED framework

Define buyer milestones for each stage

Agree on what the buyer has done before a stage changes. These are starting definitions for a sales motion, not a mandatory CRM redesign. Keep forecast category and close date separate from stage.

Source: Salesforce Trailhead: forecasting process and buyer evidence

Make the forecast treatment explainable

Multiply deal value by the assumed win probability to calculate weighted pipeline. Then check whether the buyer can close inside the forecast period. Inspect the largest deals individually: one delayed purchase can remove much of the expected total.

• Record account and motion, amount and metric, stage evidence, category and timing evidence, uncertainty, next step, owner, and date.
• Save the original forecast and deal state before the next update.
• Explain changes through buyer facts, amount, timing, or assumptions rather than changing fields just to reach target.
• Keep large or exceptional opportunities explicit and count them once.

The deal is qualified, but it will not close this quarter

The buyer has completed the evaluation, but procurement cannot finish until next quarter. The opportunity can retain its qualified stage while its expected close date and current-quarter forecast contribution change.

Update the close date and forecast category to reflect the procurement timeline. Keep the deal in pipeline and remove it from the current-period forecast. Review it again if the buyer confirms an earlier signing path.

Source: HubSpot: forecast categories and weighted amounts

Use consistent groups to measure accuracy

Target attainment compares actual bookings with quota. Forecast error compares actual bookings with the estimate submitted earlier. Save the original deal list so losses, slips, and newly added deals can all be explained at period close.

• Measure submitted minus actual and absolute error at the same lead time, period, and financial metric.
• Review committed deals won within the period against the original committed cohort.
• Measure dates pushed beyond period end from the original snapshot; report lost deals separately.
• Investigate definitions and stale timing before adding more precision to a weighted total.

Run the review from changes since the last call

Start with the prior submitted estimate and the deals that explain the difference. Review a changed amount, buyer commitment, decision date, or blocker. Reuse the call note or CRM record supporting the change.

Choose a next action that resolves the uncertainty: confirm an approver, test a requirement, agree on a decision date, revise the amount, or move the deal out of the period. A broader coaching conversation can follow separately.

• Retain wins, losses, slips, downsizes, and newly added deals when explaining the period’s movement.
• Resolve routine opportunity closure through the lifecycle playbook; a forecast review does not add an approval gate.
• At period close, compare the saved call with actuals at the same lead time and financial scope.