10 questions to ask before hiring a web developer
A glossy portfolio tells you what a developer can make look good. It doesn't tell you what they'll be like to work with, whether you'll own the result, or what happens when something breaks. These ten questions do. Ask them before you sign anything — the answers separate a safe pair of hands from an expensive mistake.
Before the project
- Who will actually build my site? The senior person in the meeting, or a junior you'll never speak to?
- Can I see live sites and talk to a past client? Real, working examples and a reference beat screenshots.
- How do you decide which platform or technology to use? "It depends on your project" is a good answer; "we always use X" is a flag.
- What's your process, and how involved will I be? You want to know when your input is needed and how feedback works.
About the deal
- What's included — and what isn't? The honest answer here prevents the expensive surprise later.
- Will I own everything? The code, the domain, the hosting and all the accounts should be yours.
- How does pricing work if the scope changes? Know how extras are handled before they come up.
After launch
- What happens when something breaks? Response times, support, and who to call.
- Can I edit the site myself? And if so, how much hand-holding is there to get started?
- Will you help with performance, SEO and security? Or are those "someone else's problem"?
What the answers tell you
You're not just buying a website; you're starting a relationship with whoever builds and looks after it. The answers to these questions tell you whether that person is direct, honest and going to be there afterwards — or whether you're a line item to be delivered and forgotten. Trust the pattern of the answers as much as the answers themselves.
Common questions
What should I ask a web developer before hiring them?
The essentials: who will actually build it, can you see live work and a reference, how they choose the technology, what's included and what isn't, whether you own everything, what happens after launch, and whether they handle performance, SEO and security. The answers reveal far more than a portfolio.
How do I know if a web developer is any good?
Look for live sites you can visit, a client who'll vouch for them, clear and honest answers about trade-offs, and a real interest in your business goals rather than a rush to talk features. Good developers explain things plainly and are happy to recommend less work when that's right.
What are the red flags when hiring a web developer?
A quote with no breakdown, pressure to decide now, vague answers about who does the work, recommending the same platform for everyone, no plan for performance or security, and any reluctance to confirm you'll own the code and accounts. Any one of these is worth pausing over.
Should I always choose the cheapest quote?
No — the cheapest and most expensive quotes are often building very different things. Compare scope, what's included, who does the work and what happens after launch. A slightly higher price for solid foundations and real support usually costs less over the life of the site.
Let's talk
Let's talk about your project.
Whether you've got a clear brief or just an idea, tell us what you have in mind and we'll give you an honest recommendation — even if that's a smaller project than you expected.