The questions to ask a web developer before hiring them fall into six groups: their track record, who will actually do the work, how they scope and run the project, technical standards, ownership and contracts, and support after launch. The answers matter more than the questions. A good developer gives specific, checkable answers; a risky one gives vague promises. Below are 25 questions, what a strong answer sounds like, and the replies that should make you pause.
We sit on the other side of these conversations every week, so we know which questions make a proposal clearer and which ones vendors find hardest to answer honestly. The hard ones are usually the most useful.
How should you use these questions?
Do not send all 25 in an email. Pick the ones that matter for your project, ask them on a call, and write down the answers. Then ask for the important ones (ownership, scope, support) to be confirmed in the proposal or contract. A spoken promise that never reaches the contract does not protect you.
It also helps to send every candidate the same written brief first. If you do not have one, our guide on how to write a website brief before development has a template.
Questions about experience and track record
1. Can you show me two or three sites similar to mine that are live now?
Good answer: Live links, with a short explanation of what they did on each (design, build, both) and what the client's goal was. Red flag: Only screenshots or mockups, or work that cannot be found online. Members of a long-running UK Business Forums thread on this exact question called a designer who cannot show live work an immediate warning sign (UKBF).
2. Can I speak to a past client whose project was like mine?
Good answer: Yes, with a name and contact after you have shortlisted them. Red flag: Only written testimonials with first names.
3. What went wrong on a recent project, and what did you change afterwards?
Good answer: A real example and a process change that followed. Red flag: "Nothing ever goes wrong." Every team has problems; the useful question is whether they learn from them.
4. Which types of projects do you turn down?
Good answer: Clear limits, such as "we do not take large e-commerce migrations" or "we do not build on platform X". Red flag: They do everything. Specialists usually know where their strengths end.
Questions about who does the work
5. Who exactly will design, build and test my site?
Good answer: Names or roles, and whether they are employees or contractors. Red flag: Hesitation, or a sales contact who disappears after signing.
6. Do you subcontract or white-label any part of the work?
Good answer: An honest yes or no, and if yes, how they control quality and confidentiality. Red flag: A denial you later discover is false. Subcontracting is common; hiding it is the problem.
7. Who is my day-to-day contact, and how quickly do they reply?
Good answer: One named person, a stated response time and a regular update rhythm (for example a weekly call and a shared task board). Red flag: "Just email us whenever."
8. What happens if my main developer leaves or falls ill?
Good answer: Code in a shared repository, documentation and another team member who knows the project. This is the biggest risk with solo freelancers, which we cover in website AMC vs freelancer vs in-house developer. Red flag: No answer.
Questions about scope, process and timeline
9. What do you need from me, and by when?
Good answer: A list of client tasks (content, images, logins, approvals) tied to dates. Red flag: No mention of your responsibilities. Late client content is the most common cause of delays we see, and a good vendor plans for it.
10. What is included in your proposal, and what is explicitly excluded?
Good answer: A written list of inclusions, exclusions and assumptions. Red flag: A single line such as "website design and development".
11. How many design concepts and revision rounds are included?
Good answer: A specific number, and what counts as a round. Red flag: "Unlimited revisions." This usually means either the scope is vague or the revisions will be rushed.
12. How do you handle changes after we approve the scope?
Good answer: A written change request process with time and impact estimated before work starts. Red flag: "We'll sort it out as we go."
13. What platform do you recommend for my site, and why?
Good answer: A recommendation tied to your needs (who edits the site, integrations, speed, budget), and an honest mention of alternatives. We compare common options in WordPress vs custom website development. Red flag: Every client gets the same platform regardless of needs, or a proprietary system only they can maintain.
14. Can I see the work in progress on a staging site?
Good answer: Yes, with a link you can share internally. Red flag: "You'll see it at launch."
Questions about technical standards
15. How do you make sure the site works well on phones?
Good answer: Mobile designs for each template and testing on real devices, not just a resized browser. Red flag: "All our sites are responsive", with nothing more.
16. How do you check page speed before launch?
Good answer: They measure against Core Web Vitals using tools like PageSpeed Insights, and explain how they handle images, fonts and scripts. Red flag: Promises of a perfect score, or no testing at all.
17. What accessibility standard do you build to?
Good answer: A named target such as WCAG 2.2 level AA, and a description of how they test (keyboard, contrast, screen reader spot checks). Red flag: "We add an accessibility plugin." Plugins and overlays do not make an inaccessible site compliant on their own.
18. How will you protect my existing search traffic?
Good answer: For a redesign, a redirect map from every old URL that has traffic or links, and post-launch monitoring in Search Console. Red flag: "SEO is a separate service" when you are replacing a site that already ranks.
19. Do you guarantee first-page rankings?
Good answer: No. Google's own guidance warns that no one can guarantee a number one ranking (Google Search Central). Red flag: Yes.
20. How do you secure the site?
Good answer: Updated software, least-privilege admin accounts, backups, HTTPS, form spam protection and a plan for updates. Our website security checklist lists the basics. Red flag: Security is never mentioned.
Questions about ownership and contracts
21. Who will own the domain, hosting account, code and design files?
Good answer: You do, registered in your company's name, with admin access from day one. Red flag: The developer registers the domain in their own name "to make it easier". This is the root of most "my developer is holding my site hostage" stories. Read domain, SSL and hosting renewals for the accounts you should control.
22. Which licences are you buying, and in whose name?
Good answer: A list of premium themes, plugins, fonts and services, registered to you or transferred at launch. Red flag: Licences tied to the developer's account that stop updating when you part ways.
23. How are payments tied to deliverables?
Good answer: Milestones linked to approved outputs (for example design sign-off, staging review, launch). Red flag: Most of the payment due before any work is visible.
Questions about launch and support
24. What support do I get after launch, and for how long?
Good answer: A defined warranty period for bugs, then an optional maintenance plan with stated tasks and response times. Red flag: Silence about anything after launch day.
25. What will I receive at handover?
Good answer: Admin logins, documentation, a short training session, a list of licences and renewals, and access to the code repository. Red flag: "Just call us if you need anything."
A quick scoring sheet for comparing developers
Score each candidate from 1 to 3 on each area after your calls.
| Area | What a 3 looks like | Weight |
|---|---|---|
| Relevant live work | Two or more similar live sites with clear roles | High |
| Team clarity | Named people, backup cover, stated response times | High |
| Scope clarity | Written inclusions, exclusions, assumptions, change process | High |
| Technical standards | Concrete answers on mobile, speed, accessibility and SEO | Medium |
| Ownership terms | Accounts and code in your name, licences transferred | High |
| Support after launch | Defined warranty and maintenance options | Medium |
| Communication on the calls | Clear, specific, asks you good questions back | Medium |
A developer who asks you sharp questions about your customers and goals during the sales call usually brings the same attention to the project.
Bottom line
Ask fewer questions, but ask the ones that expose risk: who does the work, what is excluded, who owns the accounts and what happens after launch. Judge the answers by how specific and checkable they are, and get the important ones written into the proposal.
If you would like to put these questions to us, our website development team is happy to answer every one in writing. Book a free consultation and bring your brief.






