Paying for Cloud in Dollars, Earning in Shillings: Managing Forex Exposure

Why your AWS bill hurts more some months than others, and what to do about it

If you run a business in Kenya and use cloud infrastructure — AWS, Google Cloud, Microsoft Azure, or even SaaS tools like a CRM, accounting package, or email platform — you have probably noticed something uncomfortable. Your revenue arrives in shillings, from M-Pesa transactions, bank transfers, or invoiced clients paying in KES. But your infrastructure bill arrives in US dollars, converted to shillings by your card issuer or bank at whatever rate applies that day. When the shilling weakens against the dollar, your cloud costs quietly rise even if your usage has not changed at all. This is forex exposure, and for a business built on dollar-denominated infrastructure, it is a real and recurring cost that deserves the same attention you give to rent, salaries, or KRA obligations.

It helps to understand why cloud pricing is dollar-denominated in the first place. The major hyperscale providers price globally in USD because their cost base — data centre hardware, chips, power contracts, global engineering talent — is largely dollar-linked, and USD pricing gives them a stable reference currency across every market they serve. Some providers offer billing in local currency through resellers or regional billing arrangements, but the underlying price is still set in dollars and adjusted periodically to reflect currency movements. Even when your invoice shows KES, the number behind it is anchored to a dollar figure that can change. There is no cloud provider, to a first approximation, that has priced its core compute and storage in shillings and left it there permanently insulated from currency movement.

For a Nairobi-based SME, fintech, SACCO, clinic, or school running its systems on cloud infrastructure, this exposure shows up in a few predictable ways. First, your monthly infrastructure spend becomes a variable cost rather than a fixed one, even when your actual cloud usage is flat. Second, if you have priced your own product or service in shillings for local customers — a school management system, a SACCO's digital banking app, a clinic's patient records platform — but your underlying cost of running that system is dollar-linked, your margins compress whenever the shilling weakens, without you having done anything wrong operationally. Third, if you have committed to a longer-term cost structure, such as a reserved capacity plan or an annual SaaS licence quoted in dollars, a shift in the exchange rate between the time you budgeted and the time you actually pay can turn a comfortable line item into a strained one.

The starting point for managing this is simply to stop treating cloud costs as a fixed number in your budget and start treating them as a range. When you plan your annual or quarterly budget, build in a buffer specifically for currency movement on dollar-denominated costs, separate from the buffer you might hold for usage growth. This sounds obvious, but many small teams budget cloud spend as if the exchange rate on the day they built the spreadsheet will hold indefinitely. It will not. Whether the shilling strengthens or weakens over your planning period is not something you can predict with confidence, so the discipline is not about guessing the direction — it is about making sure a move in either direction does not break your cash flow.

Second, get visibility into where your dollar exposure actually sits. Many businesses only notice forex impact when the monthly card statement arrives, by which point there is nothing to do except absorb it. Instead, list out every recurring cost that is dollar-denominated: cloud infrastructure, SaaS subscriptions, domain and SSL renewals, API usage fees, payment gateway charges that are dollar-settled, developer tooling licences. Once you have that list, you can see your total monthly dollar burn as a single number, which makes it much easier to reason about than scattered line items across different providers and billing cycles.

Third, look closely at how your bank or card issuer converts the charge. The rate applied on a foreign currency transaction is not always the interbank rate you see quoted in the news — it typically includes a spread, and sometimes an additional foreign transaction fee on top. Over a year, this spread compounds into a meaningful cost. It is worth asking your bank directly what rate and fees apply to foreign currency card transactions and dollar-denominated invoices, and comparing that against what a business or forex-oriented account might offer. The Central Bank of Kenya publishes reference exchange rates that can serve as a rough sanity check against what your bank is applying, though your bank is not obligated to match that reference rate exactly. If you are processing meaningful dollar volume every month, it is worth a conversation with your relationship bank about business account options designed for foreign currency exposure, rather than simply letting a personal or standard business card absorb whatever conversion terms apply by default.

Fourth, consider where you can reduce the dollar-denominated portion of your stack without compromising reliability. This does not mean abandoning major cloud providers — for many workloads, the reliability, security tooling, and regional presence they offer (including data centre options that support data residency needs relevant to Kenyan data protection obligations under the Office of the Data Protection Commissioner) are worth paying for. But it does mean being deliberate. Some SaaS tools have direct local or regional alternatives billed in KES, or local resellers and system integrators who can bill you in shillings at a fixed markup, effectively passing the forex risk to them in exchange for a premium. That premium might be worth paying if it converts an unpredictable cost into a predictable one, particularly for a small business where cash flow certainty matters more than shaving the last percentage point off a bill. It is a legitimate trade-off, not a compromise you should feel bad about.

Fifth, if your own product is priced in shillings for Kenyan customers but your cost base is dollar-linked, build a review cadence into your pricing rather than waiting for margins to erode silently. This is especially relevant for SaaS founders, agencies billing retainer clients, and fintechs running infrastructure-heavy platforms. Decide in advance — quarterly, say, or whenever the shilling moves beyond a threshold you define — that you will revisit pricing. Communicating a price adjustment tied to currency movement, framed honestly, is generally better received by Kenyan business customers than an unexplained increase, because most business owners here understand forex pressure firsthand.

Sixth, be aware of the tax and compliance layer sitting alongside your forex exposure. Kenya has rules around VAT on imported digital services and continues to develop its digital taxation framework through KRA, and invoicing requirements increasingly run through eTIMS. The specific rates, thresholds, and mechanics change and are refined over time, so rather than relying on a fixed figure here, treat this as a standing item to confirm directly with KRA or your tax advisor whenever you sign up for a new cloud or SaaS provider, or whenever your dollar-denominated spend grows meaningfully. Getting this wrong is a compliance problem layered on top of a currency problem, and the two are worth untangling separately.

Finally, for businesses with genuinely large and predictable dollar exposure — a fintech settling significant volumes, an agency with long-term dollar-denominated contracts, a SACCO running core banking infrastructure on a major cloud platform — it is worth having a conversation with your bank about formal hedging instruments such as forward contracts, which let you lock in a conversion rate for a future date. These come with their own costs and are not something to reach for casually or without understanding the terms, but for a business where a currency swing of a certain size would meaningfully damage cash flow, it is a legitimate tool, and Kenyan banks that serve corporate and SME clients typically offer some form of forex risk management product. Ask what is available, what it costs, and what commitment it requires before assuming it is either irrelevant or a silver bullet.

None of this eliminates forex exposure — you cannot opt out of a dollar-denominated cloud market by wishing it were otherwise. What you can do is stop being surprised by it: budget for a range rather than a point estimate, know your total dollar burn, understand what your bank actually charges you for conversion, decide deliberately which costs you are willing to pay a premium to convert into shillings-denominated certainty, and revisit your own pricing on a schedule rather than by accident. That combination turns forex from a recurring shock into a manageable, planned-for line item, which is really all risk management ever is.