DEV Community: Dylan Yu

Why I'm Betting Against Monthly Pricing for My SaaS (Before Any Sales)

Dylan Yu — Mon, 15 Jun 2026 19:39:49 +0000

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.

→ basevolt.app

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.

I built a conversational AI agent that turns your database into a working app — here's what changed

Dylan Yu — Thu, 11 Jun 2026 18:20:16 +0000

There are two kinds of database tools.

One kind helps you manage the database itself — write SQL, edit schemas, run migrations. That's DBeaver, DataGrip, TablePlus.

The other kind helps you work with your data — browse records, track KPIs, build internal views, manage operations. That's Retool, NocoDB, Budibase.

I've been building Basevolt — a local-first desktop app in the second category — and I just shipped something that makes that whole category feel different: a built-in AI agent you can actually have a conversation with.

Not a copilot. Not autocomplete. A full agent that can:

Query your data in plain English ("show me all users who signed up this week")
Create views on your tables ("set up a kanban view grouped by status")
Build dashboards from scratch ("make a dashboard with total signups, MRR, and a chart of signups over time")
Understand your schema and relationships without you explaining them

Here's what the workflow looks like now:

Before: Connect database → manually configure each table → set up field types → create views → build dashboard widgets one by one. 20-30 minutes minimum.

After: Connect database → tell the agent what you need → done in under 2 minutes.

Why this matters more than I expected

When I started building this, I thought the AI agent would be a nice-to-have — a power feature for lazy developers (myself included).

What actually happened: it changed how I think about database tools entirely.

The traditional model for tools like Retool or NocoDB assumes you know what you want and you configure it manually. But most of the time, especially with an unfamiliar database, you're exploring. You're asking questions like "what's in this table?" and "how does this relate to that?" and "what do I actually want to track?"

Conversation is actually the right interface for exploration. Tables and menus are the right interface for after you know what you want.

So now Basevolt does both: you explore and set things up through conversation, then you use the structured UI to work with the results.

How it works technically

The agent has full access to your database schema — tables, columns, relationships, indexes. When you ask a question, it:

Reads your schema to understand what's available
Plans what actions to take (query, create view, build dashboard, etc.)
Executes those actions directly against your local database
Returns results in the most useful format (table, chart, plain answer)

Everything runs locally. The AI calls are the only thing that leaves your machine — your actual data never does.

I also kept the MCP server integration (so Claude, Cursor, Windsurf, and Codex can still connect externally), but the built-in agent is the more accessible version of the same idea.

What I got wrong along the way

First attempt: I tried to make the agent "safe" by only letting it read data, not write. Users immediately asked "can it create views?" and "can it build a dashboard for me?" — the read-only constraint made it feel half-baked.

Second attempt: I gave it full write access but no confirmation step. It created 12 views at once when I asked it to "set up the important views." Too aggressive.

What works: The agent does one thing at a time, shows you what it's about to do, and asks for confirmation on destructive actions. Exploration is fast; mutations are deliberate.

The unexpected use case

I thought power users would love the AI agent. They do, but the people who love it most are the ones who would never have set up the workspace manually in the first place.

If you've ever connected a database to Retool, stared at the blank canvas, and closed it — the AI agent is for you. You don't need to understand views, field types, or dashboard widgets. You just describe what you want to see.

That's the user I didn't build for originally. Now they're the ones most excited about it.

Try it

Basevolt is a local-first desktop app for macOS and Windows that turns your existing database into a working data workspace — views, dashboards, and now AI conversation included. Free tier includes 2 data sources. Pro is $99/year for unlimited sources.

→ basevolt.app

If you're building something similar or have thoughts on conversational interfaces for data tools, I'd love to hear it in the comments.