The Personal Software Revolution
Everyone's talking about vibe coding as the next frontier for indie developers.
I've been building my own calendar booking app this week. Not to sell. Not to launch a startup. Just because Calendly costs $12 a month for something that is, at its core, a form that writes to my calendar. It's making me think about what vibe coding actually unlocks.
The conversation around vibe coding has largely gone to a predictable and familiar place: democratization of software development, the next generation of App Store entrepreneurs, everyday people building the next big thing. It's a compelling narrative. It's also, I think, the less interesting one.
The SaaS Tax
Here’s what I keep coming back to. Think about how many subscriptions you’re paying for right now. Project management. Note-taking. Time tracking. Habit tracking. Calendar scheduling. Link-in-bio pages. Social media scheduling. Each one costs somewhere between $5 and $20 a month. Each one has dozens of features you’ve never touched and never will.
You’re paying for software that is, conservatively, 80% bloat for your use case. That’s not a criticism of the companies building these tools — they have to serve millions of users with different needs, which means features accumulate, interfaces get more complex, and the product drifts further from what any individual person actually wants.
The economic logic of SaaS depends on this. Build for the broad middle. Charge everyone the same. Let the power users subsidize the casual ones. It works. It’s also why your habit tracker has a social feed you’ll never open and your calendar app has team features you’ll never configure.
Vibe coding changes the math. Not for everyone — not yet — but for a growing number of people who are technical enough to describe what they want and patient enough to iterate on it.
An Audience of One
What strikes me about building my own tools is how liberating the constraints become when you’re the only user.
The feature request queue has one item: whatever I need next. The turnaround time is measured in hours, not months. The interface can be exactly as weird as my workflow requires, because nobody else has to understand it. I don’t have to build onboarding, because I already know how it works. I don’t have to handle edge cases I’ll never encounter. I don’t have to worry about scaling.
This is the opposite of how we usually think about software development. The whole industry is oriented toward building for scale — toward finding product-market fit, toward serving the largest possible audience, toward growth curves that justify the venture capital. Building for yourself is almost treated as a failure mode. A side project that never became a real product. A hobby that didn’t monetize.
But what if that’s exactly the point?
What You Actually Own
There’s a secondary argument here that I think matters more as AI agents start mediating more of our digital lives.
When you use a SaaS product, your data lives in someone else’s infrastructure. Your workflows depend on someone else’s roadmap. Your access continues only as long as you keep paying, and only as long as the company keeps existing in its current form. Every subscription is a small dependency, and dependencies accumulate.
I wrote recently about trust as the only remaining moat for consumer brands. Part of that argument was about agentic commerce — AI agents shopping on behalf of consumers, making decisions based on quantifiable signals rather than brand narratives. The same logic applies to personal productivity. The more your work lives in systems you don’t control, the more vulnerable you are to changes you can’t predict.
Building your own tools doesn’t eliminate dependency — you’re still relying on the AI models, the hosting infrastructure, the underlying platforms. But it shifts the relationship. You own the code. You own the data. You can export, modify, migrate. The lock-in dissolves.
The Skills That Transfer
I don’t think everyone needs to build their own calendar app. That would be silly. But I do think there’s something worth paying attention to in how vibe coding changes the skill stack for knowledge workers.
For decades, the divide was clear: technical people built software, everyone else used it. Learning to code was a significant investment, and most people reasonably decided it wasn’t worth it for their career path. The tools kept getting better, the interfaces kept getting more intuitive, and the need to understand what was happening underneath kept receding.
Vibe coding doesn’t eliminate the technical complexity — it abstracts it. You still need to think clearly about what you want. You still need to iterate, debug, refine. You still need to understand enough about how systems work to describe them accurately. But the barrier has dropped from “learn to code” to “learn to communicate with something that codes.”
That’s a different skill. It’s closer to product management than engineering. It’s about specification, not implementation. And it’s increasingly valuable in a world where the implementation layer is getting commoditized.
The Long Game
I don’t know if I’ll finish my calendar app. I don’t know if it’ll be good enough to actually replace Calendly. The $12 a month isn’t really the point — it’s pocket change, and the time I’m spending building probably doesn’t pencil out on a purely economic basis.
But something is shifting. The tools are getting good enough that building for yourself is becoming a legitimate option, not just for developers, but for anyone who can articulate what they need clearly enough. The premium for mass-market software is starting to look less like convenience and more like a tax on people who don’t realize they have other options.
The future of vibe coding isn’t, I think, a flood of new apps on the App Store. It’s something quieter. Millions of personal tools that never get published anywhere, because they don’t need to be. Software built for an audience of one, doing exactly what that one person needs.
The most valuable software you use might eventually be software you built yourself. Not because it’s better in any objective sense. Because it’s yours.
*This article was originally published on rebeccaraebarton.com
