When I heard Odoo 19.3 shipped a native AI web design assistant — one that could build a website from inside the front-end editor — I had to test it.
Not in a “let’s see what this thing looks like” way. In a structured, graded, apples-to-apples comparison against the workflow I actually use: Claude Code running in VS Code, directly editing Odoo themes.
Here’s what I found.
Odoo 19.3 — 12 / 33
Claude Code + VS Code — 33 / 33
The Setup
I started with a fictional remodeling company — Rubber Ducky Remodel — and a random logo. I fed the logo into Claude Design, which produced a website handoff document: a full spec covering fonts, color palette, section structure, copy direction, and imagery guidance. The kind of document you’d hand to any competent web designer, human or AI.
From that spec, I identified 11 elements that a complete homepage should include. Each element was scored 0–3:
- 0 — not present
- 1 — partial or missing critical details
- 2 — mostly there, but gaps
- 3 — fully executed to spec
The 11 elements: Typography, Hero, Trust Strip, Services, How It Works, Why Rubber Ducky, Before & After, Reviews, Service Area, FAQ, and Final CTA Band.
Then I handed the same brief to each workflow and graded the output.
Odoo 19.3 — Native AI Builder
Odoo 19.3 includes an AI web builder powered by a language model directly inside the website editor. For this test, I ran it on Runbot with Gemini 2.5 Pro.
The result was serviceable. The builder produced a real, navigable homepage with a hero section, trust strip, services overview, how-it-works steps, and a final CTA band. For someone who has never built an Odoo website and just wants something live, this is genuinely useful.
But it didn’t hit the spec.
What it missed:
- Typography — The fonts specified in the handoff doc (Fredoka, Mulish, JetBrains Mono) were ignored entirely. The site defaulted to Odoo’s theme fonts.
- Hero — The H1, subhead, and CTAs were roughly right, but the background image was a generic stock photo of an office building — not the warm, finished bathroom image the spec called for.
- Services — The section existed, but the branded headline (“One crew. Three specialties.”) was replaced with a generic “Our Services.”
- How It Works — The four steps were present, but the one-line descriptions under each step were absent.
- Five sections missing — Why Rubber Ducky, Before & After, Reviews, Service Area, and FAQ were nowhere on the page.
Score: 12 / 33
Claude Code + VS Code
My current workflow uses Claude Code running inside VS Code, editing the Odoo theme files directly. The same Claude Design handoff doc was the input.
The output was denser. Above the fold, you had the hero and the trust strip. Scrolling down: the crew intro, services, process steps, the “Why Rubber Ducky” differentiator section, before-and-after image placeholders, testimonials, a service area callout, an FAQ accordion, and the final CTA band.
Every font matched. Every section was present. The structure followed the handoff document closely.
Score: 33 / 33
Full Scorecard
| # | Element | Odoo 19.3 | Claude Code + VS Code |
|---|---|---|---|
| 1 | Typography | 0 | 3 |
| 2 | Hero | 2 | 3 |
| 3 | Trust Strip | 3 | 3 |
| 4 | Services | 2 | 3 |
| 5 | How It Works | 2 | 3 |
| 6 | Why Rubber Ducky | 0 | 3 |
| 7 | Before & After | 0 | 3 |
| 8 | Reviews | 0 | 3 |
| 9 | Service Area | 0 | 3 |
| 10 | FAQ | 0 | 3 |
| 11 | Final CTA Band | 3 | 3 |
| Total | 12 / 33 | 33 / 33 |
What This Actually Means
A few things are worth saying plainly.
This test has confounding factors. Running on Runbot with Gemini is not the same as running Odoo 19.3 in production with a better-configured model. The Runbot environment constrains what the builder can access, and the model selection matters. A different setup might produce different results.
But for Odoo Online users, this is the reality. If you’re on Odoo Online — particularly on a standard plan — the native AI builder is your primary option. You don’t have a local IDE, you don’t have direct file access, and you’re not going to spin up a Claude Code environment. For that user, 19.3’s builder delivers something real. It’s just not a faithful execution of a detailed spec.
This gap will close. Odoo is investing heavily in this feature. The R&D is visible and the trajectory is clear. In two or three versions, this comparison will look different. The question isn’t whether the native builder gets better — it will — but how much of a head start the external IDE workflow provides in the meantime.
Watch the Experiment
I walked through the full comparison on video, including side-by-side screenshots of both outputs. You can watch it here: https://youtu.be/xKQLj8nwpHE
Questions or pushback? Drop a comment on the YouTube video or find me on LinkedIn.