How long does it take
to build a website?

“How long will my website take?” is a fair question with an unfair answer, because “a website” covers everything from a one-page launch to a hundred-page platform with logins and dashboards. A landing page and an online store are both “websites” the way a bicycle and a lorry are both “vehicles.” So let’s make the answer useful: real timelines by type, the phases underneath them, the delays that catch people out, and the levers you can pull to launch faster without cutting corners.

Key takeaways

• A single landing page ships in roughly 1 week, a small business site (5 to 10 pages) in 2 to 4 weeks, a marketing site with a CMS or blog in 4 to 8 weeks, and an e-commerce store or custom web app in 2 to 4 months.
• The build itself is rarely the bottleneck. Content that is not written, feedback stuck in an inbox, and mid-project scope changes cause most delays.
• “Launch date” and “first time you see real work” are different numbers. With a lean team you should see a first delivery within a couple of business days, even on a project that takes weeks to finish.
• Integrations (payments, CRM, booking, custom logic) add time in a way that page count does not. Ten simple pages are faster than three pages wired into three systems.
• You control the fastest lever: content ready, one named decision-maker, quick feedback, locked scope. Do those four and you cut weeks off any timeline.
• Speed and quality are not opposites. Fast should mean nothing sits in a queue, not that testing got skipped.

Website timelines by type

Here is what each kind of project typically takes, assuming content and feedback move at a reasonable pace. Ranges are in weeks so you can plan around them rather than guess.

Site type	Typical timeline	What’s happening
One-page landing page	3 days to 1 week	One focused message, one goal, usually one long scrolling page. Design and build move quickly when copy and brand assets are ready.
Small business site (5–10 pages)	2–4 weeks	Home, about, services, contact and a few supporting pages. Standard structure, light custom design, no complex integrations.
Marketing site with CMS/blog	4–8 weeks	Everything above plus a content system so your team can publish posts, case studies or resources without a developer. Templates and editor setup add time.
E-commerce store	6–12 weeks	Product catalogue, cart, checkout, payments, shipping and tax rules. More moving parts, and more testing before you can safely take money.
Custom web app	3–6 months	Logins, dashboards, user roles, custom logic. This is software, not a brochure site, and it is measured in months.

Two things to hold onto. First, these assume content and feedback move at a reasonable pace. More on why that matters further down. Second, “launch date” and “first time you see real work” are different numbers. With a lean team you should see a first delivery within a couple of business days of kickoff, even on a project that takes weeks to finish.

What actually determines the timeline

Five factors move the clock more than anything else, and only one of them is about writing code. Understand these and you can predict a timeline better than most quotes will.

Scope

Pages, features, and how much is custom versus standard. Five pages is not fifty. But scope is not just page count. A three-page site that pulls live data, syncs to a CRM and takes payments is more work than a twenty-page brochure site. When you scope a project, separate what genuinely needs to be custom from what can reuse a proven pattern. The custom parts drive the timeline; the standard parts rarely do.

Content readiness

Whether your copy, images, logos and brand guidelines already exist, or need creating. If you need words written, photos taken and graphics designed, that is real work with its own timeline sitting in front of the build. A team that also handles copywriting, graphic design and video can absorb that in parallel instead of leaving you to source it from separate freelancers who never talk to each other. Content is the input the build runs on, so its readiness sets the pace.

Revision rounds

How many rounds of feedback each stage takes, and how sharp each one is. Two tight rounds move fast. Five vague rounds of “make it pop” stretch a two-week job into a month. The number of rounds matters less than how specific and how quick each one is. Clear notes returned in a day keep momentum; open-ended feedback returned in a week does not.

Integrations

Payments, CRM, booking systems, email tools, custom automations. Each connection is a small project of its own: setup, testing and edge cases. Wiring your site into a HubSpot CRM, a booking calendar and an email flow adds days even when the page count is tiny. This is exactly where “just a simple site” quietly turns into a bigger build, so it pays to name your integrations up front.

Approvals and decision-makers

How quickly someone with authority says yes. A single named decision-maker who can approve on the spot beats a committee that meets every second Tuesday. Approvals sitting in a queue are the most common invisible delay on any project, and they cost nothing to fix once you spot them.

Notice that only one of those five is really about the building. Which brings us to the uncomfortable truth further down.

Phase by phase: what happens each week

Whatever the size, a good build moves through the same five phases. Bigger projects spend longer in each, but the order rarely changes.

Week 0: Discovery and planning

Goals, audience, brand, examples you like, and the sitemap. Short and sharp, no forty-page brief required. This is where the structure gets agreed so nothing has to be rebuilt later. Skipping discovery to “save time” is the classic false economy: it just moves the delay downstream, where it costs more to fix. Expect this to take days, not weeks, on a normal site.

Design

Wireframes first (the structure and layout), then high-fidelity screens (the polish, colour, type and imagery). Most revision rounds happen here, so this is where fast, specific feedback pays off most. Getting the design right on screen is far cheaper than changing it once it is built. If you want a sense of how this stage works on its own, our UI/UX design process covers it. On a small site this is days; on a larger one, a week or two.

Build

Turning approved designs into a working, responsive site that behaves on phones, tablets and desktops. On a well-run project you are reviewing real pages during this phase, not waiting for one big reveal at the end. This is also when integrations get wired in and tested, which is why sites with payments or a CRM connection spend longer here than page count alone would suggest.

QA and review

Testing across devices and browsers, checking every link and form, tightening copy, fixing the small stuff, and confirming speed and accessibility basics. With unlimited revisions the question is not “can we change it” but “how fast does your feedback come back.” Rushing this phase is where quality problems hide, so it earns its days.

Launch and beyond

Going live, pointing the domain, checking analytics and forms, and watching the first real traffic. On a proper website development engagement, launch is the start, not the finish. The site keeps getting updates after go-live, and the same connected team can grow it with SEO and ads and automate the busywork running behind it. It is one relationship, not a handoff.

Why content and feedback are usually the real bottleneck

Here is the part most agencies will not say out loud: on the majority of projects, the slowest part is not the developers. It is the client-side inputs.

Not out of any fault. It is simply where the bottleneck lives. The build stalls waiting for copy that was never written, product photos that were not sent, feedback stuck in someone’s inbox, or a change of direction three weeks in that undoes finished work. A capable team can move quickly. A project can only move as fast as the decisions and materials feeding it.

This is also where juggling several separate vendors hurts you most. When your designer, developer, copywriter and marketer are different freelancers on different tools, every handoff becomes a new waiting line, and nobody owns the whole timeline. That is the exact pain of juggling five vendors who never talk. One connected team on a flat monthly retainer removes those seams: the people writing your copy, designing the pages and building the site are already talking to each other, so work does not sit idle between handoffs. The timeline tightens because the gaps disappear.

How to speed it up without cutting quality

The good news is that the fastest lever is almost entirely in your control, and none of it involves rushing the work:

• Have your content ready before kickoff, or hire the team to create it, so words and images are never the thing everyone is waiting on.
• Name one decision-maker up front, so approvals do not sit in committee for a week at a time.
• Batch your feedback into clear, specific notes and turn them around within a day or two.
• Lock the scope before kickoff and resist “one more thing” mid-build. Park new ideas for a phase two so they do not stall phase one.
• Choose the right tool for the job. A no-code build on Webflow or WordPress can be faster than fully custom code when it fits your needs. See Webflow vs WordPress and no-code vs custom development to weigh the trade-offs before you commit.
• Start with a lean first version and expand. A focused launch that actually goes live beats a sprawling all-at-once build that slips for months.

Do those, and you will cut your timeline more than any developer ever could. And note what is not on the list: skipping testing, ignoring mobile, or shipping something half-checked. “Fast” should mean nothing sits in a queue and you see progress quickly, not that quality got traded away. Those are very different things, and only one of them is worth wanting.

Two real timelines

The numbers below are illustrative, not a quote. They show how the same principles play out at two very different sizes, and where the time actually goes.

A one-week landing page (illustrative)

• Day 1: Kickoff call, goals and one clear conversion target agreed. You send existing brand assets and rough copy.
• Day 2: First design of the full page delivered for review.
• Day 3: One round of specific feedback returned the same day; revisions applied.
• Days 4 to 5: Build into a responsive, fast-loading page; forms and tracking wired in.
• Day 6: QA across devices, final copy polish, sign-off.
• Day 7: Live.

Total: about a week, because the scope was tight, the copy was ready, and feedback came back the same day. Change any one of those and the week stretches.

A six-week business site (illustrative)

• Week 1: Discovery, sitemap and a content plan for eight pages agreed.
• Week 2: Wireframes and homepage design; first round of feedback.
• Week 3: High-fidelity design across the page types; second round of feedback and sign-off.
• Week 4: Build of all pages, responsive behaviour, and a HubSpot contact form.
• Week 5: Content loaded, SEO basics in place, and the blog or CMS set up so your team can publish.
• Week 6: QA across devices, fixes, final review and launch.

Total: about six weeks, with you reviewing real work from week two onward rather than waiting for a single reveal at the end. If content or approvals slip, week six becomes week eight, which is exactly the pattern from the section above.

When it’s not a website at all

If your project has logins, dashboards, user accounts or custom logic, you are not building a website: you are building an app, and the timeline shifts from weeks to months. That is normal; it is simply a different kind of work with more testing and more moving parts. See how much a custom web app costs and our custom software approach for what that actually involves. And if you are on Wix or Squarespace and running into their ceilings, when to leave Wix or Squarespace covers the signals that it is time to move to something you can grow into.

The bottom line

A landing page in about a week. A small business site in a few weeks. A marketing site or store in a month or two. An app in longer. But the honest headline is this: the timeline is set less by how fast a team can build and more by how ready you are, with content in hand, decisions quick and scope locked.

Want a real timeline for your site instead of a range? Book a call and tell us what you need. We will give you a scoped schedule you can plan around, with the first delivery landing within a couple of business days, not a couple of months. Prefer to see what a flat monthly retainer covers first? See pricing.