Burn Rate Runway: The Multi-Currency & Expansion Problem

# Burn Rate Runway: The Multi-Currency & Expansion Problem

When we work with founders who are scaling beyond their home market, we see a recurring pattern: their burn rate and runway calculations stop being accurate the moment they hire their first international team member or launch in a new geography.

A founder will confidently tell their board they have 18 months of runway. Three months later, after opening an office in Europe or hiring engineers in Singapore, they're scrambling because the actual cash position tells a different story.

The problem isn't that they're bad at math. It's that traditional burn rate and runway models treat all cash outflows as equal and all revenue as instantly fungible. When you operate across multiple currencies, tax jurisdictions, and payment systems, that assumption breaks down immediately.

Let's talk about what founders actually need to know about burn rate and runway when they're scaling internationally—and why your spreadsheet is probably lying to you.

## What Most Founders Get Wrong About Global Burn Rate

When you ask a founder to calculate their burn rate, they'll typically give you a number like this:

**Monthly Burn Rate = Total Monthly Expenses - Total Monthly Revenue**

That's correct for a single-currency, single-jurisdiction operation. But the moment you expand, this oversimplifies in three critical ways.

### The Currency Mismatch Problem

Let's say you're a U.S.-based SaaS company with $500K in monthly revenue (USD). Your original burn rate is $200K/month (net burn), giving you roughly 12 months of runway.

Now you open a London office and hire five engineers at £60K/year each (roughly $300K/year salary cost). You also establish an entity in the U.K. to hire locally. Here's what happens:

1. **Your expenses are now split across currencies**: USD salaries, benefits, and infrastructure costs, plus GBP salaries and UK employment taxes.
2. **Your revenue currency mix stays the same**: Mostly USD-based customers, with some GBP revenue from UK clients.
3. **Currency exchange rates fluctuate**: The GBP/USD rate swings 2-3% monthly. A 5% weakening of sterling means your effective burn rate (measured in USD) suddenly increases because your GBP expenses cost more dollars to pay.
4. **You have cash in two currencies but need to pay obligations in both**: You can't pay UK payroll with USD. You need actual GBP in your UK bank account.

Your spreadsheet says burn rate went up by ~$25K/month (the salary cost of the UK team). But your **actual USD cash position** deteriorated by more than that because currency conversion costs and exchange rate movements created a headwind you didn't model.

In our work with Series A startups expanding into Europe or Asia, we've seen currency fluctuations account for 2-4% of monthly cash variance on top of operational burn.

### The Timing Mismatch Problem

Here's another wrinkle: cash doesn't convert instantly, and different currencies have different payment timelines.

When a customer in Singapore pays you in SGD, that payment typically doesn't hit your USD account for 2-3 business days *after* conversion. Meanwhile, you've committed to paying your Singapore team in SGD on the 25th of the month.

If you're calculating runway as **Total Cash / Monthly Net Burn**, you're ignoring this timing gap. You might show positive cash flow on paper, but your SGD account is empty because the USD revenue hasn't converted yet.

We've seen founders run payroll short on a Thursday because they didn't account for T+2 or T+3 settlement delays on forex conversions. Their spreadsheet said they were fine. Their accountant had to scramble.

### The Tax Jurisdiction Problem

When you operate in multiple countries, you're now managing multiple tax systems:

- **Income tax withholding**: Different rates by country. A developer in Germany has different tax obligations than one in Poland.
- **VAT/GST management**: The U.K. charges 20% VAT. You may need to collect VAT from customers and remit it quarterly. That's cash outflow that doesn't directly correlate to your operating expenses.
- **Corporate tax**: Some jurisdictions require monthly or quarterly estimated tax payments. Others only require annual filings. Your burn rate calculation needs to account for when cash actually leaves your account.
- **Transfer pricing rules**: If you have intercompany transactions (e.g., charging the UK subsidiary for corporate overhead), you need to price those according to regulations. Get it wrong, and you face penalties that hit cash.

Most founders don't reserve for quarterly VAT or corporate tax payments in their monthly burn rate. Then Q2 hits, they owe $80K in UK VAT they haven't accrued, and runway suddenly looks 2-3 months shorter.

## How to Calculate Burn Rate Across Multiple Currencies and Jurisdictions

So what does a more accurate burn rate model look like when you're expanding globally?

### Step 1: Segment Expenses by Currency and Jurisdiction

Instead of one "Total Monthly Expenses" line, break it down:

```
USD Expenses:
- U.S. Salaries: $120K
- Cloud Infrastructure (billed in USD): $15K
- Marketing (split across currencies): $25K
- Benefits, Taxes, Compliance: $18K
Subtotal: $178K

GBP Expenses:
- UK Salaries: £45K
- UK Employment Taxes: £12K
- Compliance/Accounting (UK): £4K
Subtotal: £61K (~$77K at current rates)

SGD Expenses:
- Singapore Salaries: SGD 280K
- Local Compliance: SGD 8K
Subtotal: SGD 288K (~$215K at current rates)

Total Monthly Burn (USD equivalent): $470K
```

But here's the key: **don't just convert everything to USD at today's exchange rate and call it your burn rate**. You need to model currency sensitivity.

### Step 2: Model Currency Sensitivity

For each major currency, calculate what your burn rate looks like if that currency appreciates or depreciates by 2-5%:

- If GBP weakens 3%: Your USD-denominated burn rate increases because you need more dollars to fund the same GBP expenses.
- If SGD strengthens 3%: The opposite effect—your USD burn rate improves.

Your true burn rate range might be $460K-$485K, not a fixed $470K. Runway planning needs to account for that range, not the midpoint.

We recommend our clients model a **pessimistic scenario** (currencies move against you) and a base case when forecasting runway past 6 months.

### Step 3: Segregate Working Capital and Tax Obligations

Your operational burn rate (salaries, infrastructure, marketing) is different from your **cash burn** when you include:

- **VAT/GST payables**: Track these separately. If you're collecting VAT from customers but not yet remitting it, that's a timing mismatch that improves your cash position short-term but hurts it when payment is due.
- **Estimated tax payments**: Add a line item for quarterly and annual tax payments by jurisdiction.
- **Intercompany balances**: If you're charging subsidiaries for overhead or services, track those receivables and payables. They affect cash flow timing.

Your **net burn** (used to calculate runway) should include all of these, but tracked separately so you understand what's discretionary (salaries, marketing) versus non-negotiable (taxes, withholdings).

### Step 4: Build a Weekly Cash Flow Forecast, Not Just Monthly

Once you're operating in multiple currencies with different payroll cycles, weekly cash flow forecasting becomes essential.

Your monthly burn rate might be $470K, but if payroll is staggered (U.S. on the 15th, U.K. on the 25th, Singapore on the 20th), your weekly cash need varies dramatically. You might need $180K in Week 2, $220K in Week 3, and $90K in Week 4.

If you're relying on monthly revenue timing that doesn't align with these expenses, you could hit a cash crisis even with 12 months of "runway" on paper.

In our work with expanding startups, we've moved clients from monthly to weekly cash forecasts, and it surfaces timing issues that would have been catastrophic in a few months.

## Extending Runway When You're Multi-Currency

Once you understand your true burn rate across currencies, you can make smarter decisions about extending runway.

### Hedge Currency Exposure (Selectively)

If you have material expenses in GBP or SGD but revenue primarily in USD, you have currency risk. Some options:

- **Forward contracts**: Lock in exchange rates for anticipated payroll payments 30-90 days out. Costs 0.5-1% but eliminates volatility.
- **Natural hedges**: Raise revenue in the same currency you're spending. If you're building a UK presence, focus on acquiring UK customers paid in GBP.
- **Cash reserving in local currencies**: Keep 60-90 days of expenses in GBP and SGD to reduce conversion frequency.

Most startups don't hedge—they assume it's too complex or expensive. But a 5% currency swing on $100K+ of monthly expenses is real money. In our experience, selective hedging of 3-6 months of committed expenses is often worth the cost.

### Optimize Payment Timing and Netting

If you have both receivables and payables in the same currency, consolidate them:

- Collect customer invoices in GBP if you have GBP expenses.
- Use **multi-currency netting accounts** to reduce forex conversion costs (platforms like Wise, Revolut, or Mercury offer these).
- Batch payroll across jurisdictions to hit conversion windows once weekly rather than daily.

We've seen founders reduce forex costs by 40-60% just by batching conversions and aligning inflows with outflows by currency.

### Reassess Hiring Currency Allocation

When you're planning to hire in a new geography, model the full cost including benefits, taxes, and currency impact:

- Hiring a U.S. engineer at $150K costs closer to $200K when you include taxes, benefits, infrastructure.
- The same engineer in Portugal might cost $100K all-in, but if your revenue is in USD and you're converting EUR to USD monthly, that salary is effectively costing you 3-4% extra due to forex.
- Sometimes, a nearshore hire (Latin America for U.S. companies, Central/Eastern Europe for EU companies) extends runway more than you'd expect because of favorable currency matches.

We worked with a SaaS company planning to extend runway by hiring in cheaper geographies. Once we modeled the currency impact, they realized hiring in Poland (EUR-denominated costs, some USD revenue) was better for runway than hiring in the Philippines (SGD and PHP costs, USD revenue, high forex drag).

## Communicating Multi-Currency Burn Rate and Runway to Investors

Here's where most founders stumble: investors want a single runway number, but your runway is now a range dependent on currency movements and expense timing.

When presenting to investors:

1. **Lead with base-case net burn** (operational burn + taxes + working capital)
2. **Show the range** (optimistic/pessimistic scenario with currency assumptions)
3. **Highlight the key sensitivity drivers**: "Our runway is 14-16 months, depending on GBP/USD exchange rates and timing of VAT payments."
4. **Be transparent about currency hedging**: "We're naturally hedged for GBP because 30% of revenue is UK-denominated. We're exposed to SGD for our Singapore team—currently unhedged, representing ~$20K/month of forex risk."

Investors respect founders who understand the nuances of their cash position. A founder who says "we have 18 months of runway" without acknowledging currency complexity looks less sophisticated than one who says "our operational runway is 16 months, plus 2 months of working capital buffer, with sensitivity to GBP weakness."

## The Bottom Line: Burn Rate Runway Gets Complicated Fast

Your burn rate and runway aren't fixed numbers once you expand internationally. They're ranges that depend on:

- Currency exchange rate movements
- Payment settlement timing across systems
- Tax jurisdiction requirements
- Seasonal revenue patterns by geography
- Payroll and vendor payment schedules

Founders who stay ahead of this complexity—by modeling weekly cash flow, segregating expenses by currency, and accounting for timing mismatches—have visibility that keeps them from being blindsided.

Founders who stick with a single monthly burn rate number often discover, too late, that their runway was shorter than they thought.

## Next Steps

If you're expanding internationally or planning to, your burn rate and runway calculations need to evolve. [The Startup Financial Model Dependency Problem](/blog/the-startup-financial-model-dependency-problem/) can help you structure the model correctly, but the key is starting now, not after you've hired the international team.

At Inflection CFO, we help founders build financial models that account for currency complexity, tax timing, and real cash flow—not just spreadsheet math. If you're scaling across geographies and want to validate that your runway calculation actually reflects your cash position, we offer a free financial audit that specifically looks at these gaps.

The best time to catch a runway surprise is before it becomes a crisis.