Every pricing advice for SaaS says the same thing: charge monthly, optimize for MRR, grow that recurring revenue.
I'm ignoring all of it.
Basevolt — my local-first database admin panel — is priced at $99/year flat. No monthly option. No per-seat pricing. Just $99, once per year, unlimited everything.
I haven't made a single sale yet. But here's why I chose this model anyway, and why I think it's the honest choice for this product.
The math that looks wrong (but feels right)
At $50/month, I'd need 24 customers to hit $1,200 MRR.
At $99/year, I need 12 customers to hit the same revenue in year one.
The SaaS playbook says this is leaving money on the table. No expansion revenue. No "land and expand."
But I'm not building for the VC playbook. I'm building for:
- Solo developers
- Side projects
- Small teams who hate subscription creep
These people don't want to calculate "if we add 3 more seats next quarter, what's our run rate?" They want to know exactly what this costs, forever.
What I'm betting will happen
Higher intent, lower volume.
The $99 upfront will filter out tire-kickers. People who balk at $99 aren't my customers anyway. People who see $99/year and think "that's reasonable for a tool I use daily" will convert with less hesitation.
No "I'll start the trial and decide later." No "let me check budget next quarter." Just: yes, this solves my problem, here's $99.
Different churn psychology.
With monthly, every billing cycle is a decision point: "is this still worth it?"
With annual, the question becomes: "I've already paid, how do I get value from this?"
I'm betting this reduces churn anxiety and increases actual usage.
Fewer support headaches.
I've seen it with other products: monthly subscribers generate "how do I cancel" tickets. Annual customers are more invested in figuring things out.
If I'm wrong, I'll find out soon enough.
The risks I'm accepting
Cash flow will be lumpy.
If I get 10 sales in January, then 2 in February, that's terrifying when you're bootstrapped. MRR is predictable. Annual revenue comes in waves.
I'm betting I can survive the volatility.
No automatic expansion.
Per-seat SaaS loves this: customer grows from 5 to 50 people, revenue grows 10x automatically. My model? I have to build real Pro features that add value, not just charge more for usage.
Some people will bounce.
A segment of prospects will want monthly. Some will bail when I say no. I'm accepting that trade-off. The positioning is part of the product.
Why I still think it's the right call
Basevolt is local-first. Your data never leaves your machine. No cloud costs on my end. No per-seat complexity.
The value proposition is "buy once, own it." Forcing monthly pricing would feel like a gym membership for a bicycle I sold you.
If I were building a collaborative cloud tool, I'd probably do per-seat. The economics demand it. But for a personal desktop app? The honest price is a flat fee.
What I know so far
- Beta feedback: People love the "no subscription" pitch
- Pre-launch emails: Multiple people specifically said "thank god, no monthly fee"
- Competitor reviews: "Pricing is confusing" and "another subscription" are common complaints for Retool/NocoDB
The market of people exhausted by subscription creep exists. They're just quieter than the people complaining about price increases.
The bet I'm making
If you're VC-backed, this is probably the wrong call. Your investors want that MRR line going up and to the right.
If you're bootstrapped, building a tool you use yourself, targeting developers who hate bullshit pricing: consider it.
I'll report back in 60 days with real numbers. If I'm wrong, you'll get an honest post about why monthly pricing won.
Either way, we'll know.
Basevolt is a local-first database admin panel for PostgreSQL, MySQL, and SQLite. $99/year, unlimited data sources, no per-seat nonsense.
If you're also experimenting with non-subscription pricing, or think I'm making a huge mistake, I'd love to hear it in the comments.
Top comments (1)
The churn psychology point is stronger than you might realize. Annual billing does not just reduce churn anxiety for the customer. It changes your own decision-making as a founder.
With monthly billing, you are constantly optimizing for retention metrics. Every feature decision gets filtered through "will this reduce churn next month?" That pressure makes you build for the noisiest users (the ones threatening to cancel) instead of the ones who actually represent your best customer profile.
With annual, you get a year of usage data before renewal. You can see which features people actually use vs which ones they asked for and forgot about. That signal is dramatically cleaner.
One risk you did not mention: the refund window. If someone buys at $99 and hits a frustration point in week two, the refund request feels bigger than canceling a $9/mo subscription. You will want a clear policy up front, and you might consider a 14-day full refund guarantee to reduce the perceived risk of that upfront payment. It converts fence-sitters without costing you much because the people who request refunds in the first two weeks were never going to be retained customers anyway.
The competitor review signal ("another subscription" as a complaint) is the most useful data in this whole post. That is not you guessing at positioning. That is real customers in your category telling you what they hate. Build your landing page around that.