The CS stack, minus the bloat. You don't need the success tool.

What we actually ran on

The real kit, not the ideal one. We ran Zendesk for ticketing and the knowledge base, RingCentral for the phones behind our 866 number, ChurnZero for customer success (and another success tool before it), and our own CRM at the center of it all. We built our own data warehouse — though that served the whole business, not just CS — and we built our own churn-prediction emails. Almost everything else was bought. The things we deliberately skipped were the in-app chat and marketing-site chat tools; we never missed them.

That list is unremarkable, and that's the point. There's no exotic tool on it that explains our retention. The retention came from the work in the other fourteen articles. The tools just had to not get in the way — and one of them, it turned out, did.

The success tool competes with your CRM

Here's the thing almost nobody thinks about when they buy a dedicated customer success tool: it competes with your CRM. We dogfooded our own CRM and ran both sales and success on it, so we felt this directly. You used to manage the entire customer relationship in one place. Add a success tool that isn't tightly integrated, and that single relationship splits in two.

That fracture is the hidden cost, and it's worse than the sticker price. The entire premise of this series is that retention runs on knowing your customer — one coherent view of the relationship, the history, the value delivered, the expansion shelf. A poorly integrated success tool takes that one view and saws it in half, so your CSM is now reconciling two systems to understand a single account.

And there's a behavioral cost on top of the structural one. These tools become a crutch — a way to mass-email the customer base in lieu of delivering real service. It's easier to fire off a campaign from the success platform than to pick up the phone, schedule the QBR, and actually talk to the customer. The tool quietly substitutes activity for service, which is exactly the trap the support chapter warned about, now wearing a different badge.

The lean stack — stripped to the bone

So what does a lean SMB customer success team genuinely need? Less than you've been told. Three things, by function.

For support: a ticketing system like Zendesk, and a phone system. That's the minimum, and it's non-negotiable — the support basics are the floor of retention.

For the relationship: a CRM. It's where you track communications, renewals, and upsell potential — the single coherent picture of the account. For most SMB success teams, this is the success tool. It already handles 95% of what a dedicated platform would, without splitting your customer in two.

For adoption: something to review product usage by account — so you can see who's going deep and who's drifting. A product-analytics tool like Mixpanel or Amplitude works, but a homegrown view is easier than founders expect here, and it should be the default. You're usually just answering "which accounts are using which features," and your own data can tell you that.

The bootstrapped instinct does double duty here. Defaulting to a homegrown usage view instead of a bought platform doesn't just save money on an expensive line item — it keeps the customer picture whole, because the data lives next to the CRM instead of in a third silo. The constraint produced the better architecture, not merely the cheaper one. That's been the pattern the whole way through: the limits made the decisions sharper.

The honest hierarchy of what drives retention

This is the last section of the last article, so let me end the whole series with the ranking that everything in it points to. Here is what actually drives retention, in order:

First, great customer support. The front line, the phone answered by the second ring, the issue solved over the weekend. This is the foundation, and nothing above it compensates for its absence.

Second, great service from your CSMs: training, onboarding, QBRs, real account management, and communicating new features to customers who'd benefit. The proactive human work that turns a live account into a durable one.

Then, and only then, tools. You need the basics of support — ticketing, email, FAQs. And you need a CRM to manage the relationship. Beyond that, a CRM is all you need to drive retention. You do not need expensive CSM tools.

That's the series. Fourteen articles of machinery — health scores and save plays and renewal motions — and it all resolves to something a vendor can't sell you: pick up the phone, do the unglamorous work, know your customer, and put the people who own those relationships in a position to succeed. The tools matter. They just matter last.