Five Questions to Ask Before Approving a Technology Vendor

A technology vendor often receives something valuable before the first invoice is paid: access to your data, your systems or your customers. Yet approval decisions are frequently made on the strength of a sales demonstration and a completed questionnaire. The five questions below help procurement, finance and IT leads decide together, and they work for a small software subscription as well as for a large managed service.
Start with what the vendor will actually touch
Before asking anything about the vendor, define the exposure. List the data it will hold, the systems it will connect to, and the staff or customers who will rely on it. A vendor that only receives a public marketing list is a different decision from one that connects to your finance system. Writing this down in a few lines gives every later answer something to be measured against, and it helps decide how much scrutiny the vendor deserves.
The five questions
- What data will you hold, where will it be stored, and who can access it? Look for specific answers: locations, roles, and how access is granted and removed, rather than general assurances.
- How do you show that your controls work? Ask for evidence you can read, such as an independent report, a recent test summary or a described process, and ask what it covers and what it leaves out.
- What happens when something goes wrong? Ask how and how quickly you would be told about an incident, who you would hear from, and what you would be expected to do.
- Which other companies do you depend on? Your vendor's suppliers become part of your exposure. Ask which ones handle your data and how the vendor reviews them.
- How do we leave? Ask how your data is returned or deleted at the end of the contract, in what format, and how deletion is confirmed.
Reading the answers
Good answers are specific, consistent and easy to verify. Be cautious when answers are vague, when different people at the vendor say different things, or when a request for evidence is met with a promise to follow up that never arrives. A questionnaire marked yes in every box proves little; the useful part is what the vendor can show behind each yes. Where something cannot be shown, decide whether the gap can be closed by a contract term, a technical limit on access or a smaller scope, or whether it is a reason to pause.
A hypothetical example
Hypothetical, for illustration only. Suppose a logistics company is choosing between two scheduling tools. Both claim strong security. When asked the fifth question, one vendor describes a documented export and deletion process; the other says data can be requested by email with no stated timeframe. The product features are similar, so that difference, not the demonstration, becomes the deciding factor, or a contract term to negotiate before signature.
Make the approval a record
Whatever the decision, write down what was asked, what was answered and who accepted any remaining risk. A short record helps at renewal, helps new colleagues understand why a vendor was chosen, and gives an auditor or customer something to review. Assign an owner for the relationship and a date to revisit it, because vendors change over time.
Next step
If you would like help reviewing a vendor before you sign, read about our vendor due diligence service, then request a consultation to discuss the supplier you are considering.