And don't forget the safety in getting to say "our systems are down because of [X TRUSTED SOFTWARE FROM LARGE KNOWN BRAND] and we're just waiting for them to fix it" instead of "our shitty internal tooling is broken and no one knows how to fix it"

This feels like it goes along the lines of "people's vibe code is cluttering up our PR's, people still need to review" -- it misses the boat: models are already capable of getting you up to speed on how the code is organized and works, in as much as you want to or need to be up to speed. They are already helping me cut down review time because I don't need to aimlessly hop around, I have a good starting point that I can scrutinize and dialogue about. Same thing here: employee leaves company -- about 3 years ago you would be right, now the company is left with an unmaintainable mess of legacy code and tech debt. TODAY this just doesn't matter. No one really needs to read that code too closely, it's already easy for agents to digest and explain and modify.

Doing this today, in production, with full trust, is clearly not wise, but the writing is clearly on the wall that this is going to be the norm more and more over the coming years. The times they are a-changin.

I think you can avoid the pain by thoughtfully designing it to avoid lock-in. You want it so that if needed, a dev can vibe-code a migration tool to the equivalent SaaS offering. AI lowers the barrier for creating these in-house replacements, but it also lowers the barrier for scrapping them too.

Even more accurate (I work in this space):

3. Bugs creep in, feature request pile up.

4. Employee continue in the company and request help (or the managers see the need):

4.1 They hire more, but if all are vibe-coders too

4.1.1 The product gets more complicated (no more complex, that good developers can manage!)

4.1.2 Bugs creep in, feature request pile up.

4.1.3 People start to get desperate, not worries! now:

4.1.3.1 Somebody vibe-code a new alternative that solves the immediate problem

4.1.3.2 Bugs creep in, feature request pile up.

4.1.3.3 Needs to sync with the other tools

4.1.3.3.1 Somebody vibe-code the sync that solves the immediate problem

(the saga continue)

In parallel:

4.2 Eventually is obvious that need external help

THEN:

4.2.1 They ask for consultors for build tool, of course, from a company that has embraced the IA!

4.2.2 They build new shinny tool!

4.2.3 Bugs creep in, feature request pile up.

4.2.4 Needs to sync with the other tools ....

AND:

4.3.1 They ask for consultors, to teach them what to do, of course, from a company that has embraced the IA!

4.3.2 New shinny theory of how do the thing with IA is now being implemented!

4.3.3 It require a rewrite of not only past solutions but, a change of how the company behave!

4.3.3.1 Needs to sync with the other tools .......

4.3.4 And it spark beautiful office/political debates around some philosophical whatever that also trigger changes in the structure, hiring or whatever, alienating the people that has been working there, that after months, has started getting the handle of it!

4.3.5 Employees either leaves the company or moves on to another project.

4.3.6 New employees arrive, with a wild new IA tool and different vibes that vibe-coding!

... the saga continues

5. Is now clear that it need to buy a product form a well stablished software provider

5.1 And all of them are now in the IA craze!

.............

That's a huge part of it. But also you presumably hired a full-time programmer for a reason, and in almost every case that reason was not to have somebody to write and maintain your CRM system. So any system they build and maintain is not just another thing for you to worry about, it's a huge chunk of time that the developer isn't doing what you hired them for.

Depends on the size of the organization.