Full-time Available Part-time Available Book a slot
Process

How long does a website actually take to build?

Published 6 July 2026 · 5 min read · by Galib

The build is rarely the slow part. The slow parts are content and feedback. Here is a realistic timeline for three project sizes, and what makes them slip.

The short answer

Small business site: 2 to 3 weeks. Mid marketing site with several unique templates: 4 to 6 weeks. Large site or a store: 8 to 12 weeks. The clock effectively starts when the content is ready; a project waiting on copy can sit for months without a line of code being the reason.

Every project I run has the same four phases. The sizes differ; the shape does not.

What are the phases?

  • Discovery. Map the outcome, the pages, the must-haves, who edits it after. Usually one call plus a short brief.
  • Design. Layout and copy direction for every key page, reviewed and signed off before any build.
  • Build, SEO and speed. The actual development: templates, content, schema, image and font optimisation, a 90+ PageSpeed target from day one.
  • Launch and support. Migration with redirects mapped, a handoff walkthrough, a snag-list window.

How long is each phase?

For a typical mid-size site: discovery is a few days, design is about a week including one review round, build is two to three weeks, and launch week handles migration and final checks. Most of the calendar time that is not build is feedback: waiting on your review of the design, then your review of the staging site.

What actually causes delays?

  • Content that arrives late or in pieces. The biggest one by far. See the FAQ below.
  • Slow or scattered feedback. One consolidated round of notes moves fast; drip-fed changes over two weeks do not.
  • Scope growing mid-build. "Can we also add a booking system" in week three resets part of the timeline.
  • Third-party dependencies. Waiting on a merchant account, a domain transfer, an API key from another vendor.

Small, mid, large: week by week

Small business site (2 to 3 weeks): week 1, discovery and design sign-off; week 2, build; week 3, review, fixes and launch.

Mid marketing site (4 to 6 weeks): week 1, discovery and design; week 2, design sign-off and build start; weeks 3 to 4, build; week 5, staging review and revisions; week 6, launch and snag list.

Large site or store (8 to 12 weeks): weeks 1 to 2, discovery and full design; weeks 3 to 7, build in stages with interim reviews; weeks 8 to 9, catalogue or content load and QA; weeks 10 to 12, staging review, redirects, launch, post-launch tuning.

Can it be done faster?

Yes, within reason, if the content is final on day one, feedback comes back within a day, and the scope is locked. A small site can then land in a week to ten days. Compressing a mid or large project mostly means agreeing a smaller launch scope and a phase two.

What is the fastest realistic launch?

A single landing page with ready copy: a few days. A small brochure site with content ready: about a week. Anything described as "just a quick five-pager" is usually a two-to-three week project once real content and review rounds are counted, and that is the honest number I would quote.

In short

Key takeaways

  • Small site 2 to 3 weeks, mid site 4 to 6 weeks, large site or store 8 to 12 weeks.
  • The build is rarely the bottleneck; late content and slow feedback are.
  • Content close to final before a page is built saves a round of rework.
  • One consolidated round of feedback is far faster than drip-fed changes.
  • A hard deadline is easiest to hit when it is known on day one.
FAQ

Common follow-up questions

Can you build a website in a week?

A single landing page or a very small brochure site, yes, if the content is ready and the design is straightforward. A full multi-page business site in a week means cutting the review rounds, which usually shows.

What if I need it live by a specific date?

Tell me the date up front. If it is realistic we plan backward from it; if it is tight we agree what ships for launch and what follows in a phase two. A hard deadline is easier to hit when it is known on day one.

Why does content slow a project down?

Building around placeholder text and then swapping in real copy causes rework: layouts that fit lorem ipsum break with real headings and paragraphs. The build goes faster and cleaner when the copy is close to final before the page is built.

Do you work on more than one project at a time?

Yes, a small number in parallel, scheduled so each has dedicated build blocks. Your timeline accounts for that; it does not mean your project sits idle.

What happens after launch?

A short snag-list window for anything that surfaces in the first week, a handoff walkthrough, and then either ad-hoc support or a monthly maintenance plan.

Asadullah Al Galib
Asadullah Al Galib

WordPress and PHP developer. Ten years of shipping client sites on schedule, with a routine built to keep it that way.

See how the work runs →
Start a project

Working to a deadline?

Send me the scope and the date on Upwork and I'll tell you straight whether it fits, and what a phase one would look like if it doesn't. Usually within one business day.