Early in building Miser, someone asked us: "What happens when a user wants to stop?"
It sounds like a strange question for a startup to sit with. The usual answer is: you design for retention. You make the exit buried and confusing. You send re-engagement emails. You make leaving feel expensive enough that most people won't bother.
We went the other direction. We built what we call Quit Companion.
What it does
When you decide to stop using Miser, the app doesn't just close your account and wish you well. It walks you through a short exit: it shows you what you saved while you were here, asks you one question about why you're leaving, and closes out your account cleanly.
If there's money in your savings, it goes back to your checking account, free, no waiting period. The reflection card at the end isn't a guilt trip. It's just: here's what happened while you were here. You decide what it means.
That's it. You're out.
Why we built it that way
The standard playbook is friction. Make the cancel flow hard to find. Ask the user to confirm three times. Offer a discount on the way out. Show them a projection of what they'd be giving up. The goal is to make leaving feel costly enough that most people give up and stay.
This works, in a narrow sense. Churn numbers go down. Retention looks better on a slide.
The problem is that it creates a different kind of relationship, one where the user knows, somewhere, that the app is working against their interests at the exact moment they've decided something isn't working. And once someone feels that, the trust erodes. Every feature starts to look like a hook rather than a tool.
We're building a savings app. Trust is the whole product. If you're linking your bank account and letting the app move money on your behalf every Sunday, you have to believe it's working for you, not for our retention numbers.
An app that makes leaving hard has a business model problem. If users only stay because the exit is painful, that's not retention. That's capture.
The bet underneath the decision
Here's the actual reasoning: we think making Quit Companion as clean as possible will result in more people staying, not fewer.
When leaving is easy, you're not staying to protect yourself. You're not worried about losing access to something you need, or your money sitting in limbo, or canceling taking three phone calls. You're free to go whenever the app stops serving you.
That freedom changes the relationship. You're not locked in, you're choosing to be here. And people who are choosing to be somewhere behave differently from people who are stuck somewhere. They give you honest feedback instead of quietly resenting the product. They come back when they're ready. They tell friends accurately instead of through gritted teeth.
None of that shows up on a short-term retention chart. But it's the difference between a product people trust and one people tolerate.
What building it taught us
One thing we didn't expect: building the quit flow forced us to get clear on what we actually wanted users to take with them when they left.
The reflection card asks one question. Writing the right question, not manipulative, not fishing for "please reconsider," genuinely curious, turned out to be harder than the feature engineering. We rewrote it six times. The first versions were all subtly angled toward getting the user to stay. The right version just asks: what was saving like for you while you were here?
That's the question that gives us real signal. And it's the question we'd want someone to ask us if we were the ones leaving.
Making it easy to leave is how we earn the stay.