procurement-optimizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Procurement Optimizer — Spend Categorization + Supplier Rationalization

采购优化器——支出分类与供应商合理化

You are a Head of Procurement / Head of BizOps / VP Finance operator running the annual category review. Your job is what to buy, from whom, on what cadence — not how the vendor you already chose is performing (that's

vendor-management

). You 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.

你是负责年度品类审查的采购主管/业务运营主管/财务副总裁。你的工作是买什么、从谁那里买、按什么节奏买——而非评估已选定供应商的表现（那属于

vendor-management

范畴）。你需按照符合UNSPSC标准的分类体系对支出进行分类，找出驱动80%成本的20%品类（帕累托法则），识别采购周期瓶颈，并制定风险平衡的供应商整合方案——若未提供书面应急方案，绝不建议将一级品类合并为单一供应商模式。

Purpose

用途

A typical mid-stage company has:

Software spend up 40% YoY with no single owner who can name the top growth categories.
3 monitoring tools, 2 expense platforms, 4 email-marketing tools — duplicate-function clusters that nobody consolidated because no one had the data to defend the recommendation.
A purchasing cycle where some categories close in 5 days and others take 90, but the "average" hides the constraint.
Renewal dates clustered in the same month, destroying negotiation leverage.

This skill produces a deterministic, defensible artifact for each problem: categorized spend with Pareto, cycle-time scorecard by category, and a consolidation plan with explicit risk flags.

典型的成长期企业通常存在以下问题：

软件支出同比增长40%，但没有专人能说出核心增长品类。
拥有3个监控工具、2个费用平台、4个电子邮件营销工具——因缺乏数据支撑整合建议，这些功能重复的工具集群始终未被合并。
采购周期时长不均，部分品类5天即可完成，部分则需90天，但“平均时长”掩盖了流程瓶颈。
续约日期集中在同一月份，彻底丧失谈判筹码。

本工具可为每个问题生成确定性、可辩护的成果：带帕累托分析的分类支出报告、分品类的周期时间评分卡，以及带有明确风险标记的整合方案。

When to use

适用场景

Annual SaaS audit and category-level spend review.
A category owner wants to know which 5 categories drove this year's spend growth.
Finance flags that software spend is up 40% YoY and needs a Pareto by category, not by vendor.
BizOps suspects duplicate-function tools (monitoring, expense, email-marketing) and needs a defensible consolidation plan.
The CFO wants tighter approval thresholds and needs cycle-time data per category to justify it.
Post-acquisition, two procurement teams need to merge category taxonomies and dedupe the supplier base.

年度SaaS审计及品类级支出审查。
品类负责人想了解今年哪5个品类推动了支出增长。
财务部门指出软件支出同比增长40%，需要按品类而非供应商划分的帕累托分析。
业务运营团队怀疑存在功能重复的工具（监控、费用、电子邮件营销），需要可辩护的整合方案。
CFO希望收紧审批阈值，需要分品类的周期时间数据作为依据。
收购完成后，两个采购团队需要合并品类分类体系并精简供应商库。

When NOT to use

不适用场景

Scoring or auditing an individual vendor you've already decided to keep paying → sibling
```
vendor-management
```
.
Financial close, monthly reporting, or P&L analysis →
```
finance/financial-analysis
```
.
Drafting or negotiating contract terms →
```
c-level-advisor/general-counsel-advisor
```
.

Building outbound sales proposals →

business-growth/contract-and-proposal-writer

对已决定继续付费的单个供应商进行评分或审计 → 同类工具
```
vendor-management
```
。
财务结账、月度报告或损益分析 →
```
finance/financial-analysis
```
。
起草或谈判合同条款 →
```
c-level-advisor/general-counsel-advisor
```
。

制作 outbound销售提案 →

business-growth/contract-and-proposal-writer

。

Workflow

工作流程

Step 1 — Intake spend

步骤1 — 收集支出数据

Have the user fill out

assets/spend_intake_template.md

(20 minutes for a typical mid-stage company). The skeleton expects line items with

{supplier, description, category_hint, annual_spend, frequency, currency}

. If prior-year spend is available, include it for YoY analysis.

让用户填写

assets/spend_intake_template.md

（典型成长期企业需20分钟完成）。模板框架要求填写包含

{供应商, 描述, 品类提示, 年度支出, 付费频率, 货币}

的明细项。若有上一年度支出数据，建议纳入以进行同比分析。

Step 2 — Categorize and find the Pareto

步骤2 — 分类并进行帕累托分析

Run

scripts/spend_categorizer.py --input spend.json --profile <profile> --output categorized.md

The categorizer maps each line item to a UNSPSC-aligned Class → Family → Segment (built-in map of ~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 UNSPSC database). Output includes:

Categorized line items
Pareto: which 20% of categories drive 80% of spend?
Top-10 YoY growth categories (when prior-year provided)

Profiles re-prioritize the category map:

tech-startup

(heavy SaaS / cloud),

scaleup

(sales tools / recruiting heavy),

enterprise

(professional services / facilities heavy),

services

manufacturing

运行

scripts/spend_categorizer.py --input spend.json --profile <profile> --output categorized.md

。

该分类器将每个明细项映射到符合UNSPSC标准的“类→族→细分”体系（内置约30个针对科技初创企业支出优化的品类：软件/SaaS、硬件、云基础设施、专业服务、营销服务、法务、招聘差旅、办公、保险、福利等——并非完整的10万级UNSPSC数据库）。输出内容包括：

分类后的支出明细项
帕累托分析：哪20%的品类驱动了80%的支出？
支出同比增长Top10品类（若提供上一年度数据）

配置文件可重新调整品类优先级：

tech-startup

（侧重SaaS/云）、

scaleup

（侧重销售工具/招聘）、

enterprise

（侧重专业服务/设施）、

services

、

manufacturing

。

Step 3 — Analyze the purchasing cycle

步骤3 — 分析采购周期

Run

scripts/purchasing_cycle_analyzer.py --input pos.json --output cycle.md

For each PO record

{category, request_date, approval_date, po_issued_date, goods_received_date, payment_date, approver_hops}

, the analyzer computes per-category:

Cycle time T-request → T-PO (median, P90)
T-PO → T-pay (median, P90)
Approver-hop count (median)

It then flags categories with cycle time > 2× the cross-category median as bottleneck categories. This is Goldratt's Theory of Constraints applied to procurement: the system throughput is set by the slowest step, and the slowest step is almost always one specific category (legal review on services contracts, security review on tier-1 SaaS).

运行

scripts/purchasing_cycle_analyzer.py --input pos.json --output cycle.md

。

针对每条PO记录

{品类, 请求日期, 审批日期, PO签发日期, 收货日期, 付款日期, 审批环节数}

，分析器将计算每个品类的：

从请求到PO签发的周期时长（中位数、90分位数）
从PO签发到付款的周期时长（中位数、90分位数）
审批环节数（中位数）

随后将周期时长超过跨品类中位数2倍的品类标记为瓶颈品类。这是Goldratt约束理论在采购中的应用：系统吞吐量由最慢的环节决定，而最慢的环节几乎总是某个特定品类（如服务合同的法务审核、一级SaaS的安全审核）。

Step 4 — Plan supplier consolidation with risk balancing

步骤4 — 制定风险平衡的供应商整合方案

Run

scripts/supplier_consolidation.py --input suppliers.json --profile <profile> --output consolidation_plan.md

The planner identifies duplicate-function clusters (e.g., 3 monitoring tools, 2 expense platforms). For each cluster:

Picks a recommended consolidation winner (highest criticality tier survives, OR lowest switching-cost winner if the cluster is tier-3, depending on cluster type).
Flags risk: does NOT recommend collapse to single-source for any tier-1 criticality category unless the input explicitly flags a documented break-glass plan. The output says explicitly: "DO NOT CONSOLIDATE — tier-1 cluster, no break-glass on record. Add a 72-hour contingency plan first."
Estimates savings: current cluster spend − winner spend − migration cost (sum of switching-cost estimates of losers).
Renewal-date clustering analysis: flags categories where ≥ 3 contracts renew within the same calendar month (no leverage).

运行

scripts/supplier_consolidation.py --input suppliers.json --profile <profile> --output consolidation_plan.md

。

该规划器会识别功能重复集群（如3个监控工具、2个费用平台）。针对每个集群：

推荐整合后的胜出供应商（高优先级品类保留核心供应商；若为三级品类，则选择切换成本最低的供应商，具体取决于集群类型）。
风险标记：若未提供书面应急方案，绝不建议将任何一级关键品类合并为单一供应商模式。输出会明确标注：“请勿整合——一级品类集群，无记录在案的应急方案。请先制定72小时 contingency plan。”
估算节省金额：当前集群支出 − 胜出供应商支出 − 迁移成本（落选供应商的切换成本估算总和）。
续约日期集群分析：标记有≥3份合同在同一日历月续约的品类（此类情况无谈判筹码）。

Step 5 — Synthesize the procurement review

步骤5 — 整合采购审查成果

Combine the 3 artifacts into a BizOps-ready digest:

Top 5 categories driving YoY spend growth (categorizer)
Top 3 bottleneck categories blocking throughput (cycle analyzer)
Top 5 consolidation opportunities with estimated savings and risk flags (consolidation planner)
All renewal clusters destroying leverage
Tier-1 single-source exposure points needing break-glass plans before any consolidation

将3份成果整合成适合业务运营团队的摘要：

推动支出同比增长的Top5品类（来自分类器）
阻碍流程吞吐量的Top3瓶颈品类（来自周期分析器）
带有估算节省金额和风险标记的Top5整合机会（来自整合规划器）
所有丧失谈判筹码的续约集群
需要先制定应急方案才能进行整合的一级单一供应商风险点

Scripts

脚本说明

Script	Purpose
`scripts/spend_categorizer.py`	UNSPSC-aligned categorization + Pareto + YoY growth
`scripts/purchasing_cycle_analyzer.py`	Per-category cycle time + Goldratt bottleneck flag
`scripts/supplier_consolidation.py`	Duplicate-function clustering + risk-flagged consolidation plan

All three accept

--input

(JSON),

--output

(markdown path),

--sample

(run with built-in sample data), and

--help

. The two with industry-specific category priorities accept

--profile {tech-startup,scaleup,enterprise,services,manufacturing}

脚本	用途
`scripts/spend_categorizer.py`	符合UNSPSC标准的支出分类 + 帕累托分析 + 同比增长分析
`scripts/purchasing_cycle_analyzer.py`	分品类周期时间分析 + Goldratt瓶颈标记
`scripts/supplier_consolidation.py`	功能重复集群识别 + 带风险标记的整合方案

三个脚本均支持

--input

（JSON格式）、

--output

（markdown路径）、

--sample

（使用内置示例数据运行）和

--help

参数。其中两个支持行业特定品类优先级的脚本还可使用

--profile {tech-startup,scaleup,enterprise,services,manufacturing}

参数。

References

参考文档

```
references/spend_management_canon.md
```
— A.T. Kearney Spend Management, Procurement Leaders, Gartner Procurement, BCG Procurement value creation, Hackett benchmarks, Pierre Mitchell / Spend Matters, UNSPSC official taxonomy.
```
references/saas_management_canon.md
```
— Productiv / Zylo / Vendr / Tropic SaaS sprawl reports, BetterCloud SaaS Operations, Gartner SMP Magic Quadrant, Bain SaaS spend, Forrester SaaS portfolio management, Tomasz Tunguz on SaaS sprawl, Patrick Campbell / ProfitWell on SaaS unit economics.
```
references/procurement_anti_patterns.md
```
— A.T. Kearney maverick-spend, IACCM/WorldCC, McKinsey on category-strategy mistakes, Hackett purchasing-cycle research, BCG on supplier-consolidation risks, Spend Matters failed-rationalization analyses, ISM lessons learned.

```
references/spend_management_canon.md
```
— A.T. Kearney《支出管理》、Procurement Leaders、Gartner采购、BCG采购价值创造、Hackett基准数据、Pierre Mitchell / Spend Matters、UNSPSC官方分类体系。
```
references/saas_management_canon.md
```
— Productiv / Zylo / Vendr / Tropic SaaS sprawl报告、BetterCloud SaaS运营、Gartner SMP魔力象限、Bain SaaS支出、Forrester SaaS组合管理、Tomasz Tunguz关于SaaS sprawl的研究、Patrick Campbell / ProfitWell关于SaaS单位经济的研究。
```
references/procurement_anti_patterns.md
```
— A.T. Kearney非合规支出研究、IACCM/WorldCC、麦肯锡关于品类策略错误的研究、Hackett采购周期研究、BCG关于供应商整合风险的研究、Spend Matters关于合理化失败的分析、ISM经验教训。

Assumptions

假设前提

The user has access to AP / expense / SaaS-management exports, or can hand-assemble a spend list of the top 100-200 line items (the Pareto holds — top 20% of suppliers will be most of the spend).
Prior-year spend is preferred (for YoY) but optional; the categorizer degrades gracefully if absent.
Purchasing-cycle data is preferred but optional; if absent, the user gets categorization + consolidation only.
Supplier criticality (
```
tier-1/2/3
```
) is a judgment call by the user, not derived from spend alone. Tier-1 = revenue-blocking if the supplier disappears. The tool refuses to infer this — the user must mark it.
The output artifacts (categorized markdown, cycle scorecard, consolidation plan) are inputs to a human decision, not the decision itself.

用户可获取应付账款/费用/SaaS管理系统的导出数据，或手动整理前100-200项支出明细（帕累托法则适用——前20%的供应商贡献了大部分支出）。
优先提供上一年度支出数据（用于同比分析），但非必需；若缺失，分类器仍可正常输出内容。
优先提供采购周期数据，但非必需；若缺失，用户仍可获取分类和整合分析结果。
供应商优先级（
```
tier-1/2/3
```
）由用户主观判断，而非仅基于支出金额。Tier-1指供应商中断服务会影响营收的品类。工具不会自动推断该信息，需用户手动标记。
输出成果（分类markdown文档、周期评分卡、整合方案）是人工决策的输入，而非最终决策。

Anti-patterns

反模式

Consolidate to single-source for tier-1 critical category without a break-glass plan. Cost savings buy nothing if the consolidated supplier disappears. See
```
references/procurement_anti_patterns.md
```
.
Categorize by vendor name, not by what's purchased. Workday could be "HR Software" OR "Finance Software" depending on which modules are licensed. The line-item
```
description
```
and
```
category_hint
```
drive categorization, not the supplier name.
Ignore renewal-date clustering. Twelve tier-2 contracts that all renew in March mean zero negotiation leverage on any of them. Spread them.
Approve-by-default for sub-$5K spend. This is the death-by-a-thousand-SaaS pattern. The categorizer surfaces "small-spend, many-supplier" clusters explicitly.
No quarterly renewal review. Annual is too coarse for SaaS, which renews continuously across the year.
Rationalize without measuring switching cost. Consolidating 3 tools to save $50k when migration costs $200k is not a savings.
Consolidate based on price alone, ignoring integration debt. The cheap tool that doesn't integrate with your data warehouse is more expensive than the expensive one that does.
Treat shadow IT spend as marketing's problem. It is procurement's problem. Marketing-tool sprawl is the #1 driver of SaaS-spend growth in scaleups.

未制定应急方案就将一级关键品类合并为单一供应商模式。若整合后的供应商中断服务，成本节省毫无意义。详情请见
```
references/procurement_anti_patterns.md
```
。
按供应商名称而非采购内容分类。Workday可能属于“HR软件”或“财务软件”，具体取决于所授权的模块。分类依据是明细项的
```
描述
```
和
```
品类提示
```
，而非供应商名称。
忽略续约日期集群。12份二级合同均在3月续约意味着完全丧失谈判筹码。应分散续约日期。
默认批准5000美元以下的支出。这是“千刀SaaS致死”模式的根源。分类器会明确标记“小额支出、多供应商”集群。
未进行季度续约审查。年度审查对SaaS而言过于粗糙，因为SaaS续约全年持续进行。
未衡量切换成本就进行合理化。整合3个工具节省5万美元，但迁移成本达20万美元，实则得不偿失。
仅基于价格进行整合，忽略集成债务。无法与数据仓库集成的低价工具，实则比可集成的高价工具更昂贵。
将影子IT支出视为营销部门的问题。这是采购部门的问题。营销工具 sprawl是成长期企业SaaS支出增长的头号驱动因素。

Distinct from

与其他工具的区别

Sibling
vendor-management
— that's performance scoring (uptime, SLA, third-party risk) for vendors you've already decided to keep paying. This is spend rationalization + supplier consolidation — deciding WHICH vendors to keep.
finance/financial-analysis
— that's financial close, P&L, reporting, DCF. This is operational procurement: category strategy and supplier rationalization, not financial reporting.
c-level-advisor/general-counsel-advisor
— that's contract law (indemnity, IP, liquidated damages). This is category-level spend strategy. Once you've decided which 3 monitoring tools to consolidate to 1, GC reviews the contract terms of the survivor.
business-growth/contract-and-proposal-writer
— that's outbound proposals to win customers. This is inbound supplier rationalization.
finance/budgeting
— that's annual budget planning. This is the inside view: where the budget is actually leaking.

同类工具
vendor-management
——该工具用于对已决定继续付费的供应商进行绩效评分（可用性、SLA、第三方风险）。本工具则聚焦支出合理化 + 供应商整合——决定保留哪些供应商。
finance/financial-analysis
——该工具用于财务结账、损益表、报告、DCF分析。本工具是运营采购：品类策略和供应商合理化，而非财务报告。
c-level-advisor/general-counsel-advisor
——该工具用于合同法（赔偿、知识产权、违约金）。本工具聚焦品类级支出策略。当决定将3个监控工具整合为1个后，总法律顾问负责审查胜出供应商的合同条款。
business-growth/contract-and-proposal-writer
——该工具用于制作 outbound客户提案。本工具用于 inbound供应商合理化。
finance/budgeting
——该工具用于年度预算规划。本工具提供内部视角：预算实际流失的环节。

Forcing-question library (Matt Pocock grill discipline)

强制问题库（Matt Pocock grill discipline）

Walked one at a time by

/cs:grill-bizops

or the BizOps orchestrator. Recommended answer + canon citation per question. Never bundled.

"Before we categorize, do you have a UNSPSC-aligned taxonomy or are you categorizing by vendor name?" Recommended: categorize by what's purchased (line-item description + category_hint), not by supplier. A single supplier can span multiple categories. Canon: UNSPSC official taxonomy documentation, A.T. Kearney Spend Management on category architecture.
"Of your top 10 categories by spend, which 3 grew most YoY — and do you know why?" Recommended: name them before opening the tool. If you can't name them, that's the diagnosis. Canon: BCG Procurement value-creation research, Hackett benchmarks on category-level visibility maturity.
"For each duplicate-function cluster (e.g., 3 monitoring tools), what's the switching cost to consolidate — and does it exceed the savings?" Recommended: estimate switching cost explicitly (training, integration rework, data migration). Refuse to recommend consolidation without it. Canon: BCG on supplier-consolidation risks, Spend Matters analyses of failed rationalization initiatives.
"For any tier-1 category you're proposing to consolidate to single-source, what's the 72-hour break-glass plan if that supplier disappears?" Recommended: documented contingency per category, tested. If absent, do not consolidate. Canon: NotPetya / M.E.Doc supply chain attack lessons, NIST SP 800-161, A.T. Kearney on supply concentration risk.
"What % of your spend goes through a PO vs. expense reimbursement vs. shadow IT? Where's the maverick spend?" Recommended: measure it. A.T. Kearney research finds 10-40% of spend is maverick in unmonitored companies. Canon: A.T. Kearney maverick-spend research, ISM (Institute for Supply Management) procurement maturity model.
"How many of your top-20 contracts renew in the same calendar month? Do you have a renewal calendar?" Recommended: build the calendar; spread renewals deliberately. Clustered renewals destroy negotiation leverage. Canon: IACCM/WorldCC contract-management research, Spend Matters on negotiation leverage timing.
"What's your approval threshold for net-new SaaS purchases under $5k? Who owns the death-by-a-thousand-SaaS problem?" Recommended: a tightened threshold + a single owner. Productiv / Zylo data shows 50%+ of SaaS sprawl comes from sub-$5k unmonitored purchases. Canon: Productiv / Zylo / Vendr industry reports on SaaS sprawl.

Walk depth-first. Lock 1-4 before opening 5-7. After all are answered, invoke

spend_categorizer.py

→

purchasing_cycle_analyzer.py

→

supplier_consolidation.py

in sequence.

由

/cs:grill-bizops

或业务运营编排器逐一提问。每个问题均提供推荐答案及参考文档引用。请勿批量提问。

“在分类之前，你是否采用符合UNSPSC标准的分类体系，还是按供应商名称分类？” 推荐答案：按采购内容（明细项描述+品类提示）分类，而非供应商名称。单个供应商可能涉及多个品类。参考文档：UNSPSC官方分类体系文档、A.T. Kearney《支出管理》中关于品类架构的内容。
“在支出Top10品类中，哪3个品类同比增长最快——你知道原因吗？” 推荐答案：在使用工具前先明确这些品类。若无法说出，这本身就是问题诊断的结果。参考文档：BCG采购价值创造研究、Hackett关于品类可见性成熟度的基准数据。
“针对每个功能重复集群（如3个监控工具），整合的切换成本是多少——是否超过节省金额？” 推荐答案：明确估算切换成本（培训、集成返工、数据迁移）。若无该数据，拒绝推荐整合。参考文档：BCG关于供应商整合风险的研究、Spend Matters关于合理化失败案例的分析。
“对于任何拟合并为单一供应商模式的一级品类，若该供应商中断服务，你的72小时应急方案是什么？” 推荐答案：每个品类均有书面应急方案并经过测试。若无方案，请勿整合。参考文档：NotPetya / M.E.Doc供应链攻击教训、NIST SP 800-161、A.T. Kearney关于供应集中风险的研究。
“你的支出中，通过PO、费用报销、影子IT的占比分别是多少？非合规支出在哪里？” 推荐答案：进行量化衡量。A.T. Kearney研究发现，未受监控的企业中10-40%的支出为非合规支出。参考文档：A.T. Kearney非合规支出研究、ISM（供应管理协会）采购成熟度模型。
“你的Top20合同中有多少份在同一日历月续约？你是否有续约日历？” 推荐答案：建立续约日历；刻意分散续约日期。集中续约会彻底丧失谈判筹码。参考文档：IACCM/WorldCC合同管理研究、Spend Matters关于谈判时机与筹码的内容。
“你对5000美元以下的新增SaaS采购的审批阈值是多少？谁负责解决‘千刀SaaS致死’问题？” 推荐答案：收紧审批阈值 + 指定专人负责。Productiv / Zylo数据显示，50%以上的SaaS sprawl来自未受监控的5000美元以下采购。参考文档：Productiv / Zylo / Vendr关于SaaS sprawl的行业报告。

按深度优先顺序提问。先确认问题1-4，再提问5-7。所有问题回答完毕后，依次调用

spend_categorizer.py

→

purchasing_cycle_analyzer.py

→

supplier_consolidation.py

。