Bloomberg published a piece today about vibe coding and the new kind of FOMO it is creating. If you have not come across the term yet, you have likely seen the output: someone with no engineering background ships a working app in a weekend using nothing but prompts and an AI coding tool. They post a screenshot. The comments fill with a mixture of admiration and quiet dread.

That dread is the FOMO Bloomberg is writing about. Not fear of missing out on a party, but fear of being left behind as non-technical people start building things that previously required a development team.

The question worth asking is not whether vibe coding is real — it clearly is — but what it actually means if you are running a business.

What vibe coding actually is

The term was coined by Andrej Karpathy, a former OpenAI researcher, in early 2025. The idea is simple: instead of writing code, you describe what you want in plain language to an AI agent. The AI generates the code. You describe any problems. The AI fixes them. You never look at the actual code directly.

Tools that enable this — Cursor, Replit, Bolt, Lovable, v0 — have grown rapidly. Recent industry data puts 41% of all code written globally as AI-generated, with 92% of US developers using AI coding tools daily. The market for vibe coding tools is projected to reach $8.5 billion.

The implication is significant: the barrier between “I have an idea” and “the idea runs as software” has collapsed.

Why the FOMO is real

A year ago, building internal software meant either hiring developers, buying off-the-shelf tools, or going without. Today, someone with a clear idea, patience with prompts, and an afternoon can get surprisingly far.

This has created a visible gap between businesses experimenting and those that are not. The gap shows up in:

• Internal tools that used to take months being prototyped in days
• Small businesses automating workflows they assumed were too complex to touch
• Non-technical founders shipping MVPs without a CTO

If your competitors are doing this and you are not, the productivity gap compounds quickly. That is the FOMO Bloomberg is describing.

The trust problem nobody is talking about

Fortune published a piece on April 2 that cuts to what the FOMO framing leaves out. The headline: “In the age of vibe coding, trust is the real bottleneck.”

The trust problem has several dimensions:

You often do not know what you built. When you generate code you cannot read, you are trusting a black box. That works fine for a weekend prototype. It gets complicated when the prototype starts handling real customer data, real payments, or business logic that has to be right.

AI-generated code fails in non-obvious ways. Errors in human-written code are usually visible in the stack trace. Errors in AI-generated code can be structural — a data model that looks fine until scale reveals the flaw, or security logic that almost works until it does not.

Maintenance is a long game. Vibe coding tools are great at generating code and less effective at helping you understand what you shipped six months ago. Adding features to something you do not understand gets progressively harder.

Compliance and security require expertise, not vibes. Healthcare, finance, legal, and any regulated industry cannot run on generated code that nobody reviewed. The liability does not disappear because the code was written by an AI.

None of this means vibe coding is wrong. It means it has a natural ceiling.

What this actually means for business owners

The businesses getting the most from vibe coding right now are using it for a specific category of work: internal tools, one-off automations, proof-of-concept builds, and rapid prototyping.

Where it falls short is anything that needs to be reliable, secure, maintained, and built to grow. That is not a knock on the tools. It is just honest about what they are designed for.

The distinction matters because many businesses are now asking the same question: we need custom software to do X, should we vibe code it or commission it properly?

The honest answer depends on what X is:

• If X is a lightweight internal dashboard that two people use, vibe code it. The stakes are low, the iteration is fast, and you learn something useful along the way.
• If X is a client-facing tool, a data pipeline, a customer communication system, or anything with compliance requirements, the trust bottleneck is a real problem. That is when you need something built properly, with architecture decisions made by people accountable for the outcome.

What This Means for Business

The vibe coding conversation is useful for business owners not because it tells you to vibe code everything, but because it forces a useful question: what software should my business have that it does not have yet?

For years the answer was “we cannot afford to build that.” That excuse is getting harder to sustain. The question is now sharper: of the things we need to build, which ones are prototype-grade and which ones are production-grade?

Getting that distinction right is the difference between a weekend experiment that becomes a competitive advantage and a vibe-coded app that creates a liability. The tools exist to move fast. What you need alongside them is the judgment to know when fast is the right gear.

If you want the playbook other teams are using with Claude and Codex right now, grab the free Working With Claude field guide. Download it here.