What Does a Website Cost? The Line Items Behind the Price
"How much is a website?" has no single answer — but it isn't a random range either. We open up the line items inside a quote, the decisions that genuinely drive cost up, and the places where cutting the budget gets expensive later.
It's the question we get most: "How much is a website?" The honest answer is that it has the same shape as "how much is a building?" How many square metres, how many floors, what ground, how long does it have to stand? What sets the price isn't the page count — it's what the site has to do.
A quote generally breaks into four line items. First, discovery and scope: the stage where you decide what gets built — the item that costs the most when it's skipped. Second, design: brand identity, page templates, mobile behaviour. Third, development: turning those templates into real pages that are fast and manageable. Fourth, content and launch: copy, image optimisation, technical SEO setup, analytics and form integrations.
The things that genuinely drive cost up are these: designing every page bespoke instead of from a template, multiple languages, a custom admin panel, e-commerce and payment flows, integrations with external systems (ERP, CRM, booking), animation density, and accessibility compliance. None of these is a bad decision; each one is simply real work and a maintenance obligation.
There are things that bring cost down, too, and most of them are free: having your content ready before we start, a single decision-maker, three reference sites you like handed over up front, and the courage to say "not for now". Most projects stretch because they're waiting on a decision, not because the development is hard.
And there are places where cutting gets expensive later: performance, the technical SEO foundation, and code quality. A slow site that's closed off to search engines looks cheap on the first invoice — then you keep paying for it out of the ad budget every month. We don't write those three as optional line items. They're all standard, because adding them afterwards always costs more than building them in.
Our approach is to define a clear scope and quote a fixed price: what's included, what's deferred to a second phase, and what post-launch maintenance costs are all written down. There are no surprise invoices; and if there is one, it's our estimating error, not your budget's problem.
Have a project in mind?
Let's engineer your solution
From a rough idea to a shipped, self-running product — we build fast, reliable digital products and solve the hard problems along the way.
Start a projectMore from the blog
Beyond Websites: The Engineering Underneath Everything We Ship
A polished interface is only the part you see. The real work is the engineering beneath it. We open up the architecture, automation, and system design that turn a good-looking site into a product that runs reliably at scale.
One Language or Many? Getting the Site Structure Right From Day One
A multilingual site doesn't mean double the traffic — it means double the maintenance. The questions we ask before deciding on a language structure, when prefixes like /tr are the right call, and why automatic language redirects break SEO.
The Technical SEO Checklist: The First 12 Steps on a New Site
However good the content is, a broken technical foundation stops a search engine putting it where it deserves to be. The checklist we go through item by item before every project goes live — and the mistakes we see most often in the field.
