Multi-Year Deal Decay Watch 2026
Multi-year contracts remove the renewal forcing function — accounts die in year 2 and everyone finds out in year 3. This play rebuilds the checkpoint: every contract anniversary re-baselines engagement against the day they signed, and the delta routes the account — decaying books get a mid-term value review that re-sells the original business case, compounding books get an expansion review.
A three-year deal is three chances to be ignored. The multi-year contract you celebrated removed the one forcing function post-sale teams reliably respond to — the renewal date — and the discount bought silence, not loyalty. So the account slides in year 2, nobody has a reason to look, and everyone finds out in year 3 when the "we've actually been evaluating alternatives" call comes. This play rebuilds the checkpoint the contract deleted: every anniversary fires a re-baseline of engagement against the day they signed — score delta, active seats versus purchased, features adopted versus what was sold — and that delta, not the distant renewal date, decides whether the account gets a mid-term value review or an expansion conversation.
Measure it on the score delta versus signing at each anniversary, the percentage of multi-year accounts actually reviewed in year 2, and the final-renewal rate on multi-year deals — the number this play exists to protect.
How it works7 steps
01SignalMake the anniversary a trigger, not a date
The signal is mechanical: a contract anniversary hits on any deal with 12+ months still to run, straight from the close date in Salesforce. It fires carrying the commercial frame — months to final renewal, contract ARR — plus the two numbers the whole play turns on: the engagement score today and the score the account had at signing. Don't wait for a human to remember; the entire failure mode this play fixes is that nobody's calendar says "check on the three-year deal." Anniversary 1 matters most: decay found there is fixable, decay found at anniversary 2 is triage.
02ScoreRe-baseline against the day they signed
Comparing this quarter to last quarter hides slow decay — down 3% a quarter looks like noise and compounds into a dead account. The honest comparison is against signing day, and Accoil emits it as three fields:
- Score delta vs signing — the headline. Flat-to-up is a healthy deal; down 15+ points is a renewal risk hiding behind a signed contract.
- Active vs purchased seats — the shelfware gauge procurement will read at final renewal whether you do or not.
- Features adopted vs sold — pull the adoption promises from the original close plan and score against those. The gap between what was sold and what got adopted is the exact text of the year-3 objection, available two years early.
03DecisionSplit the book: decaying or compounding?
One rule, read off the re-baseline: score delta down 15+ points from signing, or active seats under 60% of purchased, means decaying; delta flat-or-up with seats holding means compounding. Write the thresholds into the play and tune them annually — the point is that no multi-year account passes an anniversary unclassified. Either way a Slack alert goes out; the only question is which conversation it books.
04ActionAlert the owner with the delta, not a task
Decaying accounts post to #cs-renewals tagging the owner, and the alert carries the whole comparison: score at signing versus today, seat utilization, the adoption gaps against the close plan, months until the real renewal. The framing matters — this is not "schedule a check-in," it's "this account is 22 points below the day they signed and renews in 19 months." Time is the asset here; the alert should make clear how much of it is left.
05Human stepCSM re-sells the original business case
The mid-term value review is not a QBR ritual — no slide recapping ticket volumes. It's a re-selling of the original business case to an audience that may have partially changed, with usage evidence on the table: here's what you bought this to do, here's what's actually adopted, here's the gap, here's the plan to close it.
- Dig out the original close plan and open with its promises. Nothing focuses a mid-term conversation like the customer's own success criteria.
- Bring the delta, name it plainly, and leave with owners and dates on an adoption plan — the review's output is a plan, not a meeting summary.
- Re-run the re-baseline 90 days later. If the delta hasn't moved, escalate to an exec sponsor touch; a decaying multi-year account that shrugs off a value review is your earliest possible look at a year-3 loss.
06ActionCompounding accounts earn the growth conversation
A multi-year account whose score is up on signing with seats near capacity isn't "fine, skip it" — it's your warmest expansion pipeline, pre-committed through the term. Flag it to the account team in Slack with the same evidence pack pointed the other way: usage growth since signing, teams pressing seat limits, adopted features that imply the next tier. The anniversary is the natural moment to grow a deal mid-term; an expansion signed at anniversary 1 also resets the relationship clock the contract had stopped.
07OutcomeCatch it in year 2, count it in year 3
The play's output at each anniversary is a classified book: every multi-year account marked decaying or compounding, with a review or an expansion motion attached — no account left unexamined because "the renewal is ages away." The proof arrives on a lag: track the final-renewal rate of multi-year deals that got anniversary reviews against the ones signed before this play existed. That before-and-after is the cleanest case you'll ever make that the quiet middle of a contract is where renewals are actually won.
How Accoil fits
Accoil is the memory in this play: it holds the engagement score from signing day and re-baselines against it on demand, turning "how's the account doing?" into a delta with a date on it — score movement, seat utilization, adoption against the close plan. Salesforce supplies the forcing function the contract removed, and Slack puts the delta in front of the owner. The play needs almost no new machinery; it needs the signing-day baseline nobody else kept.
Swap the delivery freely — anniversaries tracked in HubSpot or Pipedrive instead of Salesforce, alerts in Teams instead of Slack — and the watch runs the same, because Accoil pushes the same re-baseline signal wherever the work happens.
Accoil is the scoring layer in this playbook — it works on the product events you already collect, and shows your accounts scored in under 48 hours. Free to start, no credit card.
Explore Accoil →Keep reading
Renewal Forecast Truth Serum Playbook 2026
When an account enters the 120-day forecast window, compare what the CSM called it against what the usage data says: accounts forecast commit or safe while engagement declines get auto-flagged onto the pipeline review agenda, the CS leader re-grades with the evidence on the table, and every override gets logged with a reason code — so forecast accuracy becomes a measured number that improves.
Customer Layoffs Counter-Play 2026
When a customer announces layoffs your ARR already shrank — you just haven't been told. This play hears the news first: Clay's enrichment catches the layoff, Accoil rechecks seats and engagement against it, and the AM shows up with a right-size-and-retain offer before the customer asks — while the surviving team gets re-onboarded and the forecast gets the truth.
The Shelfware Confession Playbook 2026
When seat utilization sits under 60% for 60 days, take it to the customer before procurement finds it: build a utilization truth doc — what's used, what's dormant, what activation would take — and have the AM present both paths honestly, a reactivation plan or a clean right-size quote. Right-sized accounts renew with trust intact and expand later, because the next quote is credible.
Every playbook, one download
All 31 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.