A quote lands with one line that reads "Website development: $22,000" and nothing underneath it. It's a single number sitting next to a word that gets used to cover everything from a Squarespace template swap to a full commerce build with live freight rates. The client signs anyway, because by that stage in the process asking "what exactly is development" feels like admitting you don't know something you should.
You should ask. Development runs through a sequence of distinct, chargeable stages, each with its own deliverables, and each one is where a template install and a proper build start to look very different from each other.
This piece breaks down what actually happens inside "web development": the front-end build, the backend and CMS setup, integrations, quality assurance and launch. If you want the difference between a designer and a developer, or how much the whole project should cost, we've covered that in how to choose a website agency in NZ and website design cost in NZ. This one is about what you are paying for once design is signed off and someone actually has to build the thing.
Development, design and "the build" aren't the same thing
Design decides how a page looks and how a user moves through it. Development turns that decision into a working site: code, structure, data and the systems that keep it running after launch. A designer can hand over a flawless Figma file and the site still won't function if the development underneath it is thin. Where it gets confusing is the word "build", which agencies use loosely to mean the entire project. Inside a proper scope, the build breaks into stages you should be able to see itemised: front-end, backend, integrations, QA, launch. A quote that skips straight from "design" to "launch" with one number in between has skipped the work along with the paperwork.
The front-end build: what you're actually paying for
Front-end development is the part clients assume they already understand, because it's the part they can see. It's also where a lot of the real cost sits.
A properly built front end includes:
- Semantic, structured markup for every page template, not just the homepage, built to hold real content lengths rather than the placeholder copy in the design file
- Responsive behaviour tested across breakpoints, so the layout holds up on a 13-inch laptop and a phone in landscape, not just the 1440px frame the designer worked in
- Interactions and micro-animations built to match the intended feel, from hover states to scroll-triggered reveals, without dragging page speed down in the process
- Accessibility basics: proper heading hierarchy, alt text fields, colour contrast that passes, keyboard navigation that actually works
A template install can look identical to this in a screenshot. The difference shows up three months later, when a client asks for a new page type and discovers the "site" is a handful of fixed pages with no underlying system to extend. Real front-end development is built so a new page type slots into an existing system rather than forcing a rebuild. A skin over a theme has nowhere to grow.
Backend and CMS setup: the part clients rarely see and always feel
This is the stage that decides whether your marketing team can update the site themselves in eighteen months, or whether every content change becomes a support ticket. A real backend scope covers content models built around how your business actually operates, not the platform's default fields. If you sell across three product categories with different attributes, the CMS needs collections that reflect that, with fields for the information your team will actually need to fill in on a Tuesday afternoon with no developer watching over their shoulder. It covers permission structures, so a marketing coordinator can publish a blog post without also being able to touch pricing. It covers URL structure and redirect logic set up correctly the first time, because fixing it after the site has been indexed is a slower, costlier job than doing it before launch.
On a Shopify build, this stage runs alongside the front end rather than after it. Shopify's theme design happens inside Shopify's own architecture as part of the build itself, so backend configuration, product data structure and the visual design are developed together, not handed off in sequence. If an agency's timeline shows "design" finishing before "Shopify development" starts, ask them to walk you through how that actually works in practice.
Integrations: what gets scoped, tested and handed over
Most established businesses aren't building a website in isolation. There's an accounting system already in use, a freight provider with existing rates, an email platform with a subscriber list that has to survive the migration and often an ERP or inventory system running the warehouse. Development work here means mapping exactly how each of those systems needs to function inside the new site: what data has to sync, how often and what happens when a sync fails. We scope, manage and facilitate these connections, working with the relevant platform or app partner to get them configured correctly, tested against your real data and handed over with clear documentation of how they work. For anything beyond a standard payment gateway or email tool, such as an ERP feed or complex stock sync, we've written a longer piece on complex Shopify integrations for ERP, inventory and accounting that goes into how that scoping actually happens.
This is also where a lot of quotes go quiet. "Integrations included" on a proposal with no list of which systems and no explanation of who owns the connection after launch is doing a lot of work to avoid a conversation about scope.
Quality assurance: the stage that gets cut first when timelines slip
QA is unglamorous, which is exactly why it's the first line item an agency drops when a deadline gets tight. It's also the stage most likely to determine whether launch day goes smoothly or turns into a support call. A real QA pass covers cross-browser testing on the browsers your actual customers use, not just the one on the developer's laptop. Every form on the site gets submitted with real data and checked against where that data is supposed to land. Page speed gets checked against a target, not a vague sense that it "feels fast". A full 404 and redirect check against the old site's URL structure stops search rankings built up over years from resetting to zero on launch day. Skipping this stage doesn't remove the cost. It moves the cost to after launch, when you're the one finding the broken form instead of the agency.
Launch: more than pointing a domain at a new server
Launch day has its own checklist, and a rushed one is where avoidable problems show up in front of customers rather than in a staging environment. Proper launch development includes DNS and SSL configuration confirmed in advance, analytics and tracking set up and verified before the switch rather than after, a final redirect map applied and tested and a staged rollback plan in case something needs to be reverted quickly. If your business runs on Shopify and you've been through a launch where the previous developer disappeared partway through, our piece on what to do when your Shopify developer goes MIA covers how to pick that project back up without starting from zero.
How to tell a real development scope from a template install with a different label
The clearest signal is specificity. A real scope names the CMS collections that will be built, the integrations that will be configured and the browsers and devices that will be tested. A template install describes the outcome ("a modern, responsive website") without describing the mechanism that gets you there. Ask three questions of any development quote. First, what happens to my content structure if I want to add a new product category or service line in a year. Second, which third-party systems are being connected, and how is each one tested before launch. Third, what does the QA pass actually check, item by item, rather than as a single line that says "testing". An agency running a proper development process will have specific answers to all three, because they're already written into the scope document.
What this actually costs
Development is often the largest single line in a website build, because it's the stage where the most hours go in and the most can go wrong if it's rushed. Pricing varies by platform and complexity: a Webflow build for a content-led business sits differently to a full ecommerce build with product variants, freight rules and an ERP connection behind it. For a full breakdown of what drives the price up or down across a typical NZ project, see website design cost in NZ. If you're an agency or in-house team that needs development capacity without hiring, our white label website development service covers that gap.
Common questions
What's the difference between web design and web development?
Design decides how the site looks and how a visitor moves through it. Development builds the working site behind that design: the code, the content management system, the integrations and the testing that make it function. You need both, and they're costed as separate stages within the same project.
How long does website development actually take?
For a considered business site on Webflow, expect the development stage to run six to ten weeks depending on the number of page templates and integrations. A Shopify build with product data migration, custom app connections and freight configuration often runs longer, ten to fourteen weeks, because design and development happen concurrently within Shopify's architecture rather than one after the other.
Can I just use a website builder instead of paying for development?
You can, and for a very simple site with no integrations and no growth plans, it might be enough. The gap shows up once you need a CMS structure that matches how your business actually sells, a connection to your accounting or freight system, or a page speed and accessibility standard that a drag-and-drop template wasn't built to hit.
What does "integrations included" actually mean in a quote?
It should mean a named list of systems being connected, such as Xero, Klaviyo or a specific freight provider, each scoped, configured and tested against real data before launch. If a quote uses the phrase without naming the systems, ask for the list before signing.
Do I need to test the site myself before launch?
You should still walk through the site yourself before it goes live, particularly the forms and checkout flow if you're running commerce. A proper development process includes its own QA pass, but a second set of eyes from someone who knows your business catches issues a QA checklist won't.
What happens if my developer disappears partway through the project?
It happens more often than most business owners expect, particularly with freelance Shopify developers juggling several clients. The fix depends on how much documentation exists and how the codebase was structured. We've written a full guide on what to do when your Shopify developer goes MIA covering how to assess the damage and pick the project back up.
If you're staring at a quote with one line item and a number next to it, or trying to work out whether your last build actually included the development it was billed for, we're happy to walk through it with you. Get in touch at https://www.skyrocket.co.nz/contact.
