Capstone — End-to-End Procurement
You have spent thirteen lessons building a procurement operating system component by component. You classified vendors into Kraljic tiers. You ran six-dimension assessments. You designed and tested three-way match tolerance rules. You built a supplier risk dashboard. You analysed logistics carrier performance and spend patterns. You wrote professional vendor communications. You deployed five persistent intelligence agents. And you built a vendor exit protocol for the scenario you hoped would never happen.
Each of those capabilities is valuable on its own. But the procurement team that uses /vendor-assess once and never connects the output to their risk thresholds, their agent configuration, or their invoice reconciliation rules is using a point tool. The team that connects these capabilities into a system — where the classification register informs the risk thresholds, which inform the agent watch list, which feeds the executive brief, which drives the actions that prevent the exit scenarios — has a procurement operating system.
This capstone builds that system for one spend category from scratch, running all seven phases in sequence, using each phase's output as the input to the next. The deliverable is not a document. It is a deployable system that runs continuously after this session ends.
Duration: 90 minutes. Use your own vendor data from Exercises 1-8 wherever possible.
Capstone Scenario
You are the procurement lead for a mid-sized organisation. Your CPO has asked you to bring a new vendor category under active procurement management — a category that has been procured ad-hoc by different business units without coordinated vendor relationships, tolerance rules, or risk monitoring.
Your category: Choose one from your own organisation, or use this scenario:
Category: Industrial packaging materials (corrugated cardboard, protective foam, shrink film)
Current state: 7 vendors across 3 business units; no classification; no formal assessments; invoices processed manually with high exception rates; no agent monitoring
CPO requirement: Classify and assess all vendors; configure automated invoice processing; deploy risk monitoring; deliver the first weekly executive brief within this session
Each phase below maps to a skill or set of skills you have already used. Follow the sequence — each output feeds the next phase.
Phase 1: Vendor Classification
Skills: /vendor-assess (classification mode)
Time: ~12 minutes
Feeds: Phase 2 (assessment depth), Phase 4 (risk thresholds), Phase 6 (agent watch list)
Start with classification — you cannot calibrate assessment depth, risk thresholds, or agent monitoring without knowing what tier each vendor belongs to.
For each vendor in your category, classify using the Kraljic framework (supply risk × profit impact):
/vendor-assess mode:"classification"
vendor:"[Vendor name]"
category:"[Your category]"
annual-spend:"[Amount]"
dependency:"[Sole-source / dual-source / multiple alternatives]"
switching-timeline:"[Days or months to replace]"
profit-impact:"[% of category cost / operational dependency]"
Build your classification register:
| Vendor | Tier | Classification | Supply Risk | Profit Impact | Review Frequency | Priority Action |
|---|---|---|---|---|---|---|
Cross-phase note: The vendor tier determines everything downstream. Your Tier 1 (Strategic) vendors get full six-dimension assessments (Phase 2), quarterly review frequency, and a place on the Vendor Health Monitor watch list. Your Tier 4 (Bottleneck) vendors get the same monitoring intensity despite low spend. Tier 2 and Tier 3 vendors get lighter treatment — use your assessment time where the risk is highest.
If you completed Exercise 1 in Lesson 3, you already have a partial classification register. For the capstone, extend it with the new category vendors, or bring in the Exercise 1 register if the categories overlap.
Phase 2: Vendor Assessment
Skills: /vendor-assess (full assessment mode)
Time: ~15 minutes
Feeds: Phase 4 (risk dimensions and scores), Phase 5 (spend baseline and savings targets), Phase 6 (agent parameters)
Classify first, then assess. For Tier 1 (Strategic) and Tier 4 (Bottleneck) vendors from Phase 1, run the full six-dimension assessment:
/vendor-assess mode:"full-assessment"
vendor:"[Tier 1 or Tier 4 vendor name]"
category:"[Category]"
financial-data:"[Latest accounts summary or risk indicators available]"
operational-data:"OTD: [X]%, quality rejection: [X]%, lead time: [X days]"
compliance-data:"ISO 9001: [yes/no], Modern Slavery statement: [yes/no]"
relationship-data:"[Years trading, last formal review, contract terms]"
market-data:"[Number of alternatives, market concentration, switching cost]"
Collect assessment scores for each Tier 1/4 vendor:
| Vendor | Financial | Operational | Compliance | Relationship | Strategic Fit | Market Position | Overall |
|---|---|---|---|---|---|---|---|
Cross-phase note: The assessment dimensions connect to the risk framework (Phase 4) — financial score informs the financial risk dimension, operational score maps to performance risk. The market position dimension informs your tolerance rules in Phase 3 (Tier 1 vendors with strong market position can negotiate tighter tolerances). Record the scores — Phase 4 uses them.
Phase 3: Reconciliation Rules Configuration
Skills: /invoice-reconcile
Time: ~10 minutes
Feeds: Phase 5 (invoice processing baseline), Phase 6 (Invoice Reconciliation Agent parameters)
Configure the tolerance rules for your new category's vendors. Tolerances should be calibrated to vendor tier (a Tier 1 Strategic vendor relationship warrants tighter tolerance investigation than a Tier 3 Commodity vendor):
/invoice-reconcile mode:"configure-tolerances"
category:"[Your category]"
tier-1-price-tolerance:"[Typically 0.5-1%]"
tier-2-price-tolerance:"[Typically 1-2%]"
tier-3-price-tolerance:"[Typically 2-3%]"
tier-4-price-tolerance:"[Typically 0.5-1% — same as Tier 1: bottleneck vendors warrant careful invoicing review]"
quantity-tolerance:"[e.g. 0 units for Tier 1; 1 unit for Tier 3]"
materiality-threshold:"[Invoice value below which minor variances auto-approve]"
escalation-threshold:"[Invoice value above which variances go to CPO not category manager]"
Verify the configuration by running a test invoice:
/invoice-reconcile mode:"test"
invoice-amount:"[Sample invoice amount]"
po-amount:"[PO amount]"
goods-receipt:"[GR amount]"
vendor-tier:"[Tier from Phase 1]"
apply-rules:"from:supply-chain.local.md"
Confirm the test invoice is classified correctly: MATCHED (within tolerance), PRICE VARIANCE (in tolerance), or PRICE VARIANCE (out of tolerance — route to manager).
Cross-phase note: These tolerance rules are loaded into the Invoice Reconciliation Agent in Phase 6. The agent applies exactly these rules to every incoming invoice from category vendors automatically.
Phase 4: Supplier Risk Dashboard
Skills: /supplier-risk
Time: ~12 minutes
Feeds: Phase 6 (Vendor Health Monitor thresholds), Phase 7 (executive brief risk section)
Using the assessment scores from Phase 2, build the supplier risk dashboard for your critical vendors:
/supplier-risk mode:"build-dashboard"
vendor:"[Tier 1 or Tier 4 vendor]"
financial-risk:"[Score from Phase 2 financial dimension]"
operational-risk:"[Score from Phase 2 operational dimension]"
concentration-risk:"[Single-source or multi-source — from Phase 1]"
compliance-risk:"[Certification gaps from Phase 2 compliance dimension]"
geopolitical-risk:"[Vendor country / supply route risk]"
review-frequency:"[Quarterly for Tier 1/4; bi-annual for Tier 2]"
Output dashboard structure:
| Vendor | Financial | Operational | Concentration | Compliance | Geopolitical | Overall | Alert Threshold | Review Date |
|---|---|---|---|---|---|---|---|---|
Define alert thresholds for each vendor at this stage — the specific score or metric change that would trigger an immediate Vendor Health Monitor alert. Example:
- AlphaSteel Corp Tier 1: alert if financial score drops >2 points, or OTD falls below 88%
- KIFTL Tier 4: alert if OTD falls below 85%, or any financial distress news (zero tolerance for single-source Bottleneck)
Cross-phase note: These thresholds load directly into the Vendor Health Monitor in Phase 6. Do not configure the agent with generic thresholds — use the risk-informed thresholds from this phase.
Phase 5: Logistics and Spend Analysis
Skills: /logistics-brief, /spend-analysis
Time: ~15 minutes
Feeds: Phase 6 (Logistics Intelligence Agent parameters, Spend Intelligence Agent category configuration), Phase 7 (executive brief baseline data)
Logistics analysis:
/logistics-brief mode:"carrier-performance"
category:"[Your category]"
carriers:"[Primary carriers used for this category]"
sla-thresholds:"[Per carrier OTD target]"
cost-baseline:"[Current cost per kg or per shipment]"
volume:"[Monthly shipment volume]"
Note: current carrier OTD rates, cost per kg, and the carrier(s) with the highest performance gap against SLA. These become the performance baseline against which the Logistics Intelligence Agent tracks improvement or decline.
Spend analysis:
/spend-analysis mode:"category-baseline"
category:"[Your category]"
vendors:"[List from Phase 1]"
spend-period:"trailing-12-months"
sites-or-bus:"[Business units buying from this category]"
commodity-index:"[Relevant index — e.g. paper/board FOEX PIX if packaging]"
The spend analysis output should identify:
- Total category spend and split by vendor
- Any price inconsistency across business units (site A paying £X; site B paying £Y for the same product)
- Annual saving if all aligned to the best observed rate (this becomes the savings pipeline entry)
- Whether the commodity index has moved >8% since the last contract negotiation (renegotiation trigger)
Record for Phase 7:
- Category spend total (for executive brief)
- Largest single identified saving opportunity with £ value
- Any commodity price alert
Phase 6: Deploy All Five Agents
Skills: All 5 agents + /schedule
Time: ~15 minutes
Feeds: Phase 7 (all agent outputs feed the executive brief)
This is the phase where the category goes from manually managed to continuously monitored. Deploy each agent with the parameters derived from the earlier phases:
Vendor Health Monitor — use the vendor list from Phase 1 and the alert thresholds from Phase 4:
/schedule agent:"vendor-health-monitor"
vendors:"[Tier 1 and Tier 4 vendors from Phase 1 classification register]"
thresholds:"[Risk-informed thresholds from Phase 4 dashboard]"
daily-news-scan:"enabled"
weekly-digest:"monday-07:00"
hot-alert-recipients:"CPO, [category manager]"
digest-recipients:"CPO, Finance Director, Logistics Manager"
Invoice Reconciliation Agent — use the tolerance rules configured in Phase 3:
/schedule agent:"invoice-reconciliation-agent"
trigger:"ap-inbox-arrival"
tolerance-rules:"from:supply-chain.local.md [Phase 3 config]"
exception-routing:"tier-based-routing"
weekly-report:"friday-17:00"
report-recipient:"Finance Manager"
Procurement Calendar Agent — load contract and certification data from Phase 2 assessments:
/schedule agent:"procurement-calendar-agent"
contracts:"[Contract list with expiry dates from Phase 2 assessments]"
certifications:"[ISO and compliance expiry dates from Phase 2]"
alert-recipients:"[category manager], CPO"
Logistics Intelligence Agent — use the carrier baseline from Phase 5:
/schedule agent:"logistics-intelligence-agent"
carriers:"[Carriers identified in Phase 5]"
sla-baselines:"[OTD targets from Phase 5 analysis]"
cost-baselines:"[Cost per kg from Phase 5]"
fuel-index-threshold:"5%"
weekly-report:"monday-08:00"
alert-recipients:"Logistics Manager, Procurement"
Spend Intelligence Agent — use the spend baseline and commodity index from Phase 5:
/schedule agent:"spend-intelligence-agent"
category:"[Your category]"
vendors:"[Full vendor list from Phase 1]"
commodity-index:"[Relevant index from Phase 5]"
commodity-threshold:"8%"
baseline:"[Phase 5 spend data]"
monthly-report:"first-monday"
alert-recipients:"CPO, Finance Director"
Verify all five agents are configured and active. Note the confirmation output from each /schedule command.
Phase 7: First Weekly Executive Brief
Skills: /supply-chain-brief
Time: ~11 minutes
Feeds: Deliverable
You now have a running procurement operating system for your category. Generate the first weekly brief that your CPO and COO will receive:
/supply-chain-brief type:"weekly-executive"
audience:"CPO, COO"
category:"[Your category]"
format:"one page; RAG status per metric; one key issue;
one recommended action with owner and deadline;
savings pipeline total"
include:"vendor-health-summary, invoice-performance-summary,
contract-calendar-critical, logistics-performance-summary,
spend-analytics-summary"
baseline-data:"[Phase 5 spend total, Phase 4 risk summary,
Phase 5 savings pipeline, Phase 3 exception rate]"
Evaluate your output against the CPO brief standard:
| Element | Present? | Decision-ready? |
|---|---|---|
| RAG status for each key metric | ||
| Single most-important issue this week | ||
| Recommended action with owner and deadline | ||
| Savings pipeline total with £ value | ||
| Vendor risk summary (any alerts since last brief) | ||
| Contract calendar — any critical deadlines? |
If any element is missing or is too detailed for executive consumption, refine the prompt:
/supply-chain-brief type:"weekly-executive"
[add specific format instruction: e.g. "RAG status only, no supporting data"
or "limit to 3 bullets per section" or "combine logistics and vendor risk
into single Operations section"]
Iterate until the brief is genuinely decision-ready — the format your CPO would actually want to receive.
Capstone Deliverable
By the end of this session you should have produced:
1. Classification Register All category vendors classified with Kraljic tiers, review frequencies, and priority actions (Phase 1).
2. Vendor Assessment Scores Full six-dimension assessments for all Tier 1 and Tier 4 vendors (Phase 2).
3. Reconciliation Rules Configuration Tier-calibrated tolerance rules for the category, tested against a sample invoice (Phase 3).
4. Supplier Risk Dashboard Risk scores across five dimensions with alert thresholds for each Tier 1/4 vendor (Phase 4).
5. Logistics and Spend Baseline Current carrier performance and category spend data with the identified savings pipeline entry (Phase 5).
6. Five Deployed Agents All five agents configured, scheduled, and running — with parameters derived from the earlier phases (Phase 6).
7. First Weekly Executive Brief The CPO/COO brief template with first output, formatted for decision-use (Phase 7).
This is your procurement operating system for one category. It classifies, assesses, monitors invoices, tracks deadlines, monitors carriers, analyses spend, and delivers a weekly brief — without requiring the procurement team to remember to run any of it.
- Monday 07:00: Vendor Health Monitor hot alerts (if any) + weekly vendor health digest
- Monday 08:00: Logistics performance report + Procurement Calendar weekly sweep
- Friday 17:00: Invoice exception report with open items approaching payment terms
- First Monday of month: Spend intelligence report with new savings opportunities and commodity alerts
- Weekly: Supply chain brief to CPO and COO (you generate the first one manually; the agents feed subsequent briefs)
Connecting the Exercises: How the Chapter Fits Together
The capstone uses all eight skills and integrates all eight exercises. Here is how the exercise outputs connect:
| Earlier Exercise | Capstone Phase Using It | What It Contributes |
|---|---|---|
| Ex 1 — Vendor Classification (L03/L04) | Phase 1 + Phase 2 | Classification register and assessment depth calibration |
| Ex 1B — Risk Configuration (L04) | Phase 4 | Six-dimension scores and alert thresholds |
| Ex 2 — Invoice Reconciliation Sprint (L06) | Phase 3 | Invoice pattern data for tolerance calibration |
| Ex 3 — Supplier Risk Dashboard (L07) | Phase 4 | Risk dimension framework and scoring methodology |
| Ex 4 — Logistics Optimisation (L08) | Phase 5 | Carrier performance baseline |
| Ex 5 — Spend Consolidation (L10) | Phase 5 | Category spend baseline and consolidation opportunities |
| Ex 6 — Three-Way Match Rules (L05) | Phase 3 | Tolerance rule design pattern |
| Ex 7 — Intelligence Dashboard (L12) | Phase 6 + Phase 7 | Agent configuration and executive brief format |
| Ex 8 — Vendor Exit Protocol (L13) | Phase 4 + Escalation design | Alert thresholds and exit scenario preparedness |
The capstone is not an independent exercise — it is the integration of everything you have built. If you completed the earlier exercises with your own vendor data, the capstone output is a working starting point for your organisation.
Try With AI
Setup: Use these prompts in Cowork or your preferred AI assistant.
Prompt 1: Reproduce
I just completed a full procurement cycle for one category using 8 skills
and 5 agents. Summarise the sequence of phases I followed, the skill used
in each phase, and explain why the order matters — what would break if I
ran Phase 4 (risk monitoring) before Phase 1 (vendor classification)?
What you are learning: The dependency chain that connects vendor classification to every downstream workflow — classification determines assessment depth, risk thresholds, and review frequency.
Prompt 2: Adapt
I want to repeat this capstone for a second procurement category (e.g.,
indirect services or IT hardware). What would I need to change in each
of the 7 phases? Where can I reuse my existing configuration, and where
must I start fresh? Produce a checklist for "deploy procurement
operating system for new category."
What you are learning: The reusability of your procurement operating system — which components are category-specific (tolerance rules, vendor list) and which are shared (agent schedules, brief format).
Prompt 3: Apply
My CPO asks: "What would it take to roll this out across all 12 of our
procurement categories?" Draft a one-page rollout plan that covers:
1. Which categories to prioritise (and why)
2. Estimated time per category based on what you learned
3. What infrastructure is shared vs. per-category
4. What the CPO's weekly brief looks like once all 12 are live
What you are learning: The difference between building a prototype for one category and scaling a procurement operating system across an organisation — the strategic planning that turns a chapter exercise into a real deployment.
Continue to Lesson 15: Chapter Summary & Quick Reference →