Our web design process, step by step

You fill out the intake form at /start/web-design. Five steps, about ten minutes. Industry, tier, ten base questions, five industry-specific questions, contact info. Photos and logo upload directly in the form. The intake row lands in our admin console with everything we need to start design.

Our pipeline picks the matching industry starter template, generates first-draft copy with Claude Haiku 4.5 from your intake answers, forks the template repo, and deploys a preview site to Vercel. You get a live URL within 24 hours.

This first draft is not the final site. It is a starting point that already has your business name, your services, your colors, and your contact info wired in. It saves us about three days of "set up the project" work.

A human takes over. We tune the typography to fit the brand. We swap stock placeholders for real photos when you have them. We rewrite headlines and the hero copy. We adjust spacing, motion, and the small interactive details that distinguish a real design from a templated one. Figma for explorations, code for the final version.

Final body copy. Per-page metadata. JSON-LD structured data for search engines. Open Graph images. Sitemap. Robots. Analytics. The unglamorous parts of a launch that decide whether the site ranks and whether it shares cleanly on social.

You get a Loom walkthrough plus a live preview URL. You leave comments inline on the staging site or send back a written list. We do one revision pass. Big changes are caught here. Small changes get queued for after launch.

Domain pointed. SSL verified. Performance budget checked. Lighthouse 95 plus on every page. Final QA on three phones and two desktops. Site goes live. We send you a launch email with everything you need to manage the site going forward: admin links, password vault, runbook.

Next.js, Tailwind, and Vercel for the build and deploy.

Supabase for any data the site needs.

Resend for transactional email like contact form replies.

Claude Haiku 4.5 for first-draft copy. A human writes the headline and the close.

Notion for the runbook and the project notes you can read.

Figma where we need to explore something before writing code.

AI helps. First drafts of body copy, alt text, meta descriptions, image cropping suggestions. The unglamorous high-volume tasks where speed matters more than judgment.

AI does not help. Headlines, brand voice, positioning, the choice of which photo to use, the decision to remove a section. These are judgment calls a human still does better.