The 10 Questions to Ask Any Web Agency Before You Sign Anything

Hiring a web development agency is one of the most consequential technology decisions a growing business makes. Get it right and you have a partner who builds you a fast, secure, well-converting website that generates returns for years. Get it wrong and you end up with a site you cannot update without calling the agency, a CMS you do not have full access to, and a bill that keeps growing without the results to justify it.

The challenge is that most business owners are not in a position to evaluate the technical quality of an agency's work — they can see whether a design looks good, but they cannot assess whether the underlying architecture is sound, whether the performance will hold up under real traffic, or whether the content management system will actually give their team the editorial independence they need.

These ten questions are designed to close that gap. They are not trick questions — a good agency will answer them clearly and confidently. The answers (and the hesitations) will tell you more about an agency than any portfolio presentation.

1. "Who will own the website and all its assets when the project is complete?"

This should have a simple, unambiguous answer: you do. Full stop. The domain, the hosting account, the CMS login, the source code, the design files — all of it should be in your name, under your control, accessible to you without the agency's involvement.

Some agencies operate a different model: they host your site on their infrastructure, retain the source code, or use proprietary systems that you cannot access independently. In these arrangements, the agency becomes your permanent, unavoidable dependency. If you want to leave, change agencies, or manage the site in-house, you may find you have to rebuild from scratch.

The red flag answer: "We host all our clients' sites on our platform" without offering an alternative. Or: "The source code is proprietary to our workflow." Or: hesitation and deflection. If an agency is not immediately clear that you own everything, that is a serious concern.

2. "Can you show me a Lighthouse Performance score for a recent client site on mobile?"

Performance is easy to promise and difficult to deliver. A Lighthouse Performance score on mobile — which Google uses as the primary basis for its performance-based ranking signals — is a concrete, reproducible measurement that a competent agency should be able to produce immediately for any recent client.

What to look for: a mobile Lighthouse score above 75 is acceptable; above 85 is good; above 90 is excellent. Below 60 on mobile indicates a site that is structurally slow and likely to hurt the client's organic rankings.

The red flag answer: they show you only desktop scores (mobile is harder and more relevant). They show you a Lighthouse score from a tool like GTmetrix rather than the actual Google PageSpeed Insights result. They cannot produce a score at all, or they explain that performance "depends on the client's content." Performance is determined primarily by architecture and implementation, not content.

3. "What CMS will you build on, and why that one for my specific needs?"

The CMS choice should be driven by your requirements — your content team's technical level, the complexity of your content model, your need for editorial independence, your budget for ongoing fees — not by the agency's default preference.

A good agency will explain the options, articulate the tradeoffs, and make a specific recommendation based on your situation. They will be able to explain why they are not recommending other options and what those options would have cost in terms of performance, security, or editorial experience.

The red flag answer: "We build everything on WordPress/Webflow/Squarespace" without any discussion of whether those platforms are appropriate for your specific needs. Platform lock-in at the agency level often indicates that the agency has a preferred workflow that serves their efficiency rather than your outcome. A client-focused agency builds on the right platform for each client.

4. "What happens to my site if I stop working with you?"

This question reveals the actual structure of the engagement and the agency's philosophy about client independence. The correct answer is: nothing. Your site continues to run. You log into your CMS directly. Your hosting continues. You can hire another developer or manage the site in-house.

Some agencies are structurally positioned as permanent dependencies: the site is hosted on their infrastructure, the CMS requires their expertise to manage, or there are ongoing contracts that the site's operation depends on. These are not necessarily bad arrangements if disclosed upfront — some clients prefer full-service management. But they should be transparent, and you should understand exactly what "leaving" would involve before you sign anything.

5. "How will my content team manage the site without developer involvement?"

This is the editorial independence question, and it is one of the most important for businesses that publish content regularly or update their site frequently. The answer should describe a specific editorial workflow: what your content team will log into, what they will be able to do independently, and what will require developer involvement.

Specifically: can a non-technical team member publish a new blog post? Update the homepage hero copy? Add a new team member? Create a new case study? Change the pricing page? These should all be self-service operations that do not require a developer ticket.

The red flag answer: they describe the content management experience vaguely, focus heavily on design capabilities rather than editorial workflow, or suggest that "most changes" will be handled through their retainer. A site that requires constant agency involvement for routine content updates is not serving your team — it is serving the agency's recurring revenue.

6. "What does your quality assurance and testing process look like?"

Every professional development agency should have a documented QA process. This includes: cross-browser testing (Chrome, Firefox, Safari, Edge), device testing (desktop, tablet, mobile at different screen sizes), performance testing (Lighthouse scores, real-device testing, load testing for high-traffic scenarios), accessibility testing (WCAG compliance), and content proofreading and link checking before launch.

The answer should be specific. "We test thoroughly" is not an answer. "We test on Chrome, Safari, and Firefox on both desktop and mobile, run Lighthouse audits targeting a minimum of 85 on mobile, check all internal links, test all forms end-to-end, and do a final review on three physical devices before launch" is an answer.

7. "How do you handle security — both during development and after launch?"

Security is a technical discipline, not a setting. The question has different implications depending on the platform:

• On WordPress: how are plugin updates managed? Is there a process for monitoring vulnerability disclosures? What happens when a critical security update is released?
• On a headless stack: what is the attack surface of the public-facing site? Is the CMS admin interface on a different domain? Are environment variables secured?
• On any platform: how is the production environment configured? Are there staging environments? How is access managed?

An agency that dismisses the security question with "we follow best practices" or "WordPress is secure" (it is not, by default) is not taking it seriously. An agency that explains their specific approach to dependency management, access control, and vulnerability monitoring is demonstrating the operational discipline that protects your business.

8. "Can you walk me through how a previous client's site performed versus their goals, not just how it looks?"

Portfolio presentations almost always show design. They rarely show results. A client-focused agency should be able to share specific outcomes from previous projects: the conversion rate before and after, the organic traffic growth in the 12 months after launch, the Lighthouse performance score on mobile, the reduction in developer dependency for routine content updates.

If an agency can only show you how their work looks, they are a design shop. If they can show you what their work achieved for a client's business, they are a results-oriented partner. The latter is what you want.

9. "What is included in your post-launch support, and what will cost extra?"

The go-live date is not the end of the project — it is the beginning of a long relationship between the site and the business it represents. Understanding the post-launch relationship upfront prevents friction later.

Clarify specifically: what is included in any maintenance retainer? Is there a response time SLA for critical issues? What costs extra (new pages, design changes, plugin updates, security patches)? Is hosting included or separate? Who do you contact when something breaks on a Sunday afternoon?

The red flag answer: vague descriptions of "ongoing support" without specific terms, or no post-launch support discussion at all. An agency that does not raise post-launch expectations proactively is either planning to charge for everything at a day rate or planning to be difficult to reach after the final invoice is paid.

10. "What do you see as the biggest risk in this project, and how will you manage it?"

This question separates experienced agencies from inexperienced ones. Every non-trivial web project has risks: content migration complexity, integration challenges with third-party tools, timeline risks from client content delivery, technical risks from platform constraints, or design review cycles that extend timelines. An agency that has been through enough projects has seen these risks materialise and has processes for managing them.

A good answer will identify one or two specific risks relevant to your project context and describe a concrete mitigation: a content migration staging environment, a defined content freeze date, a specific integration testing approach, or a timeline buffer built into the project plan. An agency that says "we don't anticipate any significant risks" has either not thought carefully about your project or is telling you what they think you want to hear.

Beyond the Questions: What to Evaluate in the Answers

The questions themselves are less important than the quality and confidence of the answers. Pay attention to:

• Specificity: Vague answers about "best practices" and "industry standards" are signs that the agency does not have deep operational experience. Specific answers about processes, tools, and previous outcomes indicate real expertise.
• Willingness to say no: A good agency will occasionally push back on your assumptions, suggest a different approach than the one you described, or tell you that something you want is not the right solution. An agency that agrees with everything you say is telling you what you want to hear, not what you need to know.
• Transparency about tradeoffs: Every platform, every approach, every technology has tradeoffs. An agency that presents any option as perfect without acknowledging what it costs in other dimensions is oversimplifying to close the sale.
• Cultural fit: The agency-client relationship for a website project lasts months, and the post-launch relationship can last years. The team you are talking to is the team you will work with. Communication style, responsiveness, and alignment on what a good outcome looks like matter as much as technical capability.

Conclusion: The Right Agency Will Welcome These Questions

A competent, client-focused web agency will not be put off by any of these questions. They will be glad you asked them — because it means you are serious about the outcome, not just the deliverable. They will answer specifically, transparently, and with confidence.

An agency that deflects, gives vague answers, or becomes uncomfortable when you ask about ownership, performance, or post-launch support is telling you something important about the engagement before it begins. Pay attention to that signal.

Your website is a significant investment. The agency you choose to build it determines whether that investment generates returns for years or becomes a liability you need to replace. These ten questions are the minimum bar for making that decision with adequate information.

If you are evaluating agencies and want a benchmark for comparison, we are happy to answer every one of these questions directly — and to show you live client examples with performance scores, editorial workflows, and outcome data. No sales pitch required.