A custom website project for a small business normally runs 4 to 12 weeks from signed brief to launch, with post-launch stabilisation adding another 2 to 4 weeks on top. That range holds for a standard brochure or business site; e-commerce and SaaS builds typically extend to 10 to 24 weeks depending on integrations and content volume. The single principle that protects that schedule, according to government project management guidance, is treating the timeline as a living document rather than a fixed promise.

Before your first call with an agency, ask for three things:

A phase-based schedule with named sign-off points, not a single delivery date
A written contingency allowance for internal review cycles
Confirmation of who on your side needs to approve each milestone

Ask for a phase-based timeline with sign-offs before you sign anything else. That one habit prevents more schedule disputes than any contract clause.

Key Takeaways

A realistic website design timeline runs 4 to 12 weeks for a standard business site, and it holds only when both agency and client follow a phased, sign-off-driven process with built-in review buffers.

Point	Details
Standard timeline range	Expect 4 to 12 weeks for a professional business site, longer for e-commerce or SaaS builds.
Discovery sets the pace	Two to four weeks of proper discovery on medium-complexity projects prevents costly scope drift later.
Content readiness drives speed	Sites with copy ready on day one can launch in 3 to 4 weeks; late content is the top cause of delay.
Build in contingency	A 10 to 15% buffer for review cycles keeps a “living” timeline realistic rather than aspirational.
MedwayWebDesign’s approach	Structured kickoff, two design revision rounds, sprinted development, and 14 days of post-launch support as standard.

How long does a website design timeline usually take?
What are the phases of a website design project?
What does the client need to provide during a web design project?
Why do website projects run late?
What does a 10-week website timeline actually look like?
What should you ask an agency to prove their timeline is credible?
How does Medway Web Design structure a project timeline?
Get a realistic timeline before you commit to an agency
Frequently asked questions about website design timelines
Sources

How long does a website design timeline usually take?

The honest answer depends on scope, but the bands are consistent across the industry. A landing page or one-pager can go live in 1 to 2 weeks once copy and imagery are ready. A small brochure site of 5 to 10 pages typically needs 3 to 6 weeks, and a 5-page site with content ready on day one has launched in as little as 3 to 4 weeks. A standard business site running 10 to 20 pages, with a few custom features, generally takes 6 to 10 weeks. E-commerce builds move to 10 to 16 weeks once payment gateways, product catalogues and stock integrations enter the picture, and SaaS or platform-style projects with authentication, dashboards and third-party APIs often run 12 to 24 weeks.

What pushes a project from the short end of a band to the long end is rarely the design work itself. It’s how ready your content is, how many integrations you need, and how many people have to sign off before anything moves forward. A single decision-maker with brand assets sorted moves fast; a five-person committee reviewing copy in separate email threads does not.

Project type	Typical duration	Main deliverable	Primary client input needed
Landing/one-page	1 to 2 weeks	Single conversion-focused page	Final copy, one hero image
Small brochure (5 to 10 pages)	3 to 6 weeks	Multi-page site with navigation	Page content, brand assets
Standard business site (10 to 20 pages)	6 to 10 weeks	Custom site with forms/CMS	Content across all pages, stakeholder sign-off
E-commerce	10 to 16 weeks	Storefront with checkout	Product data, payment setup, policies
SaaS/complex platform	12 to 24 weeks	Custom application with integrations	Technical specs, API access, QA involvement

What are the phases of a website design project?

Most agencies work through a seven-step sequence: discovery, sitemap and wireframes, visual design, content production, development, testing and QA, then launch and post-launch optimisation. Each phase should end with a specific deliverable and a named person signing it off before work continues.

Discovery takes 1 to 3 weeks for a standard site, longer for complex builds; medium-complexity custom projects often need two to four weeks of discovery alone to avoid the scope drift that comes from vague requirements. The deliverable is a signed brief and technical scope, approved by whoever holds budget authority.

Sitemap and wireframes usually take 1 to 2 weeks and produce a site structure and low-fidelity layout, signed off by the project owner before visual design starts.

Visual design runs 2 to 3 weeks, building in two to three revision rounds as standard. Extra rounds beyond that add time, so agree the revision limit up front.

Content production can run in parallel with design if you start early, but it frequently becomes the bottleneck when copy isn’t ready.

Development takes 3 to 8 weeks depending on custom functionality and integrations, with the CMS build and any third-party connections handled here.

Testing and QA, covering accessibility, cross-browser checks and speed, typically needs one to two weeks and should never be compressed.

Launch involves redirects, analytics and DNS/SSL configuration, usually three to seven days of coordinated work.

Before accepting any phase as complete, check: does the deliverable match the signed brief, has the named approver actually reviewed it, and is feedback documented in one place rather than scattered across emails and calls?

What does the client need to provide during a web design project?

The agency controls execution, but you control the pace. Late content and unclear feedback are the two most common reasons a website development schedule slips past its target date.

Before kickoff, have ready:

A completed brief covering goals, audience and must-have features
Brand assets: logo files, colour codes, fonts, existing photography
Final or near-final copy for priority pages
A subject-matter reviewer who can answer technical or product questions quickly
Hosting and any third-party account credentials (booking systems, CRMs, payment providers)
One named point of contact with authority to approve decisions

Response speed matters as much as the content itself. A client who consolidates feedback from every stakeholder into a single document within 48 hours keeps a project on schedule; one who lets three people send conflicting comments across a week does not.

Pro Tip: Ask your agency for a shared feedback document with line-by-line comments rather than emailing screenshots. It halves the back-and-forth on revision rounds.

Pro Tip: Build a simple content delivery plan before kickoff, mapping which pages need copy by which week, so writing never becomes the thing holding up development.

Why do website projects run late?

Delays rarely come from the design or build work itself. They come from slow content delivery, scope changes introduced mid-project, feedback arriving from multiple people at different times, third-party integrations that need vendor cooperation, and stakeholders who go quiet during a review window.

The fix is procedural, not heroic effort:

Fixed review windows (say, five business days) with an automatic escalation if feedback doesn’t arrive
A change-control process that prices and reschedules new requests rather than absorbing them silently
A built-in buffer, typically 10 to 15% of total project time, for review cycles
A template brief and firm content deadlines agreed before development starts

Industry experience consistently points to client responsiveness as one of the largest swing factors in whether a project lands on time or drifts by weeks, more so than the technical complexity of the build itself.

What does a 10-week website timeline actually look like?

Here’s a worked example for a standard business site with a responsive, engaged client:

Week 1 — Kickoff meeting, detailed brief signed off, brand assets collected
Week 2 — Sitemap delivered and approved
Week 3 to 4 — Wireframes built and signed off; content writing begins in parallel
Week 5 to 6 — Visual design concepts presented, one revision round, final sign-off
Week 7 to 8 — Development sprints; CMS build and any integrations
Week 9 — QA: accessibility, cross-browser and speed testing; content loaded into pages
Week 10 — Launch prep (redirects, analytics, SSL), go-live, and a short stabilisation window

Content writing, SEO groundwork and any third-party integration setup should run alongside design and development wherever possible, not after them. Build a review buffer into weeks 4, 6 and 9. At each stage, ask for a specific milestone: sitemap approval in writing, a signed-off design mockup, a QA report before go-live.

What should you ask an agency to prove their timeline is credible?

Before signing a contract, push for specifics. Ask who will actually be assigned to your project, how often you’ll get status updates, what the sprint or milestone cadence looks like, and what contingency is built in for review delays.

A credible, living timeline includes:

Named dependencies (what’s waiting on what)
Defined testing windows, not “we’ll test before launch”
Firm content deadlines tied to specific dates
A documented change-control process for anything added mid-project

Red flags include a single delivery date with no phase breakdown, no mention of revision limits, and vague answers about who’s actually doing the work.

Your agreement should specify phase sign-offs with named approvers, acceptance criteria for each deliverable, clearly defined buffer policies, and a post-launch support window for addressing issues after launch.

Pro Tip: If an agency can’t tell you their weekly reporting cadence during the sales conversation, that’s usually a preview of how communication will go once the contract is signed.

How does Medway Web Design structure a project timeline?

MedwayWebDesign runs every custom build through a structured kickoff, a documented brief both sides sign, two rounds of design revisions built into the quote, sprinted development, a formal QA checklist, and 14 days of post-launch support as standard. Buffers for review cycles are built into the schedule from day one rather than negotiated after a delay happens.

A typical MedwayWebDesign client timeline mirrors the phase structure above: brief and discovery in week one, sitemap and wireframes by week three, design sign-off by week six, development and QA through weeks seven to nine, and launch in week ten, with contingency days sitting inside each phase rather than tacked onto the end.

Ian Rickard has overseen enough of these projects at MedwayWebDesign to see the pattern clearly: the projects that finish on schedule are the ones where the client treats sign-off dates as real deadlines, not the ones where the agency simply works faster.

Trust in a timeline comes from the process behind it: an example project plan shared at kickoff, a client responsibilities checklist agreed in week one, and a fixed post-launch support window rather than an open-ended promise. Explore MedwayWebDesign’s approach to custom web design for a fuller look at how phases and pricing connect.

Why realistic timelines matter more than fast ones

Most clients arrive expecting a trade-off between fast and good. That trade-off mostly disappears when a disciplined, repeatable process replaces guesswork. What I’ve seen cause real damage isn’t a slow timeline. It’s an unrealistic one that collapses under its first review cycle. Launch day isn’t the finish line either. Post-launch support exists because good sites keep improving after go-live, not despite it.

Get a realistic timeline before you commit to an agency

Most agencies will quote you a single launch date and hope the details sort themselves out. MedwayWebDesign gives you a phase-by-phase schedule with named sign-offs before you sign a contract, so you know exactly what’s expected of you and when, rather than discovering the gaps three weeks into a build.

Before your first meeting, prepare a written brief covering goals and must-have features, gather your brand assets and any existing content, name a single point of contact with approval authority, and list any third-party tools or integrations you need connected. Turning up with those four things ready is the single fastest way to compress the discovery phase without cutting corners.

If you’re ready to see what a realistic schedule looks like for your project, request a timeline review or a fixed-price estimate through MedwayWebDesign’s business web design guide, and get a phase-based plan back before you commit to anything.

Frequently asked questions about website design timelines

How long does it take to design and build a small business website?
Most small business websites take 4 to 12 weeks from signed brief to launch, depending on page count, custom features and how quickly content is delivered.

What’s the fastest a website can realistically launch?
A simple landing page or 5-page brochure site with content ready on day one can launch in 3 to 4 weeks. Anything faster usually means skipping QA or using a template with minimal customisation.

Why do web design projects take longer than the initial estimate?
Delays in web design projects are often caused by late content delivery, mid-project scope changes, and feedback arriving from multiple stakeholders at different times. A fixed review process and change-control agreement prevent most of this.

How much time should be allowed for post-launch fixes?
Plan for 2 to 4 weeks of stabilisation after go-live, and expect organic search visibility to take 3 to 6 months to show measurable improvement.

What should I ask an agency before agreeing to a timeline?
Ask for a phase-by-phase schedule with named sign-off points, their built-in contingency for review delays, and who specifically will be working on your project week to week.

Sources

Custom Web Development Process: From Idea to Launch

A realistic website design timeline for small businesses