Subscription fatigue is real and I'm not adding to it

Do the exercise

Open your bank statement. Or your password manager. Or that spreadsheet you definitely don't have where you track subscriptions (you have one, don't lie).

Count every developer tool you pay for monthly. Not Netflix, not Spotify. Just dev tools. The code editor plugin. The CI runner tier. The hosted database. The monitoring dashboard. The design tool. The project management app. The domain registrar that quietly switched to monthly billing. The AI tool with usage-based pricing that fluctuates every month.

Got your number? Multiply it by 12.

That's what you actually spend per year on developer tools. Most people I talk to land somewhere between $1,500 and $4,000. Some are way higher. One freelancer I know added it up and almost choked: $6,200 a year, and half of those tools he hadn't opened in months.

The $15/month illusion

Nobody thinks about subscriptions in annual terms. That's by design.

$15/month doesn't feel like $180/year. $29/month doesn't feel like $348/year. $49/month doesn't feel like $588/year. The monthly framing is the entire trick. You compare it to a coffee. "That's less than a lunch!" Yeah, and 12 lunches is $180 you spend without ever making a conscious annual decision.

Every subscription is a bet that you'll keep using the tool long enough to justify the ongoing cost. And every company offering a subscription is betting that you won't cancel even when you stop using it. They're usually right. The average SaaS churn rate is something like 5-7% monthly. That means most people keep paying for months after they've stopped getting value.

I've done it myself. I paid for a hosted Postgres instance for four months after I'd already migrated that project to SQLite. I paid for a monitoring tool for a side project that I'd shelved. I paid for a premium tier of a note-taking app because downgrading meant exporting my data first and I kept putting it off.

Each one was "just" $10-20 a month. Together they were over $100 a month of pure waste.

Why local tools shouldn't charge rent

Here's where I get opinionated.

Some tools genuinely need a subscription. If the company is running servers for you, storing your data, maintaining uptime, handling your traffic, they have real monthly costs. A subscription maps to their cost structure. Fair enough.

But when a tool runs entirely on your machine? When it uses your compute, your storage, your API keys, and doesn't phone home to any server? What exactly is the monthly charge for?

You're renting software that's already on your hard drive. The company's ongoing cost to serve you is approximately zero. But they charge you $15/month because recurring revenue looks good on their metrics dashboard and investors love MRR charts that go up and to the right.

I find that gross. I especially find it gross when the tool in question is aimed at developers, because developers should know better than anyone what software actually costs to deliver. If you're interested in understanding the economics differently, check out our reasoning behind one-time pricing and how we minimize infrastructure costs.

Zowl is $99 once

I built Zowl as a native macOS app. It runs on your Mac. Your API keys, your filesystem, your CPU. After you download and activate it, my cost to support your usage is effectively nothing. There's no backend. There's no database with your account. There's no server cluster keeping your sessions alive.

So the price is $99. Once. You get the full app. Every update within the v1 lifecycle. No feature gates. No "upgrade to unlock pipelines." No "your trial expires in 3 days" banner that follows you around the UI.

If I release a v2 with major new capabilities, that'll be a separate purchase. You decide if the upgrade is worth it. If it's not, v1 keeps working. It doesn't stop functioning because you didn't renew. It's software you bought. It belongs to you.

There's also a free tier. One pipeline, up to 5 tasks, no time limit. Not a trial. Not a "taste" that expires. A real free version you can use for as long as you want.

"But how do you sustain a business?"

People ask me this like one-time purchases are some radical experiment. They're not. They're how software worked for decades before the subscription era.

Sublime Text charges once. Panic charges once for Nova. Sketch charged once for years (before they switched to subscriptions, and a lot of people were annoyed about it). These businesses survived and thrived on new customers, not on extracting recurring revenue from existing ones.

My model is simple: make Zowl good enough that people tell other people. New customers show up. They buy it. I keep improving the product so the next person who finds it also thinks it's worth $99. That's the whole flywheel.

The day I can't attract new buyers is the day the product isn't good enough. That's a healthy pressure. It forces me to keep shipping features that matter instead of coasting on renewal inertia.

The subscription model incentivizes the wrong things

When your revenue comes from renewals, your biggest risk is churn. So what do you optimize for? Retention. Stickiness. Making it hard to leave. Lock-in features. Proprietary file formats. Export flows that are deliberately painful. "Are you sure you want to cancel?" pages with four guilt-trip screens.

None of that makes the product better. It just makes the product harder to leave. Those are different things and the subscription model conflates them.

With one-time purchases, I don't care about lock-in. If you buy Zowl and switch to something else next year, I already got paid. I don't need to trap you. My incentive is to make v2 compelling enough that you choose to buy it, not to make v1 annoying enough that you feel stuck.

Your tasks, your PRDs, your pipeline configs, your logs. All stored as regular files on your Mac. You can read them, copy them, move them, delete them. Nothing is locked in a proprietary database that only Zowl can open. If you leave, you take everything with you.

The market is correcting

I'm not the only one doing this. There's a growing pushback against subscription pricing for tools that don't need it. Developers are tired. They're counting their monthly charges and getting angry about it.

Every few weeks I see a post on Hacker News or Twitter where someone lists their monthly dev tool costs and the replies are full of people saying "same" and sharing their own embarrassing totals. The sentiment has shifted. Five years ago, subscriptions were the default and one-time pricing was seen as unsustainable. Now, one-time pricing is a selling point. People actively seek out tools that respect their wallet.

I think this is healthy. Subscription pricing won when it was genuinely better for users (pay less upfront, always get updates, lower commitment). But it overshot. It spread to tools where it makes no sense, justified by investor pressure rather than actual cost structure. The correction was inevitable.

$99, once, done

I'm not going to pretend this is charity. I charge $99 because Zowl is worth $99. If it saves you even a few hours of work per week, you've made your money back in the first month. By month two, it's free. And it stays free forever because there's no month three charge.

Count your subscriptions again. Imagine replacing even two or three of them with one-time purchases. That's hundreds back in your pocket per year. Not because you're using fewer tools. Because the tools you're using respect the fact that they live on your machine and cost nothing to deliver after the first download.

That's the model. That's why I chose it. And that's why I'm not adding another line to your monthly statement. Try Zowl and see what paying once for software actually feels like.