HT Blue Built an Entire Small Consulting Firm's Website in Under 10 Minutes

A client emailed us a link to their 15-year-old website, along with a list of everything that was broken. They wanted to keep the logo and replace everything else. Less than ten minutes later, we sent back a link to a new ten-page site running in production.

The stopwatch makes a good headline, but it is not the interesting part. What interests me is why the work could move that fast, and which parts of it still belong to people.

The Brief Was Already Written

The old site looked its age, and the client knew it. Their email spelled out exactly what was broken and what they wanted changed.

That list mattered more than any tool we used. A clear statement of what is wrong is a specification. Most website projects spend their first weeks producing one. This client handed it to us in an email.

How the Ten Minutes Broke Down

We split the work across two AI systems, each doing what it does best, with our team directing both.

• Design with Codex. OpenAI's Codex is best known as a coding agent, but OpenAI added image generation to it in April 2026, so the same tool can produce UI mockups and visual assets. We used it to generate page designs from the client's brief.
• Build with Claude. Claude, Anthropic's AI model, turned the chosen designs into working code: new copy, new hero sections, new call-to-action icons and imagery, ten pages in all.
• Domain and deployment. We purchased a new domain and deployed straight to production.
• Form capture with Resend. Resend is an email API for developers, a service that lets code send email reliably. We wired its API keys into the site's forms so every inquiry reaches the client.
• Handoff. We emailed the client a live production link. They were floored.

Why Two Models Instead of One

From a systems architecture perspective, the useful idea here is the handoff. The mockup acts as a contract between agents. Codex commits to a visual direction, and Claude builds against it.

Builders working on image-to-website workflows report the same lesson: keeping the reference image in front of the coding model is what holds the result together. Each agent gets a narrower job, and a narrower job is easier to check.

That is what people miss when they hear "AI built a website." No single prompt produced this site. People decided what the client needed, chose which design direction to build, and rejected output that wasn't right. The agents compressed the execution. They did not make the decisions.

The Ten Minutes Rested on Years

Three things made the speed possible, and none of them happened inside the ten minutes.

• A clear brief. The client knew what was wrong and said so.
• A ready stack. Our build, hosting, and form patterns were already in place, so nothing was invented on the clock.
• Judgment at every handoff. Our team knows what a small consulting firm's site needs to do, which let us accept or reject AI output in seconds instead of debating it.

Agentic automation works best when the people around it have already done the thinking. Then the agents can do in minutes what used to take a project team weeks.

What Ten Minutes Does Not Cover

Being honest about speed means being clear about what comes after the link goes out.

• Redirects. A 15-year-old site has inbound links and search history. Old URLs need to redirect to the new domain, or that value is lost.
• Copy review. AI-written copy is a strong first draft about someone else's business. The client still confirms every claim about their services, credentials, and experience.
• Accessibility and performance testing. A site that looks right still needs testing with keyboards, screen readers, and real devices.
• Email deliverability. Form notifications should send from a verified domain so they land in the inbox, not in spam. With Resend, that means adding DNS records to verify the sending domain.
• Ownership. The client should own the domain, the code, and the accounts, not just a link.

Scale matters too. A ten-page site for a small firm is a different problem from an enterprise CMS migration, where content models, integrations, and governance make extreme speed a warning sign. Marla Quinn makes that case in The Trap of AI CMS Migrations. Small, focused sites are where this approach shines.

Practical Takeaways

• If your website is small and old, replacing it is now a matter of minutes or hours, not months. The slow part is deciding what you want.
• Write down what is broken. That list is the most valuable input you can give anyone rebuilding your site.
• Treat speed as half the job. Ask whoever builds it about redirects, accessibility, copy accuracy, and who owns the domain and code.
• Let AI agents handle execution, and keep people on the decisions.

If your firm's site is overdue, our Small Business Package and Vibe Coding Services are built for this kind of fast, focused rebuild. Get in touch and send us your list.