Evaluating a web development company is harder than it should be. Agencies are good at presenting well. Portfolios are curated. Case studies highlight successes and omit failures. References are selected carefully. The challenge for any business trying to find a reliable web development partner is getting past the marketing material to an honest assessment of capability and reliability.
These eight questions, asked directly in a proposal or discovery meeting, reveal more about a web development company than any presentation slide.
1. Can you show me a site you built that has Google Lighthouse scores above 90?
Performance is not a feature — it is a measure of how well the work was done. A web development company that consistently delivers high-performance sites will be able to show them immediately. One that cannot is telling you something important about how they build.
2. What CMS would you recommend for this project, and why?
The answer tells you whether they are recommending the best tool for your situation or the one they know best. A good answer includes trade-offs and explains why the recommendation fits your specific requirements. A weak answer recommends the same platform they always use regardless of context.
3. How do you handle scope changes during a project?
Scope changes happen in every project. How a development company handles them — whether through a clear change request process with documented cost implications, or through informal agreements that create disputes later — is one of the most important indicators of how the engagement will feel to manage.
4. Who specifically will work on this project?
Agencies frequently pitch senior people and deliver with junior teams. Ask who will actually be doing the work, what their experience is with similar projects, and whether that will be consistent throughout the engagement. If the answer is vague, push for specifics.
5. What does post-launch support look like?
Understand exactly what is included after go-live, for how long, and at what cost. Bugs discovered after launch, content updates, performance issues, security patches — who handles these, and on what terms? A company that is unclear about post-launch support is one that regards the project as finished at launch.
6. Can you describe a project that went wrong and how you handled it?
Every experienced development company has had projects that encountered problems. The question is not whether problems occur — they always do — but how they are handled. A company that cannot answer this question honestly either lacks experience or lacks the self-awareness to learn from it.
7. How do you handle security?
This includes SSL certificates, software updates, user authentication, protection against common attacks like SQL injection and cross-site scripting, and the handling of any user data. A professional answer is specific. A vague answer is a warning sign.
8. What are the risks to the timeline you have proposed?
The most reliable development partners are the ones who are honest about where delays typically come from — usually content delivery, stakeholder feedback cycles, and third-party integrations. A company that presents a timeline with no acknowledged risks is either inexperienced or telling you what you want to hear.
The right web development company will answer all of these questions directly and specifically. The ones that deflect, generalise, or get defensive about being asked are telling you something useful before the contract is signed.