Discovery Calls With Web Agencies: 14 Questions to Ask Before Signing

What to ask a web agency on a discovery call is not, as most buyers assume, a list of questions about price and timeline. The strongest questions are diagnostic. Ask how the agency decides what technology to build on, ask what its last few projects taught it, ask exactly what happens in the ninety days after launch, and ask who specifically will be doing your work. Price and timeline matter, but you can compare those on a spreadsheet. What you cannot compare on a spreadsheet is whether the agency actually thinks before it builds, and the discovery call is the only sample of that thinking you get before you sign.

The thing to hold in your head for the whole hour is that a discovery call is a two-way audition. The agency is using the call to decide whether you are a good client, with a realistic budget and a workable brief. You should be using the exact same hour to decide whether the agency does real discovery or simply takes orders. The way an agency runs a discovery call is a free, honest preview of how it will run your project. An agency that listens carefully on the first call will listen carefully during the build. An agency that talks for an hour about its awards will hand you an hour of output and no questions later. The fourteen questions below are grouped by what each one is really testing, and for each one it helps to know both the answer you want and the red-flag answer that should make you pause.

How a Good Agency Runs the Call

Before you get to your questions, watch how the call itself is run, because three of your fourteen tests are about the call rather than the project. The first is simple: ask who is on this call and whether they will be on your project. The answer you want is that the people talking to you are the people who will lead or do the work, or that the agency is upfront that a salesperson is hosting and will introduce you to a named delivery lead at the next step. The red-flag answer is a polished salesperson who cannot answer a single technical question and never names the people who will actually build the site. That is the classic bait and switch, where the team that wins the work is not the team that does it.

The second test is preparation. Ask what the agency already knows about your business before this call. A good agency will have looked at your current website, glanced at two or three competitors, and formed an opinion, so the call opens with observations rather than a generic deck. A red flag is zero preparation, where they ask you to explain your industry from scratch and run a script that could be aimed at any client in any sector. An agency that templates the discovery call will template the build.

The third test you do not ask out loud, you measure. Watch the ratio of listening to pitching. A good agency spends most of the hour asking about your goals, your customers and your constraints, and only a small part describing itself. If the call is sixty minutes of logos, awards and process slides with barely a question about your business, you have learned something important: this agency leads with itself, and a monologue now becomes a monologue later. One related signal sits in the same bucket. Notice whether the agency pushes you to sign on the call. A confident shop gives you room to think and compare. Pressure to commit today, a discount that expires at midnight, a contract emailed before you have hung up, all of that tells you the agency is worried you will look elsewhere and find better.

Testing Technical Depth

The next four questions probe whether the agency understands what it is building, and this is where brochure language gets exposed fastest. Start by asking how they decide what to build the site on. A strong answer is reasoned and specific to your project, weighing performance, who will edit the content, how portable the result is, and the skills your team already has. They should be able to name the trade-off they are recommending and why. The red-flag answer is "we always use this," delivered as if one tool fits every job. It does not. An agency with one hammer chose that hammer for its own convenience, not for your project, and you will inherit the consequences for five years.

Then ask how they make a site fast and how they prove it. A professional answer is made of numbers. It names Core Web Vitals targets, an LCP under 2.5 seconds, an INP under 200 milliseconds, a CLS under 0.1, measured on real mobile field data, with a date you can re-test. The red flag is the comfortable phrase that means nothing: "we follow best practices," "it will be fast," with no metric, no tool and no measurement method. Performance is the easiest thing to claim and the easiest to fake on a fast laptop, so an agency that will not attach a figure to it is not committing to it.

Accessibility is the question most buyers forget and the one that increasingly carries legal exposure, so ask how the agency handles it. A good answer builds to WCAG 2.2 AA as a baseline, tests with a keyboard and a screen reader, and treats accessibility as part of the build rather than a bolt-on. A serious red flag is the offer to "just add an accessibility overlay or plugin." Overlays do not make a site genuinely accessible, and they have themselves become a magnet for litigation. An agency reaching for an overlay is telling you it does not build accessibly in the first place. Finally, ask what the site looks like under the hood and whether another developer could take it over. The answer you want is a clean, documented, standards-based build that any competent developer could maintain. The red flag is a bespoke in-house framework only this agency understands, or a site trapped inside a proprietary builder's format, because either one quietly converts a technical choice into a lock-in.

Reading Process Maturity

Three questions test whether the agency runs projects or improvises them. Ask the agency to walk you through its process from kickoff to launch. A mature shop describes a named, repeatable sequence: discovery, design, build, review, quality assurance and launch, with defined points where you check the work and sign it off. The red flag is "we just get started" or a vague gesture at how it usually goes. No process means no predictability, and no predictability is how a clear brief drifts into a late, over-budget project.

Next, ask how they handle changes and feedback during the build. A good answer includes a defined number of feedback rounds, a written change-order process, a single tool for collecting comments, and a clear line between fixing a bug and adding a new feature. Be wary of two answers here. "Unlimited revisions" sounds generous but is a trap, because the cost of those revisions has to live somewhere, either in an inflated starting price or in a project that never quite finishes. The opposite red flag is no feedback process at all, which means every change becomes a negotiation. Then ask how and how often you will communicate. You want a named cadence, a weekly check-in, a single point of contact, a shared channel or project tool, and a stated response time. "Email us whenever" with no structure is how agencies go quiet halfway through a build, and the discovery call is your one chance to catch that before it happens.

Checking Post-Launch Posture

Two questions reveal whether the agency sees launch as the finish line or the start of a relationship. Ask what happens in the first ninety days after the site goes live. A good answer describes a defined warranty or snagging period during which anything that does not work as specified is fixed at no charge, alongside a proper handover and training for your team. It draws a clear line between a defect, which the agency owns, and a new feature, which is paid work. The red flag is an agency for which the project simply ends at launch, with no warranty and bugs billed from day one. A warranty is an agency betting on its own quality, and an agency that will not make that bet is quietly telling you it expects defects.

Then ask what ongoing maintenance and support look like, and whether they are optional. The answer you want is a real service: updates tested on staging before they reach production, backups with a stated frequency, uptime monitoring, security patching, a defined response time and a regular report, priced transparently and offered as a choice. There are two red flags. One is no maintenance offering at all, which leaves your site to rot, and an unmaintained site is a security incident waiting to happen because outdated plugins are the most common way sites get compromised. The other is maintenance that is mandatory and bundled so tightly it becomes another reason you cannot leave. Good maintenance is something you choose because it is worth it, not a leash.

The Commercial Questions Worth Asking Now

The last two questions are commercial, and while a contract review deserves its own careful pass later, two things belong on the discovery call itself. Ask exactly what is and is not included in the price, and how extras are priced. A good agency gives you a written scope and an hourly change rate stated in the contract, with a quote before any extra work starts. The red flag is a single vague all-in number and a change rate that does not surface until you are mid-project, which is the lowball-then-bill pattern: win on price, profit on changes once you have no leverage to walk.

Finally, ask who owns the site, the code and the domain when the project is done. The answer you want is unambiguous: you own all of it, the work is assigned to you in writing on final payment, and the domain and hosting account are registered in your name. The red flag is "we own it and you licence it from us," a domain registered to the agency, or hosting bundled into a reseller account you have no login for. If an agency gets defensive when you raise ownership on the first call, you have learned everything you need to know about how the relationship is built.

Booking a Discovery Call With WitsCode

We have built more than 250 sites, which means we have also run a great many discovery calls from the agency side of the table. We know exactly what a good one feels like, because we hold ourselves to the same things this article tells you to look for. We prepare before the call by looking at your current site and your market. We listen more than we pitch, because the first hour should be about your business and not our awards. We name the actual people who will do your work. We will not push you to sign anything on the call, and you will own your code, your domain and your hosting when we are done.

If you have a project in mind, book a discovery call with us and use it as your practice run. Bring all fourteen questions and ask us every one, even if you go on to hire someone else. A good discovery call should leave you better informed whether or not it ends in a contract, and we are happy to be the call that sets the bar you measure the others against.