
Vibe coding: can an SME have its app coded by AI?

A prototype in an evening or a real application? What vibe coding allows an SME to do, its limits in security and maintenance, and when to switch to custom development.
Yes, for a prototype to show people or a small tool that only you use. No, as soon as the application handles customer data, connects to your other software or still needs to be running in two years. Vibe coding very quickly produces something that works on screen. It guarantees neither the security of the code, nor its maintenance, nor that anyone will understand it on the day it needs fixing.
The subject came up again this week on X, where developers and founders are debating these applications described in everyday language and written by AI. The term was coined by Andrej Karpathy, co-founder of OpenAI, in a post published on 2 February 2025, and the Collins dictionary made it its word of the year for 2025. For an SME manager, the question is simple: can it be used to avoid paying for development?
What exactly is vibe coding?
You describe what you want to an AI tool, it writes the code, and you judge by the result on screen without reading what was produced. Karpathy described it like this: he accepts all the changes without reading them, pastes error messages back in as they are until the problem goes away, and admits that the code quickly grows beyond what he understands. He himself kept the method for throwaway weekend projects.
It needs to be distinguished from AI-assisted development. In that second case, a developer uses the same tools to go faster, but reviews every change, tests it and can explain why the code does what it does. The tools are identical. What changes is that someone remains in control.
What can you really build on your own with AI?
More than you might think, as long as the stakes stay small. A few uses where vibe coding is genuinely useful to an SME:
- a clickable mock-up to test an idea with five customers before committing a budget;
- a small personal tool that turns an export from your till software into a readable table;
- a demo page to convince a partner or associate that the idea holds up.
These projects have things in common. Few people use them, they do not store sensitive data, and if they break down, nobody is blocked in their work. In this context, speed more than makes up for the fragility of the code.

Photo: Kelly Sikkema on Unsplash
Where does vibe coding reach its limits in business?
The trouble starts when the prototype becomes the company's tool. A form that records customers, a login area for your sales staff, a link with the accounts: from that point on, what you cannot see on screen matters as much as what is displayed.
Is generated code safe?
Not by default. The security vendor Veracode submitted 80 programming tasks to more than 100 AI models for its 2025 report on the security of generated code. In 45% of cases, the code produced contained a known flaw, of the kind listed in the OWASP ranking of the most common web risks. The most recent models did no better than the older ones on this point, even though their code was more often syntactically correct.
In a vibe-coded application, nobody reviews, so nobody spots these flaws. An access key left in code visible to the browser, a database open without a password, a form that accepts anything: these are commonplace mistakes, and they are enough. The PHP2Shell vulnerability recently showed what a website that nobody monitors any more can cost.
Who will fix the application in six months?
An application lives. Your payment provider changes its interface, a new version of iOS breaks a screen, a colleague asks for an export that did not exist. With code nobody has read, every fix starts from scratch, and the AI may break elsewhere what it repairs here. Karpathy said so himself: when the tool cannot fix a bug, it works around it or asks for random changes until it goes away. Acceptable for a weekend project, not for the software that runs your schedule.
Where is the data stored?
Rapid creation tools often host the application and its database themselves, on servers whose country you do not always choose. For personal data about customers or employees, this is a question to settle before going live, not after. Our article on data hosting in Switzerland or France details the criteria.

Photo: Jiří Navrátil on Unsplash
How can you tell whether your project can make do with an AI prototype?
Ask yourself four questions before putting a vibe-coded tool in your team's hands:
- Will more than five people use it every day?
- Does it contain personal data, prices or payment information?
- Does it need to exchange data with your ERP, your payroll software or your CRM?
- Will it still need to work in two years?
If you answer yes to even one of these questions, you need someone who understands the code, whether in your team or at a provider. If the answer is no across the board, enjoy the speed and keep the tool in its place as a draft.
Is the vibe-coded prototype lost if you move to real development?
No, and that is often the best surprise. A working prototype explains your need better than a twenty-page specification: you can see the screens, the sequence, the things that seem obvious to you and that you would never have thought to write down. It saves time at the scoping stage.
The code itself is more rarely kept as it is. Depending on what we find in it, we reuse parts or start again from a clean base, and it is the audit that settles the question. What follows then looks like a standard MVP, with the steps we describe in our article on the timeline and steps of a mobile app MVP.
How does METEORA use AI without vibe coding?
We use AI every day to develop faster. On e-palett, EPALIA's business software, features were written with the help of Claude Opus 5, and the project has 100% test coverage: the code suggested by the AI goes through the same checks as the rest, and a developer understands it before it goes into production.
This is what makes it possible to meet short deadlines without sacrificing what comes next. For custom software, an MVP starts from €4,900 (CHF 4,900 in Switzerland) with a useful first version in 4 to 8 weeks. The Git repository and the documentation are handed over to you on delivery, which leaves you free to change provider. The principle is the same for mobile app development for iOS and Android.
If you have already put together a prototype with an AI tool, keep the link handy for our first conversation. In fifteen minutes, we can tell you what is worth keeping and what will need rebuilding.
Frequently asked questions
What is vibe coding?
It means creating an application by describing it to an AI in everyday language, then accepting the code produced without reading it. The term was coined by Andrej Karpathy in February 2025 and the Collins dictionary made it its word of the year for 2025.
Is vibe coding risky for a business?
Yes, as soon as the application handles real data. In Veracode's 2025 report, the code generated by more than 100 AI models contained a known security flaw in 45% of cases. Without review, nobody spots these flaws before going live.
Can a prototype made with AI be turned into a real application?
Yes. The prototype serves as a basis for scoping, because it shows the intended screens and user journey. The code is partly kept or rewritten depending on what the audit reveals, then the application follows the steps of a standard MVP.
How much does it cost to have an agency take over an AI prototype?
At METEORA, an MVP starts from €4,900 (CHF 4,900 in Switzerland) for a useful first version in 4 to 8 weeks. On-site scoping is free of charge and the detailed estimate is delivered within 48 hours.
Should you ban AI tools for your teams?
No, it is better to set a framework for them. Prototypes and small personal tools remain useful, provided you do not put customer data in them and have anything meant for the whole team reviewed by a competent person.
How much would your project cost?
Project type, features, timeline: a costed estimate in two minutes, with no commitment.
Does your AI prototype deserve a real version?
Show us what you already have, even if it is rough. Scoping free of charge, estimate within 48 hours, code and documentation delivered. Write to us or book 15 minutes with Jérémy.