One of the most common questions from NZ businesses starting a website project - and one that gets vague or unrealistic answers far too often. "It depends" is true but unhelpful. Here are realistic timelines based on what actually happens in practice.
The Short Answer by Project Type
| Website Type | Realistic Timeline | |---|---| | DIY website builder (Wix, Squarespace) | 1-4 weeks (your time only) | | Template-based, built by a designer | 3-6 weeks | | Custom website, 5-10 pages | 6-10 weeks | | Custom website, 10-20 pages | 10-16 weeks | | E-commerce (standard) | 10-18 weeks | | E-commerce (complex/custom) | 4-9 months | | Web application or custom platform | 4-12+ months |
These are realistic timelines from project start to launch. They assume a competent designer, reasonable client responsiveness, and no major scope changes during the project.
What "Project Start" Actually Means
A note on when the clock starts: in most agency engagements, "project start" is when the brief is agreed and the deposit is paid - not when you first make contact.
Initial conversations, proposals, revisions to proposals, contract review, and invoicing typically add 1-4 weeks before a project formally begins. This isn't wasted time - it's essential setup - but it matters if you have a hard deadline.
If you need a website live by a specific date, work backwards from that date accounting for both the pre-start process and the build timeline.
The Phases of a Custom Website Build
Understanding what's happening during the build explains why it takes as long as it does - and where delays usually come from.
Discovery and briefing: 1-2 weeks
The designer needs to understand your business: your services, your customers, your competitors, your goals, your brand, what you do and don't like. Good briefing at this stage saves significant time later. Poor briefing leads to design work that misses the mark.
This phase typically involves a questionnaire, a discovery call, and sometimes a review of your existing materials (old website, brochures, social media).
Design: 2-4 weeks
For a custom website, the designer creates the visual look and feel of the site - typically starting with the homepage, then key interior pages. You review and provide feedback. Revisions happen. Further review. Final sign-off.
This is the phase most dependent on client responsiveness. A client who takes two weeks to review designs adds two weeks to the project. A client who reviews within 24-48 hours and gives clear, actionable feedback keeps the project moving.
Development: 2-6 weeks
The approved designs are built into a working website. Pages are coded, content is placed, forms are connected, navigation works, mobile responsiveness is implemented, speed is optimised.
This phase is largely internal to the developer - you'll typically see a staging site partway through and again at the end.
Content population: 1-3 weeks (often the bottleneck)
If you're providing your own content, it needs to be supplied before or during development. This is the single most common source of project delays in NZ web design.
If you haven't written your service descriptions, gathered your photos, finalised your team bios, confirmed your NAP (name, address, phone), and organised your other content before development starts, the project will wait for you. Sometimes for weeks.
Testing and revisions: 1-2 weeks
The completed site is tested across devices and browsers. Issues are fixed. You review the final result and request any remaining changes. A final round of amendments before launch.
Launch: 1-3 days
DNS changes, final checks, search engine notifications. This part is usually fast once everything is ready.
What Causes Projects to Run Late
Based on what consistently delays NZ website projects:
Client content not ready. The most common delay by far. If you haven't prepared your content before development begins, the project waits. The solution is to have all written content, photos, and other materials ready before your project starts - or to include copywriting and photography in the project scope.
Slow client feedback. Designers need timely responses to move forward. A feedback deadline of "whenever you get a chance" consistently extends projects by weeks.
Scope changes during the build. Adding pages, changing services, deciding you want e-commerce after all, or rethinking the whole positioning mid-project all extend timelines and usually cost more. Changes are inevitable - significant ones mid-build are costly.
Decision-making delays. If multiple stakeholders need to approve design work and they can't align, the project waits. Assign one decision-maker on your side before the project starts.
Technical problems. Domain transfers, email migration complications, integration issues with third-party tools. These are usually resolvable but take time.
Designer capacity. Agencies run multiple projects simultaneously. If a key person is sick, or if a more complex project than expected is consuming resources, your project can be delayed even when you've done everything right. This is worth discussing upfront: how many projects does the designer carry simultaneously, and what's the escalation path if there's a delay?
How to Run Your Project Faster
The things that most reliably accelerate a website project are all on the client side:
Prepare all content before the project starts. Write your service descriptions, gather your photos (or arrange photography early), finalise your contact details, prepare your team bios, and collect any other content you want on the site. Having this ready at project start saves weeks.
Designate a single decision-maker. If your business has multiple owners or stakeholders who need to approve the website, agree internally on who makes the final call. Design by committee is slow; design with a clear decision-maker is fast.
Respond to feedback requests within 24 hours. When your designer sends you something to review and asks for feedback, respond within a business day. "I'll get to it this week" adds a week. "I'll look at it today or tomorrow" keeps the project moving.
Be specific with feedback. "I don't like this" or "can you make it pop more" sends a designer back to the drawing board without useful direction. "The blue feels too cold - can we try something warmer?" or "the headline is too long - can we try a shorter version?" gives them something to work with.
Trust the process. The biggest delay in many projects is a client who approves something, then changes their mind three times over the next two weeks. Make decisions, commit to them, and move forward.
Urgent Timelines: What's Actually Possible
If you need a website in two weeks, what can you get?
In two weeks: a well-configured DIY platform (Squarespace, Wix) that you're building yourself, or a very simple template-based site from a designer who can prioritise you. Not a custom build.
In 4-6 weeks: a good template-based site from a responsive designer with content ready from day one. Possible if content is ready and feedback is fast.
In 6-8 weeks: a proper custom site is feasible at the faster end of the range if scope is well-defined, content is ready, feedback is fast, and the designer has capacity. Not guaranteed.
If you have an urgent deadline and want a genuine custom result, discuss it explicitly before engaging a designer. Ask: "Is this timeline achievable for you given your current workload?" Get an honest answer.
One More Thing Worth Knowing
Timeline and quality are related. The agencies that consistently deliver in "2 weeks" for custom websites are almost always using pre-built templates and swapping content - not building custom. That's not inherently wrong, but it's worth knowing what you're getting.
Genuinely custom work requires time for design, development, and testing that physically cannot be compressed below certain limits. When a quote promises a custom result on an extremely short timeline, ask specifically what "custom" means in that context.
How We Work at Local Site Growth
Our custom website projects typically run 6-10 weeks from project start to launch, depending on scope and content readiness. We're honest about timelines upfront and don't make commitments we can't keep.
Before any project starts, we build a free first page demo of your website - so you can see the actual design work for your business before committing to anything. This also gives both sides a clear reference point for design direction before the full project begins, which genuinely saves time in the design phase.
If you're planning a website and want to understand what the project would look like for your specific business, start with the free first page demo here.
Working out whether to redesign or rebuild? Website Redesign vs New Website: What's Right for Your NZ Business? covers the full decision.
Ready to compare agencies? How to Choose a Web Designer in NZ covers the questions that matter.