Why Unheavy Is a One-Time Purchase (And Always Will Be)

The First Decision I Made

Before I wrote any code, before I had a design, before I knew what the destruction animations would look like — I made one product decision with certainty. Unheavy would not be a subscription.

I want to explain why, because I think the reasoning matters beyond Unheavy. The subscription-versus-one-time decision in a product like this isn't just a pricing model. It's a statement about what the product is allowed to want from the people using it.

What a Subscription Requires

A subscription is a recurring revenue model, which means it depends on recurring engagement. Most businesses treat this as neutral. It isn't neutral when the product is for people in emotional pain.

When your monthly revenue depends on monthly active users, every product decision you make gets filtered through the same question: will this bring people back? Will this keep them opening the app? That question is reasonable for a project management tool. In a mental health-adjacent product, it's structurally misaligned with what people actually need.

What do people in emotional pain need? Sometimes they need to use a tool intensively for two weeks and then not need it for three months. Sometimes they need it once, and the once is enough. The ideal outcome for the user is not necessarily frequent engagement. A subscription business can't afford to build toward that outcome.

The Incentive Drift Problem

Here's how product teams at subscription apps end up building features that subtly harm their users without intending to: they follow the incentives. The metrics say retention is down. The metrics say people aren't coming back. So the team brainstorms engagement features. Streaks. Weekly check-ins. Notification nudges: "You haven't journaled in 3 days."

Each of those decisions is rational from a business perspective. Each of them is potentially harmful in this context. A streak mechanic turns emotional release into a performance you can fail. A reminder notification catches you at an arbitrary moment and inserts a task where there shouldn't be one. The app's needs start to colonize the user's mental space.

I don't think the people building those features are doing anything cynical. I think they're solving the problem they were given. The problem is the incentive structure, not any individual team.

The Guilt Tax

There's a specific thing that happens when you're struggling and you're also subscribed to a wellness app: you stop opening it. Not because it stopped working. Because opening it means confronting the fact that you haven't been using it, that the streak is long broken, that you're paying for something you're not doing.

The subscription becomes another obligation on top of the weight you were already carrying. And when you finally do open it — after the guilt has built up enough — you're not in a neutral state. You're already behind.

I've watched this pattern play out with journaling apps, meditation apps, fitness apps. The product that was supposed to help creates a secondary problem: a recurring, low-grade sense of inadequacy around not using it enough. That's a feature of the business model, not a bug.

Who Gets Hurt Most

The people who most need an emotional release tool are often in the least position to manage a subscription. Someone in a bad stretch isn't tracking their billing cycle. They'll miss the cancellation window. They'll feel charged for something that didn't help. That's a specific cruelty — and one that lands hardest on people who were already struggling.

One-time pricing means: pay once, it's yours. Use it in a hard month and then don't touch it for six months. Come back when you need it. There's no meter running. No message asking why you've been away. The app just waits — zero pressure, zero agenda.

What One-Time Pricing Forces on Me

Here's the honest flip side: one-time pricing is harder to build a business around. I don't get recurring revenue. I don't get second chances if the first impression isn't strong. Every person who downloads Unheavy is a first-and-possibly-only interaction, and the product has to justify itself in that single session.

I think that's the right constraint. It means I can't rely on habit, sunk cost, or inertia. I have to make something that earns its place when someone needs it — and something they're genuinely glad to have when they do.

The counterargument I take seriously: subscription revenue funds ongoing development. If a product genuinely helps people, recurring revenue means it can keep getting better. That's a real argument. I just don't think it applies cleanly here, because the conditions that make subscriptions work — frequent, habitual use — are at odds with what I'm trying to build.

Pricing and Privacy Are the Same Decision

There's a connection I keep coming back to. The most valuable data in a product like this is the content people write — their fears, regrets, the things they can't say out loud. That data is extraordinarily sensitive. A subscription business has a structural incentive to understand its users better over time: their emotional patterns, what brings them back, what keeps them engaged. Data and revenue can become entangled in ways that aren't obvious at first.

I store nothing. No content, no emotional metadata, nothing that could be inferred about what someone wrote. The no-storage decision and the one-time pricing decision came from the same place: I want Unheavy to have no agenda with the person using it. No reason to want more from them than the moment they're in.

The product should want what the user needs. A subscription model makes that very hard to maintain.

The Simplest Version of This

Some tools should be yours. Not rented. Not conditional on continued engagement. Just yours — ready when you need them, silent when you don't.

That's what I was trying to build. The pricing model is how I keep that promise.