An expansion investment case should answer four questions: what are we funding, how much cash could it require, when should that investment pay back, and what would make us change course? Build the case around those decisions, rather than a revenue target alone. This guide explains how to connect the team, commercial assumptions and funding requirement, with an illustrative example and the Expansion Modeller features that support the process.
The problem
A proposal to enter a new country can describe the opportunity without explaining the investment.
“Hire three people and reach £1 million in sales” leaves important questions unanswered. When do those people start? How long before they become productive? Does “sales” mean contracts signed or cash received? What happens if the first customers arrive later than planned?
Start by separating the market thesis from the financial case.
The market thesis explains why customers should buy. The financial case explains the resources needed to test that belief and the conditions under which further spending makes sense.
Your case should connect three things:
- People: roles, salaries, hiring dates and ramp-up periods.
- Commercial activity: pipeline, deals, contract values and collections.
- Capital: monthly spending, cash exposure and investment recovery.
Use one shared set of assumptions across all three.
The issues it causes
An incomplete funding request
A salary budget is not a complete expansion budget. Other variables, include employer on-costs, the chosen hiring route, commissions, marketing and other planned expenditure.
Then put each cost in the month when it occurs. A one-off setup payment and a recurring monthly expense should not disappear into the same annual total.
The British Business Bank recommends forecasting income and outgoings by period, then calculating a running cash balance. Apply that discipline to the expansion rather than presenting only a year-end result. Source: British Business Bank. (british-business-bank.co.uk)
Revenue that arrives too early in the plan
Challenge any forecast that gives a new salesperson full productivity immediately.
Specify the hire month, ramp-up period, sales cycle and expected attainment. Then distinguish signed contract value from collections.
This distinction matters because a business can be profitable while experiencing cash shortages, including when it incurs costs before customers pay. Source: British Business Bank. (british-business-bank.co.uk)
A hiring-route comparison with missing assumptions
Do not compare an Employer of Record’s monthly fee with entity setup costs alone.
For your financial comparison, include team size, entity running costs and any assumed delay before hiring and selling. Separately, establish whether each route is appropriate for the intended activities.
Market-entry preparation also needs to address practical constraints. The International Trade Administration identifies regulatory, logistical and language considerations among the questions businesses should examine. Keep that assessment alongside the model, rather than expecting a financial forecast to answer it. Source: International Trade Administration. (trade.gov)
The solution: build an expansion investment case
Build the case from explicit assumptions, then summarise the decision it supports.
1. Define the investment boundary
State the country, customer segment, offer and proposed entry date.
Specify what the expansion budget includes. For example, decide whether central management time, product localisation and shared tools are incremental costs within this case or costs carried elsewhere.
Set your approval criteria before adjusting the forecast. These might include a maximum cash commitment, a target payback month and evidence required before adding another role.
2. Build the team month by month
For every role, record:
- Team and seniority.
- Local salary and employer on-costs.
- Hire month and ramp-up period.
- EoR fee, where applicable.
- Quota and average deal size for quota-bearing sales roles.
Distinguish essential launch hires from roles that could wait. This gives you a specific alternative to cutting every budget line by the same percentage.
3. Explain how revenue becomes cash
Choose the revenue model: monthly recurring, annual prepaid or one-off.
Document the sales assumptions behind it. Include quota, attainment, deal size, ramp-up and sales cycle. Where marketing contributes pipeline, specify acquisition costs and conversion assumptions.
For recurring revenue, include churn and expansion assumptions rather than treating every customer as permanent.
4. Make the funding calculation visible
The following is a simplified, manually constructed example, not a country benchmark or an Expansion Modeller output. All figures are illustrative. It assumes zero opening cash allocated to the project and no financing flows; it does not separately model tax or exchange-rate changes.
| Period | Monthly cash outflow | Monthly cash collected | Monthly net cash | Cumulative net cash at period end |
|---|---|---|---|---|
| Months 1–3 | £30,000 | £0 | −£30,000 | −£90,000 |
| Months 4–6 | £40,000 | £20,000 | −£20,000 | −£150,000 |
| Months 7–9 | £45,000 | £40,000 | −£5,000 | −£165,000 |
| Months 10–12 | £50,000 | £65,000 | £15,000 | −£120,000 |
| Months 13–18 | £50,000 | £70,000 | £20,000 | £0 |
In this example:
- Monthly cash flow first becomes positive in month 10.
- Peak cash exposure is £165,000, reached in month 9.
- Cumulative cash investment is recovered at the end of month 18.
Those are different milestones. Positive monthly cash flow does not mean the initial investment has been recovered.
For this illustrative funding request, adding a 20% contingency to peak exposure gives £198,000. If £125,000 is already allocated, the additional requirement is £73,000.
Explain the contingency basis rather than presenting it as a universal rule. Also distinguish cash the business holds from cash it can commit to this project.
5. Test the decision
Create a base case and deliberate alternatives.
Try a longer sales cycle, lower quota attainment, a later hire or a different hiring route. Change one assumption at a time before combining them into a downside case.
Record the resulting peak exposure and payback timing. Then ask whether the proposal still meets the approval criteria.
Keep an assumptions register alongside the model, with an owner, evidence and review date for each material input. That register is a working practice, not an automated product feature.
The Expansion Modeller features that deliver it
Expansion Modeller, by Emerald Technology, connects the in-country team with monthly costs, revenue and investment payback.
Country inputs and the org canvas
The app covers 160 countries, with local currency, employer on-cost percentages, typical monthly EoR fees and average months to hire.
Emerald salary benchmarks cover hundreds of roles across five seniority levels in 67 countries. Users can override any salary, allowing the case to reflect a specific hiring assumption rather than relying solely on a benchmark.
On the org canvas, you can create teams and roles, assign hire months and ramp-up periods, and view salary totals in local and plan currencies. Roles can be switched off to test a scenario without deleting them.
A financial model tied to sales assumptions
Quota-bearing sales roles connect to the revenue forecast. Deals are whole numbers, built from quota, deal size, ramp curve and sales cycle length.
The model supports monthly recurring, annual prepaid and one-off revenue, while separating bookings from cash collected.
It also includes:
- Commission rates and alternative commission bases.
- Churn and customer expansion assumptions.
- A marketing funnel from leads through to wins, giving a CAC view.
- One-off and monthly costs, such as travel, tools and legal expenditure.
- Reporting in USD, GBP or EUR, using daily-refreshed exchange rates.
Key outputs include breakeven month, payback month, peak cash exposure, a cash journey chart and a deals and cash-collection chart. Diagnostics and a payback adviser suggest levers to reach the payback target.
EoR versus entity comparison
Switching to the entity route adds setup and running costs, plus a setup delay before hiring and selling can start.
The EoR versus entity comparison always covers the first 12 months. It combines the difference between entity costs and whole-team EoR fees with revenue brought forward under the model’s month-one selling assumption.
That assumption is part of the comparison, not a guarantee that a particular business can begin trading immediately.
For larger teams, EoR fees can meet or exceed entity costs. The app then shows a neutral tipping point and suggests reviewing an entity.
A four-step investment case
The investment case is organised into:
- At a glance
- Runway
- Where the money goes
- Entity review
Runway options include periods such as 12, 18 and 24 months, with funded cover against payback time, contingency percentage and months, and cash on hand versus the amount to raise.
The entity review timeline addresses when to start with EoR and when to review an entity. Plans can be shared through a read-only link, and teammates can be invited to a workspace.
Every plan includes every feature; country and user allowances differ across the plans described on the pricing page.
The benefit of those features
A funding discussion tied to specific assumptions
Use the cash journey to discuss when exposure builds, not just how much the project costs over a year.
In the worked example, a £125,000 allocation falls short of the £165,000 peak exposure even before contingency. That is a precise funding issue to resolve before approval.
A clear choice about hiring sequence
Switching off a role lets you examine a narrower launch team without deleting the original structure.
The decision becomes specific: does delaying this hire reduce exposure enough, and what happens to the associated revenue forecast? Review both effects before choosing the lower-cost version.
A defined hiring-route review
The first-year comparison gives the team a consistent period for examining EoR and entity assumptions.
Use it to frame an initial decision and a later review, rather than assuming one route must remain preferable indefinitely. The financial comparison should sit alongside the operational assessment.
A shared basis for review
A read-only plan gives reviewers access to the model behind the proposal. Use the accompanying narrative to explain the evidence, unresolved questions and approval conditions.
Keep the broader market-entry rationale alongside the numbers; related planning content belongs in the Expansion Modeller blog.
The outcome
The finished expansion investment case should end with a decision, not another forecast chart.
Summarise:
- The team and spending being approved.
- The assumptions supporting sales and collections.
- Peak cash exposure and contingency.
- Cash already allocated and additional funding required.
- Breakeven and payback timing.
- The downside case and conditions for pausing further spending.
- The timing and basis of the entity review.
Assign owners to the assumptions that need validation, and set the next review date before committing the budget.
The aim is not to prove that expansion will succeed. It is to make the commitment clear: what the company is prepared to invest, what must happen for that investment to pay back, and when new evidence should change the plan.