Hiring a web developer is a bit like hiring a contractor for your house. If you pick well, you get exactly what you wanted and it lasts for years. If you pick poorly, you spend the next year fixing problems you didn't know existed.
Most of the problems between clients and developers come from a handful of unanswered questions. Not because either side is being sneaky — but because nobody thought to ask.
Here are the ten questions to ask before you hire. Ask them all. The answers will tell you a lot — not just about the developer's process, but about whether they're the right fit for you.
1. Can I see examples of your past work?
Start with the basics. Any decent developer should have a portfolio you can review.
But don't just look at pretty screenshots. Ask for live links and check them yourself:
- Do the sites load quickly?
- Do they work on your phone?
- Are they still up and running? (Not just built once and abandoned)
- Do they look like the kind of site you'd want?
Portfolios can be dressed up. Live links can't.
If a developer can't show live examples or gets defensive about this question, that's a red flag.
2. Who will actually be building my site?
This matters more than you'd expect.
Some agencies or freelance studios show you the founder in the sales call, then hand your project to a junior developer or an overseas contractor. That's not necessarily bad — but you should know upfront.
Ask directly:
- Who will be writing the code?
- Will I have a direct line to that person?
- Who do I contact if I have questions during the project?
If you're paying for senior-level work, you should get senior-level work. If you're paying for junior-level work, you should know that too.
3. What exactly is included in the price?
This is where projects most often go sideways.
Ask for a written scope that lists:
- Every page or feature included
- Number of revision rounds
- Any integrations (payment gateways, contact forms, third-party tools)
- What happens if you ask for changes outside the original scope
A good developer will provide this without you having to push. A vague "it depends on what you want" answer is a sign you'll be arguing about money later.
Related questions:
- Is the price fixed or hourly?
- What's the payment schedule? (Deposit? Milestones? On delivery?)
- Are there any additional costs I should know about? (Hosting, domains, plugins, premium features)
4. How long will it take?
Every project has a timeline. Ask for a specific one.
What to expect:
- Simple landing page: 3–7 days
- Standard business site: 1–3 weeks
- E-commerce store: 2–5 weeks
- Custom web app: 1–3 months+
Beware of two extremes:
- "I can have it ready tomorrow" — Either they're only doing a template install, or they're overpromising
- "It depends on how many changes you ask for" — True, but not an answer. You should get a realistic range upfront
Also ask: what happens if the timeline slips? Good developers build in buffer time. Great ones communicate early if they're running behind.
5. Who owns the code when it's done?
This is one of the most important questions. And most clients forget to ask it.
There are three possible answers:
1. You own everything. The developer hands over all files, credentials, and rights. You're free to work with anyone else in the future. This is the best outcome.
2. The developer retains certain rights. Maybe they keep a license to reuse their framework. Maybe they own part of the codebase. This is fine if you understand it upfront — but you should know.
3. You're locked in. The developer keeps the code, and you need them for every future change. This is the worst scenario — and unfortunately common in the agency world.
Ask explicitly: "When this project is done, do I own all the code and can I take it to another developer if I want?"
If the answer is anything other than a clean "yes," ask why.
6. What's the ongoing cost after launch?
Websites aren't one-time expenses. Every site has ongoing costs — and you should know what they are before you commit.
Ask about:
- Hosting — monthly or yearly cost
- Domain — yearly cost
- SSL certificate — should be free with modern hosting
- Premium plugins/themes — yearly renewals
- Maintenance — if the developer offers it, what does it cover and what does it cost?
For WordPress: expect $5–$30/month for hosting plus some plugin renewals. For custom code: often free hosting (Vercel) but may need occasional code updates.
Add up the true cost over 3 years — not just the initial build.
7. What happens if something breaks after launch?
Every site has bugs at some point. What matters is how they get handled.
Ask:
- Is there a warranty period? (Usually 7–30 days after launch for issues caused by the developer's work.)
- What if something breaks 6 months later? Are fixes included, or is that billed separately?
- How do I report issues? Email? A ticketing system? A Slack channel?
- What's your response time?
A good developer will have clear answers. A bad one will dodge.
8. Will I be able to update the site myself?
This is huge for small businesses.
If you plan to update text, swap images, add blog posts, or manage products yourself, you need a site built with that in mind.
For WordPress sites: Ask if they'll set up a proper admin experience for you, and whether they'll give you a walkthrough.
For custom-coded sites: Ask whether there's a content management system included, or if every change needs a developer.
If you'll need to make regular updates yourself, make sure the developer knows that from the start.
9. Do you offer SEO or marketing help?
Some developers do just the build. Others handle SEO, content, marketing, and growth.
Neither is wrong — but you should know which kind you're hiring.
If SEO matters for your business, ask:
- Is basic on-page SEO included? (Meta tags, clean structure, fast load times)
- Do you offer ongoing SEO services?
- Do you help with content strategy?
Some developers include basic SEO for free as part of the build. Others charge separately. Ask upfront so there are no surprises.
10. Can I speak to a past client?
This is the single most revealing question you can ask.
A confident developer with happy clients will say yes immediately. They'll give you a referral you can email or call.
A developer who dodges this question — or who "doesn't have anyone available right now" — is telling you something.
When you talk to the past client, ask:
- Did the developer deliver what they promised?
- How was communication during the project?
- What would you do differently if you were starting over?
- Would you hire them again?
The answers will tell you more than any portfolio can.
Bonus: Two red flags to watch for
While you're asking these questions, watch for two warning signs.
1. Pressure to decide quickly. "I can only hold this price until Friday" or "I have another client waiting" are common pressure tactics. Good developers don't need them. If someone's pushing you to sign before you're ready, walk away.
2. No contract, or a very short one. Every project should have a written agreement covering scope, timeline, payment, and ownership. If a developer won't put things in writing, that's not a small detail — it's a sign of how they'll handle problems later.
What to do with the answers
Don't just collect the answers — compare them across the developers you're considering.
A developer who can't provide live links, refuses to give a written scope, or dodges the code ownership question is probably not the right choice. A developer who happily answers everything, provides references, and puts things in writing is probably a safe bet.
You don't need the cheapest option. You need the one whose process you trust.
If you're the developer reading this
These questions aren't adversarial. If you're a developer, you should have clear answers to all ten — written down, ready to share, without being asked.
Preemptively answering these questions in your proposals and on your site is one of the strongest trust signals you can give a client. It says: "I know what you're worried about, and I've already addressed it."
If you can't answer one of these confidently, that's a gap worth closing before you pitch your next client.
Ready to hire a developer and want to know what to expect? Read our guide to what to expect when you hire a web developer.
Or if you're curious about pricing first, read our honest breakdown of website costs.
