borghei/Claude-Skills / business-operations/vendor-management
vendor-management
VerifiedVendor 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.7 KB |
| assets/sample_portfolio.json | config | 3.6 KB |
| assets/sample_sla.json | config | 2.2 KB |
| assets/sample_vendor_candidates.json | config | 2.7 KB |
| assets/vendor-review-template.md | markdown | 3.1 KB |
| assets/vendor-selection-scorecard.md | markdown | 2.9 KB |
| references/renewal-negotiation-leverage.md | markdown | 10.1 KB |
| references/vendor-risk-tiering.md | markdown | 8.6 KB |
| scripts/portfolio_analyzer.py | script | 11.2 KB |
| scripts/sla_report.py | script | 10.5 KB |
| scripts/vendor_scorecard.py | script | 10.4 KB |
assets/vendor-selection-scorecard.md
View on GitHub# Vendor Selection Scorecard — [Decision]
**Decision owner:** [name] · **Date:** [date] · **Budget:** [amount/year]
**Decision deadline:** [date] · **Current solution:** [incumbent or none]
> Weights were agreed on [date] by [who], **before** any vendor was scored.
---
## 1. Must-haves (pass/fail)
A candidate failing any of these is disqualified regardless of score. Keep this
list short — every entry is a candidate eliminated, so anything that is merely
strongly preferred belongs in the weighted criteria instead.
| Must-have | Why it is non-negotiable | Vendor A | Vendor B | Vendor C |
|-----------|-------------------------|----------|----------|----------|
| | | pass/fail | | |
| | | | | |
---
## 2. Weighted criteria
Weights must be set before scoring and must sum to 100.
| Criterion | Weight | What a 10 looks like | What a 5 looks like |
|-----------|--------|---------------------|---------------------|
| Functional fit | | | |
| Security + compliance | | | |
| Integration effort | | | |
| Support quality | | | |
| Roadmap + viability | | | |
| Exit cost | | | |
Defining the anchors ("what a 10 looks like") before scoring is what stops the
scorecard becoming a justification for a decision already made.
---
## 3. Scores
| Criterion | Weight | Vendor A | Vendor B | Vendor C | Evidence |
|-----------|--------|----------|----------|----------|----------|
| | | | | | [demo, reference call, doc reviewed] |
| **Weighted total** | 100 | | | | |
| **Annual cost** | | | | | |
| **Value (score/100k)** | | | | | |
---
## 4. Stability check
Generated by `vendor_scorecard.py`.
- **Margin to runner-up:** [X]% — under 5% is a tie, decide on other grounds
- **Weight-sensitive:** yes/no — [which criteria flip the result]
- **Cost premium:** leader costs [X]x runner-up for a [Y]% score advantage
---
## 5. Risk tier of the selected vendor
| Dimension | Value | Points |
|-----------|-------|--------|
| Data classification | | |
| Business criticality | | |
| No ready alternative | | |
| Subprocessors | | |
| **Tier** | | |
**Obligations this tier triggers:** [security review cadence, exit plan, SLA
requirements, business review cadence]
---
## 6. Commercial position before negotiation
| Item | Detail |
|------|--------|
| List price | |
| Target price | |
| Walk-away point | |
| Our leverage | [real alternative / timing / multi-year / reference / volume] |
| Their fiscal year-end | |
| Terms we need beyond price | [increase cap, true-down, exit rights, SLA credits] |
---
## 7. Recommendation
**Selected:** [vendor] · **Annual cost:** [amount] · **Term:** [length]
**Rationale (3-4 sentences):** [why this one, what we traded away, what the
runner-up would have given us instead]
**Key risks and mitigations:**
| Risk | Mitigation | Owner |
|------|-----------|-------|
| | | |
**Decision record:** who approved, on what date, and what would cause us to
revisit.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |