What it means in practice
Instead of writing code, you tell the AI what you want: “Build me a page where I upload 15 spreadsheets from our sites and get one summary out.” The AI writes the code, you run it, look at the result and say what needs changing. It goes fast and you do not need a developer for it.
This is exactly how most prototypes come about in our workshops. A manager who has never written a line of code has something running within 90 minutes.
When vibe coding is enough
- Personal tools. Something only you use, on data you already have.
- Prototypes. Testing an idea before a budget leans on it.
- One-off tasks. A calculation you do once and never return to.
- Early validation with a customer. Showing something live instead of a slide.
Where vibe coding ends
Once someone other than you starts using the thing, sensitive data reaches it, or the business begins to depend on it, vibe coding stops being enough. That is the point of moving to spec-driven development or agentic engineering: a specification, acceptance criteria, tests and review.
One of our clients, an estate agency, had a custom CRM built. It worked, but it was not just vibe coding: underneath it sit a specification, tests and security rules. The distance between “it runs on my laptop” and “fifteen agents sell on it” is bigger than it looks.
How we teach it
In the Vibe coding in business workshop, managers and senior business people go through four build cycles. Each one starts from a prepared repository that already holds sample data and the rules for how code is written in that company. Fast development with AI can perfectly well respect your standards; you just have to know that.