The part the builder controls is the smallest part.
When someone asks how long a website takes, they are usually imagining the build itself — the pages, the design, the code, getting it live. That part, for a typical five-to-eight page business site, genuinely does take two to three weeks when I have everything I need. The problem is that "everything I need" is rarely ready on day one.
In my experience, the single biggest cause of a website running late is content: the words, the photos, the pricing, the list of services, the "about" blurb, the contact details. None of it is complicated. All of it takes time to gather if you have not done it before. And most clients have not.
What a realistic timeline actually looks like.
Here is roughly how a website project breaks down in practice, for a sole trader or small business in Kent getting their first proper site:
- Week 1 — Discovery and content gathering. We agree on structure and I send you a simple brief. You fill in the words for each page, pull together photos (or we agree to use stock), and confirm the services and prices you want listed. This week is almost entirely on you.
- Weeks 2–3 — Build. I build the site once content is in. You get a staging link to review.
- Week 4 — Revisions and review. You come back with changes. One round of proper revisions is normal; three rounds of "actually, can we change the whole homepage" is not.
- Week 5 — Domain, email, and go-live. Pointing your .co.uk domain, setting up any redirects, connecting Google Search Console, and going live. Usually a day or two of actual work, but DNS propagation adds a buffer.
Five weeks, if everyone is responsive. But I have had projects stretch to twelve weeks because the content took nine weeks to arrive. That is not unusual — it just needs naming honestly at the start.
The content bottleneck, explained plainly.
You know your business better than anyone. You also think about it all day, every day, which paradoxically makes it harder to write about. Sitting down to describe what you do, in plain English, in a way a stranger would understand — that is genuinely difficult. Most people stare at a blank document for longer than they expected.
Add to that: finding decent photos. Not a flattering selfie or a blurry shot from three years ago, but photos that actually show the work, the premises, or the product. A roofer in Deal once sent me seventeen photos; fifteen were taken in the dark from two floors up, and one had a thumb in it. We sorted it, but it added a week.
The fix is not magic — it is just starting earlier. I now send clients a content brief on the day we agree to work together, not when I am ready to build. The earlier you start collecting, the less it holds things up.
Decisions that stall projects more than people realise.
Content is the biggest delay, but it is not the only one. Here are a few others I see regularly:
Not knowing your own prices. Sounds obvious, but plenty of trades and service businesses have never written their prices down. If you want them on the site, you need to decide them first. "We'll sort the prices out later" usually means two weeks of back-and-forth.
Too many decision-makers. One person runs the business but wants a partner, a family member, and a friend to sign off the design. Each person has opinions. By the third round of changes, the site looks like it was designed by committee — because it was. The faster projects I have worked on had one decision-maker who trusted the process.
Changing the brief mid-build. "Actually, can we add a booking system?" halfway through is a new project, not a revision. It is fine to add things — just understand it resets the timeline.
Domain and email access issues. If your domain is registered with a provider you set up in 2017 and you cannot remember the login, that can add days. Sort your domain access before we start. GoDaddy, 123-reg, and Namecheap all have account recovery processes, but they take time.
What you can do right now to speed things up.
If you are thinking about getting a site built — whether with me or anyone else — here is how to cut weeks off the process before you even have the first conversation:
Write a rough paragraph about each service you offer. Do not worry about it being polished; a builder can tidy prose but cannot invent the facts. List every service, what is included, what is not, and roughly what it costs. That alone will save a fortnight.
Take or gather photos this week. Natural light, clean background, show the actual work. A Kent electrician I worked with spent one afternoon photographing his van, his tools, and a completed job he was proud of — those images made the whole site feel credible. For a product business, decent photos on a white or neutral background are genuinely worth more than a fancy layout.
Find your domain login. If you do not have one, register a .co.uk now at Namecheap or Krystal — both are solid and straightforward. A .co.uk currently runs around £8 to £12 per year. Do not pay more than that.
Write down the ten questions customers ask you most often. Those become your FAQ, your service page copy, and often your strongest SEO content. They are also the questions you probably answer differently every time, and a website is a chance to nail the answer once.
When a faster build is possible.
There are situations where two weeks, start to finish, is genuinely achievable. I have done it. The conditions are: you have content ready to hand over on day one, you have one clear decision-maker, the brief is simple (under six pages, no shop, no booking system), and you are available to review quickly when I send the staging link.
For my Idea to Launch sprint, that compressed timeline is the whole point — it forces the content decisions upfront so the build can move fast. It suits founders who have been sitting on an idea and need to get something credible live before a specific date: a trade show, a product launch, a conversation with a potential stockist. The constraint of a deadline is often the thing that cuts through the dithering.
Mind you, even a sprint needs the content. There is no version of this where I can produce a convincing website for a business I know nothing about without some input from the person who runs it.
A word on agencies quoting shorter timelines.
Some agencies will quote you four weeks as a standard. Ask them what that assumes. Usually it assumes content ready on day one, a single sign-off contact, one round of revisions, and a straightforward brief. None of those assumptions are unreasonable — they just do not always reflect how a first-time client actually operates.
I would rather be honest about a realistic six-week timeline than promise four weeks and deliver eight. You can plan around an honest estimate. You cannot plan around an optimistic one.
The number that matters more than launch date.
Here is the thing I try to get clients to focus on: the date the site goes live matters less than what is on it when it does. A site that launches a fortnight late but has clear pricing, good photos, and honest copy about what you do will generate more enquiries than one that launched on time and says nothing useful. I have seen both. The content always wins.
So yes, plan a timeline, hold people to it (including yourself), and push to get it live. But do not cut corners on the words and images to hit an arbitrary date. The site will be there for years. A few extra days of content work is worth it.