Search for vendor management and you will find third-party risk frameworks, supplier governance committees, maturity models, and a great deal of writing about ERP modules.
None of it is wrong. All of it is written for a company with a procurement department, a compliance function, and a budget that assumes both.
If you are five people, or twenty, you have the same underlying problem and none of that apparatus. This is the version for you.
What vendor management means when you are five people
Strip away the frameworks and it comes down to one thing: a single place that holds everything about a supplier — current contact information, current qualification status, and current performance history — so that anyone on your team, at any moment, knows who they should be buying from.
That is the whole discipline at this scale.
Notice what it is not. At five people, vendor management is not a compliance function. Nobody is auditing you. There is no committee. It is an information-sharing function — the mechanism by which what one person knows becomes what everyone knows.
Everything else in this guide follows from that.
The four things that actually go wrong
Before the process, the diagnosis. In small teams, vendor problems take four recognizable forms.
1. There is no record of who actually performed. Everybody has opinions about your vendors. Nobody has written them down. So the decision gets made by whoever happens to be in the room, based on whatever they happen to remember.
2. You cannot find the right vendor quickly once the list gets big. Fifty vendors in a spreadsheet is a searchable document. Two hundred spread across email, a shared drive, and three people’s phones is not.
3. Qualification and compliance drift. Insurance lapses. Licenses expire. Certifications go stale. Nobody notices until the moment it matters, which is always the worst possible moment.
4. Institutional memory walks out of the door. One resignation, and a decade of hard-won judgment about who is good and who is trouble leaves the building.
The real risk: several buyers, one vendor pool
Here is the pattern that causes the most damage, and it has nothing to do with company size.
The businesses that suffer worst are not the ones spending the most. They are the ones where several people buy independently against the same pool of vendors.
Five locations, five managers, five sets of go-to contacts. Each manager is doing a perfectly reasonable job. Collectively, the results are bad:
- No vendor receives enough volume from you to care much about the relationship
- Some managers negotiate well and some do not, and nobody can see the difference
- The same vendor is charging your company different rates in different places
- Nobody has a view of the whole, so nobody can fix any of it
Consolidate that spend onto one or two properly qualified partners and both sides gain. You get better pricing through volume, better service, and faster response when something breaks. They get a relationship worth protecting. It is one of the genuinely rare win-wins in purchasing.
And it is completely unavailable to you until the vendor information sits in one place where everyone can see it.
If this describes you, vendor management is not an administrative nicety. It is the thing standing between you and materially better pricing. Property management firms hit this first and hardest. Construction is close behind. So is any business where more than one person is authorized to spend money.
A status is only useful if it travels
Small section, large consequence.
Vendors move through states. New. Preferred. Caution. Do not use. Recording that state is easy. Making it useful is the part that gets missed.
Consider: you downgrade a vendor to caution on Monday, for good reason. On Tuesday, a colleague in another office raises a purchase order with them, because nobody told her.
You did not have a vendor management system. You had a document.
This is the entire difference between a list and a system — not features, not reporting, but whether a change made by one person reaches the next person to act on it, before they act. If a status change has to be communicated by email to take effect, sooner or later it will not be communicated.
The loop
The organizing idea behind everything below, and it is simple enough to state in one line:
Rate the vendor when the job closes, the record builds, and you choose by evidence on the next project.
Every practice in this guide is either an input to that loop or a consequence of it. The reason it works is that it pays back immediately. You are not entering data for a hypothetical future audit. You are entering it so that next quarter’s decision takes ten minutes instead of an afternoon of asking around.
The four practices
Building your approved list
The foundation. An approved vendor list is not a contact list — it is a set of decisions you have already made, so that you are not making them under pressure.
The key distinction: approved means qualified to bid, not awarded. Getting on the list earns a vendor an invitation. Winning the work is a separate decision.
Build it by category rather than by habit. List every category your business needs covered, count your qualified options in each, and work on the gaps. One contractor in a category is not a list; it is a dependency.
Qualification runs in two steps: a fast background check — real website, business email domain, registered company, evidence of actual work — and then a qualification form covering business information, key people, references, credentials, and scale. Whether a vendor bothers to complete that form tells you nearly as much as what they write on it.
Full guide: How to Build an Approved Vendor List
Scoring performance
The practice that makes the loop turn, and the one most often skipped.
Score at the midpoint as well as at the end for anything of length, because performance changes shape. Use a calendar cadence for perpetual vendors who never finish — quarterly or twice a year. Collect from everyone who dealt with the vendor, not just the buyer, and run an average, because one person’s account of one bad day is an anecdote rather than a record.
Six criteria are enough: price, quality, schedule, communication, adaptability, and ease of doing business. Ask for a star rating plus one or two sentences — stars get submitted, comments explain the outliers.
Full guide: The Vendor Scorecard
Choosing between bids
Quotes rarely arrive comparable. One includes materials, another does not. One is a lump sum, another is unit rates. One assumes you are providing access equipment. Comparing them as they arrive is how the cheapest bid turns out to be the most expensive.
Level them first — normalize the scope, the exclusions and the assumptions, and only then compare price. Then weight the non-price criteria deliberately, rather than letting price decide by default.
When your work is recurring rather than competitive
Not every business runs competitive bids. If your vendor work is recurring trades across multiple sites — the same plumber, the same landscaper, the same cleaner, year after year — you have exactly the same information problem without ever writing a request for proposal.
The list, the statuses and the performance record all still apply. The bidding does not. Use it on its own, or alongside your bids.
When a spreadsheet is genuinely enough
Let us be honest about this, because most articles on the subject will not be.
For one or two people, a spreadsheet works. You can manage a vendor list in Excel perfectly well. If that is your situation, build it, keep it current, and spend your attention elsewhere.
It breaks at four identifiable points.
More than a couple of people editing it. Everyone tinkers with a shared spreadsheet. Lock it down and it stops being updated; leave it open and it drifts out of accuracy within months.
A field team that needs it away from a desk. The moment someone has to look up a qualified vendor while standing in a mechanical room, a file on a shared drive is the wrong tool.
No permissions. There is no way to separate the people who need to read the list from the people who should be allowed to change it.
No reminders. Credential expiry gets discovered rather than anticipated, which is much the same as not tracking it at all.
And the structural limit, which is the sharpest way to put it: a spreadsheet is good at holding a contact list. It is poor at holding credentials and performance history. Those two things are the entire reason vendor management is worth doing.
What to look for in a tool
Useful even if you end up choosing something else.
First, understand what goes wrong at the top of the market. Enterprise vendor management systems routinely run into six figures. They typically arrive as a module bolted onto a larger ERP, which means you need the ERP first. Implementation is slow, and a substantial share of the cost is consultants doing the launch rather than software doing the work.
For a company with an established ERP and a procurement team, that can be entirely rational. For a business of five to twenty people, the whole category is mis-sold — you are being quoted for machinery built to solve a problem you do not have.
So the criteria for a small team are different:
- Works without an ERP behind it. If it requires one, it is not for you.
- Starts without an implementation project. You should be able to get value from it in an afternoon.
- Low enough barrier that you can test it on real data before committing budget or time.
- Holds qualification and performance, not just contacts. Otherwise you have bought an address book.
- Has permissions, so the record survives contact with the whole team.
- Works on a phone, for the people who are not sitting at a desk.
The mistake people make in week one
The failure mode is not entering too much information, or too little. It is not committing.
What happens is this: half the vendor information goes into the new system, and half stays where it always was — in email threads, in attachments, in a folder on somebody’s desktop, on paper in a drawer. A half-populated system is worth less than either option chosen wholeheartedly, because now nobody trusts it and everybody checks both places.
The value comes entirely from concentration. Reviews, qualifications, contacts, credentials and the history of every project a vendor has worked on, in one place, so that looking someone up answers the question completely rather than partially.
So the advice for the first week is unglamorous: put everything in. Including the vendors you are unsure about, including the history you half-remember, and including the ones you have decided not to use again — especially those.
Where to start
If you are starting from nothing, in order:
- Write out your categories and count qualified options in each. Work the gaps.
- Pick one place for vendor records, and move everything into it.
- Set statuses on the vendors you already use.
- Start scoring at the end of the next job you complete. Not retrospectively — from now.
- Review in six months. By then you will have enough record to make one decision by evidence rather than by memory, which is the point at which this stops feeling like admin.
PowerRFP is free RFP software with vendor management built in. You can add your vendors and their contacts with no limit on the free plan, and manage your vendors alongside the bids you run. Create a free account.