Which of your paying customers have gone quiet?

Free quiet accounts checker · Last updated November 2026 · Runs in your browser

Most churn is decided weeks before the cancel button. The customer stops logging in, keeps paying out of inertia, and leaves at the next renewal or the next budget review. Billing dashboards can't see this because the card still clears.

Drop in a CSV with each customer and when they were last seen. You get back the paying accounts that have gone silent, ranked by how much MRR sits on them. Your file never leaves this tab.

1. Usage export

Customer email or ID plus a last-seen date. MRR too, if it is in the same file.

2. Billing export (optional)

A Stripe subscriptions export works as is. Joined on email, so paying customers missing from the usage file show up as never seen.

Processed in this tab. Close it and the data is gone.

Retention Diagnostic

You have the names. The harder question is why they went quiet.

A calculator tells you how much is leaving. It cannot tell you which part is failed payments, which part is people who never activated, and which of the two is cheaper to fix. I work that out on your actual data and send back three fixes ranked by what each one is worth, within 10 working days.

  • ✓ Voluntary and involuntary churn, split and costed
  • ✓ What the leavers did in their first month
  • ✓ Three fixes, ranked by dollars recovered
  • ✓ Fixed price, written, no call required
See what it covers $2,500, fixed.

How do I get a last-seen export?

You need one row per customer and the last time anyone from that account did something in the product. Where that lives depends on your stack:

  • Your own database. Most apps already store a last login or last activity timestamp on the user table. If you only have events, the query below works.
  • Product analytics. PostHog, Mixpanel and Amplitude can all export people or users with a last seen property to CSV.
  • Billing. Stripe can export subscriptions to CSV from the dashboard. That gives you email, status, plan amount and interval, which is what the second box expects.
select u.email,
       max(e.created_at) as last_seen
from users u
left join events e on e.user_id = u.id
group by u.email;

For B2B, group by account rather than user if you can. An account with one active admin and nine silent seats is fine this month and in trouble at the seat count review. That is a different problem, and the seat downsizing playbook covers it.

Why look at silence instead of churn rate?

Churn rate is a lagging number. By the time a customer shows up in it, they've already made the decision, often weeks before. Silence is the earliest signal most small SaaS companies already have, and it costs nothing to collect because the timestamp is sitting in the database.

A quiet account is a cancellation that hasn't been filed yet. You can still talk to them.

The list also tells you something the churn rate can't: whether the quiet accounts have anything in common. If most of them signed up in the same month, sit on the same plan, or never connected the same integration, you have found a cause rather than a symptom.

One honest limit. Login data undercounts products that do their work in the background, like a dunning tool or a backup service, where a happy customer never needs to log in. For those, use the last time the product did something valuable for the account instead of the last login.

What else should I check?

Questions about quiet accounts

Short answers. The checker itself is above.

What is a quiet account?

A customer who is still paying but has not used the product for a while. This checker calls an account quiet once nobody has been seen for 14 days, which you can change. Quiet accounts have not cancelled yet, which is the point: you can still reach them before they do.

What data do I need?

One CSV with a customer identifier (email or account ID) and a last-seen or last-login date. MRR helps, because it ranks the list by money at risk. If your usage data and billing live in different places, add a Stripe subscriptions export as a second file and the checker joins them on email.

Is my customer data uploaded anywhere?

No. The CSV is read and processed by JavaScript in your browser tab. The page sends one ping saying the check ran and roughly how many rows it had, so I know whether anyone uses it. No names, emails, dates or amounts are sent.

How many days without a login counts as quiet?

It depends on how often the product should be used. For a daily tool, 7 days of silence is a warning. For something used weekly, 14 to 21 days. For a monthly reporting tool, closer to 45. Set the threshold to roughly twice the gap you would expect between visits from a healthy customer.

What does "never seen" mean?

A paying customer with no last-seen date, or one who appears in your billing export but not in your usage export at all. These are usually accounts that bought and never set the product up. They tend to be the cheapest to save and the easiest to lose at renewal.

What should I do with the list?

Email the highest-MRR quiet accounts yourself, as the founder, with a plain question about what changed. Send never-seen accounts a setup offer rather than a feature tour. Then find out whether quiet accounts share a cause, such as one plan, one signup month or one missing integration, because that is the fix that scales.