Back to blog
#pricing#indie-dev#business

Why I charge $99 once instead of $20/month

I don't host anything. I don't run servers. There's no cloud. My costs are zero after you download the app. Why would I charge you rent?

Why I charge $99 once instead of $20/month

The pitch I refused to make

Every SaaS pricing page says the same thing. "$20/month, cancel anytime, start your free trial." It sounds cheap. Twenty bucks. That's a lunch. You don't even think about it.

Until month six.

Let's do the math

| Model | Month 1 | Month 6 | Year 1 | Year 2 | |---|---|---|---|---| | $20/month subscription | $20 | $120 | $240 | $480 | | $99 one-time | $99 | $99 | $99 | $99 |

By month 5, you've already paid $100 on the subscription. You've now spent more than the one-time price and you own nothing. Stop paying, lose access. Keep paying, and by the end of year one you've handed over $240 for software that runs entirely on your machine.

Two years in, you're at $480.

For a desktop app. That doesn't use my servers. That doesn't store your data in my cloud. That connects to AI providers using your own API keys.

Tell me how $20/month makes sense here. I'll wait.

My costs after you download Zowl

Zero.

I'm not exaggerating. Let me break it down.

Hosting: There's no hosting. Zowl is a native macOS app. It runs on your Mac. It stays on your Mac. I don't run a backend. I don't maintain a database with your account in it. There's no server somewhere in Virginia keeping your sessions alive.

AI costs: You bring your own API keys. When Zowl sends a prompt to Claude or GPT-4, that API call goes from your machine to Anthropic or OpenAI. I'm not proxying it. I'm not skimming a margin on your token usage. Your keys, your bill, your business.

Storage: Your tasks, your PRDs, your pipeline configs, your logs. All local. All on your filesystem. I never see any of it.

So after you buy Zowl and activate it, my ongoing cost to support your usage is practically nothing.

Why would I charge you monthly rent on software that costs me nothing to deliver?

The subscription model makes sense sometimes

I want to be fair. Subscriptions aren't always a scam.

If you're running Figma, your files live on their servers. They maintain a real-time collaboration engine. They handle multiplayer cursors, version history, component libraries synced across teams. That costs real money every month. A subscription makes sense.

If you're using Notion, same deal. Your data is in their cloud. They run servers, backups, search indexes, API infrastructure. Monthly costs, monthly price. Fair.

Slack, GitHub, Linear, Vercel. All cloud services with real ongoing infrastructure costs. Subscriptions are the right model for those.

But Zowl isn't any of those things. Zowl is a desktop application. It's closer to Sublime Text than it is to Notion. And Sublime Text got this right years ago: pay once, use forever.

Here's my actual opinion, and it's spicy

Subscriptions for local software are a scam.

Not a harsh take. Not controversial. A scam. When a company charges you $10/month for an app that runs entirely on your computer, processes data locally, and doesn't touch their servers, they're charging you rent on something you already have. They're betting on inertia. They're hoping you forget to cancel, or that the switching cost feels too high, or that you've built enough muscle memory that you'll keep paying just to avoid relearning something new.

I know why devs do it. Recurring revenue looks amazing on a pitch deck. Investors love MRR. VCs want to see that hockey stick. And the truth is, subscriptions are easier to grow because the revenue compounds month over month instead of requiring new customers every cycle.

But I'm not raising venture capital. I'm an indie dev building a tool I use myself. I don't need to impress a board. I need to build something good enough that people want to pay for it, and then let them pay for it once, like adults buying a tool.

What you actually get for $99

The Pro license gives you Zowl with all current features, forever. Every update within the v1 lifecycle. No feature gates. No "upgrade to unlock pipelines" nonsense. The full app.

If I release v2 with a major new architecture or significant new capabilities, that's a new purchase. You decide if it's worth it. If it's not, v1 still works. It doesn't phone home and self-destruct because you didn't re-up. It's software you bought. It's yours.

There's also a free tier. You can run Zowl with a single pipeline and up to 5 tasks. No time limit. No "14-day trial" with a credit card form lurking behind it. Use the free tier for as long as you want. If you need more, you know where the buy button is.

The race to recurring revenue broke something

I've been a developer long enough to remember when you bought software. You walked into a store (or downloaded it from a website that looked like it was built in 1998), paid your money, and owned the thing. It worked until you decided to upgrade.

Somewhere around 2015, the entire industry decided that was stupid and everyone should rent everything. Adobe went subscription. Microsoft went subscription. Even apps that had no business being subscription went subscription. A PDF editor for $8/month. A calculator app with a $3/month "pro" tier. A notes app that charges you rent to store plain text files on your own hard drive.

We lost something when that happened.

I paid for a code editor license from Panic (the folks who make Nova) in 2023. One-time purchase. It still works. It gets updates. I don't think about it. That's how buying software should feel. You pay, you use it, it's done. No monthly anxiety about whether you're "getting your money's worth." No guilt-scrolling through your subscriptions trying to figure out which five to cancel.

Why this works for me financially

People ask me this a lot. "How do you sustain a business on one-time purchases?"

New customers. That's it.

If Zowl is good, people tell other people. If the product keeps improving, new developers find it and buy it. I don't need to extract ongoing revenue from existing customers. I need to make something worth buying and keep making it worth buying.

When I started building Zowl, I charged $49. Raised it to $99 when the feature set justified it. I'll probably raise it again for v2. Each price reflects the value at that moment. You pay for what exists, not for what I promise to build over the next 12 months of your subscription.

The day I can't attract new customers is the day the product isn't good enough. That's a healthy pressure. It keeps me shipping.

One more thing

I track the numbers. The average Zowl Pro user would've paid $320 under a $20/month model by now (based on average time since purchase). They paid $99 instead. That's $221 they kept. Multiply by every Pro user, and that's real money that stayed in developers' pockets instead of mine.

I'm fine with that. I'm still here, still shipping, still paying my bills from home. If Zowl saves you hours of work every week and it cost you less than a nice dinner, the math works for both of us. That's the whole model. This philosophy is complemented by the infrastructure-free approach and how Zowl requires zero backend infrastructure, which makes this pricing possible. No tricks, no drip pricing, no "your card will be charged" emails at 3 AM. You bought Zowl. It's yours. Go build something with it.