Most of the playbook assumes a “standard” corporate investment case: reasonable data, normal confidentiality, single-entity governance, and commercial objectives. In reality, you will often face edge cases: very little data, highly sensitive or market-moving proposals, cross-border complexity, or public/mission-driven decisions.
This chapter gives you practical patterns for handling those situations without breaking the discipline of a good business case.
23.1 Low-Data/High-Uncertainty Contexts
Innovation, new markets, early-stage technology, crisis response, and some ESG or regulatory changes often fall into the “low data, high uncertainty” bucket. The temptation is either to give up on quantification or to pretend you know more than you do. You need a third way.
Shift from point estimates to ranges and hypotheses
Instead of asking, “What is the benefit?” ask, “What is a plausible range and what would have to be true for this to be attractive?”
- Use ranges for key drivers (e.g., adoption 10–40%, price uplift 1–5%, cost reduction 5–15%).
- Model base, conservative, and ambitious cases explicitly—not hidden in a single, “averaged” number.
- Be transparent: label ranges as such in both model and narrative.
Use analogs and precedents carefully
Where you lack direct data:
- Look for adjacent precedents: similar products, markets, channels, or initiatives inside or outside your firm.
- Adjust for differences: smaller market, different price points, cultural or regulatory distinctions.
- Treat analogs as sanity checks, not as precise predictors.
You can say, “Comparable initiatives have seen 15–25% improvement; we are assuming 10–15% reflecting X and Y differences.”
Design “learn first, scale later” cases
For genuinely new bets, your case should often be explicitly staged as a learning journey:
- Stage 1 (Discovery / MVP): modest spend to validate core customer behavior and unit economics.
- Stage 2 (Pilot / limited rollout): scale to a few markets / segments; refine economics and feasibility.
- Stage 3 (Scale): major rollout only if pre-defined learning thresholds are met.
The business case then justifies Stage 1 and 2, not the entire eventual vision. Your ask becomes: “Approve this learning investment and option, not full-scale commitment.”
Express “value of information”
Where possible, articulate:
- What key uncertainties you aim to reduce.
- How the proposed tests will improve decisions (e.g., avoid a bad $50m bet by spending $3m on structured learning).
- What you will do if results are ambiguous (tighten test design, run second wave, or stop).
This makes management more comfortable with spending money in the face of uncertainty: the investment buys insight and options, not just assets.
23.2 Confidential or Market-Moving Proposals
Some cases, especially in M&A, pricing, strategic partnerships, restructuring, and sensitive tech or data moves, can move markets, affect competitors, or carry legal exposure if information leaks.
Tighten access and versioning
- Define a need-to-know list and stick to it; limit distribution of full packs and models.
- Use clear confidentiality markings on documents (e.g., “Highly Confidential – Project X – Limited to [named group]”).
- Maintain a short list of where files reside and who has access; avoid uncontrolled email forwarding and local copies.
Split information by layer
Use a layered information architecture:
- Core decision pack (to the full decision body): includes economics, risks, recommendation—but may aggregate or anonymize certain details (e.g., counterparty names, detailed valuation).
- Annex / secure room materials (smaller group): detailed target analysis, negotiations, sensitive scenarios, internal politics.
- Verbal only elements: in some cases, the most sensitive angles are better handled verbally in-room, with minimal written trace, consistent with legal guidance.
Always align with Legal and Compliance on how far you can reasonably go in minimizing written detail; regulators and auditors still need enough traceability.
Coordinate with disclosure and insider-trading rules
For listed companies or regulated sectors:
- Work with Legal and IR (Investor Relations) to understand when a proposal becomes inside information.
- Ensure all involved individuals are on an insider list where required, and understand restrictions on trading and communications.
- Map the external communications path: when and how the decision (if approved) will be announced to markets, customers, employees.
Your case should prove that you’ve thought about how this will land externally, not just internally.
Scenario and contingency for leak risk
For truly market-moving situations (e.g., big M&A):
- Consider including a short scenario for premature leak (e.g., press speculation or rival bids): what will you say and do?
- Align on who speaks externally and under what message discipline.
This is not about paranoia; it’s about having a cool-headed contingency in an inherently sensitive context.
23.3 Cross-Border and Multi-Entity Complexities
When your business case crosses borders, legal entities, or business units, complexity multiplies: tax, transfer pricing, governance, regulatory, HR, and cultural issues all show up.
Clarify unit of decision vs unit of analysis
Be explicit on two levels:
- Unit of decision: who is approving what—global ExCo, regional board, joint venture board, specific entity boards?
- Unit of analysis: whose P&L, balance sheet, and KPIs are we modeling—global consolidated, regional, BU, legal entity?
Sometimes the global case is positive but specific entities or units see short-term pain; calling that out avoids downstream resistance.
Tax, transfer pricing, and booking of value
Work with Tax and Finance to understand:
- Where revenues and costs will be booked (legal entities and jurisdictions).
- Transfer pricing and intra-group charges (IP, services, shared platforms).
- Tax incentives, withholding taxes, and potential double taxation or BEPS issues.
- Capital structure impact across entities (debt vs equity injections).
Your business case should at least show:
- Consolidated view for the ultimate decision body.
- Entity-level impacts where they materially affect local boards, regulators, or management incentives.
Regulatory and labor law differences
Cross-border initiatives may trigger:
- Country-specific regulatory approvals (e.g., foreign investment, data residency, licensing).
- Labor law and works council obligations (consultation, notice periods, redundancy rules).
- Cross-border data transfer constraints (privacy, banking secrecy, sectoral rules).
Include:
- A short regulatory map by jurisdiction (what approvals, by when, with who).
- A labor framework summary where workforce changes span multiple legal regimes.
Governance and decision rights across entities
Multi-entity structures (JVs, subsidiaries, partially owned affiliates) raise questions:
- Which board formally approves the investment and carries fiduciary responsibility?
- How are rights and obligations allocated in shareholder agreements or JV contracts?
- Are there minority rights, vetoes, or reserved matters that could block or reshape the initiative?
Your case may need:
- Separate, tailored packs for different entity boards or JV partners.
- Clear mapping of which approvals are contingent on others (e.g., parent approval subject to JV board sign-off).
23.4 Public Sector and Non-Profit Considerations
Public bodies and non-profits operate under different constraints and objectives: legality, propriety, value-for-money, equity, and outcomes for citizens or beneficiaries often matter more than classical NPV.
Clarify objectives beyond financials
In these contexts, be explicit that the case is evaluated against multi-dimensional objectives, such as:
- Outcomes: health, education, safety, inclusion, environmental quality.
- Equity: distributional effects across income groups, regions, or communities.
- Legitimacy: alignment with laws, mandates, and democratic decisions.
- Efficiency: cost-effectiveness and value-for-money, not just profit.
Translate these into:
- Outcome metrics (e.g., lives saved, waiting time reduction, pollution levels, employment outcomes).
- Distribution metrics (e.g., by region, income bracket, demographic group).
Use appropriate economic appraisal tools
Public and non-profit cases often use:
- Cost–benefit analysis (CBA): monetize a broad set of benefits (e.g., time savings, health outcomes, environmental effects) and compare them to costs.
- Cost-effectiveness analysis (CEA): where benefits are hard to monetize, compare cost per unit of outcome (e.g., cost per QALY, cost per student graduation).
- Multi-criteria analysis (MCA): where objectives are multiple and partly incommensurable.
Your case should:
- Follow any official guidelines (e.g., treasury “Green Book” or equivalent) on appraisal and discounting.
- Distinguish clearly between financial impacts (budgetary) and economic/social impacts (welfare).
- Note any key distributional or equity impacts that may justify decisions even where pure financials are weak.
Transparency, consultation, and accountability
In public and non-profit spheres:
- Cases may be subject to freedom of information, audit, or parliamentary/board scrutiny.
- Stakeholder consultations (citizens, NGOs, unions, communities) may be mandatory or expected.
Design your case for public defensibility:
- Clear logic, evidence, and fairness considerations.
- Explicit acknowledgement of trade-offs (who pays, who benefits, who may be negatively affected and how they’re mitigated).
- A summary that can be understood by a non-technical but informed public audience.
Ethics and mission alignment
Beyond legality, ask:
- Does this initiative align with the organization’s mission and values?
- Could it create ethical dilemmas (e.g., algorithmic bias, exclusion, surveillance, environmental harm)?
- Are there safeguards (governance, oversight, transparency) to maintain trust?
Sometimes, for mission-driven organizations, the decisive criterion is: “Does this advance our mission in a way we can defend with integrity?” The business case must help answer that.
23.5 Special Situations Checklist
Use this checklist whenever you suspect you’re in an edge case. It helps you adapt the standard business case discipline rather than abandon it.
Low-Data / High-Uncertainty
- Have we explicitly listed the top uncertainties and assumptions, with ranges instead of single values?
- Does the case distinguish learning stages (discovery, pilot) from full-scale rollout, with separate asks?
- Are we clear on what we will learn, by when, and how that will change decisions (proceed, pivot, stop)?
- Are ranges and scenarios transparently shown (base, conservative, ambitious), not buried in the model?
Confidential / Market-Moving
- Is there a clear access list and are documents appropriately labeled as confidential?
- Have Legal, Compliance, and IR confirmed the plan for insider status and disclosure where applicable?
- Are we using layered information (core pack vs secure annex) in a way that still preserves decision traceability?
- Do we have a basic leak scenario and communications plan, if relevant?
Cross-Border / Multi-Entity
- Are the unit of decision and unit of analysis clearly defined (group vs entity vs JV vs BU)?
- Have Tax and Finance validated entity-level impacts, transfer pricing, and tax implications?
- Are regulatory, labor, and data-residency issues by jurisdiction at least summarized, with owners and timelines?
- Are governance, veto rights, and multi-board approval paths documented?
Public Sector / Non-Profit
- Are objectives and KPIs defined beyond financials (outcomes, equity, ESG, mission outcomes)?
- Have we used the appropriate appraisal method (CBA, CEA, MCA) per relevant guidance?
- Are distributional impacts (who gains/loses) explicitly described and addressed?
- Is the case written to withstand public scrutiny, with clear reasoning and ethical considerations?
General edge-case hygiene
- Where evidence is thin, is that fact clearly acknowledged, with compensating governance and staging?
- Have we avoided “we’ll figure it out later” areas in matters of legality, compliance, risk, or ethics?
- Is there a clear stop-loss / exit strategy if key assumptions fail, especially for large or sensitive initiatives?
- Does the executive summary clearly flag that this is a special situation and state how uncertainty/confidentiality/complexity has been handled?
If you can work through this checklist and adapt your case accordingly, you can handle edge conditions without abandoning rigor. The principles of good business cases—clarity of decision, transparency of assumptions, explicit trade-offs, and accountable ownership—are even more important when the ground is uneven.
