
Choosing a supplier should help you make a decision.
Good procurement does not have to mean months of paperwork. A better process starts with the requirements that matter, compares meaningful differences, and narrows the field intelligently.
Start with the outcome, not the RFP
Before asking suppliers to respond to anything, get clear about the problem you are trying to solve.
That sounds obvious, but it is easy to skip.
A company might say:
“We need a new phone system.”
But that is already describing a solution.
The actual need might be:
- Customers are waiting too long to reach someone.
- Employees need to work from anywhere.
- Several locations need to communicate as one organization.
- The current system is unreliable.
- Customer information needs to flow between communications and the CRM.
Those are very different problems.
Once you understand the outcome, you can decide which capabilities actually matter.
That prevents the procurement process from becoming a contest to see which supplier can check the most boxes.
Not every requirement deserves equal weight
One of the easiest ways to create an RFP marathon is to treat every requirement as equally important.
They usually aren't.
Suppose you are comparing three suppliers and your requirements list has 80 items.
Supplier A meets 76.
Supplier B meets 72.
Supplier C meets 68.
It might look like Supplier A is clearly the winner.
But what if the four things Supplier A cannot do are the four things your organization needs most?
A simple checklist would point you toward the wrong answer.
Instead, separate requirements into groups such as:
Now the comparison starts reflecting the actual business decision.
Find the differences that matter
Most qualified suppliers in the same market will have a lot in common.
If you ask five cloud communications providers whether they offer voicemail, mobile applications, call forwarding, and conference calling, you will probably get five versions of “yes.”
Those questions don't help you narrow the field very much.
The useful questions are the ones that reveal meaningful differences.
For example:
How does the supplier handle an outage?
How difficult is the solution to manage?
What systems can it integrate with?
What happens when the organization adds another location?
What does implementation require from our internal team?
Who provides support when there is a problem?
Which capabilities cost extra?
What does the contract allow us to change later?
Those answers begin to show which supplier fits your organization—not just which supplier has the longest feature list.
Don't invite everyone to everything
More competition does not automatically create a better procurement process.
If there are 30 possible suppliers in a market, you probably don't need 30 proposals.
Research the market first.
Look at basic qualifications, geography, technical capabilities, certifications, contract requirements, customer fit, pricing models, and other obvious filters.
You might begin with 30 possible suppliers and discover that:
- 12 do not serve your locations.
- 5 cannot meet a critical technical requirement.
- 4 are not a fit for the size of your organization.
- 3 use a pricing or contract model you cannot accept.
For public-sector buyers, which suppliers already hold cooperative or government contracts that could provide an appropriate purchasing path?
Now you have six suppliers worth investigating.
After a few conversations, maybe three deserve serious consideration.
That is much more manageable than asking 30 suppliers to complete a 100-question RFP.
Talk to suppliers before asking them to write a book
There is value in structured written responses, especially when fairness, regulation, public procurement rules, or organizational policy requires them.
But conversation is often a much faster discovery tool.
Give qualified suppliers the problem and ask:
How would you solve this?
Their questions can be as valuable as their answers.
A strong supplier may identify a requirement you overlooked, challenge an assumption, explain a tradeoff, or show you a completely different approach.
Those conversations help you improve the requirements before you lock them into a formal procurement document.
The goal isn't to let suppliers write your requirements for you.
It is to understand the market well enough to ask better questions.
Compare tradeoffs, not just scores
There usually isn't one supplier that is best at everything.
One might offer the strongest technology.
Another might have the best local support.
Another might integrate more easily with your existing systems.
Another might cost less.
Another might give you more flexibility if your organization changes.
That means supplier selection is really about understanding tradeoffs.
This is where I use the same kind of thinking behind my Five-Star Method.
I want to understand the supplier or solution across five dimensions:
Resilience — What happens when something goes wrong?
Performance — Will it consistently deliver what we need?
Flexibility — Can it adapt as our needs change?
Operational Excellence — Can we realistically implement, operate, support, and manage it?
Business Value — Does the result justify the cost, effort, and risk?
The purpose is not to produce five perfect scores.
The purpose is to make the differences visible enough to make an informed decision.
Price matters. Total value matters more.
Price should absolutely be compared.
But the lowest quote is not necessarily the lowest-cost decision.
Imagine two suppliers:
Supplier A looks cheaper.
But Supplier A requires substantially more internal IT work, charges separately for implementation, has limited support, and requires another product to provide an important capability.
Supplier B includes those things.
The $90,000 solution might actually cost more.
A useful comparison looks beyond the quoted price and asks about:
The goal isn't simply to buy cheaply.
It is to understand what you are getting for what you are spending.
Sometimes you really do need an RFP
An RFP is not bad.
Sometimes it is exactly the right tool.
Government organizations, large institutions, grant-funded projects, regulated industries, and major purchases may have procurement rules that require a formal competitive process.
An RFP can also be useful when requirements are complex and suppliers need to respond to the same detailed questions.
The problem isn't the RFP.
The problem is using an RFP as the first step in understanding the problem.
Do the thinking first.
Research the market.
Identify the requirements that matter.
Find the meaningful differences.
Then, if a formal RFP is required, it becomes much more focused.
Instead of asking every possible question, you can ask the questions that will actually help distinguish one qualified supplier from another.
Procurement should narrow uncertainty
A good procurement process should make the decision clearer at each step.
Think of it like a funnel:
Start with the outcome.
Then:
Understand the requirements.
Research the market.
Remove suppliers that clearly don't fit.
Compare the meaningful differences.
Understand the tradeoffs.
Bring the strongest options forward.
Make the decision.
That is very different from sending a giant spreadsheet to everyone you can find and hoping the highest score reveals the answer.
The goal isn't less diligence. It's better diligence.
Avoiding an RFP marathon does not mean cutting corners.
It means putting the effort where it creates value.
Spend less time collecting answers to questions that won't affect the decision.
Spend more time understanding the outcome, validating important requirements, researching qualified suppliers, and comparing the tradeoffs that actually matter.
Good procurement isn't about creating the biggest process.
It's about creating enough structure to make a confident decision.
And sometimes, the smartest procurement strategy is not asking more suppliers more questions.
It's asking fewer, better questions of the right suppliers.
