A lot of distributed companies stumble into a favorable structure without ever designing it: revenue comes in USD from customers, while a meaningful share of costs — engineering, support, ops — sit in currencies that buy more per dollar. On paper, that's margin upside built into the business model. In practice, most finance teams treat it as background noise instead of something to actively manage, and leave real money on the table because nobody owns the FX conversation as a decision, not a monthly report.

The gap isn't sophistication — it's ownership. FX exposure usually sits at the intersection of treasury, payroll, and hiring, and because it touches three functions, it's common for it to belong to none of them in practice.

The arbitrage is real, but it's not free money

It's tempting to treat USD-in, local-currency-out as a permanent structural advantage. It isn't — it's a position, and positions move. A currency that made a hiring market attractive two years ago can appreciate enough to erode a meaningful chunk of the advantage without headcount changing at all. Teams that never modeled the downside are the ones who get a surprise cost increase they can't explain in a board meeting.

The reframe

Treat the margin benefit of distributed hiring as a range with a known sensitivity, not a fixed number — the same way you'd treat any other market-exposed input to the model.

Three things worth building deliberately

1. A hedging policy sized to the actual exposure

Most early-stage distributed companies don't need a sophisticated hedging program — they need a written threshold. Below a certain percentage of total costs in a given currency, active hedging often costs more in fees and complexity than the exposure it protects. Above that threshold, even simple forward contracts on a portion of known recurring payroll can meaningfully reduce the surprise factor, without requiring a full treasury function to manage it.

2. Payroll timing that doesn't fight the market

Where contractually possible, batching or timing currency conversion around payroll cycles — rather than converting reactively as bills come due — gives treasury more room to convert at a reasonable rate instead of whatever the rate happens to be on a fixed date every month. This is a process change, not a market-timing strategy, and it's one of the lowest-effort improvements available.

3. A reporting view that separates FX from operating performance

When a cost line moves because of currency and a cost line moves because of an actual operating decision, they need to be visible separately — to the CFO and to the board. Blending them together is how a currency-driven cost increase gets mistaken for a spending problem, and vice versa. A simple constant-currency view alongside the reported number solves most of this.

The advantage isn't the exchange rate. It's whether your reporting can tell the difference between a currency move and a decision.

Where this connects to runway

This isn't a separate conversation from runway forecasting — it's the same discipline applied one level down. A cash-band forecast that already accounts for FX sensitivity on hiring plans is far better positioned to absorb a currency move without a surprise board conversation than one that treats burn as a single blended number. The teams that get real value from a distributed hiring strategy are usually the ones who stopped treating FX as background noise around the same time they stopped treating runway as a single fixed figure.

A reasonable starting playbook

  • Name an owner for FX exposure — usually finance, even if treasury execution sits elsewhere.
  • Set a written threshold for when hedging becomes worth the complexity, rather than deciding case by case.
  • Review currency exposure on the same cadence as the runway re-forecast triggers, not as a separate annual exercise.
  • Report cost movement in constant currency alongside the reported figure, every cycle.

None of this requires a large treasury build-out. It requires deciding, in writing, that the arbitrage is a position to manage rather than a fact to assume — which is really the same shift most of this newsletter keeps coming back to, one line item at a time.