Website Build Timeline: What Happens Each Week

Quick answer: A small business website usually takes 1–4 weeks when the content is ready and the design follows a proven layout, and roughly 6–12 weeks when it needs custom design, fresh copywriting and sign-off from several people. Content and approvals cause more delay than the build itself.

Ask five agencies how long a website takes and you'll hear five different numbers, partly because each starts the clock somewhere different. Some count from the signed quote, others from the day your content arrives. Below, we break a project into the stages that actually happen, show an example week-by-week plan, and are frank about where the time tends to go.

How long does a small business website take from brief to launch?

It depends less on page count than on how many decisions are still open when the project starts. These are typical ranges from our own projects and the wider market, not guarantees:

A focused marketing site can comfortably go from brief to launch in six weeks when scope is clear and decisions come quickly. Scope also drives budget; our guide to what a website costs shows how the two move together.

What happens in each stage of a website project?

Seven stages, some of which overlap:

1. Discovery and brief. Goals, audience, services, competitors, must-have features and who signs off. A written brief saves days later; our website brief template lists what to include.
2. Sitemap and wireframes. The page list and a plain layout for each key template, agreed before anyone discusses colours.
3. Visual design. The homepage and one or two inner templates designed in full, then applied across the rest.
4. Content. Copy, photos, testimonials and product data. This runs alongside design and is usually the critical path.
5. Build. Templates coded, the CMS configured, content loaded, forms and integrations connected.
6. Quality assurance. Testing on real phones and browsers, speed checks, form tests, tracking checks and proofreading.
7. Launch. DNS switched, redirects live, search tools set up, and a handover session for your team.

Here is an illustrative plan for a six-week custom marketing site. It's an example to show how stages overlap, not data from a particular project:

Which stages usually cause delays?

Most slippage happens on the client side, and almost all of it is predictable. That isn't a criticism; business owners are running a business while the site is being built. The common causes:

• Late content. Copy and photos that were "nearly ready" in week one are still missing in week five. The build can't finish without them.
• Extra feedback rounds. A new person joins the review at the design stage and reopens decisions that were already made.
• Slow approvals. A week waiting for sign-off adds a week to launch.
• Missing access. Nobody knows who holds the domain registrar login, or the DNS sits with a former developer.
• Policy pages and legal review. Terms, privacy and refund pages left until the end, then held up by review.

It helps to ask at the outset which of these is most likely in your business. If three partners must approve every word of copy, build that into the plan rather than discovering it in week four. If the photos depend on a shoot, book the photographer before design is signed off.

Agencies cause delays too: vague scope, an overloaded team, or features quietly added mid-build. A written scope with named deliverables protects both sides.

How do e-commerce and custom features change the timeline?

Each feature that touches another system adds its own setup and testing time. The main multipliers:

• Product catalogues. Entering, photographing and describing products takes longer than designing the pages that show them.
• Payments. Gateway activation involves KYC checks that run on the provider's schedule, not yours.
• Shipping and tax rules. Zones, rates and invoices all need testing with real orders.
• Integrations. CRMs, booking tools and accounting software each bring their own quirks.
• Multiple languages. Translation and review roughly double the content work.
• Migrations. Moving hundreds of old pages or products means mapping and redirecting each one.

A store with fifty products and flat-rate shipping can sit at the shorter end of the range. One with variants, wholesale prices and live courier rates sits at the longer end, mostly because there's more to test.

Once a project grows into logins, dashboards and workflows, it's closer to software than a website, and our guide to custom software timelines is the better reference.

What can you do to launch faster without cutting corners?

• Start content on day one. Write service pages while design is underway, not after.
• Put the decision-maker in every review. One person with authority to say yes prevents rework.
• Agree feedback windows. A set number of working days per review keeps momentum on both sides.
• Consolidate feedback. One shared document per round, not comments scattered across email and WhatsApp.
• Collect access early. Domain, DNS, hosting, Google Business Profile and analytics logins in the first week.
• Launch in phases. Go live with core pages, then add the blog, case studies or a second language afterwards.
• Design with real content. Placeholder text hides problems, such as headlines that don't fit, until the build stage.
• Stick to the agreed layout. Redesigning a template mid-build is the most expensive way to lose a fortnight.

What should happen in the first 30 days after launch?

Launch day isn't the finish line. Use the first month to confirm everything works and to catch problems while they're small:

• Test every form, call button and WhatsApp link, and confirm each one is recorded in analytics
• Verify the site in Google Search Console and submit the XML sitemap
• Check that old URLs redirect to the right new pages, and watch for 404 errors
• Run a mobile speed test on your main templates
• Update your website link on Google Business Profile and social profiles
• Confirm backups and security updates are scheduled
• Read the first enquiries that arrive and check they reach the right inbox with the details your team needs
• Keep a fix list of small issues and clear it in one batch in week three or four

Before the project closes, collect every login and file you'll need later; our website handover checklist lists them.

Frequently asked questions

Can a business website be built in one week?

Yes, if it's a small site on a proven layout and every piece of content is ready on day one. The risk is skipping planning and testing to hit the date. A one-week launch works best as a deliberate first phase, with improvements scheduled afterwards.

How long does a website redesign take?

A redesign often takes longer than a new build of the same size, because existing content has to be audited, rewritten or redirected. Expect a timeline similar to a custom marketing site for most small businesses, with extra time for large content migrations.

Why do website projects get delayed?

Most delays come from late content, extra feedback rounds, slow approvals and missing logins. Scope added mid-project is the other big cause. A clear brief, one decision-maker and agreed review windows prevent most of them.

How long does an ecommerce website take?

Usually 6–12 weeks or more, depending on catalogue size, integrations and how quickly product data and payment activation are completed. A small catalogue on a hosted platform can be faster; complex shipping, wholesale pricing or custom features take longer.

What should I prepare before the project starts?

Your goals, a list of services or products, examples of sites you like, brand files, existing copy and photos, and logins for your domain, hosting and analytics. Most importantly, decide who has the final say on design and content.

Plan your timeline with us

We scope every project into stages with dates for both sides, so you know what's needed from you and when. Read about our website process, or book a planning call and leave with a realistic launch date and a fixed quote.