Vibe Coding Is Fun. Don't Use It for Your B2B Site.

Vibe coding is everywhere right now. Lovable, Bolt, v0, Cursor — describe what you want in plain English, watch a site appear in minutes, ship before lunch.

The term comes from Andrej Karpathy, OpenAI founding member, who coined it in February 2025. His description was honest about what it is: "fully give in to the vibes, embrace exponentials, and forget that the code even exists." That's the appeal. It's also the warning label.

Karpathy himself has since moved on. He now uses the term "agentic engineering" for serious AI-assisted development — explicitly to distinguish it from vibe coding. When the person who named it stops using the name, that's a signal.

What vibe coding is genuinely good for

Be fair to it. Vibe coding earns its keep when:

Speed matters more than longevity. You need a prototype for a pitch on Monday. You're testing an idea before committing. You're learning by building, not building to ship.

No real users yet. An internal tool used by three people. A landing page for an event next week. A throwaway dashboard.

The cost of being wrong is low. If it breaks, no customer notices. If you rebuild it next month, no contract is at risk.

Why your B2B website is none of those

A B2B site has a different job. It's the thing a CEO checks before signing a contract worth fifty thousand euros. It's the thing your competitor's procurement team compares yours to. It's the thing that has to load in under two seconds in a meeting room on a hotel WiFi.

Vibe coding ignores almost all of that by design. Specifically:

Trust comes from coherence. Vibe-coded sites look generic because they were assembled from generic patterns. A B2B buyer can spot it. They don't always know why, but it lands as "this company doesn't take itself seriously."

Performance is engineering, not a vibe. Core Web Vitals affect both SEO and conversion. A vibe-coded site might look fine and still ship a 3 MB JavaScript bundle that kills it on mobile.

Integrations are where reality breaks the prompt. CRM, analytics, marketing automation, GDPR-compliant forms, cookie consent for Norwegian and EU users — the moment you wire it to your actual stack, the vibes stop and the architecture starts.

The code is your liability. When something breaks at 11 PM on a Sunday, you own that code. If you accepted it without reading it, you have no idea what it does. "I'll just have AI rebuild it" works for a prototype. Not for a site customers depend on.

What to do instead

Use vibe coding to think out loud. Sketch the site, try ideas, throw away versions. Then have a competent developer — or an AI-assisted one who actually reads the code — build the real thing on a maintainable stack with real testing.

The fast version is fine for a weekend. Your B2B site has a longer job.

Building or rebuilding your B2B site and not sure which path fits? Get in touch.