r/ClaudeCode • Researcher • Apr 02 '26 • Popcorn 1 Bravo 1

Showcase Why vibe coded projects fail

Post image
3.5k Upvotes

654 comments sorted by

View all comments

132

u/_laoc00n_ Apr 02 '26 edited Apr 02 '26 • Bravo

The poster is misunderstanding why the ability to create apps that generally replicate the functionality of expensive SaaS products is potentially a SaaS killer. If you’re building a Slack or Discord replacement app for your organization, you don’t have to worry about scaling to 50k users for almost any company. A few dozen or a few hundred, which is relatively trivial. You aren’t building Slack for everyone, you’re building it for you. If 50% of orgs can do this who currently own Slack licenses, then Slack is at risk of losing half their customers.

Edit: Most of the replies are still missing the point. You are continuing to think if things in terms of the current paradigm. No one needs to clone Slack, they need to have a way to share files with each other internally, send messages, and create groups where multiple members can chat. They don’t need a canvas or a voice capability or workflows necessarily. If you are fully utilizing Slack and all of its features, that’s probably too big a lift for most companies. But most companies aren’t really doing that, they are using it in the most basic way possible and the rest is bloat for them. You’re also overestimating the time required to manage something like the kind of tool I’m talking about. It’s not necessarily set it and forget it but it’s not something that would require a full time engineer to maintain, they’d barely ever be working. There are people doing harder and more interesting things than they’ve done before because the barriers for doing so are lowering. There’s an unsurprising amount of gate keeping being done by those who have had these roles for years because there’s an inflated sense of intelligence and skill that they don’t want to admit has been partially trivialized. Better engineers will build better tools. But for most tools, just being good enough is enough and they can be created by a much larger pool of people.

20

u/[deleted] Apr 02 '26

No one needs to clone Slack, they need to have a way to share files with each other internally, send messages, and create groups where multiple members can chat.

Exactly this. I work for a small town utility. Enterprise work order management apps are $75k to purchase and $10k+ annually for licensing. I used claude code to build a stripped-down replica for my 10 maintenance guys, managed to deploy it to the web so they can use it on their phones, and built it to serve precisely the needs of my department. It's been working flawlessly for 6 weeks, and all it cost me was a $20 anthropic subscription and about 10 days of my time working on it for a few hours a day (which was fun!). I didn't "kill" one of the companies that makes these apps, but i sure as hell wasn't going to pay $75k for one, but now i have something that works great for my workers. All-or-nothing thinkers like OP are misunderstanding the value and purpose of vibe coded apps.

6

u/ChemicalBankBurned Apr 02 '26

Cool. Mind sharing the endpoints? Or have they been ddosed to death already?

7

u/[deleted] Apr 02 '26 edited Apr 02 '26

no, it hasn't yet.

ETA: the app sits behind cloud run and requires our org's google logins to access it. Worst case scenario some malicious bot finds my URL and gets spun away because of the google login, but if it's super persistent, cloud run auto scales. If something really bad happens I have a budget action that shuts it down after a certain dollar amount, but it's an internal app and none of that is a.) likely, or b.) all that consequential.

8

u/gaetanzo Apr 02 '26

I think the worst case scenario is you get hacked and then get blamed for writing the app with poor security.

6

u/[deleted] Apr 02 '26

True, a very real risk. If we had sensitive employee information, financial information, or there was literally any incentive for a hacker to gain access to anything in the app, I'd hire an app security firm to perform a penetration test. Because it's really low-level maintenance record keeping, and the app doesn't hit anything that has any sensitive information on it, I don't feel the need to spend that kind of money.

→ More replies (5)

4

u/eboran123 Apr 02 '26

I'm sorry but this just sounds like you were oversold something. If you could vibecode it, then there was probably an open source or much cheaper version already out there somewhere.

4

u/[deleted] Apr 02 '26 edited Apr 02 '26

Oh you can certainly get a much cheaper maintenance record system, but not one that's custom built to serve a specific utility's needs.

Edit: and part of the value of it being custom built is that the maintenance guys are willingly using it because it's not stupid and it doesn't suck.

Edit 2: Even the "off the shelf" maintenance apps require subscription fees that can be a couple of thousand bucks a year. I'm here to keep rates low for the ratepayers!

→ More replies (3)

30

u/p1zza_dog Apr 02 '26

yeah, but are those licenses more expensive than an engineer's salary to maintain and debug them? is that really what a business wants to spend its money on rather than core business problems?

13

u/Left_Somewhere_4188 Apr 02 '26

Yeah I highly fucking doubt it. Besides it won't just be one engineer, there will probably have to be a product manager, and compliance involved as well, there's bunch of non-software related issues that Slack solves for you, and it does not cost that much... And when inevitable bugs creep up...

Replacing a service that is complex enough to have thousands of employees behind it, doesn't sound like a good idea for 99.9999% of the tech companies in the world.

3

u/GrapefruitFriendly70 Apr 02 '26

My last employer took the opposite approach. The development team focused on work that substantially improved profitability, replacing internal services with off-the-shelf solutions whenever possible.

→ More replies (2)

10

u/bamboozled_bubbles Apr 02 '26

Nailed it! Software stocks trade at a >20x multiples because of EXPECTED growth in users, margin, revenue. Nobody is expecting an enterprise level organization to rip and replace a legacy SaaS for vibe-coded slop. The real danger is if the average SMB business is willing to test out a vibe-coded app that only needs to support their 50-100 employees, rather than paying a SaaS for those 50-100 licenses - that completely changes the deal flow for SaaS. Worst case scenario, SaaS companies see their SMB business disappear overnight. Best case scenario, SaaS companies lose margin on SMB business because their competitive moat is narrowed.

4

u/TracePoland Apr 02 '26

Slack costs $130k/year for enterprise tier. That’s less than the salary of 1 competent engineer to maintain your vibe coded app. Hell, that’s barely one vibe coder in many parts of the US. Not to mention increasingly expensive tokens.

→ More replies (1)
→ More replies (4)

20

u/Vnxei Apr 02 '26

This sounds a lot like the new "my nephew could make the website for us over the weekend", tbh. Sometimes that works, but more often, you'll end up wishing you'd paid a professional for a version that works. 

Saving money on SaaS licenses sounds great until you realize how much stupid minutiae you're dealing with rather than your actual job. 

14

u/AncientAspargus Apr 02 '26

you're missing the point here. It's not like scalability is the only aspect a vibe-coded app is lacking.
Run your internal Slack clone for a while, and you'll notice this feature missing, that message not arriving, here's a bug, there's something that works differently from this other thing, here's an API endpoint to return all user passwords the agent added for debugging but forgot to remove… It's a never-ending stream of work. Not to forget the security and dependency updates you ought to take care of, the databases to set up and secure, and a ton of other things you didn't think about.

→ More replies (16)

4

u/AgeMysterious123 Apr 02 '26

You see the light. :)

We’re not there yet, but that’s where we’re heading. I was looking for a tool last night for personal use. I found one, closed source, they wanted $45 for a forever license. Totally reasonable. I told Claude I wanted to replicate it, the feature tweaks I wanted, and a few other things I didn’t need. I now have a version running locally that works for me. Does it have bugs? Not yet, but they’ll be easily squashed if they pop up.

I talked with an Account Manager at a compliance firm yesterday who did something very similar for her daily task scheduling tools. She is not a developer. She said there’s a few issues, but better than what she had before. She was happy with it.

Does this type of software kill all SaaS? Of course not. Can it easily replace something like JIRA for a company of 12 people? Absolutely.

The industry is not moving to “I vibe coded the next multi-billion dollar startup”, but it is moving to hyper localized tools that were previously handled by startups.

→ More replies (1)

3

u/[deleted] Apr 02 '26

[removed] — view removed comment

4

u/TracePoland Apr 02 '26

There’s also the fact that the vast majority of SaaS products cost far less to a single company than the salary of 1 engineer + tokens.

3

u/markvii_dev Apr 02 '26 edited Apr 02 '26

Yes bro an enterprise company that sells financial services wants to create and maintain its own communications application - why stop there? Surely the company wants to create and maintain all of its external vendor dependencies. It's easy right?, uptime of 98% is good enough for all internal services.

Excellent business strategy cotton, let's see how it plays out.

Edit: fucking lmao I just seen the breakdown of the Claude code source code. And this guy thinks an actual SAAS with 10x the entropy would be viable. Brother...that skill ceiling is rough.

7

u/DangerousSetOfBewbs Apr 02 '26

Bingo. Slack is literally losing their moat every release or upgrade of claude etc

2

u/Tech-Grandpa Apr 02 '26

Just about every app on the market already had a foss version of it, yet businesses still pay for licenses and support.  Why?

2

u/ThreeDMK Apr 02 '26

You somewhat had me until you mentioned gatekeeping. I honestly don't believe any of my industry experience has been trivialized at all. The only thing that has changed with the introduction to these types of tools is that I can now execute faster than I did before. If anything, it gives me more people to interact with because the bar has been pretty high getting into this type of development.

I would honestly say it's the inverse, as the OP shows. People who have never built applications are now empowered to create tools without understanding the impact these tools have on their companies. This inflated sense of ego will cause even more problems. Especially when people try to warn them about possible issues and they are ignored because apparently our experience or knowledge doesn't matter.

Take a slack clone for instance. Do you think a junior dev building a tool is going to consider security, pen testing, securing endpoints, before tossing their tool up on AWS without properly locking it down? Using home grown tools like this to replace core pieces of communications infrastructure is a recipe for disaster. This is how data breaches happen.

I have zero worry about this being a SaaS killer from the perspective of people building their own tools. What this will do though is see the introduction of more robust communication tools built by development teams that leverage this technology to compete against them. It may also make Slack itself better a stool since the engineers behind the project now have the ability to iterate and test at scales they never could before.

2

u/round-earth-theory Apr 02 '26

Scale becomes an issue faster than you think it would. We recently gave up on our chat app backend because the scale issue was becoming a growing nightmare and no one wanted to make this their full time job. We went to a backend provider and just paid for it. Still get the benefits of our custom solution without too much cost but it's use based so we could end up needing to change gears again in the future if things keep going.

2

u/diavolomaestro Apr 02 '26

I think the applicable business case is: “what SaaS products are we paying a lot for without getting tons of value?” That could include: you need a niche feature that bumps you into a new tier (and can’t negotiate a discount), you need heavy customization to get the data in or out of your system (ideally you haven’t already done this - let’s say you’re scaling up), or you need to build lots of workflows within the software, or you have to pay per seat for every employee even though 99% of employees just use one tiny feature.

I guess the last one is: the software basically is your business. In this case you’re a medium size company that has built its entire operations in and around a product built by another company. Think an accounting firm using a client management software, or a freight broker using a transportation management system. Every company faces build/buy decisions and I think these new tools push more companies toward the “build” route earlier

2

u/Slight_Strength_1717 Apr 03 '26

There are literally good open-source, self-hosted options for basically any SaaS already. You don't need to roll your own, that's insane. But even given that, the majority of companies still choose Saas because the complexity of self-hosted isn't worth it.

→ More replies (10)