Simple CRUD app sure, but we're nowhere near being able to vibe code even a relatively low-complexity enterprise SaaS product.
If it's got customer data in it and/or you're making important business decisions based on it, you really need your system to be accurate and secure. My experience is the people who procure enterprise software know this and tend to care a lot about it. They often have legal and contractual obligations around that.
In the 1990s there were people who thought OOP with point and click tools like FoxPro and Delphi would make it so easy to create software that everything could be built in-house without expert programmers. The invention of SQL was supposed to eliminate roles like Report Writer and Data Analyst because now business people could just write their own queries "in English" and get back answers.
And yet, precisely that happened in the end, just not with the tools envisioned. Excel, VBA and, where you had one knowledgeable employee, MS Access makes for incredibly powerful and incredibly hard to maintain "shadow IT" - and made even more difficult when someone sneaked in a password, because that takes a bit of an effort to remove [1], knowledge that is easy for us today to find, but not when I was young.
Also, back in the IE6 era, there was a lot of point-and-click created web interfaces... just that it wasn't HTML5 or even HTML. It was an <object> tag loading some ActiveX written by some intern in VB6, or Java, or Flash. I sort of miss that era but also, it was a damn security nightmare. Flash with its constant stream of security vulnerabilities was ripe for exploits, but at least it didn't run native code with full user privileges by design. I'm not kidding, theoretically you could go and import/use functions from any system DLL up to and including Kernel32. OLE/OCX, ActiveX... a design way ahead of its time.
[1] https://stackoverflow.com/questions/272503/removing-the-pass...
The new tools didn't shrink demand for COTS enterprise software - it grew massively since the 90s!