Your customer warned you. Just not in one place.

Picture an account sixty days before renewal. Four people each see something different:

1. Support: "Ticket closed. They said thanks."
2. Sales: "Renewal looks likely."
3. Product: "Usage is down a third since last month."
4. The founder's inbox: "Quick question, how do we export our data?"

Every one of them is right. Nobody puts it together. The customer leaves.

The problem isn't missing data. It's scattered data.

Small SaaS teams usually have the signals they need. They're just spread across tools and people who don't compare notes. Support sees tickets. Sales sees the pipeline. The founder sees their inbox. Product sees usage. Each view looks fine on its own.

Churn hides in the gaps between them.

One weekly list beats a bigger dashboard

You don't fix this with more charts. You fix it with one list, every week:

• Every account showing two or more signals, from any source.
• One owner per account on that list.
• One question to the customer within 48 hours: "What's changed?"

The list doesn't need to be clever. It needs to exist, and someone needs to look at it.

Which signal gets missed most?

In our experience, it's the fourth one: exit-shaped questions that land in one person's inbox. "How do we export our data?" or "When exactly does our contract end?" are among the most honest churn signals there are, and they're the least likely to be logged anywhere.

If you take one thing from this post: when someone asks one of those questions, treat it like a usage drop. Reply within 48 hours and ask, kindly and directly, what's prompting it.

Clynto pulls these signals into one weekly list for you, with the follow-up drafted for your approval.

Examples in this post are composites of common patterns, not specific customers.