Separating the user problem from the budget holder problem

A team loves a new tool because it removes repetitive entry. Its manager declines the purchase because the current reporting problem remains unresolved. The demonstration answered a real need but not the organisational decision.

Establish what each person is accountable for

Ask users which tasks are difficult and what a successful day looks like. Ask budget holders which results they must defend and what alternatives they could fund. Avoid assuming a senior title automatically identifies the economic buyer.

The GOV.UK service-metrics guidance connects measures to service purpose. A founder can use that principle to relate user improvements to an outcome the organisation recognises.

This does not mean converting every minute saved into a cash claim. Extra capacity creates financial value only under circumstances the buyer can explain.

Build a connected value argument

An illustrative logistics product could reduce dispatcher corrections. The user benefit is less rework. The manager may care about missed delivery windows and the time senior staff spend resolving escalations.

Test the proposed connection. Are the corrections actually causing delays? Will removing them change the staffing requirement or simply make work less stressful? Both can matter, but they support different purchase arguments.

Avoid pitching incompatible promises to different stakeholders. The product should not be presented as a headcount-reduction tool to finance while being sold as workload expansion to the operating team without an honest discussion.

Bring the perspectives into one test

Agree an evaluation with measures for the user task and the organisational result. Identify who reviews each measure and what outcome would justify the next decision.

If the user benefit is strong but the budget case remains weak, narrow the target segment or reconsider packaging. Pressuring an internal enthusiast to sell an unproven business case rarely resolves the evidence gap.

Prepare a two-part evidence sheet showing the user result and the organisational consequence it is expected to influence. Draw the connection as a hypothesis until the buyer verifies it. This makes it possible to improve the product without overstating a financial benefit that the operating change has not yet produced.

GAT’s pilot-to-revenue article describes the need for an explicit purchase path. Understanding the budget holder’s problem makes that path more credible while preserving the user evidence on which the product depends.