If you are searching for how long it takes to build a website, you are really asking two different questions: how long it should take, and how long it will take your project, with your content, your decision speed, and your feature list. The honest short answer: a simple business site can go live in three to four weeks, a proper custom build usually takes eight to twelve, and anything with eCommerce, customer portals, or third-party integrations lands between twelve and twenty-four. This guide is written for business owners planning a website in 2026. It breaks down where every one of those weeks goes, what derails projects most often, and how to keep yours on schedule — so you can plan around a real timeline instead of a sales pitch.
How Long Does It Take to Build a Website? Timelines by Project Type
There is no single answer, because “a website” covers everything from a one-page brochure to a full customer portal. What matters is which category your project falls into. These are realistic calendar ranges — not best-case promises — based on how projects actually run when an agency and a client each have other work on their plates:
- Landing page or one-pager: 2–4 weeks. A single page with a clear offer, a contact form, and basic analytics. Custom-designed, not a template, but no blog, no logins, no integrations beyond a form.
- Brochure business site (5–15 pages): 4–8 weeks. The classic company website: home, services, about, team, contact, maybe a small blog. Custom design, mobile-responsive, built on WordPress or a modern stack so your team can update it.
- Custom business website (20–50 pages, blog, integrations): 8–12 weeks. Multiple service areas, a content hub, CRM or email-marketing integrations, custom templates per section, and real SEO groundwork. This is the sweet spot for most established businesses rebuilding their web presence.
- eCommerce store: 12–16 weeks. Product catalog setup, payment gateways, shipping rules, tax configuration, email flows, and the testing that money-handling software demands. The design work is only a third of it.
- Custom portal or web application: 16–24+ weeks. Client dashboards, booking systems, memberships, custom workflows. At this point you are building software with a website on top of it, and the timeline behaves like software.
Notice the unit: calendar weeks, not effort weeks. A project that takes 80 hours of design work does not finish in two weeks if your designer is also handling three other clients and you take five business days to review each round. This is the single biggest gap between the estimate in a proposal and the date on your calendar. When you are vetting a web development agency, ask whether their timeline is in calendar weeks with your review cycles included — an honest agency will say yes and show you where your weeks go.
The Five Phases Every Website Project Goes Through
Whatever the project size, the work follows the same five phases. They overlap — a good team starts design while discovery wraps up, and development begins on approved templates before every page is designed — but nothing is truly finished until each phase is done. Here is where the weeks go.
1. Discovery and planning (1–2 weeks)
This is the unglamorous foundation: stakeholder interviews, a sitemap, technical requirements, and agreement on what success looks like. Skipping it is the most expensive shortcut in web development. A one-week discovery that surfaces “we also need the site in two languages” or “the CRM has to push data both ways” saves you from a four-week surprise later. Deliverables are usually a sitemap, a technical brief, and a content inventory — a list of every page, what it must say, and who writes it.
2. Design: from wireframes to final UI (2–4 weeks)
Wireframes (the skeleton: layout and priority of content on each template) come first, then visual design. A brochure site typically needs three to six unique templates — homepage, interior page, service page, blog index, blog article, contact — and each gets one to two revision rounds. Design is where taste enters the process, so it is also where timelines stretch: two rounds of structured feedback take a week; five rounds of “can we try another direction” take a month. The agencies that finish on time put the number of revision rounds in the contract and charge for extras.
3. Content: copy, imagery, and legal pages (1–3 weeks)
Content runs in parallel with design and development, but it is the phase most clients underestimate. A 20-page site needs roughly 10,000–15,000 words of finished copy, plus team photos, project imagery, testimonials, and legal pages. Professional copywriting takes time; writing it yourself takes longer than you think, usually evenings you do not have. We will say this plainly because it decides more launch dates than any technical factor: content is the number one reason website projects miss their deadlines. Start writing the day the project kicks off, not the day development finishes.
4. Development: building, integrations, and CMS setup (3–8 weeks)
This is where designs become a working site: front-end build, CMS configuration (WordPress, or a headless setup), custom functionality, and integrations with your CRM, email platform, analytics, and payment systems. The range is wide because complexity lives here. A brochure site on a solid theme framework is on the short end; custom post types, multilingual setups, API integrations, and eCommerce logic push you to the long end. Good development also includes the invisible work: speed optimization, mobile testing across real devices, accessibility basics, and SEO foundations like proper heading structure, meta templates, and redirects from the old site.
5. Testing, launch, and handover (1–2 weeks)
Quality assurance, content loading and formatting checks, cross-browser and cross-device testing, performance validation, and the launch sequence itself: DNS changes, SSL, redirects, analytics verification, and search-console setup. Then handover — training your team on the CMS and documenting how to do the things you will do every month. Rushed launches skip this phase and pay for it in broken forms discovered by customers, missing redirects that tank rankings, and a team afraid to touch the CMS. Budget the two weeks. It is the cheapest insurance on the project.
What Delays Website Projects Most
Ask any agency what pushes projects past their estimates and you will hear the same five culprits. None of them are technical — they are all organizational, which means you have more control over them than you think.
- Content gaps. The design is approved, development is done, and the site sits on a staging server for six weeks waiting for the “About” page copy and team photos. This alone accounts for more delays than every other cause combined.
- Feedback loops with no decision-maker. Five stakeholders review the homepage, each leaves contradictory comments, and nobody has the authority to resolve them. Every design round that should take three days takes three weeks.
- Scope creep. “Just one more page” said twelve times is a second project. Each addition seems small, but design, build, content, and testing multiply across all of them. Mid-project additions should be priced and scheduled, not absorbed.
- Third-party dependencies. Payment gateway approvals, CRM API access, ERP documentation, DNS transfers, hosting migrations. These live outside your agency’s control and routinely take two to four weeks longer than anyone assumes. Start them in week one.
- Late stakeholder involvement. The CEO who sees the site for the first time at launch review and asks for a redesign. Get every person with veto power into the discovery phase, or accept that their feedback will arrive at the most expensive possible moment.
From Our Experience: Timeline Realities Nobody Puts in the Proposal
After years of building business websites, a few patterns repeat so reliably that we now say them out loud in the first meeting. Consider this the fine print, written large.
Proposals are written in effort-weeks; calendars run in real weeks. “Eight weeks” in a proposal usually means eight weeks of production time, not eight weeks from signature to launch. Your review cycles, your holidays, your team’s availability — those are real weeks too, and a good estimate includes them. When a timeline looks suspiciously fast, it is usually because the client’s weeks were left out of the math.
Content is the bottleneck nine times out of ten. We said it above and we will say it again, because it is the one warning clients consistently ignore. If you want one lever that shortens your project more than any other, it is this: have your copy and photography ready before development starts. Agencies can build around placeholder text, but every week of waiting for real content is a week the site cannot be properly tested, reviewed, or launched.
Feedback is cheap in week two and expensive in week nine. Changing a headline in a wireframe takes minutes. Changing it after development means rebuilding templates, retesting pages, and sometimes reworking integrations that referenced the old structure. This is why structured, decisive feedback early is worth more than perfection late. The most expensive sentence in web projects is “we’ll figure out the content later” — the second most expensive is “can we just change the whole homepage” in the final week.
Never launch on a Friday. It sounds like superstition until you have watched a DNS propagation issue sit unresolved over a weekend while customers hit an error page. Launch Tuesday through Thursday, with the full team available the next day. This is a small discipline that prevents the worst kind of delay: the public one.
Know when rushing is the wrong call. There are legitimate reasons to move fast — a product launch, a seasonal window, a rebrand reveal. But compressing a timeline by skipping performance work, accessibility, or SEO foundations does not save time; it borrows it at high interest. A site that loads slowly fails Google’s Core Web Vitals thresholds, and fixing speed on a finished site costs far more than building it in. If the deadline is immovable, cut scope, not quality: launch the essential pages properly and phase the rest.
How to Shrink Your Website Timeline Without Cutting Corners
You cannot negotiate with reality, but you can remove the friction that makes reality slow. These are the five moves that actually work:
- Freeze the scope, phase the launch. Define exactly what ships on day one and park everything else in a phase-two list. A focused 8-week launch beats a bloated 20-week project that tries to do everything and does none of it well.
- Appoint one decision-maker. Collect input from everyone, but give one person the authority to resolve conflicts and approve rounds. This single change does more for timelines than any process improvement we have seen.
- Write content alongside design, not after it. Start copy in week one. Hire a copywriter if your team cannot spare the hours — it is consistently the highest-ROI line item on a website project.
- Timebox feedback to 48–72 hours. Agree up front that each review round gets three business days. Slow feedback is the silent timeline killer: nobody notices it happening, but it adds a month to the calendar without anyone making a single decision.
- Book the boring logistics early. Hosting access, domain transfers, DNS, SSL certificates, payment gateway accounts, CRM API keys — request all of it in week one. Third-party approvals are the delay you cannot sprint through, so start the clock immediately.
If you are planning a build, our web development services page covers how we scope and schedule projects — and the honest version of this same conversation is the first thing that happens on a discovery call.
Frequently Asked Questions
How long does it take to build a simple business website?
A simple brochure site — roughly 5 to 15 pages with custom design — typically takes 4 to 8 weeks from kickoff to launch. The fastest realistic path is a one-page landing site, which can go live in 2 to 4 weeks. In both cases, having your copy and images ready before the project starts is what separates the short end of the range from the long end.
How long does it take to build a custom website from scratch?
A fully custom business website — unique design, 20 to 50 pages, blog, and integrations with your CRM or marketing tools — usually takes 8 to 12 weeks. Add eCommerce and you are looking at 12 to 16 weeks; add customer portals, booking systems, or complex workflows and the range becomes 16 to 24 weeks or more, because at that point you are building software.
What is the fastest way to get a business website online?
Launch in phases. Ship a strong landing page or a tight 5-page site first — that can be live in 3 to 4 weeks — then expand with the blog, service pages, and integrations in phase two. This gets you collecting leads and ranking in search months earlier than waiting for a perfect full site, and it de-risks the project because feedback from the real world shapes phase two.
Why do most website projects take longer than estimated?
Three reasons cover the vast majority of overruns: unfinished content (copy and photography arriving weeks late), slow or conflicting feedback (no single decision-maker, revision rounds stretching for weeks), and scope creep (features added mid-project without adjusting the schedule). Third-party dependencies — payment gateways, CRM access, DNS transfers — are the fourth. Almost none of the delay is technical; it is organizational.
Can a website be built in one week?
A basic page can be assembled in a week if the design is templated, the copy is finished, and there are no integrations — but that is assembly, not a proper build. Anything involving custom design, real content strategy, testing, and SEO foundations cannot be done well in seven days. Be wary of anyone who promises it can: the corners being cut are the ones you will pay to fix later.
So, how long does it take to build a website? Long enough to do properly, and shorter than you fear if you control the things that actually cause delays: content readiness, decisive feedback, frozen scope, and early logistics. Get those four right and an 8-to-12-week project finishes in 8 to 12 weeks. Get them wrong and the same project finishes whenever it finishes. If you are planning a build and want an honest timeline for your specific scope, talk to us — the first thing we will do is tell you which end of the range you are on, and why.