Choosing a digital agency: 5 questions that really matter

Most digital agency selection processes reward the wrong things. A procurement team sends out an RFP, 6 agencies respond and the shortlist is decided by 2 factors: how polished the pitch looked and how sharp the price was.

Neither predicts how well they’ll deliver.

A beautiful pitch deck tells you the agency has a good pitch team. A low day rate tells you the agency wants to win on price and may claw back the margin later through change requests. Neither tells you whether your project will land on time, connect properly with your systems or still work 12 months after launch.

The questions below are the ones we wish every client asked us. They’re harder to answer with a slide, and that’s exactly why they work.

1. Who actually does the work?

At many agencies, the people in the pitch room aren’t the people who build your product. Senior strategists and creative directors win the work and then hand it over to a delivery team you’ve never met, sometimes in another country, sometimes through a subcontractor.

That isn’t automatically a problem. It becomes one when it’s hidden.

Ask directly: who works on this project day to day, and what percentage of their time is reserved for us? Then ask for names, roles and seniority in writing, ideally in the contract or statement of work. A good agency commits to key people and agrees what happens if someone leaves. An agency that only wants to name names after signing is telling you something too.

It also pays to meet the delivery lead before you sign. A 30-minute conversation with the person who will lead your project tells 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 complete", "all features delivered" or "launched on schedule", they’re describing a timeline, not a result.

A completed rollout is a schedule. It says the work happened. It says nothing about whether conversion improved, support tickets went down, your team can actually use the new platform, or customers noticed anything at all.

Strong agencies define success in terms of the business problem you hired them for. They ask what you measure today, agree a baseline before work starts and propose 2 or 3 metrics the project should move. They’re also honest about which metrics they can influence and which depend on factors outside their control.

If an agency can’t tell you how they’d know the project had failed, they probably won’t notice when it does.

3. What happens when the scope changes?

The scope will change. Every experienced client and every honest agency knows that. New stakeholders join, priorities shift, new regulation arrives or user testing shows the original brief was wrong.

So the useful question isn’t "are you flexible?" Every agency says yes. That’s a promise, and promises are cheap in a sales conversation.

Ask about the process instead. How is a change request submitted? Who assesses the impact on cost and timeline? How quickly do we get an estimate? Who approves it on our side? What happens to work in progress while a decision is pending?

Ask for 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 quietly absorbs changes until the budget breaks, or charges for them in a way you only discover when the invoice arrives.

4. How do you deal with our legacy systems?

Very few digital projects start with a blank page. There’s almost always an ERP, a CRM, a product database, an identity provider or a 15-year-old system nobody fully understands but everything depends on.

This is where projects get stuck. 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 of your technical landscape. Do they check APIs and data quality before committing to a timeline, or do they assume integrations will just 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 managing parts of the stack?

A confident agency wants early access to your technical people. They flag risks in the first weeks instead of the last. If the proposal treats integration as 1 line with a neat estimate, be sceptical.

5. What happens after launch?

Launch day feels like the finish line. In reality it’s the start of the part that decides whether the investment pays off.

The handover is the real test of an agency. Ask what documentation you’ll get and who it’s written for: your developers, your content editors or the agency itself as a reference for later. 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 quietly make themselves indispensable with undocumented systems and proprietary, closed setups may keep you as a client longer, but not because they earned it.

The 5 questions for your digital agency at a glance

• ✓Who actually does the work, and how much of their time is yours?
• ✓How does the agency measure success: against a business result or a delivery checklist?
• ✓What happens when the scope changes, and how does a change request work?
• ✓How does the agency deal with your legacy systems and integrations?
• ✓What happens after launch: documentation, training, ownership and support?

Want to see an agency that answers these questions itself? Read who we are or explore our work. If you want to handle scope changes well, the Agile Manifesto is still worth a read.

Frequently asked questions

The simplest test of all

Before you sign, ask the agency for the contact details of a client they’ve worked with for 2 years or more.

And actually call that client.

Not a case study, not a testimonial 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 client of 2 years or more can tell you how an agency behaves when things get hard. That’s the information that really predicts how well they’ll deliver.

Our answers, in the open

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 that, not against a delivery checklist.

What happens when the scope changes? Changes go through a written request with a clear impact on time and budget, which you approve before any work starts.

How do we deal with legacy systems? We start with discovery of your existing stack and involve your technical team early, so integration risks surface in week 1, not month 6.

What happens after launch? Everything we build is yours. We document it for the people who will work with it, train your team and agree support terms upfront.

And yes, we’re happy to put you in touch with clients we’ve worked with for a long time.

Looking for a digital agency? Let’s go through it together.

Book a 30-minute call with Wisefrog. Bring these 5 questions and hold us to every answer.