How much of your own time a website build actually takes

What a builder needs from the buyer, and at which point in the project

A website project doesn't stall because the builder disappears. It stalls because a few emails asking for photographs and business hours go unanswered, and nobody flags it as a problem until the delivery date has already slipped.

Every website build has two people doing real work on it, and one of them is you. A builder can lay out pages, write code, and build features on schedule. What they can't do is invent your opening hours, your service list, or your staff photos out of thin air. Those come from you, and the schedule depends on when they arrive.

The need for that input doesn't land all at once. Early on, a builder needs the basics: what pages you want, what the site needs to do, roughly how you picture it looking. Later, the need shifts to content and detail — the actual words, the actual photos, the actual prices for each service.

A builder who spaces those questions out across each phase, rather than dumping every one of them on the kickoff call, is doing you a favor. It gives you time to gather what's needed instead of scrambling the week it's due. What that whole schedule actually depends on is largely this rhythm of asking and answering.

Gathering photographs, hours, services and staff details before the build starts

The biggest time cost on your side is gathering what already exists rather than creating anything new. Photographs of the actual shop, the actual hours you're open, the actual list of services with actual names — none of it is creative work. It just needs somebody to sit down and pull it into one place.

Waiting for a builder to ask for each piece is the slow way to do this. Gathering photos, hours, services, and staff details before the project starts, in a single folder or document, turns a dozen scattered requests into one clean handoff.

A phone camera and decent lighting cover a lot of what a small site needs in photography. Professional photos help, but waiting on a shoot shouldn't be what holds up an entire launch. Start with what exists now, and swap in better images later if it matters that much to you.

Review rounds, and how much attention each one really takes

A review round isn't a formality you skim in thirty seconds and wave through. It's the point where you catch a wrong phone number, a service you no longer offer, or a photo that doesn't match what's actually on the menu. Skipping a careful look here is how small mistakes reach a live site.

That said, a review round doesn't need to eat an evening. Looking at a page with a specific question in mind — does this describe what we do, is the contact information right, does anything look off — takes a fraction of the time an open-ended, style-it-yourself review takes.

Specific feedback moves faster on both ends. A note saying the second paragraph doesn't match what you actually offer gets fixed quickly. A vague sense that something feels off sends a builder guessing, and guessing costs you both time neither side needed to spend. Turning a fuzzy feeling about a page into words a builder can act on is worth practicing before the first review lands in your inbox.

Who inside the business is allowed to approve a page

A page can get approved by you, then unapproved by a partner or manager seeing it for the first time after it's already live. That isn't a builder problem. It's a decision-making problem that started before the build did, and it costs real time to unwind once a page is built around one person's sign-off.

Decide, before the project starts, exactly who has final say on each page. One person doesn't have to make every call alone, but somebody needs to be the one whose approval actually means approved, rather than a rotating cast of people each weighing in at a different stage.

This matters most on anything two people in the business might disagree about: pricing language, service descriptions, the tone of the homepage copy. Settling who owns that call before a page is first presented saves a round of rework that has nothing to do with the site's quality and everything to do with who gets the final word.

What happens to a project when the buyer goes quiet

A project doesn't collapse the moment you go quiet on an email thread. It slows, then stalls, then sits until somebody remembers to check on it. A builder working through a queue of other projects can't hold a slot open indefinitely waiting on photos that never arrive.

Silence usually means something ordinary, not neglect. You're not ignoring the project — you're buried in the actual business the site is meant to support, and the email asking for staff bios slid down the inbox. That's understandable. It's also exactly the gap that stretches a timeline the most.

What a stalled project does to price is worth knowing before it happens to you. Time a builder spends reopening a project, re-reading old notes, and rescheduling around a gap is time that has to be accounted for somewhere, and a paused project rarely restarts exactly where it left off.

Agreeing feedback deadlines the same way delivery dates get agreed

A delivery date gets written into a proposal as a specific commitment. The deadline for your feedback doesn't always get the same treatment, and that asymmetry is where a lot of projects quietly slip. A builder promising a date is only keeping half of a two-sided agreement if nobody wrote down when you're expected to respond.

Ask for feedback deadlines the same way you'd ask about a delivery date: specific days, tied to specific milestones, written down where both sides can see them. A homepage draft with feedback due by a stated date is a commitment you can actually plan around. A vague promise to send it over whenever you get a chance is not.

A missed feedback deadline deserves the same kind of conversation a missed delivery date would get — not blame, just a clear-eyed look at what it does to the rest of the schedule. A request that grows into something bigger than a quick review is worth naming early, before it quietly eats a deadline that was set for something smaller.

More from the blog

All posts