Blog

Churn doesn't start at renewal. It starts at kickoff.

The renewal call is a lagging indicator. By the time an account tells you they're not renewing, the decision is usually months old, made by someone who stopped showing up to your meetings long before they stopped paying.

Ask a CS team when they knew an account was in trouble and you get a remarkably consistent answer: "we had a feeling around week three of onboarding." Not a metric. A feeling. Somebody went quiet, a data export never arrived, the champion stopped replying, and the kickoff energy never came back.

That feeling is real signal. It's just not written down anywhere.

What actually goes wrong

Onboarding fails in a specific, boring way. It's almost never the product, and almost never one dramatic event. It's a sequence:

  1. Sales makes a commitment (a date, an integration, a migration) that lives in a deal note or an email thread nobody reads again.
  2. The kickoff call sets a plan that assumes that commitment.
  3. Something slips. A file doesn't arrive, an SSO step errors, a champion goes on leave.
  4. Nobody notices for eleven days, because noticing requires someone to reread every thread on every account, every morning.
  5. The plan is now fiction, and the customer knows it before you do.

Step four is the whole problem. Everything else is normal project friction that a competent team handles routinely, if they see it in time.

Why "just check in more" doesn't work

The standard advice is more touchpoints. Weekly syncs, health scores, a check-in cadence. It helps at the margins and fails at scale for a simple reason: attention doesn't divide evenly.

One person carrying 60 accounts can't give each a real read every week. What they actually do, correctly given the constraint, is triage by whoever's loudest. The accounts that get attention are the ones already complaining. The accounts quietly drifting toward non-renewal are, by definition, not complaining. They're quiet. Quiet reads as fine.

So the failure mode is structural. The accounts most likely to churn are the least likely to get your attention. No amount of discipline fixes that, because the bottleneck isn't diligence. It's reading time.

The thing worth measuring

Here's a number that predicts renewal better than any health score: how many days pass between a commitment slipping and someone noticing?

Most teams can't answer it, which is itself the answer. But you can approximate it. Pick ten accounts that churned last year. For each, find the first moment in the record (an email, a note, a missed date) where the trouble was visible in hindsight. Then find the date someone actually raised it internally.

The gap is usually two to four weeks. That gap is where the renewal was lost. And it's almost entirely a function of nobody having time to read.

What closing the gap looks like

You don't need to read every thread. You need something that already has, and can tell you which three accounts to look at today, with the quote that made it think so.

That's the bet behind Herofy. Connect HubSpot and Gmail, and Sidekick (our AI) reads each account's deal notes and threads, finds what sales committed to, drafts the onboarding plan from it, and tells you each morning who's stalled and why. Every signal shows its evidence: the actual sentence from the actual thread, not just a number. It drafts the nudge that gets things moving. You edit it and send it, or you skip it.

Two things it deliberately doesn't do. It never contacts your customers; a human sends every message, even in the most autonomous mode. And it doesn't run as a black box: every claim cites its source, you can dismiss anything, and the rules it follows live in a plain-English handbook you can read and edit.

The uncomfortable part

Fixing this doesn't feel like fixing churn. It feels like onboarding getting slightly less chaotic. There's no dashboard moment where a number jumps.

The payoff shows up two quarters later, as renewals that were never in doubt. That's the hardest kind of win to attribute and the only kind worth building for.

Onboarding is chapter one. Most of the story is decided there.


Running onboarding at a small B2B SaaS team on HubSpot, where every account matters? We're pre-launch, building with a small number of design partners. Come build it with us.