Your Customer Success Team Closed 4,200 Tickets Last Quarter. They Generated $0 in Expansion Revenue. Your NRR Is 94%. You’re Leaking.

Your Head of Customer Success walks into the QBR with the usual deck. Ticket volume: up 12%. Average resolution time: down 18%. CSAT: 4.6 out of 5. NPS: 52. Renewal rate: 89%. The room nods. The VP of Sales pitches new logo targets for next quarter. The CMO presents campaign performance. Meanwhile, one number nobody mentions: Net Revenue Retention is 94%. That means for every dollar of revenue in your base at the start of the year, you exit with 94 cents. Your “customer success” organization is actually a well-dressed customer retention organization that is losing six cents on every dollar while presenting tickets-closed as a success metric. The six cents, compounded over five years, is 26% of your revenue base evaporating silently while the CS team celebrates CSAT scores.

Net Revenue Retention measures the change in revenue from an existing customer cohort over a defined period, incorporating expansion, contraction, and churn. In subscription and recurring-revenue businesses, NRR below 100% indicates that the existing base is shrinking and that new customer acquisition is funding replacement of lost revenue rather than driving net growth. NRR above 110% indicates that the existing base is producing organic revenue growth independent of new customer acquisition.

The Fusion: Buzzword Function Meets Measurable Growth Lever

“Customer Success” is the most linguistically successful organizational rebranding of the last 15 years. Support teams renamed themselves CS. Account management teams renamed themselves CS. Onboarding teams renamed themselves CS. The rebrand conferred strategic status without requiring a corresponding change in function, measurement, or economic contribution. Most organizations now have a Head of Customer Success whose team performs the same work as the Head of Support did in 2008, reports the same ticket-volume metrics, and produces the same economic output — which is to say, close to zero incremental revenue. The title is new. The function is old. The expense is real.

Welded to Net Revenue Retention, Customer Success stops being a rebranding and becomes a measurable growth function. NRR is the scoreboard that distinguishes a genuine expansion engine from a relabeled support team. If NRR is below 100%, the CS organization is a cost center regardless of what the business cards say. If NRR is between 100% and 110%, the organization is producing modest economic contribution and has clear room to improve. If NRR is above 110%, the organization is operating as a genuine growth lever and may deserve additional investment. The metric settles the argument. The question is whether the CS leader reports against it, and whether their compensation is tied to it.

The comfortable delusion is that Customer Success is “strategic” in a way that defies traditional measurement. Organizations accept this framing because measuring CS against revenue outcomes is uncomfortable for the CS team and disruptive to the tickets-and-satisfaction reporting rhythm they have established. The discomfort is the entire reason NRR-based accountability produces results. Every month the CS team continues to report on ticket volume instead of expansion revenue is another month the organization funds an expensive support function while calling it a growth lever.

The CS Redesign That Moved NRR From 94% to 117%

B2B software business, roughly $110 million in ARR, 14-person customer success organization reporting to a Chief Customer Officer. The team reported quarterly against three metrics: customer satisfaction, ticket resolution time, and logo retention rate. All three metrics were in the top quartile of the peer benchmark. The CCO had been in role for three years and was considered a category-leading CS executive. The NRR metric, calculated by the finance team for the board, was 94%. It had been between 92% and 96% for every quarter of the CCO’s tenure.

The board had never pushed on the gap because the CSAT and retention numbers were strong, and the CS team’s internal narrative framed expansion as “sales territory” rather than CS territory. Expansion revenue, when it happened, was credited to the account executive who closed the incremental order. The CS team had no direct incentive to drive expansion and no compensation tied to NRR. The finance team calculated NRR quarterly and published it in the board deck, and nobody on the CS team read the board deck.

I redesigned the CS function in Week 6. The structural changes were three. First, the team was renamed from Customer Success to Customer Expansion, to make the actual job explicit. Second, the primary reporting metric became NRR by account segment, published monthly alongside the ticket metrics but at the top of the deck rather than the bottom. Third, the compensation structure was restructured so that 40% of variable pay was tied to NRR performance against target, with the target set at 108% for the first year and 112% for the second year. Ticket metrics and CSAT remained in the scorecard but at 20% weighting combined.

The behavioral changes followed the compensation changes, as they always do. Within 90 days, the CS team had rebuilt the account-management rhythm around quarterly business reviews that explicitly identified expansion opportunities, with specific dollar targets attached to each opportunity and specific product-module recommendations based on usage patterns. The team had stopped running support-volume analyses and had started running usage-depth analyses, which revealed that approximately 40% of the installed base was using less than half the product capability they had contracted for. That underutilization was the expansion opportunity, and it had been sitting visible in the telemetry data for 18 months with no CS team ever examining it.

NRR over 12 months moved from 94% to 108%. Over 24 months, it reached 117%. The incremental revenue contribution over those 24 months was approximately $24 million — pure organic growth from the existing base, at roughly zero incremental acquisition cost, through the simple intervention of pointing the CS team at the metric that actually measures their economic contribution. Three members of the original CS team transitioned out during the first year because the new operating rhythm was a materially different job than the one they had signed up for. Four new hires came in from enterprise sales backgrounds rather than support backgrounds, and those four produced disproportionate expansion revenue in Year 2. The total headcount was unchanged. The function’s economic output was transformed.

The rebranding of support functions as “Customer Success” over the past 15 years has been primarily a linguistic exercise rather than an operational redesign. Organizations that distinguish themselves in net revenue retention do so by compensating and managing their customer-facing post-sale teams against expansion revenue outcomes rather than against service-level metrics. The measurement choice determines the behavior, and the behavior determines the NRR.

The Playbook

Move 1: The NRR Diagnostic

Calculate Net Revenue Retention by customer cohort for the last eight quarters. Segment by account size tier — enterprise, mid-market, and SMB — because NRR dynamics are meaningfully different across segments and an aggregate number can conceal either a strong enterprise book or a bleeding SMB base. Publish the segmented NRR at the top of the CS review deck, not the bottom, and require the CS leader to speak to it before any other metric.

If NRR is below 100% in any segment, that segment is economically contracting. The CS function in that segment is, by definition, not producing net growth from the existing base, and the organization is funding replacement revenue from new acquisition at acquisition cost rather than expansion cost. The gap between the two is the economic cost of CS misalignment in that segment.

Move 2: The Expansion Playbook

Rebuild the CS team’s operating rhythm around expansion opportunity identification rather than ticket resolution. The primary analytical work shifts from “what did customers complain about this week” to “which customers are using less than 60% of what they have contracted for, and what is the next logical expansion they should be using.” Every account review produces a specific expansion dollar target with a specific product or module recommendation, and those targets roll up to the segment NRR number.

Support volume and incident management remain necessary operational work but are structurally separated from the expansion function. In most restructured organizations, the support work moves to a dedicated technical support team, and the CS team is freed from ticket-volume responsibility. This is the change that most enables the behavioral shift, because as long as the CS team owns tickets, the tickets will consume the team’s calendar and attention.

Move 3: Comping CS on NRR, Not Tickets

Restructure the variable compensation of every CS team member to include NRR attainment as at least 40% of total variable. The target should be set above 100%, typically between 105% and 115% depending on category economics and customer base maturity. CSAT and retention metrics can remain in the scorecard but should never exceed 25% combined weight, because over-weighting those metrics reintroduces the incentive to prioritize customer satisfaction over expansion revenue.

The compensation redesign will produce voluntary attrition in the first two to three quarters as CS team members who are not suited for expansion-focused work self-select out. That attrition is necessary and should not be treated as a failure of the redesign. The replacements should be recruited from account management and inside sales backgrounds, not from support backgrounds, because the skill profile required for expansion is materially different from the skill profile required for ticket resolution.

Move 4: The 90-Day Question

What is your NRR, by segment, and is your CS team paid on it? If the answers are “I am not sure” and “no,” you have diagnosed the problem. If the first answer is specific and the second answer is no, you have a CS leader who understands the metric and an organization that has not aligned compensation to it, which is the easier fix of the two. If the first answer is unknown, the diagnostic work itself is the first 30 days of the playbook, because nothing else can be designed until the baseline segment NRR is measured and published.

Monday Morning

Ask your CS leader to report NRR by customer segment at the next weekly leadership meeting. If they do not have the number, give them two weeks to pull it from the finance team. Once the baseline is published, commit to a compensation redesign before the next fiscal year. Every quarter your CS team reports ticket metrics without NRR accountability is another quarter of organic growth opportunity sitting in the installed base while the team optimizes for the wrong scoreboard.

For the NRR diagnostic template and the CS compensation redesign worksheet, visit toddhagopian.com/freetools. The full customer expansion methodology is in The Stagnation Assassin at toddhagopian.com/book. Operator conversations on NRR discipline, customer success accountability, and the economics of expansion revenue are at The Stagnation Assassin Show: toddhagopian.com/podcast.

Your CS team is closing tickets this week. Your NRR is bleeding. The finance team has the number. Nobody on the CS team has read it. The question is whether you will put NRR at the top of the next CS review deck or keep letting ticket volume be the story.