Websites & Ecommerce
How long does a bespoke website take to design and build?
The short answer
Most bespoke UK business websites take eight to sixteen weeks from an agreed brief to launch. A focused site with content ready can be delivered in six to ten weeks; a larger platform with migration, integrations and several stakeholders commonly takes twelve to twenty weeks. Content approval is usually the biggest avoidable delay.
Indicative price ranges
Focused site
6–10 weeks
Small route set, content ready, one decision-maker and limited integration.
Typical bespoke build
8–16 weeks
Discovery, custom UX and design, CMS, migration, forms, analytics and launch QA.
Connected platform
12–24+ weeks
Complex feeds, ecommerce, portals, several departments or phased data migration.
Timescales begin when scope and responsibilities are agreed. A fixed launch date is realistic only when content, access and approval deadlines are fixed too.
Typical timescales
- 1–2 weeks
Discovery
Commercial goals, audience journeys, technical constraints and route map.
- 2–4 weeks
Design
Wireframes, interface system and responsive page designs.
- 4–10 weeks
Build
Templates, CMS, integrations, content and iterative reviews.
- 1–2 weeks
Launch assurance
QA, accessibility, redirects, analytics and production checks.
Who this suits
- Teams able to name one accountable decision-maker.
- Businesses that can provide content and system access to a schedule.
- Projects where launch quality matters more than an arbitrary reveal date.
Who it does not suit
- A complex platform expected in a fortnight.
- Projects with no agreed content owner.
- Committees unable to make time-bound decisions.
What actually drives the cost
Content readiness
Late copy and imagery block design, build and QA simultaneously.
Decision-making
Consolidated feedback keeps sprints moving; conflicting rounds do not.
Migration
Old URLs, files and metadata require an inventory and controlled redirects.
Integrations
External systems need access, test data and failure handling.
The fastest responsible route
Prioritise the pages and functions needed for the first commercial outcome, then phase the rest. This is different from cutting QA: accessibility, forms, redirects and analytics still need to work on day one.
Vaas & Zo launched a migration and subscription experience in six weeks because the national campaign deadline was fixed and decisions were made quickly. RM English was a multi-month phased engagement because the work combined public content, 87 village guides, live property data and a wider digital platform.
Read what a UK business website costs before compressing a schedule: speed changes team shape and scope, not just the calendar.
Proof
Where we have done this
Common questions
Can a website be built in four weeks?
A small, tightly scoped site can. A bespoke business platform usually cannot be responsibly discovered, designed, built, populated and tested in that time.
What delays projects most?
Content, fragmented feedback and late access to third-party systems.
Can we launch in phases?
Yes. Launch the essential journeys first, then add lower-priority content and functions against an agreed roadmap.