The Challenge
A Series B enterprise AI platform with $42M ARR had built a strong Beacon motion — brand-first, anchored by 14 credible enterprise references, scaled through tech-company cohorts. New logo acquisition was healthy. The land was working.
The expansion was not. Net Enterprise Revenue Expansion sat at 104%. Existing accounts were renewing but not expanding. The customer success team was running QBRs that recapped usage. The AEs had moved on to new logos. The accounts that should have been growing from a single department into the enterprise were renewing flat or growing by single digits.
The founder thought this was a CS problem. The actual problem was that nobody owned the expansion motion as a motion. The land had a playbook. The expand had a calendar invite. The buying committee for the expansion — the divisional CIO, the line-of-business owner, the CFO who had not been in the original deal — was being treated as a renewal conversation instead of a new enterprise sale inside an existing logo.
The Foundational Plan: Expansion Motion Architecture
Through founder, CRO, and VP Customer Success interviews, we ran the existing customer base through the 52-motion taxonomy a second time — this time as expansion motions. Three distinct expansion motions were operating without anyone naming them. We architected an "Expansion Beacon" motion stack — the same Beacon archetype applied inside existing accounts, with the buying committee mapped fresh for each expansion opportunity.
Supporting intellectual assets included:
- Account tiering for the top 60 existing enterprise accounts based on expansion headroom, not current spend
- Expansion buyer center maps identifying the divisional CIOs, business unit owners, and enterprise architects who had not been in the original land deal
- A reference architecture showing the eight expansion patterns the existing customer base was actually running, sourced from the 14 reference customers' public commentary
- Commercial framework restructuring expansion conversations away from seat-add renewals and toward enterprise-wide commitments
Ongoing Production: Expansion Signal at Scale
Expansion Signal on 60 named accounts (Months 1–6): Nine-section briefs built per existing account — what they had deployed, the unfinished layer inside their own environment, the divisional buyers who had not yet been engaged, recent reorgs and CIO commentary, the three expansion bets we would prioritize. Each Signal hosted on a page under the client's domain and shared into the account by the AE, not the CSM.
Buying committee mapping per expansion: The expansion buying committee at a global bank looks nothing like the original deal's buying committee. Each was mapped fresh, with named humans and public commitments.
AE re-engagement at the senior altitude: AEs were pulled back into expansion conversations alongside CSMs. The CSM owned the relationship. The AE owned the commercial motion. A senior operator sat in on every expansion conversation above $500K.
Quarterly Signal refresh: As the customer's own roadmap shifted, the Signal shifted with it. Three customers received refreshed Signals within a week of internal reorgs that the AE would otherwise have learned about a quarter late.
Reference architecture distribution: The eight expansion patterns became a reference document the AEs deployed in every expansion conversation, anchoring the discussion in what peers were doing.
Business Impact & Results
NERE expansion: Net Enterprise Revenue Expansion grew from 104% to 168% across the engaged cohort over three quarters. Twelve accounts grew by more than 2x in the period. Three accounts grew by more than 4x.
ERR strengthening: Enterprise Revenue Retention moved from 118% to 142%. Logo retention held flat at 96% — the gains were all in compounding inside existing accounts.
Expansion deal velocity: Average expansion deal closed in 4.1 months, down from 7.3 months. Expansion deals over $500K were closing at the same velocity as the original land deals.
AE and CSM alignment: The internal handoff between AE and CSM was rebuilt around the Signal. Pipeline visibility for expansion grew from quarterly forecast guesses to a maintained 90-day forward view.
Board-level read: The CRO presented NER, ERR, and NERE as separate metrics to the board for the first time. The expansion motion was named, measured, and forecastable.
.svg)
