How to Find a Good Web Developer in the UK: A Small Business Guide

Can I see examples of similar work? — Not just any portfolio — sites of a similar size and complexity to what you need. A stunning e-commerce build doesn't tell you much if you need a simple five-page brochure site, and vice versa.

Who actually does the work? — Some agencies sell the project then hand it to a subcontractor you never speak to. Ask directly who you'll be working with day to day.

What happens after launch? — Is there a support period included? What does an hour of changes cost afterwards? Get this in writing, not implied.

Who owns the domain, hosting, and code? — This is the one people skip and regret. You should own your domain and hosting account outright, and have access to the full source code — not be locked into the developer to make even small changes.

What's the communication plan? — How often will you hear from them during the build? One update at the end is a red flag for anything beyond a very small site.

Fixed price or hourly? — Ask which it is, and what happens if the scope changes. A fixed price with no scope document is just an hourly rate with extra steps.

No live examples of real client sites — Template mockups or "concept" work in a portfolio, with nothing you can visit and click through, is a warning sign.

No written scope or contract — If what you're getting, for what price, by when, isn't written down anywhere, you have no way to hold anyone to it later.

Pressure to decide immediately — "This price is only valid today" is a sales tactic, not a technical constraint. A legitimate developer can hold a quote for a reasonable window.

Vagueness about ongoing costs — Hosting, maintenance, and support costs should be stated plainly, not discovered after you've paid the deposit.

You can't get a straight answer about ownership — If it's unclear whether you'll own your own domain and hosting account, assume you won't — and ask why.