SoftwareCrafting Logo

Vendor Selection

How to Compare Software Development Agencies

Portfolios are marketing. Compare on the things a bad agency cannot fake.

Anyone can show screenshots. Almost nobody will happily put you on a call with the engineer who will actually write your code.

7 criteria
That a weak agency cannot fake
Same brief
The only fair way to compare quotes
Ask us too
These questions apply to us equally

Quick Answer

Updated August 22, 2026

How should I compare software development agencies?

Score every agency on seven things rather than on their portfolio: who specifically writes the code and their seniority, whether you can speak to that person before signing, who reviews the work, what happens when someone is unavailable, whether the repository is yours from day one, what the exit and handover look like, and how they respond when you ask what went wrong on a recent project. The last one is the most revealing — agencies that cannot name a failure are either inexperienced or not being straight with you.

Criteria that matter

7

Shortlist size

3 agencies, one tier

Most revealing question

"What went wrong recently?"

Best for

  • Buyers running a first agency selection process
  • Teams with three proposals and no way to compare them
  • Anyone who has picked wrong before and wants a real process

Not best for

  • Procurement with a fixed evaluation framework already mandated
  • Very small engagements where the process costs more than the work
  • Buyers whose only criterion is price
Talk to a senior engineer

Side By Side

Strong signals versus weak ones

How to Compare Software Development Agencies — side-by-side comparison
What you are checkingWeak signalStrong signal
Who you meet in the sales processA salesperson or account managerThe engineer who will build it
Response to "who writes the code?""Our team"A named person, with their background
Code reviewNot mentioned, or billed separatelyStandard, and they explain how
Repository ownershipTheirs, handed over at the endYours, from the first commit
Estimating styleA single confident numberA range with assumptions named
Response to "what went wrong recently?"Nothing comes to mindA specific story and what changed after
Exit termsVague, or annual lock-inWritten notice period and handover scope
Response to a bad-fit briefEnthusiasm regardlessThey tell you it is not for them

Each Option In Detail

What each one is actually good and bad at

What to weight heavily

The signals that correlate with delivery rather than with sales quality.

Free to check, expensive to skip

Strengths

  • Named engineers with verifiable backgrounds, available to speak before you sign
  • Repository under your organisation from the first commit
  • A written notice period and a defined handover scope
  • Estimates as ranges with the assumptions stated next to them
  • A specific, unflattering story when you ask what went wrong recently

Limits

  • None of this is visible in a proposal document
  • It requires you to run calls rather than compare PDFs
  • Good agencies with poor sales presentation can look worse on paper

Best for: Any engagement where the outcome matters more than the paperwork

What to weight lightly

Signals that mostly measure marketing budget rather than delivery capability.

Cheap to produce, easy to fake

Strengths

  • Portfolios do confirm a company has shipped something
  • Awards and directory rankings occasionally reflect real client satisfaction
  • Team size indicates capacity, which matters for large programmes

Limits

  • Portfolio screenshots do not prove the work is still live or was built by the team you get
  • Most rankings and badges are paid placement
  • Client logos may represent a two-week engagement three years ago
  • A large team says nothing about who is assigned to you

Best for: A first-pass filter, and nothing beyond that

Decision Guide

If this is true, choose this

Decision rules for comparing software development agencies
IfChooseWhy
An agency will not let you speak to the engineerRemove themIt usually means the person selling and the person building are far apart.
Their estimate is a single confident number on a vague briefAsk for the assumptionsConfidence without assumptions is a sales technique, not an estimate.
They say yes to a brief that is clearly outside their strengthRemove themAn agency that never says no will not tell you when your plan is wrong either.
Quotes differ by more than about doubleRe-issue one written feature list to all of themMost enormous gaps are scope differences, not margin differences.
Everything looks equalRun a small paid trial with twoTwo weeks of real work reveals more than any number of calls.

The Honest Take

Use this framework on us

Every criterion here is one we expect to be measured against, and we would rather lose a deal to a better-fitting agency than win one we should not have. Ask us who will write your code and we will name them and put them on the call. Ask what went wrong recently and we will tell you about a project where we underestimated a third-party integration and what we changed afterwards. If an agency — including this one — cannot answer these plainly, that is the signal.

Do not hire us if any of these is true

  • You need a scale or certification profile a seven-person team cannot offer
  • Your evaluation is genuinely price-first and you accept the associated variance
  • The technology is outside what we work in, which we will tell you early
  • You want a supplier who does not question the brief

Still Deciding?

Send the brief and we will tell you which option fits

Including when that option is not us. A senior engineer reads every brief and replies with the lightest sensible next step rather than the largest one.

Quick Brief

Start the conversation here

Tell us what you are weighing up. We will say which option fits and why, even when it is not us.

Your Name

Work Email

What do you need help with?

Get an honest recommendation

FAQ

Questions people ask about comparing software development agencies

What should I ask a software development agency?

Who specifically writes the code, can I speak to them, who reviews it, what happens when they are unavailable, is the repository mine from day one, what does leaving look like, and what went wrong on a recent project. Those seven cover most of the risk.

How do I compare quotes that differ enormously?

Issue the same written feature list to everyone and ask what is excluded. Most gaps are scope and seniority differences rather than margin. If a quote is half the others, something is missing and it is usually QA, deployment, or maintenance.

Are agency awards and rankings meaningful?

Mostly not. Most rankings are paid placement or affiliate-driven. Verified client reviews on directories are somewhat better, but they still reward marketing effort. Treat all of it as a first-pass filter, never as evidence.

Should I run a paid trial?

Yes, whenever the engagement is large enough to justify it. Two weeks of real work on a real ticket tells you about communication, code quality, and honesty in a way that no number of sales calls will.

What is the biggest red flag?

An agency that agrees with everything. If nobody pushes back on your scope, your timeline, or your technology choice during the sales process, they will not push back when it matters either — and that silence is what you are actually paying to avoid.

Ready when you are

Not sure
where to start?

Tell us your goal and we'll suggest the smallest, fastest way to get there. We reply in under 4 working hours.