How to Choose a Development Agency

Choosing a development agency is one of the most important decisions you will make in a software project. After working on software projects for more than two decades, both inside large technology organisations and alongside founders building their first platforms, I've seen how often agency selection determines whether a project succeeds or struggles. Get it right and you have a team that builds what you need, keeps you informed, and delivers something you can rely on. Get it wrong and you are months in, over budget, and arguing about what was agreed.

This guide walks you through how to evaluate agencies properly — without needing a technical background to do it.

Why agency selection goes wrong

Most people choose the wrong agency for one of three reasons.

They go on price alone. The cheapest quote wins. But a low quote often means a narrowly scoped estimate — one that grows significantly once the real work begins. By the time that becomes clear, you are already committed.

They go on first impressions. The agency had a nice website, a confident sales call, and a portfolio of work that looked impressive. But looking good and building well are different skills. Plenty of agencies are excellent at winning business and poor at delivering it.

They skip the awkward questions. Nobody wants to feel difficult in an early conversation with a potential supplier. So the hard questions about timelines, about what happens when things go wrong, about who owns the code — do not get asked. And then they matter.

The good news is that none of this is complicated to avoid. It just requires a bit of structure and a willingness to treat this decision like any other significant purchase.

What to look for when evaluating an agency

When you are assessing an agency, ignore the surface-level stuff; the branding, the office location, the size of the team. Focus on these six things instead.

Evidence of similar work

Have they built something like what you need before? Not in the same industry necessarily, but a similar type of project, similar complexity, similar scale, similar kind of users. Ask to see it. Ask to speak to the client who commissioned it.

How they handle the brief

A good agency asks questions before they quote. If someone sends you a price within 24 hours of a first conversation, that is not efficiency, it is guesswork. You want an agency that slows down at the start, asks what you are trying to achieve, and comes back with a considered response.

How they communicate

You will be in a working relationship with these people for months. How do they communicate? Are they clear? Do they respond quickly? Do they explain things in plain language or do they hide behind jargon? The way an agency behaves before you hire them is usually the way they behave after.

What the contract actually says

Two things matter most in any development contract. First: who owns the code once it is built? It should be you. Second: what is the payment schedule tied to? It should be tied to milestones and deliverables, not just time. If a contract is vague on either of these, that is a problem.

Their process for handling change

Requirements change during a build. That is normal. What matters is whether the agency has a clear, fair way of dealing with it. Ask them directly: if we need to change something mid-project, how does that work? What gets agreed in writing? What does it cost? The answer tells you a lot.

References you can actually speak to

Not written testimonials on a website. Real clients you can call. Ask them: did the project come in on budget? Did it take as long as you were told? Would you use this agency again? Most agencies will provide references, but few buyers actually call them. Call them.

Red flags to watch for

Pause and ask questions if you see any of the following.

• They cannot show you a relevant example of previous work
• They quote a fixed price before fully understanding what you need
• They cannot clearly explain their process for managing the project
• They are vague about who owns the code at the end
• They discourage you from getting a second opinion
• They push for a long commitment before delivering anything
• They cannot name a single person who will be your main point of contact
• They make promises about timelines that seem too good to be true
• References are unavailable or only offered as written quotes
• Jargon is used to answer simple questions. Clarity should never require a glossary

None of these are automatic disqualifiers, but each one deserves a direct conversation. If the answers do not satisfy you, trust that.

A simple scoring framework

When you have spoken to two or more agencies, use this framework to compare them side by side. Score each agency from 1 to 5 on each area. Add the scores up. It will not make the decision for you, but it will make the comparison honest.

Print this out and fill it in by hand if that helps. The point is not to be scientific; it is to stop you making the decision based on whoever made the best impression in the sales call.

Downloadable vendor scorecard

The scoring table above is a starting point. The full vendor scorecard from Qube Catalyst gives you a more detailed evaluation tool — with guidance on how to weight each factor based on the type of project you are commissioning. It covers:

• Evaluation criteria across seven areas
• Guidance on what a good and poor answer looks like for each
• A scoring summary you can share with a colleague or advisor
• A notes column for recording what each agency actually said

Getting an independent view

Even with a good framework, agency selection is hard when you do not have a technical background. You can ask the right questions and still not know whether the answers you are getting are honest.

This is where an independent review helps. Before you sign anything, having someone assess the proposal on your behalf someone with no commercial interest in the outcome can surface issues that are easy to miss.

Things an independent review typically catches:

• Quotes that are low because key elements have not been included in the scope
• Payment schedules that front-load your risk and back-load the agency's
• Contract terms that leave code ownership unclear
• Timelines that are unrealistic for the scope described
• Proposals that use impressive language to describe a generic approach

It is not about distrust. Most agencies are not trying to deceive you. But without independent input, you have no way of knowing what you do not know and that is where the expensive surprises come from.

Quick checklist: before you sign with an agency

• I have spoken to at least two agencies and compared them directly
• I have seen relevant examples of their previous work
• I have spoken to at least one of their previous clients directly
• I have asked about their process for managing changes mid-project
• I understand who owns the code once the project is complete
• I know the payment schedule and what it is tied to
• I have a named point of contact for the project
• I have had the proposal reviewed by someone independent of the agency