How Long Does a Website Take to Build?

"How long will it take?" deserves a straighter answer than "it depends." The honest version: it depends on scope, but scope has typical shapes, and the delays that stretch projects are predictable enough to plan against. Here are the shapes.

The honest tiers

A focused small-business site, about two to four weeks of studio time. Five to ten pages, professional design and copy, a contact flow, launch checks. The Weca tier of work: one clear offer, one audience, done properly. The variable that moves this number most is not design; it is how quickly the client returns feedback.

A structured business or organizational site, about four to eight weeks. More pages, per-service depth, real content structure, integrations. This is where most of our cases live: enough surface area that content structure and navigation decisions carry their own weight.

A platform or product, from eight weeks upward, honestly scoped. Portals, dashboards, booking systems, anything with accounts or payments. The engineering is bounded; what makes these projects long is the decisions around the engineering, and pretending otherwise is how they get longer.

The one-week website exists: a single page or a tightly templated build. It answers the question "does this business exist online." It does not answer "why this business," which is the question every serious buyer asks. A week is a real option for a real need; it is a false economy for a business whose website is its main storefront.

What actually eats the calendar

Three delays account for nearly every blown deadline, and none of them are code:

• Copy arriving late. The single largest cause. Design can proceed with placeholder text, but launch cannot. The fix is contractual: writing included in scope, or a firm copy deadline before design starts. We put the words in scope precisely to delete this delay. see writing copy that converts.
• Decision latency. Each round of feedback that waits a week costs a week. Two focused review rounds beat six scattered ones; the schedule survives clients who batch their thinking and suffers the ones who trickle.
• Scope that grew quietly. The fourth page becomes nine; the contact form becomes a portal. Not dishonesty, enthusiasm. The protection is the change conversation: anything new goes on a list and is priced before it is built, not discovered at the invoice.

The studio-side schedule

For transparency, the phases and their honest proportions: discovery and definition take about a fifth of the calendar; design and copy together the largest share; build and quality assurance the remainder, with launch checks that are short but non-negotiable, the redesign checklist items exist because each one has, somewhere, cost someone a launch.

Communication rhythm is the hidden variable: a weekly fifteen-minute check-in, on schedule, beats a monthly deep-dive that reschedules twice. Projects do not drift in months; they drift in silent weeks.

The question behind the question

When a client asks "how long," the operational question is usually "when can I stop being embarrassed by the current site." Worth saying plainly: a staged launch beats a delayed perfect one. Ship the pages that carry the business the week they are ready; add depth in the weeks after. A live, honest, fast site outranks a launch date that keeps moving.

If the current site is the pressure, start with the audit, a written account of what is wrong, ranked, so the timeline and the fix are aimed at the actual problem rather than at the embarrassment.