The real cost of a cheap website

You’ve got a quote for a website that seems almost too good to pass up. Maybe a friend of a friend can do it for a few hundred pounds. Maybe an online builder promises the whole thing for the price of a monthly coffee habit. Or maybe you’ve already been down that road, and now something feels wrong — the site’s slow, the person who built it has gone quiet, and you can’t work out how to change your own opening hours.

I want to be clear from the start: wanting to spend carefully is not a mistake. Budgets are real, and a small business owner who shops around is doing exactly the right thing. The problem is never that you tried to save money. The problem is that with websites, the cheapest option often has costs that don’t show up until a year or two later — and by then they’re a great deal harder to fix. So let me show you where the money actually goes, what tends to get quietly removed to hit a low price, and how to buy well whatever your budget.

Where the money in a website actually goes

When you pay someone to build a site, you’re rarely paying for the pages you can see. You’re paying for the work around them. Here’s what a proper build includes, and what usually gets stripped out to make a price look cheap.

Setup and ownership. Registering your domain in your name, setting up hosting in an account you control, connecting everything correctly. Fiddly, unglamorous, and easy to skip.
Mobile care. Most of your visitors are on a phone. Making a site work properly on every screen size takes real effort, not just shrinking the desktop version.
Testing. Checking the contact form actually sends, links work, and the site loads on different browsers and devices before it goes live.
Security and updates. Websites are built on software that needs regular patching, the same way your phone does. Skip it and the site slowly becomes a target.
Handover. Making sure you have the logins, the files, and enough documentation that someone else could pick it up later.

None of that is visible on the finished page. So when a price is unusually low, it’s worth assuming that one or more of these was left out. Not because anyone set out to cheat you, but because these are the corners you can cut without the customer noticing on day one.

The hidden costs that arrive later

A cheap site can work perfectly well the week it launches. The trouble tends to surface months down the line, and it usually takes one of these forms.

You don’t actually own it

This is the big one. Imagine a café owner who paid someone to build their site. Two years on, they want to move to a new designer — and discover the domain name is registered to the old developer, the hosting is on his personal account, and the site itself is built on a platform only he can access. They don’t own their own address on the internet. To get it back, they have to track him down and hope he cooperates. That’s not a rare horror story; it’s one of the most common situations I’m called in to untangle.

It’s built on something that locks you in

Some cheap builders and “website systems” are proprietary, meaning the site only works while you keep paying that particular company or person. Stop paying, or lose contact with them, and the site simply switches off. There’s nothing to export and nothing another developer can take over. You weren’t buying a website; you were renting one, and the rent never ends.

It stops getting updated, then gets hacked

A site with no maintenance is fine until it isn’t. The underlying software ages, a security hole appears, and one day the site gets defaced, starts sending spam, or quietly redirects your customers somewhere nasty. Now you’re paying for an emergency clean-up — which costs far more than the modest upkeep that would have prevented it. I’ve written separately about what website maintenance actually involves, because it’s the step most cheap builds skip entirely.

The developer disappears

The person who built it moves on, gets busy, or simply stops replying. If everything lives in their accounts and their head, you’re stuck. Even a small change becomes impossible, and the next developer has to reverse-engineer someone else’s work before they can help you — which you pay for.

The “three developers deep” trap

Here’s how a manageable problem becomes an expensive one.

The site breaks. You find someone cheap to patch it. Their fix works, but it’s a quick bodge on top of the original. Six months later something else breaks, so a third person patches the patch. Each fix is cheap in isolation, and each one adds a layer of “just get it working” on top of the last.

After a few rounds, you have a site that no one fully understands — a stack of patches balanced on top of each other, where touching one thing breaks another. At that point a new developer can’t just make a small change; they have to carefully unpick years of accumulated bodging, or start again. The tragedy is that every individual decision along the way was the sensible, frugal choice. It’s the compounding that gets you. When a site reaches this state, it’s worth reading how to tell when a website is beyond saving, because sometimes a clean rebuild is genuinely cheaper than another patch.

How to buy well on a small budget

Now the useful part. A small budget is not the problem — spending it badly is. Here’s how to get a genuinely good site without spending a fortune.

Do fewer pages, properly. A tight five-page site that’s fast, works on a phone, and has a contact form that actually reaches you will out-earn a sprawling twenty-page site that’s a mess. Resist the urge to buy scale you don’t need yet. You can always add pages later — if you own the site.

Own your domain and hosting yourself. This costs almost nothing and protects everything. Register your domain name in your own name, with your own email and card. Set up the hosting account yourself, or make sure it’s created in your name and you hold the login. Let your developer work inside your accounts, not the other way round. If they ever vanish, you still hold the keys.

Get “who owns what” in writing. Before any money changes hands, agree in plain writing who owns the domain, the hosting, the content, and the actual site files when the work is done. One short email you both agree to is enough. The answer you want is simple: you own all of it.

Prefer standard, portable platforms. Ask what the site will be built on, and whether another developer could take it over without special permission or a subscription to one company. Well-known, widely-used platforms mean you’re never trapped with a single person. Avoid anything where the site only works while you keep paying its maker.

Questions that expose real quality — at any price

Here’s the honest balance: a high price is no guarantee of a good site either. I’ve seen expensive builds with exactly the same lock-in and neglect as the cheap ones. So don’t judge by the number on the quote. Judge by the answers to these questions, which work whether you’re spending a little or a lot. Ask every one before you commit.

Will I own everything — the domain, the hosting, the content, and the files? You want a clear yes.
What happens if you’re unavailable? A good answer explains how you’d carry on without them. A vague one is a warning.
How is the site kept updated and secure after launch? There should be a real answer, even if it’s “here’s what you’ll need to arrange.”
Could another developer take this over? If handover would be difficult, ask why.
What’s it built on, and is it a standard platform? You’re listening for something portable, not a private system only they can touch.

Whoever gives you straight, confident answers to these — cheap or otherwise — is the person to trust. Anyone who dodges them is showing you the future cost of the bargain.

When to get help

You can do a surprising amount of this yourself. Checking who your domain is registered to, making sure you hold your own logins, and asking the five questions above cost nothing and prevent most of the disasters I see.

It’s worth getting help when: you can’t tell who actually owns your site or domain; the person who built it has gone quiet and you’re locked out; or you’re staring at a site that’s been patched so many times no one dares touch it. Those are the moments where a bit of expert time saves you a lot of money later, because the alternative is paying in emergencies.

If you’re not sure which camp you’re in, that’s exactly what a Free Site Check is for — an honest look at what you’ve actually got and what it would take to put it right. And when a site is genuinely past the point of patching, a proper rebuild done so that you own every piece of it is the kind of work I do — you can read more about rebuilds done right.

Cheap isn’t the enemy. Hidden cost is. Buy with your eyes open, insist on owning your own site, and a small budget can buy you something that lasts.