Agency pitches are designed to sound similar. Everyone has a proven process, a collaborative approach, and a portfolio of delighted clients. Differentiating between them based on the standard pitch is nearly impossible.
These seven questions cut through the polish and get to what actually determines project outcomes.
The most important question, asked almost nowhere near enough.
Large and mid-size agencies routinely pitch with senior talent and deliver with juniors. The person presenting your project and the person building your project may never be in the same room. Ask explicitly: which specific people will work on this project, and what is each person's role?
A credible answer names people. An evasive answer talks about "the team" or "our developers" in the abstract.
For boutique studios, the answer is often simple: the people you're talking to. That's a meaningful advantage — what you see in the pitch is what you get in the build.
An agency that builds in everything builds in nothing deeply. The answer you want is specific: we build in Next.js with TypeScript, occasionally Astro for content-heavy sites. We don't do WordPress unless the client has an existing WP infrastructure we're working within.
A vague answer — "we use the best technology for each project" — is a red flag. It sounds flexible. It means they'll use whatever their available developers happen to know.
Ask why, not just what. The reasoning tells you whether the choice is considered or arbitrary.
Revision scope is where most project relationships go bad. Without a clear policy, every change request is a negotiation, and negotiations slow projects and breed resentment.
What you want to understand:
A good agency has this written into their contract. If the answer is "we're flexible" or "we'll figure it out as we go," you're setting up a conflict.
This question reveals the risk structure of the engagement. See our full post on fixed-price web development for the details, but the short version:
Hourly billing means your cost is open-ended. Fixed billing means the agency absorbs scope risk. Both models are legitimate; both have conditions where they work better.
The key question is: what causes additional cost outside the initial quote? Any agency that can't answer this clearly is structuring a project you'll have no visibility into financially.
This matters enormously and is asked far too late.
You should own:
Some agencies retain code ownership as leverage. Some put the domain in their account by default. Some use internal tools that aren't transferable. Ask before you sign — not after the site is live.
The launch is not the end. Dependencies update, forms break, analytics stop firing, content needs updating. Most agencies offer some form of post-launch support — but the terms vary enormously.
What you want to understand:
A studio that provides 30 days of included post-launch support is giving you something meaningful. A studio that hands off a zip file and sends an invoice is not.
This is the most underasked question and the most revealing answer.
Agencies that know their limits — and say them clearly — are more trustworthy than agencies that claim capability in everything. "We don't do design-in-the-browser — we prototype in Figma first" tells you their process. "We don't take projects without a discovery phase" tells you they scope seriously. "We don't do WordPress" tells you they have standards.
An agency that never says no to anything is probably saying yes to things they shouldn't. In web development, over-commitment is how quality falls apart.
These questions aren't gotchas. They're alignment tools. A good agency will welcome them — clear answers to clear questions reduce misunderstanding for both parties.
If an agency becomes defensive or vague when asked any of these, treat that as signal. The pitch is the best version of the relationship. If the answers are evasive before the contract is signed, they will be evasive after.
Ask early. Sign once you're satisfied. Then focus on building something good together.
About to evaluate web agencies? Start a conversation with us — we'll answer all seven questions directly and tell you honestly whether we're the right fit.
We take on a small number of projects each quarter. Tell us what you're building.
The real cost of a startup website — broken down by tier, stack, and scope. Template vs custom, showcase vs platform, what hidden costs nobody quotes upfront.
Large agencies have the portfolio and the pitch deck. Boutique studios have the accountability, the stack ownership, and the direct line to the people actually building your product.