Multi-Year Deal Decay Watch 2026
A multi-year deal takes the renewal date off the calendar for years. This play puts a check on every contract anniversary instead: it compares the account with customers who renewed, at the same contract month, and with its own first year, then puts one move on the account in your CRM – an expansion look, a value review, or no move until the next anniversary.
A multi-year customer with growing usage gives you a reason to explore expansion – they're committed, and the anniversary is a natural moment to grow the deal. If usage is drifting, starting in year two leaves more time to help than waiting until the last quarter of the term.
Nothing prompts anyone to look, because the renewal date is years away. This play puts a check on every contract anniversary, and one move on the account record: an expansion look, a value review, or no move until the next anniversary.
Measure it on mid-term expansion, the share of multi-year accounts checked at each anniversary, and the final-renewal rate on multi-year deals.
How it works10 steps
01SignalStart 30 days before each contract anniversary
A HubSpot workflow flags every multi-year account whose anniversary is 30 days out, with the months left to the final renewal, the contract ARR and the features sold at close.
Set No move and skip the rest if the final renewal is inside 90 days – that's the renewal play – or if a move from another play is still inside its review window.
02ScoreCompare with renewed customers at the same contract month
Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), renewed at the same or higher revenue at the end of a term, measured by months since their contract started. Annual renewers count. Aim for 20; with fewer, label it low confidence.
- Their usage by contract month: active users as a share of seats paid (active means used in three of the last four weeks), and the core action per active user per week, at months 12, 24 and 36.
- Their revenue: median ARR at renewal for those who renewed up.
- The pattern: the median and the lowest quarter (25th percentile) of each usage measure at each month. Your CS lead approves it.
Compare the account with the peers at its month, and with its own first full quarter after launch. Say a three-year account pays $48,000, sits above the peer median at month 12, and similar customers who renewed up pay $66,000: the $18,000 is a comparison, not a forecast. (The numbers are illustrative.)
Run it as a saved query in PostHog, Amplitude or Mixpanel, with each account's contract start loaded from the CRM. Under about a hundred accounts, do it by hand.
03ScoreCheck the records before calling it a gap
- Features adopted vs sold: the modules on the order form and the use cases in the close plan, against what's in use. It's the list a buyer reads at the final renewal, two years early.
- Records complete? A tracking change, an SSO migration or a new workspace can make usage look lower than it is.
- Sponsor & org changes: 90 days of CRM notes and tickets, plus any reorg or budget news. If the person who signed has left, run the champion play first.
04DecisionAsk first: is it compounding?
Default rule to tune: at or above the peer median on both usage measures, and up on its first year. Yes means an expansion look.
05ActionDraft an expansion look for a compounding account
The note below goes on the record. For extra seats or an add-on, work it through the seat-adoption play; for a plan upgrade, the upgrade handoff.
06DecisionThen: decaying, or on track?
Default rules to tune:
- Decaying: below the peers' lowest quarter on either usage measure, down 20% or more on its first year, or under half the features sold in use. Value review.
- On track: everything else, or a gap the records explain. No move.
The lowest-quarter line will flag some customers who go on to renew. Before it triggers value reviews, check it against later renewals: each quarter, count how many renewers and how many leavers crossed it.
07ActionDraft a value review that re-sells the business case
Not a QBR recap. The CSM opens with the customer's own goal from the close plan, shows what's adopted and what isn't, and leaves with an adoption plan with owners and dates. The audience may have changed since signing, so invite whoever owns the budget today.
08ActionLeave an on-track account alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to the next anniversary. Between anniversaries the account stays in the weekly check; the leave-it-alone play covers the decision.
09Human stepYour team decides and runs the move
The AM or CSM runs it as drafted, changes it, or passes, and owns every customer conversation. Before acting, record the success measure and the review date: usage back above the peers' lowest quarter is progress; a mid-term expansion, or the final renewal flat or up, is the result.
10OutcomeReview what changed, then sharpen the benchmark
Eight weeks on, record whether usage moved and what else played a part. If a decaying account hasn't moved, bring in an executive sponsor, change the move, or give it time. At the end of the term the renewal deal records the result. Each quarter, compare lanes with renewals: compounding accounts that didn't renew, or decaying ones that renewed untouched, mean the benchmark needs work.
Setup and templates
Sources: contract start, term, final renewal date, ARR and notes from the CRM; features sold, recorded by the account owner from the order form or close plan (no record? use the modules in the plan they bought); active users, seats, the core action and features in use from a saved query in PostHog, Amplitude or Mixpanel. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. PostHog can sync HubSpot or Salesforce into its data warehouse and join contract start in SQL. In Amplitude or Mixpanel, load contract start as an account property (Amplitude: the Salesforce integration or Group Identify API; Mixpanel: a warehouse connector). By hand: a monthly export of accounts with an anniversary in the next 30 days into one spreadsheet, one row per account.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Contract start | Date picker | CRM |
| Final renewal date | Date picker | CRM |
| Next anniversary | Date picker | CRM workflow from Contract start (in HubSpot, the Format data action needs Data Hub Professional), or the anniversary check |
| Features sold | Multiple checkboxes | Account owner, from the order form |
| Usage vs peers, same age | Number (% of benchmark median) | Anniversary check |
| Usage vs first year | Number (% change) | Anniversary check |
| Features adopted vs sold | Single-line text ("4 of 6") | Anniversary check |
| Anniversary lane | Dropdown select: Compounding · On track · Decaying | Anniversary check |
| Recommended move | Dropdown select: Expansion look · Value review · No move | Anniversary check |
| Move reason | Single-line text | Anniversary check |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Anniversary check, then account owner |
| Review result | Dropdown select: Expanded · Back on benchmark · Gap closing · No change · Stopped | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The anniversary flag is an annual schedule on Contract start, 30 days before the date. The list is a saved view: Next anniversary is less than 30 days from now, or Review date is this week or overdue. In HubSpot the review-date part is two filter groups: Review date is This week, or Review date is before Today. Each move creates a task for the owner, "Anniversary: [move]", with the draft in the body.
Expansion look (note on the record): [core action] at [x]% of peers at month [n] · up [y]% on its first year · [active users] active on [seats] seats · [features in use beyond the plan] · the ask: [seats, add-on or plan] from [date].
Value review invite (CSM to the budget owner):
Hi [name] – it's [n] years since [company] chose [product] to [goal from the close plan]. [Feature] is working well for [team]; [feature sold] hasn't taken off yet, and I have a couple of ideas. Thirty minutes in the next two weeks to go through it?
Value review brief: the original goal · features adopted vs sold · usage vs peers at the same age and vs its first year · who owns the budget today · the adoption plan with owners and dates.
No move: "On track at month [n] – [reason]. Recheck [next anniversary]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark from your renewed customers with your team, and you approve it. Each week we check the multi-year accounts in the agreed segment with an anniversary coming up, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive. On Pipedrive, the anniversary check fills Next anniversary, since Pipedrive formulas can't calculate dates. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Usage Bill-Shock Absorber Playbook 2026
A usage spike can be the best news an account sends you. This play catches it mid-cycle, compares it with how your customers who moved up a plan grew, and puts a drafted move on the account in your CRM before the invoice lands: a plan conversation, a note naming a runaway meter – or no move, with the reason noted.
Renewal-Risk Radar Playbook 2026
Renewals go best when the account already looks like your customers who renewed. From 90 days out, this play compares every renewing account with them each week – usage and revenue – checks the records, and puts one move on the account in your CRM: an expansion look, a value review, a save plan with the CSM – or no move, with the reason noted.
The Shelfware Confession Playbook 2026
Seats paid and seats in use drift apart. This play compares each account's seat use every week with customers its size that renewed at the same or higher revenue, checks the records before calling it a gap, and puts one move on the account in your CRM: a seat review with both paths, a reactivation plan, a right-size quote – or no move, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.