Vendor Management — The Portfolio View
Your organisation has 47 vendors. You know this because you just counted — pulling from three spreadsheets, the finance system, a shared drive folder of contract PDFs, and two email threads from people who left last year. Nobody had this number before you assembled it. Your CFO thought it was around 30. Your operations manager guessed 25. The actual number — and the £1.85 million annual spend it represents — was invisible until someone decided to look.
This is not unusual. In most organisations, the vendor portfolio is scattered across procurement records, departmental credit cards, auto-renewing subscriptions, and contracts signed by people who have since moved on. The result is predictable: contracts renew without renegotiation because nobody knew the renewal date was approaching; three teams pay for overlapping project management tools because nobody has a cross-departmental view; and a marketing automation platform costing £67,000 per year renews even though the team that used it was disbanded six months ago. Research from McKinsey and Kearney consistently finds 5-15% of total vendor spend as addressable savings through portfolio rationalisation, with conservative implementations typically realising 8-12% within the first year — savings that require no hard negotiation, just knowing what you already have.
This lesson teaches you to make the invisible visible. You will use the /vendor-review command to run a portfolio audit, interpret the output, build a renewal calendar, and identify where rationalisation can recover wasted spend. The goal is not to cut vendors for the sake of cutting — it is to ensure that every vendor relationship is visible, evaluated, and actively managed.
This exercise requires the Operations plugin (official) and the Operations Intelligence plugin (custom). If you have not installed them, follow the instructions in the Chapter 38 prerequisites before continuing.
The Invisible Portfolio Problem
Vendor management fails not because organisations lack vendor relationships — they have too many. It fails because the portfolio is invisible. Nobody has a single, current, accurate view of:
- Every vendor, what they provide, and what it costs
- Which contracts are expiring and when
- Which vendors are underperforming against their SLAs
- Which vendor categories have multiple vendors providing the same capability
- Which subscriptions are actively used versus passively renewing
The consequence is operational waste that compounds quietly. Each auto-renewed contract, each overlapping tool, each unknown-usage subscription is individually small enough to escape attention. In aggregate, they represent a significant and entirely preventable cost.
| Failure Mode | What Happens | Why It Persists |
|---|---|---|
| Auto-renewal without review | Contracts renew at existing terms; no negotiation | Nobody tracks renewal dates across all vendors |
| Overlapping capabilities | 3 teams use 3 different project management tools | No cross-departmental view of vendor categories |
| Unknown usage | Subscription renews but nobody uses the product | The person who signed the contract has left |
| Underperformance without evidence | Vendor misses SLAs but nobody has the data to prove it | Performance tracking is manual or nonexistent |
The first step in solving any of these problems is the same: build the portfolio view. You cannot rationalise what you cannot see. You cannot negotiate without evidence. And you cannot manage renewals if you do not know when they occur.
Running a Portfolio Audit with /vendor-review
The /vendor-review command evaluates vendors across cost, risk, performance, and fit. For a portfolio audit, you provide a complete vendor list and ask for a full portfolio analysis.
Worked example. You are the Operations Manager at a 200-person professional services firm. You have assembled a list of 47 vendors from finance records, departmental budgets, and subscription management tools. You type:
/vendor-review
Run a vendor portfolio audit for our organisation. We are a 200-person
professional services firm based in the UK. Here is our vendor list
(47 vendors):
[Paste vendor list with columns: vendor name, category, annual cost (GBP),
contract end date, primary department owner, usage status
(active/partial/unknown)]
What to expect: The output should contain four major sections — spend analysis, immediate attention items, rationalisation opportunities, and a renewal calendar.
| Output Section | What to Verify |
|---|---|
| Spend by category | Categories are correctly assigned; total spend matches your input data |
| Immediate attention | Renewals within 90 days are flagged with dates and values |
| Rationalisation opportunities | Overlapping categories are identified with estimated savings |
| Renewal calendar | All 47 vendors appear with correct dates organised by quarter |
A well-formed portfolio audit output looks like this:
VENDOR PORTFOLIO AUDIT
════════════════════════════════════════════════════════════
Total vendors: 47
Total annual spend: £1,847,000
Audit date: [Date]
Data completeness: 68% (15 vendors missing usage data)
── SPEND BY CATEGORY ────────────────────────────────────────
Software / SaaS: £842,000 (46%) — 31 vendors
Professional services: £420,000 (23%) — 8 vendors
Infrastructure / cloud: £385,000 (21%) — 5 vendors
Other: £200,000 (11%) — 3 vendors
── IMMEDIATE ATTENTION REQUIRED ────────────────────────────
RENEWALS IN NEXT 90 DAYS (7 vendors):
CRM platform — £124,000/yr — renews 15 April
Project management — £18,000/yr — renews 22 April
HR platform — £31,000/yr — renews 1 May
[...]
ACTION: Begin renegotiation for all renewals >£50,000 immediately.
USAGE UNKNOWN — HIGH SPEND (5 vendors):
Marketing automation — £67,000/yr — no usage data
Analytics platform — £45,000/yr — no usage data
[...]
ACTION: Audit usage before next renewal.
── RATIONALISATION OPPORTUNITY ─────────────────────────────
Project management tools: 3 vendors — £42,000 combined
→ Consolidate to 1-2 tools; estimate £15,000-£20,000 savings
Video/conferencing: 2 vendors — £28,000 combined
→ Consolidate; estimate £10,000-£14,000 savings
Document management: 2 vendors — £19,000 combined
→ Review; one may be legacy/redundant
── RENEWAL CALENDAR (NEXT 12 MONTHS) ──────────────────────
Q2: £312,000 in renewals — 12 vendors
Q3: £95,000 in renewals — 8 vendors
Q4: £223,000 in renewals — 11 vendors
Q1 (next year): £187,000 in renewals — 9 vendors
── SAVINGS SUMMARY ─────────────────────────────────────────
Category consolidation (estimated): £25,000-£34,000
Unknown-usage cancellation opportunity: £112,000
Renegotiation opportunity (>£50k): £18,000-£37,000
Total addressable savings: £155,000-£183,000
════════════════════════════════════════════════════════════
Notice the "68% data completeness" flag. Fifteen vendors have no usage data, which means the audit cannot determine whether those subscriptions are actively used. The AI correctly flags this gap, but it cannot fill it — only your organisation can confirm actual usage. The addressable savings figure of £155,000-£183,000 is conditional on that usage data being collected. Treat it as a ceiling, not a commitment.
Evaluating the Audit Output
The portfolio audit is a structured starting point, not a final recommendation. The AI does not know which tools your teams actually rely on, which vendor relationships are strategic, or which contracts have complex exit terms. Your job is to evaluate the output against your organisational knowledge.
What to evaluate:
- Spend categories — Are vendors assigned to the correct categories? A security consultancy miscategorised as "Other" will distort the professional services total.
- Rationalisation assumptions — The AI estimates savings from consolidation, but does it account for switching costs? If consolidating three project management tools requires migrating 200 users, the short-term cost may exceed the annual savings.
- Renewal urgency — Are the renewal dates correct? A vendor with a 90-day notice period and a renewal in 95 days is not "upcoming" — it is already past the negotiation window.
- Missing vendors — Does the audit cover all 47 vendors you provided, or did some get dropped? Count the output.
- Savings realism — The "total addressable savings" figure is an estimate. Does it distinguish between near-certain savings (cancelling unused subscriptions) and speculative savings (renegotiation outcomes)?
The addressable savings estimate depends on assumptions the AI makes about renegotiation outcomes, consolidation feasibility, and cancellation candidates. A 15-30% renegotiation saving on enterprise contracts is a common industry benchmark, but your specific leverage depends on contract terms, competitive alternatives, and relationship history. Always decompose the savings number into its components before presenting it to leadership.
SLA Scorecards — From Audit to Evidence
The portfolio audit tells you where your money goes. SLA scorecards tell you whether you are getting what you paid for. Run /vendor-review a second time, focused on a specific vendor's performance:
/vendor-review
Generate a vendor scorecard for our cloud infrastructure provider.
SLA commitments: 99.9% uptime, <4hr P1 response, <24hr P1 resolution.
Last quarter actual: 99.7% uptime (3 incidents), average P1 response
2.1hr, average P1 resolution 31hr.
Contract value: £385,000/yr. Renewal in 8 months.
What to expect: A structured scorecard comparing contracted SLAs against actual performance, with a clear MET/BREACH status for each metric and renewal strategy recommendations.
| Scorecard Element | What to Verify |
|---|---|
| SLA comparison | Each metric shows contracted vs. actual with MET/BREACH status |
| Financial impact | Estimated cost of breaches (downtime, lost productivity) |
| Credit claim | Whether the contract entitles you to SLA credits |
| Renewal strategy | Specific negotiation points based on performance evidence |
The scorecard transforms anecdotal frustration ("they've had some outages") into structured evidence that changes your negotiation position. You are no longer asking for better terms — you are demonstrating that the vendor failed to deliver the terms they already agreed to.
Exercise: Run a Vendor Portfolio Audit (Exercise 1)
Type: Vendor management
Time: 30 minutes
Plugin command: /vendor-review
Goal: Audit a 47-vendor portfolio, identify rationalisation opportunities, and build a renewal calendar
Step 1 — Prepare Your Vendor Data
Use the following scenario. You are the Operations Manager at a 200-person UK professional services firm. Your assembled vendor list includes 47 vendors across four categories:
- Software/SaaS (31 vendors): CRM, project management (x3), HR platform, marketing automation, analytics, design tools, communication tools, development tools, security tools, and others
- Professional services (8 vendors): Legal counsel, external auditors, recruitment, management consultancy, IT consultancy, training provider, PR agency, translation services
- Infrastructure/cloud (5 vendors): Primary cloud provider, secondary cloud, CDN, domain/DNS, backup storage
- Other (3 vendors): Office supplies, facilities management, insurance
For each vendor, note: name, category, approximate annual cost, contract end date (spread across all four quarters), department owner, and usage status.
Step 2 — Run the Portfolio Audit
/vendor-review
Run a full vendor portfolio audit for a 200-person UK professional services
firm. We have 47 vendors. Total annual spend is approximately £1.85M.
[Paste or describe your vendor list with: name, category, annual cost (GBP),
contract end date, owner department, usage status (active/partial/unknown).
Mark at least 5 vendors as "usage unknown" and include at least 3 overlapping
categories (e.g., 3 project management tools).]
Step 3 — Evaluate the Output
What to evaluate:
- Does the spend-by-category breakdown match the input you provided? Are the percentages correct?
- Does the audit flag the correct number of renewals in the next 90 days?
- Are the rationalisation opportunities real? Would consolidating those vendors actually be feasible in your organisation?
- Does the "usage unknown" section correctly identify the vendors you flagged?
- Is the total addressable savings figure decomposed into categories, or is it a single unsupported number?
- Would a COO find this report actionable — could they make decisions based on it, or would they need to ask follow-up questions?
Step 4 — Build the Renewal Calendar
Extract every renewal date from the audit output and organise them into a quarterly renewal calendar:
| Quarter | Vendors Renewing | Combined Value | Negotiation Required (>£50K) |
|---|---|---|---|
| Q2 | [list] | £[total] | [yes/no for each] |
| Q3 | [list] | £[total] | [yes/no for each] |
| Q4 | [list] | £[total] | [yes/no for each] |
| Q1 (next) | [list] | £[total] | [yes/no for each] |
Step 5 — Identify the Top Three Actions
Based on the audit, identify the three highest-impact actions your organisation should take immediately. For each, specify:
- Action — what to do
- Value at stake — the annual cost affected
- Deadline — when the action must be completed (based on renewal dates or usage audit timelines)
Deliverable: A completed portfolio audit with evaluated output, a quarterly renewal calendar, and three prioritised actions. Save this work — Lesson 4 (Contract Analysis) will deepen the intelligence on your highest-value vendor relationships.
The vendor portfolio audit and renewal calendar you build here are the foundation for exercises in Lessons 4 (contract analysis), 7 (compliance), and 12 (persistent agents). Keep this work in your Cowork session — each subsequent lesson adds layers to this initial audit.
Try With AI
Reproduce: Apply what you just learned to a simple case.
I run a 50-person technology startup with 22 vendors. Run a vendor
portfolio audit. Here are my vendors:
- AWS (cloud infrastructure, £180,000/yr, renews Sept, engineering)
- Salesforce (CRM, £45,000/yr, renews March, sales)
- Slack (comms, £12,000/yr, renews June, all departments)
- Notion (docs/wiki, £8,000/yr, renews June, all departments)
- Confluence (docs/wiki, £6,000/yr, renews August, engineering)
- Jira (project mgmt, £14,000/yr, renews August, engineering)
- Asana (project mgmt, £9,000/yr, renews May, marketing)
- Linear (project mgmt, £7,000/yr, renews July, product)
- GitHub (code hosting, £18,000/yr, renews October, engineering)
- Figma (design, £11,000/yr, renews April, design)
[Add 12 more vendors of your choice to reach 22, including at least
2 with "usage unknown" status.]
Identify rationalisation opportunities and build a renewal calendar.
What you are learning: Running an audit on a smaller portfolio builds the pattern recognition you need before tackling a larger, messier dataset. Notice how even 22 vendors produce overlap (docs/wiki x2, project management x3) that nobody was tracking.
Adapt: Modify the scenario to match your organisation.
Run a vendor portfolio audit for my organisation. We are a [size]
[industry] company based in [location]. I have [N] vendors:
[List your actual vendors or create a realistic set for your industry.
Include: name, category, annual cost, renewal date, owning department,
and usage status. Be honest about which vendors you are unsure about
— mark those as "usage unknown".]
Focus on: (1) where we have overlapping capabilities, (2) which
renewals are approaching without a negotiation plan, and (3) which
high-spend vendors have no performance data on file.
What you are learning: Applying the audit to your own vendor base reveals the specific gaps in your organisation's portfolio visibility — gaps that are invisible until someone explicitly maps them.
Apply: Extend to a new situation the lesson didn't cover directly.
I have completed a vendor portfolio audit that identified 5 overlapping
categories and £180,000 in potential addressable savings. My COO has
asked me to present a vendor rationalisation business case to the
leadership team next week.
For each of the 5 overlapping categories, help me build a rationalisation
recommendation that includes:
1. Current state (which vendors, what each costs, who uses them)
2. Recommended target state (consolidate to which vendor and why)
3. Migration risk and timeline
4. Estimated savings (net of switching costs)
5. A one-paragraph executive summary suitable for a leadership slide
Also flag any category where rationalisation is NOT recommended and
explain why (e.g., switching costs exceed 3 years of savings).
What you are learning: Moving from audit to business case is the real operational skill. The audit identifies the opportunity; the business case determines whether it is worth pursuing. This prompt tests whether you can translate analytical output into executive-level recommendations — including knowing when NOT to consolidate.
Flashcards Study Aid
Continue to Lesson 4: Contract Analysis — Obligation Extraction →