How to Choose a Web Developer (Without Getting Burned)

Most bad website experiences aren't about bad design, they're about a mismatch discovered halfway through the build, when it's expensive to fix. Here's what to check before signing anything.

"WordPress with some plugins" and "Next.js, built bespoke" are not the same product at similar prices. Template-and-plugin builds are cheaper upfront but tend to need constant updates, slow down as plugins accumulate, and break more easily during theme updates. Ask directly what stack a developer builds on, and be suspicious of vague answers.

"Roughly £X, could go up depending on scope" is where a lot of website budgets quietly double. A genuinely scoped quote should be fixed once the brief's agreed, if a developer won't commit to a number, that's usually a sign the brief hasn't actually been thought through yet.

Some agencies build on proprietary platforms or retain effective control of hosting in a way that makes leaving expensive or difficult later. Confirm upfront that the finished site and its code belong to the business, not to the agency's platform.

A simple brochure site should be weeks, not months. If a developer's timeline for a basic build stretches past a month with no clear reason (custom integrations, complex bookings, etc.), that's worth questioning before committing.

Hosting, domain, SSL, who's responsible for these, and is there a support option if something breaks? A website that goes live and is then effectively abandoned by its builder is a common and avoidable problem.

A developer who asks what the site actually needs to do before quoting a price is a better sign than one who quotes instantly off a vague brief. Scope should drive price, not the other way around.