Материалы журнала опубликованы на английском языке. Русская версия сайта

StrategyPARTNER · EVIDENCE · RISK

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

Illustration: How to Choose a Software Development Company

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.

Gevorg AntonianFounder & CEO, Axiom Forge
In this article6 sections · 4 min

Ask for evidence you can open

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.

Meet the people who will build

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.

Read the proposal for its assumptions

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.

Check ownership and security early

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.

A scorecard for the shortlist

Score each company on the same lines. Strong signals are specific and checkable. Weak ones are adjectives.

Strong and weak signals when choosing a software partner
CriterionStrong signalWeak signal
WorkA live product or prototype you can openScreenshots without context
TeamYou meet the people who will buildSales staff only until signature
EstimateAssumptions and exclusions written downOne number without scope
OwnershipRepository and accounts in your nameAccess only after the final payment
After launchSupport terms and response times namedTo be discussed later
CommunicationVisible progress every weekUpdates on request

Start with a small paid stage

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

Questions leaders ask

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.

Sources

  1. NCSC — Supply chain security guidancencsc.gov.uk (opens in a new tab)
  2. OWASP — Top Tenowasp.org (opens in a new tab)

How Axiom Forge can help

Turn the guidance into an accountable product plan.

Axiom Forge connects product direction, UX, design and engineering for websites, apps and AI systems. Start with the business outcome, the people who must use the product and the operating constraints behind it.

Founder-led review · NDA on request · No obligation

See services and starting prices

Write to us

Email us — we reply in English, Russian or Armenian.

Our time now:

Analytics preferences

We use Google Analytics and Google Ads to understand which pages help visitors and to measure enquiries. Form contents and personal details are never sent to them.