The Cost Behind the Cost: Budgeting Your Team's Attention Before You Commission Advice

Consultancy proposals arrive with a fee, a timetable and a list of deliverables. They rarely arrive with an honest estimate of what they will demand from the client. For UK buyers, that omission matters. The invoice is visible; the internal time is not. A finance director pulled into three workshops, an operations manager assembling data over a fortnight, a chief executive asked to arbitrate between options: each hour has a cost, even if it never appears on the consultancy invoice.

This is not an argument against buying advice. It is an argument for buying it with a clearer view of the whole outlay. The discipline is to treat client-side effort as a budget line in its own right, estimate it before signature and design the engagement around the capacity that actually exists.

The visible fee and the invisible cost

UK organisations are accustomed to scrutinising professional fees. Procurement teams will challenge a day rate, compare competing proposals and ask what is included. Far less often do they ask what the engagement will cost in internal meetings, data preparation, review cycles and decision-making. Yet senior attention is finite, and in many businesses it is more expensive than the consultancy time it is meant to direct.

In an SME, the same small group may be responsible for operations, finance and customer delivery. In a larger business, decision rights are dispersed across functions, which can multiply the number of people who must be consulted. The internal cost is not merely an accounting matter. It is an opportunity cost: the work that does not happen while the team is briefing, reviewing and chasing. It is also a risk: delayed decisions, fatigue and slippage in business-as-usual activity.

A practical estimate in five steps

Estimating internal effort need not be elaborate. It needs to be explicit.

First, map the stages of the engagement as the client will experience them: mobilisation, diagnosis, design, decision and embedment. Second, name the roles that must be involved at each stage. Be specific. 'Senior stakeholders' is not a role; a finance director, a head of operations and a commercial manager are. Third, estimate hours per role per stage. Use a base case and a high case, because workshops and review cycles have a habit of expanding. Fourth, apply an internal hourly cost. This may be a charge-out rate, a fully loaded salary cost or a simple opportunity-cost assumption agreed by the finance team. Fifth, add a contingency for decision latency and rework. Fifteen to twenty-five per cent is a reasonable starting range for many engagements.

The output can be a single line in the business case: client effort valued at a stated sum, based on a stated number of hours across named roles. That line is more useful than a vague assurance that involvement will be light.

Read the proposal for client obligations

Proposals often contain phrases such as 'client team to provide data', 'weekly steering group' and 'workshops with senior stakeholders'. These are not incidental. They are commitments of time, and they should be read as such.

Ask for a client responsibility schedule. It should state what is required, from whom, by when and in what form. If the proposal assumes access to management information, ask whether that information exists in a usable format and who will extract it. If it assumes fortnightly governance, ask how long those sessions will run and who must attend. A good consultancy will welcome the question. A weak one will treat it as friction.

The questions to settle before signature

Five questions are worth resolving before the contract is agreed. Which decisions will require our sign-off, and when? What data must we supply, and who owns its preparation? Who is the single point of contact on the client side? What is the minimum viable senior attendance, as distinct from the ideal? What happens if our availability slips?

These questions do not undermine the consultancy relationship. They establish the operating conditions in which advice can be useful. An engagement that depends on unrealistic client availability is not a robust engagement, however strong the methodology.

Negotiating around capacity

Negotiation should focus on sequencing, cadence and division of labour. The consultant can take on data gathering and first-pass analysis; the client team can review a draft rather than build it. Workshops can be fewer and better prepared. Decision points can be scheduled around board cycles rather than in parallel with them. The aim is not to reduce the fee for its own sake. It is to buy the outcome without exhausting the team that must live with it.

A proposal that requires less internal time may be better value even at a similar fee. Conversely, a cheaper proposal that demands weeks of senior attention may prove the more expensive choice. The comparison should be on total cost, not invoice alone.

The business case should show both sides

Add internal effort to the business case alongside fees, expenses and any technology costs. Use conservative benefits. If the internal cost changes the payback period materially, revisit scope or phasing. A phased engagement that protects capacity may outperform a comprehensive one that leaves the team unable to implement its findings.

For boards and senior teams, the test is simple: has the business case accounted for the attention the organisation must supply, not only the advice it will receive? If not, the case is incomplete.

Conclusion

The best consultancy relationship is not the one that demands least from the client. It is the one that asks for the right attention at the right moments. Before signing, put the internal time in the business case. It is the cost behind the cost, and it deserves the same scrutiny as the fee.