Oxygen's UAE Digital Blogs | Expert Insights on HubSpot, AI & CRM

Why You Shouldn't Vibe Code Your Company Website: 4 Risks | Oxygen

Written by Alwyn Mathew | Nov 18, 2026, 1:48:09 PM

You shouldn't vibe code your company website, because the launch is the only part AI makes easy. Keeping the site credible, secure, up to date and editable by your team takes years, and nobody writes a prompt for that part.

The appeal for a marketing director is obvious. Describe the site to an AI tool after lunch and it's live by the evening, without an agency brief or a six-week wait.

The costs arrive months later, when the site has to grow, change and stay safe.

What is vibe coding, and what is an AI website builder good for?

Vibe coding means describing the website you want to an AI website builder, such as Lovable or Bolt, and letting it write the code. A working site appears in minutes, at a fraction of an agency's price.

That speed is useful. A prototype to brief a designer, a page to test an idea, a site for a one-off event: AI builds all of them well. The trouble starts when the prototype becomes the company website without anyone deciding it should, and the business inherits everything a website needs once it's live.

What risks does a vibe-coded website create for a business?

A vibe-coded website creates four risks: it can make your firm look cheap, it is harder to keep secure, it is harder to maintain, and your team can't easily change it or connect it to your CRM. All four get worse as the company grows.

Brand: it makes your firm look cheap

A vibe-coded website looks finished at first glance and generic at the second. AI builders produce a competent average: familiar layouts, images that look slightly wrong, and copy that says a lot and tells the reader nothing. Asking the tool to "make it better" rarely helps. It piles on more until the page gets busier and worse.

Nearly a third of consumers say AI-generated marketing makes them trust a brand less, and the share who prefer AI-generated content fell from 60% in 2023 to 26% in 2025. A site that looks machine-made tells a prospect you didn't bother, before they've read a word.

Laurent Ross, Oxygen's Managing Partner EMEA, makes the wider case in how AI slop is killing professional services brands: the tools are fine, and the damage comes when nobody with taste reviews what they produce. Vibe coding usually skips that review.

Security: AI now finds the weak spots

The same kind of AI that builds websites is now finding their weaknesses. In October, researchers used AI to find a serious flaw in PHP, which runs most of the world's websites, and attackers were already using it before a fix was out. If AI can find holes in software that has been reviewed for decades, it finds them faster in code nobody reviewed at all.

Months earlier, an experimental OpenAI model got into Australian government systems during testing, in one case through an access key someone had left exposed. Nobody told it to break in: it was looking for data. OpenAI later apologised.

Vibe-coded sites leave the same kind of keys exposed. A scan of 5,600 of them found more than 400 exposed access keys and other secrets, and Veracode found that AI-written code introduced a security flaw in 45% of its tests, close to a coin toss. The next one to find those keys won't apologise.

Upkeep: every fix starts with code your team didn't write

Every website needs looking after: security fixes, software updates, and the page that breaks after an update. Who on your team could fix it tonight if it broke?

A vibe-coded site makes that harder, because nobody on your team wrote the code or decided how it fits together. Whoever maintains it, from the person who prompted it to a freelancer or an agency, has to work out how it was built before they can fix it. Asking the AI to patch its own work only helps if someone can check the fix.

Control: your team can't change it or connect it

A site that an AI writes as one block of code can't be edited in a normal page editor. Changing a headline, adding a page or swapping an image then needs a developer or another round of prompting, which is the very dependency vibe coding promised to remove. The forms are often stuck too, sending enquiries to an inbox instead of your CRM.

"You can even vibe code it and have it on HubSpot, but then it's not editable. Your team can't just go in and drag and drop a module."

Laurent Ross, Managing Partner EMEA, Oxygen

If your firm already has a site built with AI and nobody is sure who looks after it, ask Oxygen's web team to review it. We'll tell you what to keep, what to fix and what to rebuild.

Why do these risks matter more for professional services firms?

A professional services website carries your clients' trust, and often their data, so one security slip costs more than vibe coding ever saved. A law firm, audit practice or consultancy that leaks a client document through its website can lose that client, and every referral they would have sent.

The legal exposure sits with you as well. Personal data collected through your website forms falls under the UAE's Personal Data Protection Law, or under DIFC's or ADGM's own data protection rules if you're licensed there. Either way, the business carries the risk, whichever tool built the site.

What should a company website run on instead?

A company website should run on a managed platform, where a dedicated security team keeps the foundations patched and your team keeps control of the content. HubSpot, the platform we build on, showed what that looks like in October.

When the PHP flaw broke, HubSpot confirmed on its Trust Center that PHP isn't part of its platform, so its websites had nothing to fix. When researchers reported a critical flaw in HubSpot's own CMS on 13 October, it had a permanent fix live within about eight hours, with nothing for customers to do. On a vibe-coded site, you are the security team.

What does a properly built website have that a vibe-coded one doesn't?

A properly built website has three things a prompt doesn't produce: a design system, a planned architecture and security built in from the start. None of them shows up in a demo, which is why a prompt skips them.

Design system: keeps every page on brand

A design system is the set of approved building blocks a website is made from: headers, page sections, forms, buttons and templates, each in your fonts, colours and spacing. Your team builds new pages by combining them, so page fifty looks as deliberate as page one.

A vibe-coded site has no such system. Every prompt gets a slightly different answer, so the site drifts further off brand with each change.

Systems architecture: decides where every lead and record goes

Systems architecture is how the website fits with everything around it: your CRM, forms, email, analytics, each language version, and where the data is stored. Get it right and an enquiry lands in your CRM with its source attached, assigned to the right person. Get it wrong and leads sit in an inbox while nobody can say which campaign paid for itself.

An AI builder answers the prompt in front of it. It doesn't ask where form data should go, who needs to see it, or what happens when you add a second language or a third market.

When our client Tricor, a business services group with offices in 49 cities across 22 markets, moved more than 1,000 pages from WordPress to HubSpot, the architecture was planned first: market sites under one CMS that local teams could run, and a form on every location page feeding leads to the right owner.

Access and permissions: planned before launch

On a properly built site, security is decided before launch: who can sign in and what each person can change, two-step sign-in for editors, access keys kept out of the code, and forms that collect only the data you need. Vibe code the site and each item depends on someone thinking to ask.

We use AI in website builds every day. It works because those three are in place first, and because people with taste reject an average first draft.

When is vibe coding fine, and when should you build properly?

Vibe coding is fine wherever nothing important breaks if the site does. Build properly once a site carries clients, data or a team.

Vibe coding is fine for Build it properly for
A prototype to brief a designer Your main company website
A page to test an idea with a few customers Anything clients or staff log in to
A one-off event page with no form Forms that collect personal data
A demo for an internal pitch Sites connected to your CRM or payments
A solo founder's first landing page An Arabic and English site that several people update

If your site belongs in the right-hand column, the cheap build is the expensive one.

How do you know if your company website is built properly?

Ask your team six questions this week. If any answer is vague, the website needs a proper build, whoever built it the first time.

  • Does every new page look like your brand, without a designer fixing it first?
  • Does every form send enquiries straight into your CRM, with the page and campaign they came from?
  • Can you see the full customer journey, from the first page a lead read to the meeting they booked?
  • Can marketing launch a landing page for a new campaign in a day, without a developer?
  • Can your team edit any page in the CMS, in English and Arabic, without breaking the layout?
  • Who applies the security fixes, and how quickly?

Oxygen's web team builds HubSpot websites for professional services firms, with AI speeding up the build and people checking what it writes. Book a website consultation and we'll answer those six questions for your current site, and show you what fixing each one takes.

FAQs on vibe coding a business website