Why I built Retain (after watching my own customers disappear)

Hi, I'm Gabriel. Before Retain, I built Save Now, a SaaS for aesthetic and beauty clinics. This is the story of how losing customers in silence turned into Retain.

Building Save Now, and watching customers vanish

Save Now helped clinics manage bookings, clients, and the day-to-day of running an aesthetics practice. We were growing. New clinics signed up every week, onboarding looked fine, and the product mostly worked.

And then, every so often, a clinic would just stop.

No support ticket. No "we're switching to a competitor." No angry email about a missing feature. One month the account was active, booking clients, paying on time. The next month, nothing. Login stopped. Payment lapsed. Gone.

There was no complaint to respond to, no objection to overcome. Just silence, and then a churned account on a spreadsheet I didn't want to open.

The frustration that pushed me into retention

Here's the part that got to me: I'd worked hard for every one of those customers. Ran the ads, did the demo calls, walked owners through their first week. Spent real money and real time turning a stranger into a paying clinic.

And then they left without telling me why. I couldn't fix what I didn't understand, and I couldn't understand what nobody was telling me.

That frustration is what pushed me deep into retention. Not as a feature to build, at first, just as a question I couldn't let go of: what actually happens between "paying customer" and "gone"?

The signals were there the whole time

Once I started looking, the silence wasn't really silent. Every account that churned had left a trail, I just hadn't been looking at it.

Incomplete onboarding. Clinics that never finished setting up their first week of bookings rarely made it past month two. They'd signed up, poked around, and quietly stalled before the product ever became part of their routine.

Low or dropping activity. The clinics about to churn weren't using Save Now less because they said so. Login frequency and bookings-per-week just started sliding, weeks before the cancellation.

Unused features. Some clinics never touched the parts of the product that actually created a habit, like recurring client reminders. They were using Save Now as a glorified calendar, not the tool it was built to be, and that's a much easier relationship to walk away from.

Failed payments. The most obvious signal, and the one I was most likely to miss, because a failed card doesn't always trigger anything that gets in front of you in real time.

None of these signals, on their own, screamed "this account is leaving." But together, weeks before the cancel, they were about as close to a warning label as you could ask for.

What the signals also told me about my product

The signals didn't just predict who was going to churn. They exposed exactly where the product was falling short.

The clinics stuck on incomplete onboarding weren't lazy, our onboarding had a gap. The ones ignoring the features that actually created habit weren't the wrong customers, we hadn't shown them why those features mattered. I wasn't just building a churn early-warning system. I was reading a map of everything that needed fixing, drawn by the customers who left before I could ask them.

That's how Retain was born

Turns out, this wasn't just my problem. A lot of lean SaaS teams are flying blind the same way I was, losing customers without ever knowing why, because the signals live scattered across product events and payment data that nobody's connecting.

Retain is what I built so I'd never have to open that spreadsheet again without knowing exactly why an account was on it. It watches the same signals I was chasing by hand at Save Now, incomplete onboarding, usage trend, key feature adoption, failed payments, and tells you which one actually predicts churn for your product, before the cancel button gets clicked.

If this sounds like your spreadsheet too, sign up for free and see what your own churn signals are already telling you.