This playbook is designed to get you to a decision‑grade business case fast. Use it when you need to marshal facts, quantify value, present options—including doing nothing—and secure a clear “approve/deny/iterate” decision with funding and ownership. If your deadline is imminent, read this chapter end‑to‑end, complete the Quick‑Start Checklist, and draft the Minimum‑Viable Business Case (MVBC) outlined in 1.5. Then deepen the sections using the step‑by‑step chapters referenced in the Table of Contents. If you have more time, follow the five‑stage workflow in 1.3 to build a robust, CFO‑ready case with no surprises at approval.
Two principles underpin everything here:
- Decision‑grade over encyclopedic. Your goal is a high‑quality decision, not a comprehensive report.
- Pre‑wire, then decide. Socialize the logic and numbers with stakeholders before the formal meeting, so the meeting is a decision, not a debate.
1.1 Who This Guide Is For
This guide targets practitioners who must produce business cases that withstand executive, board, or investor scrutiny:
- People leading or sponsoring change: general managers, product leaders, operations heads, CIO/CTO deputies, transformation leads.
- Individuals who must bless the numbers: finance business partners, FP&A managers, CFO staff.
- Program and portfolio leaders: PMO directors, portfolio managers, investment committee secretariats.
- Founders and intrapreneurs: startup CEOs, venture leads, incubator heads inside large enterprises.
- Public sector and non‑profits: leaders who must justify funding using cost–benefit, outcomes, and societal value.
What you should already know. You have basic familiarity with the concept of a business case and can work with spreadsheets. You’ve read cases before and understand financial metrics at a working level (NPV, IRR, payback). You can convene subject‑matter experts and stakeholders.
What you will get. A practical way to: (i) frame the decision, (ii) build options and quantify value, (iii) craft the narrative and economics, (iv) pre‑wire stakeholders, and (v) secure approval and mobilize.
What this guide is not. It is not an academic treatise, a procurement manual, or a substitute for legal/regulatory advice. It won’t make the decision for you; it will make the decision easier to take.
1.2 When You Need a Business Case (Decision Triggers)
You need a formal business case when the decision is material, irreversible, cross‑functional, or externally accountable. Use the triggers below. If two or more light up, prepare at least the MVBC in 1.5.
- Material spend or commitment. CapEx, OpEx, or vendor contracts above threshold; multi‑year commitments; headcount increases tied to new capabilities.
- Irreversibility or lock‑in. Architecture choices, long‑term leases, decommissioning legacy platforms, strategic partnerships.
- Cross‑functional impact. Dependencies across tech, operations, commercial, finance, risk/compliance, HR, or multiple geographies.
- External scrutiny. Board, investors, lenders, regulators, audit, grants, or public funding with formal justification requirements.
- Portfolio prioritization. Competing initiatives; need to sequence work over scarce capital or capacity.
- Market‑moving or reputational risk. Customer impact, brand exposure, ESG implications, cyber/privacy risk.
- New revenue logic. Entering new markets, product category expansion, major pricing or channel changes.
- Regulatory/compliance response. Mandates, consent decrees, security standards, or safety requirements.
- Budget cycle or replan. Annual plan, rolling forecast, or midyear correction requiring a reallocation of funds.
- Previous case aging. Assumptions stale, costs shifted, or scope drift—your original approval no longer reflects reality.
When a full case may be overkill. If the decision is truly low risk, reversible, and within a single function’s budget, a one‑page decision memo can suffice. But set a stop‑loss (time/cost limit) and log assumptions; if scope or risk grows, upgrade to the MVBC.
1.3 The 5‑Stage Workflow at a Glance
This workflow minimizes rework, aligns stakeholders early, and produces a crisp, CFO‑ready case. Timebox each stage; don’t aim for perfection before moving forward.
Stage 1 — Frame & Align
Purpose: Define the decision, value at stake, boundaries, and success criteria.
Key questions: What problem/opportunity? Why now? Who decides? What does “good” look like? What’s out of scope?
Core activities:
- Draft a one‑page Case Intent (decision to be taken, value hypothesis, initial scope, success metrics).
- Identify audiences and decision paths (manager, CFO, committee, board).
- Capture baseline (status quo costs/benefits, performance, risk).
- Build an initial assumptions log and risks list.
Outputs: Case Intent, stakeholder map, baseline definition, assumptions log version 0.1.
Common pitfalls: Solution bias, vague success metrics, invisible stakeholders.
Stage 2 — Shape Options & Value Drivers
Purpose: Generate credible alternatives, including the “do nothing” baseline, and articulate how value is created.
Key questions: What are the viable options (build/buy/partner; scope variants)? What drives benefits (revenue, cost, risk)?
Core activities:
- Build an options set (including scope and service levels).
- Construct a value driver tree linking actions to financial and non‑financial outcomes.
- Define evaluation criteria (strategic fit, feasibility, risk, speed, economics).
- Run quick validation (expert interviews, customer/stakeholder touchpoints).
Outputs: Shortlist of options, value driver tree, selection criteria.
Common pitfalls: False precision on benefits; ignoring feasibility or capacity constraints.
Stage 3 — Build the Economics & Risks
Purpose: Quantify costs and benefits with scenarios, and make risk explicit.
Key questions: What does each option cost? What benefits are attributable and when do they ramp? How sensitive are the results?
Core activities:
- Stand up a financial model with clear drivers, sources, and version control.
- Quantify benefits (revenue uplift, margin, cost takeout, risk reduction) and costs (CapEx, OpEx, one‑time, run‑rate).
- Run sensitivity and scenario analyses; calculate NPV, IRR, payback, and risk‑adjusted returns.
- Build a risk register with mitigations and residual risk.
Outputs: CFO‑reviewed economics, scenarios, and risk register.
Common pitfalls: Double counting benefits; ignoring working capital; optimistic timelines.
Stage 4 — Plan Delivery & Governance
Purpose: Prove you can execute and realize the benefits.
Key questions: Who will do what, when, with which resources? What dependencies and vendor choices exist? How will benefits be tracked?
Core activities:
- Develop a roadmap with milestones, exit criteria, and critical path.
- Define organization & governance (roles, decision rights, cadence).
- Outline resourcing (internal capacity, vendor needs, procurement approach)
- Prepare change management and communications plan.
- Establish measurement & benefits tracking (KPIs, baselines, data sources).
Outputs: Implementation plan, governance model, measurement plan.
Common pitfalls: Underestimating change effort; unclear ownership; missing vendor lead times.
Stage 5 — Write, Pre‑Wire & Decide
Purpose: Craft the narrative, socialize it, and secure the decision.
Key questions: What is the ask? Why this option now? What risks remain and how are they managed?
Core activities:
- Write the executive summary and assemble the case pack (main document + appendices + model).
- Pre‑wire: walk key stakeholders through the numbers and risks; refine based on feedback.
- Run a red‑team challenge for logic and numbers; complete submission QA checks.
- Present for decision; document the outcome, conditions, and next steps.
Outputs: Approved/declined/iterate decision; funding release; accountability assigned.
Common pitfalls: New information surfacing in the meeting; unclear ask; sloppy version control.
1.4 Quick‑Start Checklist
Use this when you need momentum today. Print it and tick items as you go.
- Define the decision and the ask. Write one sentence: “We are asking [decision body] to approve [option] at [cost] to realize [benefit] by [date].”
- Clarify success criteria. List the three KPIs that will prove the decision worked (e.g., NPV ≥ X, payback ≤ Y months, risk reduced by Z).
- Confirm governance path. Who must approve? What gates and deadlines? Put dates in your calendar.
- Map stakeholders. Identify the economic buyer, influencers, users, risk/compliance, and finance. Note their likely concerns.
- Capture the baseline. Document current performance and costs, with sources and dates.
- Draft the options set. Include Do Nothing (status quo), Option A (minimal viable), Option B (recommended), Option C (expanded scope).
- Sketch the value driver tree. Link activities to revenue, cost, and risk outcomes; highlight top three drivers.
- Stand up the model. Create a clean driver‑based workbook with tabs for inputs, calculations, outputs, and a change log.
- Quantify costs. Separate one‑time vs. run‑rate; CapEx vs. OpEx; include internal effort and vendor spend.
- Quantify benefits. Use attributable, time‑phased estimates with ramp profiles; avoid double counting.
- Run sensitivities. Vary top three drivers; show impact on NPV and payback.
- Build the risk register. Identify top risks, likelihood/impact, mitigation, and residual risk.
- Outline delivery. Milestones, critical path, required roles, and vendor plan; add exit/stop‑loss criteria.
- Draft the executive summary. One page: decision, options, economics, risks, plan, ask.
- Pre‑wire finance. Review assumptions and metrics with your finance partner or CFO staff.
- Pre‑wire risk/compliance. Validate controls, privacy/security, regulatory touchpoints.
- Pre‑wire the economic buyer. Walk through the story; note objections; refine.
- QA the pack. Check math integrity, version control, footnotes, and consistency of numbers across sections.
- Prepare the decision meeting. Agenda, time allocation, exhibit order, anticipated questions, backup materials.
- Document the outcome. Decision, conditions, funding release schedule, benefit owners, and next steps.
If you can’t complete all steps, ensure you do 1–8 and 14–17. Those are the minimum to avoid surprises and secure a decision.
1.5 Minimum‑Viable Business Case Template (Overview)
When time is short, produce an MVBC: a 5–7 page narrative or deck, supported by a driver‑based model and a compact appendix. It must be tight, sourced, and decision‑ready—no filler.
MVBC sections and what to write
- Decision & Headline (½ page).
- Purpose: Make the ask unmistakable.
- Write: “Approve [option] for [amount] to achieve [value] by [date].” State top three headlines: NPV, payback, IRR (or public‑sector equivalents), and one strategic rationale. Add a one‑line “why now.”
- Problem/Opportunity & Why Now (½ page).
- Purpose: Establish context and urgency.
- Write: Two or three sentences on the pain/opportunity, size of prize, and consequences of inaction. Include 1–2 facts with sources.
- Options Considered, Including Do Nothing (¾ page).
- Purpose: Show you explored credible alternatives.
- Write: Shortlist 3–4 options. For each: intent, scope, major dependencies, pros/cons. Explicitly include Do Nothing as the base case.
- Recommended Option & Scope (½–1 page).
- Purpose: Show why this option wins.
- Write: Scope boundaries (what’s in/out), core design choices (build/buy/partner), alignment to strategy and constraints, key dependencies, and why this option dominates on criteria.
- Economics Summary (1 page).
- Purpose: Bring the numbers to the foreground.
- Write: A simple chart or bullet summary of total costs (CapEx/OpEx, one‑time/run‑rate), total quantified benefits (by driver), NPV/IRR/payback, and 2–3 sensitivity results (what moves the case). Include the time horizon and discount rate. Call out any non‑financial benefits that matter to decision‑makers.
- Risks, Controls & Residual Exposure (½ page).
- Purpose: Prove risk is understood and actively managed.
- Write: Top five risks, mitigations, and residual risk statements. Note regulatory/privacy/security coverage and any gating dependencies.
- Delivery Plan & Governance (½–1 page).
- Purpose: Demonstrate executability.
- Write: Phases, milestones, exit/stop‑loss criteria, critical path, named roles (benefit owners, workstream leads), key vendor steps, and cadence (steering, KPI reviews).
- Measurement & Benefits Realization (¼–½ page).
- Purpose: Show how outcomes will be tracked and realized.
- Write: KPIs, baselines, targets, data sources, review cadence, and who owns each benefit.
- The Ask & Next Steps (¼ page).
- Purpose: Make closing the decision easy.
- Write: Decision required, funding release schedule (e.g., tranche by stage gate), any pre‑conditions, and immediate Day‑0/30/90 actions.
- Appendix (as needed, kept lean).
- Include: Assumptions log, detailed model outputs, vendor quotes, legal/privacy confirmations, architecture diagram, and sensitivity tables. Everything referenced in the main body must be source‑linked here.
MVBC quality bar
- Traceability. Every number has a source and owner; assumptions are dated and version‑controlled.
- Comparability. Options are evaluated on the same horizon and metrics; base case clearly stated.
- Proportionality. The depth of analysis fits the decision size and risk.
- Clarity. Plain language, minimal jargon, consistent terminology; one idea per sentence; one message per exhibit.
- Integrity. The executive summary can be read alone and still support a decision; no contradictions across sections.
MVBC formatting guidance
- Keep the main body to 5–7 pages (or 10–12 slides) with an executive summary first.
- Use driver‑based exhibits (value driver tree, cost/benefit waterfall, sensitivity tornado) to communicate the economics succinctly.
- Put detail in the appendix; don’t bury the decision in backup.
- Maintain document hygiene: version number, date, owner, and distribution list.
How to proceed from here
- Use the Quick‑Start Checklist to create your MVBC.
- As soon as you have a working draft, pre‑wire finance, risk, and the economic buyer.
- If the decision is large or high‑risk, expand your case using the five‑stage workflow: deepen options, economics, delivery, and governance, then finalize the decision pack using the step‑by‑step chapters.
