Contrary to what most people assume, the expensive part of a website is not the part you can see.
The visible part — the layout, the colours, the photography, the typeface, the bit your friends comment on — has been getting cheaper every year for a decade. There are thousands of good templates. There are tools like Elementor and Divi that let a reasonably creative person assemble something that looks professional in an afternoon. If all you want is a website that looks like a real business has a website, the market floor for that is roughly a grand, and the result will, genuinely, look fine.
So if a pretty site costs a thousand pounds, the obvious question is what the other four, five, nine thousand is for when someone quotes you more. The lazy answer is "they're charging for the same thing with a nicer logo." The honest answer is that you are not paying for what you can see. You are paying for everything underneath it — the thinking that happens before any pixel is drawn, the architecture that decides whether the pretty site actually does anything, and the relationship that means someone is still on the hook when it doesn't. That is the gap. And the reason it matters is that the cheap site, the one that skips all of it, is very often the more expensive option by the time the dust settles.
This piece is about where the money actually goes, and why the thousand-pound site has a way of costing you more than the five-thousand-pound one.
The thinking happens before the first pixel.
Every site worth building starts with a body of work that the client never sees and is never quite sure they paid for, because it doesn't show up on the screen. It is the research, and it happens before anyone opens a design tool.
It is the work of figuring out who the real audience is — not who you, as the business owner, picture when you imagine your customer, because that picture is almost always a flattering composite of your three favourite clients. It is working out what those people are actually looking for in the ten seconds after they land on a page, which is rarely what the business most wants to say about itself. It is being clear about what the business needs the site to accomplish — a booking, a phone call, a quote request, a sale — and designing backwards from that. It is looking at what the competitors are doing, not to copy them, but to find the thing they are all doing badly, because that gap is usually where the work is.
None of this is visible in the finished product, and all of it determines whether the finished product works.
On a thousand-pound site, none of this happens. The process is: you hand over a one-line brief — "I want a new site for my business" — the designer comes back with one option, maybe two, you have a look, you approve it or you ask for a few tweaks, and at that price point asking for tweaks is already a luxury, because the margin assumes you'll take roughly what you're given. There is no room in a thousand pounds for someone to sit with your business for two days and tell you that the audience you think you have is not the audience you actually have. The visual element does not begin until the thinking is done — and on a cheap site the thinking is simply never done, because there is no money allocated to it. The site goes straight to looking like something, having first established nothing.
For a worked example of this — the pre-pixel thinking made concrete on a real, cinematic, sub-second build — see the Miabella build case study.
A nice site and a site that converts are not the same thing.
Here is the distinction that the whole industry is built on quietly not explaining to you.
Designing a nice site and designing a site that converts are two different jobs. You can do the first one beautifully and still produce something that does not move a single visitor closer to becoming a customer. A site can be elegant, fast, on-brand, photographed by someone talented, and still leak every visitor it gets, because nothing in it was arranged around the decision you want the visitor to make.
Decoration is not strategy with a coat of visual polish on top.
The arrangement of a page — what the visitor sees first, what question gets answered before they have to ask it, where the proof sits relative to the claim, how many steps stand between landing and acting — that is conversion architecture, and it is a separate discipline from making things look good. It is also invisible, which is exactly why it is the first thing cut when the budget is a thousand pounds. You cannot point at it in the mockup. The client cannot see it being skipped. So it gets skipped, and what gets delivered is decoration: a nice-looking page with no underlying argument.
The pay-twice trap.
What I see constantly is the business that paid for the pretty site, noticed after six months that it wasn't bringing in any work, and concluded — reasonably — that they needed to spend money fixing it.
So they go and get it fixed. Often they go a route that sounds sensible: one person to redesign the look, a separate specialist to "sort out the conversion side." A lot of companies do exactly this, because the original design was pretty and they don't want to throw it away. And it still doesn't work, because the thing that was wrong was never the surface. The underlying architecture — the structure the visitor actually moves through — stays the same. You've now paid two people, you've paid more in total than a proper build would have cost, and the site still doesn't do its job.
The reason this keeps happening is that the driver behind the second spend is almost never "let's make this genuinely work." It is "what is the minimum we can spend to get this fixed." And that is the wrong question. It feels like the prudent question — it has the shape of being careful with money — but it quietly guarantees the worst outcome, because the honest answer in most of these cases is that the site needs gutting from the ground up, and "the minimum" will never buy that. So you spend the minimum, twice, three times, and arrive eventually at the number you were trying to avoid, having paid extra for the journey.
The cheap site, in other words, is rarely a thousand pounds. It is a thousand pounds plus the redesign plus the conversion patch plus, finally, the proper rebuild — and somewhere in there, the cost of every month the site spent not bringing in the work it was supposed to bring in.
What you're actually paying for sits under the site.
Strip the visuals away and there is a technical layer underneath that decides whether the site is a thing you own or a thing that owns you.
This is the part that makes a site tick along without hiccups, that doesn't fall over when a plugin updates, that doesn't quietly slow to a crawl as it ages, that doesn't drain your lifeblood — and a steady monthly fee — just to stay upright. It is the difference between a site built on something simple and durable and a site built on a teetering stack of dependencies that each need feeding. We build HTML-first for exactly this reason: the fewer moving parts sitting between a visitor and your content, the fewer things there are to break, to patch, to pay for, and to slow the whole thing down.
You don't see this layer either. It is, almost by definition, the part that is invisible when it is done well — a site that simply works does not advertise the engineering that lets it. But it is most of what separates a build that costs real money from one that doesn't, because getting it right takes experience and time, and experience and time are the two things a thousand-pound budget cannot buy. Every decision at this layer has a downstream consequence, and a cheap build makes all of those decisions by default — whatever the template did, whatever the plugin shipped with — rather than on purpose.
Process is the part nobody itemises.
There is one more thing in the gap between the cheap site and the proper one, and it is the hardest to put on an invoice. It is process — and the most important thing process buys you is someone willing to push back.
A good build involves being told no. It involves the person you hired saying "I know you asked for that, but it will cost you conversions, and here's why." It involves iteration that goes deeper than moving a button — iteration on the actual argument the site is making. None of that exists on a thousand-pound site, and not because cheap builders are bad people. It is because of a straightforward asymmetry in incentives.
A thousand-pound site has no downside for the seller. They build it, they invoice, they move on. Whether it works for you a year later is not their problem and was never priced as their problem — at that number it can't be. A five- or ten-thousand-pound site is different in kind, not just in degree, because at that price the build is tied directly to our risk and our relationship with you. We are going to hear about it if it doesn't work. We are hoping you'll come back, and recommend us, and let us point at the result. That hope is the thing that makes the pushback happen — it is in our interest for the site to actually perform, which means it is in our interest to tell you the uncomfortable thing rather than just take the brief and cash the cheque. You are, in a real sense, paying for someone to have skin in the game. The cheap site is cheap partly because nobody does.
So, honestly.
I want to be fair about this, because there are cases where the thousand-pound site is exactly the right call, and pretending otherwise would be the same sleight of hand I'm objecting to.
If you need a placeholder — a single page that proves you exist while you work out what the business even is — buy the cheap template, and don't let anyone talk you into more. If you're testing an idea you might abandon in three months, don't pour five thousand pounds into the foundations of something that might not be there by summer. If the website is genuinely incidental to how you get work — if every client comes by word of mouth and the site is just somewhere to send them afterwards — the pretty, cheap site is fine, and the rest of this argument doesn't apply to you.
But if the site is supposed to bring in the work — if it is, or should be, a thing that turns strangers into enquiries while you sleep — then the cheap site is the expensive one. Not as a slogan. As arithmetic. You will pay for the research eventually, because without it the site is aimed at the wrong people. You will pay for the conversion architecture eventually, because without it the pretty site leaks. You will pay for the technical layer eventually, because the cheap stack ages into a monthly tax. And you will pay for all of it in the worst possible order — piecemeal, reactively, after months of a site quietly underperforming — instead of once, deliberately, at the start.
Our floor for a proper build sits north of the templates for all the reasons above, and we are happy to tell you, before you spend anything, whether your situation is one where that floor is worth clearing or one where a cheap template is genuinely the smarter buy. Sometimes the answer is the template. When it is, we'll say so. But if you've already bought the cheap site once and you're staring at the quote to "fix" it, the thing worth measuring is not the cost of the patch. It's the cost of having paid the cheap price twice.
Email us. We'll look at what you've got, tell you whether it's worth saving, and give you the real number — the one you'd otherwise arrive at the long way round.