How do you choose a software development company?
Quick answer
Judge a software company on how it works, not on its sales pitch. Ask who you will actually talk to, how it quotes, whether you own the code, what happens after launch, and ask to speak to a past client. The answers matter more than the size of the company or the length of its client list.
Vastavik Bajpai , Founder
· 2 min read
Every software company website says the same things: experienced, reliable, on time. None of that is checkable. What is checkable is how a company behaves in its first conversation with you. Here is what to look for.
Who will you talk to?
Ask whether the person you brief is the person who will build it. If your questions will be relayed through an account manager, expect delays and misunderstandings. Small teams often win here simply because there is nobody in between.
How do they quote?
A quote that prices each part shows the company has understood the work. A lump sum after a fifteen-minute call shows it has not. Be equally wary of a quote that is much lower than the others; something has been left out.
Will you own the code?
Ask directly, and ask to see the clause. A company that hesitates is planning to keep you. See our guide on source code ownership.
What happens after launch?
Ask what support costs, what the response time is, and whether the answer is written into the agreement. Software that nobody maintains stops working within a year.
Can you see real work and talk to a real client?
A case study should name a problem and what was built. Ask if you can speak to the client. One honest conversation beats a page of logos.
Do they say no?
The best sign of all is a company that tells you something you asked for is unnecessary, or that ready-made software would do the job. A supplier that agrees with everything is selling, not advising.
If you would like to put us through these questions, get in touch. A senior engineer replies within one working day.
Questions people ask
Does the company need to be in my city or country?
No. Most software work runs remotely over calls and screen sharing. What matters is a clear process, overlapping working hours, and a written agreement.
Are bigger companies safer?
Not necessarily. Size brings process but also distance from the people doing the work. Judge the process and the people you will deal with.
Should I run a paid trial?
A small paid first piece of work, such as the written scope and clickable design, is a low-risk way to see how a company works before committing to the build.
Related pages
Pages people read alongside this one.
The service this guide is about
More guides
Custom software or ready-made: which to buy?
Buy ready-made software when it does most of what you need and your process can bend to fit it. Build custom software when your process is the advantage, when several tools no longer talk to each other, or when subscription costs and workarounds are eating the savings.
Fixed price or pay by the hour: which is better?
Choose a fixed price when the scope is clear and written down. Choose paying by the hour when the work is genuinely uncertain and you can watch it closely. Most business projects do best with a fixed price per part, which gives you a firm number for what is known and a clear process for what changes.
Who owns the source code in a software contract?
Unless the contract says otherwise, the company that writes the code usually keeps the copyright. Your contract should assign the code, designs and documents to you once the project is paid for, and should list any open-source or paid parts that keep their own licences.