AI has been a great tool for both technical and non-technical founders. Especially my heart goes out for the non-technical people who can take their idea and develop a prototype or a "good enough" version of their idea (even better, some of them could actually get interested in programming and how software works 😊). But given all of this, I think the ability to build more easily can also bring out new kinds of problems, more specifically in a business setting:
Just because you can build something doesn't mean you should
I think this applies to organizations of all kinds of sizes, from startups to enterprise teams. On the surface it seems like a great idea, you can now "optimize" everything that you can dream of. All of a sudden you find yourself in a situation where you're vibe-coding a solution for every single detail you can think of. That begs the question, at what point are you actually working on the hard and actual limiting parts of the business?
Obviously the frequent and time consuming things should always be automated as well as possible. But there's also a clear distinction between removing bottlenecks and wasting time in micro-optimization land. More often than not you should just either spend that 5 minutes doing the thing or using existing and cheap solutions for solving those problems.
So next time you're starting to vibe code, maybe ask yourself, does building this thing either make or save money for yourself and your business.