Your Expansion Pipeline Has 47 Accounts Ready to Grow and Nobody Called

It is Tuesday, 10:34 AM. Your CS ops lead opens the customer health dashboard. 214 active accounts. She filters by Health equals Green and Product Usage delta positive 30 days. 47 accounts. She adds a filter for Seats Added inside the last 45 days. 34 accounts. She opens the Account Manager activity view. Six of those 34 have any AM touch logged in the last 30 days. The other 28 have last-contacted stamps between 74 and 210 days ago.

She scrolls. A $180K account added 12 seats in July and got a form-letter QBR reminder two weeks later. A $340K account rolled out a new product line, tripled API calls, and the AM last logged a call on May 18th. A $95K account expanded from one department to three and the AM working it has been on parental leave since June with no coverage assigned.

Pull the last four quarters of net revenue retention. The number reads 106%. The board deck rounds it to 110. The install base grew 41% in headcount and 34% in ARR. Net-new logos delivered $2.4M. Expansion delivered $1.1M against a plan of $2.8M. The CRO writes the gap off to "macro conditions." The math reads as a missed motion.

Expansion is a function. Most Series B and C teams have not staffed it because the first 40 customers expanded on inbound, a founder call, and a Slack Connect channel the CEO watched. The install base grew to 214 accounts across four product lines, two pricing tiers, a usage-based add-on, and a partner-sourced tier the AM bench never inherited. The function lives in the gap between the CS ops lead who owns the health score, the AMs who own the QBR calendar, the RevOps lead who owns the usage feed, the CRO who reads the NRR, and the CSMs who log tickets under a different taxonomy. On the org chart it sits under Customer Success. In practice it sits inside a Looker tab three people bookmarked.

The 47 accounts nobody called

Pull the health dashboard. Filter by Health Green, Product Usage delta positive 30 days, Seats Added inside 45 days, and NPS score above 40. Count accounts with any AM outreach inside 30 days. Count accounts with a scoped expansion opp on the pipeline. Count accounts with a scheduled QBR in the next 45 days. Most teams past Series B find 15 to 25 percent of the install base fits every expansion signal, one in four has an active AM touch, one in six has a scoped opp on the board, and half the scheduled QBRs slide by two weeks.

Walk one account. The $340K logo that tripled API calls. Product usage jumped week of May 4th when the buyer's platform team rolled a new integration. The health score flipped to Green on May 11th. The CS ops lead added them to a "trending up" cohort on May 14th. The AM opened the account on May 18th, sent a check-in email that got no reply, and moved to a churn-risk account the next Monday. The buyer's platform lead pinged their peer at a competitor on July 22nd asking about a multi-region rollout. Your competitor scoped a $410K expansion deal in three weeks. Your AM has the account marked "healthy" on the September QBR sheet.

The team that should own this knows it is broken. The CS ops lead ships a weekly health digest that stops at score color. The RevOps lead maintains a usage feed nobody wired to the forecast dashboard. The AM bench carries 42 accounts each and works the top ten by revenue. The CRO reads an NRR number the board sees rounded up.

Hiring an expansion lead is the slow answer

The textbook fix is a Director of Expansion or an Account Management leader with an install-base number. Loaded comp in the US runs $170K to $240K a year. Months one through three go to rebuilding the health rubric, mapping usage signals to expansion motions, and rewriting the AM comp plan. Months four through nine are when scoped expansion opps on the board move from 30 to 90 a quarter, expansion win rate lifts from 22 to the low 30s, and NRR clears 115%.

The fractional version is faster and stops at the same wall. Seven to eleven thousand a month buys twelve to sixteen hours a week of senior expansion work. The first month rewrites the scoring rubric and sequences the top 50 expansion candidates. The 214-account base keeps drifting because a fractional lead cannot watch every usage signal, score every account inside an hour of the signal, brief every AM before a call, draft every expansion talk-track against the buyer's usage pattern, and page the CRO when a competitor lands inside the account.

Both versions assume the work is a person auditing a cohort on a cadence. The work itself is watching every product usage signal in real time, scoring every account against a live expansion rubric the second the signal fires, matching every score to the buyer's org chart and current contract, drafting an expansion talk-track tied to the specific usage pattern before the AM opens the account, sequencing every AM's day around the top three expansion signals of the morning, pulling every competitor mention from the support queue and pushing it to the AM inside an hour, and posting an expansion health digest the CRO reads before the forecast call. On 214 accounts across four product lines that is 40 to 55 hours a week of senior expansion work. No single hire clears that pile and holds the NRR number at the same time.

What a fractional AI expansion function does

Hand the health dashboard, the product usage feed, the support ticket stream, the contract terms, the org-chart layer from Cognism or ZoomInfo, the QBR calendar, the pricing catalog, and the last four quarters of closed-expansion opps to a fractional AI agent. The agent does the work an expansion lead, an AM enablement manager, and a CS ops analyst would do together. The cadence is per-signal on scoring, per-account on the talk-track, per-morning on the AM sequencing, per-hour on competitor mentions, and per-Friday on the CRO digest.

Every usage signal scored inside an hour. The $340K account triples API calls at 11:14 AM Tuesday. By 12:02 PM the account carries an updated expansion score, a talk-track that names the new integration by name, a proposed $180K to $260K deal shape, and a scheduled AM outreach for Wednesday morning.

Every AM briefed before the call. The AM opens the account Wednesday at 8:47 AM. The brief names the three usage signals from the last two weeks, the two org-chart moves at the buyer, the one open support ticket the platform lead filed on Monday, and the two comparable deals your team closed in the last quarter.

Every competitor mention paged inside an hour. A support ticket at 2:04 PM mentions a competitor by name. The AM gets a Slack ping at 2:11 PM with the ticket, the account context, the last three usage signals, and a suggested outreach window inside 48 hours.

Every AM morning sequenced around the top three signals. The AM opens Slack at 8:47 AM. The queue names the three accounts with the strongest expansion signals overnight, the one account that dropped a health flag, and the one QBR scheduled today with a draft agenda in the shared doc.

Every expansion digest posted before the CRO forecast call. Friday, 9:00 AM. The digest names the 12 scoped opps this week, the seven accounts with new signals, the three at competitor risk, and the NRR forecast for the quarter.

The unit economics of a missed expansion motion

A Series B company at $22M ARR sitting on 214 install-base accounts with 106% NRR is burning three specific things. The AM bench, the CS ops lead, and the RevOps lead spend a combined 18 to 26 hours a week on account triage, QBR prep, and manual usage reporting against a fully loaded hour of $180 to $310. That is $14K to $32K a month of senior time on work a live scoring feed clears. The AM bench gets six to ten hours a week back inside the first sprint.

The NRR line is the second one. Moving scoped expansion opps from 30 to 90 a quarter on a base averaging $150K per opp lifts expansion ARR from $1.1M to $2.6M a year, closing the gap the CRO writes off as macro. NRR moves from 106 to 115 to 122 across three quarters on the same install-base spend. The board deck stops rounding.

The compete line is the third. A competitor scoping a $410K expansion deal inside your Green-health account is a story that shows up in the win-loss digest as "lost expansion, competitor scoped first." An expansion motion that scores usage signals in real time and pages the AM inside an hour lands the talk-track in front of the buyer before your competitor books a call.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one Gainsight seat than a Director of Expansion hire. The scoring feed and the talk-track engine run in week one. The AM sequencing and the competitor-mention paging run in week two. The CRO digest ships off a live feed before the sprint closes.

What changes after the sprint

Picture the same Tuesday, 10:34 AM moment, thirty days after the sprint ships. Your CS ops lead opens the health dashboard. 47 accounts scoring Green with positive usage delta. 41 have an AM touch inside seven days. 34 carry a scoped expansion opp with a talk-track in the shared doc. The $340K account shows a scoped $260K expansion opp on the board, an AM call logged for Thursday, and a competitor mention from the July 22nd ticket flagged with an outreach that landed the same day.

By Friday the CRO reads an expansion digest that names 12 opps closing this month, seven accounts with new signals, three at competitor risk, and an NRR forecast trending to 117% for the quarter. The AM bench works the top three expansion signals of the morning instead of the top ten accounts by revenue. The CS ops lead runs a Monday review that closes the loop between usage signal and scoped opp inside seven days.

If your health dashboard currently shows 47 Green accounts with two seats added last month and zero AM outreach logged, the version where every usage signal scores in an hour and every AM opens a briefed queue by 8:47 AM is fourteen days away. Expansion is a function. You can hire against it, you can retain a fractional expansion lead for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.