Choosing a web developer is hard because you cannot judge the work until you have paid for it. These eight questions make the difference visible early. A good developer will answer them without hesitation. A weak one will get vague.
1. Can I see live sites you built, not just screenshots?
Ask for URLs. Open them on your phone. Check how fast they load, whether they look right on a small screen, and whether they still work. A portfolio of screenshots proves nothing, but a live site is honest.
2. Who owns the domain, the code and the content?
The answer must be you. Ask for the domain to be registered in your name and for the source code and content to be handed over when the project ends. Get this in writing.
3. What is included after launch?
Find out how long free fixes last, and what happens if the site is hacked or breaks. Ask who monitors uptime, who updates plugins and who restores a backup. If nobody does, that is a cost you will pay later.
4. How do you handle security?
Good answers mention SSL, backups, login protection and updates. Weak answers say "we install a security plugin". Ask specifically about backups: where they are stored and when they were last tested.
5. What will the final price be, and what could change it?
A fixed quote should list the pages, the features and the number of revision rounds. Ask what counts as extra. Surprises usually come from unclear scope, not from bad faith, so clarity protects both sides.
6. Who writes the content and supplies the photos?
Delays almost always come from content arriving late. Agree who provides text and images, and when. Ask whether the developer can write copy or arrange photography if you cannot.
7. How fast will the site be?
Ask for a target and a test. For example: "A Lighthouse performance score above 90 on mobile". A developer who has never checked this probably builds slow sites.
8. Who will I be dealing with?
Ask who does the design, who builds it and who answers your messages. A small team where you know the names is often better than a large agency where you are passed between departments.
Red flags
- A quote that arrives in five minutes without any questions about your business.
- No written contract or scope.
- Insisting on registering the domain and hosting in their name.
- Guaranteed "number one on Google" promises.
- No answer to the security question.
Green flags
- Questions about your customers and goals before talk of design.
- A clear scope, timeline and payment schedule.
- Live examples you can test.
- A plan for what happens after launch.
Our answers
We are happy to answer all eight for your project. Send us your questions or use the instant estimator to see a starting price range.
