How long does it take to build a website?

Expect 2 to 4 weeks for a brochure website, 4 to 8 weeks for an e-commerce site, and a minimum of 2 to 4 months for a web app or SaaS product. These are honest ranges — not sales pitches. And in the vast majority of projects that run late, the root cause is not technical. It's editorial and organisational. Here's everything broken down.

Real timelines by project type

The type of site is the primary factor driving the timeline. Here's what we consistently see in practice:

Brochure website (5 to 15 pages): 2 to 4 weeks. This is the fastest type of project to deliver — provided content is ready before development begins. A well-scoped brochure site with copy and visuals supplied at kickoff can be live in under three weeks.
E-commerce site: 4 to 8 weeks. Product catalogue management, shipping rules, payment modules, abandoned cart flows, return policies — every detail must be decided before a line of code is written. A 50-product catalogue takes less time than a 500-product one.
Web app or SaaS: 2 to 4 months, sometimes more depending on functional scope. Discovery alone can take two to three weeks, because you need to model data, define user roles, and anticipate edge cases. Skipping that phase always costs more later.
Redesign of an existing site: comparable to a new build, with an added constraint — migrating existing content and preserving acquired SEO rankings, which typically adds a week to the schedule.

These timelines include design, development, revision rounds and testing — not just pure coding time.

Phase breakdown: what actually takes time at each step

A well-run web project always goes through the same phases. Skipping or rushing them is a guaranteed way to create problems at the end.

Discovery and brief (2 to 5 days): defining the site's objectives, required pages, features, editorial tone, and target audience. The more precise this phase is, the faster everything else goes. A vague brief generates back-and-forth across every subsequent phase.
Sitemap and wireframes (3 to 5 days): structuring the content before designing it. We decide who sees what, in what order, with what information hierarchy. This step prevents having to redo the design twice.
UI design (1 to 2 weeks): high-fidelity mockups, colour palette, typography, components. One round of feedback is enough if the brief is solid. Two rounds already means a week lost.
Development and integration (1 to 3 weeks depending on size): the longest phase on complex projects. It includes integrating the mockups, developing features, and connecting third-party tools (CRM, analytics, payment, forms).
SEO copywriting and content (1 to 2 weeks, often run in parallel): if copy isn't ready before development, this phase delays everything else. You cannot test a page without its final content.
QA and testing (3 to 5 days): cross-browser and cross-device testing, form and link checks, performance audits, mobile behaviour verification. Non-negotiable — shipping without QA means shipping bugs to production.
Launch (1 to 2 days): deployment, DNS configuration, basic SEO checks (canonical tags, sitemap, Search Console). DNS propagation takes anywhere from a few hours to 48 hours depending on the registrar.

What actually causes delays (without exception)

We've seen projects estimated at 3 weeks stretch to 3 months. Here's why, in order of frequency:

Content provided by the client — by far the number one cause of delays. Unwritten copy, missing photos, low-resolution logos, testimonials never collected: if you don't have your content ready before kickoff, the project stops and waits. This isn't about bad intentions — it's systemic. And it's entirely preventable.
Unconsolidated feedback rounds. When multiple people give feedback separately — the CEO says one thing, the marketing lead says another — each correction round easily costs 3 to 5 days. One decision-maker on the client side is non-negotiable if you want to hold a schedule.
Features added mid-project. “Actually, we'd also like a members area“ halfway through development: the classic that shifts everything. Every out-of-scope addition pushes the delivery date back — sometimes by as much as the original project. Scope must be frozen before coding begins.
Unexpected third-party integrations. Connecting a CRM, a booking tool, a non-standard payment API — each third-party integration can take 2 to 5 days depending on documentation quality and API limitations. Discovering them at the end of a project is catastrophic.
Missing access credentials. Retrieving hosting login details, the domain transfer code, Google Search Console access, Analytics account access, third-party tool credentials — if these aren't requested at kickoff, a simple administrative formality can block the launch for several days.

The “website in 48 hours“ trap

Some providers offer sites in 48 hours, 72 hours, or “within a week.“ It's technically possible — with a no-code builder, a generic template, and zero real customisation. What you get: a site that looks like thousands of others, with no SEO strategy, no performance optimisation, and often no serious mobile adaptation.

The real danger isn't the timeline — it's what gets sacrificed to meet it. A rushed site costs more to fix than to build properly from the start, in time, in lost SEO, and in credibility with your visitors. On a custom website build, speed of execution should never come at the expense of quality.

How to move faster as a client: concrete levers

You have a direct and often underestimated lever over your project timeline. Here's what actually makes a difference:

Prepare your content before kickoff — not in parallel, before. Copy for your main pages, rights-cleared or in-house photos, your logo in SVG or high-resolution PNG, client testimonials. A shared Drive folder with everything in it on day one often saves a full week.
Designate a single decision-maker for sign-offs. Not a committee, not “I need to check with my business partner“ at every stage. One person with final say who responds within 24 hours — this is the single most impactful human factor on the schedule.
Consolidate all your feedback in one document, once per phase. No drip-feeding feedback across multiple messages. No verbal notes in a meeting followed by more emails two days later. One document, once, per phase — and we move forward.
Share access credentials at kickoff: hosting provider, domain registrar, Google Search Console, Analytics account, any third-party tools to be integrated. Immediately, not at the last minute.
Approve quickly. Client response times are often the main bottleneck. If a mockup sits waiting for approval for 5 days, the project waits 5 days. That's not a criticism — it's a reality to anticipate in how you organise your side of things.

At KELAP, we send a structured brief before starting every project, with a precise list of what we need and by when. That's how we consistently deliver on time without unpleasant surprises on either side.

The takeaway

A website takes time not because the code is complicated, but because it's a collaborative project with decision, validation and content production phases that depend on both sides. We have the technical side covered. The part that depends on you — content, fast decisions, access credentials — is what separates a 3-week project from a 3-month one.

If you want to understand in more detail what building a website for your business actually involves, we've broken down the key steps in a dedicated article. And if you're ready to get started, tell us about your project — we'll give you an honest estimate and a realistic schedule from the very first conversation.