Neither predicts delivery.
A beautiful pitch deck tells you the agency has a good pitch team. A low day rate tells you the agency is willing to win on price, and possibly recover margin later through change requests. Neither tells you whether your project will land on time, integrate with your systems, or still be working 12 months after launch.
The questions below are the ones we wish every client asked us. They are harder to answer with a slide, which is exactly why they work.
1. Who actually does the work?
In many agencies, the people in the pitch room are not the people who build your product. Senior strategists and creative directors win the work, then hand it to a delivery team you have never met, sometimes in another country, sometimes through a subcontractor.
This is not automatically a problem. It becomes a problem when it is hidden.
Ask directly: who will be on this project day to day, and what percentage of their time is allocated to us? Then ask for names, roles and seniority in writing, ideally in the contract or statement of work. A good agency will commit to key people and agree what happens if someone leaves. An agency that refuses to name anyone until after signing is telling you something.
It is also worth asking to meet the delivery lead before you sign. A 30 minute conversation with the person running your project will tell you more than a 60 slide credentials deck.
2. How do you measure success?
Listen carefully to the answer. If the agency talks about "rollout completed", "all features delivered" or "launched on schedule", they are describing a timeline, not an outcome.
A rollout completed is a schedule. It says the work happened. It says nothing about whether conversion improved, whether support tickets dropped, whether your team can actually use the new platform, or whether customers noticed anything at all.
Strong agencies define success in terms of the business problem you hired them to solve. They will ask what you measure today, agree a baseline before work starts, and propose 2 or 3 metrics that the project should move. They will also be honest about which metrics they can influence and which depend on factors outside their control.
If an agency cannot tell you how they would know the project failed, they probably will not notice when it does.
3. What happens when scope changes?
Scope will change. Every experienced client and every honest agency knows this. New stakeholders join, priorities shift, a regulation lands, or user testing reveals that the original brief was wrong.
So the useful question is not "will you be flexible?" Every agency will say yes. That is a promise, and promises are cheap in a sales conversation.
Ask for the process instead. How is a change request raised? Who assesses the impact on cost and timeline? How quickly do we get an estimate? Who on our side approves it? What happens to work already in progress while a decision is pending?
Ask to see an example of a real change request from a previous project, anonymised if needed. An agency with a mature process will have one ready. An agency without one will either absorb changes silently until the budget breaks, or bill for them in ways you only discover at invoice time.
4. How do you handle our legacy systems?
Very few digital projects start from a blank page. There is almost always an ERP, a CRM, a product database, an identity provider or a 15-year-old system that nobody fully understands but everything depends on.
This is where projects break. Not in the design, and rarely in the front end, but at the integration seams: the points where new work has to exchange data with existing systems.
Ask the agency how they approach discovery on your technical landscape. Do they audit APIs and data quality before committing to a timeline, or do they assume integrations will work? Who on their team has hands-on experience with systems like yours? How do they coordinate with your internal IT team or other vendors who own parts of the stack?
A confident agency will want access to your technical people early. They will flag risks in the first weeks rather than the last. If the proposal treats integration as a single line item with a neat estimate, be sceptical.
5. What happens after launch?
Launch day feels like the finish line. In reality, it is the start of the part that determines whether the investment pays off.
Handover is the real test of an agency. Ask what documentation you will receive, and who it is written for: your developers, your content editors, or the agency's own future reference. Ask whether your team will be trained, and how. Ask who owns the code, the design files, the accounts and the credentials. Ask what support looks like in the first 90 days, and what it costs after that.
The best agencies build for independence. They want you to be able to run, change and extend what they built, with or without them. Agencies that make themselves quietly indispensable through undocumented systems and proprietary setups may keep your business longer, but not because they earned it.
The simplest test of all
Before you sign, ask the agency for the contact details of a client they have worked with for 2 years or more.
Then call them.
Not a case study, not a testimonial quote on a website, but a real conversation. Ask what went wrong, how the agency responded, and whether the people from the pitch were still involved a year later. Long relationships survive problems, so a 2+ year client can tell you how an agency behaves when things get difficult. That is the information that actually predicts delivery.
Our answers, openly
It would be unfair to publish these questions without answering them ourselves.
Who does the work? Wisefrog is founder-led. The people you meet in the first conversation are the people who shape and deliver your project, and we name them in the proposal.
How do we measure success? We agree the business outcome and a baseline before we start, and we report against it, not against a delivery checklist.
What happens when scope changes? Changes go through a written request with a clear impact on time and budget, approved by you before any work begins.
How do we handle legacy systems? We start with discovery on your existing stack and involve your technical team early, so integration risks surface in week 1, not month 6.
What happens after launch? You own everything we build. We document it for the people who will use it, train your team, and agree support terms up front.
And yes, we will happily connect you with long-standing clients.
Choosing an agency? Let's talk it through.
Book a 30 minute call with Wisefrog. Bring these 5 questions, and hold us to every answer.