Run it: the solo CS operating cadence

A machine that exists on paper changes nothing. The last piece is the cadence that turns all of this into a habit you actually keep, and the good news is that once the agents are doing the watching and drafting, the human cadence is genuinely light. You are not running a customer-success department. You are running a weekly ritual and a short list of one-time setup decisions, and that is the whole operating model.

The weekly thirty-minute ritual

Block thirty minutes a week and run the same loop every time. Open the at-risk queue the agents have surfaced and read the few accounts whose signals have tripped, not the whole base, only the ones the machine flagged. Review the outreach the agents have drafted, adjust anything that needs your voice, and approve it to send. Then look at the renewals coming up and book the handful of human calls, the amber renewals, the save conversations, the expansion talks, that genuinely need you, and let the green accounts renew on the recap alone. Thirty minutes, once a week, and the base is covered. That is what replaces a team carving the accounts into territories and working a calendar of check-ins: a single founder working only the exceptions the system surfaces.

The reason this stays at thirty minutes rather than creeping back into a full-time job is the discipline of the earlier chapters. The signals keep you out of healthy accounts. The agents keep you out of the busywork. The approval gate keeps your judgement on every touch without making you author every word. Remove any one of those and the ritual swells; keep all three and it holds.

What to set up this week

Do not try to build the whole machine at once. This week, make three decisions and you will have a working v1. Pick your activation event, the single moment that predicts a customer will stay, and start measuring days-to-it. Pick your top three health signals from the data you already have, login recency, one key usage event, support sentiment, and stand up a crude health score. Pick your renewal lead time, the ninety-day mark is a sensible default, and set the agent to compile a recap at that point. Three decisions, and the funnel has a spine you can tighten later.

Then claim the automatable wins in parallel, because they need no judgement: wire up dunning so failed payments retry and recover, set the renewal-reminder sequence running, and point a win-back agent at your churned list. Those run unattended from the moment you build them and start returning revenue immediately.

This connects to the rest of the growth machine exactly where you would expect. The retention work here feeds your lifetime-value maths, the expansion stage is where account growth becomes a deliberate engine rather than a happy accident, the win-back motion is its own reclaimable channel, and the tooling that holds the health score and the sequences is the service-hub layer underneath it all. Build the post-sale funnel stage by stage, run it as a thirty-minute weekly ritual, and you will out-retain founders with three times your headcount, because you built the machine they keep telling themselves they will hire for later.