CRM for Customer Success Managers: Onboarding, Health Scores, and Renewal

Customer success managers need a CRM that follows the customer lifecycle after the sale, not just before it. Onboarding, health scores, and renewals all need to live in the same system so the team can see risk early and act before it becomes churn.

Customer Success Managers (CSMs) use CRM to manage the post-sale customer lifecycle — onboarding, adoption, health monitoring, renewal, and expansion. Their CRM needs are distinct from sales: they’re not managing a pipeline of new deals, they’re managing a portfolio of existing customer relationships with different health signals, risk levels, and growth potential. CRM for CSMs needs to surface which customers need attention and when, track health scores and engagement, and manage the renewal process with the same rigour that sales manages the initial deal. This guide covers how to configure CRM to support the CSM workflow effectively.

That makes the CSM CRM workflow retention-focused from the start rather than reactive at the end.

CSM CRM Workflow by Customer Lifecycle Stage

Onboarding Tracking in CRM

The onboarding period (typically first 60-90 days after contract close) is the highest-risk period for early churn. Customers who don’t achieve their first meaningful outcome within 90 days are significantly more likely to churn at renewal. CRM should track onboarding milestones explicitly:

Required onboarding fields on the Company/Account record:

• Kickoff call completed (date)
• Technical setup completed (date)
• First user trained (date)
• First value moment achieved (date — the customer’s first meaningful outcome with the product)
• Onboarding status (dropdown: Not started / In progress / Complete / Stalled)

Automated task creation: when a deal closes and is assigned to a CSM, create a set of CRM tasks automatically:

• Day 1: Schedule kickoff call
• Day 3 (after kickoff): Send onboarding resources / access credentials
• Day 14: Check-in call — are they on track?
• Day 30: 30-day health review — first value moment achieved?
• Day 60: 60-day review
• Day 90: 90-day health assessment and success story documentation

These tasks are created by CRM automation from the deal close trigger — no manual task creation required from the CSM. The CSM’s job is to complete the tasks, not to remember to create them.

Health Scores: Building a Customer Health Scoring Model

A customer health score is a composite score that represents the overall health of the customer relationship — from 1 (critical risk) to 100 (excellent) or from Red/Yellow/Green. Health scores aggregate multiple data signals that individually might not indicate risk but together show a pattern:

Health score components and typical weightings:

• Product usage (30%): are they using the product? How often? Are key features being adopted?
• Support experience (20%): number of open tickets, resolution time, CSAT score
• Engagement with CS (20%): has the CSM had a substantive interaction in the last 30 days? Is the champion still engaged?
• Commercial health (15%): are they paying on time? Are invoices overdue?
• NPS / satisfaction (15%): most recent NPS score or CSAT rating

Configure the health score as a calculated field in the CRM — ideally updated automatically when any input variable changes. In HubSpot, build this as a calculated property or via workflow automation. In Salesforce, use a formula field or Einstein scoring. Dedicated CS platforms (Gainsight, ChurnZero, Totango) provide more sophisticated health scoring than native CRM tools.

Renewal Management as a Pipeline

Renewal management should be treated as a pipeline — not just a date on the calendar. Create a Renewal pipeline (separate from the sales pipeline) with stages:

1. Renewal Identified: 90+ days out; health assessment initiated
2. Health Assessment: CSM has reviewed health score and identified any risks
3. Commercial Discussion: pricing and contract terms being discussed
4. Renewal Sent: contract sent for signature
5. Renewed / Churned: outcome

Automated renewal pipeline creation: 90 days before each customer’s renewal date, a workflow automatically creates a Renewal deal in the pipeline, assigns it to the CSM, and creates the first renewal task. CSM doesn’t need to remember which renewals are coming — the CRM surfaces them automatically.

Renewal pipeline metrics the CSM manager reviews weekly:

• Renewal deals by stage and expected renewal date
• Gross renewal rate ($ renewed ÷ $ up for renewal)
• Net renewal rate ($ renewed including expansion ÷ $ up for renewal)
• Churn rate: $ churned ÷ total ARR at start of period

Customer Success Platform vs CRM for CSM Workflows

Dedicated Customer Success platforms provide more sophisticated CS-specific functionality than CRM customisation:

• Gainsight: enterprise CS platform; deep health scoring, playbooks (automated response workflows to health score changes), executive business review templates, renewal forecasting. Integrates with Salesforce. Best for CS teams managing 100+ accounts at enterprise scale.
• ChurnZero: mid-market CS platform. Strong real-time engagement tracking, renewal management, and in-app messaging. Integrates with HubSpot and Salesforce.
• Totango: flexible CS platform with strong free tier. Good for teams transitioning from spreadsheet-based CS management to a dedicated tool.
• HubSpot Service Hub: for HubSpot users, Service Hub adds CS-oriented features (tickets, satisfaction surveys, knowledge base) without leaving the HubSpot ecosystem. Less specialised than Gainsight but simpler to maintain for teams without dedicated CS ops.

Evaluate dedicated CS platforms when: the CSM team manages more than 50-75 accounts per CSM, health scoring needs to incorporate product usage data from multiple sources, or renewal pipeline complexity exceeds what CRM customisation can support cleanly.

CRM for Customer Success Managers: Turning Data Into Retention Actions

Customer success managers who use the CRM only to log calls and update renewal stages are using a fraction of the platform’s value. The CSM-specific CRM practices that produce measurable retention improvement are those that make health signals visible before they become churn signals, that structure the onboarding process as a trackable milestone sequence, and that connect expansion opportunities to the renewal workflow so that net revenue retention is managed proactively rather than reactively.

The best version of the workflow is the one the team can keep using during busy weeks. If it only works when someone is manually policing it, the process needs more clarity.

Common Problems and Fixes

“CSMs don’t know which accounts are at risk until a customer calls to cancel”

Reactive churn management — responding after the customer has made a cancellation decision — has a very low success rate. The fix is health score automation: (1) build a health score that updates automatically (daily or weekly) from product usage, support, and engagement data; (2) set a threshold (health score below 40 = Red) that automatically creates a CSM task: “Account [X] has dropped to Red — schedule a recovery call within 48 hours”; (3) create a manager alert for accounts that drop to Red and have renewal within 90 days. The goal is surfacing risk 60-90 days before the renewal conversation, not the day before.

“We track renewal dates but CSMs don’t start renewal conversations early enough”

The fix is automation, not reminders. The 90-day automated renewal deal creation (described above) removes reliance on CSMs remembering to start the process. Additionally, build an escalating urgency workflow: when renewal is 60 days out and the renewal deal is still in stage 1 (no commercial conversation started), send the CSM manager a notification. When renewal is 30 days out and the deal hasn’t advanced, send an executive alert. Urgency automation prevents late renewal conversations — the most common cause of churn that could have been prevented.

Problem: Onboarding Milestones Are Not Tracked in the CRM

Customer success managers who track onboarding progress through email threads and personal notes have no structured way to identify customers who are falling behind. When a customer reaches day 30 without completing key onboarding milestones, the CSM discovers the problem only when the customer asks for help or expresses frustration. By day 30, the window for early engagement that drives long-term retention has narrowed significantly.

Fix: Build an onboarding milestone tracker as a structured CRM object or a set of required fields on the customer account. Define five to seven milestones that represent the key steps in your onboarding process: first login completed, primary use case configured, team member invited, integration connected, first value moment achieved (a milestone specific to your product’s core promise). Record the target completion date and actual completion date for each milestone. Create an automated CRM alert when a customer is more than five days behind on any milestone: the alert should create a task for the CSM to intervene with specific guidance for the incomplete step. Review onboarding completion rates monthly to identify which milestones have the highest drop-off rates and refine the onboarding process accordingly.

Problem: Success Plans Exist as Documents Rather Than CRM Records

Customer success plans (the documented agreement between the CSM and the customer about goals, timelines, and success metrics) are typically created in Google Docs or Word and attached to an email. They are rarely accessible from the CRM account record. When the CSM changes, when the customer’s executive sponsor changes, or when a QBR review requires current success plan information, the document must be located, opened separately, and manually reviewed alongside the CRM record.

Fix: Migrate customer success plans from documents to structured CRM fields. Create a success plan section on the account record with fields for: stated customer goals (text), success metrics (text: how the customer will measure success), agreed milestones (date fields for key target dates), current health assessment (CSM’s qualitative assessment with date), and next QBR date. For organisations that need richer success plan functionality, tools like Gainsight, ChurnZero, and Planhat integrate with Salesforce and HubSpot to provide purpose-built success plan templates linked to CRM account data. The minimum requirement is that a new CSM taking over an account can understand the customer’s goals, current health status, and upcoming milestones entirely from the CRM record without needing to locate and read a separate document.

Problem: Expansion Opportunities Are Created After Renewal, Not Before

CSMs who focus primarily on renewal success and only begin tracking expansion opportunities after the renewal is confirmed miss the most effective window for expansion conversations. The customer who is reviewing their contract renewal is simultaneously reviewing their relationship with the vendor and their plans for the product. This is the optimal time to introduce expansion: the customer is already engaged in a commercial conversation, the relationship is typically at a high point immediately before renewal, and the expansion can be incorporated into the renewal terms.

Fix: Create CRM expansion opportunity records 90 days before the contract renewal date as a standard workflow. The expansion opportunity should capture: the expansion type (additional seats, higher tier, additional module), the estimated expansion value, the primary use case for the expansion, and the stakeholder who would need to approve it. Link the expansion opportunity to the renewal deal so that both are managed together in the renewal conversation. Configure a CSM dashboard that shows, for every account with a renewal within 90 days, both the renewal status and the expansion potential assessment. This dual view encourages CSMs to think about net revenue retention (renewal plus expansion) rather than gross retention (renewal alone) and produces higher NRR without requiring a separate commercial motion.

Frequently Asked Questions

What CRM fields are most important for a customer success manager?

The most important CRM fields for a CSM are: contract end date (drives renewal workflow), contract value (ARR or MRR), customer health score (composite indicator of product usage, support activity, and sentiment), last QBR date, onboarding completion percentage, assigned CSM owner, expansion potential (qualitative assessment), and primary contact and executive sponsor. Secondary fields include NPS score, support ticket count in the last 90 days, product usage tier, and key customer goals. Make contract end date, contract value, and CSM owner required fields: the absence of any one of these makes renewal pipeline management and health scoring impossible.

How should a CSM use CRM data to prepare for a QBR?

A QBR preparation workflow using CRM data should cover: review the customer health score trend for the last 90 days and identify any significant changes, pull the product usage data for the period (from the CRM or an integrated product analytics tool), review the support ticket summary (volume, severity, and resolution time), check the onboarding milestone completion status and any outstanding items, review the success plan goals and assess progress against each, identify any expansion opportunities linked to the account, and draft the QBR agenda based on the data review. This preparation should take 30-45 minutes for a well-maintained account record and produces a QBR that is data-led rather than relationship-led.

What is the difference between a customer success CRM and a purpose-built CS platform?

A CRM adapted for customer success provides account management, health scoring, and renewal pipeline functionality using native CRM features and custom configuration. A purpose-built CS platform (Gainsight, ChurnZero, Totango) provides additional features designed specifically for customer success: automated playbooks triggered by health score changes, native product usage data integration, customer journey milestone tracking, and 360-degree account views that combine CRM, product, and support data. For organisations with fewer than 50 customer accounts per CSM, a well-configured CRM provides sufficient functionality. For CSM teams managing 50 or more accounts per person, a purpose-built CS platform with CRM integration typically reduces administrative overhead significantly and improves early warning capability.

How do you measure the effectiveness of customer success using CRM data?

The primary metrics for customer success effectiveness from CRM data are: gross revenue retention (GRR: percentage of contracted revenue retained at renewal, excluding expansion), net revenue retention (NRR: GRR plus expansion revenue as a percentage of total contracted revenue), health score accuracy (do accounts with high health scores renew at higher rates than accounts with low scores? if not, the health model needs recalibration), time to first value (for new customers, how many days from contract signature to the first documented value milestone), and QBR completion rate (what percentage of accounts in the book of business have had a QBR in the last 90 days). Report all five metrics monthly and compare against the prior quarter to identify trends.