The realistic answer up front
Most small business websites take four to eight weeks from signed brief to launch. A simple brochure site can be done in two to three weeks if everything runs smoothly; a content-heavy or e-commerce site can take eight to twelve weeks or more. Anyone promising a quality custom site in a few days is either using a rigid template or skipping steps you will later wish they had not.
The build itself is rarely the slow part. The clock is set by decisions, content, and feedback, much of which sits on your side. Understanding the stages, and where the delays really come from, lets you keep your project moving rather than watching it drift while everyone waits on someone else.
Stage 1: Discovery and planning (3–7 days)
Before a single pixel is designed, a good agency works out what the site needs to achieve, who it is for, and how it should be structured. This is where you agree on goals, target keywords, the page list (the sitemap), and the core message. Skipping this stage to "save time" is the classic false economy that causes expensive rework later.
Your part here is to be available and decisive. Answering a discovery questionnaire promptly and giving clear feedback on the proposed structure keeps things tight. Discovery is short in calendar terms but pivotal: a well-planned site practically builds itself, while a poorly planned one stalls repeatedly as gaps surface mid-build.
Stage 2: Design (1–2 weeks)
Next comes the look and feel. Depending on the agency, you might see a homepage mockup, a full design in a tool like Figma, or a styled prototype. You review it, request changes, and sign off. This stage usually runs one to two weeks, and the biggest variable is how many revision rounds you need before you are happy.
To keep design on schedule, agree the number of revision rounds upfront and consolidate your feedback. Sending five separate emails over a week, each with one more tweak, drags a two-day task into two weeks. Gather everyone's comments, send them in one go, and design moves quickly. Endless drip-fed changes are the most common cause of design overrun.
Stage 3: Content and copywriting (runs in parallel, often the bottleneck)
Content is the single biggest reason websites run late, and it is usually waiting on the client. Photos, logos, service descriptions, team bios, and the words on every page have to come from somewhere. If the agency writes the copy, that is a defined task on a schedule. If you are supplying it, it can sit on your to-do list for weeks.
The fix is simple: start content as early as possible, ideally during discovery, and treat it as a real deadline rather than something to do "when you get a minute". If you know writing is not your strength, pay for professional copy. It is almost always cheaper than the cost of a launch slipping a month because the words were not ready.
Stage 4: Development and build (1–3 weeks)
This is where the approved design becomes a working website: pages coded, content loaded, forms wired up, mobile layouts handled, and features built. A straightforward brochure site might take a week; an e-commerce site with products, payments, and integrations can take three weeks or more. Custom functionality is the main thing that stretches this stage.
During the build you can usually step back a little while the developer works, but stay reachable for the occasional question. The smoothest builds happen when the design and content were properly finalised first. If those are still moving, the developer ends up rebuilding pages, and the time saved earlier by rushing gets paid back here with interest.
Stage 5: Testing, review and launch (3–7 days)
Before going live, every page is checked: links, forms, mobile and tablet layouts, browser compatibility, loading speed, and the basic SEO setup. You get a final review on a staging link to spot anything that needs fixing. Then come the launch tasks — pointing the domain, setting up SSL, submitting the sitemap to Google — which take a day or so to settle.
Resist the urge to rush this stage. Launching with broken forms or a contact page that emails nowhere quietly loses you enquiries from day one, and you may not notice for weeks. A proper test-and-review pass is short but essential. Build in a couple of days of buffer so a last-minute fix does not blow your launch date.
What makes projects run late
Almost every delay traces back to a handful of avoidable causes, and most of them sit with the client rather than the developer. Knowing them in advance is the best way to keep your project on track, because you can pre-empt them before they bite.
The recurring culprits are slow feedback, content that never arrives, and scope creep, where new features get added mid-build and quietly push everything back. None of these are mysterious, and all are within your control. A responsive client with content ready and a fixed scope is the single biggest factor in hitting a launch date.
- check_circleContent delays — the number one cause; start it on day one
- check_circleSlow or drip-fed feedback — batch your comments and reply within a couple of days
- check_circleScope creep — "can we also add…" mid-build resets the timeline
- check_circleToo many decision-makers — agree who has the final sign-off before you start
- check_circleThird-party hold-ups — domain access, payment account approval, stock feeds
How to make your website launch faster
You have more control over the timeline than you might think. Come to discovery prepared, with your goals, logo, brand colours, and any existing content gathered in one place. Nominate a single decision-maker so feedback does not get tangled in committee. Block out time in your own diary to review work promptly, because the project moves at the speed of your slowest reply.
Finally, be realistic. A rushed website is a website with corners cut, and those corners tend to be the SEO and testing that determine whether the site actually works. Aim for the four-to-eight-week window, prepare your content early, and give honest, batched feedback. Do that and you will launch on time with a site you are proud of rather than one you are quietly apologising for.
Frequently asked questions
Can a website really be built in a week?expand_more
A simple site can, if you use a template, supply all your content upfront, and keep revisions minimal. But a fast turnaround usually means trade-offs in custom design, SEO, and testing. For a quality bespoke site with proper search optimisation, four to eight weeks is realistic. Treat one-week promises with caution unless you genuinely only need something basic.
Why is content always the slow part?expand_more
Because writing clear, persuasive copy and gathering decent photos takes real effort, and it usually sits at the bottom of a busy owner's to-do list. The website cannot launch with empty pages, so it waits. Start content during discovery, set firm deadlines, and consider paying for professional copywriting if writing is not where your time is best spent.
Does e-commerce take longer than a brochure site?expand_more
Yes, noticeably. A shop needs products loaded, payment and shipping configured, tax settings, and often integrations with stock or accounting systems, all of which need careful testing. Where a brochure site might launch in three to four weeks, an e-commerce build commonly takes eight to twelve weeks, more if the catalogue is large or the checkout is heavily customised.
What can I do to speed things up?expand_more
Prepare content early, gather your logo and brand assets before you start, nominate one decision-maker, and reply to feedback requests within a day or two. Avoid adding new features mid-build. The project moves at the speed of your responses, so a prepared, responsive client is the single biggest factor in launching on time.