Why the Best Technology Advisors Won't Recommend Their Own Products

There is a simple test for the quality of technology advice: can the advisor recommend doing nothing?

Not “we recommend a phased approach” or “we suggest starting with a pilot.” Genuinely nothing. Can the person advising you look at your situation, assess your needs, and conclude that the best course of action is to not spend money on the thing they are being paid to advise you about?

If the answer is no - if the advisor’s business model requires you to buy, build, or transform - then what you are receiving is not advice. It is a sales process with better slide decks.

The Structure of Conflict

Technology advisory has a structural conflict problem that is rarely discussed openly. The vast majority of technology advisors derive revenue from one or more of the following: selling technology products, implementing technology products, or maintaining ongoing relationships with technology vendors who pay them for referrals, certifications, or partner status.

This is not a secret. It is the industry’s business model. And it shapes every recommendation that comes out of it.

When a consulting firm recommends a cloud migration, it is worth asking whether they have a partnership with the cloud provider. When a systems integrator recommends a platform, it is worth asking whether they are certified - and compensated - by that platform’s vendor. When an advisory firm recommends a “comprehensive AI transformation,” it is worth asking who will be engaged to deliver it.

The answers to these questions do not necessarily invalidate the advice. But they contextualise it. They reveal the invisible hand that shaped the recommendation before it reached your desk.

What Independence Actually Means

Independence in technology advisory means something specific. It means the advisor has no financial relationship with any technology vendor. No partnerships, no referral fees, no certifications that depend on selling a specific product, no revenue that increases when you buy more technology.

This is a harder standard than it appears. The technology industry is built on ecosystems of mutual benefit. Vendors, consultants, integrators, and resellers form interlocking relationships where everyone’s revenue depends on everyone else’s sales. Stepping outside this ecosystem means forgoing significant revenue streams. Most firms choose not to.

The result is that truly independent technology advice is rare. Not because independence is technically difficult, but because it is commercially inconvenient.

The Advisor’s View vs. The Vendor’s View

The difference between an independent advisor and a vendor-aligned one becomes visible in the recommendations they produce.

A vendor-aligned advisor sees your organisation through the lens of their products and services. They assess your “readiness” for their solutions. They identify “gaps” that their offerings fill. Their roadmap leads, inevitably, to their engagement. This is not dishonesty - it is perspective. When your toolkit is a hammer, the assessment will find nails.

An independent advisor sees your organisation through the lens of your objectives. They assess what you are trying to achieve, what is actually preventing you from achieving it, and what the most effective intervention would be - whether that is technology, process change, organisational restructuring, or doing nothing at all.

The independent advisor can recommend a competitor’s product. They can recommend open-source tools. They can recommend that you hire differently, restructure a team, or fix your data governance before touching AI. They can recommend waiting. They have no revenue reason to prefer any of these options over the others.

This is not a marginal difference. It is the difference between advice that serves the advisor and advice that serves the client.

The Cost of Conflicted Advice

The cost of conflicted technology advice is difficult to measure precisely, because it manifests as opportunity cost and misdirected investment rather than visible failure.

It looks like the AI programme that consumed eighteen months and significant capital before being quietly wound down. It looks like the cloud migration that was technically successful but delivered none of the promised cost savings. It looks like the digital transformation that transformed the technology stack but not the business outcomes.

In each case, the technology worked. The implementation was competent. The advice was the problem - not because it was wrong about the technology, but because it was wrong about whether the technology was the right solution to the actual problem.

Organisations rarely audit their advisory relationships with this lens. They evaluate whether the project was delivered on time and budget. They do not evaluate whether the project should have been undertaken at all, or whether the scope was shaped by the advisor’s interests rather than the client’s needs.

What to Look For

If you are evaluating a technology advisor - whether for AI strategy, cloud architecture, digital transformation, or any other significant technology decision - there are straightforward questions to ask.

Does the advisor sell technology products? If yes, their recommendations will be shaped by what they sell. This is not speculation. It is how incentives work.

Does the advisor have vendor partnerships, certifications, or referral arrangements? If yes, ask how these relationships influence their recommendations. The answer will be revealing.

Does the advisor’s revenue increase if you spend more on technology? If yes, their advice will tend toward more spending. Not because they are dishonest, but because they are human, and incentives shape behaviour.

Can the advisor provide examples of recommending against a technology investment? If they cannot, ask yourself whether their assessment of your situation is advice or advocacy.

The Principle

The principle underlying all of this is not complicated. It is the same principle that governs financial advice, legal counsel, and medical practice: the advisor’s interests should not conflict with the client’s interests. When they do conflict, the quality of advice degrades. Not always dramatically. Often subtly. But reliably.

Technology decisions are now material to most organisations’ strategy, risk profile, and competitive position. The standard of advice should match the stakes. That means independence - not as a marketing claim, but as a structural reality.

The best technology advisors will not recommend their own products, because they do not have products to recommend. What they offer instead is something considerably more valuable: an honest assessment of what you actually need.