Skip to content

borghei/Claude-Skills / business-operations/vendor-management

vendor-management

Verified

Vendor lifecycle — weighted selection scorecards, risk tiering, renewal and notice-deadline tracking, spend concentration, and SLA credits. Use when selecting a vendor, preparing a renewal, or reviewing a vendor portfolio.

assets/vendor-review-template.md

View on GitHub
# Vendor Business Review — [Vendor] — [Period]

**Internal owner:** [name] · **Risk tier:** [1-4] · **Annual spend:** [amount]
**Renewal date:** [date] · **Notice deadline:** [date] · **Auto-renew:** yes/no

> The notice deadline, not the renewal date, is the date that constrains us.

---

## 1. Position summary

| | |
|---|---|
| Relationship status | Healthy / Watch / At risk |
| SLA compliance this period | [X]% of metrics met |
| Credits owed | [amount] — claimed / unclaimed |
| Usage vs entitlement | [X] of [Y] seats ([Z]% utilised) |
| Renewal posture | Renew as-is / Renegotiate / Consolidate / Exit |

**One-line summary:** [e.g. "Response times have degraded three quarters running;
raise at this review with the series and a termination-on-repeat-breach ask at
renewal."]

---

## 2. SLA performance

Generated by `sla_report.py`.

| Metric | Target | Actual | Severity | Credit | Trend |
|--------|--------|--------|----------|--------|-------|
| | | | | | |

**Credits:** earned [X]% / cap [Y]% / applied [Z]% = [amount]
**Claimed:** yes/no — [unclaimed credits are the norm; diarise the claim]

**Trend commentary:** [three declining periods is a pattern, not an incident —
show the full series]

---

## 3. Commercial

| | This period | Prior period | Change |
|---|------------|--------------|--------|
| Spend | | | |
| Seats entitled | | | |
| Seats used | | | |
| Cost per active seat | | | |

**Reclaimable:** [unused seats x unit price] — must be actioned **before** the
vendor issues a renewal quote anchored on current entitlement.

---

## 4. Risk review

| Check | Status | Last verified | Next due |
|-------|--------|---------------|----------|
| Security certification current (SOC 2 / ISO 27001) | | | |
| Exceptions section reviewed, not just the opinion | | | |
| Subprocessor list current | | | |
| Exit plan documented | | | |
| Exit plan **tested** (data exported and opened) | | | |
| Continuity / DR evidence | | | |
| Financial viability signals | | | |

**Distress signals observed:** [senior departures, support decline, roadmap
slippage, aggressive prepay offers, ownership change — two or more triggers an
exit-plan review]

---

## 5. Open issues

| # | Issue | Raised | Vendor commitment | Due | Status |
|---|-------|--------|-------------------|-----|--------|
| 1 | | | | | |

---

## 6. Renewal plan

**Decision:** [renew / renegotiate / consolidate / exit] · **Decided by:** [date]

| Milestone | Date | Owner | Status |
|-----------|------|-------|--------|
| Usage review complete | R-180 | | |
| Alternative evaluated (if renegotiating) | R-150 | | |
| First vendor conversation | R-120 | | |
| **Notice served** | R-90 | | |
| Terms negotiated | R-60 | | |
| Signed | R-30 | | |

**Our leverage:** [real alternative / vendor fiscal timing / multi-year /
reference value / consolidation]

**Asks beyond price:** [annual increase cap, seat true-down, termination on
repeat SLA breach, data export format, subprocessor notice]

**Walk-away point:** [the number or term at which we exit, decided before the
conversation]

---

## 7. Actions

| Action | Owner | Due |
|--------|-------|-----|
| | | |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall