The Website Design Process, Step by Step
If you have not been through this before, the process can feel opaque — you approve something, then nothing visible happens for two weeks. Here is what is actually going on at each stage, and what is required from you.
Stage 1 — Discovery (2 to 5 days)
A conversation about what your business does, where work currently comes from, who your customers are, and what is not working now. Not a slide deck.
The questions that matter are commercial rather than technical: what is a customer worth, how do they currently find you, what do they ask before they buy, and where do you lose them. A discovery process that never asks those is a formality.
You provide: honest answers, including about what has not worked before.
Stage 2 — Structure and sitemap (2 to 4 days)
Deciding what pages exist. This is the least visible stage and has more effect on whether the site works than anything that follows.
The main decision is granularity. One services page is easy and ranks for nothing. A page per service, per location and per audience is more work and is how sites actually get found. This is where a build either becomes a brochure or becomes a search asset.
You provide: a complete list of what you sell and where you sell it. Be exhaustive — services you forget to mention do not get pages.
Stage 3 — Content (1 to 3 weeks — the bottleneck)
This is where almost every project stalls, and it is worth understanding why.
Copy cannot be written well without information only you have: how you actually price, what makes you different in a way a competitor could not also claim, which objections you handle on every sales call. Getting that out of a busy owner is genuinely hard, and it does not happen through a form.
Photography is the other half. Stock photos of a generic office are visibly stock, and customers discount them. Real photographs of your team, your vans, your premises and your finished work outperform stock by a wide margin, and getting them takes an afternoon that nobody schedules.
You provide: an hour on the phone for content interviews, and real photos. Agree a date for both at kickoff. Projects that do this finish on schedule; projects that do not, do not.
Stage 4 — Design (1 to 2 weeks)
Key page templates get designed — usually the homepage, a service page and a contact page. Not every page, because most pages share a template, and designing forty individually is billable work that changes nothing.
Review these on a phone, not just a desktop. Most of your visitors will be on a phone, and a layout that works beautifully on a 27-inch monitor can be unusable on a handset.
You provide: consolidated feedback. One round of collected comments from everyone who has an opinion beats five rounds of individual notes, and drifts the timeline far less.
Stage 5 — Build (1 to 3 weeks)
The design becomes a working site on a staging URL. This is the quietest stage from your side and the busiest from ours.
Things that should be happening here but often are not: image optimization, accessibility, page speed work, schema markup, and the search structure that determines whether any of this gets found. Ask whether they are.
You provide: nothing, other than availability for questions.
Stage 6 — Review and testing (3 to 5 days)
You go through the staging site properly. Check it on your own phone, on an older device if you have one, and ask someone outside the business to try to find something specific.
Test every form yourself and confirm the notification email arrives. This is the single most common launch failure — a form that submits successfully and delivers nowhere, discovered weeks later when someone mentions they never heard back.
Stage 7 — Launch (1 day)
If you are replacing an existing site, the critical piece is redirects: every old URL mapped to its new equivalent. Missing redirects are the reason redesigns lose traffic, and it is entirely preventable.
Also on launch day: analytics and Search Console verified, sitemap submitted, SSL confirmed, and a full backup taken before and after.
Stage 8 — After launch
A site launched and never touched again starts declining almost immediately. Rankings drift, software ages, content goes stale.
Expect a small dip in the first two to four weeks after a redesign while search engines re-crawl and re-evaluate. That is normal. If it has not recovered after six weeks, something is wrong — usually redirects — and it needs investigating rather than waiting out.
Realistic total
Three to five weeks for a straightforward small business site. Six to ten for something larger. Anyone promising a custom site in a week is using a template, which may be fine — but you should know that is what you are buying.
Quick answers
How long does it take to build a website?
Three to five weeks for a typical small business site from kickoff to launch, and six to ten weeks for larger sites with many service or location pages. The timeline is set almost entirely by how quickly content and photography arrive, not by development speed.
What do I need to prepare before building a website?
A list of every service as a separate item, your service areas, licenses and certifications, real photos of your work or premises, logins for your domain and current host, and three competitor sites you like with a note on why.
What is a website launch checklist?
At minimum: redirects mapped from every old URL, analytics and Search Console verified, forms tested end to end including the notification email, SSL active, sitemap submitted, and a full backup taken immediately before and after going live.
Why do website projects get delayed?
Overwhelmingly because of content. Development rarely runs late; waiting on copy, photography and approvals does. Projects where the client agrees a content deadline at kickoff finish roughly on time; projects that leave it open do not.
Let’s talk about what your site should be doing
Tell us what you do and where you work. We will give you a straight answer on whether we can help, what it would take and what it would cost — usually the same day.
- Reply within one business day
- No sales sequence, no obligation

