The One-Week Website: What Actually Takes the Time

"One-week website" is a phrase we use in proposals, and it's true, but it hides where the week actually goes. Clients picture us typing code for seven straight days. That's maybe a day and a half of the actual timeline. The rest is decisions, and decisions are the part clients control, not us.

Building the pages themselves, once we know what they need to say and look like, is fast. A homepage, an about page, a services page, and a contact page, built on a solid template with real content dropped in, takes us roughly a day of focused work. That's the part people imagine when they hear "one week."

What takes the other five and a half days is everything that has to happen before that day of building: agreeing on the words, choosing which three services get top billing out of the eleven things you actually do, finding or shooting photos that don't look like stock, and getting someone at your company to approve a decision instead of saying "let me check with the team."

Every slow website project we've ever run was slow because of words, not design. Design has fewer decision points, and most of them are ours to make once we understand the brand. Copy requires someone from your business to decide, in writing, what you do, who it's for, and why anyone should care. That's a harder job than it sounds, and most founders have never had to compress their business into four sentences before.

We've started asking clients to answer five plain questions before we write a line: who buys from you, what do they usually say when they're annoyed with a competitor, what's the one thing you wish people knew before they called you, what do you charge more for than everyone else and why, and what happens in the first week after someone becomes a customer. Those five answers, even messy ones, save us more time than any style guide.

Second biggest time cost: usable images. Most small businesses have a phone full of blurry product shots and one nice photo from a launch event three years ago. If we're shooting new photos or video, that's a scheduling problem as much as a creative one. We need your team, your space, and daylight, all lined up on the same afternoon.

If we're not shooting new material, we're often hunting through what exists to find five images that don't contradict each other in lighting, color, and quality. That search takes longer than people expect, because a website with mismatched photography looks unfinished even when every sentence on it is perfect.

We've timed it. On a typical project, the actual build takes about 30% of the calendar time. Approvals, meaning the gap between us sending something and a client giving a clear yes or a specific edit, eat close to 40%. The rest is copy and photo prep. A slow approver can turn a one-week website into a six-week website without a single hour of extra work happening on our end.

We quote a week because that's how long the work needs when a client shows up ready. It's not a marketing number, it's a target that keeps everyone honest about what's actually required from their side. Clients who hit it usually aren't more organized people in general, they've just decided the website is the priority that week, not a background task squeezed between everything else.

If you can't clear that space this month, that's fine, but say so up front. We'd rather plan a realistic three-week timeline around your schedule than watch a one-week plan quietly become two months because approvals kept slipping.

It's worth saying clearly what a "day of building" actually includes, because clients sometimes picture typing from a blank screen. In reality it's assembling a template we already trust, dropping in finished copy, placing chosen images, and adjusting spacing and color until the page feels like the brand instead of a generic layout. The template does the structural thinking. Our time goes into the specific choices that make it feel like your business rather than any business.

We also budget time for what we call the boring middle: setting up the contact form to actually reach an inbox someone checks, connecting analytics, making sure the site looks right on a small phone screen and not just a laptop, checking that every button actually leads somewhere. None of this is glamorous work, but skipping it is how a website looks finished on day one and breaks quietly within a month.

A pattern we've noticed: the second website we build for a returning client is almost always faster than the first, even with the same scope. The client has already learned what a fast approval looks like, already has a rough sense of the words they want to use, and already trusts the process enough not to second-guess every choice. First-time clients aren't slower because they're worse at this, they're slower because nobody's shown them what fast actually requires from their side.

There's also a difference between a website that's done and a website that's launched. Done means every page works. Launched means someone actually pointed the domain at it and told customers it exists. We've seen technically finished sites sit unlaunched for weeks because nobody wanted to be the one to say "go live," which is really just the approval problem showing up one more time, right at the finish line.