Table of Contents
Most organisations that describe themselves as practising consulting demand management are, on close inspection, practising something narrower: a sequence of approval steps that confirms a project is affordable and administratively in order, without asking whether it deserves consulting resources ahead of everything else competing for the same budget and attention. The gap between those two things is a gap in timing rather than sophistication, and it is where most consulting portfolio value is lost before a firm has been engaged.
This article examines what consulting demand management actually is, why the approval process is not a substitute for it, and what the organisations that have closed the gap have built in practice. It is the second article in Consulting Quest’s consulting utilization cluster, and it assumes the investment framing established in the first: that consulting is a managed category with portfolio logic, not a sequence of individual project decisions.
What the Approval Process Actually Does
Most organisations already have a structure they would point to as evidence that this is managed: an engagement committee, a business case review, a sign-off process before spend is committed. The committee meets, the form is completed, the contract proceeds. In Consulting Quest’s five-year benchmark data across sixty organisations, the Idea to Sourcing dimension, which covers demand visibility, demand management, make-or-buy, and budget governance, scores an average of 2.18 against an overall six-dimension average of 2.63, the lowest of the six dimensions. The explanation is structural: by the time a consulting request reaches the committee, the provider has typically already been identified and the sponsor has already committed internally, so the committee is reviewing paperwork rather than arbitrating priorities, and in that sequence almost no project is ever refused.
These are legitimate steps, and completing them correctly matters. Consulting budget management asks a different question: whether this project is the right use of consulting resources at this moment, given everything else competing for the same budget and attention. None of the approval steps are designed to raise it.
The Planning Cycle Problem: Why Procurement Arrives Too Late
The approval process inherited this situation rather than created it. Procurement’s involvement began after the decisions that matter had been taken, which is partly why it so often begins there: in most organisations, the planning conversations where priorities are set belong to strategy and finance, and Procurement does not hold a seat in them. The executive who wants the project has more authority in that conversation than the function that would challenge it, and by the time the project reaches a formal process, the sponsor’s commitment has created a political weight that the approval function is not structurally positioned to override. Rejecting a project on strategic grounds requires a seniority and a relationship with the planning cycle that most consulting procurement functions have not established.
The absence compounds itself: the less Procurement is present in planning conversations, the less institutional standing it accumulates to challenge demand before it is formed, which is the structural reason capable procurement organisations tend to plateau at whichever state they have reached rather than moving through it.
The result is a consulting portfolio shaped by organisational urgency and political weight rather than by deliberate allocation. Projects with the loudest sponsors and the most immediately visible problems get resourced, while priorities that are harder to articulate, or whose value is distributed across a longer horizon, wait or are never asked. In a post-merger integration this dynamic is compressed and amplified simultaneously: every workstream lead arrives with a problem and a preferred firm, and the timeline that makes careful evaluation feel dispensable is the same timeline that makes careful evaluation most necessary. Without portfolio-level demand management mapped to the integration thesis, consulting spend accumulates across parallel mandates that duplicate effort, produce conflicting recommendations, and exhaust the advisory budget before the hardest problems are scoped.
Where a competent reader can locate their own organisation quickly, the following table makes the distinction operational:
What Consulting Demand Management Actually Is
Consulting demand management is the discipline of ensuring that consulting resources, including budget, management attention, and supplier relationships, are allocated to the initiatives most likely to create strategic value, before projects are scoped and before firms are engaged. It functions as an arbitration mechanism whose purpose is allocation rather than control, and the question it is designed to answer is whether this project is the best use of consulting resources right now, given everything else competing for the same budget and attention.
In a deal context the distinction becomes structural. Due diligence generates one list of priorities, Day One planning generates another, and each integration workstream generates its own. Without an arbitration function that compares these lists against the deal thesis before any of them become scoped projects, the organisation funds everything and optimises nothing, which is precisely what most post-merger integration advisory budgets reflect.
Consulting budget management of this kind requires strategy, finance, and procurement to be present simultaneously, and it requires the conversation to happen in the planning cycle rather than the approval cycle. That sequencing is the mechanism on which everything else depends.
Consulting Procurement Maturity: Three States and What Separates Them
Consulting Quest identifies three observable states in which organisations operate, each distinguished by when the consulting demand management question is asked and who is in the room when it is answered.
The Approval State
A consulting request arrives in Procurement or Finance. Budget is confirmed, the contract is reviewed, and the project proceeds. The question of whether this project should exist, and whether it deserves resources ahead of other competing priorities, was never formally asked, because by the time the request arrived it had already been answered informally by the executive who wanted it, and the approval process had neither the timing nor the authority to revisit it. This is where the majority of organisations operate, including many that would describe their consulting demand management as structured and mature.
The Project Evaluation State
A more structured process exists: business cases are required, criteria are applied, and some projects are deferred or rejected. The project evaluation state approves projects on their own merits, which is genuine progress, though a project scoring well individually may still be the wrong priority given everything else running on the same strategic agenda. The evaluation also still happens after demand has been expressed, after a problem has been framed and a sponsor has committed, so the window in which arbitration was possible has closed before the process begins. The process is sound, but it activates after the moment that matters has passed, which is why capable procurement organisations tend to plateau here rather than move through it.
The Portfolio Arbitration State
Consulting demand is mapped against strategic priorities on a regular cycle, annually and at each planning review, and trade-off decisions are made across the portfolio rather than project by project. A portfolio view shows what is running, what is planned, and what is competing for the same resources, and the question shifts from whether to approve this project to whether this project is the best use of available consulting resources given everything else.
That question can only be answered with a portfolio view, and it can only be acted on if Procurement is present before projects are formed. At that stage Procurement brings something the planning conversation does not otherwise contain: knowledge of what projects of this type actually cost to run well, which delivery models produce the best outcome at what scale, which panel firms have directly relevant experience, and where scope discipline at intake reduces the total cost of the mandate. A project that looked unaffordable at the initial ask frequently becomes viable once that knowledge is applied, and the portfolio comparison is then made on demand that has already been optimised rather than on raw requests whose cost and scope reflect only what the sponsor believed the project required.
For organisations assessing where their consulting demand management currently sits, Consulting Quest’s Consulting Procurement Maturity Model provides a structured diagnostic.
Why Organisations Resist Centralising Consulting Governance
The decentralised model, in which each business unit manages its own consulting demand and Procurement validates the contract, works well for individual decisions. A business unit lead who knows their problem, knows the relevant firms, and has a credible budget case will generally make a reasonable project decision. The argument for leaving it there is that centralising the portfolio view introduces overhead, slows decisions, and substitutes a governance function’s judgment for the judgment of the people closest to the problem. This argument is serious, and the organisations that have not made the shift are not, in most cases, unaware of the alternative.
The argument holds at the project level and breaks at the portfolio level, because no single decision-maker has visibility of all the projects simultaneously. The business unit lead who approves a strong project does not know that three other units have approved projects that duplicate its scope, compete for the same implementation resources, or address the same symptom from different angles without coordinating. The cost of that incoherence is not visible in any single approval; it accumulates across the portfolio and becomes visible only when the organisation reviews its consulting spend at year-end and finds that the aggregate does not reflect the strategic priorities the leadership team believed it had set.
Portfolio arbitration adds a comparison function that no individual project owner can perform, because it requires seeing all the projects simultaneously, which is precisely the visibility the decentralised model withholds from each decision-maker. The full portfolio logic is addressed in Consulting as an Investment: The Governance Gap Most Organisations Haven’t Closed; this article focuses on the demand management layer that precedes it.
Make-or-Buy in Consulting: The Decision That Precedes Sourcing
The first decision a functioning consulting demand management process generates, once a project has been validated and prioritised, is the make-or-buy question: should this work be done internally, externally, or through a hybrid of both? This question belongs inside the demand management process, positioned after validation and before sourcing, and its placement there is what gives it any practical force. Organisations that reach the make-or-buy question with a preferred firm already in conversation have answered it by default.
The decision requires assessing whether the internal team has the required expertise and availability, whether their output would carry the necessary authority with stakeholders, whether the work should remain inside the organisation for reasons of confidentiality or capability building, and whether external perspective adds value that internal knowledge cannot provide. Answering these questions honestly requires the kind of internal capability mapping that most organisations do not maintain systematically, which is itself a demand management gap.
The organisations that ask this question consistently, before any firm is engaged, find that a meaningful proportion of consulting demand is better served by internal teams, hybrid delivery, or expert input than by full consulting mandates, which is the more accurate answer to the question demand management is designed to ask. Make or Buy: The Decision That Shapes Everything addresses this in full.
What Strategic Demand Management Looks Like in Practice
The organisations that have moved to portfolio-level arbitration have generally built three operating mechanisms, each of which addresses a different part of the consulting demand management problem.
The consulting demand review
A regular review, quarterly in a standard operating environment and monthly against the integration workplan in a PMI context, covering all consulting demand that is active, planned, and emerging. Attended by strategy, finance, and procurement. The output is a portfolio allocation that determines which initiatives receive consulting resources, in what sequence, and with what mandate. Its authority comes from seeing the whole portfolio simultaneously, which no individual project owner can do, and from having the organisational standing to make trade-off decisions before projects are formed rather than after sponsors have committed.
The pre-initiation gate
Before a project brief is written or a firm is contacted, a lightweight pre-initiation step asks three questions: does this align with a current strategic priority; is this the right moment given the current portfolio; and is the need sufficiently defined to proceed, or does it require an internal workshop or exploration RFI first? Projects that cannot answer these questions are returned for further definition, which is itself a form of consulting budget management, because it prevents the scoping and sourcing effort that an underdefined demand consumes before the question of whether it should exist has been properly answered.
The portfolio scorecard
A maintained view of all consulting engagements showing strategic alignment, current status, expected value, and actual outcome against projection, updated at each demand review. The scorecard creates the institutional memory that prevents the same decisions, good and bad, from being invisible to the organisation. An organisation running a post-merger integration uses it to track consulting spend against the integration thesis, so that when a mandate runs over budget, the trade-off is visible: extend it, or redeploy those resources to a higher-priority workstream before the window for that decision closes.
What Consulting Budget Management Actually Requires from Procurement
Procurement’s involvement in consulting demand management typically begins too late, and the structural reason is the one identified in Section 2: the planning conversations where demand is shaped belong to strategy and finance, and Procurement does not hold a seat in them by default. After a need is defined, a firm is shortlisted, and an executive sponsor has committed, Procurement’s leverage is limited to contract terms and rate negotiation, and improving that leverage does not change the consulting budget management question, which is whether the right projects were approved in the first place.
Moving Procurement earlier requires something other than a process redesign. It requires Procurement to maintain the portfolio view that makes the demand review possible, to bring supplier market intelligence into the pre-initiation gate, and to have the organisational relationships that allow it to raise the portfolio question before projects are formed. That is a different function from contract processing, and it requires different capabilities: market knowledge, pipeline visibility, an understanding of the strategic priorities that demand should be mapped against, and the credibility to challenge a project request before a senior sponsor has committed to it.
Genuine consulting demand management is a joint discipline: strategy brings priority context, finance brings resource constraints and the investment logic that connects spending decisions to value measurement, and Procurement brings market knowledge and portfolio visibility. The arbitration works when all three are present in the planning cycle, and the organisations that have moved furthest have found that the shift requires less of Procurement gaining authority and more of all three functions sharing a portfolio view that none of them had held individually. This repositioning of Procurement’s role is addressed in Procurement at the Strategy Table: From Gatekeeper to Portfolio Architect.
Consulting Demand Management as a Governance Change
The organisations that have made the shift from expense validation to strategic arbitration have generally found the mechanics straightforward: a demand review, a pre-initiation gate, and a portfolio scorecard are not technically complex. What they represent organisationally is more consequential, because they require Procurement to be present in planning conversations that have historically belonged to strategy and finance, and they require strategy and finance to treat consulting as a category with portfolio logic rather than a series of individual project decisions that happen to share a budget line.
The value of that change is not visible in any single approval decision. It accumulates in the projects that were redirected to internal delivery before a firm was engaged, in the mandates that were sequenced differently because someone held the portfolio view when the question was still open, and in the advisory budgets that finished the year reflecting the strategic priorities leadership believed it had set rather than the ones that happened to have the loudest sponsors.
Consulting Quest 
English 
Français 
Português 
