“How long does it take to build a website?” is usually the second question every client asks us, right after price. It is also the question with the most dishonest answers online. Some agencies promise a full website in 48 hours. Others say six months and will not explain why. Neither answer helps you plan a launch, a marketing campaign, or your budget.
Here is the honest version: what the timeline looks like for each type of site, what happens in each phase, and the things that actually slow projects down. Spoiler: the delay is rarely the building.
A simple brochure website takes about 1 to 2 weeks. A business website with booking or forms usually takes 3 to 5 weeks. A standard Shopify store setup takes 1 to 2 weeks, while large e-commerce catalogues can take 4 to 8 weeks or more. The build itself is rarely the slow part. Waiting on content, photos, and feedback is what stretches most projects.
How long does it take to build a website, by type?
Every project is different, but after building sites for small businesses and startups, the patterns are consistent. Use these ranges for planning, not promises.
A simple brochure website: 1 to 2 weeks
This is a five to eight page site: home, about, services, gallery, contact. It tells people who you are, what you do, and how to reach you. There are no bookings, no payments, and no complicated features. If the text and photos are ready on day one, a brochure site can genuinely be designed, built, and live inside two weeks. This is the fastest honest timeline there is.
A business website with booking or forms: 3 to 5 weeks
Add a booking system, quote request forms, a blog, or integrations with tools like a CRM or email marketing platform, and the timeline grows. Each feature needs setting up, connecting, and testing. A form that looks simple can involve notification emails, spam protection, thank-you pages, and making sure enquiries land in the right inbox. Three to five weeks is a realistic range when content arrives on time.
An e-commerce store: 1 to 2 weeks for a standard setup, longer for large catalogues
Online stores take longer when the catalogue is big, because there is simply more to check. Products, photos, prices, shipping rules, tax settings, payment gateways, order emails, returns policies. A store with 20 products is a different job from one with 2,000. The build might take three weeks, but loading products, testing checkout with real payments, and fixing the small things that only show up in testing can double that. Anyone who promises you a proper store in a few days is skipping the testing, and you will find out during your first real orders.
If you are weighing up platforms, our WordPress vs Shopify comparison explains how the choice affects both cost and timeline.
A DIY builder site: a weekend, with real limits
One option you will see advertised everywhere is building it yourself on a drag-and-drop builder. For a very simple site, you can honestly get something live in a weekend. The catch is the hidden time: learning the tool, fighting with layouts that will not sit right on phones, and fixing SEO basics the builder handles badly. Many owners spend 30 or 40 hours and end up calling a developer anyway. DIY is fast to start. It is not always fast to finish well.
The phase-by-phase breakdown
However long the total is, the work follows the same order. Knowing the phases helps you see where your project actually is, instead of just hearing “it’s in progress”.
Phase 1: Planning and discovery (2 to 4 days)
We agree the pages, features, and goals. You get asked a lot of questions: who are your customers, what should the site make them do, what do you like about competitors’ sites. Skipping this is how projects end up rebuilt halfway through.
Phase 2: Design (about 1 week)
You see the homepage design first, usually as a visual mockup or a working draft. This is the stage with the most back and forth, and that is normal. Two rounds of revisions are typical. The clock here depends mostly on how fast feedback comes back.
Phase 3: Development (1 to 3 weeks)
The approved design gets built into a working website: all pages, menus, forms, and features. On WordPress this includes setting up the theme, plugins, and anything custom. You will usually see a staging link so you can watch it come together.
Phase 4: Content loading (a few days, if content is ready)
Your final text, photos, prices, and product details go in. This phase is quick when content was prepared during phases 1 and 2, and painfully slow when it starts now. More on that below.
Phase 5: Testing and launch (2 to 4 days)
Every page gets checked on phones, tablets, and desktops. Forms are submitted and confirmed. Speed is tested, backups and security are set up, and the site goes live. Google’s web.dev resources explain why this testing stage matters for search rankings as well as visitors.
What slows website projects down
In our experience, the build itself is almost never the bottleneck. These are:
Content that is not ready. The number one cause of delays, by a long way. Writing five pages of text takes business owners far longer than they expect, because they are also running a business. A project quoted at four weeks quietly becomes nine while everyone waits for the About page.
Slow feedback. Design feedback that takes ten days instead of two adds over a week to every round. Two slow rounds and your launch date has moved by a month without a single extra hour of development work.
Scope changes halfway through. “Can we also sell gift cards?” sounds small in week three. It can mean payment setup, new pages, and fresh testing. New ideas are fine, but they restart parts of the process. Writing them down for a phase two is usually the smarter move.
Too many decision-makers. When five people have to agree on a homepage, feedback arrives as five conflicting opinions. One named person who gathers comments and sends a single reply keeps things moving.
Waiting on accounts and access. Domain logins, hosting details, payment gateway approvals for stores. Payment approvals in particular can take days and sit entirely outside your developer’s control.
How you can speed up your own project
The good news is that the client controls most of the delays, which means you can remove them:
- Prepare content before the project starts. Rough text in a document is fine. Your developer or a copywriter can polish it. Blank pages are the problem, not imperfect wording.
- Gather your photos early. Real photos of your team, premises, and work beat stock images and avoid a last-minute scramble. (If you are wondering what else affects the budget while you plan, our guide to small business website costs is worth a read.)
- Give feedback in rounds, not drips. Collect everyone’s comments, send them together, and be specific. “Make it pop” helps nobody; “make the heading bigger and use the blue from our logo” gets done the same day.
- Name one decision-maker. One person approves designs and answers questions. Committees are where timelines go to die.
- Answer questions quickly. A two-day delay on a simple question often costs more than two days, because the developer has moved to another project and has to get back into yours.
A word about rush jobs
Can a website be built faster than the ranges above? Sometimes, yes. If your content is ready, the design is straightforward, and you can give feedback within hours, a simple site can be turned around very quickly. We have done it for launches with fixed dates.
But be careful with anyone who promises rush delivery as their normal offer. Speed usually means something was cut: testing on real phones, proper SEO setup, or the backup and security steps. Those cuts are invisible on launch day and expensive later. A realistic timeline with everything done properly beats a fast launch followed by a month of fixes. If you have a hard deadline, say so at the start. A good developer will tell you honestly what fits and what does not, rather than promising everything and delivering half.
So, when should you start?
Work backwards from when you need the site. Add the realistic build time for your type of site, then add two weeks of slack for the delays nobody plans for. If you need to be live for a busy season, that means starting months ahead, not weeks.
If you are planning a site now and want a timeline based on your actual project rather than generic ranges, talk to us. We will look at what you need, tell you how long it should take and why, and put it in writing before any work starts. See our services for what we build, or contact us with your plans and deadline. Honest timelines, no drama.
Frequently Asked Questions
Can a website really be built in a week?
A simple brochure site can, if your text and photos are ready and feedback is fast. Stores and sites with booking or custom features cannot be done properly in a week. Anyone promising that is skipping testing.
Why do agencies give such different timelines for the same site?
Because their process differs. Some include design, revisions, content loading, and testing; others quote only the build. Always ask what is included in the timeline before comparing.
What is the biggest cause of website delays?
Waiting for content and feedback. Writing text, gathering photos, and approving designs sit with the client in most projects, and they are the stages that stretch.
Does using WordPress or Shopify change the timeline?
Yes. A Shopify store with a ready-made theme is usually faster to launch than a custom WordPress build, but product loading and testing still take time. Custom features add weeks on any platform.
How can I make sure my project finishes on time?
Prepare content early, name one decision-maker, send feedback in complete rounds, and agree the timeline in writing before work starts. Most on-time projects do those four things.
