Renewal Forecast Truth Serum Playbook 2026

The account crossing into the 120-day renewal window in Salesforce fires the play — 120 because a gap found at 30 days is a post-mortem with extra steps. The payload carries both versions of the truth side by side: the CSM's forecast category straight from the CRM, and the behavioral record — the engagement score and its trend, whether the executive users are still showing up, and the support ticket load. Exec activity is the tell most forecasts miss: end users often keep working right up until the decision-maker, who checked out a quarter ago, signs the cancellation.

Accoil holds the behavioral side — engagement scored 0–100 from the events you already send to Segment, PostHog, Amplitude or Mixpanel — and the gap computation is a simple contradiction check: accounts forecast "commit" or "safe" whose engagement has declined meaningfully over the trailing 60 days. Out comes the working set for the review:

• Gap-account list — every commit-but-declining account, no exceptions for whose book it's in.
• Gap size — how far the score fell and from what baseline; a slide from 85 to 70 outranks a wobble from 45 to 40.
• Days to renewal — the same gap at 110 days is a save plan, at 40 days it's an escalation.

Run the check the other direction too: accounts forecast "at risk" with strong, rising engagement are sandbagged renewals hiding expansion revenue — the gap cuts both ways.

The split is deliberately narrow: does the forecast disagree with the usage data? Accounts where both agree — green and engaged, red and fading — pass through untouched; the CSM called it, the data concurs, no meeting required. Only the contradictions spend anyone's time. That restraint is what keeps the pipeline review from becoming another everything-review, and it's why CSMs tolerate the play instead of gaming it.

The gap list posts to the pipeline-review channel 24 hours before the meeting, each account carrying its evidence inline: forecast category, score trend, exec activity, support load, gap size, days to renewal. Nobody compiles a deck; nobody gets ambushed live. The 24-hour head start matters — it gives the CSM time to bring context the data can't see, which is exactly what the meeting is for.

In the review, the CS leader walks the gap list and re-grades each account with everyone looking at the same evidence. Two rules make it work:

• Check the conversation record before accepting either story. Pull the last two calls in Gong and compare what the customer actually said against what the CRM recorded. "We're evaluating options next quarter" has a way of becoming "renewal on track" by the time it reaches a field.
• RevOps logs every override with a reason code. If the CSM holds the commit despite the decline, fine — "champion confirmed budget on 6/12" is an auditable claim. Next quarter, overrides get scored against outcomes, and the reason codes tell you which kinds of judgment beat the data.

Field report: track forecast accuracy per CSM per quarter — but not to punish. The systematically-optimistic CSM is usually carrying too many accounts to actually know their book; that pattern is a capacity signal, not a character flaw, and treating it as one turns your best retention lever into a staffing fix instead of a blame ritual.

Every re-grade, override and outcome lands in one quarterly report: forecast accuracy overall and per CSM, surprise-churn ARR that reached the board (the target is zero), gaps caught and saved versus caught and lost. Within two quarters the compounding effect shows up — CSMs start checking the engagement trend before setting the category, because they know the data gets a vote. The play's endgame is to make itself boring: fewer gaps flagged, because the first draft of the forecast already told the truth.