How Long Does It Take to Build a Small Business Website?

If you have decided you want a website, the next question is usually how soon you can have it. The honest answer is that it depends far more on what you are building, and how ready you are, than on how fast anyone can type. A clean one-page site can be live within a few days. A full bespoke build with custom features takes weeks. And in almost every case, the thing that decides whether it lands on the fast or slow end of that range is you, not the person building it.

Honest timelines by type of site

Forget the marketing promises of instant sites. Here is what each kind of build realistically takes when it is done properly, assuming your content is ready to go.

Two honest caveats. First, "a few days" assumes a managed or one-page build where the structure is largely set and your content is ready; a fully bespoke design from a blank file always takes longer because the design itself is real work. Second, these are working timelines, not promises made before anyone has seen your content. The difference between the two is the rest of this guide. If you want the cost side of these same bands, our guide on what a small business website should cost lines up with them.

What actually slows a build down

Here is the part most articles skip, because it is not flattering to admit. The developer is rarely the bottleneck. In my experience, and across the industry, projects stall in the same few places, and almost all of them sit on the client's side. That is not a criticism; running a business is busy, and a website is rarely the most urgent thing on your desk. But knowing where the delays come from is how you avoid them.

• Waiting on your words. By a distance the biggest one. A site cannot be finished around "copy to follow". If the about page and service descriptions take three weeks to arrive, the build takes three weeks longer, no matter how fast the developer is.
• Waiting on photos. Real photos of your work, your team or your premises beat stock every time, but gathering or shooting them takes time. The hunt for "that good photo from last year" stalls more projects than any code ever will.
• Slow feedback rounds. If a draft sits in your inbox for a week before you reply, every revision cycle adds a week. Quick, batched feedback is the single biggest thing that keeps a build moving.
• Decisions left open. Not sure whether you want a booking form or just a phone number? Unsure of your service list? Open questions pause the build until they are answered.
• Scope creeping mid-build. Adding "oh, can we also have a shop" halfway through is fine, but it resets the timeline. New scope means new time.

What to have ready before you start (the prep checklist)

If you walk into a build with these sorted, you can genuinely halve the timeline. None of it is hard, it just needs doing before, not during.

1. Your core text. What you do, the services you offer, a short about, and how people should get in touch. It does not need to be polished prose; a clear draft is enough for a good designer to shape.
2. Your photos. Real images of your work, premises, team or products, gathered in one folder. Decent phone photos beat stock.
3. Your logo and any branding. A logo file if you have one, plus any colours you already use. If you have none, say so early so it can be designed in, not bolted on.
4. Your must-have list. What the site has to do: just inform, take enquiries, take bookings, sell. Decide this before you brief, because it sets the whole timeline.
5. Reviews and credentials. A few genuine reviews and any accreditations (Gas Safe, NICEIC, qualifications) ready to drop in for trust.
6. Domain access. If you already own a web address, the login to manage it. If not, that is a five-minute job to sort at the start.

If you are not sure what content the site even needs, that is worth nailing down first. Our checklist on what every small business website needs covers exactly what to gather, so the prep above writes itself.

The fast-track: a managed site live in days

If speed is the priority, the quickest honest route is a managed build where the heavy structural decisions are already handled and the job is to design around your business and drop in your content. Because the hosting, setup and framework are sorted on day one, a site like this can be live within days of your content arriving, rather than weeks. You can see the kind of work this produces in the live demos, which are real builds, not mockups.

A bespoke build trades that speed for total customisation: every layout designed from a blank file, custom features, and software-grade testing, which is why it lands in the weeks-not-days bracket. Neither is better; they answer different needs. If you are weighing the two on cost and ownership as well as speed, our guide on pay-monthly versus one-off websites covers that side.

Why "a website in 24 hours" is usually a warning sign

You will see ads promising a finished site overnight. Be a little wary. A genuine one-day turnaround almost always means one of two things: a template with your logo dropped in and your own text pasted over the placeholder, or a half-built shell that quietly takes weeks of back-and-forth to actually finish. Real design and proper setup take a little time. Fast is good; instant usually means corners cut.

The right question is not "how fast can you do it" but "how fast can you do it well, and what do you need from me to get there". A good answer to that includes a request for your content, because that is the honest bottleneck.

The bottom line

A simple managed business site can be live in days. A custom brochure site is one to three weeks. Anything with a shop, bookings or custom features runs to several weeks or more. The timeline is set less by the building and more by how ready you are: get your words, photos and decisions sorted before the work starts, give quick feedback, and you will land at the fast end of every one of those ranges. Drag your heels on the content, and the most talented developer in the country still cannot finish your site.