How to write a Business Case that influences decision‑makers

When executives and board members review a business case, they are ultimately asking a simple question: “Is this project worth committing people and money to, and are we able to deliver it? The business case exists to confidently answer that question.

Before you start writing, you should understand the current state, be clear on the problem you’re solving, and have a defined approach to address it. If any of that is unclear, step back to Pro Partner’s step‑by‑step Project Brief guide which is a practical way to work through those fundamentals.

A business case is where you move from problem definition to creating a commitment from the board, for management to undertake. Your recommendation needs to stand up to scrutiny years into the future. You can create this by going deeper into the current state, rigorously evaluating solutions, understanding the commercial and financial implications, and defining a delivery approach that gives decision‑makers ongoing visibility and control.

Below is a practical guide to building a stand-out business case for the executive and board level, alongside a real example of a board‑approved business case. This example went through multiple iterations to reflect executive expectations and directly address questions it was subjected to. We’ve anonymised the content to show what good looks like in practice.

Decide on a structure for your business case

A strong business case is just as much about the content as it is about the structure and presentation. Decision‑makers will not spend time trying to piece together your logic. They expect a clear, logical flow that allows them to understand the problem, assess their options, and make an evidence-based decision. Without a robust structure, even good analysis can feel unclear or unconvincing as key points are dropped and confidence in the recommendation is lost. A well-structured business case can remove that those issues and makes analysis easy to follow, ensuring every critical element is understoodijjjj

The following five questions provide an business case structure which can be applied consistently across many different types of projects. In our experience, they reflect how executives and boards make decisions, by moving through understanding, strategy, options, contracts, finances and management.

The top 5 questions every business case should answer:

1. Is there a compelling case for change? (Strategic case) 

2. Does the preferred investment option optimise value? (Economic case) 

3. Is the proposed option commercially viable? (Commercial case) 

4. Is the spending proposal affordable? (Financial case) 

5. Can the proposal be delivered successfully? (Management case). 

Q1. Is there a compelling case for change? (Strategic case)

The strategic case is where you must establish why this initiative deserves the boards' attention. The strategic case sets the context for each discussion that follows by clearly laying out how the current state is roadblocking priorities, creating risks, and/or opportunity cost. Decision‑makers are looking for reasons why maintaining that state is no longer acceptable. Your business case will demonstrate what's at stake if nothing changes and how the proposed direction aligns with strategic goals. When done well, this strategic case creates urgency, clarity, and alignment between board members by giving executives a compelling reason to solve the problem.

Strategic case contents

A strong strategic case does five things, quickly and clearly:

• Situation analysis: Set the context. Show how the environment has changed and why the status quo is no longer acceptable.

• Strategic risks: Highlight the real risks (e.g. continuity, inefficiency, strategic constraint) and their impact on the business.

• What if we do not change: Make it clear that inaction increases risk, cost, and missed opportunity over time.

• Mission and vision statement: Define the projects objectives and the outcomes achieving them will help create

• Benefit realisation: Show how value will be measured and delivered over time, beyond the life of the project.

Done well, this section creates urgency and alignment. It moves the conversation from “should we do this?” to “how do we do this?”.

How to present strategic risks and issues 

The strategic risks outlined in the table below are drawn from a real business facing significant operational and continuity challenges. As part of their strategic case, management clearly demonstrated how these risks could be reduced through the changes introduced by the proposed solution, showing a measurable shift from a high‑risk current state to a more stable and controlled future position.

Risk/issue	Description	Impact	Current probability	Current Risk Score	Future Probability	Future Risk Score
Dependence on key external provider	Reliance on external provider for core system support.	Severe.  Service disruption if the provider fails, requiring workarounds	Almost certain.  Current vendor is the only vendor who can support the core system	Extreme	Possible. Changing the vendor combined with the proposed contractual deliverables for thorough documentation and potential to provision additional offshore support, reduces this risk.	Moderate
Dependence on key internal personnel	Few internal experts on bespoke software.	Severe.  Risk of operational delays if staff are on leave or unavailable.	Almost certain	High	Possible.  A more standardised system will support more standardised and automated workflows meaning there will be a decreased need for specialised knowledge to support the processes and shorter onboarding time for new staff.	Moderate
Security concerns	Legacy systems are vulnerable to malware or attacks.	Severe.  Data breaches, reputational damage, loss of stakeholder trust.	Unlikely.  After migrating the system to the new environment	High	Very unlikely. Demonstratable discipline and third-party security auditing written into standard terms MSA.	Low
Business critical functions not within core system	The core system was designed with a narrow scope	Moderate.  Operational errors and rework due to manual processes	Almost certain	High	Unlikely. New system will be designed with broader business context. A phased approach will be used to expand the system's capabilities and its potential to support future needs.	Low

Q2: Does the preferred investment option optimise value? (Economic case) 

The economic case is where you step beyond the problem and demonstrate that you have identified the right way forward. It is not enough to show that change is required. Decision‑makers need confidence that the preferred option represents the best balance of value, risk, and long‑term outcome.

The economic case should show that the options have been rigorously tested. It brings together structured analysis, market evidence, and comparative evaluation to demonstrate that the recommended approach is fit for purpose and stands apart from the alternatives.

Economic case contents

A strong economic case does five things, clearly and objectively:

• The proposed approach: Define the option being recommended in clear, practical terms so decision‑makers can understand what they are committing to and the scale of the change.

• Problem resolution: Show how the approach directly addresses the issues raised in the strategic case. Make this explicit so the connection is easy to follow.

• Strategic options analysis: Compare credible options and assess them against consistent criteria such as cost, risk reduction, and strategic fit.

• RFP process and vendor selection: Demonstrate that you’ve tested the market and followed a fair, structured process to select the best partner.

• Recommendation: Clearly state which option you are recommending and why it provides the best balance of value, risk, and delivery confidence.

The most important discipline in economic case is being objective. Decision‑makers need to see that the recommendation is the result of structured comparison and evidence, not a pre-determined outcome. Executive confidence will be built in how options are presented, how trade-offs are explained, and how clearly the preferred option stands apart.

Done well, the economic case builds confidence that:

• The right options have been considered

• The key trade-offs are understood

• The recommended path is the most balanced and defensible

In the example business case, there were multiple decision layers that led to the final recommendation. The first layer was a strategic decision about how to respond to the problem. This included assessing options such as doing nothing, enhancing the current system, adopting a hybrid approach, or moving to full replacement. This step was critical because it defined the level of change and investment the organisation was willing to commit to. In the example, the analysis showed that both the status quo and partial solutions would retain or defer key risks, rather than resolve them, making a full replacement the only option that addressed the problem.

Once the direction of a full replacement was agreed, the economic case moved to the next decision, comparing the available options within that path.

At this point, an RFP was used to identify credible full replacement approaches. Because these options sat within the same strategic decision, the analysis could go deeper to discover which option performed best across the areas that matted most to the board. This layered decision making approach is what made the recommendation successful. It showed that the organisation first chose the right level of investment, and then selected the strongest option within that path. This provided confidence that the preferred option was the best available.

Q3: Is the proposed option commercially viable? (Commercial case) 

The commercial case is where you demonstrate that the preferred option can be delivered in a way that protects the organisation’s interests. It moves from what to do and focuses on how to do it. Specifically, how the solution will be contracted, funded, and managed commercially over time.

Commercial case contents

A strong commercial case does five things:

• Contracting strategy: Define how the engagement will be structured to balance flexibility and control, including staged commitments and decision gates before further investment.

• Master Services Agreement (MSA): Establish the overarching legal and commercial framework, covering risk allocation, liability, IP ownership, security, and exit provisions.

• Statements of Work (SOWs): Break delivery into clear phases with defined scope, deliverables, and cost, enabling controlled investment and formal checkpoints.

• Software licences and cost model: Show how ongoing costs (licences, hosting, support) will be managed, ensuring transparency, scalability, and avoidance of lock-in.

• Funding and revenue position: Clearly set out how the investment will be funded and whether there is any revenue or value recovery expected over time. This includes confirming funding sources (e.g. internal budget, grants, reserves), affordability over the lifetime of the solution, and whether the investment enables any future revenue or cost savings (even if these are not relied on for approval).

In the example business case, the investment is staged so that early phases confirm feasibility before committing to a full build. Funding for the investment is shared across internal and external sources and not offset by any potential future revenue, breaking the dependancy for the solution to generate cashflow to fund itsself. It was important that the investment stood on its own as a risk‑reducing, capability‑enabling decision.

Done well, the commercial case builds confidence that:

• The organisation remains in control of cost and contractual commitments

• Risk is appropriately managed and shared

• The investment is affordable and well-structured over time

• Any future revenue or value is credible, but not overstated

Proposed contractual settings with vendor(s)

Agreement Type	Current State (2004–2025)	Proposed Future State
License agreements	No formal licensing arrangements. The system is bespoke, developed on a time & materials basis, with full ownership retained. No licence fees based on features or users.	Likely introduction of software licensing, with defined usage terms and cost structure.
Software delivery model	No SaaS arrangement. System is internally hosted in a cloud environment but not contracted as a subscription service.	Likely transition to SaaS or SaaS-like model with subscription-based access and vendor-managed service.
End user licence agreements	No formal end user licence agreements in place.	No change anticipated.
Development	No formal development agreements governing scope, deliverables, or commercial terms.	Possible introduction of structured development agreements to define delivery phases and obligations.
Support & maintenance	Covered under an existing Master Services Agreement (MSA) with current provider.	New MSA expected with future delivery partner to govern ongoing support and service levels.
Confidentiality	No formal non-disclosure agreements currently in place.	Formal NDAs to be established to protect commercial and operational information.

Q4. Is the spending proposal affordable? (Financial case) 

The financial case is where you prove that the recommended option can be funded and sustained over time. It answers a simple but critical question for decision‑makers: Can we afford this, and are we comfortable with the financial position it creates?

Financial case contents

A strong financial case does five things, clearly and transparently:

• Validation of earlier strategic decisions: Reassess the options considered in the strategic and economic cases through a financial lens, demonstrating that alternative pathways do not provide a materially better financial outcome that would warrant reconsideration.

• Financial risks of the status quo and preferred solution: Show the cost of doing nothing, including hidden and escalating costs, alongside the financial risks of the proposed option.

• Detailed financial costing of the recommended solution: Break down total cost of ownership, including implementation, internal effort, and ongoing operating costs.

• Cashflow model: Show how costs and funding are spread over time, making affordability and timing of investment clear.

• Internal labour costs: Make internal effort visible, as this often represents a significant but overlooked cost and capacity impact.

A key discipline in the financial case is revisiting earlier decisions. The strongest financial cases validate that the strategic and economic choices made earlier still ring true when viewed through a financial lens, before moving into detailed analysis of the recommended solution.

In the example business case, the financial case clearly showed:

• Lower‑cost options (such as status quo or hybrid approaches) appeared cheaper upfront but carried higher long‑term cost and risk.

• The recommended option required a higher initial investment but delivered a more stable and predictable cost base.

• No alternative pathway provided materially stronger financial outcomes once lifecycle cost, risk, and future investment were considered

Done well, the financial case builds confidence that:

• The organisation understands the full financial commitment

• The investment is affordable within the funding model

• Alternative options have been tested financially and are not materially stronger

• The recommended option represents the best balance of cost, risk, and long-term value

Financial costing of strategic options

Financial costing table for the recommended option (from the economic case)

Q5. Can the proposal be delivered successfully? (Management case) 

The management case is where you demonstrate that the organisation can actually deliver what it is committing to. It shifts the focus from the investment decision to execution, showing that there is a clear path forward, the right governance in place, and the capability to deliver the outcome successfully. Done well, this section gives decision‑makers confidence that delivery is structured, controlled, and achievable.

Management case contents

A strong management case does five things, clearly and practically:

• Delivery approach, phases and timeline: Set out how the work will be delivered in a structured way. Delivery approach will show a clear sequence of phases (e.g. discovery, design, build, deployment), with realistic timeframes and defined outcomes for each stage. The goal is to give confidence that delivery is planned and achievable.

• Milestones and stage gates: Define the key decision points throughout the delivery. These are formal checkpoints where progress is reviewed, risks are reassessed, and approval is required to continue. Strong stage gates ensure that the organisation remains in control and can adjust, pause, or stop if needed.

• Change management considerations: Show what the organisation needs to do to support the solution. This includes stakeholder engagement, training, communication, and embedding new ways of working. In some cases, change can mean restructuring the organistion to support new ways of working. The strongest management cases recognise that delivery success is not just technical and it depends on people changing how they work.

• Resources, Roles and responsibilities: Clearly set out who is accountable for what action across the project or programme. This ensures there is no ambiguity in decision‑making, ownership, or delivery accountability.

• Risk management: Identify the key delivery risks and how they will be managed. This includes assigning ownership, defining mitigation strategies, and showing how risks will be monitored and managed throughout the project.

A key discipline in the management case is demonstrating control without overcomplication. Some decision‑makers are looking for detailed project plans, but they really just want assurance the right decipline and rigour will be applied. Executives are looking for confidence that delivery is structured, governed, and supported by the right capability.

In the example business case, the management case write parts of a Project Management Plan early to demonstrate how:

• Delivery is structured into defined phases with clear outcomes

• Formal stage gates provide control over progression and investment

• Roles across internal teams and vendors are explicitly defined

• Risk and change are actively managed throughout the programme lifecycle

Additional thoughts

Plan business case content with board members and executives

Before you start writing, plan the contents with the decision makers who will approve the business case. This avoids rework later and ensures the case reflects what decision‑makers actually need to see. Confirming the key questions the board expects answered, agree the level of detail expected for approval and check whether the problem and proposed apprach are are understood and generally supported. Just as importantly, align on the process they expect you to follow; how options will be evaluated, what evidence is required, how options will be assessed, and the level of rigour needed before a recommendation is made.

This early alignment also surfaces sensitivities and likely areas of challenge, including strategic drivers, cost, risk, and preferred approaches, allowing you to address them proactively. Done well, the business case becomes formal confirmation of a direction and approach that executives already understand and support. It removes late-stage issues caused by lack of engagement and ensures the final document reflects how decisions will actually be made.

Use an Appendix

The Appendix can be overlooked, but it is a useful tool to provide the in-depth analysis and thinking that does not fit into the main narrative of the business case. The Business Case Appendix is should be used to provide supporting evidence for discussions and decisions in the main body. You can cite the appendix materials throughout the body of the business case.

A business case appendix typically includes:

• Detailed risk and issue register: Breakdown of risks introduced in the strategic case, including ownership, mitigation actions, and residual risk positions.

• Detailed options analysis: Supporting detail behind the strategic and economic decisions, showing how alternative pathways were assessed and why they were discounted.

• Roles and responsibilities: A detailed view of project governance and delivery structure, often aligned to elements of a Project Management Plan, that boards may want to review at approval.

• Detailed project timeline: A more granular version of the delivery plan, including key activities, dependencies, and sequencing.

In the example business case, the Appendix played a critical role for sign off. While the main document presented a clear and concise recommendation, the supporting material allowed board members to test their assumptions and investigate the detail behind decisions. The appendix was used to satisfy executives that the decision would hold up under scrutiny.

Ready to write a business case that wins the board over?

If you want to put this into practice, download the Pro Partner Business Case template and use it to write your own influential business case. This business case example has received unanimous endorsement from New Zealand boards of directors and executives, and we continually refine it to reflect how decision‑making expectations are evolving.

If you’d like support developing your business case, Pro Partner works closely with business leaders, executives, and board members to build winning strategies and deliver plans that driver ambitious projects. Contact us at getstarted@propartner.co.nz.