The cancellation happens before the second invoice. The decision happened in the first week, and by then you had already lost the argument.
Second-month cancellations are decided in the first week, when the product asked for setup work before it produced a result. The fix is to compress the time between signup and the first real outcome, ideally into one session, rather than to add retention emails at the end. Context for how normal this feels: across 3,611 tracked startups, 40.8% shrank over the trailing 30 days and only 35.6% grew.
Here is the sequence almost every second-month cancellation follows. The customer signs up, hits a screen that asks them to connect something or import something or configure something, does part of it, gets interrupted, and never comes back. Three weeks later an invoice arrives for a product they have not opened. They cancel.
Nothing about that is a month-two event. The product lost in the first fifteen minutes; month two is just when the billing system caught up. This is why win-back campaigns fired at day twenty-eight perform so badly. They are arguing with a decision that is three weeks old.
User signs up, lands on a dashboard with 47 options, has no idea what to click first, and churns in a week.
via r/SaaS
The diagnostic question is not "why did they cancel" but "what was the last thing they did before they stopped coming back". That event is almost always in the first session, and it is almost always a piece of work you asked them to do before you had given them anything.
Founders lose a few customers in month two and conclude something is uniquely wrong with their product. Some context on that.
Two things follow from that. First, do not rebuild your product because of one month of numbers. Second, and more useful: since most products are flat or shrinking most of the time, retention is where the available advantage is. Almost everyone is pouring customers into a leaking bucket and buying more water.
The single highest-leverage change is reducing the time between "signed up" and "got something they wanted". Some concrete ways to do it, roughly in order of effect:
Write down every click, form and wait between the landing page and the first result, then delete half of them. That list, not your roadmap, is what determines month-two retention.
A simple behavioural sequence beats a calendar-based one. Trigger on what the customer did, not on what day it is:
| Signal | What it means | What to do |
|---|---|---|
| Signed up, no first action within 24h | The first step is too big | One email, one link, straight to the action |
| Got the first result | They understand the value | Show them the second use case, nothing else |
| No return visit in 7 days | They are already gone | Personal note: what got in the way? |
| Used it, then stopped | Something broke or ran out | Look at their account before you email |
| Returned 3+ times in week one | This is a real customer | Ask them what is missing. They will tell you |
The sequence that carries this is in a SaaS onboarding email sequence that gets opened.
Ask one question, and make it open: what were you hoping this would do for you? Not a multiple-choice exit survey, which mostly collects the option nearest the cursor. The free-text answers are the most valuable research you will ever get for free, because they come from people who have no reason left to be polite.
Then let them go cleanly. Do not hide the cancel button, do not require an email to the support address, do not break what they built. Retention bought through friction is not retention, and it has a cost you cannot see in the dashboard:
the hostage model doesn’t create stickiness, it creates distrust.
via r/SaaS
A customer who leaves easily and well will recommend you. A customer who had to fight their way out will tell a different story, to more people, for longer.
Revenue direction was computed on 22 September 2026 across the TrustMRR corpus, restricted to the 3,611 tracked startups reporting both revenue above zero and a trailing 30-day growth figure. "Shrank" means a negative 30-day change, "flat" means exactly zero. This is a revenue movement measure, not a customer churn rate: we do not hold a reliable cohort-level churn figure, and the churn fields in our acquisition-listing corpus are too sparse to publish. We would rather show you the number we actually have than a churn benchmark we would be inventing.
BigIdeasDB Research. (2026). Why SaaS customers churn in month two. BigIdeasDB. Retrieved from https://bigideasdb.com/guides/why-saas-customers-churn-in-month-two