DEV Community: James Dong

Health Scores Are Theater: The Score Isn't the Product, the Response Is

James Dong — Thu, 07 May 2026 16:14:17 +0000

By Chinmay Pingale, Co-founder of Cuelock.

Originally published on cuelock.com/blog.

I'll be blunt. Most CS teams have built a beautifully calibrated health score that their team quietly ignores every single week.

The weighting is thoughtful. The colors are crisp. The red accounts glow like a warning system on a bridge. And when one lights up, the CSM sees it, opens Slack, sends a vague message to someone who might know the account, and then moves on to the next fire. Three weeks later, a VP asks what happened with that customer and nobody has a clean answer.

The score worked. The response didn't exist.

This is what I mean when I say health scores are theater. Not that they're useless. But treating the score as the deliverable is the same mistake as a software team that instruments every alarm in their observability stack and then builds no incident response process. The monitoring fires perfectly. The system still goes down. You knew something was wrong. You just didn't know who owned it, what the first three steps were, or whether the fix actually held.

That's where most CS organizations live right now.

The Dashboard That Did Everything Except Help

I've worked with CS teams that had genuinely impressive health score setups. Weighted signals across product usage, support ticket volume, NPS trends, and executive engagement. The scores updated in near real-time. Leadership could look at the dashboard and see exactly which accounts were in trouble.

What they couldn't see was what happened next.

When I dug into how accounts were actually managed after turning red, the pattern was almost always the same. The CSM who happened to own the account decided what to do. They pulled from memory, personal judgment, and whatever relationship they had with the account. Sometimes it worked. Often it was too slow, inconsistently executed, or invisible to the rest of the team. And when it didn't work, no one could tell you why, because nothing was captured.

At one company I worked with, the CS team had invested the better part of a year building a health score model. It was genuinely good. Their CSMs knew who was at risk. Their churn rate barely moved.

The score was fine. The system around the score was missing.

Ask yourself: when your riskiest account turned red last quarter, what happened next? Was there a clear owner? A documented response? A defined set of steps the whole team would recognize? Or did it come down to whoever was paying attention that week, and whatever they felt was right in the moment?

If the honest answer is the second one, you haven't built a risk management system. You've built a risk awareness system. And awareness without action is just anxiety with a dashboard.

The Response Is the Product

Here's the thing most CS leaders miss. The health score is an input, not an output. It tells you where to look. What you do after that is the actual work, and it's where all the retention value lives.

The teams I've seen outperform on retention share one trait. They treat the response as a repeatable system. Not heroics. Not whoever happens to be sharpest that week. A defined set of steps, owned by a specific person, with a documented outcome at the end.

Simple. Boring. Effective.

This doesn't need to be complicated. When an account hits a risk threshold, who leads? What context gets pulled in immediately? What outreach gets sent, in what order, by whom? Where do the actions live so the whole team can see what's happening? What counts as resolved versus what counts as still open?

When those questions have clear answers before the account turns red, your team executes consistently. When they don't, your team improvises. And improvisation at scale is just organized chaos.

I watched a mid-market services company run this exact transformation. Not because they rebuilt their health score. They didn't touch it. They built a structured response process around the score they already had: clear ownership, a documented playbook for their top three risk types, and a single place to track every case. Post-sale escalations dropped by about 35% over two quarters. Same data. Different execution layer.

This is the gap Cuelock is built to fill. When an account triggers a risk signal, the question isn't just "who sees it?" It's "what happens next, every time, not just when the right person is paying attention." Structured playbooks, coordinated response, and a record of what actually worked. That's the layer most CS platforms skip entirely. If you want to dig into what that looks like in practice, the startup CSM playbook walks through how to build that execution layer from scratch.

The Score Is Not the Finish Line

Getting your health score to amber or red should feel like a starting gun, not a summary. The score tells you a customer needs intervention. The response determines whether they stay.

If your team is good at building health scores but inconsistent at executing against them, you don't have a data problem. You have a process problem. Fix the thing that runs after the alarm, and the alarm starts meaning something.

The score is easy. The response is the work. Build that.

Not sure how much of your CS workflow is still manual? Find out with the AI Readiness Gap Finder.

About Cuelock

James and Chinmay Pingale are the co-founders of Cuelock, a customer success platform for SaaS teams. Learn more about the team or read more posts on the Cuelock blog.

55% of Customer Calls End Without Clear Next Steps: The Hidden Cost for CS Teams

James Dong — Mon, 04 May 2026 18:14:08 +0000

By Chinmay Pingale, Co-founder of Cuelock.

Originally published on cuelock.com/blog.

According to Microsoft's 2023 Work Trend Index, a survey of 31,000 workers across 31 countries, 55% of workers say next steps at the end of a meeting are unclear.

That stat comes from enterprise collaboration research, not a customer success report. But if you're running a CS team and those are your calls, that number has a direct dollar value attached to it.

Every unclear next step from a customer call is a commitment that may never reach a system of record. No CRM entry. No task assigned. No owner. When the customer follows up three weeks later about the thing you promised, someone opens Slack and tries to reconstruct what happened from memory.

That's not a process. That's hoping someone was paying attention.

The Commitment Gap: What the Data Shows

The problem isn't that CSMs don't care about follow-through. It's that the systems they work in weren't designed to make tracking commitments easy, and workload pressure means consistent logging doesn't happen.

Three recent industry surveys point to the same structural failure:

The Microsoft Work Trend Index 2023 (n=31,000 workers, 31 countries) found that 55% of workers say next steps are unclear at the end of meetings.
The Calendly State of Meetings 2024 (n=1,244 US and UK workers) found that 40% of respondents do not receive follow-up notes or action items, naming it a primary driver of meeting unproductivity.
The iBabs State of Meeting Management 2024 (n=2,000+ across corporate, government, non-profit, and healthcare sectors) found that fewer than half of respondents confirmed that action points from their meetings were adequately tracked and followed up.

These surveys aren't CS-specific. They cover every kind of professional meeting. Which makes the pattern more alarming, not less: the commitment-tracking failure is industry-wide, and CS teams operate inside the same broken infrastructure as everyone else.

Signal	Stat	Source
Workers who say next steps are unclear at meeting's end	55%	Microsoft Work Trend Index, 2023
Workers who receive no follow-up notes or action items	40%	Calendly State of Meetings, 2024
Respondents who confirm action points are adequately tracked	Under 50%	iBabs State of Meeting Management, 2024
CSMs who say their workload and schedule is realistic	40%	ChurnZero + SuccessCOACHING, 2024
Sellers who struggle to complete assigned tasks efficiently	77%	Gartner, 2023

The gap between a commitment made on a call and a task that has an owner is where retention revenue disappears.

Why CSMs Can't Keep Up

Here's the thing. Even if a CSM wants to log every commitment from every call, the arithmetic doesn't work out.

The ChurnZero and SuccessCOACHING 2024 CSM Confidential Report surveyed CSMs across the industry and found that only 40% say their workload and schedule is realistic, and only 41% say they can complete their work without evenings or weekends. CSMs specifically called out administrative tasks (logging customer notes, updating CRM records, managing follow-up queues) as core contributors to unsustainable workloads.

Gainsight's 2024 State of AI in Customer Success report (250+ companies across North America and Europe) found that AI saves CS teams more than 10 hours per week by automating data entry and repetitive tasks. The inverse of that number is telling: CS teams are currently spending 10+ hours weekly on work that should be automatic. That's time that isn't going to logging commitments.

Salesforce's State of Sales Fifth Edition (n=7,775 reps) reinforces this from the sales side: 68% of reps say note-taking and data input are their most time-consuming tasks, and sales reps spend only 28% of their week on actual selling. The administrative drag on customer-facing teams isn't a CS-specific problem, but in CS, the consequence isn't a missed quota. It's a missed renewal.

All of this points to a capacity problem, not a motivation problem. CSMs aren't forgetting commitments because they're careless. They're forgetting them because they're managing too many accounts, with too much manual work, and no structural safety net designed to catch what falls through the cracks.

What Falls Through

Not all untracked commitments damage retention equally. Some are minor: a resource to send, a quick check-in scheduled for next month. But the commitments that actually drive churn tend to cluster around a few specific categories.

Integration and configuration promises. "We'll have the SSO connection set up by next Friday." When that doesn't happen and nobody tracked the commitment, the customer is waiting while your team has moved on to other fires. By the time the customer follows up, it's framed as a pattern, not an incident.

Success milestone commitments. "I'll loop in our solutions team to get you to advanced reporting before Q3." These span multiple months and involve stakeholders across your organization. Without structured tracking, they quietly evaporate between QBRs.

Risk acknowledgments. "I hear you. The reporting gaps are a problem, and I'll flag that with product this week." If the CSM doesn't log this as an open item, the customer surfaces it again in 45 days, to a different CSM who has no context and no idea a commitment was made.

Renewal prerequisites. "Before we can expand the contract, we need to make sure you're hitting X outcome." If that prerequisite isn't tracked, the renewal conversation arrives without the shared context required to close it on good terms.

These aren't edge cases. They're the ordinary content of customer calls. A CSM managing 35 accounts is making commitments like these every single day. According to the iBabs and Microsoft data, fewer than half of those commitments will be adequately tracked.

The Connection to Churn

The link between untracked commitments and churn is causal. When a customer surfaces a missed commitment in a renewal conversation, they're not flagging an administrative failure. They're communicating a pattern: your team said it would do something and didn't, more than once. By the time it comes up in a renewal, the trust has already been eroding for months.

As we've covered when examining health scores and risk response: the failure mode isn't usually that CS teams lack awareness. It's that awareness doesn't reliably translate into action. Missed commitments follow the exact same pattern. The CSM knew the commitment was made, but without a system to surface it, nothing happened.

The startup CSM playbook makes the underlying point clearly: retention is a function of whether the customer believes your team does what it says it will do. Untracked commitments erode that belief silently, long before any health score turns red and long before anyone inside the CS team realizes a problem is developing.

According to Gartner's 2023 seller efficiency survey (n=501), 77% of sellers struggle to complete their assigned tasks efficiently. When sellers are struggling, deals slip. When CSMs are struggling, and the ChurnZero data shows they are, commitments slip. The outcomes are structurally similar, but the metrics used to measure them look very different on a dashboard.

Bottom line: a commitment made on a customer call is only a commitment if it has an owner, a deadline, and somewhere to live.

What This Means for Your Team

If your team is managing more than 30 accounts per CSM (not sure where you stand? check with the Capacity Planner), the commitment-tracking problem isn't hypothetical. It's happening. At 30+ accounts, a diligent CSM makes 3–5 customer commitments per day across calls, emails, and async threads. Manually logging all of them isn't realistic without a system purpose-built to handle it.

The question isn't whether commitments fall through the cracks. The question is how many are falling through right now, and whether you'll find out before or after the customer escalates or churns.

A simple diagnostic: pull the recordings or notes from your last 10 customer calls. Count the commitments made. Then check how many were logged to your CRM or CS platform within 24 hours. If the answer isn't "nearly all of them," you have a tracking gap, and you're likely not the only team on your roster dealing with it.

What to Do About It

Set a minimum logging standard. Every customer call produces at least one logged output: a completed action item, an open commitment, or an explicit "nothing to track" marker. The absence of a record should be the exception, not the default.
Distinguish commitments from activities. Most CS platforms track activities well: calls logged, emails sent, tickets opened. Fewer separate out commitments, the specific promises made during those activities. These are different data types and need distinct tracking. A "call logged" entry doesn't tell you what was promised.
Build a resolution loop. Tracking commitments is only half the work. The other half is tracking whether they were fulfilled. Knowing a commitment was made but not knowing if it was delivered leaves the same trust gap as not tracking it at all.
Close the loop with the customer. When a commitment is fulfilled, send a brief confirmation. This isn't bureaucracy. It's a signal to the customer that your team follows through. That signal compounds over a contract lifecycle and is one of the strongest predictors of a clean renewal conversation.
Reduce the manual surface area. Tools like Cuelock are built specifically for this gap: capturing commitments at the point they're made, assigning owners, and surfacing open items before they become escalations or missed renewals.

The data here points to a systemic problem, not individual failures. The fix isn't asking CSMs to work harder or be more diligent. They're already at capacity. The fix is building a system that makes commitment tracking the default, not the exception.

Methodology / Sources: Data in this post is drawn from the Microsoft Work Trend Index 2023 (n=31,000 workers across 31 countries), the Calendly State of Meetings 2024 (n=1,244 US and UK workers), the iBabs State of Meeting Management 2024 (n=2,000+ respondents across corporate, government, non-profit, and healthcare), the ChurnZero + SuccessCOACHING 2024 CSM Confidential Report, Gainsight's 2024 State of AI in Customer Success (250+ companies), the Salesforce State of Sales Fifth Edition (n=7,775 reps), and the Gartner 2023 seller efficiency survey (n=501). The Microsoft, Calendly, and iBabs survey populations include general professional workers, not CS-specific respondents. CS-specific data is noted where sourced from CS-focused reports.

Sources

About Cuelock

James and Chinmay Pingale are the co-founders of Cuelock, a customer success platform for SaaS teams. Learn more about the team or read more posts on the Cuelock blog.

The Best Customer Churn Dashboards and Software for 2026

James Dong — Thu, 23 Apr 2026 16:37:52 +0000

By Chinmay Pingale, Co-founder of Cuelock.

Originally published on cuelock.com/blog.

I'll be blunt. Most churn software tells you who's about to leave. Very few help your team actually do something about it.

That distinction matters more than any feature checklist. You can have the sharpest health scores in the industry, a dashboard that would make a data team weep with joy, and AI that predicts churn with 94% accuracy. None of it matters if your CSM stares at the alert, opens Slack, types a vague message to someone who may or may not be the right person, and then moves on to the next fire.

The gap between "knowing" and "doing" is where most retention revenue dies. So that's the lens we used for this list.

We evaluated seven tools across a spectrum: enterprise CS platforms, real-time engagement engines, structured risk-response systems, payment recovery specialists, and lightweight starters. Each entry covers what the tool does well, where it falls short, directional pricing, and who it's best suited for.

Quick View

One column worth paying attention to: Resolution Tracking. That's the ability to capture not just that an account was at risk, but how the risk was handled and what outcome it produced. Most dashboards don't track this at all. It's the difference between knowing your churn rate and knowing why it is what it is.

Tool	Best For	Health Scores	Playbooks	Resolution Tracking	AI Features	Free Tier
Cuelock	At-risk response	Yes	Core strength	Core strength	Yes	Yes
Gainsight	Enterprise CS	Yes	Yes	Limited	Yes	No
ChurnZero	Churn scoring	Yes	Yes (Plays)	Limited	Yes (Agents)	No
Vitally	Growth-stage SaaS	Yes	Yes	Limited	Yes (Copilot)	Trial
Totango	Modular workflows	Yes	Yes (BLOCs)	Limited	Yes	Yes
Churn Buster	Payment recovery	No	No	Payments only	No	No
Custify	Small teams	Yes	Basic	No	No	Trial

1. Cuelock: Best for Structured At-Risk Account Response

Here's what probably happens at your company today. An account shows signs of risk: usage drops, a key champion goes quiet, a support ticket escalates. Your CSM gets an alert. Maybe from your CS platform, maybe from a Slack bot, maybe from gut instinct.

Then what?

They improvise. They ping someone in Slack who might know the account. They draft an email that may or may not hit the right tone. They log a note somewhere, maybe. Three weeks later, a VP asks "what happened with that account?" and nobody has a clean answer.

Cuelock exists to kill that cycle. When an account triggers a risk signal, the CSM doesn't get an alert and a prayer. They get a situation-specific playbook that tells them exactly what to do: which stakeholders to pull in, what outreach to prepare, what sequence of actions has worked for this type of risk before.

What stands out

Playbooks built around the risk, not the metric. A usage drop and a champion departure are different problems. Cuelock treats them differently. The response plan adapts based on risk type, account context, and relationship stage.
Coordination that actually happens. The right people get pulled in automatically. No more hoping someone saw the Slack thread or remembering to loop in the account exec.
Resolution history you can learn from. Every action on every at-risk account is captured without the CSM doing extra logging. Over time, this gives leadership a real record of what risks were identified, how they were handled, and what actually worked. That's the data most CS orgs are flying blind without.
A system that compounds. Teams build and refine their own playbooks as they go. Six months in, your risk response isn't just faster. It's smarter than it was on day one.

If I were reading this as a skeptical CS leader, I'd probably think: "We already have playbooks in our CS platform." Well, ask yourself: when an account went red last quarter, did your team execute a consistent, documented response, or did they wing it? If the answer is "it depends on the CSM," that's the gap Cuelock closes.

Pricing

Contact Cuelock directly. The platform is built for mid-market and enterprise CS teams managing meaningful portfolios.

Best for

CS teams past the "just monitor churn" phase who need a repeatable system for responding to risk. Especially strong where multiple people touch at-risk accounts and leadership wants visibility into how those situations are handled.

Honest limitation

Cuelock is purpose-built for the risk-response layer. It doesn't replace your health scoring or product analytics platform. You'll likely pair it with another tool on this list, and that's by design. It's the execution engine, not the dashboard.

2. Gainsight CS: Best for Enterprise Customer Success at Scale

Gainsight is the tool everyone benchmarks against, and there's a reason for that. It has the deepest feature set in the category: health scoring, journey orchestration, product analytics (via Gainsight PX), customer education (Skilljar), community management, and AI-powered sentiment analysis through Staircase AI. If your CS org runs a complex, multi-touch post-sales motion across hundreds of accounts, Gainsight can handle it.

The trade-off is real, though. Gainsight implementations are measured in months. You will need a dedicated admin or ops resource to keep the system calibrated. And the UI, while powerful, shows its age compared to newer entrants like Vitally.

I've heard from multiple CS leaders that Gainsight delivers tremendous value once it's dialed in. The problem is getting it dialed in. If you have the team and the budget, it's the category leader for a reason. If you don't, you'll be paying enterprise prices for a fraction of the platform's capability.

Key capabilities

Customer 360 profiles with configurable health scorecards
Journey Orchestrator for automated multi-step engagement
Cockpit CTAs and Playbooks for daily task management
Renewal Center for revenue forecasting
Deep Salesforce, Zendesk, Snowflake, and ServiceNow integrations

Pricing

Custom, quote-based. Third-party estimates put it starting around $2,500/month, with enterprise contracts commonly running $23,000 to $60,000+ annually depending on seats and data volume. Implementation can add $10,000 to $50,000 on top.

Best for

Large CS organizations (10+ CSMs) with dedicated ops resources, complex customer segments, and the budget to invest in a platform they'll grow into over years.

Honest limitation

Long implementation, steep learning curve, and pricing that's out of reach for most sub-50-person companies. Some reviewers on G2 and Capterra describe the system as "clunky" once you get past the core workflows.

3. ChurnZero: Best for Real-Time Engagement and Churn Scoring

ChurnZero is built specifically for SaaS subscription businesses, and it shows. The platform's core strength is real-time customer health tracking paired with in-app engagement, meaning your team can both see risk and act on it without leaving the tool.

The Churn Score aggregates usage data, support interactions, and engagement signals into a single risk indicator. From there, automated Plays trigger based on customer behavior: onboarding sequences, adoption nudges, renewal prep, risk intervention. In 2025, ChurnZero added AI Agents that go beyond alerting to actively draft outreach and execute playbook steps.

Where ChurnZero shines is the middle of the market. It's lighter than Gainsight but more capable than entry-level tools. The Command Center gives CSMs a centralized view of their portfolio that's genuinely useful day-to-day.

Key capabilities

Real-time churn scoring across usage, support, and engagement data
In-app communication: walkthroughs, tooltips, announcements
Automated Plays triggered by customer behavior
AI Agents for task execution and personalized outreach at scale
Strong Salesforce and HubSpot CRM integrations

Pricing

Custom, quote-based. Published benchmarks suggest the Professional tier runs $15,000 to $39,000 annually for 10 users and 500 managed accounts. Enterprise pricing scales with user count and account volume. Costs can escalate quickly as you grow.

Best for

Mid-market SaaS companies (5 to 20 CSMs) that want deep product usage visibility combined with in-app engagement. Especially strong if you're a SaaS product and want to meet customers inside your app, not just in their inbox.

Honest limitation

The interface has a learning curve. Multiple reviewers describe the onboarding period as overwhelming. And while Plays are powerful, they're closer to automated sequences than true situation-specific playbooks. The "what to do" still often lives in the CSM's head.

4. Vitally: Best for Fast-Growing SaaS Teams That Value Speed

Vitally has earned its momentum. It combines a clean, modern interface with genuine depth: health scoring, automated playbooks, project management for customer milestones, collaborative docs, and an AI Copilot that generates summaries and drafts replies from unstructured data like transcripts, notes, and tickets.

What sets Vitally apart from the incumbents is time-to-value. Where Gainsight measures implementation in months, Vitally measures it in weeks. Where ChurnZero requires meaningful configuration before CSMs see benefit, Vitally tends to click faster for the end user.

The platform works across tech-touch, hybrid, and high-touch models without forcing you to choose upfront. That flexibility matters a lot for teams in a growth phase where the CS model is still being defined.

Key capabilities

Dynamic, configurable health scores with multiple data inputs
Automated playbooks for onboarding, renewal, and risk workflows
Collaborative Docs for shared success plans with customers
AI Copilot for summaries, suggested actions, and customer Q&A
Hubs for organizing workflows by team, segment, or process

Pricing

Custom, quote-based across three tiers: Tech-Touch, Hybrid-Touch, and High-Touch. Free trials available. Vitally is generally positioned as more accessible than Gainsight or ChurnZero, though specific pricing isn't published.

Best for

B2B SaaS companies in a growth phase (3 to 15 CSMs) that want a modern, flexible CS platform without a multi-month implementation project.

Honest limitation

Smaller integration ecosystem compared to Gainsight. Some users on Capterra note that viewer seat limits feel restrictive, and the breadth of features takes time to fully extract value from.

5. Totango: Best for Modular, Composable CS Workflows

Totango takes a different architectural approach. Instead of giving you a monolithic platform and asking you to configure it, Totango offers SuccessBLOCs, pre-built, customizable workflow modules for specific CS motions like onboarding, adoption tracking, renewal management, and churn prevention. You snap together the pieces you need and add more as you grow.

This composable model is genuinely useful for teams that know they need more than spreadsheets but aren't ready to buy into a full-stack platform. The free Community edition (up to 100 accounts) lets you test the approach before committing budget.

Totango merged with Catalyst in recent years, which expanded the feature set and data integration layer. The Spark integration framework connects well to common data sources.

Key capabilities

SuccessBLOCs: modular, templatized customer journey workflows
Dynamic segmentation based on real-time health and usage signals
Automated task creation and engagement sequences
Spark integration layer for connecting data sources
Free Community edition for small teams (up to 100 accounts)

Pricing

Free Community plan available. Paid tiers (Starter, Growth, Enterprise) are quote-based, with Growth estimates starting around $2,500/month.

Best for

Teams that want to start small and scale modularly. Also a strong fit for organizations that have tried and failed to implement a larger platform and want a more incremental approach.

Honest limitation

The modular approach can feel like a patchwork once you're running five or six SuccessBLOCs simultaneously. Reporting and analytics are less robust than Gainsight. The Totango + Catalyst integration is still being refined. Expect some rough edges.

6. Churn Buster: Best for Recovering Revenue Lost to Failed Payments

Churn Buster solves a different problem than everything else on this list, and it's a problem most CS teams underestimate: involuntary churn from failed payments. Expired cards, insufficient funds, gateway errors, fraud blocks. For subscription businesses, this can quietly account for 20-40% of total churn.

Your billing platform has default retry logic for this. Churn Buster's argument, backed by over a decade of data across 1,000+ subscription businesses, is that default logic leaves significant revenue on the table. Different decline types need different retry timing and different customer communication. An insufficient funds decline is not the same as an expired card, and treating them the same costs you money.

Median recovery rates across their customer base sit around 50%, with top B2B SaaS performers hitting 80 to 90%. At those numbers, the ROI math is hard to argue with.

Key capabilities

Smart retry logic tailored to specific decline types
Personalized recovery campaigns across email, in-app, and SMS
Analytics showing which decline types, segments, and campaigns perform best
Native Stripe, Recharge, Shopify, Recurly integrations
Strategic advisory included, not just self-serve tooling

Pricing

Based on recovered revenue. Churn Buster reports typical ROI of 10x+. Contact them for specifics.

Best for

Any subscription business (SaaS or ecommerce) losing meaningful revenue to failed payments. Especially valuable if you've never optimized your dunning process beyond whatever Stripe or your billing platform ships by default.

Honest limitation

Payment recovery only. No health scoring, no CS workflows, no voluntary churn management. You'll use this alongside another tool on this list, not instead of one.

7. Custify: Best for Small SaaS Teams Getting Started

If your CS team is one to five people and you're currently managing churn risk in spreadsheets, CRM notes, or your head, Custify is a solid first step into purpose-built tooling. It offers health scoring, lifecycle automation, renewal tracking, and basic playbook functionality at a price point that won't require a board-level conversation.

Custify's strength is simplicity. The learning curve is gentle, time-to-value is measured in days, and you can be operational before your trial expires. It's not going to blow you away with AI or advanced analytics, but it will get your team off spreadsheets and into a system that actually tracks customer health.

Key capabilities

Configurable health scores based on usage, support, and engagement
Automated task creation and lifecycle workflows
Renewal and expansion tracking
360-degree customer view with activity timeline
Integrations with Stripe, HubSpot, Salesforce, Slack, and Segment

Pricing

Starts around $999/month for the Starter plan. Growth and Enterprise tiers are quote-based. Free trial available.

Best for

Early-stage SaaS companies with small CS teams that need a purpose-built platform without enterprise complexity. The "first real CS tool" for most teams in this stage.

Honest limitation

You'll likely outgrow it. Analytics and reporting are basic compared to mid-market options. Automation is limited. Once your team passes 10 to 15 people, you'll probably be shopping for something with more depth.

So, Which One?

Knowing if any of these tools are right for you comes down to where your current process breaks.

If the problem is visibility, meaning you don't know who's at risk until it's too late, start with a health-scoring platform. Gainsight for enterprise, ChurnZero or Vitally for mid-market, Custify or Totango if you're early.

If the problem is response, meaning you see the risk but your team's follow-through is inconsistent, improvised, or invisible to leadership, that's Cuelock's lane.

If the problem is payment failures, and you've never touched your default dunning logic, Churn Buster will almost certainly pay for itself.

Most mature CS teams end up with two or three tools from this list. A common stack: a health-scoring platform for visibility, Cuelock for structured risk response, and Churn Buster for payment recovery. That covers identification, action, and involuntary churn in one motion.

Reducing churn is hard. No single tool solves it. But the teams that treat churn response as a system, not a scramble, are the ones that move the needle quarter over quarter. The right stack just makes that system possible.

About Cuelock

James and Chinmay Pingale are the co-founders of Cuelock, a customer success platform for SaaS teams. Learn more about the team or read more posts on the Cuelock blog.

How to Implement Customer Success for Non-SaaS Companies

James Dong — Sun, 19 Apr 2026 01:50:15 +0000

By Chinmay Pingale, Co-founder of Cuelock.

Originally published on cuelock.com/blog.

I'll be blunt. Customer Success for Non-SaaS companies is not about relationship building. It's about operational reliability under pressure.

Look, most traditional businesses already "have relationships." That's not the bottleneck. The bottleneck is what happens when something goes wrong. Orders slip. Projects stall. Renewals get wobbly. Information lives in emails, Slack, and one person's head. In those moments, your organization behaves like a system without error handling.

Customer success, done well, is the layer that adds that error handling. It's the discipline that turns messy, person-dependent heroics into a repeatable production process. Well instrumented. Well rehearsed. Well documented.

Why this matters? Because retention in non-SaaS compounds slowly and punishes mistakes quickly. Every prevented churn event is not just saved revenue, it's saved distraction, saved cost-to-serve, and saved organizational whiplash.

How CS differs from account management

Account management optimizes for relationship and revenue capture. Customer Success optimizes for outcomes and risk reduction.

For account management, the unit of work is the account. For CS, the unit of work is the situation. A risky implementation. A delayed shipment. A troubled renewal.

In my experience at companies like ServiceChannel, the best teams had both. Account managers owned the commercial relationship. CS owned the health of the delivery system. When that line blurred, things got sloppy fast.

Why Non-SaaS companies are adopting CS now

Complexity has outrun memory.

More products. More integrations. More stakeholders. More bespoke work. You can't run a modern non-SaaS business on institutional knowledge and hallway handoffs. Customer Success is how you encode that tribal knowledge into a repeatable system that actually works under pressure.

I've seen mid-market industrial suppliers move from "Bob is the system" to structured playbooks that cut renewal escalations by about 50% inside a year. Same revenue. Far less chaos.

When customer success actually makes sense

Business models where CS tends to work

Examples include, but are not limited to:

Subscription or recurring contracts
Long implementation cycles
High switching costs
Complex delivery or service models
Multi-stakeholder buyers

In other words, Customer Success isn't about being nicer to customers, it's about managing operational risk that Sales can't and Delivery won't. If your revenue depends on what happens after the contract is signed, you need a dedicated layer that owns that reality, documents it, and improves it over time. If it doesn't, adding CS just creates another team in the loop without changing any outcomes.

Common pitfalls for non SaaS teams

Renaming Account Managers as "CSMs" tends to look like progress on a slide while changing very little in practice. Incentives stay the same, workflows stay the same, and when the next high-stakes moment hits, you still rely on heroics. It's the organizational equivalent of shipping code straight to production without tests you absorb all the risk and get none of the reliability.

The other traps are quieter but just as costly. Teams build elaborate health scores that look impressive in dashboards and get ignored in real life, adding maintenance work without reducing risk. Leaders treat Customer Success purely as a cost center, which optimizes for activity instead of outcomes. And when Sales or Delivery create systemic problems, those issues get routed to individual CSMs, slowly burning them out rather than fixing the underlying system. Cosmetic changes feel safe. They don't move the needle. Real progress starts when you change how the system actually works.

Signs you're ready for a CS function

Ask yourself a few simple questions. Do you regularly hit high-stakes moments where retention is on the line? When those moments arrive, does the response depend on who happens to be on shift? And after the fire is out, do you actually extract lessons, or just move on and hope it doesn't happen again?

If the answer to any of these is yes, you're not ahead of the curve. You're already behind it.

Step 1: Define Your Outcome

Success is not "happy customers." It's durable retention, predictable renewals, and fewer fire drills. Write this down in one sentence. If you can't, you're not ready to build anything.

Sales, Delivery, and Finance need the same definition of success. If Sales sells unrealistic timelines, CS inherits impossible risks.

At a facilities management company I worked with, simply aligning on a single "successful go-live" definition reduced post-sale escalations by roughly 30% over two quarters. Clarity compounds.

What you get: a north star that makes every later decision easier.

Step 2: Choose Your CS Model

High touch vs. scaled vs. hybrid

For high-touch: deeper relationships, fewer accounts, higher cost, stronger risk mitigation.

For scaled: lighter coverage, more automation, lower cost, more variance in outcomes.

The primary difference is control versus efficiency. Most non-SaaS companies land in hybrid. High-touch for strategic accounts, scaled for the long tail.

Who owns onboarding

Here's the thing. If onboarding is messy, CS will spend its life cleaning it up.

My default: Delivery owns execution. CS owns clarity of milestones and risk escalation paths. In the case that you don't have a dedicated Delivery team, it does make sense for CS to own it, but it's crucial to have the correct playbooks in place.

Relationship between sales, implementation, and CS

Sales sells. If you have a delivery or implementation team, they build and execute. Customer Success keeps the train on the tracks after launch. If you don't have a separate delivery team, then Sales closes and hands the relationship to CS, and CS effectively owns post-sale execution and risk. In both cases, the principle is the same: clear lanes reduce friction, and ambiguity creates it.

When those lanes are fuzzy, handoffs turn into blame games and every escalation becomes a debate about "who dropped it." When they're crisp, risk gets owned in the right place and problems get solved faster. What you get is fewer turf wars, smoother transitions, and more forward motion.

Step 3: Build Core Processes

Onboarding

Start by making your milestones undeniable. Create one single source of truth that everyone points to, not three spreadsheets and a shared drive no one checks.

Next, assign real owners to every milestone. Name a person, not a team, and make it explicit who moves the ball forward when things slip.

Finally, define what "off track" actually means before you're in the middle of a crisis. Is it a missed date? A budget overrun? A stakeholder going quiet? Spell it out.

Simple. Boring. Effective.

Success Review / Check Ins

Don't overcomplicate this. A good quarterly review fits on three slides outcomes, risks, and next steps. Outcomes keep you honest about value delivered, risks force you to surface what everyone can see but avoids saying, and next steps create forward motion instead of vague agreement. If you can't run that meeting crisply, no amount of tooling will save you.

I've seen teams at companies like Schneider Electric standardize this simple format and cut "surprise" renewals by more than half within a year. The template didn't win deals by itself. The discipline did.

Risk management and intervention

So the account gets flagged as "at risk," and now you're in production, not planning.

You're moving through your day, and then a critical customer misses a milestone. The Slack pings start. Calendars explode. Pressure spikes. What happens next?

In the good version, there's a clear playbook. You know who leads, what context gets pulled in, and where every action is tracked. In the bad version, everyone reacts in parallel email threads, context fragments, and the loudest voice wins.

Structure beats heroics.

Renewal or expansion workflow

Don't design your renewal process in the final 30 days before a contract comes due. That's when pressure is highest and judgment is worst. The work has to be done while things are calm, not when they're on fire.

Be explicit about the mechanics. Who drafts the renewal? Who is responsible for surfacing risks early? Who owns escalation if something goes sideways? Write it down and make it repeatable instead of relying on memory or goodwill.

When you do this well, you replace end-of-quarter chaos with steady, predictable motion.

Step 4: Staff and Roles

First CS hires

A good first Customer Success hire is less a people person in a title and more a systems person who happens to be good with people. They naturally see broken flows before anyone else, own risk instead of deflecting it, and understand how customer outcomes connect to revenue rather than optimizing only for "happiness." They're steady in high-stakes moments, credible with Sales and Delivery from day one, and disciplined about documenting and standardizing what actually works. In practice, you're better off with a system builder who can grow their relational muscle than a pure relationship manager who can't build anything that lasts.

Every business calibrates this differently, and that's fine. A complex services firm will need a different profile than a distributor or a manufacturer, so there isn't one universal "right" archetype. Frankly, your very first CS hire probably won't be perfect, and that's normal. In early-stage functions you learn by doing, which means you'll likely iterate on people as much as on process. Cycling through a hire or two while you figure out what you actually need is not a failure of strategy, it's part of building a function that can scale.

CS vs. Account Manager responsibilities

Account Managers are naturally oriented toward the commercial side of the house, how to protect and grow revenue, manage the contract, and navigate pricing and negotiations. Customer Success, by contrast, is oriented toward the health of the account and the mechanics of risk resolution whether milestones are being hit, issues are being surfaced early, and problems are being resolved in a durable way. Both roles create real value, just in different parts of the customer lifecycle. Unless your team is very small or your model is unusually simple, collapsing them into a single role tends to blur incentives and weaken both motions rather than making things cleaner.

Team scaling

When you scale a CS team, the order matters. Start centralized so you can see patterns, agree on what "good" looks like, and standardize how work actually gets done. Only then should you decentralize and embed CS more deeply with different segments, regions, or product lines.

If you push autonomy too early, you don't scale expertise, you scale inconsistency. Done in the right sequence, you end up with a team that compounds its learning instead of fragmenting into isolated silos.

Step 5: Tools and Systems

Health scores

Use health scores lightly. They're best treated as signals, not oracles. A score can nudge you to look closer, but it shouldn't replace judgment or context. When teams start treating a number as ground truth, they stop listening to what's actually happening with the customer.

The key isn't perfect accuracy. It's creating a shared language about risk that Sales, Delivery, and CS can all recognize. A simple, imperfect score that gets everyone aligned and talking about the same problems will outperform a "precise" model that no one trusts or uses.

CS management

Your CRM should remain the system of record for accounts, contracts, and activity. But when customer risk surfaces, speed without alignment is just chaos in motion, and a CRM is a poor place to run that moment. You need a dedicated space where the team can move fast, stay aligned, and execute a clear, repeatable response so CSMs can focus on the right actions, pull in the right people, and prevent issues from slipping through the cracks. This is exactly the gap Cuelock is built to fill, especially for non-SaaS companies that need more structure and systems around onboarding, renewal, and risk. It gives teams a structured workspace for running playbooks, coordinating stakeholders, and capturing what actually happened so the organization can learn from it and steadily raise its standard for managing customer risk.

Practical 90 day playbook

This is not meant to be prescriptive, but instead a blueprint that worked for me, and the companies I've helped. The best thing you could do is take inspiration and apply it meaningfully to your organization.

Month 1: Get clear and pick your wedge

Define success in one sentence. Be explicit about the outcome you care about most. For example: "Reduce last-minute renewal escalations for our top 20 accounts." Write it down and socialize it with Sales, Delivery, and Finance. If people don't nod to the same definition, you're not aligned.

Map your riskiest customer moments. List the 5 to 7 moments that reliably create pain. Examples include, but are not limited to: delayed go-lives, missed milestones, scope creep, executive escalations, or renewal surprises. For each one, note who is involved, what usually breaks, and where information lives today.

Pick one risk scenario to standardize. Choose the moment that is both frequent and high stakes. Don't pick the hardest or the fanciest pick the one that will move the needle in 90 days. This is your beachhead.

What you get: a focused problem that everyone agrees matters.

Month 2: Ship a simple system that works in the real world

Ship a lightweight playbook for that scenario. Define three things only:

Who leads when this risk appears.
What context must be pulled in immediately.
Where actions get tracked in one place.

Keep it short enough that someone could follow it under pressure.

Train the team by running it, not explaining it. Walk through a recent real example together. Ask: "If this happened again tomorrow, what would we do differently?" Calibrate the playbook based on that discussion.

Start documenting every instance in one place. Create a single home for risk cases. Every time the scenario happens, open a record, follow the playbook, and capture what actually occurred. This is where your institutional memory begins.

What you get: a working process you can observe and improve, not a slide deck.

Month 3: Measure, iterate, and decide your next move

Measure what actually changes, not what looks good on a dashboard. Start with two simple questions. Did escalations for this scenario meaningfully drop? And did renewals or outcomes feel less frantic and less last-minute? If you can't answer those clearly, your playbook still has too much wiggle room and your tooling probably isn't giving you a clean view of what really happened.

Then iterate from reality, not consensus. Tighten ownership where things stalled, simplify steps that people quietly bypassed, and strip out anything that created friction without reducing risk. This is where having a single, structured place like Cuelock to run and review your risk cases pays off you can see patterns instead of relying on memory or scattered Slack threads. Your goal is fewer surprises, not a prettier process.

Finally, decide whether to expand with discipline. If the first scenario is running cleanly, pick a second high-impact risk moment and repeat the cycle. If it isn't, stop. Fix what you have before you scale it.

About Cuelock

James and Chinmay Pingale are the co-founders of Cuelock, a customer success platform for SaaS teams. Learn more about the team or read more posts on the Cuelock blog.

The Ultimate Startup CSM Playbook

James Dong — Sun, 19 Apr 2026 00:33:51 +0000

By Chinmay Pingale, Co-founder and CEO of Cuelock.

Originally published on cuelock.com/blog.

In this guide, we'll explore how Customer Success has evolved from a support function primarily oriented to enterprise companies to a well recognized growth framework for high-growth startups. We'll dive into operationalization of these principles and how they can be applied to build a scalable, revenue-driving CSM motion.

Why Customer Success is a Growth Engine

From an emotional standpoint, winning new deals is the best feeling in the world, but from a revenue standpoint, recurring deals go much farther. A study from Harvard Business Review says customer retention rates by 5% can increase profits by 25% to 95% through the economics of loyalty and retention.

Anecdotally, I've heard that companies like Ontic invest more into their retention than new sales. Keeping a customer is more important to them than getting a new one, if they had to pick one. Knowing if this is right for you comes down to a simple thought exercise. Ask yourself, "is it more work to prospect, sell, legal, and onboard a customer or provide value to an existing customer and have a renewal discussion (little legal, no prospecting, no onboarding).

What I made my unique advantage, and you can too, is investing more than your competitors into retention, especially because the ROI on that is much higher.

Nonetheless, hopefully by this point you know retention and customer success (CS) is important.

When Startups Should Invest in CSM Playbooks

If you are a business to business company, the best time will likely be much, much sooner than you think. Playbooks do not mean hiring more CSMs, it means encoding a repeatable plan to a certain trigger.

Well, why is it important if you have no CSMs? Firstly, it's to offload the cognitive load on your brain to have to remember the steps. What probably happens today is you jump right into a problem and 'do what feels right'. This is the equivalent in code of rewriting code (you should not do that) when you really should just be creating a repeatable function you can call that does the steps you want it to. The CS equivalent of that is playbooks.

As soon as you start to notice repeated patterns in risk response or onboarding, you should be making a playbook. These are the moments that define if a customer will stick around or not, and having your best set of plays written down will be a huge time, effort, and revenue saver down the line.

If I was reading this as a founder, the first thought to myself would probably be, "In a risk response or onboarding moment, I'm probably not going to go to a document". To that, I have a solution.

The Best CSM Playbook for High Growth Startups

The first thing you must know is that I'm referring to a playbook as the 'bible' of any tumultuous customer facing moments that have a retention impact.

So, what typically are these?

Onboarding is the most universal. Good and bad onboarding can, and very often is, the difference between renewing or cancelling a contract or poc.

The other is risk response. Every company will have different risks they may see. Examples include, but are not limited to:

Reorganization Risk: Point of contact or economic buyer leaves
Budget Cut Risk: Self explanatory!
Usage Dip Risk
Absence Risk: Not showing up to meetings, etc.
Renewal Window Risk: Entering 3 month renewal window

Hundreds more. Every company has their own they'll start to notice repeatedly surface up.

Step 1: Writing Plays

So, where should these documents live? The very best place is somewhere you know you'll find yourself going when the moment happens. For the step by step, I'll explain how you can do it with something more static, like a google document, and something more proactive, like Cuelock.

At this point, you already noticed a repeated risk that your company faces post-sale. For example, let's say you work in a field where reorganization is a common risk type you face.

For documents:

Clear and Specific Risk Identified ("Reorganization Risk")
Summarize ("For Acme, Inc. the most common reorganization risk we see is a champion leaving the firm")
Tasks Order
Summary of the task ("Slack the account manager to let them know that a budget cut risk was identified from Customer Company.")
Assignee ("CSM, CS Manager, Account Manager, Legal, etc.")
Recipient ("Point of contact, decision maker, internal")
Delay before taking the next action
Medium (slack, call, gmail)

For Cuelock:

Create a risk
Input risk name
Input risk summary
Add tasks Order
Summary
Assignee
Recipient
Delay
Medium

Now that your playbook templates have been scribed somewhere, we'll take a look at using them in practice.

Step 2: Using Plays

So the playbook has been written, and now we're in the action. You're going about your day, and then BOOM, one of your customers just informed you, or a CSM, that they are no longer going to be the contact because they are leaving the firm. What happens?

For document playbooks:

Preparation

Open the document
Scroll to the "Reorganization Risk" section
Copy and paste the template into your own document
Change any tasks as you see fit to the situation
Apply the tasks, assignees, recipients, to your specific scenario

Execution

Manually execute each step in order
Once the delay period is done, go to the next step
If resolved, highlight the step at which it was resolved in green

For Cuelock playbooks:

Preparation

Open Cuelock
Click Report Risk
Select the company from the CRM sync
Select the risk
Cuelock pulls context from emails, calls, notes
Cuelock interprets the template
Cuelock creates the case-specific playbook with populated messages, assignees, and recipients

Execution

(In Slack or Cuelock) Select yes, no, edit to execute a task
If resolved, click resolve when Cuelock reminds you of the next step

Here, both ways are effective, but the primary difference is in the manual document way, the cognitive load of remembering, interpreting, and executing is entirely on you or the CSM. Cuelock will allow you to only have to put in information once, at the beginning, and will become the engine for resolution.

Step 3: System of Record

It's crucial that you actually know what works and what doesn't. It's easy to depend on anecdotal evidence on what works, but that can cost an arm and a leg down the line if systems are built upon wrong, or even slightly wrong, beliefs about what is going on.

As a founder that is trying to build a sustainable, scalable company, it's crucial you get this right. You need to know what worked, at what point, and at what step of any playbook.

Playbooks are meant to be iterated, especially at the start.

For document playbooks, you have to create a copy of a case-specific playbook you ran, and you need to log when it was run, what tasks were taken, which company it involved, and more. You can do this by creating a google sheet and having the following columns:

Risk
Playbook name
Customer
Playbook link
Situation context
Total steps
Churned? Y/N
Step of resolution
Notes

For Cuelock:

Cuelock asks you at each step if it was resolved or not
If resolved, Cuelock stores the case-specific information:
- Risk
- Playbook name
- Customer
- Playbook link
- Situation context
- Total steps
- Churned? Y/N
- Step of resolution
- Notes

In both scenarios, what you get is a very valuable log at the end of a term showing exactly which risks occurred the most, how you responded to them, what worked, what didn't, and more.

You can see the intricacies of which type of customers had which risks, how they are best handled, and share that with any CSM that joins in the future. In other words, you've made a scalable system.

The key is, that has to continue as you bring on CSMs. Cuelock ensures it will, but a document or sheet may have a rough time.

The Metrics That Matter

At the startup level it's difficult to gauge this effectively, but the most important two metrics is:

NRR: Net Revenue Retained
GRR: Gross Revenue Retained

Everything else is vanity. In business, people will vote with their dollars. It's tough to gauge a before playbook and after playbook at the startup level, but as a founder, you will quickly see the value of a repeatable, adaptable set of playbooks, and can make a safe assumption on if these playbooks had a causal relationship to better GRR and NRR.

Final Note

Running a business is extremely difficult. Starting a company is ultimately just a series of picking which battles you want to fight. To me, playing the customer success plus product game paid off, and hopefully for you, it can too!

Feel free to reach out if you have any questions and if creating and operating playbooks is something you want to get serious about, check out Cuelock!

About Cuelock

James and Chinmay Pingale are the co-founders of Cuelock, a customer success platform for SaaS teams that turns risk response and onboarding into repeatable, automated playbooks. Learn more about the team or read more posts on the Cuelock blog.