Vendor management

Every vendor relationship is a managed outsourcing of a piece of your business. Most teams sign vendor contracts, put them in a spreadsheet, and forget about them until renewal. Vendors know this. They price and serve accordingly. Treated like managed relationships instead, vendors are leverage, more capability per dollar than building in-house can deliver.

The vendor spectrum

• Commodity, many substitutes, low switching cost (e.g., most SaaS productivity tools)
• Differentiated, few substitutes, meaningful switching cost (e.g., your CRM, your ERP)
• Strategic, embedded in your business model; switching would take 6+ months and disrupt customers (e.g., payments processor, core hosting provider)

Each requires a different management posture.

Vendor inventory

First move: create a vendor inventory. Every vendor with recurring spend:

• Vendor name + category
• Annual spend
• Contract end date + auto-renewal notice period
• Owner (the internal person responsible)
• Criticality (commodity / differentiated / strategic)
• Last renewal date
• Renegotiation notes

Sort by annual spend. The top 20% of vendors by spend usually represent 80% of the opportunity for management, both cost reduction and performance improvement.

The renewal calendar

Every vendor contract has a renewal date. Miss the renewal notice window and you auto-renew for another year at whatever price they set. Standard failure mode:

The contract auto-renews 60 days before the anniversary. The vendor emails a 10% price increase 45 days before anniversary. You're already locked in.

Set calendar reminders 120 days before every vendor renewal. Review active usage, alternatives, and value at 90 days. Negotiate at 60. Decide at 45.

The quarterly vendor review

For top 20 vendors:

1. Spend vs, contract
2. Usage vs, contracted seats/volume
3. SLA performance (see SLAs + SLOs)
4. Account manager responsiveness
5. Product roadmap alignment
6. Alternatives emerging in the market
7. Renewal timeline + strategy

If a vendor doesn't warrant a quarterly review, you probably don't need the vendor.

Negotiating vendor contracts

At first signing

• Never sign list price on a software contract > $10K/yr, discounts are always available
• Always negotiate multi-year with a fixed rate card, not open-ended renewals
• Negotiate termination for convenience or at least for material breach
• Negotiate a price cap on future years (CPI + X% is the standard)
• Negotiate SLA commitments and service credits for misses
• If it's strategic, negotiate source-code escrow or data-export rights

At renewal

• Always have an alternative identified, even if you're not switching, it's your leverage
• Know your actual utilization, if you're using 60% of seats, that's the conversation
• Ask for flat renewal or better before accepting any increase
• Escalate if stuck, the sales rep has limits; the account manager or RVP has more room

Vendor consolidation

Annual exercise: map the overlaps in your vendor stack. Common patterns:

• Three project management tools, each with different team preferences
• Two data warehouses because of an acquisition that never rationalized
• Five analytics tools each covering partially overlapping use cases
• Unused seats on three different HRIS tools from past iterations

Consolidation saves money and, more importantly, reduces integration complexity.

Dependence risk

Some questions for your strategic vendors:

• What happens if they 3x their price at renewal?
• What happens if they get acquired by a competitor?
• What happens if they have a 2-week outage?
• What happens if their CEO changes strategy and sunsets the product?

For any answer that would materially hurt the business, you need a contingency, a second-source plan, a data-portability clause, or a reserve of the vendor's service in a local cache.

What good looks like

• Vendor inventory is current and owned by finance or ops
• Top 20 vendors get a quarterly review
• No contract auto-renews by accident
• Known dependencies have documented contingency plans

Related: Automate vs hire · SLAs + SLOs · Risk management