You almost never send the exact same pack to every audience. The underlying analysis, numbers, and logic should stay consistent, but what you put first, what you emphasize, and how much detail you show must change. This chapter gives you practical patterns for five common audiences—Board, investors, CFO/Finance, Technology/IT steering, and Regulatory/Compliance—plus a simple checklist so you can tailor any case quickly without breaking consistency.
18.1 Board-Ready Pack (Fiduciary & Risk Emphasis)
Boards care about fiduciary duty: long-term value, risk, resilience, and leadership’s ability to execute. They have limited time and see many topics in each meeting. Your business case must be short, sharp, and anchored in what they are accountable for.
Core lens for the Board
- Enterprise value and strategic fit
- Downside and tail risks, resilience, covenant / rating implications
- Irreversibility and lock-in
- Quality and readiness of the management team and governance
- Ethics, reputation, and regulatory posture
Structure for a Board-ready pack
Typically 8–15 pages:
- 1 page – Decision & headlines
- Decision requested (option, funding envelope, key conditions).
- Headline economics (NPV, IRR, payback, or public-sector analogues).
- One or two strategic reasons and one or two major risks.
- 1–2 pages – Strategic context & “why now”
- How this move implements the strategy or protects it.
- Cost of inaction and external drivers (market, technology, regulation).
- How this move implements the strategy or protects it.
- 1–2 pages – Options & recommendation
- Baseline + 2–3 options, key differences and trade-offs.
- Why the recommended option best balances value and risk.
- 2–3 pages – Economics & downside
- Summary of costs, benefits, cash profile, and key metrics.
- Clear downside/stress scenario and impact on covenants or resilience.
- High-level view of working capital, balance sheet, and capital structure impact.
- 2–3 pages – Risk, governance & assurance
- Top 5–7 risks, mitigations, and residual risk vs appetite.
- Governance structure and stage-gates; how the Board stays in control (what they will see when).
- Assurance from Finance, Risk, Audit, Security, etc.
- 1–2 pages – Execution & leadership
- Phasing, critical path, and capacity.
- Leadership team and partners; reasons to believe they can deliver.
What to de-emphasize or move to appendix
- Detailed design, process maps, low-level technical architecture.
- Full risk register (Board only needs top items and residual posture).
- Detailed PMO content (Gantt charts, work breakdowns).
- Line-by-line cost build-ups.
Tone and style
- Direct, non-promotional, fact-based.
- Explicit about trade-offs and uncertainties.
- Clear on what could go wrong and what you will do if it does.
18.2 Investor-Facing Pack (Market, Unit Economics)
Investors focus on capital allocation, growth, and durability of cash flows. They care less about internal governance mechanics and more about the economic engine and competitive position.
Core lens for investors
- Market size, growth, and competitive dynamics
- Unit economics and scalability
- Cash profile and capital efficiency
- Moats: differentiation, switching costs, network effects, regulatory barriers
- Execution track record and milestones
Structure for investor-facing pack
Often 10–20 pages or a memo plus slides:
- Investment thesis & ask
- One-page statement of thesis: where value comes from and what capital enables.
- Amount, instrument (if relevant), and usage of funds.
- Market & problem
- TAM / SAM / SOM (with sensible definitions).
- Pain points, current alternatives, and willingness to pay.
- Solution & differentiation
- What’s different and hard to copy (technology, data, relationships, brand, regulatory licenses).
- Why now (timing / inflection rationale).
- Unit economics & growth model
- CAC, LTV, payback period, gross margins, contribution margins.
- Cohort behavior (retention curves, expansion).
- Capacity and bottlenecks.
- Financial projections & scenarios
- Revenue, margin, cash burn / generation under base, downside, upside.
- Capital efficiency metrics (e.g., revenue / invested capital, cash conversion).
- Path to profitability or improved ROIC.
- Execution & milestones
- Past proof points (pilots, renewals, reference customers).
- Next 12–24 month milestones tied to funding tranches.
What to de-emphasize or move to appendix
- Inner workings of internal governance and steering committees.
- Detailed internal process changes unless they directly affect unit economics.
- Granular phase-by-phase project plans.
Tone and style
- Concise, thesis-driven, heavily supported with data and cohort logic.
- Open about downside cases and how you’d respond (pivot, scale back, re-prioritize).
18.3 CFO/Finance Review Pack (Accounting & Controls)
Finance wants to know whether the numbers are right, policy-compliant, and decision-useful. This is where you go deep on methodology and standards.
Core lens for CFO/Finance
- Integrity and traceability of assumptions and calculations
- Alignment with accounting policies (Capex/OpEx, depreciation, leases, tax)
- Impact on P&L, balance sheet, cash, and covenants
- Sensitivities, scenarios, and risk-adjusted economics
- Control environment around budgets, spend, and benefits
Structure for Finance pack
This can be a more detailed doc or slide deck, often 20–40 pages plus model:
- Summary for CFO
- Decision, recommended option, and headline economics.
- Top 3 modeling judgments and their impact.
- Assumptions & drivers
- Detailed assumptions log (rates, volumes, ramp, pricing, FX, discount rate).
- Sources: internal data, benchmarks, expert views.
- Costing & accounting treatment
- Capex vs OpEx classification; key judgments.
- Depreciation/amortization profiles; lease accounting where relevant.
- Treatment of one-offs and restructuring costs.
- Benefits & value case
- Driver-based benefits models (bottom-up where material).
- Distinction between gross and net bankable savings; attribution rules.
- Risk and uncertainty treatment.
- 3-statement implications
- Incremental P&L, cash flow, and balance sheet views.
- Covenant and rating implications.
- Controls and governance
- Budget control points, approval thresholds, variance management.
- How benefits will be validated and reported by finance.
What to de-emphasize
- Marketing-style narrative; finance cares most about structure and evidence.
- Overly high-level slides with no link to sources; they will want to see the plumbing.
Tone and style
- Technical, precise, policy-aligned.
- Transparent about limitations and approximations.
- Friendly to spreadsheet review (clear mapping between deck and model).
18.4 Technology/IT Steering Pack (Architecture & Security)
Tech and architecture bodies care about feasibility, complexity, and risk in the technology stack, and alignment to standards.
Core lens for Technology/IT steering
- Architecture fit with target state
- Integration, data, and performance
- Security, resilience, and operability
- Technical debt and long-term maintainability
- Vendor risk and lock-in
Structure for Technology/IT pack
12–25 pages, usually slide-heavy:
1. Overview & decision
- Tech decision requested (patterns, platforms, vendors, major design choices).
- How it fits into the broader technology roadmap.
2. Current architecture & pain points
- Simplified view of current stack and key issues (complexity, fragility, cost).
3. Target architecture & patterns
- High-level architecture diagrams.
- Key patterns (APIs, events, microservices vs monolith, data domains).
- Conformance to standards and reference architectures.
4. Integration & data
- Critical interfaces and dependencies.
- Data flows, ownership, and quality considerations.
5. Security, resilience, and operations
- Threat modeling, key security controls, identity & access.
- High availability (HA) and disaster recovery (RTO/RPO).
- Monitoring, logging, observability, and support model.
6. Security, resilience, and operations
- Threat modeling, key security controls, identity & access.
- High availability (HA) and disaster recovery (RTO/RPO).
- Monitoring, logging, observability, and support model.
What to de-emphasize
- High-level financial metrics (they need to exist but won’t be the main debate).
- Detailed change management and HR implications (unless they affect run-operations).
Tone and style
- Clear but not buzzword-heavy.
- Concrete about constraints, trade-offs, and migration sequencing.
- Respectful of existing standards and the people who own them.
18.5 Regulatory/Compliance Pack (Evidence & Traceability)
Regulators and internal compliance/risk teams care about obligations, customer and market integrity, and demonstrable control.
Core lens for Regulatory/Compliance
- Compliance with laws, regulations, and supervisory expectations
- Consumer/customer protection and fairness
- Data protection and confidentiality
- Control design, testing, and monitoring
- Documentation and auditability
Structure for Regulatory/Compliance pack
Often memo-style plus annexes:
- Regulatory context & objectives
- Which laws, rules, or guidance apply.
- What risk or obligation the initiative addresses.
- Design and impact on obligations
- How the solution changes processes, data flows, customer outcomes.
- Impact on existing obligations (e.g., reporting, disclosures, suitability, KYC).
- Control framework
- Key controls, mapped to risks and obligations.
- Control owners, frequency, and testing approach.
- How exceptions will be handled and escalated.
- Customer / public impact
- How customer fairness, consent, transparency, and redress are protected.
- Vulnerable groups or systemic effects, if any.
- Evidence and traceability
- References to policies, procedures, control libraries.
- Test plans or early test results/pilots where applicable.
- Record-keeping and audit trails.
What to de-emphasize
- Strategic “why this is exciting” narrative; this audience is duty-based, not opportunity-based.
- Detailed financials, except where fines or capital/liquidity are concerned.
Tone and style
- Formal, structured, reference-friendly.
- Clear mapping between requirements, risks, and controls.
- Conservative, with explicit acknowledgement of uncertainties and open issues.
18.6 Tailoring Checklist
Use this checklist whenever you spin one base case into multiple packs.
Audience clarity
- I have explicitly written down who this pack is for and what decision they must take.
- I understand their top 3–5 concerns (e.g., risk, EPS, customer impact, regulatory posture).
Ordering and emphasis
- Sections are reordered so that what this audience cares about most appears in the first 3–5 pages.
- Details that this audience does not need are shortened or pushed to appendices.
- The ask is phrased in the language of that audience (e.g., “approve option B and funding envelope of X with gates…” vs “invest Y for Z% IRR…”).
Content selection
- Board: risk, strategy, downside, governance, and assurance are prominent.
- Investors: market, unit economics, cash, and moats are prominent.
- CFO/Finance: assumptions, accounting treatment, and model structure are prominent.
- Tech/IT: architecture, integration, security, and migration are prominent.
- Regulatory/Compliance: obligations, controls, and traceability are prominent.
Consistency across variants
- All variants share the same core numbers (NPV, IRR, payback, total costs/benefits).
- Option names and labels are identical across packs
- Risks, dates, and key milestones are consistent (even if not all are shown everywhere).
- Any conditions or caveats are carried through consistently (e.g., Board approval conditional on control X).
Tone and format
- Length and detail level are proportionate to the forum (shorter and higher-level for Board and regulators, deeper for Finance and IT).
- Jargon is tuned to the audience (avoid technical detail with Board and investors, avoid fluffy marketing with Finance, IT, and regulators).
- Visuals are chosen appropriately:
- Board/Investors: bridges, waterfalls, scenario charts.
- Finance: tables, driver maps, sensitivity charts.
- IT: architecture diagrams, sequence or flow charts.
- Regulatory: requirements-to-controls maps, process diagrams.
Pre-wiring
- Each audience’s gatekeepers (e.g., CFO staff, Chief Risk Officer, CISO, Head of Compliance, Head of IR) have seen the tailored version relevant to them.
- Feedback from one audience that affects facts (not just framing) has been rolled back into all packs.
If you can tick these items, you’re no longer sending “one size fits nobody” decks; you’re running a disciplined, multi-audience approval process from a single, consistent underlying business case.
