# Use case: Head of Customer Success **The situation** Customer Success is where the real business happens. Not the pitch, not the signed contract — the moment where your product either delivers on its promise or it doesn't. The CS leader owns that moment, at scale, across every customer the company has ever signed. That's an enormous responsibility. And it's also enormous leverage. When CS is working well, revenue compounds. Customers expand. Advocates refer new business. NRR climbs. The company builds on a foundation of customers who are genuinely succeeding — and that foundation is more durable than any sales pipeline. The challenge isn't the importance of the role. It's the visibility. CS creates value continuously, across hundreds of accounts, in ways that are often invisible to the rest of the business. A churn that didn't happen. An expansion that came from a CSM conversation six months before renewal. An onboarding that went so smoothly the customer didn't even notice. These outcomes don't show up in a dashboard unless you build one. The CS leader's job — whether that's a dedicated Head of CS, a CRO, or a founder managing the customer base directly — is threefold: build the system that makes great CS happen consistently, make the value of that system visible to the rest of the business, and ensure that customer success becomes a company-wide orientation, not just a department. *** **The approach** **Own the customer, not just the function** Customer success isn't something that happens inside the CS team. It happens in product, in support, in marketing, in sales handoffs, in the onboarding experience, in the way pricing is structured. The CS leader who sees their job as managing a team is playing a smaller game than the one available to them. The most effective CS leaders build a customer success culture — one where every department understands how their work affects customer outcomes, where the health of the customer base is a metric that matters at the board level, and where CS data informs product decisions, sales positioning, and company strategy. This starts with visibility. When the CEO and CFO can see customer health, NRR trend, and renewal pipeline in real time — not in a monthly report, but always — CS becomes part of the strategic conversation rather than a quarterly update. **Build a system, not a team of heroes** Retention and expansion shouldn't depend on which CSM a customer happens to be assigned to. The best CS operations are systematic — every customer gets the same quality of attention, the same onboarding process, the same rhythm of touchpoints, the same early warning when something changes. The individual CSM's skill and judgment matters within that system. But the system is what makes it consistent and scalable. **Make the invisible visible** CS creates value that's easy to miss if you're not looking for it. Churn prevented by an early intervention. Expansion generated by a well-timed conversation. A reference customer who came from a relationship built over two years. The CS leader's job is to make this value explicit — in language the board understands, with data that connects CS activity to revenue outcomes. *** **How to do it in Startdeliver** **Build the portfolio view that runs the business** Impact dashboards give you a live view of what matters — health distribution across the customer base, NRR trend, ARR at risk, renewal pipeline, team activity. No spreadsheet to maintain, no report to request. The data is there when you need it — for your own decision-making and for the conversations you have with the CEO, CFO, and board.

Build the dashboards that answer the questions you get asked most often. What's our gross retention? Where is churn coming from? Which segments are healthiest? How does health correlate with renewal rate? When CS data is always current and always accessible, it becomes part of how the whole company thinks about the business. → [Dashboards & Reports](https://docs.startdeliver.io/dashboards-and-reports) · [MRR & ARR](https://docs.startdeliver.io/health-and-metrics/mrr-and-arr) **See the full picture in real time** The AI reads every customer continuously and surfaces what matters — at-risk accounts, expansion opportunities, customers approaching renewal, accounts that haven't been contacted recently. You see the full portfolio health at any moment, filtered however you need it — by ARR, by CSM, by segment, by lifecycle stage.

This changes how you operate. Instead of finding out about a high-value at-risk account in a weekly meeting, you see it the moment the signals change. Instead of asking your team for a status report, you open Startdeliver and the status is there. → [How health assessment works](https://docs.startdeliver.io/health-and-metrics/how-to-set-up-health-metrics-and-assessment) · [Lists & filters](https://docs.startdeliver.io/platform-settings/lists-and-filters) · [AI Assessments](https://docs.startdeliver.io/use-cases/broken-reference) **Coach with data, not intuition** Startdeliver gives you visibility into what's actually happening in accounts — not just what CSMs report. You can see which accounts haven't been contacted recently, which ones have overdue tasks, which ones have drifted quietly while appearing fine. You can see patterns across a CSM's portfolio — where they're strong, where they need support, which account types they struggle with.

AI Manager surfaces these patterns proactively — giving you the factual basis for coaching conversations that lead to genuine improvement. → [AI Manager](https://docs.startdeliver.io/jecta-agent-and-ai/ai-manager) **Standardize the motion across the team** When every CSM runs onboarding the same way, uses the same project templates, follows the same Success Plan structure, and gets the same automated alerts — the quality of CS becomes a function of the system rather than individual talent. This is what makes CS scalable.

Build the templates, configure the automations, set the health model, define the lists. A new CSM joining your team should be able to deliver the same quality of CS as your most experienced one within weeks — because the system already knows what good looks like. → [Templates & projects](https://docs.startdeliver.io/platform-settings/templates-and-projects) · [Automations](https://docs.startdeliver.io/managing-customers/automations) · [Customer Goals & Success Plans](https://docs.startdeliver.io/managing-customers/customer-goals-and-success-plans) **Scale without proportionally growing headcount** As the business grows, the question of how to serve more customers without proportionally adding headcount becomes central. Jecta and automation handle the work that doesn't require a human — consistent touchpoints, early warning outreach, routine follow-up, Shared Space management — so CSMs can carry larger portfolios without sacrificing quality. This isn't about replacing CSMs. It's about making each one more effective. A CSM supported by Jecta and well-configured automations delivers more to more customers than one working manually. That's the leverage that lets CS scale with the business. → [Jecta: AI Agent](https://docs.startdeliver.io/jecta-agent-and-ai) · [Automations](https://docs.startdeliver.io/managing-customers/automations) **Make CS a company-wide orientation** Share the dashboards with the leadership team. Show the correlation between health scores and renewal rates in your next board meeting. When product asks for customer feedback, point them to the experience health data. When sales asks about expansion potential, show them the AI's expansion flags. When the CFO asks about the revenue impact of CS, show them the NRR trend alongside the CS activity that drove it.

CS data, made visible and accessible, becomes the lens through which the whole company understands its customers. That's the CS leader's most powerful contribution — not the accounts they personally manage, but the customer success culture they build around them. **Send leadership the weekly digest** Enable the Executive Report and add your CEO, CRO, and relevant board members as recipients. Every Monday morning they get a one-page summary of ARR, health changes, at-risk accounts, and what the CS team did last week — without anyone having to prepare it.

When leadership has a current view of the customer base in their inbox every week, CS stops being something they hear about in quarterly reviews and becomes part of how they think about the business. The customer health conversation becomes ongoing rather than periodic. → [Executive Report — Weekly digest](https://docs.startdeliver.io/dashboards-and-reports/weekly-digest-executive-report) → [Dashboards & Reports](https://docs.startdeliver.io/dashboards-and-reports) · [How health assessment works](https://docs.startdeliver.io/health-and-metrics) *** **What good looks like** * Customer health is a metric that matters at the board level — visible, current, and connected to revenue outcomes * You start every week with a live view of portfolio health, renewal pipeline, and at-risk accounts — and so does your CEO * The quality of CS across your team is consistent regardless of individual CSM experience or workload — because the system enforces the standard * Your team grows its portfolio without proportionally growing headcount — because Jecta and automation handle the volume work * Coaching conversations are grounded in account data and activity patterns — specific, factual, and forward-looking * Every department understands how their work affects customer outcomes — CS isn't a silo, it's the compass --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.startdeliver.io/use-cases/use-case-head-of-customer-success.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.