The Expansion-Readiness Score for Installed-Base Accounts

You have an installed base and a limited number of expansion conversations you can start this week. This guide gives you a repeatable way to score any existing customer account on expansion readiness, using public signals a rep can verify plus the context only the account owner holds, and to sort the whole base into expand-now, nurture, and hold. It is written for founders selling their own product, account executives, SDR leads, and CS owners who have to decide which happy customer to approach first.

The hard part is not finding activity at your accounts. It is that the same events that mean "expand" also mean "churn," and that a signal with no owner is a missed deal. This document separates the two and hands you a scoring procedure with named gates.

Why expansion beats new-logo prospecting right now

Expansion is the higher-return motion because new-logo economics got structurally worse, not because expansion got easier. The probability of selling to an existing customer is 60 to 70 percent, versus 5 to 20 percent for a new prospect. On acquisition cost, the Expansion CAC Ratio sits at a $1.00 median against a $2.00 median for New CAC. Expanding a customer from $1K to $1.5K MRR costs roughly $500, an ROI around 20 to 1.

The market has already shifted here. Teneo's 2026 B2B Software Vendor Survey found that 66 percent of B2B software growth in 2025 came from existing customers, and High Alpha's analysis puts expansion revenue at 40 to 50 percent of new ARR at high-performing SaaS companies. Teams that actively monitor expansion signals typically generate 20 to 30 percent more expansion revenue than teams that wait for customers to ask.

The catch is that not every segment expands the same way. Net revenue retention, the percentage of last year's revenue you keep and grow before adding new logos, diverges sharply by deal size.

Expansion economics by segment

The read: if your base is enterprise-weighted, expansion is where most of your growth already lives, and a scoring model pays for itself fast. If it is SMB-weighted (median NRR around 97 percent, meaning slight net contraction), scoring matters even more, because you cannot afford to spend a conversation on an account that is quietly leaving.

What an expansion signal is, and at what threshold it counts

An expansion signal is a dated, observable change at a customer that expands the seats, use cases, or budget lines your product can serve. Practitioners converge on five: department hiring surges, new function leadership, a new office or region, product launches, and funding rounds. Each one adds to the footprint you already sell into.

The one numeric threshold the open literature agrees on is hiring velocity. A company adding 10 to 20 new employees in 30 days is actively scaling operations, and when a current customer suddenly adds 15 engineers, they likely need more seats, features, or services. No source publishes validated per-signal conversion rates at a given threshold, so treat any single number as a starting point and derive your real thresholds from your own historical expansion deals.

Here is what each signal proves, and how it lies:

• Hiring surge. Proves growing capacity that needs more of what you sell. Lies when the hires are in a function you do not serve, or when it is one junior hire dressed up as momentum.
• Funding round. Proves fresh budget to allocate. Lies when you act on the announcement date instead of waiting for the planning window.
• New office or region. Proves geographic expansion where only one location may currently use you. Lies when the new site runs a competing standard chosen centrally.
• Product launch. Proves new use cases your product may support. Lies when the launch is a pivot away from the workflow you sit inside.
• New function leadership. Proves a new stakeholder and possibly a new budget line. Lies loudest of all, because it is equally a vendor-review churn trigger.

Growth or churn: reading the double-edged signal

The same signal set predicts both growth and churn, which is why the model must run a churn filter immediately after detecting a signal. A leadership change, new funding, new product line, or department restructure create upsell openings. Declining product usage, a competitor contract evaluation, or a champion departure flag churn risk. The events overlap: a new CEO or CFO reviewing vendor relationships, a strategic pivot, or layoffs are all firmographic churn signals that can look identical to growth from the outside.

The decisive filter is direction. Does the change add to or subtract from the footprint you serve, and is usage healthy? A new leader over your existing champion's function is a growth signal only if adoption is holding. If your champion is the one departing, that is the strongest early churn indicator you have, and pitching an upsell to someone auditing your contract is how a "warm" account becomes a lost one.

Use a two-axis read to place each triggered account. The horizontal axis is footprint direction: is the change adding or subtracting from what you serve? The vertical axis is adoption health: is usage rising or falling?

Only the bottom-right quadrant, footprint growing and usage healthy, earns a path to expand-now. Everything else routes to a save play, an adoption fix, or a churn watch.

The three account-owned gates

Before any expand-now verdict, a public signal must clear three gates that only the account owner can check: renewal proximity, adoption maturity, and satisfaction. A signal tells you something changed. The gates tell you whether this account is ready to be sold to.

• Renewal proximity. The 60 to 90 days before renewal is the highest-intent window. For AEs, a firmographic trigger like headcount growth or new funding stacked on that renewal window is the highest-converting expansion scenario there is.
• Adoption maturity. Upselling during active onboarding often backfires by adding complexity that reduces retention. Gate on adoption maturity, not on the calendar; a signal that fires mid-implementation waits.
• Satisfaction. Combine NPS, account size, and engagement to spot upsell readiness. Falling NPS, declining usage, loss of an internal champion, and absence of engagement are the clearest churn-risk signs, and any one of them should stop an expand-now verdict.

This is where a scan of public signals meets private context, and where most of the manual work lives. Finding which of your customers just posted fifteen engineering roles, or raised a round, or opened a second office, across the open web is exactly the kind of question Refolk answers in one plain-English query, so your reps spend their time on the gates rather than on the scan.

The scoring procedure

Run this in order. Steps one and two are setup you do once; steps three through eight repeat weekly.

Two sources disagree on the sort key in step eight, and you should reconcile both. One camp sorts by how fast the window closes: a plan limit hit today is a same-day conversation, a funding round is a this-quarter setup. The other emphasizes signal clustering first. Use clustering to decide whether an account qualifies at all, then use window-closing speed to order the accounts that qualify.

Mapping the buying committee for a cross-functional expansion

When an expansion needs budget outside your original champion's function, the account is no longer single-threaded and you must map a new buying committee. Use MEDDIC, the qualification framework where each letter names a role or requirement you must satisfy to close. The budget holder is the Economic Buyer, the advocate is the Champion, the security reviewer owns Decision Criteria, procurement owns the Decision Process, the VP who owns the target owns Metrics, and the department head in pain owns Identify Pain.

The gap that kills cross-functional expansions is the Economic Buyer. Sellers often misidentify the EB as someone who has budget to spend. In reality the EB is the decision-maker with the ability to move and alter spend to create budget for your solution. Your original champion, no matter how happy, usually cannot authorize spend in a function they do not run.

The reason to work this hard on coverage is arithmetic. Multithreading, meaning engaging multiple contacts across a deal, moves win rates dramatically.

Multithreading win-rate lift

Won deals in the $50K to $250K range involve at least ten stakeholders, per Gong's data. A cross-sell into a new function is precisely the deal that needs this breadth, because the buy touches a new Economic Buyer who was never part of the original relationship. Treat an unreached EB as a live risk, not a neutral gap.

How this goes wrong: failure modes and false positives

Most expansion scoring fails in predictable ways. Each of these produces a false positive that costs credibility with your best accounts, so build the check into the model, not into a rep's memory.

• Single-signal escalation. One junior hire or one press mention triggers outreach. The false positive is a "growth" account that never had budget. Check: require clustering plus recency before advancing.
• Double-edged leadership change misread. A new department head looks like growth but is a vendor-review churn trigger. The false positive is pitching an upsell to someone auditing your contract. Check: cross-reference against usage trend and whether it is your champion leaving.
• Funding-round over-eagerness. Outreach fires on the day of the raise. The false positive is interrupting planning and looking opportunistic. Check: enforce a 30 to 60 day delay.
• Onboarding upsell. A signal fires during implementation. The false positive is added complexity that reduces retention. Check: gate on adoption maturity, not the calendar.
• Ignoring the renewal clock. An expand-now verdict with a renewal ten months out. The window is not perishable and the play goes stale. Check: sort by window-closing speed.
• Single-threaded expansion. Relying on the original champion for a cross-functional buy. The false positive is a warm account that stalls at the Economic Buyer. Check: treat an unreached EB as a risk.
• Champion departure mistaken for opportunity. A role change looks like a fresh stakeholder to pitch. It is often your highest-value account quietly starting to churn. Check: act within 48 hours to map the replacement before pitching.
• No signal owner. A signal with no owner is a missed deal. If the funding announcement does not become a task on the account owner, the competitor who routed theirs into a CRM wins the upsell.

The champion-departure case deserves special weight because it inverts the whole model. B2B brands report an average of 23 percent annual churn, and 44 percent cannot even state their churn rate, so the accounts quietly leaving are often invisible. A departing champion is the earliest visible sign that one of them is going. Mistaking that departure for a fresh stakeholder to pitch is the most expensive error in this guide.

Who owns the score, and why it stays ad hoc

The person best suited to design an expansion-scoring program is the scarcest person on the team, which is why expansion so often runs on instinct. In Refolk's index of professional profiles, there are 81 US RevOps leaders at the VP or Director of Revenue Operations level, against 1,715 US AE/AMs and 752 US CSMs who list upselling or account expansion skills.

The people who must execute the model outnumber the person who should build it roughly 21 to 1 on the sales side and 9 to 1 on the CS side. Geography sharpens this: with 81 US RevOps leaders against 15 in the UK, a 5.4x gap, UK installed-base programs are even more likely to run without a dedicated scoring owner.

Who owns installed-base expansion (Refolk's index)

The practical consequence: do not wait for a RevOps hire to start. Keep the model small enough that a single AE or CS owner can run it - five signals, one churn filter, three gates, three verdicts - and make sure every triggered account gets a named owner so no signal dies untasked.

Account: Acme Corp
Trigger(s), dated: 15 eng roles posted (last 30 days); new office, EMEA (this quarter)
Cluster count / recency: 2 signals / both under 30 days
Growth-vs-churn: growth-leaning (usage +12% QoQ, champion stable)
Gates: renewal 74 days out [pass] | adoption mature [pass] | NPS 42 [pass]
Expansion definition hit: Team -> Business tier at 50 seats
New function: EMEA sales ops (not currently sold into)
Economic Buyer: VP Rev Ops, EMEA (unreached - live risk)
Champion: existing admin, US
Verdict: EXPAND-NOW | Owner: [AE name] | Next action + date: EB intro request, this week

Keep the score current

An expansion score is perishable, so treat it as a weekly cadence, not a one-time sort. Re-run the public signal scan every week, re-apply the churn filter to anything that moved, and re-sort by window-closing speed. Recompute your own thresholds each quarter against your closed expansion deals, since the 10-to-20-hires figure and the 30-to-60-day funding delay are starting points to be calibrated, not laws.

Run this final check before you call any account expand-now.

The measure of a working model is not how many accounts it flags. It is that when a rep opens the queue on Monday, the account at the top is genuinely the one to call, and no signal from last week is sitting without an owner.