Software vendor due diligence is a short, structured set of checks you complete before signing: confirm the vendor can show real evidence of their work, handles security and data responsibly, will still be around to support you, and gives you a clean way out. Use the checklist below, score each area and decide with the evidence in front of you.
What software vendor due diligence should answer
Four questions sit behind every check:
- Can they actually do this kind of work?
- Will they protect your data and your systems?
- Will they still be there, and can you cope if they are not?
- If it goes wrong, can you leave with your code and data?
Match the effort to the stakes. A small brochure site warrants a quick pass; a system holding customer data or running daily operations deserves every section. Write down who on your side is responsible for each check, and keep the answers in a single document so you can compare vendors side by side. If you are still choosing between options, our guide on vetting an outsourced development partner covers the earlier selection stage.
References and evidence of work
How do I check references properly?
Ask for two or three references on projects similar to yours in size and type, and call them rather than relying on written praise. Useful questions: Did the work arrive roughly when agreed? How were surprises and disagreements handled? Who exactly did the work? How was support after launch? Would you hire them again, and what would you do differently?
- Ask to see live work and click through it yourself.
- Ask for a short walkthrough of how a past project was planned and delivered.
- Check that the people you met are the people who will work on your project.
- Treat refusal to provide any reference as information.
Be wary of portfolios that cannot be verified. Evidence you can inspect beats claims.
Security practices
What should a vendor security questionnaire cover?
Keep it proportionate and ask for specifics. Core topics:
- Access control: who can reach your code, servers and data; use of individual accounts and multi-factor authentication; how access is removed when people leave.
- Secure development: code review, dependency updates, secret handling and how common web risks such as those in the OWASP lists are addressed.
- Environments: separation of development, staging and production, and whether real customer data is used for testing.
- Backups and recovery: how often, where stored, and whether restores have been tested.
- Incident handling: how they detect problems, and how and how quickly they would notify you.
- Staff: confidentiality agreements and how security expectations are communicated.
Prefer concrete answers over generic assurances. If your sector has compliance requirements, ask a qualified adviser which ones apply, as rules change. For deeper technical reading, see our web application security checklist.
Continuity and key-person risk
A vendor can be competent and still be a risk if everything depends on one person. Ask how many people could take over your project, how knowledge is shared and documented, and what happens if the lead developer leaves or is unavailable. For a small vendor, a good answer is not a large headcount but a clear practice: written documentation, version control you can access, and a described handover process.
On stability, ask how long they have been operating, how they handle work for several clients at once, and whether there are signs of strain such as slow replies. Do not expect detailed financials from a small firm, but a reasonable discussion about capacity and workload is fair. Our piece on documentation and handover explains what a healthy handover looks like.
Contract terms to read twice
Read the contract in full, and have a lawyer review it, since specifics vary by jurisdiction. These are the clauses to find and understand:
- Ownership: who owns the code, designs and data on payment, and what third-party or open-source components are included.
- Scope and acceptance: how deliverables are defined and accepted, and how changes are handled.
- Payment terms: what triggers each payment, and what happens to unfinished work.
- Warranty and support: what is fixed free after launch and for how long.
- Liability and indemnity: limits and exclusions, and whether they seem reasonable for the risk.
- Termination and exit: notice periods, handover of code, credentials and documentation, and cooperation on transition.
- Confidentiality: what each side must protect.
What are contract red flags?
Watch for code ownership that stays with the vendor without a clear licence, no right to access the repository, payment of everything upfront with no acceptance step, automatic renewals that are hard to cancel, vague scope with open-ended fees, and no exit or handover terms. Our overview of fixed-price and time-and-materials contracts explains the commercial structures you may meet.
Data handling and subcontractors
Find out where your data will live, who can see it and whether any of the work is passed to subcontractors or other companies. Ask for a list of the main third-party services involved, such as hosting and monitoring, and what they receive. If you handle personal data, check that there is a written agreement covering how it is processed, and ask a qualified adviser which data protection rules apply to you. Also confirm that you will be able to export your data in a usable form and that it is deleted when you request it.
Scoring and decision
Score each area from one to five using the evidence gathered, and mark any item that would be a deal-breaker for you.
| Area | What good looks like | Score |
|---|---|---|
| References | Verified, similar work, candid feedback | 1 to 5 |
| Security | Specific practices, tested backups | 1 to 5 |
| Continuity | More than one person knows your system | 1 to 5 |
| Contract | Clear ownership, acceptance and exit terms | 1 to 5 |
| Data and subcontractors | Known locations, written agreements | 1 to 5 |
A low score is not always a reason to walk away; it may be a list of items to fix in the contract. A deal-breaker left unresolved is.
Next step
Turn this list into a one-page worksheet, send the security and contract questions to each shortlisted vendor in writing, and compare their answers. You can see how we work on our US software development page and are happy to answer a questionnaire through our contact form.
Frequently asked questions
What should a vendor security questionnaire cover?
Cover access control and multi-factor authentication, secure development practices, separation of environments, backups and tested restores, incident response and notification, and staff confidentiality. Ask for specific practices rather than generic assurances, and keep the length proportionate to what the vendor will access. Check any regulatory obligations with a qualified adviser.
How do I check references properly?
Choose references from similar projects and speak to them directly. Ask about timeliness, how problems were handled, who did the work, post-launch support and whether they would hire the vendor again. Also inspect live work yourself and confirm the people you met will work on your project.
What are contract red flags?
Vendor-held code ownership without a licence, no repository access, full upfront payment without acceptance steps, hard-to-cancel automatic renewals, vague scope with open-ended fees, and missing exit or handover terms. Have a lawyer review the contract, since terms and legal effects vary by jurisdiction.