Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Hedge Currency Risk
Transcript
- Lucas: If you build or run a software business, you probably spend hours thinking about product-market fit, churn rates, and how to upsell existing customers. But there is a much quieter, equally dangerous force lurking in the background of any global SaaS company: currency risk. I was looking at the latest quarterly reports from a few major enterprise players, and the numbers tell a strange story. On paper, they grew their revenue by twelve percent year-over-year. But if you strip out the impact of a strengthening dollar against the euro and the yen, that organic growth was actually closer to eight percent. That four-point gap isn't a marketing metric. It's a direct hit to the bottom line caused by exchange rate fluctuations. Luna: That feels counterintuitive because we usually talk about SaaS as a purely digital product that scales infinitely. How much actual friction does currency really create when you're just sending invoices over the internet? Lucas: The friction is invisible until it shows up in the treasury department. Let's take a hypothetical example of a mid-sized platform selling to enterprises in Germany and Japan. They bill in local currencies, which makes sense for sales teams who don't want to explain exchange rates to procurement officers. But when those euros and yen come back into the consolidated balance sheet, they have to be converted at the current spot rate. If the dollar spikes in value during the quarter, every single euro they earned yesterday is worth less today. For a company with five hundred million dollars in international revenue, a five percent move in the euro can swing their net income by twenty-five million dollars. That is not a rounding error. That is a entire engineering team's salary budget, gone in a spreadsheet adjustment. Luna: So they are essentially betting against the dollar while trying to grow the business? Or do they have tools to neutralize that exposure? Lucas: They use something called hedging. Specifically, forward contracts. A forward contract is essentially a promise to exchange one currency for another at a fixed rate on a future date. If a SaaS company knows they will receive ten million euros in ninety days, they can lock in an exchange rate today. If the dollar strengthens later, they still get the pre-agreed amount. It sounds like insurance, and it is. But here is where it gets complicated. Hedging costs money. You pay premiums, you deal with basis risk, and you introduce a layer of financial engineering that most engineers and product managers completely ignore. So the question becomes: is this cost of doing business worth it, or is it just bloating the operating expenses? Luna: It seems like a classic case of corporate bloat. If the market is efficient, shouldn't investors just discount the currency risk themselves instead of paying a treasury team to manage it? Lucas: That is a fair theoretical point, but in practice, stock markets hate volatility. Investors prefer predictable earnings guidance. When a CEO says, 'We expect growth of ten to twelve percent,' and then misses that target because the euro dropped three percent, the stock gets punished. So companies hedge to smooth out the noise. They trade away potential upside—for example, if the dollar weakens and their foreign revenue suddenly becomes worth more—to eliminate the downside risk. It is a defensive strategy. And recently, we've seen some major players like ServiceNow and Adobe leaning heavily into this. They aren't just hedging; they are optimizing their natural hedges by matching revenue streams with operational costs in the same currencies. Luna: Matching costs to revenues... so if they pay their German developers in euros, they automatically offset the euro revenue? That seems like a much simpler solution than buying complex financial derivatives. Lucas: Exactly. That is called a natural hedge. If you earn in euros and spend in euros, your net exposure is near zero. The problem is that many SaaS companies have centralized their operations. They hire most of their engineering talent in places with lower labor costs or specific skill pools, often in the US or Eastern Europe, while selling globally. This creates a structural mismatch. You earn in soft currencies but pay salaries in hard currencies. To fix that, you either move your hiring patterns—which is incredibly difficult due to visa laws and talent concentration—or you stick with financial hedges. And financial hedges are getting expensive right now because interest rate differentials between the US and other central banks are wide. Luna: Wait, interest rates affect the cost of hedging? I always thought it was just about the direction the currency was moving. Lucas: It is all about the carry trade. When you buy a forward contract, you are effectively borrowing in one currency and lending in another. If the US interest rate is higher than the Eurozone rate, it costs you more to hold a short position in dollars and long position in euros. So even if the exchange rate itself stays flat, the cost of maintaining that hedge rises. This means that a SaaS company might have perfectly stable revenue, but their hedging costs eat directly into their gross margin. It is a silent tax on international expansion. And for smaller companies, the transaction fees alone can make it prohibitive to hedge anything beyond their top tier accounts. Luna: This feels like a privilege of scale. Only the giants can afford the treasury infrastructure to manage this efficiently. What happens to the challenger startups trying to go global? Lucas: They get exposed. And that exposure can kill them before they ever reach profitability. Imagine a Series B company that lands a massive contract with a Japanese retailer. They sign the deal in yen. Six months later, the yen depreciates sharply against the dollar. Their revenue recognition drops, their burn rate looks worse because they have less cash coming in relative to their expenses, and their runway shrinks. They didn't fail on product. They failed on finance. This is why we see so many SaaS companies defaulting to billing in US dollars for international deals. It shifts the risk entirely onto the buyer. And frankly, it is becoming harder to sell that way in mature markets where local currency billing is the norm. Luna: Shifting the risk to the buyer sounds aggressive. Do buyers actually accept that, or do they push back hard on dollar-denominated invoices? Lucas: Enterprise procurement teams love dollar invoicing for exactly the reason you mentioned. It simplifies their own accounting. But small and medium businesses abroad often hate it. They have to deal with their own bank fees and exchange rate uncertainty. So you see a bifurcation. Large enterprises agree to dollars. Small businesses demand local currency. And that fragmentation forces the SaaS provider to manage two different risk profiles simultaneously. It adds administrative overhead that compounds quickly. You need different payment processors, different reconciliation logic, and different forecasting models for each segment. Luna: It reminds me of how e-commerce platforms handle shipping. They try to hide the complexity from the consumer, but the logistics engine underneath is incredibly fragile. Lucas: That is a perfect analogy. The consumer sees a seamless checkout. The backend is managing inventory, customs, and currency conversion in real time. For SaaS, the 'consumer' is the CFO of the client company. They want predictability. If the SaaS vendor keeps changing prices based on FX moves, the CFO loses trust. So the vendor absorbs the shock. Which brings us back to the hedging decision. Is it better to absorb the volatility and hope the average works out, or to pay for certainty? Most public companies choose certainty because their analysts demand it. Luna: But doesn't absorbing the volatility sometimes lead to smarter strategic decisions? Like maybe they should have just avoided that risky market in the first place. Lucas: Potentially. There is a argument that hedging creates moral hazard. If you know you can easily hedge away the currency risk, you might expand into markets that are otherwise financially unstable. You might enter Brazil or Turkey when you should have stayed home. The hedge masks the true economic risk of the region. So you end up with a portfolio of businesses that look healthy on paper but are structurally vulnerable to political or regulatory shocks that no financial derivative can protect you from. Currency is just one piece of the geopolitical puzzle. Luna: I never thought about hedging as a distraction from broader geopolitical risk. It feels like putting a band-aid on a wound that needs surgery. Lucas: Sometimes. But for most operators, surgery is too expensive. Band-aids are cheap enough to keep the bleeding controlled. And speaking of keeping things running smoothly, we rely on listener support to keep these deep dives happening. A couple of dollars a month is genuinely what keeps these going. You can support us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. It helps cover the research costs and ensures we can bring you these conversations ad-free. Luna: Thanks for the support. It definitely lets us dig deeper into the nitty-gritty details like this without rushing through the financial mechanics. Lucas: Back to the main thread. We have looked at the defensive side—hedging, natural offsets, shifting risk to buyers. But there is a proactive angle that very few SaaS companies exploit: pricing power through currency flexibility. Some innovative vendors are starting to build dynamic pricing engines that adjust subscription costs automatically based on purchasing power parity in different regions. Instead of a static dollar price that gets distorted by FX, they tie the price to local economic indicators. This stabilizes revenue for the buyer and reduces the vendor's exposure because the price adjusts continuously rather than waiting for a quarterly reporting period. Luna: Dynamic pricing based on local economics sounds incredibly complex to implement technically. Does any major player actually do this at scale? Lucas: Not at the enterprise level yet. It is mostly seen in consumer SaaS or lower-tier plans. Enterprise contracts are negotiated annually, often with multi-year lock-ins. You cannot easily renegotiate a five-hundred-thousand-dollar contract every time the yen moves. But we are seeing a shift in how these contracts are structured. More clauses are including FX adjustment mechanisms. If the exchange rate moves by more than five percent, the price resets. It puts the burden of monitoring the market back on the vendor, but it also creates a more transparent relationship with the client. It acknowledges that currency is a real variable, not just a accounting footnote. Luna: That transparency feels healthier. It stops the surprise attacks on margins that we talked about earlier. But does it slow down the sales cycle? Lucas: It might add a few days to the negotiation. Procurement teams have to understand the formula for the reset clause. But compared to the alternative of a missed earnings call or a sudden drop in cash flow, it is a small price to pay. The bigger trend, though, is consolidation. As the economy tightens, smaller SaaS companies are being acquired by larger ones precisely because their currency exposures are mismanaged. The acquirer sees a cheaper entry point because the target's financial statements are inflated by favorable FX moves that are about to reverse. It is a subtle arbitrage opportunity that savvy investors are watching closely right now. Luna: So the next time you see a SaaS acquisition, you should check the notes on their foreign exchange exposure. It might reveal the real valuation gap. Lucas: Absolutely. Look at the supplemental data in the 10-K filings. Ignore the headline growth number for a second. Look at the constant currency growth. That is the true measure of operational health. If constant currency growth is lagging reported growth, the company is riding a wave of favorable exchange rates that will eventually crest. And when it does, the fall can be steep. It is a reminder that in global business, money is never just money. It is always a bet on a nation's economic policy, and those bets change faster than software code. Luna: Code changes fast, but central banks move slower. Yet their ripples last longer. It makes me wonder if we are over-indexing on product velocity and under-indexing on financial resilience. Lucas: We certainly are. Product velocity gets the headlines. Financial resilience gets the boardroom silence. But as we move further into a fragmented global economy, that resilience might become the primary differentiator between companies that survive the next downturn and those that don't. The builders who treat treasury management as a feature, not a bug, will likely win the next decade. Luna: I guess that means the best product isn't always the one with the best features, but the one with the best balance sheet. Lucas: Precisely. In a world of infinite copy-paste technology, the moat is increasingly built in the finance department. It is a quiet revolution, and it is happening right now in the quarterly reports of every major software company. Luna: And probably the ones you haven't heard of yet are already planning their next hedge. Lucas: Oh, they are. And they are watching your ticker symbol just as closely as you are watching theirs.