I run WebFluence Digital — a one-person web design and SEO agency in Dublin. When it came time to rebuild my own site, I used the same AI agent pipeline I'd been building for clients. This is what that looked like.

The constraint
I needed a site that:

Looks credible enough to sell premium web design to Irish SMEs
Ranks for "web design dublin" and related local terms
Demonstrates the actual output quality — eat your own cooking
And I needed to build it fast, because I was simultaneously building the pipeline.

The agent squad
I run an 8-agent system called webfluence-squad — a Claude Code plugin where each agent owns a specific phase of the build and writes its output into Airtable. The next agent reads from it. No manual handoffs.

Phase 1 (parallel): ux-researcher | brand-guardian | inclusive-visuals
Phase 2: visual-storyteller
Phase 3 (parallel): ux-architect | image-prompt-engineer
Phase 4: ui-designer
Phase 5: senior-pm — QA, compile, deploy to Vercel
ux-researcher scraped competitor agency sites and synthesised Dublin SME pain points — actual quotes from Reddit and Google reviews, not invented personas.

brand-guardian locked the design system: #E9204F red, #0A0A0A background, Poppins 700/900 display, Inter body. WCAG contrast ratios checked before a single component was written.

visual-storyteller turned the research into a scene-ordered storyboard — every section gets a narrative role, copy direction with actual headline drafts, and animation notes.

ux-architect produced the full component spec: Tailwind v4 tokens, layout systems, animation triggers, responsive strategy — copy-paste-ready code.

image-prompt-engineer wrote Imagen 3 prompts for every hero and section image. Iterated until approved against the brand direction.

ui-designer rendered everything: production-ready Tailwind classes, interaction states, dark mode, accessibility notes.

senior-pm compiled, QA'd, and shipped to Vercel.

The stack
Next.js 14 App Router, Tailwind CSS v4 with @theme inline, Framer Motion for scroll-scrubbed sequences, Lucide React, Vercel. Standard across all WebFluence builds.

The SEO layer
Before the build squad ran Phase 2, I fired a separate visibility audit — visibility-strategist — which produced the sitemap architecture, primary keyword per page, and FAQ schema specs. The new site was built to rank before it went live, not retrofitted after.

The result
webfluence.digital is live and indexed. 17 pages, dropdown nav, mobile drawer, contact form wired to Web3Forms. The same squad and stack I now use for every client build.

Full write-up of the visibility audit methodology — including the open source tool — in the WebFluence resources section.