A sceptical board does not need to be “won over”. It needs a decision it can examine: the problem, credible options, evidence, exposure, cost and accountability.
A long presentation can hide the ask and leave challenge until the final minutes. A one-page decision paper and a disciplined conversation make assumptions easier to test. Supporting analysis remains available for scrutiny.
Open with the decision context
Use wording like this:
We are asking the board to decide how the firm should address [specific problem]. Today it affects [clients, operations or risk] in these observable ways. We considered [options]. Our recommendation is [option and present phase], for [cost range and period], because the evidence currently supports it. These assumptions remain uncertain, and this is how the next gate will test them.
This opening states the decision before attempting to create urgency.
Include the consequence of delay, but avoid treating inaction as a fictional zero-cost or a guaranteed disaster. Describe the credible defer or contain option, its continuing cost and the trigger for reconsideration.
Respond to “we cannot afford it”
The proposed commitment is [amount or range], with [cash timing] and [internal capacity]. The current service costs [supported operating figure] and creates [evidenced manual effort or exposure]. We can defer, reduce scope or fund this phase. These are the financial and service consequences of each choice.
Show total cost of ownership, not only purchase price. Include implementation, migration, licences, suppliers, internal time, dual running, training, support and decommissioning.
Do not make a small phase look cheap by hiding the likely later programme. Show the longer-horizon range while keeping later approval conditional.
Respond to “we tried this before”
The previous initiative did not achieve [intended outcome]. The evidence identifies [scope, governance, delivery, adoption or technology causes]. Some responsibility sat with us, and some with the delivery model. This proposal changes those conditions through [specific controls]. The first gate will test whether those changes are working before further commitment.
Avoid “this time is different” without evidence. Review the previous business case, contracts, decision logs, outcome data and affected users. If the failure cannot yet be explained, fund a diagnosis before another build.
Preserve useful assets and learning from the earlier work. A reset should not become an excuse to buy everything again.
Respond to “it is not a priority”
Against the firm's agreed priorities, this work contributes to [named outcome]. The cost of delaying it is [evidence and range]. It competes with [other investments], and the opportunity cost of choosing it is [what waits]. We recommend its position because [comparison].
Competitor activity can provide context, although it is not a business case. Use current, recorded evidence and explain relevance. A client comment is one signal, not proof of market-wide need.
If the work cannot be connected to a current priority or material obligation, the board may be right to defer it.
Respond to “show me the return”
We modelled conservative, central and adverse scenarios from these assumptions. The benefits include [capacity, cost, revenue or risk outcome], and this is who owns each one. The project does not control [external influences]. We will measure [leading and outcome evidence] at [dates].
Show ranges, denominators and timing. Separate cashable savings from released capacity, and revenue protected from revenue newly created. Avoid counting gross revenue as profit or crediting the last digital touch for an entire sale.
Some risk and obligation investments do not have a positive revenue return. Present the decision as a cost of safe operation, with options and proportionality.
Respond to “can we fix what we have?”
Yes, that is one of the options. Improving the current service would involve [scope, cost, constraint and useful life]. Replacing or extending it would involve [same categories]. We recommend [choice] because it performs better against [requirements and decision horizon].
Do not describe age as sufficient evidence. Show support, recoverability, change cost, user outcomes and strategic constraints.
Run a technical assessment or proof where uncertainty is material. A board should not have to choose between competing architectural assertions.
Put the whole ask on one page
Use five short sections:
Decision
The exact approval, amount or range, owner, timing and conditions.
Problem and evidence
The affected outcome, baseline, source and confidence. Include contradictory evidence.
Options
Improve, replace, contain, defer or stop as relevant, with cost, benefit and risk ranges.
Recommended phase
Scope, dependencies, measures, assurance, operating ownership and what remains outside it.
Gate and accountability
The next decision date, evidence required and people accountable for delivery, benefit and risk.
Put technical detail, scenario calculations, procurement evidence and architecture in appendices. Use specialists in the meeting when material questions may arise.
Avoid three proposal failures
First, do not lead with product terminology. Translate the technical decision into capability, service, cost and exposure, while keeping the technical evidence available.
Second, do not phase purely to make approval easier. Phase where the first commitment is coherent, safe and capable of testing an important uncertainty. A board should see the likely total destination and retain a genuine right to stop.
Third, do not turn assumptions into facts. Label benchmarks, estimates and attribution. A board can make a judgement under uncertainty; it cannot do so responsibly when uncertainty is concealed.
Prepare governance, not a private campaign
Speak with the chair, finance, risk and affected leaders before the meeting to identify missing evidence and ensure the item is ready for decision. Pre-reads should reach all board members through the agreed process.
Do not use private conversations to create a decision outside the board or withhold material objections. The meeting should remain the place where options are tested and the decision is recorded.
Ask what would cause a director to reject or condition the proposal. If the answer reveals a missing analysis, fix it. If it reveals a different risk appetite, present the trade-off openly.
Close with the precise ask
We recommend that the board approve [phase and budget] under [governance and constraints]. At [date], we will return with [evidence] and a recommendation to continue, change, pause or stop. Today we need a decision on [specific approval] and confirmation of [named owners or dependencies].
Then allow challenge. Record conditions and dissent accurately. Do not interpret questions as failure of the presentation.
The board presentation script template available with this article provides evidence placeholders for the five objections and the one-page paper. It cannot guarantee approval, nor should it. Its purpose is to make a consequential investment easier to examine, compare and govern.
