What a £5,000 to £15,000 Website Project Should Include

I get asked about pricing a lot. It's usually the first question on a call, which is completely understandable - you're trying to work out whether this is even worth your time. The honest answer is that website costs vary enormously, and two quotes for the same project can be thousands of pounds apart. That's confusing, and it shouldn't be.

As a freelance web designer based in London, I work with businesses at this budget level regularly. So I wanted to write something practical. If you're a business owner budgeting somewhere between £5,000 and £15,000 for a new website, this is what you should realistically expect to receive for that investment - and what should raise questions if it's missing.

Why the range is so wide

A £5,000 project and a £15,000 project can both be described as "a new website." The difference is scope, complexity, and how much thinking goes into it before anyone opens a design tool.

A smaller project might be a clean, well-built five to ten page website for a business that knows exactly what it wants and has most of its content ready. A larger one could involve a content strategy, a design system built across fifteen or twenty pages, custom functionality, and a CMS setup that actually makes sense for your team to use.

The range exists because no two projects are the same. A decent freelance web designer should be able to tell you clearly what's moving the number up or down.

Discovery and strategy

Any project worth its budget starts before the design does. This phase is about understanding your business, your customers, and what the website actually needs to do.

A good discovery process covers things like who your audience is, what pages you need, how the site should be structured, and what success looks like. It's not a nice-to-have - it's the difference between a website that looks good and one that actually works.

At this budget level, you should expect a discovery phase built into the project. If a quote jumps straight to design without any of this groundwork, that's worth asking about.

Design

For projects in this range, you should receive a proper design phase - usually in Figma or a similar tool - before a single line of code is written. This gives you the chance to review and refine the layout, visual style, and content structure before the build begins. Making changes at the design stage is quick. Making them halfway through development is not.

A well-designed website at this budget should cover:

• High-fidelity layouts
• A clear visual hierarchy that guides visitors through the page
• Typography, colour, and spacing that reflects your brand
• Interactive elements like buttons, forms, and navigation

What you probably won't get at the lower end of this range is a full design system or component library. That tends to come in on larger, longer-term projects.

Development

This is where it gets technical, but the key things to look for are fairly straightforward.

A website built at this price should be fast. Not "passes a basic speed test" fast - genuinely fast, on mobile, on a slow connection, without excuses. Page speed affects your search rankings and your bounce rate, so it's not a nice extra, it's part of the brief.

It should also be accessible. That means usable with a keyboard, readable by a screen reader, and not relying on colour alone to communicate important information. This is increasingly a legal consideration as well as a practical one.

The build should also be secure and maintainable. I build on the Jamstack - which means no database to attack, fast load times by default, and a setup that any competent developer can pick up and maintain in the future. You shouldn't be locked into a proprietary system that only one person knows how to touch.

For projects in this range, you should also expect SEO basics to be handled at the development level - proper heading structure, page titles, meta descriptions, canonical URLs, and schema markup where it makes sense.

A CMS you can actually use

If you're spending this much on a website, you should be able to update your own content without calling a developer every time.

A good CMS setup for a project at this level is simple, clearly documented, and matched to what you actually need to edit. You shouldn't have hundreds of fields you'll never touch, or a system so complex that nobody on your team uses it.

Ask any designer you're talking to how content editing works, and what the handover looks like.

Launch and testing

Before your site goes live, it should be tested properly. That means checking it across different browsers and devices, running through accessibility checks, verifying all forms and integrations work, and confirming performance is where it should be.

A solid launch process also includes setting up redirects from old URLs, submitting the sitemap to Google, and making sure analytics is in place from day one.

This isn't glamorous, but it's the kind of detail that separates a clean launch from one that takes weeks to recover from.

What's usually not included at this budget

Being honest here is important. A few things that typically sit outside a project at this price point:

• Copywriting. Writing for the web is a skill in its own right. Most projects assume you're providing the copy, or that copywriting is scoped separately.
• Photography and video. Stock imagery can fill gaps, but anything custom will need its own budget.
• Ongoing marketing. A new website doesn't automatically bring in traffic. SEO content, paid ads, and social media are separate disciplines.
• Complex custom functionality. Things like booking systems, e-commerce, membership areas, or API integrations can increase the scope significantly.

A transparent designer will flag any of these early rather than let you find out mid-project.

Red flags in quotes

A few things that should prompt questions when you're reviewing proposals:

A fixed price with no discovery. If someone's giving you a number before they understand your business, that number is a guess.

Vague deliverables. "A fully responsive website" tells you very little. Ask what pages are included, what platform it'll be built on, and who owns the code.

No mention of accessibility or performance. These aren't optional for a well-built website nowadays. If a quote doesn't reference them at all, it's worth asking why.

The cheapest quote. I know that's not what you want to hear, but if someone is undercutting everyone else by several thousand pounds, something is being left out. Find out what.

Getting the most out of your budget

The best projects I've worked on at this level have one thing in common: the client came in with clear goals, not just a vague idea of wanting "a new website."

You don't need to know what technology to use or how to build anything. But if you can tell a designer what you're trying to achieve, who your customers are, and what you want visitors to do when they land on your site - you'll get a much better result for your money.

If you're at the stage of working out what your website project should look like, feel free to get in touch. I'm happy to talk through scope and budget before anything else.