# Role Vendor And Partnerships

> Use when evaluating a vendor, SaaS purchase, data processor, strategic partnership, or M&A target. Scores business fit, security, legal, financial exposure, and exit risk before recommending approve, pilot, renegotiate, or reject.

- Skill: `oyi77/role-vendor-and-partnerships` (Agent Skill)
- Install (CLI): `npx get-skill add oyi77/role-vendor-and-partnerships`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oyi77/role-vendor-and-partnerships/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: oyi77 (https://skillmd.com/u/oyi77)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oyi77/role-vendor-and-partnerships

---


# Role: Vendor & Partnerships

## When to Use

- When evaluating a new vendor, SaaS tool, or procurement purchase
- When assessing a data processor or third-party integration
- When exploring a strategic partnership or alliance
- When screening an M&A target or acquisition opportunity
- When reviewing contract terms, SLAs, or exit clauses

## Deterministic Dispatch Matrix

| Review Area | Delegated Role | Output |
|---|---|---|
| Financial valuation / ROI | `financial/role-financial-analyst` | TCO, ROI, scenario model |
| Security / data processing | `cybersecurity/role-security-engineer` | Threat assessment, data-flow review |
| Technical integration | `corporate/cto` → `development/role-system-architect` | Integration plan, lock-in risks |
| Legal/compliance terms | `corporate/legal-counsel` | Contract redlines, compliance gaps |
| Final approval | `corporate/ceo` (owner approval for Type 2) | Signed decision |

## Workflow

1. Classify: commodity vendor, strategic partner, data processor, or acquisition target.
2. Record business objective, alternatives, and measurable success criteria.
3. Run parallel reviews via dispatch matrix.
4. Score fit, TCO, security, legal, integration, exit reversibility, and strategic benefit.
5. Recommend approve, time-boxed pilot, renegotiate, or reject.
6. Type 2 agreements (material spend, data access, lock-in, M&A) require owner approval per `DECISION.md` §2.
7. Record renewal, exit date, and relationship owner.
8. Log the decision (with rollback plan) in `logs/decisions/YYYY-MM-DD.md` per `DECISION.md` §4 — all Type 2 decisions MUST be logged before execution.

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "The demo looked good" | Demos omit failure modes, egress costs, and contract limits. |
| "We can cancel anytime" | Export, migration, and termination clauses determine real reversibility. |
| "Legal can review after signature" | Signed terms are already binding; review before signature. |
| "Partnership is free growth" | Coordination cost and dependency risk are real costs. |

## Verification Checklist

- [ ] Alternatives and measurable success criteria listed
- [ ] Financial, security, technical, and legal reviews completed
- [ ] TCO includes exit/migration/data-egress cost
- [ ] Data processing and retention terms reviewed
- [ ] Approval authority verified; owner approval for Type 2
- [ ] Renewal/exit date and relationship owner recorded
- [ ] Decision logged in `logs/decisions/YYYY-MM-DD.md` per DECISION.md §4 (Type 2 mandatory)
