A Queenstown retailer got two quotes last month for what looked like the same project: $18,000 and $54,000, ex GST. The scope documents were close to identical on paper. One assumed a finished set of design files already existed. The other assumed nothing had been decided yet, including which pages a visitor would see first.
Neither quote was dishonest. They were pricing two different jobs, because "website developer" and "website designer" get used interchangeably across job ads, agency sites and casual conversation in a way that rarely matches what the two roles actually do. For a business signing off a five or six-figure redesign, that confusion gets expensive fast.
The two disciplines solve different problems. A designer decides what a visitor sees, how a page reads and where their eye goes next. A developer builds the thing that makes it work: the code, the platform configuration, the integrations, the load time. Confusing the two is how projects stall halfway through, with one side waiting on a deliverable the other side assumed wasn't theirs to produce. Treating one as a lesser version of the other is where the first quote goes wrong.
What a website designer actually does
A website designer works on the experience before a single line of code exists. That covers wireframes, page layout, typography, colour and the visual hierarchy that tells a visitor what matters first, second and third on a page. Good design work also covers information architecture: which pages exist, how they connect to each other and what happens when someone lands on your site from a Google search instead of your homepage.
Most New Zealand designers now work in Figma, producing a full set of page mockups a developer can build from. A designer's job is finished when those mockups represent every state a page can be in, including desktop, mobile, hover states, form validation and an empty product listing with no stock left. None of that is code. All of it decides whether the eventual site converts or just sits there looking finished.
What a website developer actually does
A website developer takes that design and turns it into a working site. On Webflow, that means building inside Webflow's visual development environment: structuring the CMS, setting up interactions, configuring responsive breakpoints and making sure the site performs the way the mockups promised. On Shopify, it means theme development, checkout configuration and store setup inside Shopify's own architecture.
Development also covers what a design file can't show: page speed, accessibility and structured data for search engines. It covers the technical side of integrations with the tools a business already runs too, such as Xero, Klaviyo or an ERP system. Skyrocket scopes, manages and facilitates those integration connections rather than building them directly. The technical build for a payment gateway or an accounting sync sits with the relevant platform or app, and a developer's job is making sure it's configured correctly and talks to the rest of the site properly.
Development is also where a site gets tested against real browsers, real devices and real content, instead of a single perfect product photo standing in for a whole catalogue.
None of this shows up in a client meeting the way a mockup does, which is part of why it gets undervalued in a proposal. Loading in under two seconds on a phone, passing Core Web Vitals and holding up when someone adds forty products to a Shopify store overnight are development outcomes. The design underneath can be excellent, and none of that follows automatically from it.
Why the line blurs in a small, senior team
On paper, design and development are two different jobs. In a five-person specialist studio, they're often the same conversation. At Skyrocket, our web developers in Auckland and Queenstown work directly alongside designers rather than down the hall from them. A designer building a Shopify store thinks in Shopify's theme architecture from the first sketch, because Shopify design and development happen concurrently, not as separate stages with a handoff in between. There's little point producing a polished mockup for a product page the platform can't actually render that way.
Webflow narrows the gap further. Because Webflow is a visual development tool, the same specialist frequently designs and builds a page in one sitting, moving between layout decisions and technical ones without switching software or handing off a file. A tight team, rather than a chain of account managers and subcontractors, leaves fewer places for a decision to get lost between the person who imagined a page and the person who shipped it.
This matters more on ecommerce projects, where a pricing table, a shipping rule or a discount structure is as much a design decision as a technical one. A five-person team that includes senior designers and senior developers working the same brief can settle a question like that in a single conversation. Split across three separate vendors, the same question turns into three email threads and a week of waiting.
What a web development company in Auckland is actually quoting you
When a web development company in Auckland sends through a proposal, the number attached to it depends entirely on which of these two jobs is included. A quote from website developers Auckland businesses hire for build-only work assumes design decisions are already made. A quote covering both design and development includes strategy, wireframes, visual design and the build itself, which is why two documents describing what looks like "a new website" can land tens of thousands of dollars apart.
Ask directly what stage the quote assumes you're starting from. A studio that has properly scoped the work can tell you, in one sentence, whether you're paying for design, development or both. For a longer breakdown of what's included at each stage of a build, see how web development services get packaged versus sold separately.
Why the distinction helps you ask better questions
Once you know which job you're hiring for, the questions get sharper. Are you being shown a Figma file or a live, clickable build? If it's a Webflow project, does the team building it also design inside Webflow, or does that part get handed to a subcontractor? For a Shopify project, does the person quoting understand that design and build happen inside the platform together, or are they pricing it like a print job that gets uploaded once it's finished?
These aren't procurement questions about timelines or turnaround. They're the difference between hiring a team that understands how your site will actually get built and one that discovers the gaps after the invoice is signed. Our guide on choosing a website agency in New Zealand covers the wider set of questions worth asking before you commit to either.
Working out what stage you're actually at
Most businesses approaching a website project sit in one of three positions, and each needs a different kind of help.
- You have brand guidelines and content but no site structure. You need design work first: wireframes, page layout and a visual system a developer can build from.
- You have a full set of approved design files and need someone to build them. You need a developer, and one who works fluently in the platform your designs were made for.
- You have neither, and you're starting from a blank page. You need a team that runs design and development together, so the two decisions get made against each other instead of in isolation.
Most established NZ and Australian businesses land in the third position. A Webflow build or a Shopify store rebuild rarely benefits from strategy sitting with one specialist, layout with another and code with a third. Fewer handoffs between the person who decided what the site should do commercially and the person who made it do that means fewer chances for the original brief to get lost along the way.
Common questions
Is a website developer the same thing as a website designer?
No. A designer decides how a site looks and how a visitor moves through it. A developer builds the working version of that design, including the platform setup, integrations and performance. Some specialists cover both, but the two skill sets are distinct.
Do I need to hire a designer and a developer separately?
Not always. Many established businesses get a better result from a small team where design and development happen together, particularly on Shopify, where the two are built inside the same platform instead of handed off between separate files.
What does a web development company in Auckland actually deliver?
It depends entirely on the scope written into the quote. Ask specifically whether the price covers design, development or both, and whether one team handles all of it or parts get subcontracted out.
Can one person really do both design and development well?
Yes, particularly on Webflow, where design and build happen inside the same visual tool. A senior specialist working across both disciplines removes the handoff between the person who designed a page and the person who built it.
How much do website developers in NZ charge?
Rates vary by seniority and scope, and pricing should always be quoted ex GST. A build-only quote from website developers NZ businesses hire for development work costs less than one covering strategy, design and development combined, because fewer decisions are still open by the time it's written.
What's the difference between a freelancer and a web development company?
A freelancer is one person covering both design and development, which suits a smaller, contained project. A web development company brings a team of specialists instead, which matters more once a project involves ecommerce, integrations or a platform migration needing several skill sets at once.
If you're not sure whether your next project needs a designer, a developer or both, that's a five-minute conversation rather than a guessing game. Get in touch and we'll tell you plainly where your project actually sits before you sign anything.
