Every client asks this question at some point in the first conversation. The answer most agencies give is "6–8 weeks" and then the project actually takes 14. The honest answer is that the timeline depends on specific things that are knowable before the project starts — and once you know them, you can plan the real timeline accurately.

This post is the breakdown of what actually consumes time in a custom website build, where the variance comes from, and how to spot the warning signs that a project is going to run over.

The honest timeline for a small business custom site

Assuming a 5–10 page brochure site with a contact form and a CMS, built from scratch, here's the breakdown:

Week 0 — Discovery and scope: 3–5 business days. One kickoff call, sitemap alignment, scope confirmation, written proposal. Most of the "time" here is waiting for the client to review and sign.

Week 1 — Strategy and wireframes: 5 business days. Information architecture decisions, page-by-page wireframes in Figma, content plan. Ends with a wireframe review call and client sign-off.

Weeks 2–3 — Design: 8–10 business days. High-fidelity mockups in Figma for every page, desktop and mobile. One round of design revisions. Ends with a design review call and sign-off.

Weeks 4–5 — Development: 8–10 business days. Hand-coded build, pulling from the approved designs. Staging link goes live early in this phase. Client reviews pages daily.

Week 6 — Testing, content migration, launch: 3–5 business days. Final QA, content finalisation, DNS cutover, 301 redirects, sitemap submission, launch day.

Week 7 onwards — 30 days of free iteration: included in scope but counted separately. Bug fixes, copy tweaks, content updates.

Total from kickoff to launch: 6 weeks for a well-run project. The scope above matches what most Australian small business sites actually need.

Why most projects overrun

Projects that take longer than 6 weeks usually aren't overrunning on the development side. They're overrunning on one of four client-side blockers.

Blocker 1: Content isn't ready

Every website build needs copy for every page and imagery for every section. The agency can lay out placeholder text and placeholder images during the build, but the site can't launch until the real content exists.

Most businesses underestimate how long copywriting takes. A well-written 6-page service site has about 4,000–7,000 words of copy — professional, brand-appropriate, SEO-aware. That takes 2–3 full days of dedicated writing time, not "I'll get to it next week."

If content isn't ready by week 3, the project stalls. The agency can't deliver week-4 development if the copy they need isn't available. Week 4 becomes week 6. Week 6 becomes week 10.

How to avoid it: start content work in week 0. Block time on your calendar for writing. Consider hiring a copywriter if you don't have the time. Have content ready by week 3 or agree upfront to a 3-week content buffer at the end.

Blocker 2: Stakeholder sprawl

A project where one person has final decision authority ships in 6 weeks. A project where three people need to approve everything ships in 10–12 weeks. A project where an undefined "committee" weighs in ships in 16+ weeks.

Every approval cycle adds 2–4 days to the timeline because someone is waiting for feedback, someone else is waiting for a reply, and the feedback when it arrives conflicts with earlier feedback from someone else.

How to avoid it: name one decision-maker upfront. They can consult others, but the final sign-off comes from them. Agencies that won't start without a named decision-maker are protecting you from this trap.

Blocker 3: Scope creep

"Can we just add a quick newsletter popup?" is a two-line request that adds two days to the project. "Can we also have a pricing calculator on the services page?" is another week. "Oh and a client testimonial slider" is another three days.

Each individual request is small. Together they add 20–30% to the timeline. Agencies that don't push back on scope creep end up with projects that run long — and the client blames the agency, even though the client is the one adding scope.

How to avoid it: agree the scope in writing at kickoff. When new ideas come up, write them down as "future enhancements" rather than "let's add them now." Most of them won't actually be implemented, and the ones that will can wait for a v2.

Blocker 4: The "one more round of revisions" trap

Most agencies include 2 rounds of design revisions in the scope. Clients who want a third round either pay extra or extend the timeline to accommodate it.

The classic failure mode: the client approves the designs in week 3, the development starts in week 4, the client reviews the staging site in week 5 and realises they want to change the hero layout. That's a design revision happening during development, which means designers re-open the Figma file, developers wait, then developers re-implement the changes.

Every "one more small change" at this stage adds 3–7 days to the project.

How to avoid it: take design review seriously. Review the Figma mockups on different devices, read every page of copy, imagine showing the site to your best customer. Catch the problems before development starts, not after.

The projects that actually ship in 4 weeks

Some projects ship faster than the 6-week average. These usually have:

A single, empowered decision-maker who can approve things immediately
Content that's already written before kickoff
A scope with 4–5 pages, not 15
A client who trusts the agency's design judgment and doesn't micromanage
No custom integrations (no booking flows, no custom forms, no third-party APIs)
An agency that isn't juggling too many projects at once

If all six apply, a 4-week timeline is realistic. Miss any of them and you're back to 6 weeks or more.

The projects that take 10+ weeks

Projects that run to 10+ weeks usually have specific complexity that justifies it:

E-commerce with custom product configurator: 8–12 weeks, fair
Multi-language sites: 9–12 weeks, fair
Sites with integrated booking/scheduling flows: 8–11 weeks, fair
Sites with user accounts and authentication: 10–14 weeks, fair
Multi-site migrations from legacy platforms: 10–16 weeks, fair

If your project has any of these, expect a longer timeline. The agency isn't slow — the work is bigger.

What "6 weeks" actually means in practice

When an agency says "6 weeks from kickoff to launch", it means: 6 weeks of calendar time where both the agency and the client are actively contributing. It does not mean 6 weeks of elapsed time regardless of what the client is doing.

If the client takes 2 weeks to provide content, the timeline becomes 8 weeks. If the client takes 3 days to respond to feedback each time (instead of same-day), that adds 2 weeks over the course of the project. If the client changes the scope mid-build, that adds another 2–4 weeks.

The honest version of "6 weeks" is: 6 weeks from kickoff to launch, assuming the client responds within 24 hours to every review request and the content is ready when it's needed. Projects that violate those assumptions run longer, and it's not the agency's fault.

How to set yourself up for an on-time project

Four things to do before you kick off any custom website build.

Write the copy in advance. All of it. Every page, every section. Even rough drafts help. You can refine during the project, but starting with nothing adds weeks.
Name the decision-maker. One person. Write their name in the project brief. Everyone else is a consultant, not an approver.
Agree the scope in writing. Pages, features, integrations, everything. If it's not in the scope doc at kickoff, it's not in the build.
Commit to 24-hour feedback turnaround. Block time on your calendar during the project. Each delay on your side compounds into the timeline.

Do those four things and any decent agency can ship your site in 6 weeks. Skip them and the project will take 10.

The honest recommendation

If someone quotes you "4 weeks" for a custom website build and the project involves anything non-trivial, be sceptical. Either the scope is smaller than you think, or the agency is optimistic and will be late.

If someone quotes you "12+ weeks" for a simple small business brochure site, be sceptical in the other direction. Either the agency is slow, or the scope is hiding complexity you don't need.

The honest range for most small business custom websites is 6–8 weeks from kickoff to launch, assuming reasonable client responsiveness and no major scope changes.

If you want us to scope a realistic timeline for your specific project, book a free audit. We'll review what you have, what you need, and give you a written timeline and fixed-price proposal. No pressure, no commitment.