How we built this site in a day
A dogfooding teardown of the site you are reading: from an empty repository to a live, production-grade marketing site (design system, search, SEO, AI imagery, contact form, custom domains and CI) in seven commits, under a day.
The most honest proof we can offer is the page you’re standing on. This site is a dogfooding artifact: it was designed, built, and shipped to production using the same agent-driven, guardrailed workflow we set up for clients, and we kept the receipts in the git history.
From an empty repository to a live site on a custom domain: seven commits, under a day.
The commit log
| # | Commit | What shipped |
|---|---|---|
| 1 | Initial commit | The whole Astro 6 site: design system, content collections, Pagefind search, SEO/JSON-LD, and a generated llms.txt |
| 2 | Pin Node 22 | Match Cloudflare’s build image to what Astro 6 needs |
| 3 | Workers deploy config | Static-assets Cloudflare Worker; first live deploy |
| 4 | www → apex + 404 | Redirect, a branded 404 page, and the first push through CI |
| 5 | Brand imagery | On-brand abstract art generated with FLUX for the OG card and contact banner |
| 6 | Dev-first focus + contact form | Sharpened the positioning and wired a working contact endpoint |
| 7 | Verified-domain email | Send contact mail from a verified address |
That’s not a prototype. It’s the full production stack: a token-driven design system in
Tailwind v4, static-output Astro 6 shipping near-zero JavaScript, Pagefind
search that indexes the built site, a complete SEO layer (sitemap, RSS, OpenGraph,
structured data) plus an llms.txt and an AI-welcoming robots.txt for findability,
AI-generated brand imagery, hosting on Cloudflare Workers with two custom domains,
continuous deployment on every push to main, and a contact form that actually
delivers email.
Read it through the three tiers
It’s worth being precise about what “in a day” does and doesn’t mean, the same honesty we apply to every number here.
- Basic AI (a chatbot in a browser) would have helped with snippets, but a human still hand-assembles every component, wires the build, configures DNS, and debugs the deploy. Realistically several days for this scope.
- Agentic AI (a coding agent you drive step by step) scaffolds and writes fast, but you still prompt each task, review every diff, and run the deploys, DNS, and CI changes by hand.
- Advanced AI (the workflow we build) closes those hand-offs: setup, build, deploy, and the docs that keep it maintainable run as guarded steps, with a person directing and approving rather than operating.
To be straight about it: this site was built by one person directing AI agents, somewhere between the Agentic and Advanced tiers. The headline isn’t “AI did it alone.” It’s the cadence, and the fact that the entire production surface (not just the code, but the hosting, CI, domains, imagery, and SEO) came together in a day at a quality bar we’re happy to put our name on.
The honest asterisks
- “A day” is the build window, 21 May 2026 (a final from-address fix landed the next morning, commit seven). It is not a claim that every piece of software is a day’s work.
- This is a marketing site, not a complex application with a database and auth. We scope claims to what they are.
- This very post is a later commit. The site is a living document, which is rather the point.
We measure everything this way: what’s real and timed, and what’s an honest estimate, kept clearly apart. That’s the subject of how we measure the hours saved, and you can see the same workflow at production volume in inside 452 AI-built pull requests.
Want a build (or a delivery workflow) that moves like this? Book a strategy call.