Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Technology Buying Guides 6 min read

SaaS vendor due diligence checklist for buyers

A working checklist for evaluating SaaS vendors: viability, security evidence, privacy terms, data portability, service levels and exit rights.

E
EncryptTechBD · 0 comments
Business people shaking hands
Photo: Matt Moloney / StockSnap

Buying SaaS looks like a product decision. It is also a dependency decision. The vendor will hold your customer records, run part of your operations and sit inside your incident path for as long as the contract lasts. Due diligence is how you find out whether that dependency is acceptable before the renewal date, not after an outage.

This checklist is written for the buyer, not the vendor. It covers the evidence to request, the questions that expose weak answers, a scoring method, the pilot that proves the product fits, and the exit terms that keep the decision reversible.

1. Business and product viability

  • Legal entity and ownership confirmed. Owner: Procurement. Evidence: company registration, parent company and any recent change of control.
  • Revenue model understood. Owner: Procurement. Evidence: how the vendor earns, what is included and what is metered.
  • Customer references checked. Owner: Business owner. Evidence: two references of similar size and sector, with questions about support and outages.
  • Roadmap dependency assessed. Owner: Product. Evidence: the features you need that do not exist today, with dates and contractual commitments.
  • Continuity plan requested. Owner: Procurement. Evidence: escrow, source code access or a documented migration path if the vendor fails.

2. Security evidence

  • Certification scope checked. Owner: Security. Evidence: the certificate or report itself, not the logo. Confirm the scope covers the service you are buying and the locations that host your data.
  • Independent assurance reviewed. Owner: Security. Evidence: a recent SOC 2 Type II report or equivalent, including the auditor's opinion and the period covered.
  • Penetration test summary reviewed. Owner: Security. Evidence: date, scope, critical findings and remediation status, under NDA if required.
  • Incident history discussed. Owner: Security. Evidence: the last two years of material incidents, customer impact and what changed afterwards.
  • Access controls tested. Owner: IT. Evidence: SSO, multi-factor authentication, role model, admin approval and session controls in a trial tenant.
  • Encryption and key management explained. Owner: Security. Evidence: encryption in transit and at rest, key ownership and rotation.
  • Subprocessors listed. Owner: Legal. Evidence: a current list with locations, purposes and notification terms for changes.
  • Backup and recovery tested. Owner: Security. Evidence: stated RTO and RPO, backup frequency and a recent restore test.
  • Vulnerability handling described. Owner: Security. Evidence: disclosure channel, patch cadence and severity response times.

3. Privacy and data protection

  • Data processing agreement reviewed. Owner: Legal. Evidence: signed DPA with purpose limitation, retention, deletion and audit rights.
  • Data residency confirmed. Owner: Legal and IT. Evidence: the specific regions where data is stored, processed and backed up.
  • Retention and deletion defined. Owner: Legal. Evidence: retention periods, deletion method and a certificate of deletion on exit.
  • Cross-border transfer basis documented. Owner: Legal. Evidence: the mechanism used and any customer notice required.
  • Data subject request support confirmed. Owner: Legal. Evidence: how the vendor helps you answer access, correction and deletion requests.
  • Breach notification period agreed. Owner: Legal. Evidence: a contractual notice period short enough for your own regulatory deadline.

4. Data ownership and portability

  • Ownership stated in the contract. Owner: Legal. Evidence: a clause that your data remains yours, including derived data and metadata.
  • Export formats documented. Owner: IT. Evidence: CSV, JSON or API export for records, attachments and audit logs.
  • Export limits tested. Owner: IT. Evidence: a trial export of a realistic data set, including rate limits and timeouts.
  • Metadata included. Owner: IT. Evidence: timestamps, owners, history and relationships survive the export.
  • Transition assistance priced. Owner: Procurement. Evidence: exit support hours and cost written into the agreement.

5. Service levels and support

  • Uptime commitment reviewed. Owner: Procurement. Evidence: the definition of availability, exclusions and the credit mechanism.
  • Support hours and channels confirmed. Owner: Operations. Evidence: coverage in your timezone, named contacts and escalation path.
  • Maintenance windows disclosed. Owner: Operations. Evidence: notice period and whether windows count against uptime.
  • Status communication tested. Owner: Operations. Evidence: status page, incident updates and post-incident reports.

6. Commercial and legal terms

  • Pricing model modelled for three years. Owner: Finance. Evidence: cost at current and doubled usage, including storage and API overages.
  • Renewal uplift capped. Owner: Procurement. Evidence: a written cap or a fixed renewal price.
  • Termination rights clear. Owner: Legal. Evidence: notice period, termination for convenience and termination for cause.
  • Liability and indemnity reviewed. Owner: Legal. Evidence: caps, exclusions and whether they are acceptable for the data involved.
  • Audit and assurance rights preserved. Owner: Legal. Evidence: the right to receive reports and, where justified, to audit.
  • Change of control addressed. Owner: Legal. Evidence: notice and termination rights if the vendor is acquired.

7. AI features, if included

Ask whether your data is used to train models, which model providers are involved, where inference runs, how long prompts and outputs are retained, and whether a human reviews consequential outputs. Get the answer in the contract or a published addendum, not only in a sales deck.

Scoring and red flags

Score each section from 1 to 5 against your own risk appetite, and record the evidence behind the score. A simple weighted total is enough; the value is in the conversation, not the number.

  • "We are fully compliant" without a report or certificate.
  • A certificate whose scope excludes the service you are buying.
  • No named subprocessors or no notice of changes.
  • Export available "on request" with no format or timeframe.
  • Unlimited per-record pricing growth.
  • Verbal promises about roadmap or support that are not in the contract.
  • Reluctance to answer a security questionnaire in writing.

Pilot and exit

Run a time-boxed pilot with real data, real users and a defined acceptance test. Include one failure scenario: an export, a permission change or a support escalation. Then confirm the exit plan before signature: who exports what, in which format, by when, and at what cost.

Verification before signature

  1. Confirm the certificate scope and report period match the service you are buying.
  2. Complete a trial export and reload it into a test environment.
  3. Ask the vendor to walk through their last incident report and the changes made.
  4. Test SSO, MFA and role changes with your own identity provider.
  5. Get the subprocessor list, DPA and exit terms into the final contract, not an annexure marked "to follow".

Where this fits in our work

If you need a second pair of eyes on a SaaS decision, start with Custom Software and Integrations. The pricing page explains how we scope reviews. For the wider programme, read the third-party security risk guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes