Vendor-Neutral Does Not Mean Nobody Gets Paid

“Vendor-neutral” sounds good in a proposal. It is also easy to say and hard to test.

An advisor can have relationships with hundreds of providers and still run a disciplined, buyer-first process. Another advisor can have access to the same market and steer every conversation toward the few providers they know best. The label does not tell you which one is sitting across the table.

And yes, the advisor gets paid. They should. Good discovery, market research, contract review, negotiation, implementation support, and renewal work require time and expertise.

The buying question is not whether money changes hands. The question is whether you understand the economics, the available options, and the process used to reach the recommendation.

That is what you should test before you accept a shortlist.

Start with the compensation model

Technology advisors can be paid in several ways. A buyer may pay a project fee or retainer. A provider may pay compensation after a customer purchases an eligible service. A reseller may earn margin between its cost and the customer price. Some engagements combine more than one model.

None of those structures automatically makes the advice good or bad. Each creates different incentives and different questions.

A client-paid advisor may still prefer a familiar vendor because it makes delivery easier. A provider-paid advisor may do excellent work and remain involved for years. A reseller may have deep technical capability but a narrower product catalog. A large consulting firm may appear independent while maintaining major alliance relationships.

Do not guess from the title on the business card. Ask how the engagement works.

A clear answer should cover:

Who pays the advisor
What event creates compensation
Whether payment differs by provider, product, term, or transaction size
Whether the buyer will also pay a fee
Which implementation, support, and renewal work is included

You do not need the advisor’s income statement. You need enough information to understand the incentive around your decision.

If the answer is vague, defensive, or buried in a long explanation, keep asking.

Question 1: How are you paid if we choose a provider?

Ask this early, not after the shortlist is finished.

A useful answer should identify whether the advisor is paid by you, by the selected provider, through a distribution relationship, through a resale margin, or through some combination. It should also explain whether the commercial model changes when you choose a different option.

The follow-up matters:

Would your compensation be materially different if we selected provider A instead of provider B?

That difference does not automatically disqualify the recommendation. It tells you where more scrutiny belongs.

If one option creates stronger economics for the advisor, ask the advisor to show why that option still wins on your requirements. Good recommendations can survive that conversation. Weak ones tend to fall back on relationship language, vague claims about support, or a demo everyone happened to like.

Question 2: Which options are actually in scope?

Market access is not the same as market coverage.

An advisor may have relationships with many technology providers but evaluate only a small group for your project. That can be completely reasonable. Nobody needs 40 UCaaS demos or 25 MDR proposals. A serious process narrows the field.

You need to know how it was narrowed.

Ask:

Which providers can you represent or source?
Which providers did you consider for this project?
Which options were removed, and why?
Are there credible providers outside your commercial relationships?
What happens if an outside option fits us better?

The answer should connect the shortlist to your requirements, not to the size of a partner directory.

Catch Advisors publicly describes relationships with major technology distribution platforms and a broad technology partner ecosystem. That access is useful because it expands the option set. It does not remove the need to document why a few providers made the final list.

More logos do not equal more neutrality. A defensible filtering process does.

Question 3: What evidence drove the recommendation?

A recommendation should have a trail.

Start with the requirements your team approved. Then connect each important requirement to evidence from the provider, the contract, a reference, a technical test, a pilot, or your own operating data.

For a network decision, that might include serviceability, route details, diversity, installation risk, support coverage, and contract terms. For a security service, it could include detection coverage, response authority, integration work, escalation evidence, and retained internal workload. For UCaaS or CCaaS, it may include call flows, licensing, migration effort, support history, integrations, reporting, and number control.

You should be able to see why the recommended option won and what it did not win.

Use a scorecard, but do not let the math become theater. Weight the few criteria that can change the decision. Record nonnegotiable conditions separately. Attach evidence to the score.

Our IT vendor scorecard guide provides a broader structure. For this decision, add two columns:

Field	What to record
Evidence	The document, test, reference, or data supporting the score
Commercial relationship	How the advisor can source the option and whether compensation applies

This does not turn procurement into an investigation. It keeps the buying record honest.

Sometimes the right answer is to keep the current service, correct the license mix, renegotiate a term, fix adoption, or delay a purchase until the requirement is clear.

Ask the advisor directly:

Under what conditions would you recommend no purchase, a renewal with the incumbent, or an option you cannot sell?

Listen for an actual decision rule.

“We always do what is best for the client” is a promise. It is not a process.

A stronger answer sounds like this: If the incumbent meets the approved requirements, switching costs erase the expected benefit, and the buyer can correct the contract risk, we will recommend staying. Or: If no represented provider meets the security boundary, we will document the gap and widen the search.

That is testable. It gives your steering group something to hold the advisor to when the deal gets complicated.

The ability to say “do not buy this” matters because many advisory models earn more when a transaction happens. Pretending that incentive does not exist helps nobody. Defining a no-purchase gate does.

Question 5: What happens after the contract is signed?

Compensation and responsibility should be discussed together.

If a provider pays the advisor over time, what ongoing work does the advisor perform? If the buyer pays a project fee, where does the project end? Who owns implementation coordination, escalation, billing disputes, adoption reviews, contract changes, and renewal planning?

Get specific:

Who attends implementation meetings?
Who tracks provider commitments and open issues?
Who escalates when service or billing goes sideways?
How often will performance and spend be reviewed?
When does renewal planning begin?
What work requires a new fee or scope?

A commercial relationship can support long-term service. It can also become passive revenue while the buyer does all the work. The contract title will not tell you which one you are getting.

Write the operating expectations down.

Put the disclosure in the decision record

Do not leave this conversation in someone’s meeting notes.

For each finalist, record:

Decision field	Buyer record
Advisor payment model	Client fee, provider compensation, reseller margin, or combination
Option scope	Providers considered, excluded, and outside current relationships
Selection evidence	Requirements, scores, tests, references, and contract findings
Conflict review	Known commercial differences or delivery preferences
No-purchase gate	Conditions that support staying, delaying, or choosing an outside option
Ongoing role	Implementation, escalation, optimization, and renewal responsibilities

Have the advisor confirm the record. Then let procurement, legal, finance, or the executive sponsor decide whether any item needs deeper review.

This is not a legal opinion or a claim that one compensation model is required. Contract, disclosure, procurement, and regulatory obligations vary. Use qualified counsel when the situation calls for it.

The operational standard is simpler: a reasonable buyer should be able to understand who gets paid, which options were considered, and why the recommendation won.

Neutrality is a behavior

A vendor-neutral advisor does not need to be commercially disconnected from every provider. That would make large parts of the technology channel impossible to use.

The advisor needs a process that can withstand daylight.

Can they explain the economics? Can they show the option set? Can they connect the recommendation to evidence? Can they tell you when not to buy? Will they stay accountable after signature?

Ask those five questions before you accept the shortlist. If the answers are clear, document them and move forward. If they are not, the “vendor-neutral” label has not earned much value yet.

Catch Advisors helps IT leaders evaluate providers, contracts, and renewal risk from the buyer’s side of the table. If you have a major technology decision approaching, request a free IT assessment and bring the five questions with you. You should ask them of us too.