10 Early Warning Signs of Customer Churn
The ten signals that often come before a SaaS customer cancels, where each one shows up in your data, who should respond, and which tools cover them.
By the editorial team, updated October 8, 2026.
If you want one tool to start with, Sequenzy is a reasonable first pick for a small or mid-sized SaaS whose churn signals come mostly from billing events and email behavior, especially if the subscription runs through Stripe, Paddle or Lemon Squeezy. The reason can be checked against the price list: plans are priced by emails sent and contacts are unlimited, so 25,000 contacts who each get two emails a month is 50,000 emails, which fits the 60,000-email plan at $49 a month billed monthly (the pricing page lists $529 a year for that plan). Its payment-failed event also carries a hosted invoice link, so the first message can send a customer straight to a page where they can pay or update their card. The rest of this guide explains which signals to watch, who should act on each one, and when a different tool makes more sense.
Prices in this article were read from each vendor's public pricing page on October 7, 2026. Vendors change packaging, so confirm the figures on the linked pages before you budget. Where a vendor does not publish a price, this guide says so instead of giving an estimate.
What makes a signal an early warning
Most customers who cancel do not decide in a single afternoon. Something changes first: a payment fails, a login stops, a champion changes jobs, a support thread gets longer. The useful question for a retention team is not whether a signal exists, but whether it can be acted on in time. A signal earns its place on your list when it passes three tests.
- It is observable in a system you already run. Billing webhooks, product events, helpdesk tickets and CRM contact changes all qualify. A feeling that a customer is unhappy does not, unless someone writes it down.
- It has an owner. Every signal needs one named person or one queue that reviews it. Signals without owners are reports that nobody reads.
- It leaves a response window. The response is only worth making if it can still change the outcome. A failed card needs a same-day message; a shrinking team may need a conversation over a few weeks.
How far ahead each signal appears depends on your product, your billing cycle and your contract length. A monthly consumer app and an annual enterprise contract produce very different timelines. Measure the lead time of each signal against your own past cancellations rather than borrowing a universal figure, because published averages rarely match your mix of customers.
It also helps to separate two kinds of loss. Involuntary churn comes from payments that fail even though the customer still wants the product. Voluntary churn comes from a decision to leave. The signals below mix both, so the response should differ. A failed card is mostly a billing problem; declining usage is mostly a value problem. Treating them the same is one of the most common mistakes in early-warning programs.
The ten signals
1. Failed payments and expiring cards
A failed charge is the most direct signal because it is recorded automatically and it has an obvious next step. Your billing provider emits an event when a payment fails, and most teams already receive it, even if they only see it in a dashboard. Stripe, Paddle and Lemon Squeezy each expose failed-payment events that can be sent to other systems. Sequenzy lists a saas.payment_failed event that includes a hosted invoice URL, which the customer can open to pay or update their card.
The response should be quick, specific and free of blame. A message that says the payment did not go through, links to the update page and explains what happens next tends to work better than a generic reminder. Keep a second, later message for customers who do not act, and route high-value accounts to a person. Track how many failed-payment customers return to paying, and how long it takes, so you can judge the sequence on your own numbers.
2. A falling login frequency
The most common sign is a customer who used to log in most days and now logs in once a week, then once a month. Each step down matters because it means the product is becoming less of a habit. The mistake is comparing every account with the average. A customer who logs in once a week may be perfectly healthy if that matches how their team works. Compare each account with its own history over the previous eight to twelve weeks.
When the pattern is clear, the response can be a short reminder tied to the last action the customer took, such as a report they generated or a project they left open. A generic "we miss you" email rarely changes behavior.
3. Shrinking feature breadth
Frequency and breadth are different. A customer may still log in every day but use only one feature that used to be part of a larger workflow. Breadth is usually the better measure of value. Count the number of core features each account used in the last thirty days and watch for a sustained drop. Product analytics tools such as Mixpanel and Amplitude can show this trend directly if your events are instrumented.
The response is a focused guide to the features the account has stopped using, ideally with a short example of how a team like theirs uses them. Avoid sending the entire feature list.
4. Support escalation
Frustrated customers open more tickets, reopen closed ones, use harsher language and ask for managers. Each of these is visible in a helpdesk. Look at volume and reopen rates per account, not only at average resolution time, because a fast resolution does not help if the same problem returns. Tone is harder to measure automatically, so ask support agents to flag accounts that sound close to leaving.
An escalated account usually needs a senior person to review the open issues, a written plan with dates, and a status update that does not wait for the next scheduled check-in.
5. Champion departure
When the person who championed your product leaves, the renewal often becomes uncertain. The new contact may not share the same goals, and the budget may move elsewhere. The CRM is the usual place to see this, through contact changes or a bounced address. Some teams also watch for a sudden change in who replies to emails.
The response is to reach the new stakeholder within a short window, with a message that explains what the product does for their team and what has been achieved so far. A short written summary of results is often more useful than a meeting invitation.
6. Silence after outreach
Engaged customers reply to messages, open them and accept calls. Customers who are drifting stop doing these things, sometimes without any complaint. Track replies, meeting acceptances and cancelled calls for each account, not only the open rate of a campaign. A customer who never opens a campaign may be a light user, while one who opened every message last quarter and now opens none has changed.
When you see silence, change the channel before sending more of the same. A direct question by email, a short call offer or a note in the app is more likely to get a reply than a fourth identical campaign.
7. Competitor and pricing questions
When a customer asks how you compare with a named alternative, or whether a cheaper plan would cover them, they are comparing options. This is not always a sign of imminent churn, but it deserves a direct answer. Capture these questions in support or sales notes, and tag them so you can see how often they appear for each account.
Answer the question plainly. Say where the competitor is a better fit, what the customer would lose by switching, and what would make your product the better choice for their situation. Customers who feel they were given a fair comparison are more likely to stay, even when they choose the alternative.
8. A downward satisfaction trend
A single survey score tells you little. The trend matters: a promoter who slides to passive, or a passive who drops toward detractor, is showing a trajectory. Track survey responses per account over time, and treat a sustained decline as a signal even when the score is still above your alert threshold.
The response should ask a specific question about the workflow that changed, not a general request for feedback. "What got harder in the last month?" produces more usable answers than "How are things going?"
9. Visits to cancellation or downgrade pages
A customer who opens the cancellation flow, or the page that lists downgrade options, has shown intent even if they leave without acting. Page analytics or in-app events can capture these visits. Use them as a trigger for an offer: a pause, a smaller plan, or a question about what is not working. Record the reason the customer gives, because it is one of the most direct sources of churn data you will get.
10. Seat and plan reductions
Removing seats, dropping a module or moving to a cheaper plan is partial churn. The customer is reducing how much they depend on you. Sometimes this stabilizes; sometimes it is the step before cancellation. Subscription change events from your billing provider show these changes, and they are easy to overlook because the customer is still paying.
The response is a short review of what was removed and why. If a team dropped seats after a reorganization, the conversation is about the new structure. If they dropped seats because a feature was missing, the conversation is about the roadmap or a workaround.
Where each signal lives and who responds
The table below maps each signal to the system where it usually appears, the role that should respond and a first response to try. Adjust the owners to match your team, but keep one owner per signal.
| Signal | Where the data usually lives | Who should respond | First response to try |
|---|---|---|---|
| Failed payment or expiring card | Billing provider events | Billing or operations | Same-day update message with a direct link |
| Falling login frequency | Product analytics or auth logs | Product marketing or customer success | Reminder tied to the last completed action |
| Shrinking feature breadth | Product event data | Customer success | Short guide to the unused features |
| Support escalation | Helpdesk tickets | Support lead with an account owner | Senior review and a dated written plan |
| Champion departure | CRM contact changes, bounced email | Account owner | Introduction to the new contact with a results summary |
| Silence after outreach | Email engagement, meeting records | Account owner | Direct question on a different channel |
| Competitor or pricing questions | Support and sales notes | Sales or customer success | Honest comparison that names the trade-offs |
| Downward satisfaction trend | Survey responses over time | Customer success | Specific question about the workflow that changed |
| Cancellation or downgrade page visits | Page analytics or in-app events | Product or customer success | Pause or smaller-plan option, plus a reason question |
| Seat or plan reduction | Subscription change events | Account owner | Review of what was removed and why |
Turning signals into a risk score
Once you have several signals, you can combine them into a single account score. A score is useful for prioritizing work, but it is only as good as the weights behind it. The weights below are an example of how a team might start. They are not benchmarks, and they should be replaced with weights that reflect your own customers.
- Failed payment: a large negative weight, because it needs action the same day
- Falling login frequency against the account's own baseline: a moderate negative weight
- Support escalation with a reopened ticket: a moderate negative weight
- Champion departure: a moderate negative weight that stays until a new contact is confirmed
- Visit to a cancellation page: a moderate negative weight that decays after a few weeks
To calibrate, take the accounts that cancelled over the last twelve months and check which signals were present before each cancellation, and how long before. Then check the accounts that showed the same signals and did not cancel. Those are your false positives, and they tell you whether a signal is worth acting on or only worth watching. Repeat the check every quarter, because a change in pricing or onboarding can change which signals matter.
Keep the score simple enough that the owner of each signal can explain it. A score nobody understands will be ignored, and a score that cannot be explained cannot be corrected. For the broader scoring method, see our customer health scoring guide, and for the messages that follow a score change, see our retention email sequence examples.
Tools that cover the signals
No single product covers all ten signals well. Billing events come from your payment provider, product events from an analytics tool, support data from a helpdesk, and outreach from an email platform. The question is which layer each tool should own. The sections below describe the tools that fit this topic most directly, with the price as listed on each vendor's pricing page.
Sequenzy: billing and event-triggered email
Sequenzy is best suited to teams whose early warning signals end in a message to the customer. It connects to Stripe, Paddle, Lemon Squeezy, Polar, Creem and Dodo Payments, and it can also take custom events through a webhook or API. Its payment-failed trigger includes the hosted invoice page, which makes the first recovery message specific. It also supports automations built from plan, revenue and engagement data, so a customer who downgrades can receive a different sequence from one who stays on the same plan.
Where it falls short: it is an email and automation platform rather than a product analytics suite. If you need deep funnel analysis or session-level behavior, pair it with Mixpanel or Amplitude. Its pricing is based on monthly email volume, so a large mailing schedule can cost more than a small one even with unlimited contacts. The free plan covers 2,500 emails a month. Paid plans start at $19 a month for 15,000 emails, or $205 a year, and rise to $29 for 30,000 emails, $49 for 60,000 and $99 for 120,000 on monthly billing. Check the current plan list on the Sequenzy pricing page.
Customer.io: behavioral journeys across many profiles
Customer.io suits teams that want to run behavioral journeys across a large number of people and trigger messages from product events. It is a good fit when several teams, such as product, marketing and customer success, need to send messages from the same event stream. The pricing page lists an Essentials plan at $100 a month and shows profile-based prices of $145 a month at 10,000 profiles, $235 at 20,000 and $325 at 30,000, all billed monthly. Eligible early-stage companies that have raised under $10M can receive 12 months free through its Startup Program.
Where it falls short: it needs event instrumentation to be useful, and the price moves in profile steps, so a growing list can change the budget quickly. Teams that only need billing-triggered recovery emails may find it more platform than they need. See the Customer.io pricing page for the current figures.
Mixpanel: product usage and cohort analysis
Mixpanel is a product analytics tool. It is the right place to watch login frequency, feature breadth and cohort retention, and to find out which early behaviors separate customers who stay from those who leave. It has a free plan for up to 1M monthly events. The Growth plan is listed at $140 a month, or $120 a month billed annually, and covers up to 20M monthly events. Enterprise pricing is custom.
Where it falls short: analysis is its strength, not outreach. You will still need an email or messaging tool to act on what it shows. Event naming needs discipline from the start, or the cohorts will be hard to trust. Check the Mixpanel pricing page for current plan details.
Amplitude: a free starting point for behavior analysis
Amplitude offers a free plan that covers 2M events a month with no time limit, plus product analytics, limited experiments, guides and surveys, and 10K monthly session replays. That makes it a practical starting point for a team that wants to see behavioral patterns before paying for anything. Its Growth and Enterprise plans are priced on request, and the Plus plan scales with event volume beyond the first 2M events, up to 70M.
Where it falls short: as with other analytics tools, it reports on behavior and does not send the outreach. Plan for the event volume you will need when you grow, because the free tier is measured in events, not users. The Amplitude pricing page lists the current tiers.
ChurnZero: account health for B2B customer success
ChurnZero is built around customer health scoring and playbooks for customer success teams that manage a book of business account by account. It fits B2B products where a human owns each account and the signals need to appear in the same workspace as the account plan. Its pricing is on request, so you will need to ask the vendor for a quote through the ChurnZero pricing page.
Where it falls short: it is aimed at teams with a dedicated customer success function. A small team with a few hundred self-serve customers may find it heavier than it needs to be, and the sales conversation takes time.
Gainsight: enterprise customer success
Gainsight is an enterprise customer success platform with health scoring and analytics across large customer bases. It is a sensible choice for organizations with dedicated customer success operations, multiple products and complex renewal processes. Pricing is custom and is not listed as a number on its pricing page, so a quote is required.
Where it falls short: setup and administration usually need specialist time, and it is designed for larger teams. For a company with a small customer base and a single billing system, a lighter tool is usually enough. Review the Gainsight pricing page for the current packaging.
Stripe, Paddle and Lemon Squeezy: the billing source
The billing provider is where the first signal is generated, so it matters for this topic even though it is not a retention tool in itself. Stripe's standard payments pricing is per transaction, with no permanent free plan. Paddle is a merchant of record: it handles billing, tax and payment, and charges per transaction with no permanent free plan. Lemon Squeezy also works as a merchant of record, with a $0 monthly plan and fees charged per sale. Check the Stripe pricing page, the Paddle pricing page or the Lemon Squeezy pricing page for the transaction fees that apply to you.
The practical point is that the choice of billing provider decides which failed-payment and subscription-change events you can use, and how easily they reach your email tool. Confirm the event names in the provider's documentation before you design any sequence.
Make: connecting the systems
Make is a visual automation tool that can connect billing, product and CRM systems when no native integration exists. It is useful for building a simple alert, such as posting a message to a team channel when a high-value account fails a payment. Its Free plan includes 1,000 credits a month, with a limit of two active scenarios and runs that can happen at most every 15 minutes. The Core plan is listed at $10.59 a month for 10,000 credits, or $9 a month billed annually. Check the Make pricing page for the credit rules.
Close: a CRM for account owners
Close is a CRM that small B2B teams use to log calls, emails and tasks against each account. For early warning, it is the place where a champion change, a competitor question or a missed meeting becomes a visible task with an owner. Its Solo plan is listed at $19 per user a month, or $9 per user a month billed annually. Essentials is $49 per user a month, or $35 billed annually. A 14-day free trial is offered without an ongoing free plan. Close is a CRM and not a billing-event engine, so it works best alongside the billing and email tools above. See the Close pricing page.
Tool comparison
The table below compares the tools by the job they do best, their entry price with the plan and billing view, and the main limitation to plan around.
| Tool | Best for | Entry price (plan and billing) | Key limitation |
|---|---|---|---|
| Sequenzy | Billing and product events that trigger customer emails | Free for 2,500 emails a month; 15,000 emails at $19 a month, monthly billing | Not a product analytics suite; priced by email volume |
| Customer.io | Behavioral journeys across many profiles | Essentials at $100 a month; 10,000 profiles at $145 a month, monthly billing | Needs clean event data; cost rises in profile steps |
| Mixpanel | Usage trends, feature breadth and cohorts | Free up to 1M monthly events; Growth at $140 a month, or $120 billed annually | Analyzes behavior but does not send outreach |
| Amplitude | Free starting point for behavior analysis | Free plan with 2M events a month, no time limit | Growth and Enterprise pricing on request; free tier is measured in events |
| ChurnZero | Account health for B2B customer success | Pricing on request | Sized for dedicated customer success teams |
| Gainsight | Enterprise customer success operations | Pricing on request | Setup needs specialist time |
| Close | Account notes, tasks and owners for B2B teams | Solo at $19 per user a month, or $9 billed annually | A CRM, not a billing-event engine |
| Make | Connecting billing, product and CRM systems | Free with 1,000 credits a month; Core at $10.59 a month for 10,000 credits | Free plan limited to two active scenarios |
What it costs at realistic list sizes
Price depends on how many people you contact and how often. The table uses example scenarios so you can match them to your own list. Only the plans and prices listed on each vendor's pricing page are used. Where a vendor does not publish a price for a scenario, the table says so.
| Scenario | Volume | Plan that applies | Price |
|---|---|---|---|
| Early-stage SaaS, 2,000 contacts | 4 emails each a month, 8,000 emails in total | Sequenzy 15k/month | $19 a month, monthly billing (or $205 a year) |
| Growing SaaS, 5,000 contacts | One weekly email, about 21,700 emails a month (5,000 × 52 ÷ 12) | Sequenzy 30k/month | $29 a month, monthly billing (or $313 a year) |
| Established SaaS, 25,000 contacts | Two emails each a month, 50,000 emails in total | Sequenzy 60k/month | $49 a month, monthly billing (or $529 a year) |
| Behavioral journeys, 10,000 profiles | Profile-based pricing at 10,000 profiles | Customer.io, 10k profiles | $145 a month, billed monthly |
| Behavioral journeys, 20,000 profiles | Profile-based pricing at 20,000 profiles | Customer.io, 20k profiles | $235 a month, billed monthly |
| Small B2B account team, 5 users | Five seats on Close Essentials | Close Essentials | $245 a month on monthly billing (5 × $49), or $175 a month billed annually (5 × $35) |
| Enterprise customer success | Any account count | ChurnZero or Gainsight | Pricing on request |
Two things to note. First, the Sequenzy scenarios are counted in emails sent, not contacts, so a sequence that sends more messages per person costs more even when the list stays the same. Second, the Customer.io figures are the profile-based prices shown for each profile count, billed monthly. Use the pricing page to confirm which billing option applies to your contract.
Decision guide: which tool for which problem
Most teams should start with the signal that costs them the most and the tool that is closest to it. The decision table below connects a common need to the tool that usually fits and the reason it does.
| If you need | Start with | Because |
|---|---|---|
| Recovery emails when a card fails | Your billing provider's events, sent through Sequenzy | The payment-failed event can link to the hosted invoice page, and the email platform sends the message |
| Usage trends and feature breadth | Mixpanel or Amplitude | Both are built to show how usage changes over time and across cohorts |
| Journeys from many behavioral events | Customer.io | It triggers journeys from an event stream shared by several teams |
| Health scores for a B2B account book | ChurnZero, or Gainsight for larger operations | Both combine account health with customer success workflows |
| Owners and notes for each account | Close | Champion changes and competitor questions become tasks with an owner |
| Alerts between systems you already use | Make | It connects billing, product and CRM tools without custom code for simple alerts |
How to choose
Start by listing the signals you can already observe. Most teams have billing events and support tickets, and many have product events, even if nobody reads them. Those are the signals to start with, because they cost little to add.
Next, decide where the response will be sent. If the response is an email, the email platform needs access to the events and a clear trigger. If the response is a call from an account owner, the signal has to appear in the CRM or a shared dashboard. A signal that appears in a tool nobody checks will not change any outcome.
Then pick the tool that owns the job. A billing-led team with a small list usually needs a billing source and an email platform, and can add product analytics later. A product-led team with a large user base may start with analytics and add messaging afterwards. A B2B team that manages named accounts will want a CRM with account owners before it buys a health-scoring platform.
Last, check the price against the list size and the number of emails each person will receive. Price is rarely the deciding factor for a small team, but it becomes one as the list grows. Ask whether the cost of the tool is small compared with the revenue from the accounts it is meant to protect, and whether you can measure that protection.
Setting it up in six steps
- Export your last twelve months of cancellations. Include the cancellation reason if you collect one, the date and the plan. This is the baseline you will calibrate against.
- List the events each signal depends on. For failed payments, find the event name in your billing provider. For login frequency, find the authentication or activity event. Write down the exact name and where it is stored.
- Start with three signals. A common starting set is failed payment, falling login frequency and cancellation page visits. Add the rest once the first three produce reliable alerts.
- Assign an owner and a response window to each signal. Write the owner's role and the number of hours or days allowed for the first response.
- Send the first messages and measure them. For payment recovery, track how many customers update their card and how long it takes. For the other signals, track replies and retained accounts. Compare each month with the one before, and set targets only after you have a baseline.
- Review false positives every month. Look at accounts that were flagged and did not cancel, and at cancellations that were not flagged. Adjust the weights and the thresholds, and remove any signal that never leads to a useful response.
If you are moving from a manual process, such as a spreadsheet that customer success updates each Friday, keep the spreadsheet running for one cycle while the automated alerts run in parallel. Compare the two lists. The gap between them shows you which signals the spreadsheet caught and the automation missed, and the reverse.
Pitfalls to plan for
The most common failure is too many alerts. When every login drop creates a task, the team learns to ignore them. Keep the alert list short, and make each alert carry a specific action. The second failure is sending the same message to every flagged customer. A payment failure, a champion change and a competitor question need different messages, and a single generic campaign will fit none of them well.
Seasonality also causes false alarms. Accounts used for year-end reporting, tax work or school terms may go quiet for weeks and come back. Compare each account with its own history, and add a note in the account record when you know a quiet period is expected.
Finally, be careful with privacy. Messages about how a customer uses the product, or about their payment, should follow the terms and privacy notice you have given them, and should be sent from an address they recognize. Limit access to billing and usage data to the people who need it to respond.
Frequently asked questions
Which early warning sign should I watch first?
Start with failed payments, because they are recorded automatically, they have an obvious next step and they can be handled by a short, specific message. Falling login frequency is the next most useful signal for most products, but it needs a baseline for each account before it is reliable. Adding these two gives you a useful first system without a large analytics project.
Do I need a dedicated customer success platform to do this?
Not always. A small team can run a useful early warning system with a billing source, an email platform and a CRM for account notes. Dedicated platforms such as ChurnZero or Gainsight make more sense when you manage many named accounts with their own renewal cycles, and when a human owner needs health scores in one workspace. Both are sold on quote, so compare the total effort, not just the license.
How do I tell a busy customer from one who is at risk?
Compare the customer with their own history rather than with other customers. A customer who logs in less often for two weeks may simply be busy, while one whose activity has fallen steadily for two months, and who has also reduced feature use or stopped replying, deserves attention. Combining signals is more reliable than acting on any single one.
How much does a simple setup cost?
A small setup can begin on free tiers. Amplitude offers a free plan with 2M events a month and no time limit, and Mixpanel's free plan covers up to 1M monthly events. Sequenzy's free plan covers 2,500 emails a month, and paid plans start at $19 a month for 15,000 emails on monthly billing. Make's Free plan includes 1,000 credits a month for connecting systems. Prices rise as volume grows, so check each pricing page against your expected volume.
Can I send recovery messages without sounding automated?
Yes, if the message refers to something specific. A failed-payment message that names the plan, shows the update link and explains what happens next reads as helpful. A generic "we noticed you have not logged in" does not. Send from a named person where possible, and make it easy to reply. Automation can handle the first message and hand the conversation to a person when the customer answers.
What should I do when a warning sign is confirmed but the customer still leaves?
Record the reason, the signal that came first and the response you sent. A cancellation with a clear reason is useful data, because it tells you whether the signal was early enough and whether the response was the right one. Review these records each quarter, and use them to adjust your weights and your messages. A departure is not a failure of the system if the system learns from it.
Should I contact every customer who shows a signal?
No. Start with the accounts where the cost of losing them is highest, and where a response is most likely to change the outcome. Automated messages can cover the rest, provided each one is specific and relevant. Human outreach works best for a small number of high-value accounts, where a short call or a personal note can resolve a problem that a message would not.