عربي
DAY 06 · CAPITAL + VENDORS

Interrogate the evidence, not the price tag

AI can organize a diligence pack and expose open questions. It cannot validate a contract, certify security, establish comparable pricing, or make an investment decision.

SELF-PACEDDILIGENCE ROOMREVIEWED 31 AUG 2026

This lesson is educational and is not financial, investment, tax, procurement, security, or legal advice. Use verified, authorized documents in an approved environment. Do not upload confidential proposals, contracts, pricing, bank data, credentials, or personal information unless the organization has approved the service, purpose, rights, lawful basis, retention, and access.

Any production implementation additionally requires approved redacted inputs; fact, inference, and proposal labels; rights and lawful basis; data minimization; least privilege; tenant separation; managed secrets; audit logs; representative, adversarial, and regression evaluations; proposal-only behavior; human approval; monitoring; a stop condition; an incident path; and tested rollback.

Create a verified diligence room

1Requirement: problem, users, baseline, constraints, alternatives, and “do nothing” scenario.
2Evidence: signed proposal version, contract draft, price schedule, architecture, security pack, references, and dated assumptions.
3Economics: finance-owned scenarios for implementation, integration, usage, support, change, downtime, exit, and uncertainty.
4Control: privacy, security, legal, procurement, finance, operations, and accessibility reviews.
5Test: bounded pilot with success measures, human acceptance, stop conditions, data return or deletion, and rollback.

Questions the model cannot answer for you

A fictional vendor proposes a forecasting service. The draft says “enterprise security” and promises savings but supplies no control mapping or baseline. The AI draft labels both as vendor claims, not facts. Security requests evidence; finance models downside and exit costs; operations defines a shadow test. The recommendation remains “insufficient evidence” until named reviewers close the critical gaps.

A source-bound review prompt

Act as a document organizer, not a lawyer, financial adviser, security assessor, or decision-maker. Decision requirement: [approved summary] Document register: [IDs, owners, dates, versions] Return: VERIFIED TERMS — exact source ID and section for each claim. VENDOR CLAIMS — claims not independently substantiated. CONFLICTS AND GAPS — missing, inconsistent, stale, or ambiguous information. SCENARIOS — formulas and assumptions supplied by finance; do not invent rates, savings, or probabilities. REVIEW QUEUE — questions routed to legal, finance, security, privacy, procurement, accessibility, and operations. PILOT PROPOSAL — limited scope, synthetic or approved data, acceptance criteria, human approval, monitoring, stop, incident, exit, and rollback. Do not recommend signing, purchasing, investing, terminating, or transferring funds.

Security and exit diligence

Decision gate

Use the NIST AI Risk Management Framework for risk structure and OWASP’s LLM application guidance for threat discovery. Qualified reviewers must map these to your actual system, contracts, and applicable requirements.

← Day 5: PeopleDay 7: Technology oversight →