The Quote Was Cheap. The Project Wasn't.

Two quotes land. One is roughly half the other. The cheap one looks like an easy decision, and often it is the right one.

But the number on a proposal is not the price of a website. It is the price of getting a website built once. What it costs to own for three years is a different number, and it is the one nobody puts in the document.

This is the last post in this series, so it is the one that adds up. Not to argue that cheap is bad, because sometimes cheap is exactly right, but so that you can compare two quotes on the same basis instead of on the only number either of them showed you.

What is the true cost of a website?

Build cost plus everything the build decision commits you to afterwards.

Four things live in that second half, and all four are invisible at signing.

What changes cost. Every site needs changes. New service, new prices, new photos, a page that turns out to be confusing. The build decision sets the price of every one of those for years.

What it costs to run. Hosting, domain, licences, plugins, the platform's own monthly fee. Small numbers individually. Not small over three years.

What it costs when it does not work. The hardest one to see, because it never appears on a statement. A site that loads slowly, buries the phone number, or breaks the enquiry form on mobile is charging you in enquiries that never arrive.

What it costs to replace. Every website is eventually replaced. What varies enormously is whether that is a refresh or a start-from-nothing rebuild, and that is decided by how the first one was built.

The changes tax

This is the one that surprises people most.

On a well-built site, updating your prices or adding a service page is something you do yourself in a few minutes, or a small job for whoever maintains it. On a badly built one, the same change is an email, a quote, a wait and an invoice. Same change, wildly different cost, decided entirely at build time.

Do this bit of arithmetic with your own numbers. Take the per-change fee in the proposal, assume one modest change a month, and multiply by thirty-six. Then do it again assuming those changes are things you can do yourself, where the answer is close to zero. The gap between two builds is often larger than the gap between the two original quotes, and it compounds quietly.

There is a second-order effect that matters more. When changes are expensive, you stop making them. The special offer does not go up. The new service waits. The out-of-date team page stays for another year. The site slowly stops matching the business, which is the beginning of it being useless, and it happened for budget reasons nobody ever decided out loud.

The running costs nobody adds up

A monthly hosting line sounds like nothing. Multiply it by thirty-six and it stops sounding like nothing. Then add the page-builder subscription, the premium plugins, the form service, the image host, and a maintenance retainer that covers plugin updates.

None of these are scandalous on their own, and some are genuinely worth paying. The point is what they do to the ranking. A cheaper build carrying heavy monthly costs regularly overtakes a more expensive build carrying light ones, often inside two years, and nothing in either proposal told you that.

So ask for the total monthly figure before you sign, and ask what happens to it in year two. If either answer is vague, that is the answer.

The rebuild tax

Here is the cost that dwarfs the others.

A site built on foundations you can extend gets refreshed. New design, new content, same platform, a fraction of the original cost. A site built on something you cannot extend gets replaced entirely, and you pay full price again. Sometimes sooner than you expect, because the trigger is rarely age. It is usually a business change the site cannot accommodate.

We wrote a whole framework for that decision in maintain, renovate, or rebuild. The relevant part here is that which fork you end up on is largely determined on day one, by people making choices you were not part of.

Comparing two quotes properly

Take both proposals and work out, for each: the build cost, plus thirty-six months of running costs, plus a realistic allowance for changes, plus your honest guess at whether this survives three years or gets replaced at two.

You do not need precision. You need both numbers on the same basis. Most of the time the ranking changes, and occasionally it changes dramatically.

Then ask the question the arithmetic cannot answer: what does one extra enquiry a month do for this business? For a lot of Australian small businesses, one job a month covers the entire difference between the two quotes inside the first quarter. That does not mean spend more automatically. It means the cheap option is only cheap if the expensive one would not have earned.

What a fair engagement looks like

Since a series about how things go wrong should end with what right looks like.

You know what you are getting before it starts, in writing, including what you are supplying. You can see the work on a real link early. You own the domain, the hosting, the code and the data, in accounts with your name on them. You can make ordinary changes without raising a ticket. Nothing about leaving is difficult.

And the number is a number, not a range that drifts. A serious small business site is typically a few weeks of work, you should be quoted for that in writing before anything starts, and it should not move without a conversation. If you would rather own it outright than pay monthly, you should be able to. If you would rather someone kept improving it after launch, you should be able to do that instead.

The whole series in four lines

If you have landed here first, the rest of it is short and covers the four ways this usually goes wrong.

Why web projects blow up is about the three failure modes: scope nobody wrote down, the builder who went quiet, and the decision that sat unmade for six weeks. The fault is usually shared, which is good news, because half of it is yours to fix.

Locked out of your own website is the one to read today rather than eventually. It covers domain, hosting, code and data, and includes a ten-minute audit that tells you exactly what you control. Almost nobody sets out to trap a client. It happens through convenience that hardened into leverage, and it is trivial to prevent and painful to unwind.

How to read a website quote goes through a proposal line by line: what genuinely costs money, what gets padded, and which of the three tiers your project actually sits in.

And this one is the arithmetic. The honest summary of all four: most website disasters are not technical failures. They are decisions made quickly, by people who did not have the information, that turned out to be expensive to reverse. Slowing down for one afternoon at the start is the cheapest insurance available.