How to Choose a Software Development Company: A Due-Diligence Checklist
A due-diligence checklist for choosing a software development company: evidence you can check, the people who will build, the proposal, ownership, security and a first paid stage.
The short answer
Judge a software partner on evidence you can check: work you can open, the people who will actually build your product, how the proposal handles assumptions, who owns the code and the accounts, and what happens after launch. Rankings, awards and long technology lists are weak signals. A short paid first stage is the most reliable test of all.
Weighing this for your business? Request a project review

Our take
Axiom Forge publishes its starting prices, labels concepts as concepts and shows work that can be opened and checked. Scope, cost and ownership are agreed in writing before the first invoice.
In this article6 sections · 4 min
A portfolio of screenshots proves that a company owns a design tool. Ask for products you can use: a live site, an app in a store, a prototype, a public tool. Ask what the company itself decided in that work and what it would do differently now.
Be careful with case studies built on famous names. Confirm what was actually delivered and by whom. Honest companies separate client work, their own products and concept designs.
The people in the sales meeting are often not the people who will write your product. Ask who leads the work day to day, how senior they are and how much of their time you are buying. Ask what happens if that person leaves.
A company’s location matters less than overlap in working hours, a shared working language and the habit of showing progress every week.
A serious proposal says what is included, what is not, and what it assumes about your content, your systems and your decisions. It defines how each deliverable will be accepted. One number on one page tells you nothing about what you will receive.
Compare proposals by what will exist on launch day, not by the total at the bottom.
Ask where the code will live from the first day, in whose name the cloud, domain and store accounts are opened, and when the rights to the work pass to you. These questions are easy before signing and painful after a dispute.
Ask a few plain security questions as well: how access to your systems is granted and removed, how secrets are stored, how third-party components are kept up to date. The OWASP Top Ten is a reasonable shared vocabulary, and the UK National Cyber Security Centre’s supply chain guidance explains why your supplier’s habits become your risk.
Score each company on the same lines. Strong signals are specific and checkable. Weak ones are adjectives.
| Criterion | Strong signal | Weak signal |
|---|---|---|
| Work | A live product or prototype you can open | Screenshots without context |
| Team | You meet the people who will build | Sales staff only until signature |
| Estimate | Assumptions and exclusions written down | One number without scope |
| Ownership | Repository and accounts in your name | Access only after the final payment |
| After launch | Support terms and response times named | To be discussed later |
| Communication | Visible progress every week | Updates on request |
Nothing tests a partnership like real work. A paid definition stage of one or two weeks produces a scope, a prototype or a technical plan that you keep. You see how the team thinks, how it communicates and whether its estimates hold.
If the stage goes badly, you have lost little and learned a great deal. If it goes well, the main contract begins on evidence, not on hope.
Discuss your project with the founder
How many proposals should I compare?
Three is usually enough. Fewer gives no comparison; more costs weeks and encourages choosing by price alone. Give all three the same brief so that the proposals can be compared line by line.
Does the company need to be in my country?
No. What matters is overlap in working hours, a shared working language, a contract you can enforce and visible progress every week. Many successful products are built by teams in another country.
What should I ask for before signing?
A written scope with acceptance criteria, a payment schedule tied to deliverables, the ownership and handover terms, the names of the people who will do the work, and the terms of support after launch.


