How Long Does It Take to Build a Small Business Website?
Two to three weeks is achievable. Most projects take three months. The difference is almost never the developer.
The honest answer is that a straightforward small business site takes two to three weeks of working time. The reason most projects take two to three months is not the building.
Where the time actually goes
| Stage | Working time | Who is blocking |
|---|---|---|
| Discovery conversation | 1 hour | Scheduling |
| Content — writing and gathering | 3–7 days | Usually the client |
| Design of the key pages | 3–5 days | Designer |
| Build | 4–7 days | Developer |
| Review and revisions | 2–4 days | Client |
| Technical setup and launch | 1–2 days | Developer |
Add it up and you get roughly two to three weeks. What turns that into three months is dead time between the stages — a draft sitting unreviewed for eleven days, photos promised and not sent.
The bottleneck is always content
If a project runs late, it is content. Not sometimes — nearly always.
It is not laziness. Writing about your own business is genuinely difficult, there is no deadline pressure, and there is always something more urgent. So the request to send over your service descriptions and some photos sits on the list for six weeks.
- Get someone else to write it. If content is in your court, the project moves at the speed of your least urgent task. We write it for exactly this reason.
- Do the photos in one session. Book a couple of hours, get the van, the team, the premises and some finished work, and be done.
- Decide who decides. Projects with three stakeholders and no tiebreaker take twice as long.
- Answer within two days. Not because we are impatient — because context is expensive to reload.
What each stage actually involves
Discovery
One conversation about what the business does, who buys, what the competition looks like and what the site has to achieve. Skipping this is how you end up with a beautiful site that does not produce any calls.
Content and structure
Deciding what pages exist and what each one says, based on what people actually search for rather than how the business is organised internally. This is where a site is won or lost, and it is also the least visible part of the work.
Design
Usually the homepage plus one interior page. Get those right and the rest follows the pattern. Designing all ten pages upfront wastes time — the feedback on page one changes pages two through ten anyway.
Build
Turning the design into a fast, responsive site. Mobile is checked on real devices, not just a narrow browser window, because that is where most of your visitors are.
Technical setup
Analytics, Search Console, structured data, the Google Business Profile link, redirects from the old site, and the pre-launch checks. Often skipped in cheap builds, and it is the difference between a site that exists and one that gets found.
What makes a project take longer
- E-commerce. Products, variants, shipping rules, payments. Add two to six weeks depending on catalogue size.
- Migrating an existing site. Preserving rankings means mapping every old URL to a new one. Worth doing; adds a week.
- Integrations. Anything that has to talk to your booking system or accounting is software work, not page building.
- Multiple locations. Each genuinely needs its own page with its own content.
- Committee approval. Every additional approver adds days, not hours.
And after launch
Launch is the start of the useful part, not the end of the project.
| When | What happens |
|---|---|
| Days 1–14 | Google discovers and indexes the pages |
| Weeks 2–6 | Rankings settle; you start seeing real search queries in Search Console |
| Months 2–6 | Positions improve for the terms you targeted, if the groundwork was done |
| Ongoing | Reviews, local mentions and new content compound |
If you want calls sooner than that, sort out the Google Business Profile in parallel. It is free and it works on a much shorter timescale than organic rankings do.
How to keep your project on schedule
- Book the discovery call before you commit to anything, so the scope is real.
- Gather photos and your logo before day one, not when asked.
- Nominate one decision maker.
- Block two short slots in your calendar for reviews and keep them.
- Give feedback in one batch rather than in a trickle over a week.
- Say what you do not like plainly. Politeness costs revisions.
The projects that finish in three weeks are not the ones with the fastest developer. They are the ones where somebody answered the email.
Frequently asked
Can a website be built in a week?
A simple one can, if the content already exists and decisions get made the same day they are asked for. What cannot be compressed is the thinking — working out what the site needs to say and to whom. Rushing that produces a site that looks finished and does nothing.
Why do website projects run late?
Overwhelmingly one reason: content. Photos, service descriptions, staff bios and pricing sit on the client's list behind everything urgent. A build quoted at three weeks turns into three months, and almost all of the delay is waiting.
What do you need from me, and when?
Realistically about ninety minutes of your time in total: one conversation at the start, one look at the homepage draft, and one review before launch. Everything else is our problem, provided the answers come back within a couple of days.
How long before a new site starts ranking?
Indexing takes days to a couple of weeks. Ranking for anything competitive takes months, and for a brand new domain longer still. If ranking quickly matters, the Google Business Profile is the faster lever — a well-configured profile can produce calls while the site is still gaining traction.