
Procurement Optimizer
Cut software and services spend through seat-utilisation analysis, redundant-tool...
Install
npx skills add borghei/Claude-Skills --skill procurement-optimizer -g -a claude-code -y- Repository
- borghei/Claude-Skills1k
- Category
- Engineering
- Updated
- 12d ago
- License
- MIT + Commons Clause
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Cut software and services spend through seat-utilisation analysis, redundant-tool detection, and renewal-timing leverage. Use when auditing SaaS spend, preparing a renewal negotiation, or hunting a budget-reduction target.
Procurement Optimizer
Most software spend reduction is not a negotiation problem. It is a measurement problem: organisations buy seats in round numbers, assign them generously, and never look at whether anyone logs in. The typical mid-size portfolio carries 20-30% reclaimable seat spend before anyone talks to a vendor, and the reclaim requires no concession from the vendor at all.
This skill works the levers in order of yield: stop paying for unused seats, then stop paying twice for the same capability, then negotiate price. Reversing that order, leading with a price negotiation on a bloated contract, is how organisations congratulate themselves on a 10% discount against 40% more seats than they need.
When to use this skill
- A budget-reduction target has landed and software spend is in scope
- A renewal is approaching and you need a defensible position before the vendor call
- SaaS sprawl audit: nobody can say how many tools the company pays for
- Post-merger consolidation where two portfolios overlap heavily
- Building a renewal calendar so contracts stop auto-renewing unexamined
- A vendor has proposed an uplift and you need leverage to counter it
Inputs the skill expects
- Spend inventory: tool, category, annual cost, renewal date, contract term
- Seat data: purchased, assigned, and, critically, active in the last 30 days
- Contract terms: notice period, auto-renew flag, term length
- Criticality per tool, and whether a capability alternative exists
- Headcount, for per-head benchmarking
- The as-of date, so renewal-window maths is reproducible
Clarify First
Before generating, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
