Six months after the AWS contract renewal you remember running a careful comparison, but you can't find the file. Was it Drive? Email? Someone's local downloads? The original analyst left in March. The proposal review for the renewal restarts from zero. This is the cost of not having a vendor library — every cycle is a fresh hand-curated comparison, and institutional knowledge evaporates with people.
What a vendor library actually is
A vendor library is the persistent layer underneath your individual vendor evaluations. Whereas a single comparison answers "who's better, A or B, on this specific RFP?", the library answers:
- Which vendors did we evaluate in the last 24 months — and what was the verdict?
- Which vendor's SLAs improved between v1 and v2 of their proposal?
- Which contracts expire in the next 60/30/14 days, and which need a renewal review now?
- Across all our reviews, which red flags appeared most often (so we can pre-empt them in future RFPs)?
Without the library, those questions are unanswerable. With it, they're one query away.
The minimum schema
A useful vendor library captures at least:
- Vendor — canonical name, with aliases ("AWS", "Amazon Web Services", "Amazon" all map to one entity).
- Comparisons featured in — which evaluations this vendor was part of.
- Latest score — most recent scorecard total.
- Contract end date — when does the current contract expire? Drives renewal alerts.
- Notes — context that doesn't fit elsewhere ("CFO prefers them because their CFO worked with our CTO").
The auto-detection problem
The hardest part of building a vendor library by hand is keeping vendor identities consistent. "AWS_Proposal_v2.pdf" and "amazon-msa-2025.pdf" should map to the same vendor. Manually this requires discipline; automated, it requires a normalisation function that strips version markers, dates, and document-type words, then compares canonical names. POCsheet does this automatically — every comparison enriches the library.
What the library unlocks
Once a vendor library exists, three workflows that were previously impossible become routine:
- Diff between vendor versions. When a vendor sends v2 of their SLA, comparing it against v1 takes 30 seconds, not 3 hours.
- Cross-comparison queries. "Which vendors in our library have liability caps under 1× annual fees?" becomes a single search.
- Calendar-driven renewals. Contracts surface 60 days before expiry. Negotiation starts proactively, not in panic.
Getting started
Most teams start their library accidentally — every comparison they run gets archived automatically. By comparison number 5-10, the library has compounding value. POCsheet's free plan includes the vendor library and lets you backfill your existing comparisons in one click.