The Advisor and the Vendor

The Decision Before the Decision

The most consequential decision inside a serious technology programme is often not the one that appears on the agenda. It is not the choice of platform, the shape of the architecture, or the sequencing of the roadmap. It is a quieter decision that precedes all of these and shapes every one of them, the decision about whose judgement the organisation has chosen to trust.

That decision is made long before the request for proposal is drafted. It is made in the conversations that fill the months before a board formally approves a programme, in the informal briefings that shape the language a chief executive uses when introducing the subject, in the analyst reports that quietly frame the shortlist, in the vendor demonstrations that establish the vocabulary of the whole exercise. By the time a formal evaluation begins, the intellectual perimeter of the decision has usually already been drawn. The remaining question is which supplier will occupy it.

This is not a scandal. It is the natural consequence of how modern technology decisions are organised. Executive teams face problems whose scale exceeds their internal expertise, on timelines that do not allow leisurely study, in domains where language moves faster than understanding. They reach, reasonably, for the people who appear to know. Those people are almost always attached, in one way or another, to an economic outcome. The purpose of this essay is not to complain about that arrangement. It is to describe it accurately, and to suggest why a specific and older kind of counsel, independent judgement, has quietly become one of the harder resources for a board to find.

A Room of Interested Voices

Consider the ecosystem as it actually exists today. A senior team weighing a significant technology investment will typically encounter several categories of expert voice, each competent, each necessary, and each shaped by a different economic reality.

There are the software vendors themselves. They build the products on which contemporary organisations depend, and the best of them do so with real conviction and long institutional memory. Their commercial model, however, rests on licence revenue and expansion within an installed base. They know their product intimately and their competitors somewhat less so. They cannot easily recommend that a client do nothing, because doing nothing is not a category their business model recognises.

There are the system integrators and implementation partners. Their contribution is often decisive, because complex platforms do not deploy themselves, and the difference between a well run implementation and a poor one can be measured in years of institutional pain. Their economics, however, are tied to billable days. An engagement that concludes in eight weeks with the recommendation to postpone the programme by a year is not, from their point of view, a successful engagement. It is a cancelled one.

There are the large management consultancies. Their strength is method, framework, and access to comparative data across many clients. Their weakness, from the point of view of a client seeking counsel, is that their commercial engine is powered by follow-on work. The strategy phase, however honest, exists in a system whose next phase is the design, then the build, then the transformation programme, then the managed service. A finding that argues against the whole trajectory is possible, but it is not what the model is optimised to produce.

There are the specialist boutiques and independent consultancies, some of which do excellent work and hold themselves to strict standards. Even here, most operate a model in which the initial engagement is a bridge into a longer relationship. The economics are gentler than at the largest firms, but the underlying gravity is the same.

There are the analysts, whose published quadrants and reports shape shortlists for entire industries. Their independence is asserted with care, and in many cases defended honourably. It is also worth understanding that their revenue models rest, in part, on subscriptions from the vendors they cover, on advisory work with those same vendors, and on paid inquiry from clients who tend to be evaluating one of them. The analyst community is a genuinely important part of the ecosystem. It is not the same thing as a neutral witness.

There are the internal teams, who bring the deepest knowledge of the organisation itself. Their incentives are almost never financial in the vendor sense, but they are political and professional. A chief information officer who has championed a particular platform for five years does not approach the question of its replacement with the detachment of a stranger. A head of digital who has just hired a large team around a specific stack has a legitimate stake in that stack continuing to matter. These are not corruptions of judgement. They are the ordinary weight of having a career.

Expertise and Independence

Each of these voices contributes something the others cannot. A serious technology decision requires all of them at various points. This essay does not question them. It only observes that expertise and independence are two different qualities, and that the confusion between them is one of the more common quiet regrets in boardrooms.

Expertise is the accumulated knowledge of a domain. Independence is a structural condition of the person offering counsel. An expert with strong economic interest in a specific outcome is still an expert. Their expertise remains real. What has changed is not the quality of what they know but the direction in which their judgement will bend under pressure. Every human judgement bends under pressure. Independence does not eliminate this. It changes the direction of the bend.

The value of independence, in this specific professional sense, is not that the independent voice is smarter than the vendor, or wiser than the integrator, or more insightful than the analyst. It is that the independent voice is free to ask a different set of questions. It can ask whether the problem the room is discussing is actually the problem that should be solved. It can ask whether the timing is right. It can ask whether the organisation is ready. It can ask, when appropriate, whether the honest answer is to do nothing at all. These are not superior questions. They are structurally difficult questions for anyone whose income depends on the answer going a particular way.

Platforms as Organisational Containers

The reason this distinction matters more today than a decade ago has less to do with technology and more to do with what technology has become inside organisations. Twenty years ago, an ERP selection was a technical exercise with organisational consequences. Today, an ERP selection is an organisational exercise with technical consequences. The centre of gravity has moved. The same is true of enterprise commerce platforms, of customer relationship systems, of knowledge platforms, and above all of the current wave of artificial intelligence.

A modern enterprise platform is no longer a piece of software the organisation buys. It is a container into which the organisation pours a version of itself. It encodes decisions about how the business will operate, how work will be divided, which functions will hold authority, which processes will be standardised across regions, which exceptions will be tolerated, which data will become authoritative, and which parts of the past will quietly be left behind. A decision of that scale is not, in any useful sense, a purchase. It is a reorganisation dressed as procurement.

Where the Independent Question Lives

The stakes of such decisions are the reason the question of counsel deserves so much attention. It is worth walking through several realistic situations, of the kind executive teams encounter in a given quarter, to see where the distinction between the interested expert and the independent advisor becomes practically important.

A retailer with a mature but ageing commerce platform is under pressure from its board to modernise. The incumbent vendor has proposed an ambitious replatforming programme. A competing vendor has proposed a leaner alternative built on a newer architecture. Two integrators have made bids. An analyst report suggests both platforms are viable. Every party in the conversation has an interest in the programme going ahead in some form. The question no participant in the room is structurally free to raise is whether the platform is actually the constraint. It may be that the organisation's difficulties in commerce are the result of merchandising decisions, service model decisions, or organisational design decisions that no platform will repair. That question does not disappear because it is inconvenient. It waits, and reappears eighteen months into the programme.

A financial services group is considering the introduction of artificial intelligence into its customer service function. Every vendor in the market has a compelling demonstration. Every integrator has a reference implementation. The internal team, keen not to appear behind, has begun to speak in the vocabulary of the vendors. A useful independent question at this moment is not whether the technology works. It is whether the organisation's current service model is one that should be scaled with new technology, or one that should be redesigned first. That question is uncomfortable because it implies work that produces no visible artefact for several quarters. It is also the question whose answer will determine whether the programme succeeds.

A manufacturing business is preparing to replace its ERP. The incumbent has been in place for two decades and is disliked, sometimes with reason. The proposed replacement is significantly more capable in areas the business does not yet use, and significantly less mature in areas the business depends on every day. The migration will consume three years of executive attention. The independent question is whether the business's real problem is the ERP, or the accumulation of undisciplined customisations built on top of it. If it is the latter, replacing the platform without addressing the underlying discipline will reproduce the same conditions inside a newer container.

A private equity backed group is evaluating whether to build a private knowledge system to preserve institutional memory across a portfolio of acquisitions. Several vendors offer credible platforms. Several consultancies have views. The independent question is whether the organisation is ready to treat its knowledge as an asset in the first place. Without that readiness, the platform will become an expensive archive that no one trusts. With that readiness, almost any competent platform will produce meaningful returns. The technology question is downstream of an organisational one.

A software business that has grown rapidly through acquisition is debating whether to consolidate its portfolio onto a single stack. The engineering leadership is divided. Every vendor in the room has an interest in being chosen. The independent question, which has nothing to do with the technology, is whether the business has enough clarity about its future operating model to make a consolidation decision at all. Consolidating prematurely locks in assumptions that will look wrong in eighteen months. Not consolidating at all preserves complexity that will compound. The right answer is often a smaller and more specific decision than the one the room has framed.

In each of these situations, there are recommendations that no commercial provider is well placed to make. Wait. Do less. Keep the existing system for another two years and use that time to prepare the organisation. Change the operating model before you change the platform. Buy the smaller thing. Do not buy anything yet, and use the budget for something less visible but more consequential. These are not exotic recommendations. They are, in the experience of most executives who have lived through several large programmes, the recommendations that turn out to have been correct. They are also the recommendations that no participant with a commercial stake in the programme can comfortably make.

The Discipline Behind the Practice

This is the specific space that independent advisory work occupies. Its purpose is not to replace vendors, integrators, consultancies, analysts, or internal teams. Its purpose is to sit alongside them and to ensure that the questions those parties cannot easily ask are being asked by someone, at the moment when the answers still matter. It is a supplementary discipline, not a competing one.

It is worth being honest about why independent advisory work of this kind is comparatively uncommon. The economics are difficult. It does not scale. Each engagement depends on the personal attention of one advisor and cannot be extended by adding junior staff without changing the nature of the work. It generates no follow-on implementation revenue, no managed service, no software resale, no referral fees. It cannot be productised. Its output is judgement, delivered privately, and its value is often invisible outside the room in which it was offered. From the point of view of a business school case study, it is an unattractive model. From the point of view of a client facing a decision that will still be visible in ten years, it is worth the difference.

The professional discipline behind this kind of work is stricter than it may appear from the outside. It requires refusing referral arrangements with vendors, even when they are offered in good faith. It requires refusing revenue share with integrators. It requires declining equity in the companies whose platforms one might have occasion to discuss. It requires being willing, more than once a year, to tell a client that the programme they have already begun to describe internally is not the right one. None of this is heroic. It is a set of ordinary constraints that, taken together, make the advice worth the fee.

It is also worth being clear about what independent counsel is not. It does not replace the specialised knowledge held by vendors and integrators, it is no form of neutral omniscience, and it is not always right. When it is wrong, however, it is wrong for reasons that had nothing to do with what the person offering it stood to gain. That is a smaller claim than it sounds, and it is close to the whole of the argument.

Why the Asymmetry Matters

The reason boards should care about this distinction has become more pressing over the last several years, not because vendors have grown less trustworthy, but because the decisions themselves have grown less reversible. A modern platform decision does not sit inside a single function. It runs through the operating model, the data model, the organisational chart, the vendor relationships, the customer experience, and the culture of the business. Reversing such a decision two years in is possible, but it is expensive in a way that changes the future of the company. In this environment, the marginal value of an additional independent conversation, before the decision is finalised, is very high. The cost of it is small. The asymmetry is unusual.

A related point needs some care. Independence in the sense used here is not a moral posture, and it makes no claim that the independent advisor is more ethical than the vendor or the consultancy. Vendors and consultancies contain many people of great integrity, and their judgement, correctly weighted, is often the most valuable input in the room. The independent advisor does not replace that judgement. Their role is to ensure that the questions surrounding it have been properly framed. What makes such counsel useful is that it is not asked to be the authority on the platform, but on the decision itself.

Executives who work with independent advisors over long periods tend to describe the relationship in similar terms. They do not describe it as a source of dramatic insight. They describe it as the ability to think out loud, without the conversation being quietly shaped by someone else's economic interest, and to be told the thing that no one else in the room is structurally free to say. That is a quieter service than most professional relationships in the technology ecosystem, and it is often the one that leaves the deepest mark on the outcome.

There is a final observation that returns the argument to where it began, in the responsibility of the executive team itself. No advisor, however independent, removes the burden of the decision from the people who must live with its consequences. Independence is not a way of outsourcing judgement. It is a way of ensuring that the judgement, when it is exercised, has been informed by at least one conversation whose value did not depend on what the executive team chose to do next.

Organisations do not often regret asking one more independent question before committing tens of millions to a programme that will shape them for a decade. They more often regret not having asked it, and discovering, some quarters later, that the question would have changed the answer.

A Seat Kept Open

That is all the argument contains. It runs neither against vendors nor integrators, neither against analysts nor internal teams. It only urges that at the table where a decision is made, one seat be kept for a voice free to ask a different kind of question, while the difference still matters.

There is a further question that follows this one, and it is the question the next essay in this series takes up. Independent counsel produces the conversation. It does not, on its own, produce the institution capable of receiving it, of remembering what was said, of returning to the reasoning a year later when the room has changed. Judgement, if it is to survive the moment in which it was offered, needs an organisation built to hold it. That is a different subject, and it is the subject of the essay that follows.