Why there's no single right answer
"What should a website cost?" is a fair question and there's no single honest answer to it, because a website isn't one product. A five-page brochure site telling customers who you are and how to call you, a service site with online booking and enquiry forms doing real work for the business, and a full e-commerce build taking payments and managing stock are three different products with three different build efforts and three different ongoing costs. Any figure that tries to average across all three tells you nothing useful about what your job would actually cost.
What actually drives the cost of a build is a short, knowable list, even without a market benchmark to plug numbers into. The number of distinct pages and templates matters, because a unique layout costs more to design and build than a repeated one. Custom functionality matters a lot more than page count. Booking systems, payment processing, quote calculators, customer portals and anything that has to talk to another system all add real engineering time that a static page doesn't. Content is another driver that's easy to underweight: a site where you supply finished copy and photography costs less to build than one where the copy has to be researched and written and the photography commissioned, because that's genuinely additional work regardless of who's doing the coding. And a site isn't a one-off purchase. Hosting, updates, security patching and the inevitable "can we change this" over the following years are an ongoing cost most people budget for after the fact rather than before, which is part of why a single up-front number is a poor way to think about the whole commitment.
Why this calculator uses payback period instead
Given that there's no reliable published figure to lean on, this calculator uses a different, more honest logic: payback period. A website is only "worth" what the extra work it brings in is worth to your specific business, so instead of asking what a website should cost in general, the useful question is what yours could justify spending, based on what a better one would actually generate for you. Feed in how many extra enquiries a better website would realistically bring you a month, the rate at which you close those enquiries into paid work, your average job value, and your profit margin on that work, and the arithmetic gives you the extra profit a better site would be worth to you every month. Multiply that by however many months you're willing to wait to break even (three, six or twelve) and you get a defensible budget ceiling built entirely from your own numbers, not somebody else's market average.
This is a more honest way to size a budget than chasing an industry figure for a second reason, not just the absence of a reliable one: an industry average, even a real one, describes what other businesses paid for what other businesses needed. It says nothing about whether your particular extra enquiries are worth a little to your business or a lot, and that gap is exactly what determines whether a given spend is a good decision for you specifically, independent of what anyone else paid for a differently-scoped job.
Think of it as a cost per enquiry, not a sticker price
"What should a website cost" puts the question the wrong way round. A website isn't a thing you buy once and finish thinking about. It's a piece of equipment that either brings in enquiries or doesn't, month after month, and the number that actually matters is what each enquiry it brings you costs to get, not what the build invoice said on day one. A cheap site that generates almost nothing is expensive on a per enquiry basis. A pricier site that keeps generating solid leads for years can end up cheap, once the cost is spread across everything it's brought in. Neither of those shows up if the only number you're looking at is the upfront figure.
This is exactly why the calculator above asks about enquiries, close rate and job value rather than handing back a dollar amount. Think of it less like buying a sign for the shopfront and more like hiring someone whose whole job is bringing work in. You wouldn't judge that hire on their first week's wage alone.
What actually drives a build's price up
Without a market figure to lean on, it still helps to know which levers move a quote, so a provider's number makes sense instead of feeling arbitrary. Custom design work, a layout built specifically for the business rather than a template with the logo swapped in, costs more than a templated build, because someone's designing it rather than adapting something that already exists. Integrations add real engineering time: a booking system, a payment gateway, a quote calculator, or anything that has to talk to another piece of software isn't a checkbox, it's a build task with its own testing and its own things that can go wrong. Migrating an existing site, its content, its search rankings, its email addresses, without breaking any of it, is genuinely careful work, not a copy-paste job, and a provider quoting for a migration is quoting for the risk of getting it wrong as much as the labour of doing it. And content is its own driver: supplying finished copy and photography keeps a quote down, while asking a provider to write the copy and organise the photography adds real work that has nothing to do with the code at all.
What a cheap site actually costs you later
The cheapest quote rarely stays the cheapest option once a year or two has passed. A site built to hit a low number often skips the parts that don't show up on day one: proper structure for the pages you'll want to add later, decent image handling so the site doesn't crawl on a mobile connection, and a build that a different provider can actually pick up and work with if the relationship ends. None of that is visible at launch. It shows up eighteen months later as a site that's slow, that can't be handed to anyone else without a rebuild, or that quietly stopped ranking somewhere along the way and nobody noticed until enquiries had already dropped off.
That's not an argument for spending more for its own sake. It's an argument for asking what a low number actually includes before agreeing to it, because "cheap now, rebuilt again in two years" is its own real cost, it just arrives on a different invoice.
Who actually owns the site and the domain
This matters more than the price, and it's the question most businesses forget to ask. A domain name isn't something anyone truly "owns" in the way they own a ute. As auDA explains, whoever registers a .au domain holds a licence to use it, and the registrant on that licence is whoever's name is actually on the record, not whoever built the site or happened to click the buttons. If a provider registers the domain under their own business rather than yours, walking away from that provider can mean walking away from the domain too, sometimes with the site itself held to ransom until a final invoice gets paid.
Before signing anything, confirm the domain will be registered in the business's own name, ask for the login to wherever the site actually lives (hosting, not just a content editor), and get it in writing that both come with you if the relationship ends. A provider who's comfortable handing that over is telling you something. One who hedges on it is telling you something too.
Questions worth asking before signing anything
A short list, asked before a contract is signed rather than after: Who's named as the domain registrant, and can you get that in writing? Does the price include hosting, and what happens to the site if hosting isn't renewed? Who owns the content, the images and the code once the build's finished, you or the provider? What's the process, and the rough cost, for a small change after launch, a phone number update, a new page, rather than every change going through a fresh quote? And what happens if the provider isn't around in three years, is the site built on something portable, or is it locked into a system only they can touch?
None of those questions need a market rate to answer, and a provider who answers all of them plainly, without dodging, is generally the safer one to work with regardless of what the final number turns out to be.
Turning a budget into a quote
Once you've got a budget figure that's actually yours, the next step is turning it into a real quote rather than a guess, because scope is what determines whether a given number is realistic. Our web design work starts from exactly that conversation: what you need the site to do, matched against what you're able to justify spending on it. Our pricing page shows how we quote, so you can see the structure before you ever pick up the phone. And if part of what's driving the "extra enquiries" side of your own numbers is uncertainty about visibility rather than the site itself, it's worth looking at our SEO work too. A better website that nobody finds doesn't generate the extra enquiries this calculator assumes, so the two questions are connected rather than separate.
The honest version of "what should a website cost" isn't a dollar figure at all. It's "what's it worth to me", and that's a number only your own business can supply, because it depends on your enquiries, your close rate, your job value and your margin, not on what anyone else paid.