I Charged $4.99 For Klozer For Six Months. It Was Wrong.

Klozer launched at $4.99 one-time purchase. I thought I was being generous. A closet organizer app with outfit planning and wear tracking, no subscription, pay once and own it. That's the kind of app I want to buy. So that's the kind of app I shipped.

Six months later I looked at the numbers and felt sick.

What the numbers actually said

At $4.99 one-time, after Apple's cut, I was netting roughly $3.49 per buyer. Conversion from install to purchase sat around 2.8%. Do the math on 1,000 installs: 28 buyers, about $98 in revenue. Acquisition through any paid channel was a non-starter. Even organic was barely paying for the backend costs of image storage.

Worse, I had no incentive to keep building. A user who paid $4.99 in March was the same revenue line whether I shipped twelve updates or zero. Compounding work, flat revenue.

The thing nobody tells you about one-time pricing on a utility app: your best users, the ones logging outfits weekly, cost you more in storage and sync than your dormant users. You are literally losing money on the people who love your app most.

The pivot

I switched Klozer to a freemium model with a $3.99/month or $24.99/year subscription in October. Free tier gets 30 clothing items, basic outfit planning, no wear analytics. Paid removes the cap and unlocks the wear tracking, packing lists, and seasonal stats.

Existing buyers got everything free, forever. That part wasn't negotiable. They paid for an app, they get the app.

Three months in:

• Conversion install-to-paid dropped to about 1.4% (half of before, expected)
• But ARPU on a paying user went from $3.49 lifetime to roughly $19 in year one
• Free users actually became useful. They generate reviews, word of mouth, and a meaningful share convert after their closet hits the 30-item cap, which is usually month two or three.

Revenue is up roughly 5x on similar install volume. I can finally justify spending a weekend on a feature that only 8% of users will touch.

What I'd tell myself in March

Stop confusing your pricing preferences with your business model. I don't like subscriptions either. I have eleven of them on my phone right now and I resent at least four. But a utility app that stores user data, syncs across devices, and needs ongoing development is not a one-time purchase product. It's a service. Pricing it like a service is honest, not greedy.

The other thing: $4.99 anchored Klozer as cheap. Reviewers compared it to free apps. At $3.99/month it gets compared to other paid tools, and the conversation shifts from "is this worth five bucks" to "is this worth replacing my Notes app screenshots." That's a much better conversation.

What I'm not sure about yet

I still don't know if the annual plan should be $24.99 or $29.99. I picked $24.99 because it felt clean. That might be another mistake I write about in six months.

I also haven't figured out lifetime pricing. People ask for it. My gut says $79 but I haven't tested it. The risk is the same one I just escaped, locking in a flat revenue user who costs me money over time. So probably no lifetime tier. Probably.

The real lesson isn't "charge more." It's that a price you'd happily pay as a customer can quietly kill the app you're trying to build. Your job as the developer isn't to be the nicest store in town. It's to stay alive long enough to ship version 2.