Before the timelines
But that does not mean we cannot give you a useful answer.
A simple website built from an existing template can be live in days or weeks.
A professionally designed business website will often take somewhere around 6–12 weeks.
A bespoke ecommerce website or custom digital platform can take several months.
Current website providers show exactly that spread: GoDaddy's professional service quotes around 6–8 weeks, while Wix puts professionally developed custom sites in a broader two-to-five-month range.
The biggest variables usually are not the number of pages.
They are:
- what the website actually needs to do
- whether the content already exists
- how bespoke the design is
- how much custom development is required
- which systems it needs to connect to
- how quickly decisions and feedback happen
So if somebody promises a delivery date before understanding any of that, the date does not mean much yet.
The short answer: realistic website timelines
As a rough guide:
| Type of website | Rough timeline |
|---|---|
| Simple DIY or template site | A few days to a few weeks |
| Professionally built small business website | Around 6–8 weeks |
| Bespoke business website | Roughly 8–16 weeks |
| Ecommerce website | Often 10–20+ weeks |
| Complex website or custom digital platform | 3–6+ months |
A highly focused bespoke site can move quickly.
A relatively small website can take months if the copy is unfinished, the requirements keep changing or five people need to approve every decision.
That is why the timeline should come out of the scope. Not the other way around.
What actually takes the time?
When people picture a website being built, they often picture somebody writing code.
Development is only one part of it.
A proper website project might include:
Discovery and planning
Before deciding what the website looks like, you need to understand:
- what the business needs it to achieve
- who needs to use it
- what is wrong with the current site
- what functionality is required
- which content already exists
- which systems it needs to connect to
Skipping this can make the first few weeks look faster.
It often makes the rest of the project slower.
Structure and user experience
What pages do you actually need?
How should they connect?
What does somebody need to see before they enquire or buy?
What information belongs together?
This is where the website starts becoming a journey rather than a collection of pages.
Content
Copy is one of the biggest hidden timeline problems.
A designer can create a placeholder page in an afternoon.
Producing genuinely useful copy for twenty pages may take considerably longer.
The same applies to:
- photography
- video
- case studies
- product information
- staff profiles
- downloads
- policies
If the content is not ready, the project often ends up waiting for it.
Design
This includes more than picking fonts and colours.
It might involve:
- design direction
- homepage concepts
- service pages
- mobile layouts
- component systems
- ecommerce interfaces
- forms
- dashboards or account areas
A bespoke site naturally requires more design work than applying a brand to an existing template.
Development
This is where the approved design becomes the actual website.
Straightforward pages can move quickly.
Custom functionality takes longer.
That might include:
- ecommerce
- booking systems
- APIs
- calculators
- portals
- customer accounts
- dashboards
- CMS development
- payment systems
- integrations with other software
Testing
The website then needs testing.
- Forms.
- Links.
- Mobile.
- Desktop.
- Different browsers.
- Checkout.
- Analytics.
- Performance.
- Redirects.
- Integrations.
- Accessibility.
The closer the website is to an operational system rather than a digital brochure, the more important this stage becomes.
What might an 8–12 week website project look like?
Not every project follows exactly the same sequence, and several stages can overlap.
But a straightforward bespoke business website might look something like this:
- Week 1 — discovery
- Understand the business, audiences, goals, current site, functionality and technical requirements. Agree what the project needs to achieve.
- Week 2 — structure and content planning
- Map the site. Decide the key journeys. Work out what content already exists and what needs creating.
- Weeks 3–4 — design
- Develop the visual direction and design the core page types. Feedback is gathered and decisions are made before the build gets too far ahead.
- Weeks 5–8 — development
- Build the website. Create responsive layouts. Connect the CMS. Add forms, integrations and required functionality. Meanwhile, final content can continue being produced.
- Weeks 9–10 — content and testing
- Populate final copy and imagery. Test the major journeys. Check mobile behaviour, performance, analytics, forms and technical details.
- Weeks 11–12 — final changes and launch
- Resolve final feedback. Prepare redirects if required. Complete launch checks. Move the site live.
That does not mean every business website needs twelve weeks.
It is simply a realistic example of where the time goes.
Treat it as an illustration rather than a fixed Collective schedule.
Why do website projects run late?
Development is not always the thing causing the delay.
Some of the biggest timeline killers happen outside it.
The content isn't ready
“We'll sort the copy while you build it.”
Sometimes that works.
Sometimes the entire website is finished and still contains:
Lorem ipsum dolor sit amet.
Agree early who is responsible for content and when it needs to be ready.
Feedback takes too long
The agency sends the design on Monday.
Nobody looks at it until the following Friday.
Three directors then send separate feedback.
The project has effectively lost two weeks without anybody actually working slowly.
The scope keeps changing
- Could we add bookings?
- What about a customer portal?
- Can it sync to the CRM?
- Could we launch in another language?
All perfectly reasonable requests.
But they change the project.
A five-minute conversation can sometimes create several days of additional design and development.
Too many people are approving it
More stakeholders generally means more time.
That does not mean important people should be excluded.
It means somebody needs to own the final decision.
Otherwise:
“Can we just wait until everybody has had a chance to look?”
can become the permanent state of the project.
Integrations appear halfway through
“Oh, by the way, the website needs to connect to this system we've used since 2004.”
Useful information.
Preferably discovered in week one.
Third parties are involved
- Domains.
- Hosting.
- Payment providers.
- IT departments.
- CRM suppliers.
- Legal teams.
- Existing website companies.
Sometimes the website team is ready and the project is waiting for access, approval or information elsewhere.
Can a website be built faster?
Absolutely.
Not every website needs a three-month project.
The fastest way to reduce a timeline is normally to reduce uncertainty and scope.
Start smaller
You do not necessarily need every future idea in version one.
Launch the core website.
Add the secondary functionality afterwards.
Use an existing design system or template
If bespoke design is not commercially important, using an established structure can save substantial time.
There is nothing inherently inferior about that.
Have content ready
If the copy, photography and product information already exist, whole chunks of the project can move much faster.
Make decisions quickly
A responsive client can shorten the timeline significantly without the agency cutting corners.
Current website-design services explicitly call out timely content, feedback and approvals as major factors in keeping a project on schedule.
Launch in phases
If there is a genuine deadline, you may not need to delay the whole website until every future feature exists.
Sometimes the sensible approach is:
- Phase 1: launch what the business needs now.
- Phase 2: introduce the more complex functionality once it is properly tested.
Speed becomes dangerous when it comes from skipping necessary work. It is useful when it comes from removing unnecessary work.
What can you do to keep your website project moving?
If you are the client, you have more control over the timeline than you might realise.
- Give one person authority
- There can be multiple stakeholders. There should still be somebody who can say: “That's approved.”
- Provide access early
- Domains. Analytics. Existing website. Hosting. CMS. Third-party systems. Brand assets. Do not wait until launch week to discover nobody knows the password.
- Agree who owns the content
- Is the agency writing it? Your marketing team? A copywriter? The managing director on Sunday evenings? Get clear early.
- Consolidate feedback
- One clear set of feedback is easier to act on than six contradictory emails.
- Protect review time
- If the agency sends work for review on Tuesday, somebody needs time allocated to review it. Otherwise deadlines slip even though nobody technically missed one.
- Mention the awkward stuff early
- Legacy systems. Internal IT requirements. Compliance processes. Procurement. Unusual hosting. Third-party integrations. Large data migrations. The earlier everyone knows, the easier the timeline is to plan.
Does ecommerce take longer to build?
Usually.
Not simply because there are product pages.
An ecommerce site can introduce:
- products and variants
- catalogue management
- checkout
- payment providers
- delivery rules
- stock
- tax
- customer accounts
- fulfilment
- transactional emails
- discounting
- third-party systems
- operational workflows
Each one adds decisions and testing.
What about redesigning an existing website?
Having an existing website can make things quicker.
You already have:
- a structure
- content
- analytics
- imagery
- URLs
- evidence of what people use
But it can also introduce new work.
You may need:
- content migration
- redirect planning
- analytics migration
- ecommerce migration
- integration changes
- historic data preserved
- old URLs mapped properly
A redesign can therefore be faster or slower than starting fresh depending on what is already there.
And before committing to a rebuild, it is worth establishing whether the website itself is actually the problem.
Should you choose the agency promising the fastest timeline?
Not necessarily.
A three-week timeline can be completely realistic for the right project.
It can also be unrealistic for the wrong one.
Likewise, an agency quoting four months is not automatically doing more thorough work.
Compare what is actually included.
Ask:
- how much discovery is happening?
- who is producing the content?
- is the design bespoke?
- what functionality is included?
- are integrations involved?
- how much testing is included?
- how much feedback time is assumed?
- what does the client need to supply?
A fast proposal with half the scope is not necessarily faster. It is simply a different project.
If you're currently comparing suppliers, our guide on how to choose a web design agency covers the questions worth asking before appointing one.
What should you ask before agreeing a website deadline?
Before putting a launch date in the calendar, answer these:
- Is the scope agreed?
- Do both sides understand what is actually being built?
- Who owns the content?
- And when will it be available?
- Are the integrations known?
- Or could something major emerge halfway through?
- Who makes the final decisions?
- Not who comments. Who approves?
- How quickly will feedback happen?
- A project assuming 48-hour feedback will not stay on schedule if every review takes ten days.
- Are any third parties involved?
- IT teams, hosting providers, payment providers, existing agencies or software suppliers.
- Is anything being migrated?
- Pages, customer data, products, orders, accounts or files.
- Are there any fixed launch dependencies?
- An event? Store opening? Campaign? Contract ending? Product launch?
- What actually counts as finished?
- Does launch mean: website live? All content complete? Analytics verified? Redirects finished? Internal team trained? Integrations tested? Agree that before the deadline arrives.
Have a deadline? Start with what the website needs to do
A useful website timeline comes from understanding the project.
Not from picking a date and hoping the scope fits inside it.
Simple sites can move quickly.
Bespoke websites need more time.
Complex platforms need more again.
And almost every project moves faster when the business knows what it wants to achieve, gets the right people involved and makes decisions promptly.
If you're planning a new site, you can see how we approach web design and development in Liverpool.
If budget is the other question on your mind, our guide to how much a website costs in the UK is the natural next read.