The Expansion Score: Stop Re-Selling Your Champion

Forwarded to you? I am Heath. I build go-to-market systems and put AI to work in sales, the right way, then I write down exactly what I built, what broke, and what it moved. One story per week, receipts only. This one is about the growth that was already sitting inside your customers, in the teams next door.

The reflex: go back to the champion and ask for more seats

Every team with a renewal number reaches for the same expansion move. You have a happy champion, a team that already bought, and a target to hit. So you go back to the people you already sold and you ask for more seats.

I did exactly that. I ran expansion off the team we already owned, counted the seats they were adding, and called it growth. It was the easy read, and it was the wrong one. The seats in a team you already sold are the smallest part of the account. The growth was the departments next door, the ones using nothing, the whitespace no one had mapped.

Then the catch showed up. You cannot cross-sell a new team while the team you sold is going dark. An expansion score that ignores the health of the beachhead just points reps at accounts that will churn the moment they expand. Adding a second team to a dying first team is not net new revenue, it is churn with extra steps. The block was never ambition. It was that nobody had scored the whitespace and nobody had gated it on whether the account was healthy enough to hold the weight.

The CSM feels this as "renew the team, maybe nudge for a few seats." The AE feels it as "the champion who signed will sign again." The RevOps lead feels it as "usage is up, so the account is safe." Same reflex every time: measure the team you already sold, and never look at the rooms next door or check whether the first room is still lit.

The reframe: score the whitespace, gate on the beachhead

Expansion is not a seat count. It is a map of what a customer is not using yet, and a rule about when you are allowed to go get it. The move is not to score the headcount you already own. It is to score the untapped teams, and refuse to chase them off an account that is already going dark.

Expansion is not re-selling your champion. It is the untapped team next door, and only if the beachhead is not already going dark.

Same move, other seats. An AE stares at "the champion will sign again" and drills it down: which other business unit has never seen the product, and is the account healthy enough to carry a second sale. A marketer stares at "this logo is engaged" and drills it down: which segment inside the account is untapped, and is the intent real or is it one team about to leave. The loud number is never the thing you act on. The whitespace underneath it, gated on health, is.

How the best teams frame it

I am not the first person to argue that expansion lives in the whitespace, not the champion. The operators and analysts who have built this motion at scale mostly agree on where the leverage is, and it is not the seat count. It is the map and the gate.

SOURCE

Prolifiq, "White Space Analysis: A Practical Guide for B2B Revenue Teams"

What it argues. Whitespace analysis is a grid of the customer's business units and geographies against your product lines. You fill in what each unit already uses, and the empty cells are your growth. You chase account penetration, the gaps you have not captured, not the accounts you already saturated.

My take. Agree, and the grid is only half of it. A whitespace cell you fill off a dying beachhead is not growth, it is churn with extra steps. Map the gaps, then gate the map on the health of what you already sold.

SOURCE

McKinsey, "The net revenue retention advantage in B2B tech"

What it argues. Net revenue retention is the metric that separates the winners. Expansion inside the base drives more durable growth than new logos, and the teams that win instrument the existing account and expand it systematically instead of hoping the champion comes back.

My take. Extend. NRR is the scoreboard, not the play. The play is knowing which account to expand and which to fix first, and that is a gate, not an average. A book-wide NRR number hides the accounts that are one team away from churning.

SOURCE

Kyle Poyar / OpenView, "Your Guide to Product-Led Growth Benchmarks"

What it argues. Team-based products show land-and-expand net retention of 130 to 150 percent when adoption spreads seat by seat and team by team. The in-account growth, not the new logo, is where the best product-led companies actually win.

My take. Agree hard. The expansion lives in the product signal, active users over licensed seats. That number told me where the true-ups were, 122 and 175 percent of plan, before any human had noticed the account was over its skis.

Even a curator has to concede when the field agrees: nobody who has actually built this thinks the champion is the expansion. The whitespace and the gate is the moat.

The method: Solve, Stack, Split

SOLVE THE CRUX

What is the real problem, framed as work and not a headcount?

The problem is not "we need an expansion score." It is "expansion re-sells the champion and never checks whether the beachhead survives the ask." So the first work is mapping the whitespace, the teams using nothing, and weighting them over raw seat count. Then the load-bearing rule: if the team you already sold is Dormant or Ghost-Active, expansion caps and the account goes Fix-First. For the CSM that whitespace is the untapped department, for the AE the second business unit, for a RevOps lead the true-up the plan already earned.

STACK THE CONTEXT

What tech and signals turn raw usage into a call a human can make?

Not a shopping trip. Amplitude carries active users over licensed seats and the adoption tier of each beachhead. Salesforce carries the licensed seats, the ARR, and the renewal date each score is measured against. Claude scores the whitespace and grades it against the CSM calls. Deepline enriches the whitespace accounts and runs the expansion scoring. The score arrives with the beachhead health already attached, so a healthy account and a dying one never look the same.

SPLIT · CUT THE DRAG

What low-judgment work goes to the system?

Read the usage, pull the seats, score the whitespace, apply the gate. Every account, every book, every renewal cycle, with no human in the loop until there is a divergence to own. This is the part that never scaled when a CSM did it by hand, one account at a time, and the part AI does perfectly because it is mechanical.

SPLIT · KEEP THE JUDGMENT

What stays human?

The read and the divergence. The score says whitespace here, beachhead healthy, go. The CSM owns the account where the score and their gut disagree, because that account is a real save or a real true-up nobody had flagged. One owner on the book, a blinded grade against the human calls, and every divergence feeds back into the gate.

The workflow: the board that runs it

Solve, Stack, Split is the shape. Here is the actual board, lane by lane: what the agents run, what stays human, and the tool at each step. Once it is wired, the whole book gets scored every renewal cycle without anyone kicking it off.

The receipt

At a company I was at, a product-led SaaS with a large installed base and a CSM team layered on top, this is the exact build I ran. Map the whitespace, weight the untapped teams, gate on the health of the beachhead, then grade the whole thing against the humans who own the accounts.

The CSMs did not work harder. They worked a book where the whitespace was already scored, the dying beachheads were already flagged Fix-First, and the true-ups were already surfaced. The one account where the score and the gut disagreed was not a bug in the model, it was the model doing its job: pointing a human at the save nobody had flagged.

Both of my receipts are retention-side. Drop your own workflow in. An AE turns the same build into a new-business signal: the second business unit that has never seen the product, scored as whitespace, routed only if the first deal is healthy. A growth marketer turns it into a lifecycle trigger: the untapped team inside a healthy account, routed to an adoption campaign instead of a CSM.

WHAT I LEARNED

1. Expansion is not the champion. Seats in a team you already sold are the smallest part of the account. The growth is the rooms next door.

2. Score the whitespace, not the headcount. A hundred users in one team is not the opportunity. Three teams using nothing is.

3. Gate on the beachhead. You cannot cross-sell a new team off a dying one, so a dying beachhead caps expansion and goes Fix-First, no exceptions.

4. Grade the score against the humans. The divergence is not the problem, it is the product. It is where the save and the true-up were hiding.

The move this week

Do not build the whole system. Pick your ten biggest accounts. For each one, write down two numbers: active users over licensed seats, and how many teams inside that company use nothing. The first number is your true-up list. The second is your whitespace. Then draw one line through any account where the team you already sold is going quiet, and refuse to expand it until it is healthy again. That is the expansion score in miniature, and it tells you whether the full build is worth it before you spend a quarter on it.

Two builds that sit next to this one:

• Proactive Retention. "If your CSMs find out about churn from the customer, you do not have a retention motion, you have a notification system." The beachhead gate is that same instinct, pointed at expansion instead of churn.
• Scoring the TAM. "You cannot prioritize a market by scoring one deal at a time." Same rubric discipline, pointed inside the account instead of at the whole market.

This is one build from the Build Log. Every week I take one sales or revenue problem, run it through the loop, and show the receipts. If someone forwarded this, the subscribe button is right below. Keep building. Heath.