Live data from Hacker News

AI is killing B2B SaaS

nmn.gl

441–450 of 752 posts

Re: AI is killing B2B SaaS

#441

Earlier quoted context omitted.

My career occupies a weird middle ground where, for 20 years or so, I've catered to smaller businesses that need bespoke solutions (because the SaaS available doesn't conform well to their business logic), but don't have the scale or desire to build and maintain software in-house. Sometimes these are slapped together in a weekend, if that's all that's needed. But in most cases they still become ongoing improvement an…

This sounds great if you get on well with your clients. You must be an effective networker and at sales. How do you bill, and how do you price your services?

I bill quarter-hourly at $300/hr for actual time writing or evaluating code. Phone conversations are free, and I take time to evaluate and explain what I'm doing before clocking in. The downside to this is that I make myself available 24/7 should any issues arise. I also don't necessarily charge for hunting down network issues or bugs (because I also host some software for clients). It works out to a good income for 80 hours a month or so.

I'm terrible at sales. My clients have only come to me by rererral from other clients. More than half the time, I'll tell prospective clients that there are already SaaS solutions that would be better for them than building something bespoke, and help them find solutions, because I don't want to do work that's already been done.

Re: AI is killing B2B SaaS

#442
How corporate incentives are aligned will also define the trajectory. The person who is going to take the call whether to go for vibe coded tool or external vendor has to have enough incentive to put this neck on the line.

Imagine this, you are VP of finance. You know you can get a nice tax calculator built quickly using vibe coding, but will you put your neck on the line and say, let's replace the existing vendor and use my vibe coded tool. You might fired if you send a wrong tax report to your auditor.

Let's take another example - VP of sales wants performance report and visuazliation of the sales team. He has 200 BDRs. The daily sales standup depends on this report, team gets yelled at or praised basis this. Now, will this VP be willing to put his neck on the line and say - let's use my vibe coded report and discard the existing SaaS. Even if such a report feels trivial, it is vital for functioning the sales team and hence, it needs to be reliable.

I think vibe coding will work at prototype level - the trust gap is very huge right now to even consider it for internal tools.

And, until vibe coded tools are stress tested enough this trust gap will not be fulfilled. Think about this, why some of the biggest companies in the world still run on softwares built in 2000s.

Re: AI is killing B2B SaaS

#443

Earlier quoted context omitted.

Do they actually not understand that? They might just be fine with a system that makes them more useful. How do you calculate the time spent on an internal tool like this, actually? (I’ve never been in management). Realistically your team inevitably will have some downtime, maybe some internal tool maintenance can be fit in there? I mean it obviously isn’t fully “free” but is also shouldn’t be “billed” at their full…

> Realistically your team inevitably will have some downtime What? My team wouldn't have any downtime even if we had 10x the amount of people. If you work at a company where you have times where you don't have work to do, you should polish your resume because it means the company will go under.

Agreed here as well. If you gave me 10 devs for 3 years and zero new incoming requirements the backlog wouldn't even go down by 20%.

Re: AI is killing B2B SaaS

#444
post #199

Earlier quoted context omitted.

This vibe-coding-will-replace-SaaS insanity is the new crypto-will-replace-fiat-money insanity.

It's shocking to me how prevalent this "who needs Salesforce when everyone can just vibe code their own CRM from scratch in a day" narrative has become in the business press. Like, what???

It gets eyeballs.

Re: AI is killing B2B SaaS

#445

Earlier quoted context omitted.

And both are completely different arguments then your original post.

No, those are the two main reasons management don't want to have internal systems belong to them

I see. I misread. My mistake. I agree - the issue is not technical it’s the responsibility for the project.

Re: AI is killing B2B SaaS

#446

It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…

Software without support is useless. In the business world, what's being bought isn't code—it's a solution to a business problem, with a throat to choke if things go wrong.

Re: AI is killing B2B SaaS

#447

Earlier quoted context omitted.

Good execution doesn't get easier with an LLM.

No, and I agree with the conservative sentiments here. However, putting together a SaaS alternative that frees up money during a crunch, and now with the pet features your boss has always wanted, is potent indeed.

You've hit the nail on the head. Immediate gratification.

AI is like sugar. It tastes nice, gives you energy quickly - what's not to like? The gratification is immediate, and if "today is all that matters" it's brilliant.

The problem with sugar (and AI) is medium term. So sure, that junior dev whipped up the whole framework in ClaudeCode, and it's humming nicely. Junior dev gets credit, and after a couple years moves on somewhere else.

Then something changes. Windows. TLS. Code Signing, whatever. We need to update the program to the change. Just a small tweak. Junior Dev has gone (or is otherwise occupied) so we'll get new-Junior-dev to do it. Is he expected to do the change at the code level? Or at the prompt level? Will ClaudeCode in 2029 be able to maintain ClaudeCode Code from 2026? Or will it want to rewrite everything? Will new-junior-dev have the skillset to prompt as well as first-junior-dev? Was the code good enough that a dev could just "take it over"? Or was it "it works, let's use it" standard?

AI makes everyone look good in the short term. But it worries me for what happens in 5 years, 10 years, and so on. Sugar is great, but you can't live (long term) on sugar. Sometimes you need a proper meal plan.

Re: AI is killing B2B SaaS

#448

It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…

OTOH, I was hired by an enterprise that was many months into a giant backend rewrite. After wrapping my head around the many plans, I realized they were rewriting Django, badly. One weekend I prototyped the whole thing… in Django. It worked. It met the specs. It was a CRUD app with a REST API. I came in to work Monday morning, showed it off, and inadvertently triggered a firestorm. Later my boss told me not to do tha…

I can relate to this so much. When I was a newly joined Google consultant at a partner firm, we went to their office - some 13 different types of cuisines, different types of game rooms, lounges and what not. A luxury star hotel experience. We were waiting for our meeting on behalf of this one particularly large media client who was bleeding money on Wordpress.

3 engineers arrived - fashionably late. We explained them the situation and all we wanted from them was some GCP offering that would cure our woes and one that would cut our bills. The senior consultant - and presumably the only tech guy (rest seemed to be salesy) wasted our time like a used car salesman - he didn't even understand Google's own product portfolio and recommended us to use something like Spanner - which was totally not the solution to the problem, not to mention, expensive.

My boss and I left the meeting pissed off and he told me - "Neya, you probably know more about the product portfolio than these guys. Let's leave". That weekend, I went with my tried and trusted favorite Db - PostgreSQL - CloudSQL with a custom Elixir middleware based an old CMS I wrote a decade ago. After some trial and error, the solution worked flawlessly (and still does till date on auto-pilot). My client still has the lowest cost in the region - 1/3rd the cost of their competitors...7 years later. Back then, there was no vibe-coding, no AI, no auto-completion. Just pure thinking and experimentation.

All this just to say I agree that the new guy sometimes can make the best solutions to a problem and not always screw up. I always listen to new hires these days (now I'm a fractional / CTO) because you never know who could pull off that 1/3rd cost cutting framework move.

Re: AI is killing B2B SaaS

#449
post #394

Earlier quoted context omitted.

We are certainly closer now to being able to prototype and go to market faster with a product. In one weekend is a little much but I think its hard to deny that building will continue to expedite. What most developers don't think about is that the marketing, sales, customer service are all non-trivial parts of the business/product and all require legwork that is more than just sitting at an IDE. The nail in the coffi…

> We are certainly closer now to being able to prototype and go to market faster with a product Absolutely. But this begs the question that businesses want to also sign up to maintain whatever product they've built, on top of their core business. "Service" is the word that people seem to be forgetting in SaaS. If you roll you own, all you have is software.

The "service" part can still come from internal sources. Plenty of companies have internal support for internal tooling. With a good foundation of infrastructure and a lean team that knows how to build, not just vibe code, there is most definitely some ROI there.

But yes, this brings us back to the point that simply building the tool is only a small part of the process...and it has often been one of the most expensive parts of the process.

Re: AI is killing B2B SaaS

#450
Honestly, I'm surprised by how people are pushing back against this idea. I feel like vibe coding is just in its earliest moments of actual viability, and my mind is totally blown by it, and it strikes me that it's exactly what I've always wished software could be. Plastic, flexible, personalized, effective, responsive, organic.

As an anecdote, I've been vibe coding an accounting system that perfectly matches with my own expectations of accounting software, i.e., it's intimately connected to CSVs, imports and exports from CSVs, but acts as a kind of enrichment and reporting and file association layer. If there was anything like this, any kind of SaaS that I could have and download as software and run on my own computer offline and be able to inspect and trust and version control so they wouldn't add or remove some kind of feature that I wanted down the line, then I would have gone with that.

But now I have essentially my absolute ideal solution, written with a Python backend and Vue and JavaScript frontend, and it's radically improved my ability to maintain accounting for our business account.

And I think there's something really important to point out here, which is that the feeling of lock-in is very seriously reduced when you are Vibe coding your own software, because if you don't like the way that it works or you realize that there's something missing, you can add it pretty painlessly. Like, that's always been a huge challenge with choosing vendors for a SaaS platform, is you think, oh no, well, what if their conceptual model for what I'm trying to do doesn't quite map onto our own internal systems or understanding of what's being done? Well, when you have your own Vibe-coded SaaS, you can just add that information. So there's something incredibly organic about it. I used to work at a startup in Redmond where we built this large internal system to manage a scientific process with lots of machinery and data, and it was incredibly empowering and actually became one of the core values of the business that was able to be licensed to other businesses in the same industry. And it seems like we're just improving that capacity from here.

Now obviously, if Vibe Coding magically were to go away or became much more expensive, then I'd have this legacy piece of software, which I couldn't improve, and that would be a dead end. But my expectation is that the functionality that we have today will only improve. And in several years, the scope of changes that I'll be able to make, the level of professionalism, modularization, maintainability, code quality, will only improve. And so this has me thinking in general that software is kind of undergoing a step change where we're moving into the so-called age of intent beyond the age of the interface. And that's tremendously exciting to me, and I just couldn't be more stoked about it.

Post reply on HN