Most organizations see the same patterns of decisions again and again. You approve a new plant, a cloud migration, a pricing change, an outsourcing deal, a sustainability program, an acquisition. The economics, risks, and stakeholders differ, but the type of decision is usually recognizable. Treating these as distinct categories—or archetypes—lets you reuse structure, metrics, and expectations instead of reinventing the wheel each time.
This chapter walks through five major categories of business cases and what makes each one distinctive: Investment/Capex; Product/Market Growth; Technology/Platform/Cyber; Operational Excellence/Outsourcing/Compliance/ESG; and M&A/Partnerships/JVs. We close with a practical checklist to pick the right primary category (and recognize when you are dealing with a hybrid).
4.1 Investment/Capex Cases (Build, Buy, Lease)
Investment or Capex cases concern large, often irreversible commitments to assets that will generate value over several years: plants, equipment, facilities, fleets, data centers, or long-term leases. They are classic “spend now, benefit later” decisions.
Typical triggers
You are deciding whether to:
- Build new capacity (e.g., factory, warehouse, data center) or expand existing sites.
- Replace aging assets that are costly or risky to keep.
- Adopt new equipment to unlock efficiency or quality.
- Shift from owning to leasing (or vice versa) to manage balance sheet and flexibility.
Core questions
- Capacity and demand: Do we really need this capacity? Over what horizon? How robust is the demand forecast?
- Alternatives: Build vs. buy vs. lease vs. upgrade existing; centralize vs. localize.
- Economics: What are total lifecycle costs (including maintenance, downtime, decommissioning)? How does this affect working capital and tax?
- Risk: What if demand under-delivers, input prices spike, or regulation changes? How reversible is the decision?
What must be emphasized in the case?
- Lifecycle view. Beyond initial Capex, capture maintenance, upgrades, energy, insurance, and end-of-life costs. A narrow focus on the purchase price is a red flag.
- Utilization assumptions. Capacity assumptions should tie to credible demand forecasts and historical patterns, not wishful thinking.
- Financing structure. Show implications of debt vs. cash, lease vs. own, and covenant impacts; work closely with treasury and finance.
- Residual value and flexibility. Can you repurpose, sublet, or sell if conditions change?
Common pitfalls
- Overconfidence in demand forecasts, leading to stranded assets.
- Hidden enabling costs (IT, staffing, regulatory approvals) left outside the Capex case.
- Underestimating ramp time; facilities are rarely “fully productive” on day one.
- Ignoring alternative models (leasing, contract manufacturing, shared capacity).
A good Investment/Capex case reads like a careful bet on a long-lived asset: clear logic, robust downside analysis, and explicit trade-offs between cost, flexibility, and risk.
4.2 Product/Market Growth Cases (New Offers, Pricing, Entry)
Growth cases are about increasing revenue: launching new products, entering new segments or geographies, changing pricing or packaging, or scaling a proven offer. Unlike Capex, the main uncertainties are market adoption and competitive response.
Typical triggers
- New product or feature launches.
- New geography or channel entry.
- Pricing or packaging redesign.
- Scaling a pilot or MVP that has shown traction.
- Defending or growing share in a shifting market.
Core questions
- Market: Who is the target customer? How large is the addressable market? What problem are we solving better than alternatives?
- Proposition: What is differentiated about our offer? Is it sustainable?
- Economics: What are unit economics (price, variable cost, contribution margin)? What is the acquisition and retention cost?
- Path to scale: How do we move from pilot to full roll-out? What is the commercialization plan?
What must be emphasized in this case?
- Demand logic and evidence. Customer research, pilots, funnel analytics, win/loss insights, and competitor analysis matter more than engineering enthusiasm.
- Unit economics. Go beyond “top-down TAM” to unit-level economics: price, margin by segment, acquisition cost, payback on customer cohorts.
- Scenario thinking. Adoption rarely follows the base case. Show conservative, base, and upside scenarios and what they imply for scale-up decisions.
- Capability fit. Do we have the sales, marketing, product, and operational capabilities to deliver? If not, where is investment needed?
Common pitfalls
- Overreliance on top-down market sizing without credible bottom-up adoption modeling.
- Ignoring cannibalization of existing products or channels.
- Underestimating commercialization costs (marketing, sales enablement, support).
- Assuming competitors will not react or copy.
A strong Product/Market Growth business case is clear on who will buy what, why, and at what margin, and shows a credible path from pilot evidence to scalable economics.
4.3 Technology/Platform/Cyber Cases
Technology cases justify investments in platforms, infrastructure, applications, data and analytics, and cyber/security capabilities. These often have indirect or enabling benefits—they unlock or protect value rather than directly generating revenue.
Typical triggers
- Core system replacements (ERP, CRM, billing, core banking, clinical systems).
- Cloud migrations and infrastructure modernization.
- Data platforms, analytics, and AI/ML enablement.
- Cybersecurity uplift, resilience, and regulatory compliance.
- Architecture simplification and technical debt remediation.
Core questions
- Value: What value does this technology unlock, enable, or protect (for customers, operations, risk, or future initiatives)?
- Necessity vs. option: Is this mandatory (e.g., end-of-life, regulatory) or discretionary?
- Architecture: How does this change our landscape (simplification, interoperability, vendor dependency)?
- Risk: What cyber, stability, and resilience risks are mitigated or introduced?
What must be emphasized in the case?
- Value pathways. Translate technical benefits into business terms: downtime avoided, ticket reduction, productivity gains, faster time to market, risk reduction, or avoided fines.
- Dependencies with other initiatives. Many tech investments are platforms for other cases; show the portfolio impact (which future initiatives rely on this).
- Change effort. Implementation complexity, data migration, process redesign, training, and adoption are often larger than the software spend.
- Run vs. change. Distinguish “keeping the lights on” (Run) from transformation (Change); be explicit about how OpEx profiles evolve.
Cyber/security cases in particular must be explicit about:
- Threat landscape and likelihood/impact for the organization.
- Control gaps and how the initiative closes them.
- Residual risk profile after implementation.
- Alignment with regulations and industry standards.
Common pitfalls
- “Technology for technology’s sake” with vague links to value.
- Underplaying data migration, integration, and testing complexity.
- Treating cyber as a pure cost center without quantifying downside protection.
- Over-promising reuse or modularity that architecture cannot realistically deliver.
A strong Technology/Platform/Cyber case speaks both “business” and “tech.” It gives executives enough to be confident in the value and risks without drowning them in low-level detail.
4.4 Operational Excellence, Outsourcing, and Compliance/ESG Cases
Operational and compliance cases focus on efficiency, quality, resilience, and risk posture rather than growth. They often have more certain cost impacts and more nebulous benefit narratives—especially in ESG and compliance domains—so rigor and clarity matter.
Typical triggers
- Productivity and cost-reduction programs (lean, automation, footprint optimization).
- Outsourcing, offshoring, and managed services transitions.
- Quality, reliability, and resilience improvements.
- Regulatory compliance mandates (e.g., new standards, supervisory findings).
- ESG and sustainability commitments (decarbonization, waste reduction, social impact).
Operational excellence and outsourcing
Key questions include:
- Which processes or activities are targeted and why (cost, quality, risk, speed)?
- What is the before/after operating model (locations, headcount, partners)?
- What are the one-time costs (restructuring, severance, systems) and recurring cost changes?
- What are the change-management implications for workforce and customers?
A good case will:
- Quantify savings with clear baselines (FTEs, throughput, error rates) and trackable KPIs.
- Separate structural from temporary savings.
- Address transition risks: service disruption, knowledge loss, vendor lock-in, and cultural impacts.
- Include a realistic timeline and cost for transformation, not just a “to-be” steady state.
Compliance and ESG
Here the decision often isn’t whether to do something (you may be required to) but how much and how fast to invest, and which solution path to choose.
Key questions:
- What obligations or commitments does this initiative address (laws, standards, voluntary pledges)?
- What risks are mitigated and to what residual level (fines, license loss, reputational harm, physical/environmental harm)?
- What is the minimum viable response vs. a strategic, value-creating response (e.g., using ESG to win customers, talent, financing)?
- How will we monitor and evidence compliance or ESG performance?
A strong case:
- Treats compliance/ESG as risk and value management, not just cost.
- Uses clear metrics: incident reduction, avoided penalties, access to capital, customer retention, emissions intensity, etc.
- Acknowledges ethical and stakeholder expectations, not just legal minimums.
- Avoids over-claiming hard financial benefits where evidence is thin; uses qualitative frameworks and scenario narratives appropriately.
Common pitfalls
- “Spreadsheet savings” that never reach the P&L (because scope changes, backfill occurs, or benefits leak).
- Over-simplified outsourcing assumptions (perfect transitions, zero retained complexity).
- Treating compliance/ESG as a check-the-box, producing weak cases that fail to convince internal skeptics.
- Underestimating workforce and reputational implications of operational changes.
Operational/Compliance/ESG cases live and die on credibility of baselines, savings, and risk reduction; your bar for evidence, traceability, and governance should be high.
4.5 M&A, Partnerships, and Joint Ventures
These cases involve combining or aligning with other organizations. They are among the most complex and risky decisions: multiple parties, negotiation dynamics, integration challenges, and high downside if things go wrong.
Typical triggers
- Acquiring a company for scale, capability, or market access.
- Divesting non-core businesses.
- Entering strategic partnerships (e.g., distribution, co-development, data sharing).
- Creating joint ventures with shared ownership and governance.
- Structuring alliances to accelerate time-to-market or de-risk innovation.
Core questions
- Strategic rationale: Why partner/buy rather than build or contract? Which specific strategic gaps are addressed?
- Synergies and economics: What cost/revenue synergies are expected? How will they be realized and by when?
- Valuation and structure: What is the asset worth, how is the price justified, what is the deal structure (equity, earn-outs, options)?
- Integration and governance: How will operations, systems, culture, and decision-making work post-deal?
- Risk: What if synergies under-deliver, cultures clash, or key talent leaves?
What must be emphasized in the case?
- Strategic fit and “no-deal” option. Show a clear link to strategy and explicitly test the alternative: what if we walk away and pursue organic or other options?
- Synergy model discipline. Synergy estimates should be grounded in detailed operational analysis, not just percentages of cost or revenue; double counting must be avoided.
- Integration thesis. Outline what will be integrated and what will remain separate (customers, brands, systems, teams) and why.
- Governance clarity. For partnerships and JVs, define decision rights, conflict-resolution mechanisms, capital calls, and exit provisions.
Common pitfalls
- Overstated or un-owned synergies; “someone else” is supposed to realize them.
- Ignoring integration and restructuring costs, or assuming they will be “covered by synergies.”
- Underestimating cultural and leadership friction; key person risk.
- Weak exit strategies, especially in JVs and long-term partnerships.
An M&A/Partnership/JV case must balance strategy, economics, and execution realism, and must be honest about the downside and the “walk-away” conditions
4.6 Choosing the Right Category (Checklist)
Many real-world cases are hybrids—for example, a cloud migration (tech) that enables growth (product) and cost savings (operations). Still, you should choose a primary category to drive structure, metrics, and stakeholder expectations, then acknowledge secondary dimensions.
Use this checklist to select and frame the category.
A. Decision trigger
- If the decision is mainly about long-lived physical or financial assets (plants, fleets, facilities, leases): think Investment/Capex.
- If it’s primarily about new revenue, products, markets, or pricing: think Product/Market Growth.
- If it’s about core systems, platforms, infrastructure, data, or security: think Technology/Platform/Cyber.
- If the main objective is cost, quality, resilience, outsourcing, compliance, or ESG targets: think Operational/Outsourcing/Compliance/ESG.
- If the decision centers on acquiring, partnering, or setting up a JV with another entity: think M&A/Partnership/JV.
B. Dominant value logic
- Ask: “Where does >60% of the value, measured in NPV or risk reduction, come from?”
- Capacity and asset productivity → Investment/Capex
- Revenue growth, price/mix, customer acquisition or retention → Product/Market Growth
- Enabling or protecting value via technology (speed, stability, cyber, data) → Technology/Platform/Cyber
- Sustainable cost take-out, quality, compliance, or ESG outcomes → Operational/Outsourcing/Compliance/ESG
- Synergies, strategic repositioning, or ecosystem plays with another firm → M&A/Partnership/JV
C. Main uncertainty type
- Demand / adoption / competitive response → skew toward Product/Market Growth.
- Technical feasibility, integration, or cyber risk → skew toward Technology/Platform/Cyber.
- Execution complexity in operations or workforce → skew toward Operational/Outsourcing/Compliance/ESG.
- Asset utilization and macro exposure (rates, commodities, regulation) → skew toward Investment/Capex.
- Synergy realization and integration dynamics → skew toward M&A/Partnership/JV.
D. Key audience and approver lens
- Business unit leaders and operations heads → often Operational or Capex.
- CCO, CMO, growth or product leaders, investors → often Product/Market Growth.
- CIO/CTO, CISO, architecture boards → often Technology/Platform/Cyber.
- CRO, CCO, Chief Sustainability Officer, regulators → often Compliance/ESG.
- CEO, board, corporate development, major shareholders → often M&A/Partnership/JV.
If your primary approver is, say, the CISO with a board risk committee, you likely have a Technology/Cyber or Compliance case at heart, even if there are secondary growth or cost elements.
E. Hybrid handling rules
If multiple categories appear, apply these rules:
- Rule 1: Lead with the dominant value logic. Use that as the headline category; treat others as supporting.
- Rule 2: Borrow only what you need. Use the templates, metrics, and risk framing from the primary category, and selectively add elements from the secondary one(s).
- Rule 3: Be explicit. State upfront: “This is primarily a Technology/Platform case that enables Product/Market Growth in X and Operational savings in Y.”
- Rule 4: One owner. Even in hybrids, nominate a single category owner (e.g., CIO for Tech-led cases, CCO for Growth-led), with co-owners for secondary dimensions.
F. Final category selection checklist
Before you proceed:
- I can state the primary category in one phrase (e.g., “Tech/platform modernization to enable growth”).
- I understand the dominant value logic and have aligned it with the sponsor and finance.
- I have identified secondary categories (if any) and know how they will appear in the case (e.g., as benefit streams or risks).
- I know which category-specific exhibits I will need (e.g., unit economics for growth, lifecycle cost for Capex, synergy model for M&A).
- The primary audience and approver are consistent with the chosen category framing.
Once you have chosen the right category, you can plug into the rest of the playbook: each category will shape how you build options, model economics, frame risk, and speak to stakeholders. Getting this choice right at the outset saves you large amounts of rework later—and makes your case much easier for decision-makers to absorb.
