10 Questions to Ask a Web Developer Before You Hire Them
The questions smart clients ask before hiring a web developer. What to look for in the answers, and red flags to watch for.
Hiring a web developer is confusing if you’ve never done it before. Most people don’t know what questions to ask, and some developers rely on that. Here are the questions I wish every client would ask me.
These aren’t trick questions. They’re straightforward things that will tell you quickly whether a developer is worth your time and money. I’ll explain what good answers look like and what should make you walk away.
1. Can I See Examples of Your Work?
This is the most important question and the easiest to ask. Any developer worth hiring should be able to show you real projects they’ve built.
What you’re looking for: Live websites you can actually visit. Case studies that explain the problem and how they solved it. Work that’s relevant to what you need.
Good answer: “Here are three recent projects similar to yours. I can talk you through what the client needed and how we approached it.”
Red flag: “I can’t share client work due to NDAs” on everything. The occasional NDA is normal. Every project being confidential is suspicious. Most clients are happy for their developer to reference the work.
You can see our projects on the portfolio page, with detailed write-ups of what was built and why.
2. What’s Included in the Price?
This sounds obvious, but you’d be surprised how often people commit to a project without a clear understanding of what they’re paying for.
What you’re looking for: A specific list. Design, development, mobile responsiveness, basic SEO setup, browser testing, a contact form, training on how to update content. These should all be stated clearly.
Good answer: “Here’s exactly what’s included at this price, and here’s what would cost extra if you decide you want it later.”
Red flag: Vague answers like “we’ll figure it out as we go” or “everything you need.” If they can’t tell you what’s included, they can’t tell you what’s excluded either. That’s where surprise costs come from.
Our pricing page breaks this down clearly because I think you should know what you’re getting before you even pick up the phone.
3. Who Will Actually Build My Website?
At a freelancer’s practice, this is a simple question. At an agency, it’s essential.
What you’re looking for: The name of the person (or people) who will be doing the design and development work. Their experience level. Whether they’ve worked on similar projects before.
Good answer: “I’ll be building it myself” or “Sarah will handle the design and Mark will do the development. They’ve both worked on projects like this.”
Red flag: “Our team will handle it” with no specifics. This sometimes means your project gets handed to whoever is available, which might be the most junior person in the company.
On the about page you can see exactly who you’re working with at FWD. There’s no mystery about it.
4. How Long Will It Take?
Timeline expectations need to be set clearly before anyone starts work. “As soon as possible” isn’t a timeline.
What you’re looking for: A realistic estimate broken into stages. Brief and planning, design concepts, development, content, testing, launch.
Good answer: “A project like this typically takes 3-4 weeks. Here’s roughly how that breaks down. It depends on how quickly you can provide content and feedback.”
Red flag: “We can do it in 3 days” for anything beyond a basic single-page site. Either it’s a template with your logo dropped in, or the quality will suffer. Good work takes time. A simple brochure site takes 2-3 weeks minimum when done properly. Complex sites with custom functionality take 6-8 weeks or more.
Also watch out for developers who give a timeline but no mention of what they need from you. Your responsiveness with content, feedback, and sign-offs directly affects how long the project takes.
5. What Happens After Launch?
A website isn’t finished on launch day. Things will need updating, fixing, or improving. You need to know who handles that and what it costs.
What you’re looking for: A clear support arrangement. How long is the initial support period? What’s covered? What does ongoing maintenance cost? How quickly do they respond to urgent issues?
Good answer: “You get 30 days of free support after launch for any bugs or issues. After that, maintenance packages start at X per month. If something breaks, here’s how to reach me.”
Red flag: Disappearing after launch. If a developer can’t tell you what happens when you need help six months from now, you’ll find out the hard way. Also be cautious of developers who don’t offer any ongoing support. Websites need maintenance, security updates, and occasional fixes. Someone needs to do that.
6. Will I Own the Website?
This catches more people out than you’d think. You’re paying for the website. You should own it.
What you’re looking for: Confirmation that you own the code, the design, the domain name, and the hosting account. You should be able to take your website to a different developer if you want to.
Good answer: “You own everything. The code, the design, the domain, the content. If you want to move to a different developer in the future, you can take it all with you.”
Red flag: The website is built on a proprietary platform that only the developer can manage. Or the domain is registered in their name, not yours. Or the contract says they retain ownership of the code. Any of these means you’re locked in, and leaving will cost you a complete rebuild.
7. How Will My Site Show Up on Google?
Search engine optimisation matters. If people can’t find your website when they search for what you offer, the site isn’t doing its job.
What you’re looking for: Basic on-page SEO as a standard part of the build. That means proper page titles, meta descriptions, heading structure, image alt text, fast loading speed, mobile responsiveness, and clean URLs.
Good answer: “Basic SEO is included in every build. I’ll set up your page titles, meta descriptions, heading structure, and make sure the site loads quickly. If you want ongoing SEO work like keyword strategy and content marketing, that’s a separate conversation.”
Red flag: “SEO is a separate service” when talking about basic on-page fundamentals. These should be standard practice, not an upsell. Any developer who delivers a site without proper meta tags, heading structure, and mobile responsiveness in 2026 is cutting corners.
8. What’s Your Process?
A clear process means the developer has done this before and knows how to manage a project. A vague process means they’re winging it.
What you’re looking for: Defined stages with clear milestones. Something like: initial brief, proposal, design concepts, feedback round, development, content integration, testing, launch, handover.
Good answer: “Here’s how the project will run. First we’ll agree the scope and sign off on a brief. Then I’ll create design concepts for your review. Once the design is approved, I’ll build it. You’ll review the development version and we’ll make any changes. Then we test, launch, and I’ll train you on how to manage the site.”
Red flag: “We’ll just get started and see how it goes.” No process means no accountability. If there’s no plan, there’s no way to know if the project is on track, and no way to manage scope when things change.
9. Can I Update Content Myself?
Unless you want to pay a developer every time you need to change a phone number or add a blog post, you need some way to update your own content.
What you’re looking for: A content management system or a clear method for making common updates. Training on how to use it. Understanding of what you can change yourself and what needs a developer.
Good answer: “I’ll build it so you can update text, images, and blog posts yourself. I’ll give you a training session before launch so you’re comfortable with it. For structural changes like adding new sections or features, you’d come back to me.”
Red flag: “You’ll need to contact us for any changes.” If updating a typo or adding a new team member photo requires a developer, the site isn’t built with your independence in mind. Some developers prefer this because it creates a recurring revenue stream from small content updates.
10. What If I’m Not Happy?
Disagreements happen. You need to know how they’re handled before they arise.
What you’re looking for: A revision policy that’s fair to both sides. How many rounds of feedback are included? What happens if you want changes beyond the agreed scope? What happens if the final result doesn’t match what was agreed?
Good answer: “You get two rounds of revisions at each stage. The first draft is based on our agreed brief. If you want to change direction significantly, we’ll discuss the scope and cost implications before doing the work.”
Red flag: “The first draft is the final version” or, conversely, “unlimited revisions.” The first means no flexibility. The second means the developer hasn’t thought about scope management and the project will drag on indefinitely.
Bonus: The Question Most People Forget
Here’s the one question that separates good developers from the rest:
“What would you recommend for my budget?”
A good developer will tailor their recommendation to what you can actually afford. They’ll tell you what’s essential, what’s nice to have, and what can wait until later. They’ll help you get the most value from your budget rather than pushing you towards the most expensive option.
If a developer responds to your budget by listing everything you can’t have rather than focusing on what you can, that tells you something about their approach.
Comparing Developers Right Now?
Feel free to ask me any of these questions. I’ll give you straight answers. You can also check the portfolio to see what we’ve built, read the pricing page for transparent costs, or get in touch for a no-obligation chat about your project. I’d rather you hired the right person for your needs, even if that’s not me.