Skip to main content
Hiring
August 14, 20268 min read

How Do I Know If a Developer Is Overcharging?

You have a quote and it feels high. The six signs you're being overcharged, the six that say the price is fair, and how to ask for an itemised breakdown.

Muhammad Mubashar Shahzad

Founder & lead developer at WebDevStudio — React, TypeScript and MERN

How Do I Know If a Developer Is Overcharging?

You're likely overpaying if the quote has no written scope, no ownership clause, bills standard things like mobile-responsive design or SSL as extras, charges custom prices for template work, or won't itemise when you ask. You're likely not overpaying if the scope is detailed, the exclusions are stated, and the price maps to work you can actually see listed.

Note what isn't on that list: the size of the number. A high price is not automatically overcharging, and a low price is not automatically a bargain. Overcharging is a mismatch between what you pay and what you get — not a threshold.

Got a quote that feels high? Send it to me with what you asked for and I'll tell you what's fairly priced and what I'd question — free, before you sign anything. If it's a good quote, I'll say so. Get in touch.

What overcharging actually means

The most common overcharge in this market isn't an inflated number. It's paying custom prices for template work — a bought theme with your logo and colours dropped in, billed as though it were designed for you.

This is invisible unless you ask, because the finished site looks fine. It's also why "is this too expensive?" is the wrong question. The right one is: what am I getting for this, and does the price match that? If you're new to the process, how to hire a web developer when you don't know how to code covers the whole conversation; this post is only about the money.

Six signs you're being overcharged

  • No written scope. A single-line total — "Website — $6,500" — can't be checked against anything. Ask for pages named and features described. Refusal to provide it is the answer.
  • Standard things billed as extras. Mobile-responsive design, an SSL certificate and basic SEO structure are the 2026 baseline. A line item with a price beside any of them is selling you the floor as an upgrade.
  • Template work at custom prices. Ask directly: is this a purchased theme, a design system applied to my brand, or designed from scratch? All three are legitimate. Only one of them costs custom money.
  • No ownership clause. If the quote doesn't say you own the code, the domain and the hosting on final payment, you may be renting. That's a hidden cost that lands years later, not a discount.
  • Won't itemise on request. Good providers break a quote down quickly, because they built it from parts. Vagueness here usually means the number came first and the justification second.
  • Vague ongoing costs. "Hosting and maintenance from $X" with no ceiling. Published NZ figures are $39–$99/month hosting and $50–$200/month maintenance — a quote well above that should explain what's different.

Six signs the price is fair

This half matters more than the first, because most quotes people worry about turn out to be fine.

  • The scope names pages and features specifically, so you can see what you're buying line by line.
  • Exclusions are written down without you having to ask. Providers who state what's *not* included have been burned before and are protecting you both.
  • Ownership transfers on final payment — code, domain in your name, hosting, design files.
  • The timeline names your obligations too, not just theirs. That's a sign of someone who has run projects rather than sold them.
  • There's a stated rate for changes. A quote with a change mechanism is a quote that expects reality.
  • They asked questions before quoting. A number produced without any questions about your business is a template price, and you'll discover what it doesn't cover later.

Why the same brief legitimately costs 5× more from an agency

This is real, and it isn't a scam. An agency rate covers project managers, account managers, designers, QA and premises. A freelance rate covers one person's time. Published NZ hourly bands: $65–$110 for a junior-to-mid freelancer, $120–$175 senior, $140–$220 blended at a boutique studio, $220–$320+ at a large agency (Web Maniacs).

One Auckland studio publishing its own numbers puts it bluntly: CBD agencies typically quote $15,000–$30,000+ for projects lower-overhead providers deliver for $4,000–$8,000, and calls the difference overhead rather than capability.

So a 5× gap between an agency and a freelancer is not evidence of overcharging. It's evidence you're comparing two different products. What you should check is whether you need what the overhead buys. Remote developer or local agency works through that decision.

What's standard and shouldn't be a line item

Should be included as standardReasonable to price separately
Mobile-responsive designContent writing and copywriting
SSL certificate and HTTPSPhotography and image licensing
Clean URLs, page titles, meta descriptionsKeyword research and ongoing SEO
A sitemap and indexable pagesMigration from an old site and redirect mapping
Basic performance and accessibilityThird-party integrations (CRM, payments, booking)
Testing on current browsersTraining, and a maintenance retainer

The right-hand column being priced separately is normal and honest. The left-hand column appearing as paid extras is the tell.

How to ask for an itemised breakdown without insulting anyone

Most people avoid this because it feels like an accusation. It isn't — it's a normal commercial request, and how someone responds tells you more than the breakdown itself. Send this:

text
Thanks for the quote. Before I make a decision, could you break it
down a little so I can compare it properly against the others?

  - Roughly how the total splits across design, build, content
    and testing
  - Whether the design is a purchased theme, a design system
    applied to my brand, or designed from scratch
  - What's explicitly NOT included
  - What I own on final payment (code, domain, hosting, design files)
  - The rate for anything outside this scope
  - Total ongoing costs for the first 12 months

No rush, and happy to talk it through on a call — I'd just like it
in writing so I can line the quotes up side by side.

A provider who answers this within a day, specifically, is showing you how the project will go. One who gets defensive, stalls, or replies only with reassurance is also showing you how the project will go.

When the expensive quote is the right one

Sometimes the high number is the accurate one, and picking the cheap quote is the expensive decision. That's true when:

  • Your project touches another system. Integrations are priced by the other system's API quality and what happens when a sync fails — risk that has to sit with whoever carries it.
  • You need real permissions. Multiple user types seeing different views of the same records is engineering, not configuration — see what a customer portal costs.
  • Data has to be migrated. Moving thousands of inconsistently-stored records is slow work that can't be skipped.
  • Compliance or accessibility is contractual rather than aspirational.
  • The cheap quote excluded things you'll need anyway — content, migration, redirects, training. Add them back and it often lands above the quote you were suspicious of.

When you don't need to hire anyone

Worth saying, since this post is about spending money. If you need under about five pages, you're not selling online, there are no logins or bookings, and you're happy editing text yourself, then a well-configured site builder at $20–$50/month will genuinely serve you — and any quote for a custom build is the wrong purchase, not an overpriced one.

Equally, if your current site works and the real problem is that nobody can find it, you may need help with visibility rather than a rebuild. Why your website isn't showing on Google is the cheaper place to start.

What I'd recommend

Don't judge the number. Judge the gap between the number and the written scope. Send the itemisation request above to everyone who has quoted you, then compare the replies rather than the totals — how to compare web developer quotes is the checklist for doing that properly.

If after that the expensive quote still has the better scope, it's probably the better quote. That's an uncomfortable conclusion and it's frequently the correct one.

Frequently asked questions

How do I know if my web developer is overcharging me?

Compare the price against the written scope, not against your expectations. You're likely overpaying if there's no itemised scope, no ownership clause, standard items like responsive design or SSL are billed as extras, or a purchased theme is priced as custom design. If the scope is detailed, exclusions are stated and ownership transfers on final payment, the price is probably fair even when it's higher than you hoped.

Should responsive design be a separate charge on a website quote?

No. In 2026 most visitors arrive on a phone, so mobile-responsive design is the baseline rather than an upgrade — and the same goes for an SSL certificate, clean URLs, real page titles and meta descriptions, and a sitemap. Seeing any of those as a priced line item usually means the baseline is being sold to you as an enhancement.

What should I do if I think a web developer's quote is too high?

Ask for an itemised breakdown in writing — how the total splits across design, build, content and testing, whether the design is a theme or custom, what's excluded, what you own on final payment, and the change rate. It's a normal commercial request, not an accusation. How quickly and specifically someone answers tells you more about the project than the breakdown does.

Is a higher web development quote always worse value?

No, and assuming so is how people end up with the most expensive project. The cheap quote is often cheap because content, migration, redirect mapping, training and post-launch support were left out — add them back and it frequently exceeds the quote you were worried about. Higher prices are genuinely warranted for integrations, permission models, data migration and compliance work.

Why is an agency quote so much higher than a freelancer's?

Because you're buying a different structure, not different code. Published NZ rates run $65–$175/hr for freelancers against $220–$320+/hr blended at a large agency, and NZ providers themselves describe the gap as overhead — project managers, account managers, QA and premises — rather than capability. That's worth paying when you need brand strategy or genuine team depth, and it's pure cost when you don't.

Where to start

Send the itemisation request today, to every provider who has quoted you. It costs you nothing, it arrives in writing so you can compare like with like, and the quality of the replies will sort the field faster than the prices will.

If you'd like a second opinion on what comes back, send it over — free, with no expectation you hire me, and I'll tell you plainly if one of them is a good quote or if you'd be better served by someone else entirely. Get in touch, or see what I build.

Hiring a Developer
Pricing
Small Business

Interested in working together on a React or MERN project?

Get in Touch