Customer Expansion Playbook: Plays, Evidence, Owners

Most expansion playbooks are written for the person who commissioned them. They describe a philosophy: land, adopt, prove value, expand. They list triggers in the abstract. They end with a slide about aligning customer success and sales. Then a CSM with sixty accounts opens the document on Monday morning and cannot find the answer to the only question they have, which is what to do with the account in front of them.

This article is the other kind. It is a playbook a CS or expansion leader can hand to a team this week: a small set of named plays, the evidence each play needs before anyone picks up the phone, who owns the conversation at each step, and the weekly rhythm that keeps it from decaying into a spreadsheet nobody opens. It assumes you already know what expansion revenue is and why it matters. If you are still settling the difference between the two motions, start with cross-sell vs upsell, because the two run on different evidence and a playbook that blends them fails in a predictable way.

Why expansion needs a written playbook now

The pressure on existing accounts is not a hunch. In a Gartner survey of 243 CSOs and senior sales leaders run in late 2024, 73% said they were prioritizing growth from existing customers for 2025, and 57% ranked account retention and growth as a top-three priority. The same release names the obstacle: a customer value gap, where suppliers struggle to turn the promise of the value proposition into value the customer actually realizes.

The economics point the same way. Benchmarkit's 2025 SaaS performance metrics put the median expansion CAC ratio at $1.00 of sales and marketing spend per $1.00 of expansion ARR, against $2.00 for new customer ARR. Expansion was a median 40% of new ARR, and around 67% for companies above $100M ARR. Median net revenue retention sat at 101%, which means the median company is barely growing its installed base at all once churn is netted out.

SaaS Capital's 2025 retention benchmarks describe the link to growth as a strong and exponential correlation: companies with net retention of at least 110% grew faster than the population median, and companies below 100% grew slower. The prize is real and cheaper to win than new logos. What most teams lack is a written answer to what to do, account by account, with what proof.

The five plays

A playbook with twenty plays gets used for none of them. Five covers almost every expansion conversation a mid-market team has. Each account on the book gets assigned to exactly one play per quarter. If it fits two, pick the one with the stronger evidence and park the other.

Play 5 is in the playbook on purpose. A playbook that only knows how to say "sell more" will push a commercial conversation into an account that is quietly deciding whether to renew. Gartner's value gap is exactly this account. Naming it as a play gives the CSM permission to hold the commercial motion and gives the manager a way to see how much of the book is sitting there.

The evidence standard: what counts before anyone calls

This is the section most published playbooks skip. Look at the expansion guides that rank for this topic and the triggers they list are almost entirely internal: license utilization near 90%, a jump in daily active users, adoption of an advanced feature, a green health score. Those are good signals for Play 1. They say nothing about Plays 2, 3 and 4, because the reason to buy a second product usually lives outside your product, in the customer's business.

So the playbook sets one rule for every play: no expansion call without two pieces of evidence, at least one of them dated in the last 90 days, and each with a source someone else can check. The rule does three jobs. It stops reps from calling on a hunch. It gives the manager something to inspect. And it turns the call opener into a fact about the customer instead of a fact about your roadmap.

Internal evidence

• Usage against the contract: seats, volume, API calls, storage, relative to the limit.
• Feature adoption, especially features that are gated behind a higher tier or a second product.
• Support tickets that describe a problem your other product solves.
• What the champion said in the last QBR, written down with the date.

External evidence

• Hiring: open roles in the function your second product serves, or a new leader in that function.
• Growth events: a funding round, an acquisition, a new region or facility, a new product line.
• Pressure events: a regulatory change in their industry, a security incident, a public commitment with a deadline.
• Stack changes: a competitor being removed, a migration announced, a vendor contract ending.

External evidence is the part teams under-collect, because it takes research per account and nobody's calendar has room for sixty accounts of reading. We covered the catalog of these moments in trigger events in sales. The playbook's job is narrower: decide which of those events counts as evidence for which play, and require it.

The mapping matters more than the list. A new CISO is evidence for a security product and noise for a billing product. A funding round is evidence for capacity and weak evidence for consolidation. Write the mapping down per product, once, so two reps looking at the same account reach the same conclusion. This is also the work PitchSmart does: it reads each account on your list against the products you sell and returns the buying signals that point to a specific product, each with the source attached, so the evidence step stops depending on who had a free afternoon.

Who owns each conversation

Ownership is where expansion programs most often stall. The CSM knows the account and does not want to be the one asking for money. The account manager wants the number and does not know the account. Both assume the other one is on it.

Gainsight's own description of the split is a useful default. In its comparison of customer success and account management, expansion signals such as a usage spike or a new department onboarding route from the CSM to the account manager through a shared pipeline view, and the account manager takes the renewal conversation 90 days before contract end while the CSM keeps QBRs and health tracking. That works for Plays 1 and 2. It breaks for Play 3, because the buyer for a second product is often a person neither the CSM nor the account manager has met.

Write ownership into the playbook as four roles per account, not one:

1. Detects: whoever first logs the evidence. Usually the CSM for internal evidence, and a research process for external evidence.
2. Qualifies: the account manager or expansion rep checks the evidence against the standard above and assigns the play.
3. Opens: the person who makes first contact with the buyer. For Play 3 this is the rep, with a warm introduction from the CSM where the champion knows the new buyer.
4. Protects: the CSM, who has a veto if the account is actually in Play 5. The veto must be used with a written reason, or it becomes a way to avoid the conversation forever.

The account card: one page per account per quarter

Every account in scope gets one card. Not a full account plan: a card. If you want the long version for your top ten accounts, our account planning template covers it. The card is for the other fifty.

• Play: one of the five.
• Product to lead with: one product, named. If the answer is "the platform", the play is not qualified yet.
• Evidence 1 and 2: each with a source link and a date.
• Buyer: the person who owns the problem the evidence describes, with their title. Often not your champion.
• Opener: one sentence that states the evidence and asks a question about it. No product in the first sentence.
• Owner roles: detects, qualifies, opens, protects, with names.
• Next step and date.

The "product to lead with" field is where multi-product teams lose the most time. Choosing that product from evidence, rather than from comp plan or habit, is the subject of our piece on picking the second product in land and expand.

A worked card

Take a hypothetical logistics software company selling a routing product, a driver-safety product and an analytics add-on. One mid-market customer runs routing in two regions.

• Play: 3, second product.
• Product: driver safety.
• Evidence 1: the customer posted a Fleet Safety Manager role three weeks ago (their careers page, dated).
• Evidence 2: their state regulator announced new commercial driver reporting rules taking effect next year (regulator press release, dated).
• Buyer: VP Operations, not the routing champion in dispatch.
• Opener: "Saw you are hiring a fleet safety manager ahead of the new reporting rules. How are you planning to produce those reports today?"
• Protect: CSM confirms routing adoption is healthy in both regions. No veto.

The weekly rhythm that keeps it alive

Playbooks die in week three, when the cards stop being updated. The fix is a short, fixed rhythm with an inspection step that a manager can run in under half an hour.

The monthly inspection is where the playbook earns its keep. Three numbers tell you whether it is working:

• Share of cards with two sourced pieces of evidence. If this is low, the research step is the bottleneck, not the reps.
• Conversion to a qualified opportunity, by play. If Play 3 converts far below Play 1, the evidence for second products is weaker than it looks, or the buyer is wrong.
• Share of the book in Play 5. If it grows quarter over quarter, the expansion number is about to meet the renewal number, and it will lose.

Where expansion playbooks usually break

• Every account is in Play 1. The team only has internal evidence, so it only finds capacity deals. Second-product revenue stays flat because nobody is collecting the external evidence it needs.
• Evidence without dates. "They are growing" is not evidence. A dated hiring post or press release is. Undated evidence cannot be checked for staleness, so it never expires.
• The champion is always the buyer. Your champion bought the first product. The second product usually solves someone else's problem. If every Play 3 card lists the same contact as the first deal, the buyer field is being filled from the CRM, not from the evidence.
• Openers about you. An opener that starts with a product launch is a newsletter. An opener that starts with the customer's own hiring post or regulatory deadline is a conversation.
• No one owns protect. The first sign is a renewal lost at an account that had an open expansion opportunity.

Starting on Monday

Do not roll this out to the whole book. Pick twenty accounts, split roughly between healthy and flat. Assign each a play and fill the card, including the two pieces of evidence. Where you cannot find external evidence for an account within fifteen minutes, write that down: it tells you how much research capacity the full rollout needs.

Run the weekly rhythm for six weeks, then look at the three inspection numbers. You will know which plays convert, which evidence actually predicts a conversation, and whether your team's bottleneck is finding reasons to call or making the call. That answer decides whether you need more reps, more research, or a different product to lead with. The playbook's job is to make that answer visible, account by account, with the source attached.