The True Cost of Conflicted Technology Advice
Coy Wright
Founder, Lumerai Advisors
Nobody hires a conflicted advisor on purpose. That’s what makes this problem so
persistent.
The bias in technology advisory is almost never explicit. It doesn’t show up in disclosed
arrangements or flagged footnotes. It’s baked into business models — into how analyst
firms generate revenue, how consulting practices are structured, how expert networks
source their rosters. The organizations making the largest technology decisions of their
careers are, in most cases, operating on advice shaped by interests that are never
surfaced in the engagement letter.
I’ve watched this play out from multiple vantage points: as a technology executive
making the decisions, as an industry advisor observing where they go wrong, and as
someone who spent years inside the systems that produce the advice. The cost is real.
The mechanisms are specific. And the fact that most organizations have no way to
measure it doesn’t mean it isn’t happening.
How the Conflicts Actually Work
Analyst firms — the Gartners and Forresters of the world — derive substantial revenue
from the vendors they evaluate. Research sponsorships, paid briefings, event
participation fees, custom inquiry access. None of that necessarily produces a false
recommendation. But it shapes what gets studied, which vendors appear in
comparisons, and how risks and limitations are framed. The analysis that reaches a
technology executive is downstream of commercial relationships that executive never
sees.
The consulting firms have a related but more expensive problem. McKinsey, Deloitte,
KPMG — these are not bad organizations, but their economics are not aligned with
independent technology judgment. The advisory fees are modest relative to the
implementation revenues those recommendations generate. When the same firm
advises you to modernize your ERP and then bids to deliver the modernization, the
advice is not separable from the revenue opportunity it creates. The account team isn’t
corrupt; the structure is just compromised.
Expert networks occupy a different category. The pitch is compelling: get access to
executives who’ve done what you’re trying to do. In practice, the quality control is thin.
Someone who held a CIO role five years ago, available for a 45-minute call with no
ongoing accountability, no organizational context, and no incentive beyond the hourly
fee — that is a long way from trusted advisory. It’s a useful data point at best.
Organizations consistently confuse the two.
None of these players are behaving badly within their own business models. That’s
actually what makes the problem durable. The conflicts are structural, not ethical.
Pointing that out is not a criticism of individuals. It’s a description of a market that has
not produced what it pretends to produce.
The Junior Leverage Problem
There’s a second failure mode in traditional consulting that gets less attention than bias
but probably destroys more value.
The economics of major consulting firms require that senior partners stay thinly spread
across many engagements while the actual work is done by analysts and associates
who are, by definition, early in their careers. This is not a secret — it’s the model. It
works reasonably well for financial modeling, market sizing, and process
documentation. It works poorly for the technology decisions that actually matter most.
A 27-year-old with two years of consulting experience cannot tell you whether a
vendor’s implementation partner has the depth to deliver a large-scale SAP
transformation. They can’t read a cybersecurity posture and distinguish genuine risk
management from compliance theater. They can’t assess whether the IT leadership
team of an acquisition target has the operational credibility to execute an integration on
a private equity timeline. These aren’t things you can develop by reading about them.
They come from having been accountable for the outcome under real conditions — from
having your career on the line when the go-live goes sideways.
Organizations often accept the output of junior teams because the engagement is
staffed by recognizable firm brands and the deliverables look thorough. Slide quality is
not a proxy for judgment quality. The two are frequently inversely correlated.
What Bad Advice Actually Costs
The direct costs are visible in the wreckage: ERP transformations that deliver a fraction
of projected ROI, AI programs that generate impressive demos and negligible
operational impact, cybersecurity investments that check compliance boxes while
leaving material risks unaddressed. These failures are common enough that most
technology executives have lived through at least one. They tend to be attributed to
execution problems rather than advisory failures, which means the root cause doesn’t
get fixed.
The indirect costs are harder to measure but likely larger. When a technology initiative
fails publicly, the organizational credibility damage extends well beyond the project. The
CIO or CISO whose reputation takes the hit. The board that loses confidence in the
technology investment thesis. The talent that leaves because they were part of
something that went badly wrong. These are real costs that don’t show up in the
post-mortem.
The opportunity cost is the one that keeps me up at night. Every dollar consumed by a
vendor-mandated upgrade that didn’t need to happen is a dollar that didn’t go toward
something that could have. The AI capabilities a competitor built while your budget was
tied up in a migration. The operational technology investment that would have reduced
costs 20% but kept getting deferred. The grid modernization project that would have
changed your competitive position in a market that’s moving faster than your planning
cycle.
These costs are invisible because they’re counterfactual. Nobody writes a post-mortem
on the things that didn’t get built. But they accumulate, and the organizations that
consistently make better technology decisions compound those advantages over time in
ways that become very hard to close.
What PE Firms Are Getting Wrong
Private equity deserves its own section here because the stakes and the failure modes
are specific.
Technology due diligence in most PE transactions is still treated as a technical audit
rather than a strategic risk assessment. The question being answered is “is the
technology functional?” when the question that actually matters is “will this technology
create or destroy value across the hold period?” Those are different questions with
different answers and they require different expertise to assess.
The integration execution risk in platform acquisitions is routinely underweighted.
Bolt-on technology assessments frequently miss the practical complexity of connecting
systems across entities with different ERP versions, different data models, and IT teams
with competing priorities. These are not obscure failure modes. They’re common,
well-documented, and still routinely missed by advisory teams that have never had to
manage them.
The talent dimension gets almost no attention until it’s too late. Whether an IT
organization can absorb an integration, a transformation, or an AI initiative on the
timeline the thesis requires is a human capital question as much as a technical one. It
requires someone who has actually built and managed these teams to assess
accurately.
When the technology thesis underperforms — and in many PE deals, it does — the
standard explanation is execution. That’s usually fair. What it misses is that execution
failure was predictable at the point of diligence by someone with the right vantage point.
The advisory model that produces a 40-page technical audit is not the same thing as
the advisory model that gives you an honest answer on whether the technology bet will
pay off.
What Independence Actually Requires
Independence is easy to claim. It’s worth being specific about what it actually requires.
A structurally independent technology advisor takes no vendor revenue. No referral
fees, no implementation partnerships, no event sponsorships, no funded research
relationships with companies whose products might appear in a recommendation. This
eliminates the most pervasive form of advisory bias, which is the kind that operates
below the level of conscious awareness in even well-intentioned advisors.
A structurally independent technology advisor has no implementation arm. The moment
advisory and execution are sold by the same organization, the advice is shaped by the
revenue opportunity it creates. This is not a character judgment. It is a structural reality
that no policy, ethical wall, or good intention can fully overcome.
And the advisors themselves need to have actually done the work — not studied it, not
consulted on it from the outside, but held accountability for it inside an operating
organization. The knowledge that comes from managing a large-scale implementation
that’s going sideways at 11pm on a Sunday is not accessible from the outside. It is the
kind of knowledge that changes how you read a vendor proposal, how you assess an
implementation timeline, and what questions you think to ask before a deal closes.
That combination — structural independence and operational credibility — is what
Lumerai was built around. Not as a marketing claim, but as operating constraints with
real economic consequences. We take no vendor revenue. We have no implementation
practice. Our founding partners have held the roles, run the programs, and lived the
outcomes that our clients are navigating.
The Compounding Effect
Technology decisions compound. The organizations that make consistently better calls
over a decade don’t just avoid bad outcomes — they build organizational capability,
technology infrastructure, and institutional knowledge that becomes genuinely hard for
competitors to replicate.
The inverse is also true. Organizations that spend a decade on vendor-driven upgrade
cycles, failed transformations, and advisory relationships that optimize for the advisor’s
interests rather than the client’s fall further behind with each cycle. The gap isn’t just the
cost of the bad decisions. It’s everything that didn’t get built while those decisions were
being made and unwound.
Getting independent, operator-credentialed advice on the decisions that matter most is
not expensive relative to that math. It’s one of the better-returning investments a
technology organization can make. The hard part is that the return is mostly
counterfactual — measured in the things that didn’t go wrong and the opportunities that
didn’t get missed. Those tend to be invisible right up until you’re sitting across the table
from a competitor that made better calls than you did.
—
Coy Wright is the Founder of Lumerai Advisors, a practitioner-led independent technology advisory firm,
and VP of Energy, Utilities & Resources at Rimini Street. He has served as CIO and technology executive
across energy, utilities, and infrastructure, and advises PE firms and enterprise leadership teams on
technology strategy, diligence, and governance.