Everyone wants a number, and almost nobody can give you an honest one up front. Not because designers are being cagey, but because "a website" describes a five-page brochure and a fifty-page site with a booking system equally well. The word carries no information about the work.
So instead of a number, here is the thing that's actually useful: what moves the number. Once you know that, you can read any quote — mine or anyone else's — and understand what you're looking at.
Scope is the first lever, but not the way you think
People assume cost scales with page count. It scales with the number of distinct page types.
Ten pages sharing one layout is a small job. Four pages that each need their own structure — a service page, a case study, a staff directory, a booking flow — is a bigger one, because each is designed, built, made responsive, and tested separately.
When you're scoping a project, don't count pages. Count templates.
Content is usually the real budget
This is the part almost everyone underestimates.
A website is a container for content, and content is where projects stall. If the copy isn't written, the photos don't exist, and the service descriptions live in someone's head, that work still has to happen. It either gets added to the project or it becomes the reason the project sits at ninety percent for three months.
Be honest about which of these you actually have:
- Written copy for every page, approved by whoever has final say
- Photography of your actual space, team, product, or work
- Logos and brand assets in usable formats
- Someone with time to give decisions, not just opinions
Every one you're missing is either cost or delay. Usually both.
Complexity hides in the integrations
The visible design is rarely the expensive part. What costs is everything the site has to talk to.
A site that publishes pages is straightforward. A site that takes payments, syncs a calendar, gates content behind a login, pulls from an inventory system, or pushes structured data into a CRM is a different category of work — because now there are states to handle. What happens when the payment half-succeeds? When the calendar is double-booked? When the third-party service is down?
That isn't decoration. That's software, and it's priced like software.
Custom design versus a design system
There's a meaningful difference between designing a website and designing a system that produces websites.
If you need six service pages that are structurally identical, you should be paying for one designed template and six sets of content — not six designs. A good studio will push you toward that, because it's cheaper for you and more maintainable for everyone.
If every page genuinely needs its own art direction, that's a legitimate choice and it costs more. Just make sure it's a choice and not an accident.
What you're really buying at the higher end
At a certain point, cost stops being about production and starts being about judgment.
Anyone can assemble a page. What you pay more for is someone deciding what shouldn't be on it — which ideas to cut, where the hierarchy lands, what the first ten seconds need to accomplish, and what the site will still need to do in two years. That's the part that's hard to outsource and hard to reverse.
How to get a real number
Ask for a range, not a price, and expect to answer questions first. A studio that quotes you before understanding your content situation is guessing, and you'll pay for that guess later in change orders.
When I scope a project, I'm trying to establish four things: how many distinct templates, how much content exists today, what has to integrate, and who makes decisions. With those answers the number is fairly straightforward. Without them, any figure is theater.
If you're weighing an actual project, tell me what you're working with and I'll tell you what it would take. That conversation costs nothing, and it's more useful than a number on a pricing page.