Partner due diligence basics

FrameworkDecision-makingTransparency

What “due diligence” means here

This is a practical, plain-language framework for evaluating a potential partner or provider. It’s not a legal process — it’s a way to reduce surprises by validating key claims and documenting assumptions.

The 5-question framework

  • 1) What is the claim? Write down exactly what is being promised.
  • 2) What would prove it? Identify evidence (documents, demos, references, track record).
  • 3) What could go wrong? List failure modes (delivery delays, quality issues, cost creep).
  • 4) What would we do if it goes wrong? Define exits, mitigation, and fallbacks.
  • 5) Who owns what? Clarify responsibilities, inputs, timelines, and escalation paths.

Practical validation steps

  • Ask for references that match your situation (industry, size, scope).
  • Request a written scope with deliverables and exclusions.
  • Confirm security contacts if any data or accounts are involved.
  • Test the support channel (how fast do you get a human response?).
Keep it simple: you’re not trying to “win an argument,” you’re trying to avoid hidden assumptions.

Decision memo (one page)

Before committing, write a short memo:

  • Context: what problem are we solving?
  • Options: who did we compare?
  • Trade-offs: what are we accepting?
  • Risks & mitigations: top 3 risks and the plan
  • Exit plan: how we unwind if needed

Red flags (quick list)

  • Refusal to put key terms in writing
  • Pressure to decide “today” without a clear reason
  • Unclear ownership of data, access, or deliverables
  • Promises that can’t be verified

Have a correction or suggestion? Email support@oppartnersusa.com.