How to Choose the Right Web Agency: 12 Questions to Ask First

For a lot of business owners, choosing a web agency feels a bit like buying a car without knowing anything about engines, you're relying on the seller being honest, and it's hard to know what to even ask. Price tells you surprisingly little about quality, and a polished portfolio can hide a lot. Here are twelve questions that quickly reveal whether an agency actually delivers what they promise, along with what a genuinely good answer sounds like versus what should make you pause.

About Process and How They Work

1. What does your process look like, step by step? This is the single most revealing question on the list, because it's nearly impossible to fake a good answer to it. A serious agency can walk you through discovery, wireframing or planning, design, development, review cycles, testing, and launch, in order, with rough timeframes for each. A good answer sounds specific: "We start with a two-week discovery phase where we map your goals and your users' journey, then move into design, which usually takes three to four weeks including two rounds of feedback." A bad answer sounds like a shrug: "We just kind of figure it out as we go." Improvisation might work for a solo freelancer with one client at a time, but for anyone juggling several projects, a defined process is what keeps yours from slipping.

2. Who will actually be working on our project? Many agencies pitch with their most senior people but hand off the actual work to junior staff or subcontractors you never meet. Neither approach is automatically wrong, subcontracting to a skilled freelance developer can be perfectly fine, but you should know about it upfront. Ask directly who does the work, and ask whether that person will be available if you have questions once the project is underway, not just during the sales conversation.

3. How long will this realistically take? Ask for a timeline with concrete milestones, not just a loose "about two months." A good answer breaks the project into phases with dates or week numbers attached, and is honest that timelines can shift if you're slow to provide content or feedback. A bad answer is either suspiciously precise with no room for reality ("exactly six weeks, guaranteed") or so vague it commits to nothing at all.

About Ownership and Responsibility

4. Who owns the code and content after launch? It should be you, without exception. If the agency retains control over source code, the CMS login, the domain, or hosting in a way that makes you dependent on them specifically, get clear on exactly what that means in practice. A good answer is unambiguous: "You own everything, we'll hand over full admin access and all source files at launch, and you're free to take it elsewhere." A bad answer hedges, "well, technically we manage the hosting environment," which often means you can't actually leave without a costly migration, even if nobody says so directly.

5. Is basic SEO included, or is it an add-on? A site built without basic SEO consideration, clean URLs, proper heading structure, fast load times, mobile responsiveness, costs more to fix afterward than to build correctly from the start. It doesn't need to be a full SEO campaign, but the technical foundation should be part of any competent build, not sold back to you later as a surprise upsell.

6. What happens if we want to switch providers later? A clear, honest answer here says a lot about how the agency views its clients, as partners, or as locked-in subscribers. Good agencies will tell you exactly how to export your content, transfer domain and hosting access, and walk away cleanly if you ever choose to. If the answer is evasive, or if the contract includes exit penalties buried in the fine print, treat that as a signal worth investigating further before you sign anything.

About References and Credibility

7. Can we talk to two past clients, not just see a case study? Written case studies can be polished until every rough edge disappears. An actual fifteen-minute call with a former client gives a far more honest picture, ask them what surprised them, what they'd do differently, and whether the agency was still responsive three months after launch.

8. What was your most recent project that didn't go as planned, and what did you do about it? Every agency has projects that hit problems, a scope that grew, a deadline that slipped, a stakeholder who disappeared mid-project. The ones who answer honestly and specifically ("we underestimated the complexity of the payment integration and had to add two weeks, here's how we communicated that") tend to be more reliable than the ones who claim everything always goes perfectly. Nobody has a spotless track record, and claiming one is itself a red flag.

One project we worked on started specifically because a client had been burned this way before: a previous agency had quoted what sounded like a fixed price, then invoiced separately for nearly every text change and image swap during the build. By launch, the final bill was close to double the original number, and the client only found out gradually as invoices kept arriving. When we scoped their next project, we wrote out exactly what counted as included revisions versus a billable change request, in writing, before any work started. That single change eliminated the friction almost entirely.

About Price and Contract Terms

9. Is pricing fixed or ongoing, and what exactly is included? Ask for an itemized quote, not a lump sum. A breakdown that separates design, development, content migration, and post-launch support makes it far easier to compare agencies fairly, and makes it obvious if one bid is cheap because it's simply leaving something out.

10. What do changes outside the original scope cost? Projects almost always evolve along the way. Knowing the hourly or per-request rate for out-of-scope work in advance avoids unpleasant surprises later, and it's a fair question to ask even of an agency you already trust.

11. What's included in post-launch support, and for how long? Plenty of agencies launch a site and effectively disappear the moment the invoice is paid. Ask specifically what happens if something breaks in week two, whether that's covered, and what it costs if it isn't. This question matters more than most business owners initially assume, because a website is never really "finished" the way a print brochure is; it needs monitoring, updates, and occasional fixes for as long as it's live. We've written in more detail about why ongoing website maintenance is worth budgeting for from day one, rather than treating it as an afterthought once something breaks.

How Pricing Models Differ: Fixed Price, Hourly, and Retainer

The three common pricing structures aren't just different numbers, they carry different incentives, and understanding those incentives helps you pick the right fit for your project.

Fixed price means you agree on a defined scope and pay a set total. It's the most predictable option and works well when requirements are clear and unlikely to shift much, a standard business website with a known page count, for example. The catch is that "fixed" only protects you if the scope document is genuinely detailed; a vague scope with a fixed price is where change-order billing sneaks in later, exactly as it did in the example above.

Hourly means you pay for time worked, tracked and reported. It suits projects where requirements are likely to evolve, ongoing feature development, or work where nobody can fully define the scope up front. The tradeoff is that hourly billing puts the cost-control burden on you, an agency with no incentive to work efficiently can, in theory, let hours run long, so it matters more here that you trust the agency and get regular time reports.

Retainer means a fixed recurring fee, usually monthly, for an agreed block of ongoing work, maintenance, small updates, CRO experiments, content additions. It fits businesses that need a website actively managed rather than a one-off project delivered and forgotten. Retainers reward agencies for keeping you happy over the long term rather than maximizing billable hours on a single build, which is one reason many businesses eventually move from a fixed-price launch into a maintenance retainer once the site is live.

None of the three is inherently better, the right choice depends on how well-defined your project is and how much ongoing involvement you expect to need. What matters is that the agency can explain, clearly, why they're proposing the model they're proposing for your specific situation, rather than defaulting to whichever model is easiest for them to bill.

About Security and Compliance

12. How do you handle data privacy and security on this project? A clear, concrete answer signals that the agency actually understands its responsibilities, not just a generic "we follow all the regulations" with no detail behind it. A good answer names specifics: how contact forms handle personal data, whether cookie consent is implemented properly, how backups and access controls work, and who is responsible if there's a data breach. A bad answer is a single reassuring sentence with nothing underneath it if you ask a follow-up question.

Red Flags to Watch For

• Pricing that seems too good to be true, with no explanation for why it's so low. Sometimes there's a legitimate reason, an agency building a portfolio in a new niche, for instance, but if they can't explain the gap, assume something is being cut, usually testing, SEO basics, or post-launch support.
• Reluctance to commit to timelines or specify what's actually included. Vagueness at the proposal stage rarely becomes clarity later; it tends to get worse once you've already paid a deposit.
• No references, or references that can't be verified. A phone number that goes straight to voicemail, or a "client" who turns out to be a friend of the agency's owner, is worth walking away from.
• High-pressure sales tactics demanding a fast decision with no time to think it over. "This price is only good until Friday" is a tactic borrowed from car dealerships, not a normal part of a business relationship you're about to enter for months.
• An unwillingness to put anything in writing before you sign. If the process, the scope, or the ownership terms only exist as verbal promises, they aren't terms, they're hopes.

How to Score the Answers You Get

If you're evaluating more than one agency, it helps to score answers rather than just going on gut feeling, especially since a confident delivery style can make a vague answer sound more solid than it actually is. For each of the twelve questions, rate the response on three things: was it specific rather than generic, was it consistent with what's written in the proposal or contract, and did the agency seem comfortable being asked, rather than defensive. An agency that welcomes tough questions and answers them in writing is telling you something important about how they'll behave once you're a client and not just a prospect. One that gets visibly irritated at being asked is telling you something too.

Common Questions Business Owners Ask About This Process

Won't asking this many questions annoy a good agency and scare them off? No. A competent agency answers these questions regularly, they're not unusual, and treats them as a normal part of a professional sales process. If a serious set of questions genuinely puts an agency off, that's useful information in itself.

We're on a tight budget, do we still need to ask all twelve? Especially then. A limited budget makes it more important to know exactly what's included, because there's less room to absorb an unexpected change-order bill or a support gap after launch. The questions cost nothing to ask, and the answers often matter more, not less, when money is tight.

Should we just pick the cheapest agency that gives good answers? Not necessarily. Use the questions to filter out agencies that are clearly unreliable or dishonest, then choose among the remaining, credible options based on fit, chemistry, and relevant experience, not price alone. The cheapest credible bid and the best-fit credible bid aren't always the same one.

Why We Like Clients Who Ask These Questions

A client who asks sharp questions before signing anything is, in our experience, almost always a client who ends up satisfied, expectations are clear from the start, leaving no room for misunderstandings later. We're happy to answer all twelve of the questions above, openly and specifically, before you decide.

If you'd rather skip the search process altogether, here's how we approach new projects: take a look at our custom web design service to see the process, scope, and ownership terms in plain language, then book a free consultation and ask us any of the twelve questions above directly.