A business case succeeds or fails as much on audience fit as on analytical rigor. The same numbers, narrated differently, can read as compelling to a boss yet feel thin to a board, or sound persuasive to an investor but raise red flags with a regulator. This chapter shows you how to identify the decision‑makers and influencers who matter, tailor the narrative to what they need, and deliberately socialize the case so the formal meeting becomes a decision—not a discovery session. You will learn the primary audiences and their lenses, how to map stakeholders and influence lines, what to emphasize for each audience, how to pre‑wire effectively, and who owns what in a disciplined review cadence.
3.1 Primary Audiences: Boss, Executive Committee, Board, Investors, Regulators
Your boss (direct manager or P&L leader).
Your boss is the first and most pragmatic gate. Their lens is execution credibility, immediate impact on objectives, and reputational risk for their area.
- What they value: Clear ask, fit to current priorities, quick wins, resource realism, and whether you have pre‑aligned peers who will be affected.
- Hot buttons: Hidden run‑rate costs on their budget, dependency on other managers who are not aligned, optimistic ramp assumptions, or initiatives that distract from quarterly goals.
- What to show: One‑page executive summary, a crisp costs/benefits bridge, top three risks with mitigations, and the first 90 days of the plan.
- Approval conditions to anticipate: Headcount caps, tranche‑based funding tied to milestones, or a request to pilot before scaling.
Executive committee (ExCo) or enterprise leadership team.
The ExCo adjudicates priorities across functions and portfolios. Their lens is strategic fit, capacity constraints, and the opportunity cost versus other initiatives.
- What they value: Option comparability, portfolio interactions, cross‑function dependencies, and the path to de‑risk before scale.
- Hot buttons: Double counting benefits across programs, capacity bottlenecks in scarce roles, technology debt compounding, or initiatives that violate guardrails (risk appetite, leverage, ESG commitments).
- What to show: Options grid with selection criteria, value driver tree, resource/capacity view, and how the case fits into the current portfolio roadmap.
- Approval conditions to anticipate: Re‑sequencing relative to other initiatives, shared services capacity gating, or a mandated joint governance model.
Board of directors (or investment committee of the board).
Boards focus on fiduciary duty: risk, returns, resilience, and leadership’s preparedness to execute. They rarely want operational depth; they want assurance and clarity.
- What they value: Clarity of the ask, honesty about risk and residual exposure, alignment with strategy and risk appetite, and evidence that management has staged the plan with clear gates.
- Hot buttons: Blind spots (cyber, regulatory, reputational), quality of the team and vendors, financing structure, and whether the downside is survivable without imperiling covenants or commitments.
- What to show: High‑level economics (NPV, IRR, payback) with scenarios, top risks with mitigations and owners, stage‑gate plan and funding tranches, and independent reviews (finance, risk, audit).
- Approval conditions to anticipate: Additional independent assurance, tighter risk controls, lower initial scope, or explicit stop‑loss triggers.
Investors (equity, lenders, grantors, donors).
Investors bring a capital allocation lens. Equity investors weigh growth, unit economics, and competitive advantage; lenders care about downside protection and cash coverage; grantors/donors focus on outcomes and accountability.
- What they value: Coherence of the investment thesis, unit‑level drivers, cash profile and covenants, and independent validation of assumptions. In public or philanthropic settings, clear outcome metrics and attribution.
- Hot buttons: Overly top‑down benefits, ignored working capital or tax effects, vague path to scale economics, or reports without measurement plans.
- What to show: Unit economics, customer acquisition and retention drivers, cash flow sensitivities, covenant headroom, and external benchmarks that anchor comparables. For grants, logic models and outcomes tracking.
- Approval conditions to anticipate: Performance milestones tied to disbursements, reporting cadence, or contingency reserves.
Regulators and oversight bodies.
Regulators are not investors; their lens is compliance, safety, consumer protection, continuity, and data/privacy integrity. They focus on whether the initiative upholds obligations and reduces risk.
- What they value: Clear mapping from initiative to regulatory requirements, risk controls, privacy/security by design, and change management that sustains compliance.
- Hot buttons: Ambiguity in responsibilities, untested controls, data lineage gaps, or optimistic timelines that jeopardize obligations.
- What to show: Compliance impact summary, risk register with control owners, independent assessments, and how metrics will be monitored and reported.
- Approval conditions to anticipate: Prior approvals, staged rollouts with validation, reporting obligations, or periodic audits.
Cross‑cutting audiences. Although not listed in the subsection title, CFO/Finance, Risk/Compliance, Architecture/IT, Legal/Privacy, Procurement, and PMO are gatekeepers in many organizations. Treat them as principal audiences during development even if they are not the final approvers.
3.2 Stakeholder Mapping and Influence Lines
Approvals hinge on more than the people in the room. Decisions are shaped by “influence lines”—the informal network of chiefs of staff, controllers, solution architects, risk analysts, and trusted deputies who pre‑read materials and brief principals. Map the network deliberately.
Stakeholder mapping—step‑by‑step
- Define the decision body and veto points. Identify the formal approver(s) and any function with a hard veto (e.g., Security, Legal, Safety).
- List stakeholders by role, not just name. Start with the sponsor, economic buyer, finance partner, risk/compliance lead, architecture authority, legal/privacy, procurement, PMO, benefit owners, and data owners.
- Assess power and interest. For each stakeholder, gauge decision power (approval/veto/influence), interest level (high/medium/low), and stance (support/neutral/skeptical).
- Surface influence lines. Ask: who briefs the approver; whose analyst runs numbers; who writes committee notes; who preps the risk memo. Add these names; they are leverage points.
- Capture goals and concerns. For each stakeholder, note their success metrics, constraints, risk appetite, and likely objections.
- Decide on engagement mode. Choose the most effective mechanism: one‑to‑one brief, small workshop, written pre‑read, or quick desk‑check for facts.
- Record commitments and gaps. After each touchpoint, log what they agreed to, what evidence they need, and who owes follow‑ups.
- Revisit weekly. As facts evolve, update stance and influence. Stakeholders shift when their peers endorse or when new risks surface.
Stakeholder profile—lightweight template
- Name & role
- Decision right & veto? (approve, recommend, influence, veto)
- Interest & stance (H/M/L; support/neutral/skeptical)
- What they care about (top three issues)
- Evidence they trust (internal data, customer interviews, external benchmarks)
- Likely objections (list)
- Influence line (who briefs them; whose analysis they rely on)
- Engagement plan (format, owner, date)
- Commitments & follow‑ups (notes)
Common mapping mistakes
- Confusing authority with influence. A COO may defer to the CISO on cyber; winning the CISO is winning the COO.
- Ignoring deputies. Chiefs of staff, controllers, and enterprise architects often gate what their leaders ever see.
- Underestimating cross‑initiative politics. Benefit owners elsewhere may see your case as competition; involve them early and agree attribution.
- One‑and‑done engagement. Stance evolves; absence of update can reverse earlier support.
3.3 Tailoring Expectations by Audience
You do not change the facts; you change the order, emphasis, and exhibits to meet your audience’s decision needs. Use the following tailoring guidance.
For your boss
- Lead with execution and risk. Show the first 90 days, named owners, and how you will manage disruption to current goals.
- Show budget clarity. Make the run‑rate impact visible; note what you will stop doing or defer.
- Bring the team. If possible, have benefit owners or the finance partner present; this signals readiness.
For the executive committee
- Start with portfolio impact. Where does this initiative rank on value vs. risk vs. capacity; what gets re‑sequenced.
- Make trade‑offs explicit. If speed reduces scope or increases cost, quantify the trade‑off; if you defer, quantify the cost of delay.
- Use integrative exhibits. Options grid, value driver tree, resource heat map, and a one‑slide risk dashboard resonate.
For the board
- Stay at altitude, answer the why. Keep to decision, economics with scenarios, top risks/controls, and governance.
- Show independent challenge. Identify who reviewed the model and risks; include a brief on residual risk and why it is tolerable.
- Define stop‑loss. State conditions that will trigger pause/pivot and how the board will be informed.
For investors
- Unit economics and cash durability. CAC/LTV, contribution margin, variable vs. fixed cost dynamics, cash runway, and covenant headroom.
- Comparables and defensibility. External benchmarks, barriers to imitation, switching costs, network effects where relevant.
- Milestones tied to funding. Clear performance gates for each tranche or round.
For regulators
- Compliance by design. Demonstrate how requirements are embedded in process/technology, not bolted on.
- Controls and monitoring. Control owners, testing schedule, incident response, and reporting cadence.
- Customer and public impact. How risks to consumers/citizens are prevented or mitigated; how complaints or incidents will be handled.
Formatting and tone by audience
- Boss: Conversational, concrete; 5–7 slides or a 2–3 page memo.
- ExCo: 10–15 slides with strong synthesis exhibits and a short memo.
- Board: 6–10 slides plus an executive memo; appendices for detail.
- Investors: Narrative memo with analytical exhibits; emphasize assumptions and comparables.
- Regulators: Structured memo tied to specific requirements; plain language; references to controls and policies.
Language to use—and avoid
- Use: “ask,” “decision,” “owner,” “baseline,” “residual risk,” “stage gate,” “evidence shows,” “sensitivity indicates.”
- Avoid: Marketing adjectives (“game‑changing”), vague nouns (“synergies”) without mechanisms, and passive voice that hides accountability.
3.4 Pre‑Wiring and Socialization Plan (Checklist)
Pre‑wiring turns unknowns into knowns and objections into refinements. Treat it as a structured campaign, not ad‑hoc chats. Use this checklist.
A. Plan the path (T‑20 to T‑15 working days before the decision)
- Confirm the approver and the decision date; lock submission deadlines and page limits.
- Identify veto points (security, legal, safety) and time their reviews ahead of others.
- Draft a pre‑wire map: boss → finance → risk/compliance → architecture/IT → economic buyer → ExCo/Board secretary.
B. Align on facts early (T‑15 to T‑10)
- Share the baseline and assumptions log with finance; agree on the discount rate, horizon, and accounting treatments.
- Validate key operational assumptions (capacity, vendor lead times) with owners; record their sign‑off.
- Hold a short risk workshop to build the top‑risk list and proposed mitigations.
C. Shape the narrative (T‑10 to T‑7)
- Draft the executive summary and options grid; socialize with the boss and the economic buyer.
- Ask each stakeholder: “What would stop you from approving this?” Capture the answer verbatim.
- Update the model and narrative to address material objections; document any residual disagreements.
D. Independent challenge (T‑7 to T‑5)
- Run a red‑team review with a senior peer or finance controller; invite them to break the case.
- Close the loop with risk/compliance; confirm controls, privacy, and security status.
- If needed, seek an external benchmark or vendor quote refresh to shore up weak estimates.
E. Finalization and submission (T‑5 to T‑3)
- Freeze numbers; run a consistency check—every number matches across memo, slides, and appendices.
- Prepare a pre‑read: executive summary, options grid, economics summary, risks, delivery plan, and the ask.
- Confirm agenda and time allocation with the secretary/chair; plan who will speak to which page.
F. Pre‑decision touchpoints (T‑3 to T‑1)
- One‑on‑one with the economic buyer; verify comfort and conditions for support.
- Quick desk‑check with any remaining skeptics; clarify what changed since their last view.
- Rehearse the opening two minutes and the top ten anticipated questions with your team.
G. During and after the meeting (T‑0 to T+2)
- Open with the ask and the three headlines (economics, risk, readiness).
- Capture conditions and actions in real time; confirm owners and dates out loud.
- Within 24 hours, circulate decision minutes and update the benefits tracker and governance plan accordingly.
Pre‑wiring etiquette
- Keep pre‑reads short and purposeful; aim for 5–7 pages with a clear “what we want from you” note.
- Treat every meeting as a chance to learn; never argue a stakeholder out of their concern—evidence should do the work.
Close loops. If you promised a change or analysis, deliver it promptly and highlight it in the final pack.
3.5 Roles, Responsibilities, and Review Cadence
Clarity of roles prevents slow drift, late surprises, and accountability gaps. Below are the essential roles in a robust business case process and the cadence that ties them together. Use this to set expectations on day one.
Core roles
- Sponsor (economic buyer). Owns the problem/opportunity, champions the case, is accountable for outcomes, and has the standing to secure resources. Approves scope changes between gates.
- Case lead (author). Orchestrates the work, owns the narrative, coordinates analysis and stakeholder input, and ensures version control. Acts as a single point of contact.
- Finance partner (CFO staff or FP&A). Co‑owns the model structure, validates assumptions and accounting treatments, runs sensitivities, and signs off on economics.
- Risk & compliance lead. Identifies regulatory, privacy, security, safety, and conduct risks; defines controls; confirms residual risk and monitoring.
- Architecture/IT authority. Confirms technical feasibility, integration impacts, and alignment with standards; highlights technical debt and critical dependencies.
- Legal & privacy counsel. Flags contractual, IP, liability, data protection, and regulatory issues; drafts approval conditions if needed.
- Procurement lead. Validates vendor strategy, sourcing timelines, commercial terms, and total cost of ownership; ensures comparability of quotes.
- PMO/program lead. Crafts the delivery roadmap, milestones, critical path, and resource plan; sets the reporting cadence and benefits realization plan.
- Benefit owners. Senior managers who commit to capturing specific benefits; they own the KPIs, baselines, and targets and report progress post‑approval.
- Data & analytics lead. Sources internal/external data, manages the assumptions log, and ensures reproducibility.
- Red‑team reviewer (independent). Challenges the model and narrative; tests for blind spots and optimism bias.
- Committee secretary/board liaison. Manages submission standards, agendas, time allocation, and minute‑keeping; your ally for process discipline.
RACI without a table—how to think about it
- Approve: Sponsor, decision body (boss/ExCo/board).
- Accountable: Sponsor (outcomes), Case lead (document and process quality).
- Consulted: Finance, Risk/Compliance, Architecture/IT, Legal/Privacy, Procurement, PMO, Benefit owners, Red‑team.
- Informed: Adjacent initiative leads, internal audit, communications, HR (if workforce impact).
Review cadence—recommended timeline
- Week 1 (or T‑20 to T‑15): Kick‑off and scoping.
- Align on the decision, ask, scope, and success metrics.
- Establish the assumptions log, data plan, and model structure.
- Map stakeholders and influence lines; schedule pre‑wires.
- Week 2: Options and baseline.
- Define options and evaluation criteria.
- Build the baseline with finance; agree horizon and discount rate.
- Early risk workshop to surface top risks and controls.
- Week 3: Economics and draft narrative.
- Populate costs/benefits; run initial sensitivities.
- Draft executive summary and options grid.
- First sponsor/boss review; adjust based on feedback.
- Week 4: Challenge and finalize.
- Red‑team review with finance controller or senior peer.
- Confirm controls with risk/compliance and architecture sign‑offs.
- Freeze numbers; QA consistency across deck/memo/appendix.
- Submit pre‑read and run final pre‑wires with approvers.
- Decision week (T‑0).
- Deliver the meeting; secure the decision and conditions.
- Publish minutes with actions, owners, due dates.
- Post‑decision (T+7 to T+30).
- Mobilize: stand up governance cadence, benefits tracking, and stage‑gate criteria.
- Baseline KPIs and begin reporting.
- Close any approval conditions (e.g., additional assurance, vendor terms).
Stage‑gate pattern (for larger or riskier initiatives)
- Gate 0—Discovery approval. Limited funding to reduce uncertainty; exit criteria include validated problem, initial design/architecture, and measured signals from tests or pilots.
- Gate 1—Pilot approval. Funding to test in a controlled environment; exit criteria include demonstrated effectiveness, operational readiness, and refined economics.
- Gate 2—Scale approval. Funding to roll out broadly; entry requires meeting Gate 1 exit criteria and securing capacity; exit criteria tie to benefits realization milestones.
- Gate 3—Sustain/optimize. Transition to BAU with run‑rate funding; benefits variance analysis drives optimization or sunsetting decisions.
Cadence mechanics that prevent failure
- Standing weekly case working session (30–60 minutes) with the case lead, finance, PMO, and data lead—decision log updated each time.
- Bi‑weekly sponsor check‑in to resolve cross‑functional blockers quickly.
- Monthly portfolio review (for ExCo/PMO environments) to test interdependencies and capacity conflicts.
- Quarterly benefits review post‑approval, co‑led by finance, to reconcile actuals to the case and adjust forecasts.
Quality gates and artifacts per gate
- Model sign‑off by finance (structure and arithmetic) before external circulation.
- Risk sign‑off documenting residual risk and control owners.
- Architecture note confirming standards and integration dependencies.
- Procurement memo on sourcing strategy and vendor comparability.
- Benefits register with named owners, baselines, targets, and cadence.
Decision minutes—minimum content to record
- Decision outcome (approve/deny/iterate) and funding amount/tranches.
- Conditions (assurance, controls, scope limits, reporting).
- Action items with owners and dates.
- KPIs to be tracked and first reporting date.
- Next gate or review date.
