Behind the build · 01
Anatomy of a 48-hour build.
August 2, 2026 · what actually happens between your brief and your live site
We put a brief through our own pipeline end to end — a made-up bakery, invented so we could watch every step break or hold. Not a client, and we're not going to dress it up as one. What follows is the real sequence, including the three things it caught.
The steps
1 · The brief landsTen minutes of questions: what you do, what you sell, your hours, your area, two numbers you're proud of, and the story behind the name. It's stored before payment is even created, so nothing is lost if you wander off at checkout.
2 · Copy first, mechanics secondBefore a single page is assembled, the facts get transcribed exactly — hours, prices, phone — and the writing pass happens against a research library for that trade. The bakery library has real sentences from real bakeries in it, so the words land in the register a baker actually uses. Facts are copied verbatim; only the connective writing is ours.
3 · The buildFour pages come out of the factory: home, services, about, contact. The fifth page is earned, not padded — a gallery if there are enough photos, a menu or FAQ page if the content fills one. A thin brief gets four good pages instead of five thin ones.
4 · Photos, honestlyThis brief had none. Rather than ship a bare page, licensed photos go in and get flagged as placeholders — and the go-live email asks for three to five real ones. Real photos of your own work beat a stranger's perfect ones every time, and the site tells you so.
5 · Checks that don't rely on someone rememberingAutomated passes at desktop and phone width: no sideways scroll on any page, phone number tappable, forms actually posting, no template text left behind. Then a register check that flags words the owner wouldn't use — it caught "never cloying" in a bakery menu and made it "sweet but not too sweet."
6 · A human looks before you doNothing reaches the customer unreviewed. The preview goes to one phone with a summary of anything the brief left ambiguous — in this case: no photos, and a typo in the owner's own wording that we fixed while keeping the fact intact.
7 · You flip the switchApproval opens a checklist in your account: walk your site, confirm the facts, add photos, connect your Google listing, and — if you bought tools — a payment link and your texting registration. Each step says how long it takes and what you'll need in hand. Nothing goes public until you press the button yourself.
What the run caught
Every site was shipping in fallback fonts. A security header in the template was blocking the font files. One line, invisible unless you look at a console, and it would have hit every client until someone noticed.
Client leads weren't reaching clients automatically. A form submission alerted us and waited for a human to forward it. That's fine for one client and broken for twenty, so leads now email the business owner directly, with a reply-to that goes straight back to their customer.
A "saved" promise that wasn't true. The launch checklist said answers save as you go. They only saved when you pressed a button — so an owner could type their tax ID, close the tab, and lose it. We made the promise true instead of softening the sentence.
Why publish this
Because "we build it for you in 48 hours" is easy to say and impossible to check from the outside. This is the part a normal marketing page skips: what the steps are, where a build can go wrong, and what we do about it when it does. The bugs above are the argument — a pipeline nobody stress-tests is a pipeline that finds its faults on a paying customer.
The next one of these will be a real client build, with their permission, and their numbers.