We rebuild your website in five working days. No placeholders. No invention.

Reese opens your existing site and walks it the way a careful visitor would. She follows every internal link, opens every product page, reads every word of body copy, and notes the small things most people skip. Your logo URL, your favicon, the exact hex codes you use on buttons, the fonts you pair, the phone number in the footer, the team photos on your About page, the structure of your nav. She writes it all down verbatim in a single brand brief document, and she does not paraphrase. If a page has a stubborn JavaScript widget she could not reach, she flags the gap rather than guess at what it said.

Everything after this stage works from what Reese wrote down. If she misses your Careers page, the new site will not have a Careers page. If she misreads your brand colour as a near-miss grey, the new site will sit a shade off the rest of your printed material, and you will feel it without being able to name it. If she invented a fact you never said, that fabricated fact would ride the pipeline all the way to launch and end up on the live site under your name. The fidelity of this stage is the floor for every stage after it.

Avery takes the raw crawl and turns it into a structured plan. Every page becomes a labelled block. Every section inside a page (hero, about, services, testimonials, pricing, contact) becomes its own labelled block, with the exact heading, the exact paragraph, and the exact call-to-action pasted in word for word from your old site. He is an information architect, not a copywriter. He preserves your voice rather than rewriting it. Where the crawl had a gap, he marks it clearly so it is impossible to miss. Where two pages disagree (two different phone numbers, two different addresses), he flags the conflict so a human can decide.

This is the stage that protects your voice. A small business that sounds like itself converts better than one that sounds like a template. If this stage summarised your tagline, the new site would have a slightly blander tagline. If it invented a testimonial, the new site would carry praise you never received. If it skipped your most profitable service line because it looked small in the crawl, the new site would quietly lose you that revenue. The page plan is the contract that says the new site will say what you already say, in the order you already say it.

Sasha takes the page plan and adds the look on top of it. For every section she specifies the typography (which font, which weight, which size, which line height), the colour (exact hex codes from your brand brief, not approximations), the spacing, the motion, and the image direction. She also tags every image with its source class so the next stage knows what to fetch and from where. A team photo gets one tag, a product photo gets another, an AI-generated hero frame gets a third, a stock illustration gets a fourth. The output is a design spec that is precise enough to test against, not a mood board.

Vague design produces a generic site. If this stage says clean and modern, the build defaults to whatever the framework hands it, and you get something that looks like every other small-business site on the internet. If this stage forgets to tag an image, your founder portrait could quietly become a stock photo of a stranger in a suit. Precision here is the difference between a site that looks like your business and a site that looks like a template with your name pasted on top. Typography alone accounts for most of what people read as look and feel.

Kai works through every image the design spec asked for and fetches the real file. Team photos come from your existing site only, never substituted. Logos and favicons come directly from your brand assets, with Logo.dev used as a fallback when an original URL has rotted. Product photos come from your product pages where they exist. Stock illustrations come from a curated library, and AI-generated hero frames are produced fresh and then verified to be unique, large enough, and visually correct. Every file is checked for size, resolution, and uniqueness before the stage is allowed to close. If something is genuinely missing, it is recorded as missing rather than papered over.

Images are the only thing on your site that visitors actually see as pixels. A grainy hero on the first page someone lands on undermines everything else. A stranger's face on your About page where your real co-founder should be is worse than no photo at all. A site where every section quietly shows the same image (because a generator silently failed) looks broken in a way that is hard to articulate but very easy to feel. This stage is what keeps the visual layer honest, and it is enforced by automated checks, not just by trust.

Morgan scaffolds a Next.js application, sets up the shared header, footer, and navigation, and then orchestrates a small team of focused sub-builders to assemble each section in parallel. Each builder works from the design spec for its single section and imports its images from the manifest. Nothing is hardcoded, nothing is invented, and there is a zero-tolerance rule on placeholder copy, Lorem ipsum, and Coming soon blocks. Before the stage closes, the build is required to pass a full production compile, and every route on the site has to return a healthy response on the dev server. If any of that fails, the stage does not close.

This is where the words and pictures become a real, fast, mobile-friendly website. Sloppiness here is the kind of thing visitors notice immediately: a slow page, a broken button, a contact form that silently swallows submissions, a mobile menu that does not open. Because the build is wired to the design spec rather than improvised, the site you receive will match what was approved at Stage 3 rather than a developer's best guess at it. And because the production compile is non-negotiable, the site that hits hosting is the same site Quinn is about to test, not a slightly different one.

Quinn opens the working site and tests it against the design spec, section by section, page by page. He checks desktop at a typical laptop width, tablet, and mobile. He clicks every link. He fills in the contact form and watches what happens. He scrolls slowly so any motion or reveal effects fire the way they should. He inspects alt text on images, heading hierarchy on each page, contrast ratios on text, and keyboard navigation on interactive elements. Every defect he finds is recorded with what the spec said, what he actually saw, the severity, and the specific fix he is recommending. The stage closes with a single verdict, either pass or fail.

A site that looks fine at a glance and a site that holds up under inspection are not the same site. A broken link on the services page is the kind of thing a real visitor will eventually hit, and the cost when they hit it is that they leave. A form that quietly drops submissions is worse than no form at all, because it looks like demand is missing when it is just being thrown away. Mobile bugs in particular tend to be invisible to a desktop reviewer, and they affect the majority of your visitors. This stage exists so problems get caught here, not by your customers.