How to Present a Business Case to a CFO/Committee (slide outline + narrative flow)

🎯 Overview: What This Guide Covers

• A CFO/committee-ready narrative flow for a business case (what they need to believe).
• A slide outline that turns analysis into a decision, not a data dump.
• How to structure the recommendation so it matches how committees run business case evaluation.
• What to put in the main story vs the appendix (and why).
• How to present benefits, costs, risks, and dependencies without triggering “spreadsheet skepticism.”
• How to keep numbers consistent across versions of the business case report.
• Where Model Reef can help you generate clean exhibits from the same driver logic used in the model.
• How to position your case clearly against common document expectations.

🧩 Before You Begin: Align on Audience, Decision, and Format

Before building slides, confirm three things: (1) the decision being requested (approve, reject, defer, or stage-gate), (2) the evaluation criteria the CFO/committee will use (returns, risk, strategic fit, cash timing, and execution confidence), and (3) the meeting format (10-minute read, 20-minute presentation, or pre-read plus Q&A). Your presentation should match the decision process, not your internal effort. Next, ensure you have a single source of truth for numbers and assumptions. Committee presentations fail when the narrative says one thing, the appendix shows another, and finance finds inconsistencies. Your business case report should already have a clear recommendation, a credible baseline, and net impact logic. Also, confirm who will attend and what they care about-finance, operations, risk, IT, or the sponsor-and tailor the “proof points” accordingly. If you present frequently to finance leaders, borrow the framing used for CFO audiences and finance teams to keep the language and exhibits familiar.

🛠️ Step-by-step implementation

Step 1: 📣 Start with the decision (one slide, one sentence, one number)

Open with the decision and the recommendation in plain language: “Approve Option B to achieve X outcome with Y net value and Z key risks.” CFOs don’t want suspense; they want clarity. Then anchor the recommendation to your business case justification: the return logic, the cash timing, and the strategic fit. Your first slide should answer: what are we deciding, why now, and what happens if we do nothing. Keep the headline metrics limited to the ones that matter (NPV/ROI/payback, cash impact, and execution timing). Then state the three assumptions that make the case true-this signals confidence and invites the right questions early. If you can’t summarise your business case strategy in one sentence, the rest of the deck will feel like “analysis searching for a point”.

Step 2: 🧭 Use a narrative arc (problem → options → proof → risk → ask)

Committees decide through narrative logic, not spreadsheet logic. Use a simple flow: (1) the business problem/opportunity, (2) the options considered, (3) the recommended option and why it wins, (4) the proof (numbers + operational feasibility), (5) the risks and mitigations, and (6) the decision ask and next steps. Keep each section tight and avoid detours. To maintain credibility, show that you considered real alternatives and explain your selection logic. Then present the “why it works” proof: benefit drivers, cost drivers, and the timing of value. If there’s uncertainty, present it as structured scenarios rather than a dense sensitivity table-executives understand scenarios as decision narratives. A clean narrative arc is what turns a business case into an approval conversation rather than an interrogation.

Step 3: 📊 Build the slide outline (10-slide core + appendix)

A practical core outline:

1. Decision & recommendation
2. Why now (context, urgency, constraints)
3. Current state & “do nothing” trajectory
4. Options considered (including why not)
5. Benefits (top 3, with driver logic)
6. Costs & investment profile (one-off vs run)
7. Financial summary (ROI/NPV/payback + cash timing)
8. Risks, dependencies, mitigations (top 5)
9. Implementation plan & governance (who/when/how measured)
10. Decision request & next steps

Then put the detail in the appendix: supporting calculations, benchmark sources, sensitivity ranges, and operational assumptions. This keeps the meeting focused while still giving reviewers a place to validate the work. If you want this to feel executive-grade, design visuals that explain variance and timing at a glance (bridges, waterfalls, trend lines). A consistent executive dashboard approach makes those visuals easier to standardise across cases.

Step 4: 🔍 Anticipate Q&A (and design your appendix to win trust)

Committees ask predictable questions: “What’s the baseline?” “What must be true?” “What breaks the case?” “What’s the cash impact?” “Who owns delivery?”, and “How will we measure benefits?” Build your appendix to answer these quickly, without hunting through spreadsheets. Include: assumption log (top 10), benefit register (metric, baseline, target, owner), cost breakdown (capex/opex/one-off), timeline with stage-gates, and a downside scenario summary. Also include a single “risks and mitigations” slide that shows you’ve thought operationally, not just financially. A strong appendix reduces perceived risk-even if the core case is unchanged-because it demonstrates execution readiness. If you already produce board-level packs, borrow that packaging discipline: short core story, deeper evidence behind it, consistent exhibit formatting. That’s how a business case report earns trust.

Step 5: ✅ Rehearse the decision conversation (govern versions, control edits)

Treat rehearsal as part of the deliverable. Run a 15-minute internal dry run with finance and ops and ask them to challenge the top assumptions. Your goal is to refine the story, not to defend every number. Then lock the version you will present and control edits tightly. Last-minute spreadsheet changes are a common source of inconsistencies that damage credibility. Use a visible change log: what changed, why, and what it did to outcomes. If multiple contributors are involved, define one owner for the deck and one owner for the model so accountability is clear. Tools that support real-time collaboration and governed review cycles reduce the chaos of “final_v7_really_final” workflows. When your narrative and numbers stay consistent, your business case feels executive-ready rather than fragile.

⚠️ Tips, Edge Cases & Gotchas

• Don’t lead with methodology. Lead with decision and impact, then offer method in the appendix.
• Avoid “spreadsheet screenshots.” Use simple visuals and summary tables that tell a story.
• Make uncertainty explicit. A committee trusts ranges more than hidden fragility.
• If your case is strategic (risk/compliance), present the “cost of inaction” and trigger thresholds clearly.
• If benefits depend on behavioural change, show adoption ramp and who drives adoption; otherwise benefits will be discounted.
• Keep your business case example tight: one scenario that makes the value feel real, not hypothetical.
• Use version discipline. CFOs often challenge not because the idea is bad, but because numbers move between drafts. A transparent review trail prevents “which version is correct?” conversations from hijacking the meeting.

🧪 Example / Quick Illustration

Instead of presenting 20 slides of detail, open with a single decision slide: “Approve rollout to reduce processing cost by $X/year with payback in Y months.” Then show one bridge: baseline cost → cost after change → net savings (with the top two drivers only). In the appendix, include a benefits register and the downside case so the committee can pressure-test assumptions without derailing the meeting. If you’re using Model Reef, generate the exhibit directly from the same driver logic that produces the forecast-so the chart and the numbers always agree. Then share a read-only version of the outputs for pre-read review and keep a single “presented version” locked for the meeting. When stakeholders can validate the logic safely, the discussion shifts from “do we trust the spreadsheet?” to “do we want this outcome?”

🙋 FAQs

🚀 Next Steps

To get approved faster, standardise your pack: one clear recommendation slide, one financial summary, one risk slide, and a governed appendix that answers predictable questions. Then make the workflow repeatable-so you’re not reinventing the structure every time you need funding. If you want a cleaner way to keep narrative, drivers, and outputs aligned, Model Reef can help you generate consistent exhibits from driver-based logic, compare scenarios cleanly, and reduce version chaos as stakeholders iterate. If you want to see how this looks end-to-end in a real workflow, point stakeholders to a product walkthrough before the meeting so Q&A starts at a higher baseline.