How Long Does It Take to Build a Website?
The honest answer for a small business site is days, not months. Here's why the industry quotes weeks anyway, what those weeks actually get spent on, and the one thing that decides whether your project is fast or slow — which usually isn't the person building it.
The short answer
For a standard small business website — a few pages, mobile-friendly, a way to get in touch:
| Size | Our timeline | Common industry quote |
|---|---|---|
| 3 pages | 3 days | 2–4 weeks |
| Up to 5 pages | 5 days | 4–6 weeks |
| Up to 8 pages | 7 days | 6–8 weeks |
| Full custom build or web app | ~14 days | 2–4 months |
Those are our published delivery times, on the services page next to the prices. The clock starts when your content is in hand — which is the part most timelines quietly depend on and rarely mention.
Where "6 to 8 weeks" actually goes
Six weeks sounds like six weeks of building. It almost never is. For a brochure site, the hands-on work is usually a handful of days. The rest of the calendar is:
Queue position
You're not first in line. A shop juggling nine projects starts yours when a slot opens, and that wait is invisible to you — it just looks like "the website is taking a while."
Approval rounds
Account manager collects your feedback, relays it to a designer, designer makes changes, it comes back for review. Each loop is a couple of days of calendar for maybe an hour of work. Four loops is two weeks gone.
Waiting on you
This is the big one, and it's rarely framed honestly. The project sits idle while everyone waits for the About text or the photos. That's not the builder's fault — but a timeline that assumes it away was never realistic.
Process built for bigger jobs
Discovery calls, wireframes, mood boards, staged reviews. All of it earns its keep on a large project. On a five-page site for a barbershop it's ceremony, and you pay for it in both directions — in the quote and on the calendar.
The test: ask any builder how many hours of actual work your site takes, then compare that to the calendar time they quoted. If it's 20 hours spread over 8 weeks, you're paying for their queue, not their craft.
What a 3-day build actually looks like
Not corner-cutting — just a small site with no committee attached:
- Day 0 — you fill out the quote form. Two minutes: what your business does, roughly how many pages, what it needs to do.
- Day 1 — structure and layout go up. The pages exist, mobile included, and your real content goes into them.
- Day 2 — you look at it and say what's wrong. Wording, colours, the photo you hate. Changes go in the same day.
- Day 3 — forms tested, titles and descriptions written, HTTPS on, live.
The thing that makes this possible isn't working faster. It's the absence of a queue, a relay chain, and three approval layers between you and the person doing the work.
The one thing that decides your timeline
Content. Not design, not development — content.
The projects that finish in three days are the ones where the owner already knew what their business does and could say it in a paragraph. The ones that stretch to three weeks are almost always waiting on text and photos.
So if you want it fast, have these ready before you start:
- What you do, in plain language. A paragraph is enough. Don't write marketing copy — just explain it like you would to a customer standing in front of you.
- Your services, and prices if you publish them.
- Hours and service area. Which towns, which days.
- A logo if you have one. If you don't, that's fine — say so early rather than mid-build.
- Photos. Real ones of your work beat stock every time, and phone photos are usually good enough.
- Your domain login. The single most common last-day delay is nobody being able to find it.
Not having all of it isn't a blocker. Not knowing it's needed until day two is.
What genuinely takes longer
Some things aren't padding. These legitimately extend a timeline:
- Online booking or payments. Real systems with real testing. Worth the extra days.
- Customer logins or accounts. This is a web app, not a website, and it should be scoped as one.
- Migrating an existing site. Preserving URLs so you don't lose the rankings you already have takes care.
- Lots of pages. Forty pages of real content takes as long as it takes.
- Mobile apps. Different job entirely — see mobile app development.
What shouldn't be skipped, however fast
Speed is only a problem when it comes from leaving things out. At any timeline, a finished site has:
- A working mobile layout — most of your visitors are on a phone
- A contact form someone has actually submitted as a test
- A title and description on every page, so Google has something to show
- Business name, address and phone matching your Google listing
- HTTPS
If those are all present in three days, nothing was cut. They're a checklist, not a schedule.
Common questions
What if I don't have my content ready?
Can I make changes after it's live?
Is a fast website lower quality?
What's the fastest you can realistically go?
The bottom line
A small business website is a days-long job wrapped in a weeks-long process. You can pay for the process if it buys you something — on a large project it often does. On a five-page site, mostly it buys you waiting.
Ask two questions before you sign: how many hours of work is this actually, and what are you waiting on from me? The answers tell you more about your timeline than any quote will.
Our delivery times sit next to our prices on the website design page, and the cost guide covers the money side of the same question.