Build the evidence pack before a buyer asks for it. Learn the buyer's review process at discovery, and send the pack during the pilot. Name one owner for open items on each side. Stage 6 then starts with answers on file and only the buyer's own questions left.

Why does due diligence stall deals?

The reviewers arrive late on the seller's calendar and early on the buyer's. Procurement professionals are decision-makers in 53% of business buying cycles, and they engage from the start (Forrester, January 2026).

A seller who first meets them at stage 6 of the enterprise B2B sales cycle has a contract that waits on missing documents.

For regulated buyers, the review is a legal duty, so a champion cannot waive it. Three rules shape the questions as of 8 November 2026:

  • EU financial entities. DORA applies from 17 January 2025. Article 28(4) requires due diligence on an ICT provider before the contract. Article 28(3) requires a register of all ICT contracts (EUR-Lex).
  • EU essential and important entities. NIS2 Article 21 lists supply chain security as a minimum measure. Entities must consider the security practices of each direct supplier (EUR-Lex).
  • US banks. The 2023 interagency guidance sets a life cycle from planning to termination (FDIC, June 2023). A September 2026 proposal would replace it, with comments due 16 November 2026 (Federal Register).

The 2023 text is still the standard. One law firm expects no final version before 2027 (Crowell & Moring, September 2026).

What goes in the evidence pack?

Eight items cover most first requests. Keep them in one folder, under one NDA, with a date on each.

Security evidence, owned by the CTO or the security lead:

  1. A SOC 2 report, or a dated plan to get one.
  2. A completed standard questionnaire (CAIQ).
  3. The latest penetration test summary.
  4. The incident response and business continuity plans.

Data and company documents:

  1. A data flow and data location page.
  2. A subprocessor list with locations.
  3. Your standard data processing agreement, so legal starts from your paper.
  4. A company file: registration, insurance, ownership and any licences.

Write the data flow page once, during technical scoping, and use it again. Under GDPR Article 28, a controller needs sufficient guarantees, a contract and authorisation for any further processor. A privacy reviewer asks for those three first.

Do you need a SOC 2 report before your first enterprise deal?

Some buyers insist on one, so ask at discovery. A Type 1 report tests the design of controls at one point in time. A Type 2 report also tests whether the controls operated over a period.

The AICPA sets no minimum period, and the shortest period in practice is three months. One audit firm gives this timeline (Cherry Bekaert, June 2025):

  1. Readiness work: 1 to 2 months.
  2. Remediation: 1 to 6 months.
  3. Type 2 testing: 3 to 12 months.
  4. Report issue: about 1 month.

The report can cover five categories, from Security to Privacy (AICPA & CIMA). Start with Security. Add a category when a named buyer needs it.

If you have no report, offer a bridge. Complete the Cloud Security Alliance CAIQ v4.1, released on 27 January 2026 (CSA). Submit it as a Level 1 self-assessment to the public STAR Registry. Add a dated letter from your auditor if the audit has started.

Will a certificate replace the buyer's questionnaire?

Sometimes, and more often for lower-risk services. Ask each reviewer if they accept a report and a CAIQ in place of their own form.

The US proposal says certifications may be adequate for a bank's due diligence, depending on the facts (Federal Register, September 2026). A certification does not transfer the bank's accountability. Banks still check its scope, currency and gaps (Skadden, September 2026).

Keep every answer in one library, with the source document and the date. Start the next questionnaire from that library.

What is the procedure?

  1. Discovery. Ask what the last vendor supplied, who reviewed it and what held it up. The MEDDPICC discovery call covers this under Paper Process.
  2. Scoping. Record the data flow, locations and subprocessors in the scope document.
  3. Pilot. Send the pack when the sandbox work starts. Use test data until the review is complete.
  4. MOU. Name the reviewers and put target dates in the MOU or LOI. Ask for the contract template.
  5. Review. Keep one shared list of open items, each with an owner and a date. Check it twice a week.

What do regulated buyers add at the contract?

EU financial buyers first decide if your service supports a critical or important function. Ask them early. DORA Article 30(2) lists terms for every ICT contract, such as data locations, service levels and termination rights.

Article 30(3) adds terms for critical or important functions (EUR-Lex):

  • measurable performance targets
  • audit and access rights
  • participation in threat-led penetration testing
  • a mandatory transition period on exit

Draft a DORA addendum before an EU bank or insurer asks for one. Compliance software buyers have their own chain, set out in who signs off on a KYC or AML vendor.

To find buyers worth this pack, get five named buyers, free.