How Long Should a Website Build Actually Take?

"How long will it take?" is usually the second question we get asked, right after what it costs.

It is a harder question than it sounds, because "a website" covers everything from a five page site for a plumber to a booking platform with user accounts and payments. Quoting one number for both is how people end up disappointed.

So here are real timelines for the three shapes of project we actually build, what happens inside each week, and the honest answer about why projects slip. That last part matters more than the rest, because the thing that makes a build take four months instead of six weeks is almost never the code.

The Short Version

• A small business or trade website: one to three weeks, if the content is ready.
• A larger custom website: four to eight weeks.
• An app, SaaS product or internal system: three months and up, delivered in stages rather than one launch.

Now the detail, because the caveats are where the truth lives.

A Small Business Website: One to Three Weeks

This is a site for a trade, a local service business, a clinic, a club. Five to ten pages. Services, proof of work, contact, a quote path, maybe a couple of location pages.

There is no good reason for this to take three months, and it very often does elsewhere. The reason it takes three months is usually that it is sitting in a queue, not that it is being worked on.

Realistically:

• Days 1 to 2: we get what we need from you. What you do, who you serve, what you charge, photos of real work, your accreditations, your reviews.
• Days 3 to 6: the build. Structure, pages, copy drafted, everything responsive and fast on a phone.
• Days 7 to 9: your review round. You look at a real, live preview link, not a picture of a website, and tell us what is wrong.
• Days 10 to 12: changes, then the launch checklist. Domain, SSL, analytics, Search Console, structured data, redirects from the old site if there is one.

Our Fast-Track Website is exactly this, from £600, and it is fast specifically because it starts from proven foundations rather than a blank page. You are not paying for someone to reinvent a services page layout that already works.

The single variable that decides whether this is one week or three is whether your content exists. More on that below, because it is the whole ballgame.

A Larger Custom Website: Four to Eight Weeks

More pages, a bespoke design rather than a proven layout, and usually something that has to work rather than just be read: a booking flow, a members area, a filterable portfolio, an integration with a system you already use.

The shape changes. You get a design stage, because when a site is bespoke you should see and approve it before anyone builds it.

• Week 1: discovery and scoping. What the site needs to do, who uses it, what counts as success, and a page by page structure.
• Weeks 2 to 3: design. Key screens and flows, so you can click through a prototype and react to something real.
• Weeks 3 to 6: build, in two week cycles, each one ending with something working that you can look at.
• Weeks 6 to 8: testing, content loading, performance and accessibility checks, then launch.

Our website build packages start from £1,500 and this is the territory they cover.

An App, SaaS Product or Internal System: Three Months and Up

Once there are user accounts, payments, permissions, data that matters, and an admin side, you are building software, not a website. Different rules.

The most important one: do not aim at a single launch date three months out. That is how projects die. You build in two week sprints, each ending in something that works, and you keep the ability to change your mind as you learn.

Our full project process is one to two weeks of discovery and scoping, one to three weeks of design sprint, then two week build cycles with a demo at the end of each, then one to two weeks of testing and refinement before launch.

That structure exists to solve a specific problem: the thing you thought you wanted in week one is usually not quite the thing you want in week seven, and you only find that out by using it. Which is also the argument for starting with an MVP rather than specifying the finished article up front and hoping.

The Real Reason Projects Run Late

Now the honest part.

In our experience the build almost never causes the delay. Content does. Specifically:

Photos. You need real pictures of real work. Not stock images of a model in a clean hard hat. Getting them means someone actually going out and taking them, which means finding an afternoon, which means it slides.

Copy and approvals. Someone has to decide what the About page says, and whether the prices go on the site, and whether you are happy being described as the best in the county. These are business decisions and they need the owner, who is busy doing the actual job.

Feedback rounds. A preview link sent on Monday and reviewed the following Thursday adds a week to the project every single time it happens.

Third parties. Domain access from the person who set it up in 2016 and left. The old developer who does not reply. Merchant account approval. These can quietly cost weeks and none of it is anyone's fault.

Scope drift. Not one big change, but eleven small ones. "Can we just add a booking form" is never just.

We plan around this now. We draft copy for you rather than sending a blank document and waiting, we tell you exactly which photos to take before the build starts, and we agree review windows up front so a round is days not weeks. It is why a Fast-Track site can be one week: the decisions are front loaded so nothing stalls halfway.

How to Make Your Build Faster

If you want the short version of the above, from your side:

1. Sort the photos first. Before anything else. Twenty good pictures of finished jobs unblocks half the project.
2. Decide the money question early. Are prices going on the site, and what are they. This one question holds up more homepages than anything technical.
3. Give one set of feedback, from one decision maker. Five people commenting separately over two weeks is the single most expensive thing you can do to a timeline.
4. Get your domain and hosting logins found now. Before you need them. This is the classic launch day surprise.
5. Ship, then improve. A live site earning enquiries beats a perfect site in review. Most "we must have it before launch" items are genuinely fine as a week two update.

Be Wary Of Both Extremes

A three month timeline for a five page trade website usually means you are in a queue behind bigger clients, not that anyone is doing three months of work.

A two day turnaround on a genuinely custom build usually means a template with your logo dropped in, no thought about how anyone finds you, and no proper launch checks. Some of the "48 hour website" offers are real, but they are real because the scope is genuinely tiny, and if the scope was not tiny then something is being skipped. Usually it is the SEO groundwork, the speed work, or the testing on an actual phone.

What you want in between is a firm timeline, a named process, and something you can look at before launch day.

How We Can Help

We will give you a realistic date, tell you what we need from you and when, and show you working previews as we go rather than a big reveal at the end. If a timeline is not achievable we will say so before you commit rather than halfway through.

Get a ballpark on cost and scope from the quote generator, see what we have built in our recent work, or get in touch and tell us when you need to be live by.