If you can describe it, you can build it.

Vibe coding is a new way of making software. You don't write code. You don't drag boxes. You describe what you want, in normal English, to an AI like Claude. It builds it. You look at it, react, ask for changes. It updates. That's the loop.

The name is silly on purpose. It captures the feel — you're not engineering, you're describing a vibe and steering. The output is real, working software you can use today.

For anyone who has spent twenty years writing requirements for someone else to build, this is a category change. The thing in your head and the thing on the screen are now seconds apart, not sprints apart.

Why not engineers, agency, or Power Apps?

You always had options. They all came with a tax.

The honest read: engineers and agencies are worth every penny when something has to scale, be secure, and live for years — and overkill when you just want to test if an idea is any good. Power Apps and no-code platforms are useful, but you're still learning a tool and you hit a wall the moment you want something the platform didn't predict. Vibe coding closes the gap between thinking it and seeing it.

Vibe coding closes the gap between thinking it and seeing it. The cost of trying drops to almost zero — which changes what you bother trying.

Vibe coding

Minutes to hours. The cost of a subscription. You describe; it builds. Change in seconds. No syntax to learn. Best for prototypes, internal tools, "what if" tests — the things that used to die in the backlog because nobody could justify a project for them.

The loop — and what to build first

The mechanics are simple. You describe. It builds. You react. You ship or scrap. If you've ever sent a colleague a message saying "can the report show last month too?" — you already have the skill. You're describing intent. The AI is the colleague who builds it for you, instantly, and never gets tired of revisions.

Real things people have built in under an hour

• A weekly KPI dashboard from a CSV export, with date filters and traffic-light flags.
• A bid go / no-go scorer that reads a tender PDF and rates it against your criteria.
• A meeting-minutes tidier that turns a Teams transcript into actions, owners, and dates.
• A holiday-cover planner for a regional team — drag names, see clashes, export the result.

Pick the most boring, most repetitive thing on your week. Open Claude. Describe it: "I do this every Friday — I'd love a tool that..." See what comes back in 90 seconds. You've lost nothing. You may have just deleted a three-hour task from your future.

One honest caveat.

Vibe coding does not replace engineers. It replaces the part where you used to wait. Anything that handles money, customer data, or has to run unattended for years still needs proper engineering, proper testing, proper governance.

But the prototype that proves the idea worth building? That used to take a project. Now it takes an afternoon — and that changes which ideas get to exist at all.