If you have ever asked a web designer how long a website takes, you have probably had one of two experiences: either you got an unhelpful answer like “it depends”, or you got a suspiciously specific promise like “we can have it done in five days”. Both leave you none the wiser.
Here is the honest answer. A simple business website typically takes two to four weeks to build properly. A bigger site — one with online ordering, bookings, or lots of pages — usually takes six to twelve weeks. And the truth nobody tells you upfront is that the timeline rarely depends on the designer. It depends on you, the client.
This guide breaks down where those weeks actually go, what slows websites down, and how to keep your project moving — whether you work with Altus Web Solutions or anyone else.
The short answer: typical build times
Every project is different, but most business websites fall into one of four bands. Use these as rough guides, not guarantees:
- Simple brochure site (5–10 pages): 2–4 weeks. Homepage, about, services, contact — the basics, done well. This is the most common project for small businesses and trades.
- Content-rich or multi-service site (10–30 pages): 4–8 weeks. More pages, more photography, more decision-making. Think estate agents, clinics, training providers.
- E-commerce or booking sites: 6–12 weeks. Product catalogues, payment setup, delivery rules, testing every checkout path. This is where rushing genuinely costs money later.
- Custom builds with special features: 8–16 weeks. Member areas, dashboards, integrations with your existing systems. Proper scoping takes time on these — and it should.
Notice something important: the design itself is rarely the slowest part. A competent designer can lay out a homepage in a day. The weeks go on everything around the design. Which brings us to the real question.
Where the time actually goes
A website project has roughly six phases. Here is what each one involves, and why each one can stall.
1. Scoping and agreement (a few days)
This is the conversation before any work starts: what does the site need to do, how many pages, what content exists, what needs creating. Good scoping protects both sides. Projects that skip it — “just build something, we will figure it out as we go” — are the ones that run twice as long, because every week brings a new surprise that was never planned for.
Typical delay here: signing off the scope itself. You are busy running a business; reading a proposal is never urgent. Block half an hour, read it, approve it, and the project starts moving.
2. Content gathering (1–3 weeks — the most underestimated phase)
Text, photos, logos, prices, service descriptions, team bios. Almost every project bottleneck we have ever seen lives here. The design cannot be finished until the words are, because layout serves content, not the other way round.
Most delays in this phase are not anyone’s fault: you need to write your service descriptions, find a decent photo of your team, confirm your prices, decide what to say on the about page. It is real work, and it competes with running your business.
How to keep it moving: do not wait until the design is ready to start writing. Start the moment the project is agreed. We give every client a simple content checklist on day one — work through it in small chunks and you will never be the bottleneck.
3. Design (1–2 weeks)
With the scope agreed and content arriving, the designer produces the homepage concept and key page layouts. This is the fun part — and also where the project can drift. Endless rounds of “could we just try it in a slightly different blue” eat weeks and rarely improve the result.
How to keep it moving: limit yourself to two rounds of revisions. That sounds strict, but in practice it focuses the mind: you gather all your feedback in one go, the designer addresses it all, and you do one final polish. Projects with unlimited revisions almost always take longer and end up worse, because design by committee dilutes every decision.
4. Build and content loading (1–3 weeks)
The approved design gets turned into a working website: pages built, content loaded, contact forms wired up, mobile layouts checked, speed optimised. On simple sites this is quick; on shops and booking systems it takes longer because every path needs testing — a broken checkout costs you real orders on day one.
How to keep it moving: be available for quick questions. A five-minute answer from you can unblock a whole day of work. A three-day wait turns into a three-day delay, every time.
5. Testing and fixes (a few days to a week)
Every professional build should include a proper testing round: the site checked on phones and tablets, forms actually submitted, links followed, spelling read through. You get a preview link and a short list to verify: is this your correct phone number, your prices, your opening hours?
Typical delay here: the review round sitting in your inbox for two weeks. Schedule the review when you receive the link — treat it like any other appointment.
6. Launch (a day, with some admin around it)
Pointing the domain at the new site, submitting it to Google, setting up analytics. Technically quick, but it involves your domain registrar and sometimes your email setup, so having your login details to hand matters.
What actually slows websites down
Strip away the excuses and almost every late website is late for one of five reasons. Memorise this list and your project has a genuine advantage:
- Content arrives late. The number one cause, by a long way. Start writing on day one.
- Decisions by committee. Every extra person with approval rights multiplies the revision rounds. Nominate one decision-maker and let everyone else advise them.
- Scope creep. “Could we just add a small booking system too?” Mid-project additions reset the timeline. If it was not in the scope, park it for phase two.
- Unlimited revisions. Two rounds keeps things sharp. Open-ended revisions keep things open-ended.
- Disappearing for weeks. Designers cannot read your mind, and silence is not approval. A quick “looks good, carry on” keeps the momentum.
None of these are about how fast the designer works. They are about how the project is run — which is good news, because you control most of them.
How long does a website take at Altus?
We build every project on a clear four-level framework, so you know exactly what you are buying and roughly how long it takes:
- Level 1 — Starter site: the essentials, done properly. Typically two to three weeks from content to launch.
- Level 2 — Business site: more pages, more polish, built to win enquiries. Typically three to six weeks.
- Level 3 — E-commerce or booking: a shop or booking system that actually works. Typically six to ten weeks.
- Level 4 — Custom build: integrations, dashboards, the complex stuff. Scoped and quoted individually, typically eight weeks plus.
Every project comes with a firm fixed price once we understand what you need — agreed before we start, in writing, no surprises. And every timeline we quote assumes the content plan is followed: you hold up your end, we hold up ours.
The questions to ask any designer about timing
Before you commit to anyone, ask these three questions. The answers will tell you whether the timeline is real:
- “What do you need from me, and by when?” If they cannot answer this clearly, they have not thought about your project yet.
- “What happens if I am late with content?” An honest answer acknowledges your role. A designer who pretends content does not matter is selling you a template, not a service.
- “How many revision rounds are included?” Two to three is healthy. Unlimited sounds generous and usually means chaotic.
Frequently asked questions
Can a website be built in a week?
Technically, yes — a simple template site can be assembled quickly. But the content, the copywriting, the testing and the polish are what take the other three weeks, and skipping them is how businesses end up with sites that look fine and convert badly. If someone promises a full custom site in five days, ask what is being skipped.
Does a bigger budget mean a faster build?
Up to a point. Paying for priority scheduling and a dedicated designer shortens the queue, not the craft. The phases above still need to happen; money buys focus, not magic.
How long until Google shows my new website?
The site itself can be indexed within days of launch if it is submitted properly. Ranking well takes longer — weeks to months of consistent content and optimisation. Anyone promising first-page rankings on launch day is selling you something else entirely.
What if I need the site for a specific date?
Tell your designer the hard deadline at the very first meeting, not halfway through. Working backwards from a fixed date is completely normal — launching before a busy season, an event, a funding round — but it only works if the content arrives on schedule.
The bottom line
How long does it take to build a website in 2026? For most small businesses, two to four weeks of real project time — plus the calendar time your own content and decisions add on top. The projects that finish on schedule are not the ones with the fastest designers. They are the ones with the clearest scope, the quickest decisions, and content that arrives on time.
If you want a website built on a timeline you can trust, book a free 15-minute website audit with Altus Web Solutions. We will look at what you have now, tell you honestly what level of project you need, and give you a firm fixed price and a realistic timeline — in writing, before you spend a penny.
