How to Write a Business Case that Gets Approved: A Step-by-Step Guide.

How to Write a Business Case that Gets Approved: A Step-by-Step Guide.

How to Write a Business Case.

Writing a business case is one of the most essential skills in project management. Whether you’re seeking approval for a new initiative, funding for a project, or support for a digital transformation programme, your ability to build a convincing business case can make or break your proposal.

This detailed guide explains how to write a business case that not only gets approved but also aligns with the Association for Project Management (APM) competency matrix. You’ll learn what a business case is, why it’s important, and how to structure it effectively with evidence, analysis, and practical examples.

What is a Business Case and Why It Matters.

A business case is a structured document that justifies the start of a project. It demonstrates the reasoning behind the investment and outlines the expected benefits, costs, risks, and alternatives.

In simple terms, the business case answers three main questions:

• Why should we do this project?
• What are the benefits and costs?
• How will we deliver it successfully?

According to the APM Body of Knowledge, a strong business case should establish clear alignment with the organisation’s strategic objectives, provide measurable benefits, and include evidence-based analysis to support decision-making.

In the APM competency framework, the “how to write a business case” competency ensures that project professionals can present a compelling case for action, built on analysis, options, and clear recommendations.

According to the Project Management Institute (PMI), organisations with well-defined business cases are 40% more likely to deliver projects successfully. Yet, many business cases still fail due to unclear objectives, weak financial justification, or lack of alignment with strategic goals. This article will ensure you don’t fall into that trap.

Benefits of Writing a Strong Business Case.

Writing a business case does far more than support approval. It creates a shared understanding among stakeholders and reduces project risk by clarifying scope, resources, and expected returns.

Here are key benefits:

• Improved decision-making: Decision-makers can clearly see financial and strategic implications.
• Increased project success rates: Studies show that projects with well-prepared business cases have a 35–40% higher success rate.
• Stronger stakeholder buy-in: A clear business case builds confidence and credibility.
• Better risk management: Identifies potential issues before they escalate.
• Efficient use of resources: Ensures investment is directed where it adds most value.

According to the Association for Project Management (APM), a business case is:

“A documented justification for undertaking a project, programme or portfolio. It evaluates the balance of benefits, costs and risks of alternative options and provides a rationale for the preferred solution.”

In simpler terms, the business case explains why a project is needed, what value it will deliver, how much it will cost, and what risks are involved. It serves as the key document used by decision-makers to determine whether a project should proceed, continue, or be stopped.

Step-by-Step Guide: How to Write a Business Case.

Creating a compelling business case involves more than just filling in a document – it’s about telling a convincing story that combines logic, data, and strategy. Below is a detailed, APM-aligned process that guides you through each step to prepare a business case that secures approval and drives measurable outcomes.

Step 1: Identify the Problem or Opportunity.

Every strong business case starts by clearly defining the problem, challenge, or opportunity the project addresses. This section sets the tone for the rest of your document. Decision-makers must immediately understand why action is needed.

Explain what the issue is, why it matters, and what the potential impact will be if no action is taken. Avoid vague statements – instead, use real data and evidence.

Example:
“Customer satisfaction scores have dropped by 20% in the last year due to outdated customer support software. Without upgrading our CRM system, the company risks losing £250,000 in annual revenue and damaging its long-term brand reputation.”

Tips:

• Use quantitative evidence such as performance reports, KPIs, or market data.
• State qualitative impacts, like customer experience, employee efficiency, or compliance.
• Link the problem to organisational or strategic goals – this demonstrates alignment with business priorities.
• Avoid jumping to solutions too early; stay focused on why change is necessary.

APM alignment:
This step aligns with the APM’s focus on establishing a clear project rationale – ensuring that project investments are justified through well-defined needs.

Step 2: Analyse the Available Options.

Once the problem is defined, evaluate the possible solutions. A credible business case must show that multiple options were considered objectively before selecting the preferred one.

Typical options include:

1. Do nothing: What happens if no action is taken? Often used as a baseline scenario to compare costs and benefits.
2. Do the minimum: A low-cost, short-term solution that reduces the issue without fully resolving it.
3. Do the optimum: The recommended option that delivers the best overall balance of cost, benefit, and risk.

Example:
Option 1 – Do Nothing: Continue with current systems. Costs remain steady, but inefficiencies persist.
Option 2 – Upgrade CRM Software: £50,000 investment; expected to increase customer retention by 10%.
Option 3 – Implement AI-driven CRM Platform: £80,000 investment; expected to increase retention by 25%, reduce support costs by 15%, and improve response time by 30%.

Tips:

• Use a simple cost-benefit analysis to show financial and strategic value.
• Highlight risks, dependencies, and implementation difficulty for each option.
• Be transparent about trade-offs – decision-makers value honesty over optimism.

APM alignment:
This reflects the competency of evaluating alternatives and ensuring investment decisions are evidence-based and strategically justified.

Step 3: Define Objectives and Success Criteria.

Clear objectives define what the project intends to achieve and how success will be measured. This section transforms the business case from an idea into a measurable plan.

Objectives should follow the SMART principle:
Specific: Clearly defined and unambiguous.
Measurable: Includes quantifiable outcomes or metrics.
Achievable: Realistic within the given constraints.
Relevant: Directly linked to strategic goals.
Time-bound: Includes a clear completion timeframe.

Example Objectives:

• Increase customer satisfaction from 70% to 90% within 12 months.
• Reduce operational costs by 15% within two years.
• Achieve full system integration and go-live by Q3 2026.
• Generate a minimum ROI of 20% within 18 months post-implementation.

Tips:

• Align objectives with the organisation’s strategic pillars.
• Include Key Performance Indicators (KPIs) for tracking benefits.
• Define how progress will be monitored during and after implementation.

APM alignment:
This links to benefits management and project performance measurement – ensuring that value delivery can be demonstrated post-project.

Step 4: Develop the Financial Case.

The financial case is the heart of your business justification. It provides the evidence that the proposed investment is cost-effective and delivers measurable returns.

Include key financial indicators such as:
Return on Investment (ROI) – The ratio of net benefit to total cost.
Net Present Value (NPV) – The current value of future cash flows.
Internal Rate of Return (IRR) – The rate at which NPV equals zero.
Payback Period – How long it takes for the investment to pay back.
Total Cost of Ownership (TCO) – The complete lifecycle cost of the solution.

Example:
Option 2: Upgrade CRM – £50,000 initial cost, £20,000 annual benefit, payback period 2.5 years, ROI 40%.
Option 3: AI-driven CRM – £80,000 initial cost, £35,000 annual benefit, payback period 2.3 years, ROI 56%.

Tips:

• Include assumptions for all calculations such as growth rates, inflation, and discount rate.
• Highlight both tangible and intangible benefits such as reputation, efficiency, or employee morale.
• Conduct a sensitivity analysis to test your financial robustness under different conditions.
• Use a structured business case template to ensure consistency and clarity in your financial data presentation.

APM alignment:
This aligns with APM’s financial management and cost control competencies, ensuring that proposed investments are justified and evidence-based.

Step 5: Assess Risks and Mitigation Strategies.

Every project involves uncertainty. A good business case doesn’t hide risks; it addresses them transparently and presents mitigation plans.

Common categories of risk include:
Strategic: The project might not align with changing business goals.
Operational: Lack of resources, poor planning, or process inefficiencies.
Financial: Underestimated costs or funding shortfalls.
Technical: Technology failure or integration issues.
External: Regulatory changes, supplier dependency, or market shifts.

Example Risks and Mitigations:

• Risk: Delay in supplier delivery. Impact: Medium. Mitigation: Secure multiple suppliers and include delivery penalties in contracts.
• Risk: Insufficient user adoption. Impact: High. Mitigation: Conduct stakeholder engagement and user training.
• Risk: Budget overrun. Impact: High. Mitigation: Add 10% contingency and monitor monthly.

Tips:

• Rank risks by likelihood and impact.
• Use a risk heat map to visualise priorities.
• Identify early warning indicators and assign ownership for each risk.
• Balance realism with reassurance – the goal is to show you’re prepared, not pessimistic.

APM alignment:
This supports APM’s risk management competency, emphasising proactive identification, assessment, and control of threats and opportunities.

Step 6: Outline the Implementation Plan.

Once approval is granted, decision-makers need to know how and when the project will be delivered. This section turns your proposal into a credible roadmap.

Include:

• Project phases or milestones: Break the project into stages with key decision points.
• Timeline: Show start and completion dates, critical milestones, and dependencies.
• Resources: Identify roles, skills, and capacity needed for delivery.
• Governance: Explain how progress will be monitored and reported.

Example Milestones:
Business Case Approval – December 2025.
Procurement and Vendor Selection – February 2026.
Implementation Start – April 2026.
Pilot Completion – August 2026.
Full Go-Live – October 2026.

Tips:

• Use a high-level Gantt chart or visual roadmap to summarise key stages.
• Indicate how quality assurance and communication will be managed.
• Include change control processes if the project scope evolves.

APM alignment:
This links to project planning, governance, and stakeholder management competencies within the APM framework.

Step 7: Present Recommendations and Next Steps.

The final step consolidates your analysis into a clear recommendation. Summarise the preferred option, why it’s the best choice, and what needs to happen next.

Example:
“After evaluating all options, Option 3 (AI-driven CRM Platform) provides the optimal balance between cost, benefit, and risk. It delivers a 56% ROI, a payback period of 2.3 years, and supports our strategic objective to improve customer experience and operational efficiency.”

Next Steps May Include:

• Submitting the business case for executive review.
• Scheduling a stakeholder approval meeting.
• Preparing a detailed project initiation document (PID).
• Assigning a project manager and establishing governance structures.

Tips:

• Keep recommendations short and decisive.
• Reinforce the strategic and financial benefits.
• Close with a positive, forward-looking statement that inspires confidence.

APM alignment:
This aligns with decision-making and stakeholder engagement competencies, demonstrating an ability to influence approval through clear communication and structured reasoning.

Common Mistakes to Avoid When Writing a Business Case.

Many business cases fail not because the idea is poor but because the presentation is weak. Avoid these frequent pitfalls:

• Using excessive technical jargon that confuses decision-makers.
• Failing to include financial justification or measurable outcomes.
• Overlooking risk management.
• Writing too much narrative without evidence or data.
• Ignoring alignment with organisational strategy.

Remember, a successful business case tells a convincing story supported by credible evidence and clear numbers.

Using a Business Case Template for Consistency.

One of the best ways to ensure structure and completeness is to use a business case template. It helps maintain consistency across projects and ensures no key sections are missed.

A good template typically includes:

• Executive summary
• Problem/opportunity statement
• Options analysis
• Financial and risk analysis
• Implementation plan
• Recommendations

Templates can also help less experienced project professionals meet the APM competency standards while maintaining clarity and focus.

Tips to Get Your Business Case Approved.

Even a technically strong and financially justified business case can be rejected if it fails to resonate with its audience. Approval doesn’t rely solely on facts and figures – it also depends on how well your proposal connects to organisational priorities, speaks the language of decision-makers, and demonstrates clear, achievable value. Below are proven strategies to increase your chances of success and gain stakeholder buy-in.

Align with Organisational Goals.
One of the most common reasons business cases are rejected is misalignment with the company’s strategic direction. Make sure your proposal supports key organisational objectives such as growth, efficiency, innovation, or customer satisfaction. Reference relevant corporate KPIs, vision statements, or ongoing initiatives to show that your project contributes to broader success.
Example: Instead of simply stating “This project will improve customer response time,” say, “This project directly supports our strategic goal of enhancing customer satisfaction and retention by improving response time by 30%.”
By making this link explicit, you position your proposal as a strategic enabler, not just an operational improvement.

Keep It Visual and Concise.
Decision-makers are often pressed for time and need to grasp your message quickly. Avoid lengthy paragraphs or overly technical explanations. Instead, use visuals such as charts, graphs, and infographics to present data clearly. Tables can summarise costs, benefits, and risks at a glance, while bullet points help highlight key insights.
A visually structured business case not only improves readability but also signals professionalism and attention to clarity – both of which build confidence in your proposal.

Use Evidence and Data.
Credibility is essential. Every assumption you make should be backed by evidence – whether from internal metrics, market research, or industry benchmarks. Quantify your claims wherever possible.
For instance, instead of saying “The system will save time,” specify “The new system will reduce average processing time by 25%, saving approximately 400 staff hours per month.”
Reliable data gives your business case authority and helps reduce doubts among finance and executive reviewers.

Engage Stakeholders Early.
Getting approval isn’t just about the final document – it’s about the process of collaboration leading up to it. Engage key stakeholders early, including finance teams, operational managers, and potential project sponsors.
By involving them in shaping your proposal, you gain valuable feedback, uncover hidden risks, and build advocates who will support your case during review. Stakeholder engagement also demonstrates transparency and teamwork, qualities that decision-makers appreciate.

Tailor Your Message.
Every decision-maker has unique priorities. A finance director will focus on cost control and ROI, while a CEO may care more about strategic alignment and long-term growth. Adjust your tone and emphasis depending on your audience.
When preparing your executive summary or presentation, highlight the elements that matter most to them – financial viability, risk management, and measurable benefits. The more you speak their language, the greater the likelihood of approval.

Be Realistic.
Avoid the temptation to overpromise on savings, timelines, or benefits. Overly optimistic forecasts can raise red flags and damage your credibility. Instead, base your assumptions on evidence and include reasonable contingencies for risks or delays.
Decision-makers appreciate honesty and balanced judgment. A realistic, well-supported proposal is far more persuasive than an exaggerated one that later fails to deliver.

Additional Success Tips:

• Tell a story: Present your business case as a narrative – from problem to solution to outcome. Storytelling engages your audience emotionally and intellectually.
• Include an executive summary: Summarise the entire case in one page. Executives often read this first, and it may determine whether they read further.
• Show quick wins: If your proposal includes short-term benefits or early milestones, highlight them. Quick wins can strengthen confidence and support phased approval.
• Use clear language: Avoid jargon and unnecessary complexity. Clarity demonstrates mastery of the subject and makes your argument easier to follow.
• Prepare for objections: Anticipate tough questions about costs, risks, or feasibility. Have concise, evidence-based responses ready.

Getting your business case approved requires more than strong content – it demands strategic communication, stakeholder alignment, and credibility. By combining these elements, you not only increase the likelihood of approval but also build trust and influence for future proposals.

Project Proposal Writing and Its Connection to the Business Case.

While project proposal writing and business case development share similarities, they serve different purposes.

A project proposal introduces a new idea or concept, while a business case provides the detailed justification needed for approval.

In practice, the proposal often evolves into a full business case as analysis deepens. Both are essential skills within the APM competency framework, helping professionals turn ideas into actionable, funded projects.

How to Present Your Business Case Effectively.

The way you present your business case can be just as important as the content itself. Even the strongest business case can fail to gain approval if it is poorly communicated. Decision-makers often have limited time and must quickly understand the value, feasibility, and strategic fit of your proposal. Therefore, how you deliver your message can determine whether your project moves forward or not.

Start by tailoring your presentation to your audience. Senior executives are primarily interested in outcomes, risks, and return on investment, while project managers or technical reviewers may want to understand implementation details. Adjust your tone, language, and level of detail accordingly.

A clear structure helps you guide your audience through the key points logically:

1. Begin with the “why.” Start by summarising the problem or opportunity and why it matters to the organisation.
2. Present the options. Briefly explain the alternatives you considered and why your recommended approach is the best one.
3. Highlight the benefits. Emphasise measurable gains such as cost savings, efficiency improvements, or strategic advantages.
4. Discuss the financials. Provide a concise overview of costs, ROI, and payback period – supported by reliable data.
5. Address the risks. Show that you’ve anticipated potential issues and developed realistic mitigation strategies.
6. Conclude with a clear recommendation and call to action.

To make your presentation engaging and professional, incorporate visuals such as charts, graphs, timelines, and cost-benefit comparisons. Visuals help simplify complex data and make your argument more persuasive. Avoid overcrowded slides – aim for one key idea per slide, supported by concise bullet points or figures.

When speaking, be confident, calm, and concise. Use straightforward language and maintain a logical flow. Avoid jargon unless your audience is highly technical. Always rehearse beforehand so you can present within 10–15 minutes while leaving time for discussion.

Be prepared to answer tough questions. Decision-makers may challenge your cost assumptions, timelines, or risk management plans. Respond using evidence and data rather than opinion. Demonstrating that you have done thorough research and scenario planning builds credibility and trust.

Finally, end with a clear summary of the decision you are asking for – whether it’s approval to proceed, funding allocation, or a green light for the next project phase. Reinforce how the project aligns with organisational goals and delivers measurable value.

A well-presented business case not only informs but also persuades. By combining solid evidence, clear visuals, and confident delivery, you greatly increase your chances of securing approval and gaining stakeholder support.

How This Aligns with the APM Competency Matrix.

In the APM Competence Framework, “How to Write a Business Case” falls under the Business Case competency area.

It evaluates a project professional’s ability to:

• Prepare and justify investment proposals.
• Analyse options and assess financial implications.
• Develop a persuasive argument aligned with organisational goals.
• Manage benefits, risks, and assumptions transparently.

Mastering this competency not only improves project outcomes but also strengthens your professional credibility as a project manager.