← All skills
procurement-optimizer
Use for an annual SaaS/spend audit, category spend review, or supplier rationalization: UNSPSC categorization with Pareto breakdown, purchasing-cycle bottleneck analysis, risk-balanced consolidation.
About this skill
Use for an annual SaaS/spend audit, category spend review, or supplier rationalization: UNSPSC categorization with Pareto breakdown, purchasing-cycle bottleneck analysis, risk-balanced consolidation.
SKILL.md
procurement-optimizer.SKILL.mdPlace it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review the contents and run it in a controlled environment first.
---
name: procurement-optimizer
description: Use for an annual SaaS/spend audit, category spend review, or supplier rationalization: UNSPSC categorization with Pareto breakdown, purchasing-cycle bottleneck analysis, risk-balanced consolidation.
category: Business Operations
version: 1.0.0
tools: []
---
# Procurement Optimizer — Spend Categorization + Supplier Rationalization
Run the annual category review covering what to buy, from whom, and on what cadence — not how an already-chosen vendor is performing (that's the sibling vendor-management skill). Categorize spend along a UNSPSC-aligned taxonomy, find the Pareto 20% of categories driving 80% of cost, surface purchasing-cycle bottlenecks, and produce a risk-balanced supplier-consolidation plan that refuses to collapse tier-1 categories to single-source without a documented contingency.
## Purpose
Typical mid-stage pattern: software spend up 40% YoY with no owner who can name the top growth categories; 3 monitoring tools, 2 expense platforms, 4 email-marketing tools sitting as unconsolidated duplicate-function clusters; a purchasing cycle where some categories close in 5 days and others take 90 while the "average" hides the real constraint; renewal dates clustered in the same month, destroying leverage. Produce a deterministic output for each: categorized spend with Pareto, a cycle-time scorecard by category, and a consolidation plan with explicit risk flags.
## When to use
Annual SaaS audit / category-level spend review; a category owner needs the top 5 categories driving this year's growth; Finance flags spend up 40% YoY and wants a Pareto by category, not by vendor; BizOps suspects duplicate-function tools and needs a defensible consolidation case; the CFO wants tighter approval thresholds backed by cycle-time data; post-acquisition merging of two category taxonomies and supplier bases.
## When NOT to use
Scoring an individual vendor already being paid → vendor-management. Financial close/P&L → financial-analysis. Contract drafting/negotiation → general-counsel-advisor. Outbound sales proposals → contract-and-proposal-writer.
## Workflow
### Step 1 — Intake spend
Collect line items with {supplier, description, category_hint, annual_spend, frequency, currency}; prior-year spend, if available, enables YoY analysis.
### Step 2 — Categorize and find the Pareto
Map each line item to a UNSPSC-aligned Class → Family → Segment (roughly 30 categories tuned for tech-startup spend: Software/SaaS, Hardware, Cloud Infrastructure, Professional Services, Marketing Services, Legal, Recruiting, Travel, Office, Insurance, Benefits, etc. — not the full 100k-entry UNSPSC database). Categorize by what was purchased (description + category_hint), never by supplier name — one supplier can span multiple categories. Compute the Pareto: which 20% of categories drive 80% of spend? Rank the top-10 YoY growth categories when prior-year data exists. Reweight priorities by profile: tech-startup (SaaS/cloud-heavy), scaleup (sales tools/recruiting-heavy), enterprise (professional services/facilities-heavy), services, manufacturing.
### Step 3 — Analyze the purchasing cycle
For each PO record {category, request_date, approval_date, po_issued_date, goods_received_date, payment_date, approver_hops}, compute per-category cycle time request→PO (median, P90), PO→payment (median, P90), and median approver-hop count. Flag any category whose cycle time exceeds 2× the cross-category median as a bottleneck — Goldratt's Theory of Constraints applied to procurement: throughput is set by the slowest step, almost always one specific category (legal review on services contracts, security review on tier-1 SaaS).
### Step 4 — Plan supplier consolidation with risk balancing
Identify duplicate-function clusters (e.g., 3 monitoring tools, 2 expense platforms). Pick a consolidation winner per cluster (highest criticality tier survives, or lowest-switching-cost winner for tier-3 clusters). Never recommend collapsing a tier-1 category to single-source without a documented break-glass plan — otherwise state "DO NOT CONSOLIDATE — tier-1 cluster, no break-glass on record. Add a 72-hour contingency plan first." Estimate savings as current cluster spend minus winner spend minus migration cost (sum of losers' switching costs). Flag renewal-date clustering: 3+ contracts renewing in the same calendar month means zero leverage.
### Step 5 — Synthesize the review
One digest: top 5 categories driving YoY growth, top 3 bottleneck categories, top 5 consolidation opportunities with savings and risk flags, all renewal clusters destroying leverage, all tier-1 single-source exposure points needing break-glass plans.
## Canon
A.T. Kearney Spend Management, Procurement Leaders, Gartner Procurement, BCG Procurement value creation, Hackett benchmarks, Pierre Mitchell/Spend Matters, official UNSPSC taxonomy (categorization); Productiv/Zylo/Vendr/Tropic SaaS sprawl reports, BetterCloud SaaS Operations, Gartner SMP Magic Quadrant, Bain SaaS spend, Forrester SaaS portfolio management, Tomasz Tunguz, Patrick Campbell/ProfitWell (SaaS patterns); A.T. Kearney maverick-spend research, IACCM/WorldCC, McKinsey category-strategy research, Hackett purchasing-cycle research, BCG supplier-consolidation risk research, Spend Matters failed-rationalization analyses, ISM lessons (anti-patterns).
## Assumptions
1. AP/expense/SaaS-management exports exist, or the user can hand-assemble the top 100-200 line items — the Pareto holds; the top 20% of suppliers will be most of the spend.
2. Prior-year spend is preferred (for YoY) but optional.
3. Purchasing-cycle data is preferred but optional; if absent, deliver categorization + consolidation only.
4. Supplier criticality (tier-1/2/3) is the user's judgment call, not derived from spend alone. Tier-1 = revenue-blocking if the supplier disappears — never infer this, require the user to mark it.
5. Output artifacts are inputs to a human decision, not the decision itself.
## Anti-patterns
Consolidating to single-source for a tier-1 category without a break-glass plan; categorizing by vendor name instead of by what's purchased; ignoring renewal-date clustering (twelve tier-2 contracts all renewing in March = zero leverage); approving sub-$5K spend by default (the death-by-a-thousand-SaaS pattern — surface "small-spend, many-supplier" clusters explicitly); annual-only renewal review (too coarse — SaaS renews continuously); rationalizing without measuring switching cost (consolidating 3 tools to save $50K when migration costs $200K is not a savings); consolidating on price alone while ignoring integration debt; treating shadow-IT spend as marketing's problem when it's procurement's — marketing-tool sprawl is the #1 driver of SaaS-spend growth in scaleups.
## Distinct from
vendor-management scores performance (uptime, SLA, third-party risk) of vendors already being paid; this skill decides which vendors to keep. financial-analysis is financial close/P&L/DCF, not category strategy. general-counsel-advisor is contract law (indemnity, IP, liquidated damages) — GC reviews the survivor's contract terms after the consolidation winner is picked here. contract-and-proposal-writer is outbound proposals to win customers, not inbound rationalization. budgeting is annual budget planning; this skill shows where the budget is actually leaking.
## Forcing-question library
Walk one at a time, depth-first — lock questions 1-4 before opening 5-7, and never bundle them. Recommended answer + canon citation per question.
1. "Do you have a UNSPSC-aligned taxonomy, or are you categorizing by vendor name?" Recommended: categorize by what's purchased (description + category_hint) — one supplier can span multiple categories. Canon: UNSPSC taxonomy, A.T. Kearney Spend Management.
2. "Of your top 10 categories by spend, which 3 grew most YoY — and why?" Recommended: name them before opening the analysis; inability to name them is the diagnosis. Canon: BCG Procurement value-creation research, Hackett category-visibility benchmarks.
3. "For each duplicate-function cluster, what's the switching cost to consolidate — does it exceed the savings?" Recommended: estimate switching cost explicitly (training, integration rework, migration); refuse to recommend consolidation without it. Canon: BCG supplier-consolidation risk research, Spend Matters failed-rationalization analyses.
4. "For any tier-1 category proposed for single-source consolidation, what's the 72-hour break-glass plan if that supplier disappears?" Recommended: documented, tested contingency per category; if absent, do not consolidate. Canon: NotPetya/M.E.Doc supply-chain attack, NIST SP 800-161, A.T. Kearney supply-concentration research.
5. "What % of spend runs through a PO vs. expense reimbursement vs. shadow IT?" Recommended: measure it — A.T. Kearney finds 10-40% of spend is maverick in unmonitored companies. Canon: A.T. Kearney maverick-spend research, ISM procurement maturity model.
6. "How many of your top-20 contracts renew in the same calendar month?" Recommended: build a renewal calendar and spread renewals — clustering destroys leverage. Canon: IACCM/WorldCC contract-management research, Spend Matters on negotiation timing.
7. "What's your approval threshold for net-new SaaS under $5K? Who owns the death-by-a-thousand-SaaS problem?" Recommended: a tightened threshold plus a single owner — Productiv/Zylo data shows 50%+ of SaaS sprawl comes from sub-$5K unmonitored purchases. Canon: Productiv/Zylo/Vendr industry reports.
Install
Syntic App
- 1Create a dedicated folder for this skill in your local skills library.
- 2Place SKILL.md into that folder.
- 3Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1Save SKILL.md in your local Syntic Code skills directory.
- 2Keep related files in the same skill folder.
- 3Run in a safe environment and validate outputs.