Churn is rarely what it looks like on the surface — and pulling the wrong lever compounds the problem.
Have a question about this? Bring it to Aurelius.
Net-new B2B SaaS sales fell 3.3% in Q4 2024, and if you are watching your churn number rise while your pipeline thins, you are not misreading the moment — you are living the structural shift that has made retention the primary growth engine of the industry. Companies with dedicated Customer Success teams achieve 20–30% lower churn than those relying on founders or account executives to carry that weight. That gap is not marginal. At recurring revenue multiples, it is the difference between a business that compounds and one that leaks.
So the instinct to reach for Customer Success as your lever is reasonable. The problem is that instinct alone, applied without diagnosis, can cost you twelve months and a headcount budget — and leave the churn number unchanged.
Conventional advice says: hire a CSM, build a health score, run QBRs, and watch retention improve. This is not wrong in the abstract. It is wrong as a first move when the root cause is unexamined.
Customer Success is a delivery mechanism. It delivers value realization, relationship continuity, and early intervention. But if customers are churning because the product does not solve the problem it was sold to solve, no CSM can close that gap. If they are churning because onboarding fails in the first 30 days — the most critical window in the customer lifecycle — a CSM hired to manage mature accounts will not touch the problem. If churn is concentrated in a specific segment, industry, or contract tier, a generalist CS motion will dilute your signal further.
The mistake is treating CS as a diagnosis when it is a treatment. You would not prescribe medication before understanding what is wrong. The same discipline applies here.
In Meditations IV.3, I wrote: "Do not indulge in dreams of what you have not, but count up the chief of the blessings you do possess, and then thankfully remember how eagerly you would have sought them, if they had not been yours." This passage is about inventory — the honest accounting of what is actually present before you reach for what you imagine will save you.
This reveals something precise about your situation. You say you can see the churn problem but cannot fully diagnose it. That partial visibility is not a reason to act — it is the very thing you must resolve before acting. The Stoics called this prohairesis — the disciplined faculty of choice, which begins not with decision but with perception. What do you actually see? What are you inferring? What are you assuming because it is easier than investigating?
Epictetus was direct on this point: we suffer not from events but from our judgments about events. A churn number is an event. The judgment that "we need Customer Success" is an interpretation layered on top of it — and interpretations can be wrong. This means the examined work life, applied to a retention problem, begins with disaggregation, not prescription.
Consider what Marcus Aurelius would do with your data. He would separate what is known from what is assumed. He would ask: where exactly is churn concentrated — by cohort, by segment, by product line, by sales motion? He would ask: at what point in the customer lifecycle does engagement collapse? He would ask: what do the customers who stayed do differently in their first 90 days than those who left?
This is not philosophical abstraction. It is the practical discipline of not treating your anxiety about churn as evidence about its cause. The urgency you feel is real. But urgency applied without clarity produces motion, not progress. The Stoic tradition insists that right action follows right perception — and right perception here means building a multi-signal picture before committing resources to a function that can only address a subset of churn drivers.
This means the question is not "should we invest in Customer Success?" The question is "what is our churn actually made of, and which of its components does CS directly address?"
Begin with a churn cohort analysis segmented by three variables: time-to-first-value, account segment, and sales source. Map where customers fall out of the lifecycle — not when you discover they have left, but when engagement silently collapsed. The 30–90 day window is where most churn is decided, even if the cancellation arrives in month nine.
Once you have that map, ask which failure modes a CS function can intercept. If customers are not reaching activation milestones, a CSM with a structured onboarding playbook is a direct lever. If customers activated but never expanded, a CS motion focused on adoption and QBR rhythm addresses that gap directly — the Turn Your QBR Into a Retention Tool Your Customers Actually Value framework is built precisely for this moment. If customers are churning silently — no complaints, no escalations, just non-renewals — you likely have a health score problem before you have a headcount problem, and Turn Customer Health Scores Into Retention Decisions Your Exec Team Trusts gives you the architecture to build signal before you build team.
If the diagnosis confirms that CS is the right lever, then org design matters as much as headcount. The largest churn improvements in SaaS companies coincide precisely with the moment founders hire dedicated CSMs rather than distributing retention responsibility across sales and ops. A CS Team Hiring Rubric built before your first CS hire prevents the common failure of hiring an account manager and calling them a Customer Success Manager.
Build the CS operations stack to scale beyond your headcount from day one. A single CSM with the right tooling — health scoring, automated engagement triggers, renewal workflows — can carry a book of business that would otherwise require three. The Build a CS Operations Stack That Scales Beyond Your Headcount course is the operational backbone for that decision.
Before you close this tab, open your CRM or your data warehouse and pull every churned account from the last two quarters. Segment them by one variable only: the date of their last meaningful product engagement before cancellation. Do not use the cancellation date — use the engagement collapse date. If you cannot find that date, that absence is itself the diagnosis: you do not have the visibility infrastructure to run a CS function effectively yet, and your first investment is instrumentation, not headcount. If you can find that date, plot it against the customer lifecycle stage. Look for the cluster. That cluster is where your lever lives — and whether CS is the right tool to pull it will become self-evident from the pattern. Write down what you see in one paragraph before you do anything else.
If your diagnosis points toward silent churn — customers disengaging without signaling — Turn Churn Signals Into Saving Conversations Before Customers Leave maps the early indicators most teams miss until it is too late.
If health score infrastructure is the gap, Turn Customer Health Scores Into Retention Decisions Your Exec Team Trusts builds the framework from signal to executive action.
For teams ready to build CS operations that scale, Build a CS Operations Stack That Scales Beyond Your Headcount is the architecture course that prevents the common failure of building a CS function that cannot grow past its founder.
Go deeper with Aurelius
Apply this to your actual situation. Aurelius will meet you where you are.
Start a session