A geographic market entry business case is a decision instrument, not a finance artifact. Its job is to help leaders choose whether to commit capital and reputation, how to stage that commitment, and what evidence must be gathered to reduce uncertainty. Teams often treat the business case as a spreadsheet exercise: fill cells, produce an IRR, and assume the number will speak for itself. That approach fails because market entry is not a stable operating business; it is a sequence of bets. The right business case makes those bets explicit and turns them into a controlled, staged commitment.
To be board-ready, a market entry business case must connect five things end-to-end: the entry thesis, the unit economics, the scaling constraints, the cash profile, and the risk posture. It must also be auditable. A director should be able to trace the revenue build to a small set of drivers, trace the cost build to headcount and operational capacity, and trace major risks to mitigations and decision rights. This chapter gives you a practical structure that produces that clarity without building a model so complex that it becomes impossible to trust.
13.1 Business Case Structure: Assumptions Hierarchy and Model Hygiene
The best business cases start with an assumptions hierarchy. Without it, every review becomes a debate about everything: someone challenges market size, someone challenges the sales ramp, someone challenges overhead allocation. An assumptions hierarchy forces prioritization by showing which assumptions actually drive value and which are second-order. It also makes leadership conversations more productive because disagreement can be translated into a small number of testable statements.
Assumptions hierarchy: Separate assumptions into four tiers. Tier 1 are “make-or-break” drivers that dominate value and feasibility, such as attainable net price, adoption rate in the beachhead segment, sales productivity, regulatory timing, and channel margin norms. Tier 2 are scaling drivers that shape the ramp, such as hiring speed, onboarding throughput, partner performance, and churn/retention. Tier 3 are efficiency drivers that matter after scale, such as support productivity, logistics density, and automation effects. Tier 4 are polish assumptions, such as small variations in rent, utilities, or minor tool costs. Your objective is not to eliminate Tier 3 and Tier 4 assumptions, but to prevent them from dominating the conversation.
A strong business case also separates narrative from math. The narrative explains why the drivers are credible in this geography: local buying behavior, channel realities, the regulatory pathway, and your ability to execute with the operating footprint you have designed. The math translates those drivers into outcomes. If the narrative cannot defend the drivers, the spreadsheet becomes decoration. If the spreadsheet cannot reflect the narrative, the story becomes wishful thinking.
Driver-based model design: Build revenue from levers that match the go-to-market system. A practical minimum is Coverage (how many target accounts/customers you can reach), Conversion (stage-by-stage win rates and cycle times), Value (net price realized after channel margin and discounting), and Retention (renewal, churn, and expansion). When you present the revenue build, do not lead with a five-year CAGR. Lead with the mechanism: “We will reach X accounts per quarter through Y channels, convert Z% at each stage, realize net price N after channel economics, and retain R% with expansion E.” If those drivers are coherent, the topline becomes credible.
Cost should be similarly driver-based. Avoid “percent of revenue” costs unless they are truly variable. In market entry, many costs are step functions: adding a warehouse, adding a compliance role, adding local support hours, opening a second city, implementing e-invoicing, or hiring a second sales team once pipeline justifies it. Step costs are where early business cases deceive themselves, because they assume scale efficiency without modeling the steps that enable it.
Model hygiene: Treat the spreadsheet like a product you will rely on for months. Keep formulas simple, use consistent units and time buckets, and make it easy to audit. A board does not need to see every formula, but it must be able to trust that the model is internally consistent and that scenarios can be changed without breaking logic.
- Single assumptions tab: One place for all inputs, with sources and confidence ratings for Tier 1 and Tier 2 assumptions.
- No hard-coded numbers in formulas: Anything material should reference the assumptions tab so scenario changes are clean.
- Clear time basis: Monthly for the first 24 months, then quarterly or annual; entry dynamics are not visible in annual buckets.
- Built-in reconciliation checks: Revenue equals volume times price, headcount ties to payroll, and cash ties to P&L plus working capital movements.
- Version control: A short changelog for key assumption changes and a locked “approval version” used for sign-off.
Review discipline: Treat the model like an approval artifact. Assign an owner, an independent checker, and a “devil’s advocate” to break it. Reconcile bookings, billings, and cash collections each month. Log every Tier 1 change with evidence and the impact on outcomes so assumptions cannot drift quietly. Confirm memo and model stay aligned.
Finally, include a confidence overlay. Rate each Tier 1 and Tier 2 assumption as high, medium, or low confidence and state what evidence would raise it. This converts a broad conversation from “do we believe this?” to “what do we need to believe this, and how much are we willing to invest to learn?” It also creates discipline after approval, because the organization knows which assumptions must be validated quickly and which are stable enough to proceed.
13.2 Investment and Operating Cost Build: Capex/Opex, Working Capital, and Ramp
Market entry economics are often misunderstood because teams focus on the P&L and ignore the cash profile. For boards and investment committees, cash is the binding constraint. Your business case must therefore be cash-first: it should show when you fund the entry, when you recover cash through operations, and how sensitive that path is to working capital and ramp speed.
Investment build: Start with the minimum viable operation from Chapters 9–10 and translate it into cost categories with timing. Classify costs as One-time (entity setup, initial legal and regulatory work, initial systems configuration, launch marketing, initial equipment), Recurring fixed (leadership nucleus, baseline support, minimum facilities, compliance staffing), and Variable (payment processing, shipping, variable service labor, cloud costs tied to usage). Keep this classification consistent across scenarios; it makes it obvious which levers management can pull when reality shifts.
Make headcount the spine of the opex build. Most entry costs are people, and people costs do not ramp smoothly. Model headcount by role family and by month for the first 18–24 months. Tie hiring to capacity constraints: sellers to pipeline management capacity, delivery staff to onboarding volume, support staff to ticket load, and finance ops to invoicing and collections volume. This prevents the common mistake of assuming you can sell and deliver at scale with a skeleton team.
Ramp realism: Entry ramps are constrained by sales cycle length, trust-building, and operational throughput. If your model assumes revenue begins immediately, it must also assume that contracting, invoicing, delivery, and support are day-one ready. If any of those are still in build, revenue should be staged. Use a ramp curve that reflects the customer journey: initial pilots, then referenceable wins, then repeatable selling. Tie each inflection to a capability becoming available, such as local support hours, a certified implementation partner, or a proven onboarding playbook.
Working capital: Model the three drivers explicitly: DSO (days sales outstanding), DIO (days inventory outstanding, if relevant), and DPO (days payables outstanding). Working capital matters even for software and services because payment terms, refunds, disputes, and channel arrangements can create cash drag. For product businesses, import duties and VAT timing can tie up cash significantly. Your model should show working capital as a cash use or source each month, not as an annual afterthought.
Include an operating cash bridge that reconciles earnings to cash. Boards trust a model more when they can see the bridge. A simple bridge is: EBIT plus/minus Non-cash items plus/minus Working capital change minus Capex and capitalized setup costs. If intercompany funding, royalties, or shared-services charges matter, show them clearly so cash movements are understood, not buried.
Make staged investment explicit. Rather than asking for one large commitment, structure the business case around tranches with proof points. For example, Tranche 1 funds validation and the minimum viable operation, Tranche 2 funds scaling in the beachhead after unit economics are proven, and Tranche 3 funds broader expansion within the geography. Each tranche should have a release condition and a stop-loss trigger. Staged funding is not timid; it is how you align capital deployment with uncertainty reduction while maintaining speed.
Hidden capital: Surface “capital in disguise” that often gets missed in entry business cases. Examples include inventory buy-back obligations, minimum marketing development funds for channel partners, extended credit terms that increase receivables, required bank guarantees, and local data hosting commitments that create multi-year contracts. Treat these as part of the investment task, because they can be as binding as capex.
13.3 Unit Economics and Breakeven: What Must Scale to Win
Unit economics is the language of scalability. A country entry can tolerate early losses, but it cannot tolerate a structurally broken unit model that only looks attractive when averaged over an unrealistic scale. Your business case must show how each unit of growth performs, what improves with scale, and what does not. This is what lets a board distinguish a “temporary investment” from a “permanent subsidy.”
Define the unit that matches your business model. For B2B, the unit might be an account, a site, or a contract. For B2C, it might be a customer, an order, or a subscription. For marketplaces, it might be a transaction or an active seller. Then define the economics per unit in the same order customers experience them: Net revenue per unit (after discounting, channel margin, and taxes), Direct cost per unit (COGS or delivery cost), Serve cost per unit (onboarding, support, payment costs), and Acquisition cost per unit (CAC or sales cost). If the unit model is unclear, your business case is not ready because you cannot explain what “growth” actually costs.
Build a net contribution view that strips away corporate allocations and focuses on what the country can control. In early entry, corporate allocations can obscure learning by making a good unit model look bad or a bad unit model look “not that bad.” The key is to show Contribution margin (net revenue minus variable costs and direct serve costs), then show how that margin funds fixed costs and growth investment.
Net revenue realism: In many entries, the difference between list price and retained net revenue is the difference between success and failure. Build a price waterfall: list price, standard discount, negotiated discount, channel margin, rebates/marketing funds, freight/duties, returns/credits, and free services. If your business case assumes premium pricing, it must also assume the proof and service system required to hold it. If it assumes low discounting, it must show why competitors and channels will not force price down.
Breakeven logic: Present breakeven in three ways because each answers a different executive concern. Unit breakeven is when a typical unit (customer/account/order) is profitable. Operating breakeven is when the country P&L turns positive. Cash breakeven is when cumulative cash flow turns positive. Many entries achieve operating breakeven but remain cash-negative due to working capital; boards care about the cash curve because it determines whether the enterprise can fund the ramp without compromising other priorities.
Show what must scale to win. In most entries, one of these is the primary scaling constraint: Sales productivity (deals per seller and cycle time), Delivery throughput (onboardings per team per month), Service capacity (tickets per agent at required service levels), or Partner performance (pipeline and conversion per partner). Make the constraint explicit and model capacity growth alongside revenue growth. If revenue grows faster than capacity in the model, the plan is implicitly assuming either heroics or quality degradation; neither is a strategy.
Include an efficiency curve only where it is justified. Some costs decline per unit with scale (support automation, procurement leverage, logistics density), but others do not (regulatory compliance baseline, local statutory reporting, certain forms of field service). Declare which costs are expected to improve, why, and when. Then link improvement to a mechanism: automation deployed, partner enablement completed, process redesigned, or a hub created. Efficiency should not be a hope; it should be a project with prerequisites.
Unit economics validation plan: Tie the unit model to a practical plan for upgrading confidence. For example, validate net price with live quotes and partner margin checks, validate conversion with pipeline stage data, validate server cost with pilot delivery time tracking, and validate retention with early adoption indicators and cohort behavior. This is how the business case becomes a learning roadmap rather than a static forecast.
13.4 Scenario Cases: Base/Upside/Downside and Probability-weighting
A single-case business plan is a storytelling exercise. A scenario-based business case is a decision tool. Directors understand uncertainty; what they want is clarity on the range of outcomes, the drivers of that range, and what management will do as new information arrives. Scenarios also protect the team after approval by setting expectations that variance is normal and that responses should be disciplined, not reactive.
Build three scenarios that are meaningfully different and grounded in mechanisms. Base case is your best estimate given current evidence. The upside case should not be “everything goes well”; it should be “one or two catalysts go better than expected,” such as a major partner outperforming, a reference account accelerating adoption, or regulatory approval arriving faster. Downside case should not be “the world ends”; it should be “one or two frictions persist,” such as slower hiring, higher channel margin demands, price pressure, or longer regulatory timelines.
Scenarios should be built by changing a small set of Tier 1 and Tier 2 assumptions, not by tweaking everything. A good practice is to limit each scenario to five changed drivers and show those drivers on one page. This keeps discussion focused on what matters and prevents confusion created by hidden changes.
Probability-weighting: In some organizations, boards prefer a single “expected value” view. If you provide probability-weighting, do it transparently. Assign probabilities to each scenario and state the rationale in plain language, anchored in evidence strength and known constraints. Then show both the probability-weighted result and the individual scenarios, because expected value can hide tail risk. A probability-weighted NPV that looks attractive can still be unacceptable if the downside includes a long cash burn tail or a reputational risk the enterprise is unwilling to carry.
Use scenarios to define triggers and actions. This is where a business case becomes an operating system. For each scenario driver, define Leading indicators you can observe early (pipeline conversion, discount-to-target, partner activity, hiring velocity, onboarding throughput, service backlog, collections), define Trigger thresholds that indicate you are trending toward upside or downside, and define Pre-approved actions that management will take. Pre-approval matters because it prevents slow reaction: when a downside trigger hits, you do not want to spend six weeks debating whether to throttle spend or change scope.
Separate spending into categories that reflect managerial flexibility. Committed spend: required to operate safely and deliver the promised experience, including compliance and baseline service. Growth spend: accelerates scaling if the model is working, such as additional sellers or marketing expansion. Optional spend: can be deferred without breaking the business, such as entering a second city early or building a custom integration. This separation gives boards confidence that downside can be managed without undermining the core, and it forces management to articulate what is truly required versus what is merely attractive.
Finally, scenario work must include cash, not just earnings. Many downside cases look survivable on P&L but fail on cash because working capital worsens and the ramp slows. Show cumulative cash burn and required funding under each scenario. If the downside requires additional funding, state whether that funding is acceptable, whether the plan includes a pivot to reduce burn, or whether the downside triggers a stop-loss and exit plan.
13.5 Board Memo Template + Approval Gates Checklist
Boards do not approve spreadsheets; they approve decisions. The board memo is the narrative instrument that links the entry thesis to the capital task, the risk posture, and the governance plan. A strong memo is concise, explicit about uncertainty, and clear about what management will do if the world deviates from the plan. The memo should also make the “why now” case: what opportunity is being captured or what risk is being mitigated by moving at this moment.
Board memo template:
- Decision requested: the exact approval needed (market, entry mode, investment tranche, and timing) and the delegations requested for management.
- Strategic rationale: how the entry advances corporate intent (growth, diversification, cost, talent, resilience) and the cost of inaction.
- Where-to-play / how-to-win: the beachhead segment and use case, value proposition, route-to-market, and the specific advantage you will bring in-country.
- Operating model: entity and footprint plan, partner strategy, delivery model, and readiness status for licenses, tax, contracting, and data requirements.
- Economics summary: TAM/SAM/SOM ranges, unit economics, pricing corridor, and the path to operating and cash breakeven.
- Investment ask: capex, opex, working capital, and timing; staged funding tranches with release conditions and stop-loss triggers.
- Scenarios: base/upside/downside outcomes, key drivers, probability-weighted view (if used), and cumulative cash burn under each case.
- Risks and mitigations: the top risks, controls in place, and the residual risks the board is being asked to accept.
- Governance and cadence: decision rights, reporting cadence, KPI dashboard, and escalation rules; who owns the P&L and who owns compliance.
- Next steps: a 30/60/90-day plan and the next gate decision date.
Attach the spreadsheet as an appendix, not the core. The memo should stand alone. If the plan requires a live presentation to be understood, it is not board-ready. A useful discipline is to open the memo with a single-page “decision sheet” that includes the recommendation, the investment, the expected outcomes, and the two or three assumptions that most determine success.
Approval gates checklist: Before asking for a full commit decision, run an evidence gate checklist. This creates integrity, reduces late surprises, and makes staged funding real rather than rhetorical.
- Gate A: Market and thesis: beachhead segment defined, customer pain validated, differentiation claim supported by proof artifacts, and clear “what would change our mind” conditions documented.
- Gate B: Route-to-market: channel economics validated, partner(s) qualified or direct model resourced, data visibility secured, and partner governance terms (audit rights, termination, reporting) drafted.
- Gate C: Regulatory and compliance: licenses and approvals mapped with timelines, day-one legal operating envelope defined, and compliance-by-design controls implemented for third parties and discounts.
- Gate D: Unit economics: net price corridor validated, cost-to-serve measured in pilots or credible analogs, and contribution margin positive at the unit level within a defined ramp period.
- Gate E: Execution readiness: country nucleus hired or in late-stage hiring, order-to-cash and support processes tested end-to-end, and critical vendors/outsourcers contracted with measurable SLAs.
- Gate F: Financial resilience: working capital modeled and funded, downside cash burn acceptable within enterprise constraints, and stop-loss triggers defined with pre-approved actions and owners.
End the approval conversation with operational clarity: who is accountable, what tranche is funded now, what evidence unlocks the next tranche, and what would trigger a pause, pivot, or exit. When that clarity exists, the business case stops being a one-time approval exercise and becomes an ongoing management tool that keeps the entry disciplined as reality unfolds.
