How to choose a software development company for your startup: criteria, questions, red flags

What matters more than price when choosing a development partner?

What matters most is whether the partner reduces the risk of building the wrong thing. At idea or pre-seed stage your biggest threat is not a bug; it is spending the round on features nobody uses.

CB Insights calls running out of money the final cause of death rather than the root problem. A good development partner works on the root: it asks which assumptions you need to test, proposes a smaller first release and tells you when a feature can wait. If the first call is all frameworks and day rates, something is missing. If you have not tested demand yet, start with how to validate a startup idea before you sign a build contract.

What do experienced buyers of software ask for?

Experienced buyers ask for frequent working software, clear accountability and control over what is built. You do not have to guess what that looks like: the US government wrote it down. The Digital Services Playbook, used by federal digital teams, asks contracts to require frequent deliverables rather than long gaps between milestones, to hold vendors accountable for what they deliver, to keep software and data built by third parties under the buyer's control, and to include a warranty period in which vendors fix defects at no extra cost.

A seed-stage startup does not need a procurement department, but the same four ideas scale down well. They are also a neutral yardstick: a vendor who is comfortable with them is usually comfortable being measured.

Which criteria should you use to compare vendors?

Use criteria you can check with one question and one piece of evidence. We built the grid below around what still matters six months after launch, when switching vendor has become expensive.

For the quality row, the DORA metrics, from a long-running research programme on software delivery, give you a shared vocabulary: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate. You do not need a vendor to report all five. You need them to answer calmly when you ask how they keep releases stable.

What questions should you ask before signing?

Ask questions that force concrete answers: who, when, where, and what proof. Send this list, unchanged, to every vendor on your shortlist:

1. Who is the single accountable lead, and how many hours a week will they give the project?
2. Can I try a comparable product you shipped, or speak to the founder who commissioned it?
3. Fixed price, time and materials, or a mix? What happens when scope changes mid-build?
4. Where will the application run, and who pays for and controls the hosting?
5. If you process our users' personal data, will you sign a data processing agreement?
6. Which open-source or third-party components will you use, and under which licences?
7. What exactly do we receive at the end: code, documentation, credentials, release instructions?
8. If we changed vendor tomorrow, how long would another team need to take over?

What are the red flags when choosing a development partner?

The clearest red flag is a quote that arrives before any questions about your users. The others are quieter:

• Everything, immediately: no feature is challenged and the scope grows instead of shrinking.
• Accounts in the vendor's name: domain, hosting, repository or app store accounts registered to them ‘for convenience’.
• No interim demos: you will see the product ‘at the end’.
• Sellers are not builders: nobody can tell you who will write the code.
• A silent contract on code ownership, third-party licences and handover.
• Impossible guarantees: fixed dates on undefined scope, or promised business results.

What should the contract say about code and accounts?

The contract should transfer ownership of the code written for you to your company, in writing, and say when that happens. In the UK, the US and Italy, among others, an outside developer owns what they write unless an assignment says otherwise: in the UK, for example, an assignment of copyright ‘is not effective unless it is in writing’ and signed (CDPA 1988, s. 90). The EU, US and Italian rules, and the clauses to check, are in our guide to who owns the code in a software contract.

Ownership on paper is half of it; control is the other half. Repository, hosting, domain, app store accounts, payment provider and analytics should sit under your company, with the vendor invited as a collaborator. This article is general guidance, not legal advice: have a lawyer review the final contract.

How do you compare quotes that are far apart?

Compare scope, not totals: two very different quotes usually describe two different products. Price is driven by platforms (web only, or iOS and Android too), integrations, design depth, data migration, security requirements and post-launch maintenance. Our breakdown of MVP development cost shows how those factors stack up for a first release.

Do you need a development company at all?

Not always. If the real question is which model fits, compare agency vs freelancer vs in-house. If what you lack is someone to own technical decisions, read about the fractional CTO model. And if you are tempted by a visual builder, check first when no-code vs custom development makes sense.