Behind the build
A practice build

Inside a 48-hour website build.

Before we took the 48-hour build to a paying customer, we put a bakery we made up through it ourselves, start to finish, to watch every step hold or break. Not a client, and we’re not going to dress it up as one. This is the real sequence, including the three things it caught.

August 2, 2026 · Plainsmith

Written the day of the run. We’ve since folded the workflow tools into the website plan, so the one line about buying tools is gone. The 48 hours still mean what they meant then: from your finished questionnaire and your payment to a preview in front of you, not to a site going public on its own.

01

The questionnaire lands.

What you do, what you sell, your hours, your area, two numbers you’re proud of, and the story behind the name. We store it before the payment is even created, so nothing is lost if you wander off at checkout. The bakery gave us its services, hours, location and contact details and not much else, which is about what a first questionnaire looks like.

02

Copy first, mechanics second.

Before a single page is assembled, we transcribe the facts exactly, hours and prices and phone, and then write 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 come from the questionnaire and nowhere else. In the review pass, “never cloying” became “sweet, but not too sweet”, which is a thing a person says about a cake.

03

The build.

Four pages came out of it: Home, Services, About and 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 questionnaire gets four good pages instead of five thin ones, and the job of the layout is that the services, the hours and a way to get in touch are easy to find.

04

Photos, honestly.

This questionnaire had none. Rather than ship a bare page, we put licensed photos in and flagged each one as a placeholder on the preview, and the go-live email asked 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.

05

Checks that don’t rely on somebody remembering.

Automated passes at desktop and phone width: no sideways scroll on any page, the phone number tappable, the form actually posting, no template text left behind, the fonts the ones we chose. Then we look at it, because valid HTML alone would not have shown us the wrong font or the awkward line.

06

One of us looks before you do.

Nothing reaches a customer unreviewed. One of us reads the finished site against the questionnaire, then the preview goes to one phone with a summary of anything the answers left ambiguous. Here that was the missing photos, and a typo in the owner’s own wording that we fixed while keeping the fact intact. The handover says what is ready, what still needs you, and where to approve.

What the run caught.

Three things, and every one of them would have reached a paying customer if the first build had been a real one.

Every site was shipping in fallback fonts.

A security header in our template allowed the font stylesheet and blocked the font files, so the browser used its fallback. One line, invisible unless you look at a console. We fixed the header and checked the type in the browser, on every page.

Leads weren’t reaching the owner on their own.

A test inquiry alerted us and waited for a human to forward it. Fine for one client, broken for twenty. We changed delivery so the inquiry emails the business owner directly, with a reply-to that goes straight back to their customer.

“Saved” did not mean saved.

The launch checklist told the owner their answers saved as they typed. They only saved on a button, so an owner could type their tax ID, close the tab, and lose it. We made the checklist save as you go, instead of softening the sentence.

The review link is a handover, not a finish line.

You still check the business details, send the photos we asked for, and approve the launch. Your domain has to be set up before the site goes public. The workflow tools come with the website plan now, and any phone or payment account a tool needs is still yours to connect, with us checking it beside you.

Why publish this? Because “we build it for you in 48 hours” is easy to say and impossible to check from the outside. A pipeline nobody stress-tests finds its faults on a paying customer. This one found three on a bakery that doesn’t exist, which is where we’d rather find them.

The next build note

What the Console review changed