Vendor register
A vendor register you can answer questions from
Record each vendor with an owner, what it does and where your team uses it. Add the contract when someone finds it; the record is useful before then.
Northwind Analytics
Dashboards the commercial team runs their weekly review on
- Owner
- Maija Meikäläinen
- Used by
- CommercialWeekly review
- Annual value
- $27,800
- Ends
- Jan 20, 2027, renews automatically
- Notice
- 60 days
Matti Meikäläinen confirmed Northwind Analytics
Still used by Commercial for the weekly review
Start with the vendors you know about
Most registers stall because they wait for paperwork. Type the vendors you already know, then fill in contracts and costs as they turn up.
Name an owner
Give every vendor one internal owner, so there is always someone to ask whether it is still in use.
Say where it is used
Tag the teams and processes that depend on a vendor, like Commercial or the weekly review.
Leave unknowns empty
A missing value shows as not recorded, never as a zero, so you can see what is left to find.
What needs attention
Fenwick Data Labs has no internal owner
Nobody to ask whether it is still in use
No contract recorded for Fenwick Data Labs
Upload it when someone finds it
The notice window on Tessellate CRM order form 2026 has closed
It renews; the next chance is a term away
Notice on Northwind Analytics subscription is due in 24 days
Give notice or renegotiate before then
Built in
Keep the register true after day one
A register decays from the day it is made. The product turns that decay into a short list of things to fix.
Findings instead of audits
See vendors with no owner, contracts with no end date and records nobody has confirmed in a year.
Confirmation requests
Send a colleague one link to confirm their team still uses a vendor. They answer without an account.
Duplicate checks
Catch the same company entered twice under slightly different names before the totals double count it.
Outcomes
What changes when the register stays current
Questions get answered in a minute
Who owns this tool, who uses it and what it costs live on one page instead of in three people's heads.
Unused tools surface on their own
A colleague who says their team stopped using a vendor creates a finding you can act on before renewal.
Handovers keep their context
When an owner leaves, the vendor keeps its notes, contracts and history, and the finding asks for a new owner.
Comparison
Your vendor list, before and after
| Topic | Before | With the register |
|---|---|---|
| Where it lives | A spreadsheet one person maintains | One register the budget owner reads directly |
| Ownership | Unclear for older tools | One named owner per vendor, with a finding when it is missing |
| Is it still used? | Found out at renewal | Confirmed by the team that uses it, from one link |
| Missing data | Blank cells that look like zero | Shown as not recorded until someone fills it in |
Related
Use it with the rest of the product
Questions
Frequently asked questions
Do I need a contract to add a vendor?
No. A vendor with a name, an owner and where it is used is a complete record. A missing contract shows up as an opportunity to add one, not as an error.
Can each division keep its own list?
Yes. Budget areas group vendors under the leader who owns them, and a member scoped to an area sees only that area's vendors.
Where do the logos come from?
From the vendor's website domain, through a logo service and the site's own icon. Without a domain the register shows a letter mark.