First, what is a vibe coded app?
“Vibe coding” is the new way of building software where you describe what you want to an AI. It produces the code, and you run it without reading much of it. It is fast, it is fun, and for testing an idea it is fantastic. A prototype that used to take us weeks can now exist in a single afternoon.
So, to be very clear: we are not against it. We use these tools ourselves every day. The question is never whether AI helped build something. The question is what happens the moment it stops being a demo and starts being something people depend on.
The demo took a weekend. The product takes longer. It looked quick. It is not.
A prototype is built to answer one question: does this idea work? A product is built to survive everything that comes next. Those are two very different jobs.
When we open a vibe coded project, we usually find the same things. There are no automated tests, so we cannot change one part without quietly breaking another. Passwords and keys are often written directly in the code, sometimes already shared in public. There is no version of history, so nobody knows what changed or why. And the structure is frequently one very large file that the AI kept adding to, with several functions that do almost the same thing.
None of this is criticism of the person who built it. It is simply the difference between generating code and maintaining it. The first is a sprint. The second is a long-term responsibility, and that is where we come in.
What we mean by secure, stable and scalable
These are not just nice words for a website. Secure means your customers’ data is protected, and your keys are not exposed. Stable means the app keeps working when something unexpected happens, instead of failing silently. Scalable means it still works when you have a thousand users instead of five, and when you want to add the next feature without rebuilding everything.
A weekend prototype rarely has any of this, and it does not need to, because that was never its job. The work we do is exactly the part the demo skipped. It is less visible, but it is the reason a product can be trusted.
So, what do we actually recommend?
Please keep building prototypes. Use AI to test ideas, to learn, and to show us what you mean far better than any document could. When you bring us one of these, you're not bringing us a nearly finished product. You're bringing us a head start.
Just let us treat the moment it touches customers, payments or your reputation as a real project, not a quick repair. The honest question is not “can you fix this quickly?” It is “what would it take to build this properly?” That is a conversation we are always happy to have.
So yes, we work in digital. No, we will not quickly fix your vibe coded app. But we would love to help you build the next version on a foundation that lasts.
Let's talk about it
We are having this conversation with more and more organisations. Teams are experimenting with AI, building prototypes faster than ever, and wondering what it takes to turn those ideas into products people can actually rely on.
If that sounds familiar, we'd love to hear your perspective. Have you built something with AI that started as a prototype? Are you figuring out what comes next? Let's talk about it.
Book a call with us