"How long will it take?" is usually the second question we get after "how much will it cost?" It is a fair thing to ask, and it deserves an honest answer rather than a salesy "a few weeks" that quietly turns into three months. The truth is that a website build timeline depends far more on decisions and behaviour than on code. The technical work is fairly predictable. What is unpredictable is how quickly content gets written, how fast feedback comes back, and whether the scope stays put or keeps growing.
This article gives you real week ranges by site type, walks through the phases so you can see where time actually goes, and is candid about what causes delays and how to avoid them.
Realistic timelines by site type
Every project is different, but after enough builds you start to see patterns. Here are the ranges we would quote for a well-run project where the client is responsive and the scope is agreed up front.
Landing page: 1 to 2 weeks
A single, focused page for a campaign or one service is the fastest thing you can build. If the copy and images are ready, a designer and developer can turn a polished, conversion-focused landing page around in a week to ten days. Add tracking, A/B test variants, or bespoke animation and you are looking at closer to two weeks. The main reason landing pages slip is not the build; it is waiting for the offer, the headline, and the imagery to be finalised.
Brochure or small business site: 3 to 6 weeks
A typical small business website of five to ten pages, home, about, services, a few service detail pages, contact, sits in the three to six week range. That assumes a reasonably clear brief, a template or lightly customised design, and content that is either supplied or written to a tight schedule. Push into custom design with lots of bespoke sections and photography, and the upper end of that range becomes the norm.
WordPress site with custom design: 6 to 10 weeks
Once you want a properly bespoke design on WordPress, with custom page templates, a blog, editable content blocks, and integrations like a booking system or a newsletter tool, you are in the six to ten week bracket. WordPress is quick to stand up but slow to make genuinely custom and maintainable. Most of the extra time goes into design iterations and building flexible, editor-friendly components rather than one-off pages.
E-commerce site: 8 to 16 weeks
Online shops are a different animal. Even a mid-sized store has product data, categories, variants, payment and shipping configuration, tax rules, stock management, and often an integration with an accounting or fulfilment system. Realistically that is eight to sixteen weeks, and the product data alone frequently becomes the bottleneck. A store with a thousand SKUs, inconsistent photography, and no clean spreadsheet of descriptions can add weeks that have nothing to do with development.
Custom web application or bespoke build: 3 to 6 months plus
If you are building something with real logic, a customer portal, a booking platform, a custom CRM or ERP, a members' area with permissions, then you have left "website" territory and entered software. These are measured in months, not weeks, and they are usually built in stages so you get a usable first version early and add to it. Anyone quoting you a fortnight for genuine bespoke software is not being straight with you.
The phases of a build
Understanding where the weeks go helps you see why the ranges above look as they do, and where you personally can speed things up.
Discovery and planning (roughly 10-20% of the timeline)
Good projects start with a conversation, not a design. Discovery is where we work out what the site needs to do, who it is for, what pages and features are in scope, and what "success" looks like. For a small site this might be a couple of meetings and a short document. For an e-commerce or custom build it is a proper requirements exercise. Time spent here is repaid many times over later, because most expensive delays come from things nobody agreed at the start.
Design (roughly 20-30%)
Design usually runs in two parts: the layout and structure (wireframes) and then the visual design. This is where feedback speed matters most. A round of design feedback that takes you five days instead of one adds up quickly across a home page and several templates. We typically design the key pages, agree the visual language, then apply it, rather than designing every page from scratch.
Build and development (roughly 30-40%)
This is the part clients imagine takes the longest, and often it is not. With a clear design and organised content, front-end build moves quickly. Development time expands when there are integrations, custom functionality, or lots of one-off page layouts. At NetTrackers we build mobile-first and SEO-ready from the first line of code, so performance and structure are baked in rather than retrofitted, which saves time later.
Content population (variable, and often the real bottleneck)
Someone has to write the words, source the images, and load it all in. If the client is writing their own copy alongside a day job, this is where projects stall for weeks. We are honest about this up front: the fastest builds are the ones where content is ready early or where you ask us to write it.
Testing and quality assurance (roughly 10%)
Before launch we test across browsers and devices, check forms and links, run through the site on a real phone, and check load speed and accessibility basics. Cutting this corner to hit a date is a false economy; you just move the problems to after launch when they are more visible and more embarrassing.
Launch and handover (a few days)
Going live is the smallest phase but needs care: DNS changes, redirects from old URLs so you do not lose search rankings, final analytics checks, and a handover so you know how to edit your own site. We usually keep a close eye on the first few days for anything that only shows up under real traffic.
What actually causes delays
Almost every overrun traces back to one of three things, and none of them are the code.
Content that is not ready
This is the single biggest cause of slipped launches. Design and build can only go so far around placeholder text before real content is needed. If you can have your copy, logos, product data, and images sorted before the build starts, you remove weeks of waiting. If you cannot, decide early to have your agency write it.
Slow or scattered feedback
A build has natural handover points where the project waits on your sign-off. If feedback takes a week each time, and comes from four different people who disagree with each other, the timeline stretches. The fix is simple: nominate one decision-maker, agree to turn feedback around within a day or two, and give it all in one go rather than in dribs and drabs.
Scope creep
"While we're at it, can we also add a booking system?" Every mid-build addition is reasonable on its own, but each one resets part of the plan. Scope creep is not wrong, sometimes a new idea genuinely is worth it, but it should be a conscious decision with an honest note about what it does to the date, not an assumption that everything still lands on the original day.
How to make your website build go faster
You have more control over the timeline than you might think.
Get your content ready before the build starts, or delegate it entirely. Appoint one person to give feedback and empower them to decide. Agree the scope in writing and treat additions as deliberate trade-offs. Say yes to a template-based or component-based approach if speed matters more than a fully bespoke look. And be reachable during the build; a project where the client answers questions the same day moves at twice the pace of one where every query waits.
The uncomfortable flip side: rushing a build to hit an arbitrary date, a trade show, a funding round, usually produces a site with rough edges you then live with for years. If the deadline is real, tell your agency early so the scope can be shaped to fit it, rather than squeezing full scope into half the time.
Where NetTrackers fits
We build fast, mobile-first websites that are SEO-ready from the first line of code, and we are straight with you about timelines rather than telling you what you want to hear. Our web design and development team runs projects in clear phases so you always know what happens next and what we need from you. Because we are one team with one strategy, design, build, content, and SEO are not being juggled between three different suppliers, which is where most delays hide.
Everything is fixed-price and month-to-month, with no contracts, so you are never locked in. Book a free strategy call and we will give you an honest timeline for your specific project, or grab a free website review to see where your current site stands.
Frequently asked questions
Can a website be built in a week?
A single landing page with ready content, yes. A full brochure site, realistically no, not if you want it done properly. Anyone promising a full custom site in a week is either using a rigid template or planning to cut corners you will notice later.
What slows down a website build the most?
Content that is not ready and slow feedback. Together they account for most overruns. The build itself is usually the predictable part.
Do I need my content ready before we start?
It helps enormously. If it is ready, the build flies. If it is not, decide early whether you or the agency will produce it, so it does not become a surprise bottleneck.
Is a faster build a worse website?
Not inherently. A well-scoped, well-organised project is fast because it is efficient, not because it is cutting corners. Problems come from rushing full scope into an unrealistic deadline, not from good planning.