How long does a
website take?

Every client asks this question. The honest answer is: it depends on two things — scope and how fast you can supply content and decisions. The code itself is rarely the constraint. What stretches timelines is waiting: waiting for copy, waiting for photos, waiting for someone to approve the draft.

Below are real ranges by project type, followed by the specific factors that compress or expand each one.

§ 01 — A landing page: 1–2 weeks

A single-page site focused on one offer — a service, a product, an event — can be live in a week when the content is ready. What "ready" means: you have your headline and supporting copy written or outlined, a logo and one or two images, and one person who can approve the final design without committee sign-off.

When those conditions are met, the build is fast. One focused page, one clear goal. The week stretches to two if there is a revision round on copy or if assets take a few days to gather. It stretches to four when content gathering becomes a separate project on its own.

§ 02 — A service business website: 3–6 weeks

A full service site — homepage, services pages, about, contact, and maybe a blog or portfolio — typically runs 3 to 6 weeks from kickoff to launch. The lower end assumes clear scope upfront, fast content turnaround, and one revision round. The upper end covers two revision rounds, content delays of a week or more, and any integrations like a contact form, booking link, or email list.

This is where most local businesses land. The site needs enough pages to answer the questions a prospective customer would ask, but it is not an application — there is no user login, no database, no real-time features.

§ 03 — A web application: 2–4 months

An application — something with user accounts, a database, business logic, and real-time features — takes longer because there is more to build and more ways for things to interact badly. Two months is realistic for a focused first version with one core workflow. Four months covers a more complete product with multiple user types, admin tools, and integrations.

Applications also have higher coordination cost: the spec needs to be clear before any code is written, and changes mid-build are expensive because code written for one data model often has to be rewritten for a different one. The brief matters more here than anywhere else.

§ 04 — What adds time

The following are the real causes of timeline slippage, in rough order of how often they appear:

• Content not ready at kickoff. If you start a project without your copy written, every week you spend gathering it is a week the build waits. The developer is ready; the site is waiting on text and images.
• Multiple decision-makers. Every extra person in the approval chain adds coordination overhead. One person reviewing a draft takes a day. Three people reviewing the same draft, coordinating feedback, and resolving disagreements takes a week.
• Scope added mid-build. "Can we also add a blog?" is a reasonable request — but if it is added two weeks into a five-week project, it extends the timeline by whatever it would have taken if scoped upfront. Changes after development starts cost more in time than changes decided before it begins.
• Revision rounds beyond the original agreement. One round of revisions is normal and expected. Two is workable. Three or more usually signals that the scope or the goals were not clear at the start.

§ 05 — What cuts time

Three things shorten web project timelines more than anything else:

• A written brief before kickoff. A brief does not need to be long. It needs to answer: what does the site need to do, who is it for, and what does success look like. One page of clear answers to those three questions saves a week of back-and-forth during the project.
• Content ready on day one. If you hand over your copy, logo, and images at the start, the developer can build without waiting. This alone can cut a 6-week project to 4 weeks.
• One approver. Name the person who makes the final call on design and copy. That person's response time is the project's heartbeat. If they are available within a day or two, projects move quickly. If they are available once a week, the project runs on their calendar.

§ 06 — How to get an accurate estimate

Ask for a milestone-based estimate, not just a final delivery date. A realistic project estimate looks like: discovery and kickoff in week one, design draft in week two, revision round in week three, development in weeks three and four, final review and launch in week five. That is not a guaranteed schedule — it is a map. If something is going to be late, you will see it in the milestones before it hits the launch date.

A developer who gives only a single end date with no intermediate checkpoints is either very confident or very optimistic. Both are worth probing before you sign.

The most reliable signal that a project will land on time is a developer who asks good questions at the start. Questions about who your customers are, what they need to do on the site, and what you define as done. Projects that start with that conversation almost always finish close to the estimate. Projects that start with "just make it look nice" almost never do.

If your site is already live and you are wondering whether it is doing its job, a Website Intelligence Audit answers that question with a specific fix plan — not a new build, just a clear picture of what is costing you leads and how to correct it.

Common questions

Is it really possible to build a website in 1–2 weeks?

Yes, for a focused landing page with clear goals and existing content. The condition is that you come to the project with your copy written or at least outlined, your images ready, and one person making decisions. When those three are true, a landing page can go live in a week. The timeline expands when any of those is missing.

Why do web agencies quote 3–6 months for a website?

Larger agencies have design approval stages, project manager layers, and queues of other clients. The 3–6 month range often includes discovery workshops, rounds of stakeholder feedback, and time waiting in their schedule. Smaller teams with a clear brief can often do the same work in 3–6 weeks because they eliminate the internal process overhead.

What part of building a website takes the longest?

Content. The code for a typical service business site takes 1–2 weeks. Waiting for the client to finalize copy, gather photos, and approve drafts can take 4–8 weeks more. The bottleneck is almost never technical — it is content preparation and decision-making speed on the client side.

How can I speed up the timeline on my website project?

Three things shorten timelines more than anything else: write a clear brief before the project starts, gather your content (copy, photos, logos) before the kickoff call, and name one person as the single approver. Every extra person in the approval chain adds days or weeks.

Should I ask for a timeline estimate before signing with a developer?

Yes — and ask for a milestone-based estimate, not just a final delivery date. A realistic estimate looks like: kickoff week 1, design draft week 2, revision round week 3, development weeks 3–4, launch week 5. If a developer gives only a single end date with no checkpoints, you have no way to know if the project is on track until it is late.