You asked three people for a quote. One came back at $500, one at $6,000, one at $30,000. They all claim to be building you "a website". They are not building you the same thing, and the number on the page tells you almost nothing until you know what sits behind it.
This is not a pricing list. Anyone who gives you a fixed figure without seeing your business is guessing, and so would we. What follows is how to read the gap between those three quotes, what's actually driving the difference, and the questions that get you a straight answer before you sign anything.
The price is a proxy for six decisions
Every website quote, whether the person giving it says so or not, is really pricing six separate decisions. Once you can see them, a $500 quote and a $30,000 quote stop looking like the same product at different prices and start looking like different products.
Who is doing the work
A $500 site might be built by a single freelancer working from a template, reselling a theme licence and doing an afternoon of setup. A $30,000 site might involve a designer, a developer, a copywriter and someone doing SEO structure, each billing separately inside the one number. Ask who touches the project and what they're qualified to do. "We" on a quote sometimes means four specialists and sometimes means one person wearing four hats badly.
Custom build versus theme
A theme is a pre-built layout that thousands of other businesses are also using, customised with your logo and colours. It's fast to deploy and cheap because the design and development work has already been paid for once and sold many times over. A custom build starts from your business, your customers and your pages, and is designed and coded to fit them. Themes aren't automatically bad. A theme built and configured properly, on solid hosting, with real content, can serve a small business well. A theme dumped online with stock images and no thought to how your specific customer reads and decides is where the trouble starts, which we cover below.
How many genuinely different page types you need
This is the one people miss. A five-page brochure site with a home page, an about page, a contact page and two service pages is a small job. A site with twelve different service pages, each answering a different customer question, plus location pages, plus a blog structure, plus calculators or booking tools, is a much bigger one, even if the total page count looks similar on a sitemap. Price scales with the number of unique templates and layouts that need to be designed and built, not the number of URLs.
Who writes the words
Design without content is a shell. If you're supplying your own copy, photography and case studies, the build is smaller. If the studio is writing service page copy, running photography, or building out twenty suburb pages of original content, that's a content project sitting inside a web project, and it should be priced and shown as one. A quote that's silent on who writes the words is a quote with a hidden cost still to come.
What it needs to connect to
A contact form that emails you is trivial. A booking system that checks real-time availability, a quote calculator that does your pricing logic, a CRM integration that pushes leads into your sales pipeline, payment processing, or a product catalogue synced to inventory: each of these is its own piece of engineering with its own testing and its own ongoing maintenance. If your business runs on a particular piece of software, say so at the quote stage. Bolting an integration on after launch nearly always costs more than building it in from the start.
What happens after launch
A website is not a one-off purchase, it's something you own and keep paying to keep running: hosting, a domain, SSL, security updates, backups, and someone available when something breaks or you need a page changed. A cheap build with no ongoing plan and an expensive build with a vague one both leave you exposed the same way. Ask what happens in month two, not just what's delivered on launch day.
How to read a quote line by line
Put two quotes side by side and check for these before you compare the total:
| Line item | What to check |
|---|---|
| Number of unique page designs | Not total pages, unique templates. A quote for "10 pages" using one template is a different job to "10 pages" using five. |
| Copywriting | Included, supplied by you, or a separate add-on billed later? |
| Photography and imagery | Stock, your own supplied photos, or a paid shoot? |
| Mobile build | Designed for mobile from the start, or a desktop site that "responds"? |
| Hosting and domain | Included in the price, or a separate ongoing cost, and who owns the account? |
| Who owns the site after handover | Do you get admin access and the ability to leave, or is it locked to the builder's platform? |
| Revisions | How many rounds of changes are included before extra work is billed hourly? |
| Timeline | What's the actual delivery date, and what happens if content isn't ready by then? |
If a quote is a single number with none of this itemised, ask for it broken down before you compare it to anything else. A cheap total built from cheap assumptions and an expensive total built from thorough ones aren't comparable until you can see the assumptions.
Where the cheap end actually goes wrong
The failure mode at the bottom of the market is rarely that the site looks bad. Templates have improved and most look fine in a screenshot. The failure is what happens once someone actually lands on it: unoptimised images and stacked plugins make it slow to load, generic copy pulled from a template doesn't answer the specific question your customer came with, and a contact form buried three clicks deep loses the enquiry before it's made. None of that shows up when you're admiring the homepage. It shows up in your enquiry numbers three months later, when you've got a website that technically exists and does not produce work.
We've written more on this specific trap in why cheap websites cost more in the long run, and the short version applies here: if a $500 saving on the build costs you enquiries every month afterwards, it wasn't a saving. Run your own numbers. If one extra enquiry a month is worth $500 to you and a slow, generic site is costing you two or three of those a month against a properly built one, the cheap option is the expensive option, just paid on a different schedule.
When the cheap site is the right call
None of this means always spend more. A brand-new business that doesn't yet know if the offer works, the market wants it, or the pricing is right shouldn't sink $15,000 into a website before any of that is proven. A fast, honest, template-based site that gets you trading, taking enquiries and testing your positioning is the correct decision at that stage, not a compromise. The mistake isn't choosing cheap when you're validating something. The mistake is staying on that same site two years later once you know exactly who your customer is and what they need to hear, and treating the placeholder as permanent because rebuilding feels like admitting the first one was wrong. It wasn't wrong. It did its job. Its job is just finished.
The test is simple: are you still finding out if the business works, or do you already know and the website hasn't caught up? The first calls for cheap and fast. The second calls for a build that matches what you now know about your customer.
Questions to ask before you sign
- Who specifically will design and build this, and have they done a site like mine before?
- Is this a custom build or a theme, and if it's a theme, what's being configured versus left as default?
- How many unique page designs are included, not total pages?
- Who writes the copy, and is that person briefed on my business or working from a generic template?
- What integrations do I need now, and what would it cost to add one later that isn't in this quote?
- What's included after launch: hosting, updates, security, and who do I call when something breaks?
- Do I own the domain, hosting account and admin access, or am I locked into this provider's platform?
- How many rounds of revisions are included before extra work is billed?
- What's the realistic delivery date, and what's the dependency on me supplying content by a certain point?
- If I want to leave in two years, can I take the site with me?
A studio that answers these plainly, on the phone, without needing to check with someone else, is telling you something about how they'll be to work with after you've paid. A studio that gets vague is telling you something too.
What to do next
Take whatever quotes you've already got and run them through the line-by-line check above before you compare totals. In most cases that alone will tell you why the numbers are so far apart, and which one actually matches what your business needs right now.
If you want a second opinion on a quote you've already received, or you'd rather start with a plain conversation about what your site actually needs to do before anyone prices it, see how we scope and build on our web design page, or get in touch directly via our contact page. We'll tell you if a smaller build is the right call, not just quote the bigger one. For what a finished site needs to do once it's live, our guide on building a website that actually converts is the next thing worth reading.