Seat & Feature-Adoption Upsell Playbook 2026

The signal fires when usage crosses an add-on-relevant threshold — a default worth tuning per product line. What it watches:

• Feature-by-feature usage — which capabilities the account leans on, and how hard, not just a blended score.
• Power users per feature — three people deep in reporting is an add-on conversation; one person dabbling isn't.
• Seat growth trend — active users climbing toward or past the purchased count.
• Plan & entitlements — what they're on, so the same behaviour reads differently on Starter than on Enterprise.

This is a different trigger from the expansion-PQL play deliberately: that one catches accounts ready for a sales conversation; this one catches specific products the account is already halfway to buying.

The scoring step joins the two halves — what they do and what they pay for — and emits the case:

• Entitlement gaps — where usage exceeds or presses against the plan: seats, volume limits, features used via workaround.
• Best-fit add-on — the one product whose job the account is already doing the hard way. One, not a menu.
• Who'd champion it — the named power users whose week the add-on improves. They're the demo audience and the internal sellers.
• Value evidence — the specific numbers that make the pitch concrete: reports run, hours in the feature, workaround frequency.

Add-on gaps and seat gaps are different sales. An add-on is a genuine purchase decision — someone new gets convinced. A seat true-up is a fact that needs an invoice — usage already exceeded the contract, and the conversation is about making the paperwork match reality gracefully. Sorting them here keeps AMs from pitching true-ups (which oversells) and invoicing add-ons (which undersells).

The add-on lane opens a CRM opportunity automatically: the add-on named, the amount sized from plan and usage, the champion contacts attached, and the value evidence in the description. The AM should be able to run the entire motion from the opportunity record without asking anyone what the account does — that's the bar for "evidence attached."

The AM books the power users — not procurement — and runs the add-on against the account's own live workflow: their reports, their data, the workaround they currently do by hand. The pitch is subtraction, not addition: "here's the part of your Tuesday this deletes." Close with the champions carrying it to the buyer, which they will, because the demo was about their week.

Seat gaps go to the next QBR (or renewal touch) as a straightforward account-health item: "you bought 25 seats; 34 people use it — let's fix the contract." Framed as stewardship with usage data on the table, true-ups close quietly and preserve trust; discovered by the customer at renewal as a surprise bill, they poison the relationship. Speed matters less than framing here — batch them into existing touchpoints rather than making them events.

Close the loop separately per motion: attach rate and cycle time on add-on opportunities, win rate and tone (any pushback logged) on true-ups. If flagged add-ons don't attach, the threshold is too eager or the value evidence too thin. If true-ups get argued, they're being framed as sales. And route the strongest signal of all back to product and pricing: the gaps accounts keep having are the packaging you should probably sell on purpose.