A joint venture business case is not a spreadsheet built to “win approval.” It is the explanation of why the venture should exist and the commitment to the behaviors required to make it work. In a wholly owned investment, control can enforce execution. In a JV, execution depends on joint decision rights and incentives. The business case therefore must do more than estimate returns; it must make the venture governable.
6.1 Market, Competitive, and Regulatory Context
Context should be ruthless about relevance. Your job is not to describe the market; it is to identify the few external forces that determine whether the JV can win and what it must be designed to do. The simplest discipline is to translate each important insight into an implication: if the insight does not change the JV’s strategic choices, required capabilities, or governance design, it should not be in the business case.
Context lens: A structured method to separate “nice to know” market information from “must design around” forces that shape the JV’s strategy, operating model, and governance.
Start with the customer and the switching logic. Market size alone rarely justifies a JV; customers’ willingness to switch does. Define the job-to-be-done and what customers value most: total delivered cost, reliability, time-to-market, compliance assurance, integrated outcomes, or access to scarce capacity. Then explain, concretely, what would cause a customer to choose the JV over incumbents. If you cannot articulate switching, your revenue model will be wishful thinking.
Next, clarify the basis of advantage. What matters is not a list of rivals, but how rivals win and whether that advantage is replicable. Build a competitor archetype map that groups players by the advantage they monetize—scale economics, premium execution, local access and trust, or ecosystem control—then test whether the JV can credibly match or counter those advantages.
- Scaled cost leaders: Win on utilization, procurement leverage, and throughput discipline.
- Integrated premium players: Win on reliability, quality, and end-to-end customer outcomes.
- Local champions: Win on relationships, permits, and stakeholder legitimacy.
- Ecosystem platforms: Win on standards, data, partners, and switching costs.
For each archetype, identify the two or three “hard” capabilities that are difficult to copy. These become design requirements. If scaled leaders dominate, the JV must reach scale quickly and make operational decisions fast. If local champions dominate, the JV must build legitimacy and stakeholder management muscle. If platforms dominate, the JV must invest early in interoperability and data governance. The competitive diagnosis should shape what you fund and how you govern, not just what you say in a deck.
Regulatory context must be treated as a core economic and operating driver, not as a legal appendix. Regulation can define who is allowed to compete, which ownership structures are permissible, what data can move, what pricing is constrained, and what conditions attach to licenses.
Regulatory thesis: A concise, evidence-backed view of how regulation shapes the JV’s feasibility, timeline, economics, and operating requirements, including approvals, conditions, and credible timelines.
Build the regulatory thesis around four questions: what approvals are required and how long they take; what conditions could materially change economics; what behaviors increase regulatory trust; and what events could trigger enforcement or license risk. Translate the answers into explicit model inputs (timing, costs, contingencies) and governance implications (decision rights, compliance resourcing, auditability).
Implication discipline: For each major external force, explicitly state what the JV must do, what it must avoid, and what decision rights or controls are required.
6.2 Revenue, Cost, and Investment Drivers
The heart of the business case is a driver-based model that makes value creation feel mechanical. Executives should see which levers create value, which assumptions dominate outcomes, and which commitments must hold. If the model is detailed but not driver-based, teams end up debating accounting categories that do not change decisions. Keep the model understandable to both operators and finance.
Value driver model: A simplified representation that links market assumptions and operating choices to revenue, cost, cash, and returns through a small number of controllable variables.
Start with the revenue constraint. In most JVs, early revenue is constrained by one dominant bottleneck: access, capacity, or conversion. Access constraints include permits, distribution rights, or anchor-customer adoption. Capacity constraints include equipment, scarce inputs, or qualified labor. Conversion constraints include product maturity, price realization, and switching friction. Identify the primary constraint for the first 12–24 months and show how it shifts over time. This prevents a common modeling error: assuming sales ramps faster than the constraint can realistically relax.
Build revenue from transparent building blocks. Use a structure that operators recognize: target customer pool, penetration path, volume per customer, price realization, and retention or renewal. Avoid “market share by year three” assumptions unless you show a believable route: segments, channels, sales capacity, and the switching logic from Section 6.1. Where the JV depends on parent-enabled demand—referrals, exclusivity, bundling, minimum volumes—model those items explicitly, with downside sensitivities that reflect the risk of non-delivery.
Revenue commitment: A parent-supported mechanism—such as volume guarantees, channel exclusivity, or referral targets—that increases demand predictability and should be treated as a contractual and governance topic.
On costs, separate variable costs, fixed costs, and interface costs. Variable and fixed costs determine break-even and minimum efficient scale. Interface costs are specific to JVs and often underestimated: service fees, duplicated work, coordination overhead, and the real cost of slow decisions. If the JV depends heavily on parent systems or shared services, interface costs can become the difference between an attractive model and an uncompetitive reality.
Interface cost: The ongoing cost and friction created by dependencies between the JV and the parents, including service charges, coordination time, duplicated effort, and delays that translate into real expense.
Model costs through the few operational drivers that matter most. If procurement dominates, show input prices and yields. If utilization dominates, show throughput and downtime. If service levels dominate, show the cost of redundancy and support. If compliance dominates, show controls and audit costs explicitly. The purpose is to make tradeoffs visible so governance can steer them deliberately.
Investment drivers must include more than capex. Many JV cases understate investment by ignoring working capital, transition costs, systems build-out, regulatory conditions, and ramp inefficiencies. Build an investment profile over time—stand-up, ramp, and scale—and tie funding to milestones so governance can pace capital.
Investment profile: The time-phased view of capital required for stand-up, ramp, scaling, and sustainment, including working capital and contingencies, linked to milestones and readiness.
Finally, be explicit about “who pays” and “who benefits.” If a parent provides people, systems, IP, or assets, decide whether those are charged to the JV, treated as in-kind equity, or absorbed by the parent. Make side economics visible early so they do not reappear later as hidden value leakage.
Economic transparency: The principle that the business case makes explicit all material costs, transfer prices, and side economics so the JV’s true performance can be governed over time.
6.3 Scenario Planning and Downside Protection
Scenario planning is what turns a JV business case into a decision system. Because uncertainty is real and because parents will not always interpret bad news the same way, the business case must define not only what is expected, but also what will happen if the world changes. Without scenarios and pre-agreed responses, the first major deviation from the plan becomes a governance crisis.
Scenario: A coherent set of assumptions about market conditions, execution outcomes, and constraints that materially changes the JV’s economics, cash needs, and strategic options.
Build at least three scenarios: base, downside, and upside. Make them structural, not cosmetic. A credible downside is not “10% less revenue.” It is a different world: delayed approvals, slower switching, competitor price retaliation, input cost spikes, ramp delays, or a compliance constraint that limits growth. Tie each scenario to the value drivers so governance can monitor leading indicators that signal which world you are entering.
The downside scenario must stress cash, not just profit. JVs often fail from liquidity conflict, not from low returns. Stress test cash burn timing, working capital swings, capex overruns, and the probability of additional capital calls. Then define remedies. What happens if one parent cannot fund on schedule? What constitutes default? What rights exist to protect the venture and the other parent’s exposure? Clarity here reduces hostage risk later.
Trigger: A predefined metric threshold or event that prompts an agreed escalation or action in governance, designed to reduce debate and delay during stress.
Convert scenarios into trigger-response rules. Triggers should be observable and objective: order intake below plan for two quarters, utilization below a threshold, unit cost variance beyond a defined band, milestone slippage, safety incidents, or regulator warnings. Responses should be specific actions with owners: cost containment, scope reduction, capital pacing, leadership changes, renegotiation of commitments, or activation of step-in rights. If the response is merely “we will discuss,” you have designed for paralysis.
Downside protection: The combination of contractual rights, financial structures, and operational safeguards that limit losses and preserve optionality under adverse scenarios.
Common protections include staged investment tied to milestones, guardrails on capital calls, funding default remedies, reserves for compliance and remediation, insurance, and exit mechanisms that can be executed without value destruction. Protections should be designed around specific failure modes, not as general control. Over-protection often backfires by slowing the venture so much that it creates the very underperformance it was meant to prevent.
Also plan for asymmetric stress. One parent may face its own crisis—earnings pressure, leadership turnover, sanctions exposure, or liquidity constraints—that changes its behavior. A robust business case anticipates this by distinguishing required support from best efforts and by designing governance so the JV can continue operating through temporary parent constraints.
Resilience design: Structuring the venture so it can continue operating through market shocks and parent-specific shocks, with clear rules for funding, decision rights, and escalation.
Close scenarios work with a short action playbook that links leading indicators to decisions and owners.
6.4 Strategic, Financial, and Non-Financial KPIs for the Business Case
KPIs are where the business case becomes governable. They translate the thesis into measurable performance, create a shared language for two parents, and provide early warning when the venture is drifting. KPI design is harder in a JV because transfer prices, shared services, and parent commitments can distort the “true” picture if definitions are not agreed up front.
JV KPI set: A balanced set of strategic, financial, and non-financial measures that reflect the venture’s value drivers, provide early warning, and are usable by both the JV management team and the parents’ governance bodies.
Start with strategic KPIs tied to the winning mechanism. For market-entry ventures, that often means approvals achieved, footprint built, and key account wins. For capability ventures, it means product milestones, adoption milestones, and IP integrity. For scale ventures, it means utilization, unit cost, quality, and delivery reliability. The goal is an early signal of advantage, not a bloated scorecard.
Financial KPIs should be few and cash-oriented. Early-stage JVs may be intentionally investing and therefore look weak on short-term profit; late-stage JVs may look profitable while destroying cash through working capital and underinvestment. Use a small set that captures growth quality and discipline: revenue and mix, contribution margin or gross margin, operating cost run-rate, cash conversion, working capital days, and variance to investment plan. In the ramp period, track runway and capital call forecasts explicitly, because surprises here are a common trigger for conflict.
Cash discipline: KPI design that makes liquidity and funding needs explicit so parents can anticipate capital calls and avoid last-minute negotiations that undermine execution.
Non-financial KPIs should reflect right-to-operate risks that can destroy a JV regardless of economics: compliance, safety, quality, cybersecurity, and regulatory relationships. Make them objective and auditable: audit findings closure, training completion, incident rates, defect rates, data access exceptions, and complaint resolution time. These metrics protect both parents because integrity failures attach reputationally to owners.
Regulatory and integrity KPIs: Measures that demonstrate the venture is meeting compliance obligations and sustaining regulator and stakeholder trust, which often determines its right to operate.
Include parent-commitment KPIs where the thesis depends on parent behavior. If one parent is expected to provide volumes, referrals, systems, or scarce talent, track delivery explicitly and review it in the same forums as financial performance. This reduces the toxic pattern where JV management is blamed for missing targets while parent obligations quietly slip.
Parent commitment KPI: A metric that tracks whether each parent is delivering agreed obligations that enable the venture’s performance, such as volumes, services, or staffing.
Define KPIs precisely and settle disputes early. Agree how transfer prices and service charges are treated, what is allocated, and what counts as one-time. A single glossary prevents the board from spending meeting time on accounting semantics instead of decisions.
KPI governance pack: The recurring set of reports and dashboards, with standardized definitions, thresholds, and commentary, used to review performance and make decisions.
Finally, attach decisions to critical KPIs. For a handful of metrics—utilization, cash runway, major milestone slippage, and integrity events—define thresholds that trigger actions and escalation. This turns performance reviews from passive oversight into active steering.
6.5 Governance of the Business Case: Review, Challenge, and Approval
A JV business case must survive two approval journeys: internal approval within each parent and joint approval across the parents. Internal approvals focus on capital, risk, and strategic fit. Joint approvals focus on fairness, enforceability, and governance. The objective is commitment that speeds execution after signing.
Business case governance: The set of forums, roles, and decision rules used to develop, challenge, and approve the business case so it is robust enough to guide negotiation and later operations.
Begin by agreeing what approval includes. In a JV, approval must cover behaviors, not only numbers. Therefore, the approval package should include the driver model and evidence for key assumptions, the scenario set and trigger-based responses, the list of required parent commitments, and the governance and operating implications of the case. Without commitments and implications, leadership may approve the economics and later resist the behaviors required to deliver them.
Build a joint fact base early. Where possible, align on shared sources: customer interviews under agreed protocols, regulatory counsel views, and operational assessments. This reduces dueling models where each parent uses its own numbers to justify preferred terms. A joint fact base does not eliminate negotiation, but it keeps disputes anchored to evidence rather than position.
Joint fact base: The mutually accepted set of data, analyses, and evidence used by both parents to build and evaluate the case, reducing rework and preventing parallel narratives.
Design a challenge process that is focused and constructive. Assign a small challenger group—finance, risk, legal, and an operator—to pressure-test the assumptions that matter most: the top value drivers, the biggest downside risks, and the enforceability of parent commitments. The output of challenge should be a better assumption, a specific protection, or a conscious decision to accept the risk.
Challenge questions: A structured set of questions used to pressure-test the business case, focused on value drivers, uncertainties, and commitments rather than exhaustive detail.
- Evidence: What supports the two assumptions that drive most value?
- Feasibility: What must be true in the first 90 days to stay on the ramp path?
- Commitments: Which parent behaviors are required and how will delivery be governed?
- Downside: What triggers the downside response and who funds what when it triggers?
Use stage-gates to synchronize internal and joint decisions: concept approval (permission to engage), term-sheet approval (permission to commit to headline economics and governance), and signing approval (permission to execute final agreements and funding). At each gate, document the remaining open issues and the true walk-away conditions so escalation is fast and surprises are rare.
Stage-gate approvals: A structured approval sequence that aligns internal and joint decision points, enabling progress while preserving the ability to stop if critical assumptions fail.
Finally, protect continuity. The business case should become the baseline for the first-year operating plan and the KPI governance pack. Require a mapping from business case drivers to operating KPIs, budgets, and capital pacing so performance can be assessed fairly and course corrections can be made quickly.
Continuity principle: The commitment that the business case, the first-year operating plan, and the recurring performance pack use the same driver logic and definitions so decisions can be made quickly.
When built with this discipline, the JV business case becomes a shared instrument. It aligns the parents on the same reality, clarifies how value will be created, and defines the monitoring and decision rules that allow the venture to adapt without constant renegotiation.
