How to pick a web developer and not get burned
A practical guide to choosing a developer for your next site. What to ask, what to avoid, and why the cheapest quote rarely wins.
I get an inquiry and the client's opening line is often "I had one already, but they never finished it". Or "I paid 2,000 euros and the site broke after six months". Unfortunately, choosing a developer based on price and portfolio isn't enough — here's a checklist that saves you both nerves and money.
1. Ask about specific projects — and what went wrong on them
Every portfolio looks nice. The more interesting question is: "What did you recently get stuck on, and how did you solve it?"
A developer who owns up to their mistake and explains what they learned is always a better choice than one who claims they've "never had that problem before".
2. Ask about code and domain ownership
This is the most common trap. Find out upfront:
- Who will own the domain and hosting?
- Do you get the source code if you end the collaboration?
- Is the site built on some custom proprietary system you can't leave?
If someone answers evasively, run.
3. Ask for an estimate, not a fixed price on the spot
A serious developer won't quote you on a 5-minute call. Either they give a range, or they take a day to actually understand the project. If you get a fixed price instantly, it either has huge padding (you overpay) or they'll cut corners on quality (you pay in other ways).
4. Check how they communicate
90% of custom-dev problems aren't in the technology. They're in communication. Before signing anything, send two or three emails. Do they reply quickly? Clearly? Do they ask good questions, or just agree with everything you say?
5. The cheapest offer rarely wins
If you get three quotes — 800, 2,400 and 4,800 euros — and all "promise the same thing", you usually have two options. The cheapest is either (a) missing something, or (b) being done by someone who's losing money and looking for corners to cut.
I won't say always go with the most expensive. Just know that with websites, "the fool wins on price but pays for the smart one" — you only notice quality when something breaks and you need it fixed.
What I ask before taking on a project
Before every collaboration I go through these points with the client:
- What's the specific goal of the site? (Sales, inquiries, presentation?)
- Who is the target customer?
- What are your deadlines and budget?
- Who will manage content after launch?
- What are you currently unhappy about with what you have?
If a developer doesn't ask you these questions, they don't know their job. Development is half code, half understanding the brief.
Looking for someone who actually finishes projects? Let's talk — the first 30-minute consultation is free.