How to choose a software development partner: 10 questions to ask

Choosing who builds your software is one of the biggest decisions in a project. A good partner saves you time and money. A poor one costs both, and you may only find out months later.

The ten questions below help you compare companies on equal terms. Ask every company the same questions, and ask for the answers in writing. You do not need to be technical. You only need to listen for clear, specific answers. If an answer is vague, ask again. If it stays vague, treat that as an answer.

1. Who will actually do the work?

The people who sell a project are often not the people who build it. Ask who will write the code, how experienced they are, and whether you can meet them before you sign. Ask who you will speak to every week.

2. Will I get a written proposal before any work starts?

A proper proposal says what will be built (the scope), how long it will take (the timeline) and what it will cost (the quote). Ask whether you pay anything before you agree to it. Be careful with a company that wants payment before it can say what it will deliver.

3. Who owns the code, the accounts and the documents?

This is the question people forget. Ask in plain words: when the project ends, will the source code, the cloud and domain accounts, and the documentation belong to me? Get the answer in the contract. If the company keeps them, moving to another team later means starting again.

4. How will I see progress?

'Trust us' is not a progress report. Ask for regular demos of working software, not slides, and a short written update every week. Seeing the real product early is the best way to catch a misunderstanding while it is still cheap to fix.

5. How do you check quality?

Ask what happens before software reaches your users. Good answers include automated tests (small programs that check the software still works after each change), a person reviewing the work, and monitoring after launch (alerts that tell the team when something breaks). Ask who is responsible if a bug reaches your customers.

6. What happens after launch?

Software needs care after it goes live. Ask what support is included, how long bug fixes are free, and what ongoing support costs. Get the free period in writing. Ask how quickly the team replies when something breaks.

7. How will you protect our data?

Ask where your data is stored, who can see it, and whether the company will sign a non-disclosure agreement (NDA) if you ask. If you handle customer details, ask which data protection law the company works to and which country your data will be stored in. Examples are India's Digital Personal Data Protection (DPDP) Act and the GDPR in the European Union. A good company answers in plain words.

8. What could change the price?

Most projects change as they go. Ask how a change is handled: is it written down, priced and agreed before work on it starts? Ask what the quote leaves out, such as hosting, paid tools or app store fees. A fixed price with a long list of extras is not fixed.

9. How would we part ways?

Even good partnerships end. Ask what the handover looks like: will you get everything, and will the team explain it to whoever comes next? A confident company answers this easily, because it plans for a clean handover from the start.

10. Can I speak to someone who has worked with you?

Ask for references you can call and for examples of similar work. Ask what went wrong on a past project and how the company dealt with it. Every project has problems, and how a company handled them tells you more than a perfect record. A company that says nothing ever goes wrong is not being straight with you.

Warning signs

• It cannot say who will do the work.

• It wants payment before it has written down the scope.

• It will not put ownership of the code in writing.

• It talks only about price, never about scope or quality.

• It promises a date and a price before it understands your requirement.

What to do next

Here is how that looks at Supervention. Senior engineers do the work. You get a written proposal with scope, timeline and quote before any work starts, at no cost until you agree. You get a demo and a written update every week. You own the code, the accounts and the documentation. We include 30 days of free fixes, sign an NDA on request, and follow India's data protection law (DPDP). If other rules apply to you, we set out in writing what we do for each. Every system has monitoring, tests and human checks. To compare us with this list, send us your requirement.

Sources: Digital Personal Data Protection Act, 2023, Ministry of Electronics and Information Technology (meity.gov.in). Regulation (EU) 2016/679, the General Data Protection Regulation (eur-lex.europa.eu).