How to choose a software development partner
A practical checklist for evaluating an agency or studio before you commit budget.
Short answer
Choose a software development partner on evidence, not pitch: ask to see software they built and still operate, insist on a small paid first engagement, confirm who actually writes the code, and check that they can explain trade-offs in plain language. Teams that operate their own products tend to make better long-term architecture decisions.
Look for operators, not just builders
There is a large difference between a team that ships a project and disappears, and one that has had to live with its own decisions in production. Operating software teaches lessons that building alone never does: what breaks at 3am, what costs money at scale, and which clever abstraction becomes a liability in year two.
Ask a prospective partner what they have built and still run today. If everything in their portfolio was handed off at launch, they have never had to pay the cost of their own shortcuts.
Ask who actually writes the code
A common failure pattern is a senior engineer in the sales conversation and a junior team on delivery. Ask directly who will work on your project, how much of their time you get, and whether you can talk to them before signing.
Start small and paid
The most reliable evaluation is a small, scoped, paid engagement, an architecture review, a spike, or a first slice of the product. You learn more from two weeks of real work than from any number of proposals, and the cost of being wrong stays low.
Warning signs
- They agree to a fixed price and timeline before understanding the problem.
- They cannot explain a technical trade-off without jargon.
- They propose a rewrite before reading your code.
- Their estimates never change as scope becomes clearer.
- You never meet the engineers who will do the work.
Questions worth asking
- What have you built that you still operate?
- Who specifically will write this code, and what else are they working on?
- What would you do first, and why that first?
- What do you think is risky about what we are asking for?
- What happens to the code and knowledge if we stop working together?
Common questions
How much should a software development partner cost?
- Cost varies widely by scope and seniority, but be sceptical of both extremes. Very low rates usually mean junior delivery and rework; very high rates should come with proven senior engineers and operational experience. Judge on total cost to a working outcome, not hourly rate.
Should I hire an agency or build an in-house team?
- In-house is better when the software is your long-term core and you can attract and manage engineers. A partner is better when you need to move now, need senior judgement you cannot hire yet, or the work is a defined phase. Many teams use a partner to build the foundation and hire in-house to operate it.
How do I avoid vendor lock-in?
- Own your repositories, cloud accounts, and domains from day one. Require documentation and readable code as deliverables, and agree up front what handover looks like.