ZH version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
75% Positive
Analyzed from 2248 words in the discussion.
Trending Topics
#software#build#saas#more#don#own#tools#lot#read#few
Discussion (53 Comments)Read Original on HackerNews
I try to learn writing and copywriting directly in english to avoid the awkward translation effect, but I focus more on the rythm, structure and content than the prasing itself
It's easy to build something for yourself that solves your own use case. You know how you work and what's important to you. Most of the effort in software goes into understand people other than you and building guardrails for them.
> Whatever niche tool you’re sketching this week, a thousand people can prompt a working version by Sunday night
A lot of people on HN are naturally builders. For them it's fun to play around with AI and see what can be built. Not everyone is like that.
For individuals, how many people actually want to spend their weekends building a niche tool for themselves vs just paying a few dollars a month to access something that does the job even though it may not be perfect?
For businesses, the buy vs. build tradeoff does now have some new compelling evidence in favour of "buy" but there's still maintenance needed for the service internally, there will be people with feature requests for it. Before you know it, the company is diverting resources away from their core business for a support tool that doesn't really drive impact.
I think we'll see more options in the marketplace as individuals will be able to get started more easily but SaaS is far from dead.
At my job (we're somewhere in the transition between startup -> enterprise), we still use a lot of SaaS and are continuing to do so, but even there we're starting to move off certain platforms (Pendo, is a recent casualty) as we've realized in many cases we can just build it ourselves, pay drastically less, and actually get to control how it all works.
My suspicion, though I could be wrong: SaaS will move more and more towards focusing solely on the enterprise. Personal users and startups will have a harder time justifying both the cost and lack of flexibility of pure software SaaS. Enterprise will continue to be ok with paying the costs in exchange for compliance and vendor stuff and integration and whatever else they care about.
100%, which is why I think hyper-tailored, small software is an exciting option. When you shift your goal to serve 1000 customers, the hardest part is not having a tech stack that supports them, but making sure the software is good enough for all their different needs. Or you try to meet them all and you get into feature creep.
> For businesses, the buy vs. build tradeoff does now have some new compelling evidence in favour of "buy" but there's still maintenance needed for the service internally
What if you neither buy or build the software but buy the service outcome?
A data analyst that creates custom workflows with auto-generated dashboards. A dev-ops that provides access with exactly the information you need, depending on the hand-off level you want for the process.
My point is that a lot of these micro tools that started to appear the last few years will vanish, either bundled with bigger SAAS, internalized, or shifted to a service offering. This trend started with productized services, this is the next step.
> SaaS is far from dead.
Micro SAAS*. I agree with all your points, but I do believe the small software landscape will change drastically in the coming years
Fully agreed. It's also just a time saver. People are lazy, and I don't mean that in a bad way, just that people don't really want to sit there and explain to an agent exactly what they want software to function like. In fact, most people don't even actually know what they want software to function like.
It doesn't just stop at humans either. When I recently started creating my smart budgeting app, Claude pointed me to use Clerk for auth. So not even the AI wants to build everything from scratch.
I have my own "bandsintown" for example because I want to avoid the advertisement shitshow. I have a number of very specific tools for building software. I doubt I ever package up any of this for use by others much less try to monetize it.
That is the vibe I got from this article. This is a good concept to have in your (meta) toolbelt.
My reasoning is people aren’t happy with many of the titans we have for certain apps, uber is my favorite example. Everyone hates the price it charges thinks it’s unfair, but to go back to a time before uber is unfathomable.
That to me is a ripe market to be overtaken. What it really needs is a taxi driver or operator so fed up with the current system they spend their energy organizing and making their own uber with less greed.
For sure not every tool will become huge, but most of the tools we use nowadays started with someone having a problem, being frustrated with the status quo, and having the will and means to execute.
The means necessary to execute get lower and lower everyday.
OP is ascribing magical powers to AI which it does not have. sure, it can replace a shitty poorly coded todo app. but nobody wanted that anyway.
Your "paper" choice is #bfbfc4 - even going to #ddd makes the APCA go from ~63 to 80 and would probably address the complaints handily. WCAG has a lot of gaps.
Anyway, did a quick fix, should be enough for now
Subjectively, even without vision problems, I strongly dislike your choice also.
I mean the website does look good, it's just hard to read.
The same set of things like skills, and custom tools etc can actually be used to get faster to the a product that kind of fits 1000 customers. But the change is that one can build even more custom things for some customers with those skills and tools.
Last year I built a custom integration for a customer in 2 weeks. Now I can probably do it in 2 days. What does that mean for the future, I have no idea, but surely getting custom solutions like this would be more of a moat not less.
I think "the context" the author defines also includes harder to unlock peripheral components that makes software products in 2026 defensible.
For example, security is getting harder not easier. Enterprise trust rides on needing to have up-to-date knowledge on data regulation as well.
Relationships, brand maturity, discovery; all of that becomes rarified as we continue to reduce the actual product launch curve -- but also the "harder to do" hygiene stuff that takes you from a "I vibe coded this in two days, good luck" to a "your successful company can count on us" type of hardening has become progressively more of a baseline requirement.
Not to forget DVD shipping eras (Sony should not discontinue physical game sales, someone needs to get us silicon/holographic/terabyte recording media already), the focus is on the bundling/unbundling of software making. Slack + Salesforce vs 'we vibed our own chat and CRM just for us'...aka a Neo-SAP ERP program.
It's a cambrian explosion of software where lots are going to learn in realtime that the code was never the value of a software engineer / software, the value is in the shared understanding of an information system or workflow or business value stream, that parts of which happen to run through digital information systems.
By the time AI is done with us, its market effects mean in order to stay employable/added value beyond just widget-watchers, we will all be business strategy experts, or we will be algorithm-fed-doped-up mindless beasts, Morlocks vs Eloi, not because of AI itself, but because of the current rapaciousness of business leaders and an assumed trajectory where society doesn't adapt to social movements and actions now made possible by the existence of LLMs.
Sidneote: the LLMs themselves are not IMO going to achieve AGI any time soon. There might be a compilation of disparate systems and LLMs form part of 'tissues' of an eventual AGI, but not currently.
We will either be experts in asbestos chemistry, safety mechanisms, and remediation... or we'll be helping people tweak it for sale as kitchen sponges and pinatas.
Will they invest more into in-house security? (Doubting the last one).
For small apps used to deliver a service in my examples, I believe the risk surface is way narrower, which might make it more acceptable. For better of for worse
The only thing AI is crushing is newcomers.
Standalone software has expertise and distribution, the only 2 things that matter and that your new software does not have.
Also the needs of a business have nothing to do with software you vibe code for yourself. Its compliance, backups, reliability. Not a few features claude did for you.
Another way to say the same thing is that many (not all, of course) SAAS were already service with a software, especially when starting out.
But we do see a sharp rise in the release of apps, without the same tendency in use. [1]
I do think there will be a place for SAAS, even micro-SAAS, but the competition will be fierce and I don't have a lot of hope for indiehacker without any "unfair advantages" like unique knowledge, data, network, etc
[1] https://www.linkedin.com/posts/ericseufert_this-ft-chart-vis...
https://github.com/maximelebreton/quick-javascript-switcher
By default, I don't run into these problems and save a lot of compute!