Workflows that source expansion
Plan limits, new-team usage, add-on patterns and support asks – expansion that shows up in usage first, checked against the customers who already expanded.
Second-Department Expansion Playbook 2026
Your best customers run the product in more than one department. This play checks every account against that benchmark each week, confirms the second team is real before anyone calls it a gap, and puts the right move on the account in your CRM: a champion-led rollout, a sponsor conversation, a guided session – or no move, with the reason noted.
Monday-Morning Account Triage Playbook 2026
Your best customers show you what good looks like. Every Monday, this play compares each account in a segment with that benchmark, ranks what each gap is worth, caps the list at what your team can run, and puts the week's moves on the account records in your CRM: close a gap, grow the upside, or leave it alone with the reason noted.
Expansion Signal to PQL Handoff Playbook 2026
Your customers who upgraded showed you what ready looks like before they asked. This play checks every account against them each week, confirms the records before anyone calls it ready, and puts the move on the account in your CRM: an upgrade conversation for your AE, an in-app prompt your team chose to automate – or no move, with the reason noted.
The Leave-It-Alone Playbook 2026
When the weekly check finds a gap worth a conversation, this play looks for a reason to wait first – a fresh purchase or renewal, a budget or org change, an open blocker, a departed champion. If the records show one, the reason goes on the CRM record with a date to look again, so the conversation happens when it can land.
Seat & Feature-Adoption Upsell Playbook 2026
Accounts show what they'd pay more for by how they use what they have. This play compares each account in a segment every week with the customers who bought your add-on or added seats, checks the records before calling it a gap, and puts one move on the account in your CRM: an add-on deal, a seat true-up – 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 Eight-Week Review Playbook 2026
Eight weeks after a move, this play brings the account back up and asks what changed. It keeps activity, progress and business result apart, checks what else played a part, and puts the verdict on the CRM record: it worked, change it, stop it, or give it more time – with the reason noted. Each quarter, what worked goes back into the benchmark.
Build the Benchmark from Your Best Customers Playbook 2026
Every other play compares accounts with a benchmark. This is how to build it: pull the customers who renewed flat or up, shrank or left, strike the unfair matches, compare usage and revenue by customer type and stage, label thin segments low confidence, and have your CS lead approve what good looks like – then check it every quarter.
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.
Support-to-Expansion Goldmine Playbook 2026
When a customer asks support for a higher limit or a missing feature, they have written down what they want to buy. This play catches the tagged ticket, compares the account with your successful customers, and puts the move on the account in your CRM with the ticket attached: an upgrade conversation, an add-on or seats offer – or no move, with the ask passed to product.
AI Agent Account Context Playbook 2026
Walk into customer calls current, with the account on one page instead of five tabs. When a move lands on an account or a customer meeting is booked, a one-page brief goes on the CRM record: the gap against your successful customers, the recommended move and its evidence, and what's still open. Your team reads it, decides and sends.
Churned-Account Win-Back Playbook 2026
Some former customers left over one reason your team has since fixed. This play checks them each quarter, and whenever a fix or new plan ships: did they look like your successful customers before they left, and does the reason still stand? The answer lands on the CRM record as a drafted note for the AE, or no move, with the reason and a recheck date.
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.
Docs Intent Signals Playbook 2026
A team reading your API reference is telling you what it wants to build. This play turns docs reads from identified accounts into evidence the weekly check reads beside usage against your benchmark, and puts the move on the account in your CRM: an expansion note for the AE, a help offer for the job they're reading about – 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.