We Let AI Write Our Website. Here’s What Happened.

This website you’re looking at? An AI wrote most of it. Not in the "we used Copilot for autocomplete" sense. In the "we described what we wanted and an AI agent built the entire thing across 58 GitHub issues" sense.

The setup

Payload CMS. Next.js. Multi-tenant architecture where multiple client sites share one codebase but get unique domains, themes, and content. Block-based page builder. CSS custom properties for theming. No Tailwind — we wanted to see if AI could write real CSS.

What worked

The AI was shockingly good at the boring stuff. Scaffold a new block type? Done in seconds. Wire up a collection with access control, hooks, and tenant filtering? Nailed it every time. CSS Modules with proper responsive breakpoints? Better than most junior devs.

What didn’t

Taste. The AI has no taste. It’ll write perfectly functional code that looks like a SaaS template from 2019. Every heading is "Empowering Your Journey" until you tell it to knock it off. You still need a human with opinions steering the ship.

The takeaway

AI doesn’t replace the architect. It replaces the scaffolding. The vision, the voice, the "no, that’s corny" — that’s still you. But the 80% of work that’s just translating decisions into code? That’s the part you can hand off.