The Builder

This is the CS leader who was hired to build something that doesn't exist yet — or inherited a function that's been under-resourced for years. They sit at companies with $75M to $1B in ARR, with the sweet spot between $100M and $500M. They've seen what Pendo and Gainsight look like when they're done right, usually at a prior company. And the gap between that vision and their current reality is vast.

Their mandate is almost always NRR. Not CSAT. Not ticket resolution time. Net revenue retention. But the mandate has more texture than the acronym suggests. For a PE-backed company at $150-$300M ARR, the board conversation has a very specific shape. GDR is the floor — every churned logo and every downsell at renewal is a number they have to defend to the executive team and explain to the sponsor. NRR tells the business whether CS is a cost center or a revenue function; getting above 100% changes how leadership thinks about the team's budget and headcount. Expansion attach rate measures whether CS is surfacing upsell and cross-sell or leaving it entirely to the account executive relationship. And for most of them, none of these numbers are reported in real time for the segment they are most responsible for. The mid-market and digital accounts may represent 30-40% of total ARR but have zero coverage, no engagement data, and no way to assess their health.

Walk into their org and you'll find a familiar landscape. Salesforce isn't clean. Gainsight is partially configured, with health scores built on human-entered sentiment rather than real data. Pendo is deployed, but it's owned by product — CS doesn't have access to the insights they need. Contact data is only 20-30% reachable, which means digital campaigns have no real audience.

Power BI is answering the wrong questions. And spreadsheets are filling the gaps everywhere else. The infrastructure was never built to support a scaled CS motion — and yet that's exactly what they've been asked to deliver.

• Clean contact data — a reachable audience they can actually engage at scale.
• Product telemetry in CS workflows — usage data flowing into the tools their team actually uses.
• Leading risk forecasting — 90 to 180 days out, not retroactive churn analysis.
• A scalable digital motion — for the unmanaged and low-touch accounts that still drive revenue.
• Cross-functional agreement — on what "good" looks like across CS, product, and revenue teams.
• Expansion signals surfaced automatically — so growth isn't left to chance or CSM intuition.

This persona values speed over perfection. They want to start with one use case, prove it works, and then expand. Their orientation is outcome-first — they don't care about methodology or frameworks for their own sake. They care about what moves the number.

Cross-functional buy-in is the real work. They know that the technical implementation is the easy part. Getting product, RevOps, and CS Ops aligned on shared definitions, shared data, and shared priorities — that's where most initiatives stall. They're skeptical of their own organization's ability to cooperate, and they value partners who understand that dynamic.