You signed the proposal three weeks ago. The invoice cleared, the kickoff call happened and since then your inbox has held exactly two emails from the studio: a request for brand assets and a link to a shared drive. No mockups. No preview link. If this is your first serious website development project in NZ, that gap between signing and seeing something can feel like the project has stalled.
It hasn't. A considered build spends its early weeks on work that never produces a screenshot: stakeholder interviews, sitemaps, content audits, technical decisions about how the site will actually run once it's live. None of it looks like progress from the outside. All of it determines how many rounds of revision the visible stages need later. If you're still comparing studios rather than mid-build, how to choose a website agency in NZ covers what to ask before you sign anything.
Here is what happens between the signature and the launch, stage by stage, with the rough timeframes a New Zealand build runs to and where each one tends to run long.
Discovery and strategy
Before any design work starts, we spend time understanding the business behind the site: who the customers are, what the site needs to achieve commercially, what content and systems already exist and what competitors in the category are doing online. In practice this means interviews with sales and marketing, a review of the last twelve months of analytics and a look at whatever CRM or ERP the new site needs to sit next to.
For a standard site this runs one to two weeks. A multi-brand business, or one with franchise or dealer structures, can push discovery closer to three weeks, because there are more stakeholders to get aligned before any design work begins.
This phase feels slow because there's nothing to look at yet. Rushing it is the surest way to end up reworking the sitemap in week nine, once someone senior finally sees the plan and asks why the site doesn't reflect how the sales team actually talks to customers.
Information architecture and content strategy
Once discovery findings are in, the site's structure gets mapped: what pages exist, how they connect, what the CMS needs to hold and how content moves through the system from a blog post to a product page to a case study. For a standard build this takes three to five working days.
Clients rarely see a sitemap and feel like the project has moved. But a site built on a proper structure holds up as the business adds products, locations or services later, and one built without it tends to need restructuring within eighteen months, which means paying for the same work twice.
Design
This is the stage clients can finally see, which is why it feels like the whole project even though it's one part of several. Wireframes come first, laying out structure and hierarchy without colour or type. Visual design follows, then two or three rounds of feedback before sign-off. For a considered NZ build this runs three to five weeks, longer for a site with a large product catalogue or several page templates to design.
Design moves faster and holds together better when the discovery and architecture work before it was actually done. Without a strategic brief to measure the work against, revision rounds have nothing to converge on, so they keep going. Design and development are different disciplines with different skill sets, which is one reason a single generalist covering both often stalls on one or the other. The difference between a website developer and a website designer covers what each role actually does.
Development
Once design is signed off, development on Webflow turns the static designs into a working, interactive site: building the CMS structure, setting up interactions and animations and configuring the site so your team can manage content without calling in a developer. A standard Webflow build takes four to six weeks from signed design to a site ready for content.
Shopify runs differently. Design and development happen at the same time rather than one after the other, because Shopify's theme architecture means the visual design gets built directly inside the platform rather than handed over as a separate file. A Shopify build for a standard catalogue runs five to eight weeks from the start of that combined stage, longer where wholesale pricing tiers, subscription logic or an in-store POS connection are part of the scope.
Most established businesses arrive with systems the new site needs to work with: an accounting platform such as Xero or MYOB, a freight and fulfilment tool for shipping quotes and tracking, or a booking system for appointments and consultations. We scope how each one needs to function inside the site, manage the setup and facilitate the connection between the two systems. The technical build of the connection itself sits with the relevant platform or app vendor, whether that's Shopify's app ecosystem, a Webflow integration or the third-party tool's own API. Getting this scoped properly during development, rather than discovered during QA, is what keeps a freight calculator or a booking widget from turning into a change order in week eleven.
This stage is also where most of the remaining technical complexity sits: custom functionality, page speed work and testing across browsers and devices. What web development services actually include breaks this stage down in more technical detail, for anyone who wants the full picture before comparing quotes.
Content population and QA
Real content goes into the real site: copy, images, product data, case studies, downloadable resources. This stage often runs longer than the kickoff timeline suggested, because content that looked finished in a planning document turns out to need editing once it sits inside an actual page next to an actual photograph. Budget one to two weeks for a standard site, three if product photography or data still needs collecting for an ecommerce catalogue of any size.
Quality assurance means testing every page, every form and every checkout flow across the browsers and devices real customers use, not just the ones on the studio's desks. Catching a form field that doesn't fire before launch costs an afternoon of testing. Catching it after launch costs however many enquiries went missing while nobody noticed.
Launch and the weeks after
Launch itself is often anticlimactic: a domain switch, a final check across every page and the site goes live. The technical work in this stage matters more than the moment itself: DNS configuration, redirects from every old URL so search rankings carry across, analytics and conversion tracking set up correctly and monitoring for anything that only shows up under real traffic.
The four to six weeks after launch carry more weight than the launch date itself. Search engines need time to re-crawl and re-index a new site structure. Real visitors behave differently than the sitemap predicted during planning. Minor issues that QA didn't catch tend to surface once traffic is real rather than simulated, and a site that underperforms in this window is one reason to work through why a website isn't converting rather than assume the design is at fault. This is the period Skyrocket's website support and maintenance covers, so issues get fixed before they cost enquiries.
How long website development takes in NZ, added up
Put every stage together and a considered website development project in NZ runs ten to sixteen weeks from signed proposal to launch, for a standard Webflow marketing site or a Shopify store of moderate complexity. A large multi-brand site, a wholesale Shopify Plus build or a catalogue running into the thousands of SKUs pushes past that range, sometimes well past it.
How that time gets spent counts for more than the total. A project weighted toward development and light on discovery reaches a visible result faster, then spends longer revising it. A project that spends real time on the first two stages spends less time revising the last three.
What happens when a stage gets cut short
Compress discovery and the cost turns up around week nine, when a stakeholder who wasn't in the first round of interviews sees the site plan and asks why it doesn't reflect how the business actually sells. Fixing that after wireframes exist means redoing them from scratch rather than adjusting a few screens.
Skip information architecture and the CMS model needs rebuilding once a third content type doesn't fit the structure a developer improvised mid-build. Skip or shorten QA and the first sign lands in the support inbox in the opening week after launch: an enquiry form that stopped submitting on one specific browser, found by a customer rather than a tester.
Common questions
How long does website development take in NZ?
For a standard Webflow marketing site or a moderate-complexity Shopify store, ten to sixteen weeks from signed proposal to launch is realistic. Larger catalogues, wholesale pricing structures or multi-brand sites take longer, and website design cost in NZ covers how that timeframe tends to track against budget.
What's the difference between web design and web development?
Design covers how the site looks and how a user moves through it: wireframes, visual design and the interface. Development is the build that makes it work: CMS structure, interactions, integrations and the code underneath. Website developer vs designer goes into the distinction in more depth.
Do we need all our content finalised before development starts?
No, but it helps. Development can proceed with placeholder content once the CMS structure and templates are built. What matters is having real copy, images and product data ready by the content population stage, since a late-arriving asset library is the most common place for a timeline to pick up extra weeks.
Can our existing accounting or freight system connect to the new site?
In most cases, yes. We scope how the connection needs to function commercially, manage the setup and facilitate the integration during development. The technical build of the connection itself sits with the platform or app vendor involved, whether that's Xero, a freight tool or a booking system's own API.
Why does the Shopify timeline look different to the Webflow one?
Because the two platforms build differently. Webflow separates design from development, so design gets approved before build starts. Shopify's theme architecture means visual design is built directly inside the platform, so design and development run at the same time rather than one after the other.
What if we're not happy with a design round?
A standard scope includes two or three rounds of feedback on wireframes and visual design before sign-off. Extra rounds are possible but tend to run smoother when there's a clear brief from the discovery stage to measure the work against, rather than open-ended preference.
If you're weighing up a rebuild and want to know what should sit behind the number in a quote, that's the process above, whether the build runs on Webflow or Shopify. Get in touch with Skyrocket to talk through what a realistic timeline looks like for your project.
