btw, someone else having the same idea you have for a saas company has always been the case forever. Individuals taking shortcuts in quality to get to market faster has also been the case forever. There's nothing new about either of those two things.
And yet, Patrick Rothfuss's The Name Of The Wind is the same concept, and sold over a million copes,
Lev Grossman's The Magicians is again the same concept, sold millions, and was adapted into a 5 season TV series for SyFy.
If anything, the success of an idea only leads to a bigger appetite for that idea.
Google was not the first search engine.
If every coked up SDR can build a tech stack, then every junior SWE can get superhuman SEO.
If every product has superhuman seo and engineering, and there are 10 or 100x more products, then probably everyone uses the exact right one for their needs, and quality for your specific usecase is higher. (More competition means more quality, more of every differentiator, including lower prices. )
In a world of zero marginal cost of production (turning ideas into reality with a prompt), maybe it’s hard for anyone to eke out profit margin; I can’t see what anyone’s edge would be in this world. The end state here is much more disruptive than “dang, a coked up sdr out-competed me on my SaaS ide-“.
When you write operational critical code, it matters. No one can blame “the AI made me do it” when things go down and hundreds of thousands of people are without service.
When your code can hurt people, it matters. You can’t burn someone’s eye with a laser then point to some AI agent when lawsuits start flying in.
When millions of dollars in production data is lost or corrupted, who is responsible? Not AI. Quality matters.
I keep hearing this one phrase about code quality again and again. Sure, no one cares about the dumb little linter failing your builds, but when code quality comes to responsibility, it goes hand in hand. It’s either that or your all working on hobby projects.
More importantly, I bet none of the companies running with that level of risk are touching Generative AI powered tools with a 30 feet pole. Maybe Boeing.
Many people I know are using GenAI in their day to day professional lives, and loving it. I'm not one of them. I'm a quality freak. While development is not my primary job, I love to write dependable code, which lets me to sleep well at night and forget that it even exists after some point.
But not everyone is enjoying and caring about their job and quality of their work, as long as they get paid and tick boxes. Even in companies where people write millions lines of code touching billions of people's lives (e.g.: Microsoft).
Time to market, retention, engagement, getting that promotion, a new car, meeting KPIs are more important than that pesky thing called quality. Because it slows them down. They are doing something amazing, so they need no permission, and the new amazing thing is "software built with AI in record time with less developers". letter Q in previous sentence stands for quality, if you find one.
That's why AI is hurting us so much right now.
We were always trying to have quality in our project, whether it was for readability or for code evolution.
No, Steve, you don't name your 42 variables with only two letter and no you don't use Norse mythology for naming servers in your infrastructure. Yes Odin is the most powerful so it's the production server but Tyr for the source control and print server isn't really obvious.
Well now AI is Steve.
It will create nice little 300 lines functions with a block repeating 6 times. You know that you will have 6 fix to make instead of one if this block was in a simple function.
It's not instinct a this point, is pure knowledge screaming "it's wrong".
And you now realise that the hidden strength from your craft wasn't about coding the best binary tree search algorithm, it was about knowing the underlying soft unknowns that really made it software.
We have a strong feeling that we're watching dozens of kids running with scissors and we don't know whether it's really scissors, we're just getting too old for this shit, or if we should just stop "progress" because we don't like it.
We're the horse breeders when everyone discovered cars.
Margins are worse, but selling is easier. If you've got a thing you can be sure that someone somewhere will give you money for it.
You can't hope to succeed by building something cool without distribution already figured out. If you haven't put the work in building a social following, you're pretty much locked into pay to play (which isn't horrible if you target small targeted bloggers/youtubers/etc, but it's not my bag). OpenClaw exploded because Peter has >100k twitter followers and among them are plenty of people who themselves have a ton of followers.
So, if you're building, you also need to focus on building an audience.
The high touch enterprise sales strategy is solid though, and easier to bootstrap. That's why Alex Hormozi and Dan Martell push people getting started that way.
The game has change. The ‘how’ we build it is easy. The ‘what’ we build is and always has been the hardest part of any SaaS or business.
Let's say you could vibe your own replacement to a $20/month app in 16 hours. Congratulations, you did work valued at an $15/hour less token expenses (over 1 year).
I say the only way to build a successful long term product is by focusing on quality, ESPECIALLY when the competition is shitting out crap.
Build something else!
This blog post seems to fundamentally misunderstand the nature of solo-developer SaaS, but then again arguably mostly software developers also fundamentally misunderstand it.
I like his sense of humour.
On most days I am resistant to stereotypes about "the welfare state" eroding incentives for entrepreneurism and innovation. But if you're going to wave it in my face like that, I might have to reconsider.
You can test this, if you talk about your idea to three people and one of them says we're already doing that and the other two think you're insane, you'd be safe.
Based on Louis Rossmann's rant 3 days ago [1], it seems Gemini has got you covered on that front too.
There was one PM at my ex-job that showed a dashboard for... well... i honestly didnt understand. I think it was some uptime checks. It broke during his presentation.
There's a company I hired at that "built an ERP in 5 days and is shipping the product in June". Same thing happened, it broke when presenting. Basic feature suggestions just returned a "Yes, we can do that!" (they meant they can tell Claude to do it, not that the product could do it).
Maybe at some point non-engineers can prompt build, but for now I'd say we're pretty safe. I think engineers give themselves too little credit. Being able to read code is an amazing tool that can only be sharpened through skill.
Lastly, I think I commented this ~2 years ago as well. If your product is vibe-codable and is replacing customers, it's a shit product. Similarly, if you can outsource your product on fiverr, its's a shit product.
I mean, it seems at the very least, that open source and in-house production has a natural advantage here? If the marginal cost of software production is now free, then FOSS/in-house just got easier to create and maintain too. Does that make it easier for FOSS/in-house, both available without a subscription to an external third party, undermine "sales critter" SAAS, by the author's own premises?
Quality will matter the most in 2026. Specifically because the barrier-to-entry for making software is down there will of course be a lot of poor quality software, which will break, expose customer data, be bloated, etc. Customers will have more options, and this will allow them to be more discerning. Open source, clean code, low dependencies...these are things that can be evaluated by HN crowd types, but it's also something that an LLM can evaluate.
We are entering into an age of software taste. For those of us that have developed taste over the years, we become the taste makers in that we care how things are built, and know what we're looking for. This applies on the supply side, when our taste drives the LLM, and on the consumption side, when we can help the masses evaluate what to use and what not to use.
NB: this is all speculation expressed as fact, in keeping with the OP's style.
That's funny and all but it can't really be true that quality doesn't matter. It has to matter at some point. Maybe it doesn't matter during the initial sales cycle; I've seen it happen: the CEO sees a slick demo that works, every user / developper rolls their eyes and try to warn them, they don't listen, and the deal is done.
But eventually if the thing that's supposed to be done, isn't, something will have to give. Even if at first they fire all the eye-rollers and replace them with obedient corporate drones, if the think isn't working and it's on the critical path, it will have to be replaced by something that actually does work.
The models are increasingly capable in impressive ways. Maybe the next gen will enable the "sales critter" to slop out commercially viable software with no tech know-how. If not, I'm sure we'll assume the next can, and if not that, the next.
But feigning confidence about the shape and nature of this unfurling sea-change is absurd when the high-profile examples we have are like, what, moltbook? And denigrate _all_ potential ingenuity and insight unilaterally into the bargain? What a careless way of looking at the world
The specifics matter here. If you run a CRM for Dentists, can someone replicate your product in a weekend? I'm going to guess that dentists have some esoteric needs related to their CRM, and it's a little more complicated than an outsider might guess.
So what is the threat model? That a dentist is going to get fed up and try to DIY? I think you should encourage that, so they'll see what goes into it. That a 22 year old chooses "CRM for Dentists" as a thing to vibe-code over a weekend? Again, good luck with that.
I really dislike this SaaSocalypse fear mongering, because it's just not based in reality. Show me five examples of established SaaS companies being wiped out by vibe coding.
Most people will barely make anything, some will be able to supplement their income, very few will be able to make a living. Even less will become "rich". For every product that blows up, there are thousands that will barely make anything.
But of course, it all depends on what your product does. If you make the millionth TODO / GenAI image editor / food calculator app and hope to make some money, good luck.
Yes, a very hyped mega-corp should be building and replacing all productivity software; why leave room for competitors when a single company can do it all? What can go wrong?
It's a huge trope to think your product didn't work for the market because the marketers beat you. I used to be that kind of developer until I made some products that people actually wanted.
But he's right that the software market is changing. Software will be easier to build and require less people to build it. So more, smaller companies will compete for market share. Margins will be cut and the consumers will get more of what they want for a lower price.
I think this is called a working market. It's what it looks like when capitalism actually works.
This could be the end of enshitification.
One guy loses $2400/mo in revenue
200 pool cleaners can now easily track their clients filter change dates without paying $12/mo for a calendar script (something that 20 years ago would have been a one time $3 purchase).