Why Are Web Development Quotes So Different?

Four things explain nearly all of it: scope (the cheap quote priced fewer things, usually without saying which), who you hired (agency overhead, freelancer time and offshore volume are three different cost bases), design depth (template, semi-custom or built from scratch), and what happens after launch (support and maintenance included or excluded). Only one of those four is about skill. Three are about what got counted.

Same brief, same meeting, wildly different numbers. Here's what's actually behind the gap — and which parts of it are legitimate.

Got three quotes and no way to compare them? Send them over and I'll show you which line items genuinely differ — free, no strings. Get in touch.

1. You didn't send the same brief

You described the project verbally, three times, slightly differently. One developer heard "booking system", one heard "contact form", one heard "we'll figure that out later" — and all three priced what they heard.

The fix is one written brief sent to everyone. Most of the variance disappears immediately, and the differences that remain are the ones worth examining. How to compare web developer quotes has the checklist for reading them once they arrive.

2. Different business models, genuinely different costs

None of these is a scam. They're different products, and the mistake is comparing their prices as though they aren't. Full bands at Web Maniacs. One Auckland studio publishing its own numbers is blunt about the gap: CBD agencies typically quote $15,000–$30,000+ for projects lower-overhead providers deliver for $4,000–$8,000, and attributes the difference to offices and account layers rather than capability.

Pay agency rates when you genuinely need agency breadth — brand strategy, multi-channel campaigns, real team depth. Below that, you're buying overhead. Remote developer vs local agency covers the trade-off in more detail.

3. Design is the biggest invisible variable

Two quotes can both say "custom website design" and mean completely different amounts of work. The three levels:

Template

A bought theme, lightly customised with your colours, fonts and logo. The layout decisions were made by someone else for a generic business, and you're adapting to them. Fast, cheap, and genuinely fine for a business that needs to look credible and be found. Published NZ range for a template small-business site: $2,000–$5,000 (Lucid Media).

Semi-custom

A design system — typography, spacing, components, colour — applied to your brand and arranged for your content. Nobody starts from a blank canvas, but the pages are laid out for what you actually sell rather than for a demo. This is where most SMB work lands, and it's the band published at $5,990–$15,000 + GST for 8–15 pages (Fuel Design).

Fully custom

A designer works on your project specifically — research, wireframes, iterations, a design language that's yours. What this buys is decisions: every page considered against what you're trying to make happen, rather than fitted into a layout that already existed.

It's worth paying for when the brand is the product, when the interface is genuinely novel, or when you're competing on experience rather than price. It's not worth paying for on a five-page site for a trades business, and paying custom prices for a template is the most common overcharge in this market. Ask which one you're getting, in writing.

4. The cheap quote excludes what you'll need anyway

Common exclusions that reappear later as invoices:

• Content writing — the single most common one. "Client to supply copy" is a real dependency, and projects stall on it more than on anything else.
• Image licensing — stock photography that's actually licensed for commercial use.
• A CMS, so you can edit the site without paying someone.
• Migration of an existing site's content, and the redirect map that preserves your search rankings.
• Hosting and SSL setup, and who pays for them afterwards.
• Post-launch fixes — whether there's a warranty period on their own work.
• Training and handover — a recorded walkthrough beats a PDF nobody opens.
• Testing — which browsers, which devices, stated explicitly.

Add the exclusions back and the cheap quote often lands mid-range. Sometimes above it — which is why the itemised comparison matters more than the totals.

5. Sometimes the expensive quote is right

The expensive quote isn't automatically padding. It's the correct price when the brief hides real risk, and the honest version of that conversation sounds like this:

• Integrations with systems that break. Your quote depends on someone else's API — its rate limits, its downtime, and what happens when a sync fails halfway through. That risk has to be priced by whoever carries it.
• Data migration. Moving thousands of records from a system that stored them inconsistently is slow, unglamorous work that can't be skipped.
• Permissions and sensitive data. Multiple user types seeing different views of the same records is engineering, not configuration — see what a customer portal costs.
• Accessibility and compliance requirements, when they're contractual rather than aspirational.
• Real traffic. A site that has to stay up under load is a different engineering problem from one that doesn't.

A developer who identifies these before quoting is showing you they've read the brief. One who doesn't mention them is either not seeing them yet, or planning to bill for them later.

When to be suspicious of a low quote

• No written scope, or a single-line total
• No ownership clause covering code, domain and hosting
• 100% payment up front
• A timeline that ignores your content and approvals
• Won't show live work you can open yourself
• Promises specific Google rankings

Any one of these is a question. Two or more is a pattern.

What I'd recommend

Write one brief. Send it to everyone. Ask each quote to itemise what's included and what's excluded — the exclusions list is more informative than the inclusions list, and good providers write it quickly because they've been burned before.

Then expect to pay somewhere in the middle. The cheapest quote is usually incomplete and the most expensive is usually carrying overhead you don't need.

Frequently asked questions

Is a cheap web developer a red flag?

Not by itself — a solo developer with low overhead is genuinely cheaper than an agency for the same work, and NZ published rates bear that out at $65–$175/hr freelance against $220–$320+/hr for a large agency. The red flags are structural rather than numerical: no written scope, no ownership clause, full payment up front, or a price that only looks low because content, migration, training and post-launch support were quietly left out.

How much should a small business website cost in New Zealand?

Published NZ ranges put a template small-business site at $2,000–$5,000, a custom 8–15 page build at $5,990–$15,000 + GST, and a fully custom or premium build at $15,000–$30,000+. Most established small businesses land in the middle band. Ongoing costs run about $39–$99/month hosting and $50–$200/month maintenance on top.

Why do agencies charge so much more than freelancers?

Because you're paying for a different structure, not different code. An agency rate covers project managers, account managers, designers, QA and premises; a freelance rate covers one person's time. NZ providers put the blended agency rate at $140–$320+/hr against $65–$175/hr freelance. That's worth paying when you need brand strategy, multi-channel work or genuine team depth — and it's overhead when you don't.

Can I negotiate a web development quote?

Negotiate the scope, not the price. Asking a developer to do the same work for less money usually means they take it out somewhere you won't see until later — testing, revisions, or post-launch support. Asking what you could cut to reach your budget is a better conversation, and a good developer will have suggestions ready, often starting with phasing the project.

Where to start

Take the three quotes you already have and write out, side by side, what each one excludes. That single exercise usually explains the entire price gap without anyone needing to defend their number.

If you'd rather have a second opinion, send them to me with your brief and I'll tell you what's missing and what I'd question — including when one of them is a good quote. Get in touch, or see what I build.