Illustrative customer success SaaS in Tampa: building NRR from 88% to 108%

The situation

An illustrative customer success SaaS in Tampa — a platform for CS teams to manage health scores, playbooks, and QBR workflows for their own clients — was at $120k MRR with 88% NRR. At that NRR, they were shrinking in real terms: every cohort of customers contracted over time because churn exceeded expansion.

The product team believed the product was strong. The CS team was doing QBRs with key accounts. But three structural problems were driving the negative NRR:

1. No expansion triggers. Accounts that were ready to upgrade (seat utilization above 80%, feature gates hit repeatedly) weren’t being asked to. The expansion happened only when the customer raised their hand — which meant many expansion opportunities passed without action.
2. No NPS loop. NPS surveys went out but nothing systematic happened with the responses. Promoters were thanked. Detractors were logged. Neither group received a follow-up that moved the needle.
3. No win-back program. Churned accounts received one cancellation confirmation email and then nothing. The team knew win-back was valuable but had no capacity to build the campaigns.

What got shipped

The snapshot went live on day 6 after purchase. Three workflow clusters were prioritized:

1. Expansion revenue triggers. Product webhooks were configured to send seat utilization data and feature gate hit events to GHL. Within 7 days, the expansion trigger workflow was live and firing on 14 accounts that had seat utilization above 80% for the prior 30 days.

The expansion email was personal — sent from the account’s owner — and specific: “I noticed your team is using 9 of the 10 seats on your current plan. Before you hit the limit and it becomes a problem, I wanted to flag the upgrade path — it’s straightforward and takes 5 minutes.” With a direct upgrade link.

Of the 14 accounts that received the expansion email in the first 30 days, 6 upgraded to the next plan tier.

2. NPS promoter → G2 review request. The NPS survey went to the 60-day post-activation cohort and to quarterly recurring cohorts. In the first 30 days, 42 promoter responses came in. The review request workflow fired within 4 hours of each response with a direct G2 review link.

Of the 42 promoters, 31 left G2 reviews in the first 60 days — an unusually high 74% conversion rate (typical for a SaaS in this product category is 20-30%). The team attributed the rate to the speed of the ask (within 4 hours, while enthusiasm was fresh) and the direct deep link (no friction to find the review form).

3. Win-back campaigns (30/60/90-day). The churned account database — 87 accounts over the prior 18 months — was imported and segmented by time since churn and cancellation reason (logged in the CRM).

Three campaign cohorts launched:

• 30-60 days post-churn: “We’ve added [specific feature] since you left — wanted to share in case it changes the picture.”
• 60-90 days post-churn: A case study from a similar customer + a 30-day free trial offer.
• 90+ days post-churn: A “we’re going to stop reaching out — thought you’d want to know what’s new first” final email.

In the first 90 days, 9 churned accounts re-activated. Average contract value of re-activated accounts: $520/month. Total win-back MRR: $4,680/month.

Illustrative outcomes at 90 days

• NRR improved from 88% to 108% — expansion revenue and win-back together added more MRR than churn removed.
• Expansion revenue: approximately $6,800/month in new MRR from accounts that upgraded after receiving expansion trigger emails.
• Win-back: 9 accounts, $4,680/month MRR.
• G2 review count: +31 in 60 days (the product had 12 G2 reviews before; it had 43 after — crossing the threshold that places it in G2’s “high performer” tier for the category).
• NPS detractor rescue: 4 of 11 detractors who received personal CS outreach resolved their issue and remained customers. 2 cancelled anyway. 5 are still in conversations.

The insight about NRR above 100%

NRR above 100% is qualitatively different for a SaaS business — not just quantitatively. When your existing customer base is growing net of churn, you have a base that’s compounding, not eroding. Every new customer you add is truly additive rather than replacement.

The team’s observation: crossing 100% NRR changed how the investors and the board talked about the business. Conversations shifted from “fix the churn problem” to “what’s the growth strategy.” That shift in context matters.

What would be done differently

The expansion trigger workflow should have been configured before the snapshot was even installed — the product already had seat utilization data; it just wasn’t being sent to GHL. Connecting that webhook on day 1 rather than day 4 would have brought in expansion revenue 3 days earlier.

The win-back campaigns would benefit from being triggered on a rolling basis (1 month post-churn, automatically) rather than as a batch launch. The batch launch worked for the existing churned database but required manual attention. The rolling configuration is already set up for future churned accounts.

Caveat

This is an illustrative scenario. NRR outcomes depend heavily on product quality, pricing model, customer segment, and competitive environment. Moving from 88% to 108% NRR in one quarter involves many factors beyond automation — including product roadmap improvements and CS team execution. Automation accelerates what’s already working; it doesn’t substitute for product-market fit.