7 Questions to Ask a Web Agency Before You Sign Anything

Hiring a web agency is a significant investment — typically $5,000–$20,000 for a service business website, plus ongoing costs. Most service business owners approach the decision the way they’d evaluate any vendor: look at portfolios, get a few proposals, and pick the one that seems most professional at a reasonable price.

That process misses the questions that actually matter.

Here are the seven questions that reveal whether an agency understands your business, your customers, and what the work is supposed to accomplish.

1. Do you have experience building websites for businesses like mine?

This sounds obvious, but the follow-up question matters: “Can you show me examples?”

A web agency that builds sites for restaurants, SaaS companies, law firms, and HVAC companies is a generalist. That’s not inherently a problem — design skills transfer across industries. But what doesn’t transfer is knowledge of how your customers make contact decisions, what trust signals matter in your category, and what a conversion looks like for your type of business.

What to listen for: Specific examples from your industry or adjacent industries. The ability to speak about what drives leads for a business like yours — not just how to make a site look good.

Red flag: An agency that shows you B2B software company case studies when you run a home services company. The audiences are completely different, and the design priorities reflect that.

2. How do you approach SEO — at launch and after?

Many agencies treat SEO as something that happens after the site is built: a “phase 2” or an add-on service. This is backwards.

Technical SEO is built into the structure of the site — site speed, schema markup, heading hierarchy, URL structure, internal linking, meta tag optimization. These things are much harder to retrofit than to build correctly from the start.

What to listen for: SEO described as part of the build process, not a separate engagement. Mention of Core Web Vitals (especially LCP and INP on mobile), Google Business Profile optimization for local businesses, and how they handle area or service pages for local search.

Red flag: “We’ll set up your Google Analytics and that’s the SEO.” Analytics is measurement, not optimization. Or: “We can refer you to an SEO partner after launch” — meaning they’re not building with SEO in mind from day one.

3. Who owns the code and design files when the project is done?

This question separates agencies that work in your interest from agencies that create dependency.

Some agencies build on proprietary platforms you can’t take with you. Some design in tools that require the agency to export files you can’t access. Some host your site in a way that gives them leverage over you at renewal time.

What to listen for: You own 100% of the code, design files, and content when the project is complete. The site is built on a platform you could move to another developer if needed. Hosting is in your name, not the agency’s.

Red flag: Vague answers about ownership. “Our platform” without explaining what that means for your access and portability. Hosting bundled with a monthly retainer in a way that makes leaving difficult.

4. What does maintenance and support look like after launch?

Every website needs ongoing maintenance: security updates, dependency updates, content changes, performance monitoring, and occasional bug fixes. The question is who handles it, on what timeline, and at what cost.

What to listen for: A clear description of what’s included after launch — and what isn’t. Response time commitments for bug fixes. Whether they monitor site uptime and performance. What happens if something breaks on a Friday at 6pm.

Red flag: No clear answer, or “just contact us when you need something.” Vague support arrangements lead to delayed responses, scope disputes, and sites that quietly develop problems nobody notices until they’re affecting conversions.

5. How do you handle it if the project goes over scope or timeline?

Almost every web project encounters scope or timeline changes. An honest answer to this question reveals how the agency operates when things get complicated.

What to listen for: A clear process for handling change requests — how they’re documented, how they’re priced, and how timeline impacts are communicated. The agency should explain what happens when unexpected technical issues arise.

Red flag: Dismissiveness (“we always deliver on time”) or vagueness (“we’ll figure it out”). Also watch for contracts with “unlimited revisions” language that isn’t actually defined — this often means unlimited rounds of minor edits and doesn’t cover scope changes.

6. How will we measure whether the site is working?

The goal of a service business website is to generate leads. “The site looks great” is not a success metric.

What to listen for: Specific metrics — conversion rate (percentage of visitors who contact you), monthly lead volume from the website, and lead quality (how many become booked clients). The agency should describe what tracking will be set up at launch so you can measure from day one.

Red flag: “Success is when you’re happy with the design.” Design aesthetics are a means to an end, not the end. An agency that can’t define success in lead generation terms doesn’t have conversion as its core objective.

7. What’s the plan for the first 90 days after launch?

Launch is not the finish line — it’s the start of measurement. In the 90 days after a new site goes live, traffic adjusts, search rankings shift, and real user behavior reveals things no design review could catch.

What to listen for: A description of what the agency does (or recommends you do) after launch. This might include monitoring Core Web Vitals, watching conversion data in analytics, fixing issues that emerge from real traffic, and making adjustments based on what’s working.

Red flag: “Our job is done at launch.” A site handed off without post-launch attention misses the optimization opportunities that real traffic data reveals — and problems not visible in testing.

The Evaluation Process

After getting answers to these seven questions, compare proposals with this framework:

Price reflects scope, not just competition. If one agency is significantly cheaper, understand what’s different — not just cheaper, but different. Fewer revisions? Simpler development? A templated approach? Cheaper is fine if the scope matches your needs. Cheaper with an undefined scope leads to friction later.

References matter more than portfolios. The portfolio shows what they’ve built. References tell you what it was like to work with them — and whether the sites actually generated results. Ask specifically: “Did the site perform the way you expected? How did they respond when something needed fixing?”

Trust your read on communication. You’re going to be working closely with this team for 2–4 months. If the sales process involves pressure, vagueness, or the feeling that your questions aren’t being taken seriously — that pattern continues through the project.

What We’d Tell You About Us

We build websites for local service businesses — HVAC companies, law firms, real estate teams, plumbers, landscapers, and other businesses where the lead comes from a local search and the customer is making a trust decision.

We’re transparent about ownership (you own everything), scope (defined in writing before we start), and measurement (conversion tracking set up at launch so you know what’s working).

If you want to see our work and have an honest conversation about whether we’re the right fit, start here.

If you’re also evaluating whether AI intake makes sense for your business, the AI Readiness Audit answers that question specifically before you commit to any build.