← Back to all posts CS Operations

Your CS Team Isn't Broken — It's Running Without a System

I've been building and fixing Customer Success organizations for 25 years — across high-growth SaaS companies, from early-stage to enterprise. Every one of them different, but here's what I've seen at least two dozen times:

A SaaS company at $10M, $20M ARR. A CS team of 3–5 people grinding hard every day. Renewals are happening. Customers are getting onboarded. Fires are getting put out.

But churn is creeping. The board is asking questions. And when the CEO asks "which accounts are at risk right now?" — the room goes quiet.

The team isn't the problem. The system is. Or more accurately, the absence of one.

What "No System" Actually Looks Like

Most SaaS companies build CS the same way: organically. You hire a CSM. Then another. Each one develops their own way of running their book. Some use spreadsheets. Some use Salesforce tasks. Some just rely on relationships and memory.

It works until it doesn't. And when it stops working, the signs are predictable:

Renewals become surprises. You find out an account is churning two weeks before the renewal date — not two quarters before.

Onboarding is different every time. Each CSM runs it differently. Time-to-value is unmeasured and inconsistent.

Health is a gut feeling. "Which accounts are at risk?" depends entirely on who you ask and what day it is.

Expansion is accidental. Upsells happen because a CSM spotted something, not because a system surfaced a signal.

Knowledge walks out the door. When a CSM leaves, everything they know about their accounts goes with them.

This doesn't mean your people aren't good. It means they're operating without infrastructure — and there's a ceiling on what any team can do without it.

The System Your CS Team Actually Needs

If your engineering team had no deployment process, no code reviews, no CI/CD pipeline — you'd call it chaos. But we accept exactly that in Customer Success, the function responsible for protecting your entire revenue base.

Here's what a CS operating system actually looks like. Over 25 years, I've developed and refined this framework across multiple SaaS environments and codified it into a framework I call CSOS — six pillars that form a complete system:

Onboarding Foundation. A repeatable process with defined milestones, time-to-value metrics, and clear handoff from sales. Not a checklist. An architecture.

Engagement Architecture. Segmentation by value and complexity. Defined touch cadences. Escalation triggers. A model that tells your CSMs what to do and when — not just "manage your book."

Health Scoring & Risk Intelligence. Quantified signals — usage, support trends, engagement, stakeholder changes — that produce a real score. Not a red/yellow/green someone updates manually once a month.

Value Expansion Engine. Defined triggers for upsell and cross-sell. CS sees expansion signals before anyone else. That shouldn't be accidental.

Renewal & Retention Strategy. A motion that kicks in 90+ days before renewal. Risk mitigation playbooks. Executive alignment triggers.

AI & Automation Readiness. The infrastructure that lets you actually scale — automated health scoring, risk alerts, engagement sequences. But only after the first five pillars exist.

Why This Matters Right Now

Two things have changed in 2025–2026 that make this urgent.

First, boards and investors have zeroed in on net revenue retention. NRR is the most scrutinized metric in SaaS right now. If your CS team can't report on it confidently and explain the drivers, you have a credibility problem.

Second, AI has made it possible for a CS team of 2–3 to operate like a team of 10. But only if the system exists first. You can't automate what isn't defined. AI amplifies whatever process you have — and if that process is "everyone does it their own way," AI just does that faster.

You Don't Need a VP of CS. You Need the System First.

The instinct is to hire a VP of Customer Success and let them sort it out. That's a $200K+ bet on one person building everything from scratch — hiring, process, tech stack, reporting — while also managing the team day-to-day.

The faster path: install the operating system first, then hire the leader to run it.

When the system exists, your VP walks into defined playbooks, working health scores, engagement models, and reporting. They spend their first 90 days optimizing and leading — not building from zero while simultaneously fighting fires.

One Thing You Can Do This Week

Ask your CS team this question:

"How long would it take you to give me a confident list of every account at risk of churning in the next 90 days?"

If the answer isn't "I can pull that up right now" — you're running without a system.

That's not a failure. It's a starting point. And the fix is faster than most people think.

← Back to all posts AI + Customer Success

Why AI Won't Fix Your Customer Success Problems

I design and implement AI-powered CS systems with clients. So when I tell you that AI probably won't fix your Customer Success problems — at least not yet — I'm not being contrarian for the sake of it.

I'm telling you what I see every week when I talk to SaaS founders and CS leaders. They all say some version of the same thing: "We need AI in our CS operation. The team is stretched, churn is up, and everyone says AI can fix it."

They're half right. AI absolutely can transform a CS operation. I've built systems where a team of 3 does the work of 10. But here's the part nobody talks about:

AI doesn't fix broken CS. It scales it.

If your operation is reactive, inconsistent, and flying blind on risk — AI just makes you reactive, inconsistent, and blind faster.

The "Just Add AI" Trap

Here's what actually happens when you bolt AI onto a CS function with no foundation:

AI health scoring with no playbooks. You build an automated health score. It flags 30 accounts as at-risk. Now what? Your team has no defined playbook for at-risk accounts. No escalation criteria. No executive engagement triggers. The AI surfaces the problem. Your team stares at it.

AI-generated QBRs with no value framework. You automate QBR creation. The AI pulls usage data and builds slides. But there's no structure tying product usage to business outcomes — because nobody defined what "value realization" looks like per segment. You get beautifully formatted decks that say nothing useful.

Automated onboarding with no milestones. You set up AI-driven sequences. But there's no definition of "successful onboarding." No time-to-value metric. No handoff criteria. The automation runs, the customer gets emails, and nobody knows if they're actually getting value from the product.

In every one of these scenarios, the AI works perfectly. The system it's plugged into doesn't.

What AI Actually Needs

AI in Customer Success isn't magic. It's an amplifier. And amplifiers need signal.

Here's what has to exist before AI delivers real results:

Defined segments. AI can't decide how to engage a customer if you haven't defined what kind of customer they are. High-touch? Tech-touch? Pooled? Each segment needs a different engagement model.

Measurable health signals. AI-powered scoring requires inputs — usage data, support patterns, engagement frequency, NPS, stakeholder changes. If you're not collecting these in a structured way, there's nothing to score.

Playbooks with triggers. AI can automate the execution of a playbook. It can't write the playbook. When health drops below 60, what happens? When a champion leaves, what's the re-engagement sequence? When usage drops 30% MoM, who gets alerted?

A renewal motion with a timeline. AI can forecast risk, but only against a defined process. When does prep start — 120 days out? 90? Who owns the conversation? What triggers executive involvement?

The Right Sequence

I've been building CS organizations for 25 years and AI-powered CS systems for the last two. Here's the order that works:

Step 1: Audit. Map your current operation against a structured framework. Where are the gaps? What's documented vs. tribal knowledge? Where are you actually losing customers? This takes 2–3 weeks.

Step 2: Build the foundation. Install playbooks, health scoring, engagement architecture, renewal motion. This is the operating system — the process your team runs on. It doesn't need to be perfect. It needs to be defined.

Step 3: Add AI. Now AI has something to work with. Health scores automate and become predictive. Risk alerts fire on real signals. Engagement sequences scale. Reporting generates itself. A team of 3 starts operating like 10.

Step 4: Optimize. AI gets better with data. Refine triggers. Adjust thresholds. Build new workflows. This is where an ongoing CS partner earns their keep.

The Math

A $15M ARR SaaS company at 85% gross retention is losing $2.25M in ARR every year to churn.

If AI-powered risk detection catches even 20% of that 90 days earlier — giving your team time to intervene — that's $450K in protected ARR. Every year.

But only if the system exists to act on what AI surfaces.

A $7,500 audit followed by a $12,000–$18,000 system build pays for itself the first time it saves a single enterprise renewal.

Honest Self-Assessment

Before you invest in AI for CS, answer these:

Can your team tell you which accounts are at risk right now — and why? If the answer requires a meeting or a spreadsheet scramble, you need the system first.

Is your onboarding documented and measurable? If every CSM does it differently, AI just automates the inconsistency.

Do you have playbooks for common scenarios? At-risk accounts, expansion signals, champion departures, executive escalations. If these live in people's heads, AI can't run them.

Can you report on NRR, GRR, and time-to-value with confidence? If not, AI dashboards just surface the fact that your data isn't clean.

If you answered "no" to two or more — you're not ready for AI in CS. But the foundation can be built in 4–6 weeks. Then AI becomes the most powerful tool your CS operation has ever had.

Bottom Line

AI is a force multiplier for Customer Success. But you can't multiply zero.

Build the system. Then let AI make it scale.