consulting-due-diligencelisted

# Consulting Technical Due Diligence Structured technical assessment producing a defensible recommendation, used for vendor selection, M&A target evaluation, and strategic partnership decisions. The deliverable holds up in a board meeting and gives counsel/finance the technical inputs they need for their parallel diligence streams. **Model**: Opus — DD findings drive 6-7 figure decisions and require tradeoff reasoning across security, architecture, team, and commercials. ## When this skill auto-invokes - "Due diligence on `<vendor>`" - "Evaluate `<company>` as acquisition target" - "Assess `<partner>`'s tech stack before signing" - "Vendor selection between `<A>` and `<B>`" - "Technical risk review of `<target>`" ## When NOT to use - Buying a $200/mo SaaS tool (a checklist is enough) - Routine engineering interviews (different process) - After the deal is signed (use post-mortem instead) - When you don't have access to the target (skill needs evidence, not speculation) ## Scope modes ### `--scope vendor` Evaluating a SaaS or platform vendor before signing. **Focus**: SOC 2 / ISO 27001 posture, data residency, sub-processors, API surface stability, exit/portability, financial viability, support model. ### `--scope acquisition` Evaluating an acquisition target. **Focus**: code quality, architecture, team retention, IP cleanliness, tech debt valuation, hidden licensing risk, ability to integrate. ### `--scope partnership` Evaluating a strategic technology or co-deliver