How to Choose a Software Development Agency
Sergio JimenezOctober 21, 20266 min read
Choosing a software development agency is mostly an exercise in telling competent suppliers apart from confident ones. Both groups have good websites, both show you logos, and both will tell you they are senior. The difference shows up in month four, when the first thing you did not anticipate arrives.
These are the questions that separate them, and the answers worth accepting.
Ask what happens when the scope changes
It will change. The only question is whether the agency has a process for it or a grievance about it.
A good answer sounds procedural and slightly boring: changes are priced, you approve them, the timeline moves by a stated amount. A bad answer is either "we are flexible, no problem" or a long explanation of why the contract protects them. The first means you will be billed for ambiguity later; the second means every conversation for the next six months will be about the contract rather than the product.
Ask who owns the code and the accounts
The answer should be you, in writing, with no conditions attached to final payment of anything beyond the current invoice.
Then ask the sharper version: whose name is on the cloud account, the app store listings, the domain registrar and the payment processor? Agencies that put their own name on these are not necessarily acting in bad faith, it is often just convenience, but the result is identical to a hostage situation when you want to leave. Everything should be created under your organisation from day one, with the agency added as a user you can remove.
Ask to meet the people who will actually write the code
The single most common failure mode in this industry is the senior engineer who attends the sales call and is never seen again. Ask directly: who is on this project, what percentage of their time, and for how long. Ask to speak to them before you sign.
If the answer is vague, or if you are told the team will be assigned after signature, you are buying an unknown. Reasonable staffing changes happen and that is fine. What is not fine is not knowing who you are hiring.
Ask how often you will see working software
The right answer is every two weeks at worst, on a real device or a real URL, by you, not in a screen share where someone drives.
Demos where you cannot touch the product hide an enormous amount. A build you can open yourself on your own phone is the only honest progress report, because it is the only one you can test against your own expectations rather than against a prepared script. Our Studio engagements are built around this for exactly that reason: you try candidate work on your own device and approve what ships.
Ask what their tests cover
Not "do you write tests", to which everyone says yes. Ask which parts of the system are covered and which are not, and expect a specific answer.
Any serious team can tell you instantly that payments, authentication and permissions are tested and that the marketing page animations are not. A team that claims everything is tested is either misleading you or wasting your money. A team that cannot answer does not have tests.
Ask what happens at 3am
Who gets paged, how fast do they respond, and what does it cost? This question sorts agencies faster than any other, because answering it requires having thought about production rather than about delivery.
A supplier who treats launch as the finish line will struggle here. The honest answers range from "we offer a support retainer with these response times" to "we do not do support, and here is how we hand over so your team can", and both are acceptable. "We are always available" is not an answer, it is a feeling.
Ask for a reference from a project that went badly
Everyone has one. An agency that claims otherwise has either not worked long enough or is lying, and both are disqualifying.
What you are listening for is not the disaster, it is the account of it. Did they see it coming, did they say so early, and what did they change afterwards? Suppliers who can describe their own failures accurately are the ones who will tell you the truth while there is still time to act on it.
The signals that should worry you
- A quote with no written scope. A single number with nothing attached is a guess you will pay for twice.
- An estimate that arrives in under a day for a complex product. Either they did not think about it, or they have padded it heavily.
- Resistance to a paid discovery. Scoping properly takes work. An agency that waves it away is planning to discover the scope while billing you for the build.
- Nobody disagrees with you. If your requirements contain no tension and the supplier spots none, they are not reading them.
- Prices far below everyone else. The work does not get cheaper, it gets juniorer, or it gets subcontracted to a team you never meet.
What a good proposal contains
| Section | What it must say |
|---|---|
| Scope | What is included and, explicitly, what is not |
| Team | Named people, roles, allocation |
| Cadence | When you see working software and how you give feedback |
| Change process | How new requests are priced and approved |
| Ownership | Code, repositories, cloud accounts, store listings, domains |
| Environments | Development, staging and production, named and separate |
| After launch | Support terms, response times, handover |
Frequently asked questions
How do I choose a software development agency?
Judge the process, not the portfolio. Ask who writes the code, how often you see working software, how scope changes are priced, who owns the accounts, what the tests cover and what happens during a production incident. Portfolios show what a team could do with a good client and a good brief. Process shows what they will do with yours.
How much should a software development agency cost?
In 2026, expect roughly 40 to 90 dollars an hour in Latin America and eastern Europe, 90 to 160 in western Europe, and 120 to 250 in the United States. Price differences within a region usually reflect seniority and how much of the work is subcontracted, not quality in any simple sense.
Should I choose an agency or hire in house?
Hire in house when you know what you are building and will keep building it for years. Use an agency when you need several skill sets for a few months each, when speed matters more than permanence, or when you do not yet have the technical leadership to interview engineers well.
What is a paid discovery and should I pay for one?
A short engagement, usually one or two weeks, that produces a written scope, an architecture decision record and a real estimate. Yes, pay for it. The alternative is a free estimate based on guesses, which gets corrected later at your expense. A good discovery is yours to take elsewhere.
What are the warning signs of a bad development agency?
A quote with no written scope, an estimate produced in hours for a complex product, refusal to name the engineers, demos you cannot touch, accounts in their name, and no answer for what happens when production breaks at night.
How long should an agency contract be?
Long enough to deliver something meaningful and short enough that leaving is realistic. Two week cycles with the right to stop at the end of any of them works well. Twelve month lock ins with no exit are a bet on a relationship you have not tested yet.
Where to start
Shortlist three suppliers, send all three the same one page brief, and compare the questions they ask rather than the documents they send back. The one that finds the hardest problem in your brief before quoting on it is usually the one to pick.
If you want to see what that looks like, send us the brief. The first call and the written scope that follows cost nothing and are yours to take anywhere.
