Your startup can spend the same $1,000 on cloud infrastructure every month and still lose months of runway.
No new servers. No increase in traffic. No change in the provider’s prices.
The exchange rate moves. The same infrastructure takes more naira to keep running.
For a business earning in naira and paying for cloud services in dollars, a flat dollar bill tells only part of the story.
The cost of standing still
Consider a startup with a $1,000 monthly cloud bill.
| Exchange rate | Dollar bill | Naira needed |
|---|---|---|
| ₦1,200/$ | $1,000 | ₦1,200,000 |
| ₦1,500/$ | $1,000 | ₦1,500,000 |
| ₦1,800/$ | $1,000 | ₦1,800,000 |
At ₦1,800 to the dollar, the startup needs an extra ₦600,000 each month for the same workload. Its naira cloud expense has risen by 50%.
These figures are hypothetical stress tests, not historical rates or forecasts. The table isolates currency conversion. Fees and taxes are excluded.
In an actual payment, the conversion rate may be only part of the cash outflow.
Settlement friction changes what leaves the account
A reference exchange rate does not necessarily equal the rate available through your payment provider.
The amount required to settle a dollar invoice can include a conversion spread, funding fees and processing charges. Their size and calculation depend on the payment route.
Consider this separate illustration:
| Component | Assumption | Naira amount |
|---|---|---|
| Invoice converted at reference rate | $1,000 × ₦1,800/$ | ₦1,800,000 |
| Conversion spread | 5% of ₦1,800,000 | ₦90,000 |
| Processing fee | 1% of ₦1,800,000 | ₦18,000 |
| Total settlement outflow | Sum of the three amounts | ₦1,908,000 |
Both percentages apply independently to the original ₦1.8 million. They are illustrative assumptions, not quoted provider charges. Taxes are excluded.
The effective settlement cost is ₦1,908 per dollar of invoice value.
Keep two measures separate:
Conversion rate = naira exchanged ÷ dollars purchased
Effective settlement cost per invoice dollar = total naira settlement outflow ÷ dollar invoice value
The second measure includes the fees in this example. Do not add them again when using it to calculate total cash outflow.
Keep taxes as separate ledger entries with their basis and treatment recorded. Verify VAT, withholding and any credit eligibility for the specific invoice and entity. A combined “tax and processing” percentage hides information the forecast needs.
Use payment records to reconcile actual cash outflow. Preserve the underlying conversion rate and charges so you can explain why it differs from the reference rate.
Separate currency exposure from engineering performance
Before responding to a higher bill, identify what changed.
| Driver | What to investigate |
|---|---|
| Usage | Compute hours, storage, data transfer and requests |
| Provider pricing | Rates, discounts and commitments |
| Service mix | Movement between services, regions or tiers |
| Currency conversion | Naira required to purchase the invoice currency |
| Settlement charges | Funding fees, processing charges and applicable taxes |
Keep the original dollar amount alongside the naira amount.
Imagine engineering reduces the bill from $1,000 to $800. At ₦1,200/$, the original bill cost ₦1.2 million. At ₦1,800/$, the reduced bill costs ₦1.44 million, before fees and taxes.
Dollar spending fell by 20%. Naira spending rose by 20%.
The optimisation worked. Currency movement outweighed the saving.
A report showing only naira can hide engineering progress. A report showing only dollars can hide growing pressure on a naira cash balance.
Bring the cost down to one transaction
The FinOps Foundation’s unit economics framework connects technology spending with the value it creates. For a transaction-based product, cost per completed transaction makes that relationship easier to examine.
Assume our startup completes 100,000 transactions each month. The entire $1,000 cloud bill supports that service.
Cloud cost per completed transaction = allocated cloud cost ÷ completed transactions
| Exchange rate | Monthly naira cloud cost | Cloud cost per completed transaction |
|---|---|---|
| ₦1,200/$ | ₦1,200,000 | ₦12 |
| ₦1,500/$ | ₦1,500,000 | ₦15 |
| ₦1,800/$ | ₦1,800,000 | ₦18 |
These figures continue the currency-only example, excluding settlement fees and taxes.
Dollar cloud cost stays at $0.01 per transaction. Naira cloud cost rises from ₦12 to ₦18.
Suppose the startup earns a ₦30 fee per completed transaction. Infrastructure consumes 40% of that revenue in the first scenario and 60% in the third.
The amount remaining after cloud cost falls from ₦18 to ₦12 per transaction. That remainder still has to cover every other cost before the business can produce a profit.
It is not gross margin. This calculation subtracts only cloud cost. It also measures average cost per transaction, not the marginal cost of processing one more transaction.
Define the denominator with care. Retries and failed requests consume resources, but they are not completed business transactions. Counting them as successful outcomes makes the cost per outcome appear lower.
Where products share infrastructure, allocate the relevant costs before calculating individual unit costs.
Pricing needs a trigger for review
Fixed naira prices create margin pressure when dollar costs rise and other factors do not offset the increase.
That does not make an immediate price increase the right response. Higher prices can affect demand, retention and collections.
Three options deserve examination:
- Contract reviews: For negotiated business contracts, consider agreed review intervals or adjustment clauses where commercially and legally appropriate. Specify the reference measure and review process.
- Usage-based packaging: Examine whether resource-intensive features, storage or data transfer should have limits or separate charges. Compare expected savings with the effect on customers.
- Review thresholds: Set a trigger for engineering, finance and product to investigate together. A rising cloud-cost-to-revenue ratio can initiate a review without automatically initiating a price increase.
The purpose is to give the business time to respond before a payment becomes difficult to fund.
Follow the currency of the cash
A startup holding naira must spend more of that balance to buy the same $1,000 when the naira-per-dollar rate rises.
A startup paying from dollar reserves still spends $1,000.
A higher naira equivalent does not automatically mean a higher dollar cash outflow.
Dollar reserves do not remove every exposure. Naira revenue buys fewer replacement dollars at the higher rate. Meanwhile, unchanged naira expenses translate into fewer dollars, which may partly offset the effect. Future local price increases could reduce that offset, but their timing and magnitude are uncertain.
Track the currencies in which the company earns, spends and holds cash.
“We raised in dollars” is insufficient if the money has already been converted to naira. The company can still face a mismatch between naira reserves and future dollar obligations.
Put the effect on runway
Keep the same startup and assume:
- 100,000 completed transactions per month at ₦30 each.
- All ₦3 million of monthly revenue is collected in the same month.
- ₦4 million in other monthly cash expenses, held constant.
- A $1,000 monthly cloud payment.
- ₦24 million in available cash, all held in naira.
The company buys dollars each month to pay for cloud services.
To isolate currency exposure, the following table and code exclude settlement fees and taxes. The earlier settlement example is separate.
Monthly net cash burn = monthly cash expenses − monthly cash receipts
Runway in months = available cash ÷ positive monthly net cash burn
| Exchange-rate scenario | Total monthly cash expenses | Monthly net cash burn | Estimated runway |
|---|---|---|---|
| ₦1,200/$ | ₦5,200,000 | ₦2,200,000 | 10.9 months |
| ₦1,500/$ | ₦5,500,000 | ₦2,500,000 | 9.6 months |
| ₦1,800/$ | ₦5,800,000 | ₦2,800,000 | 8.6 months |
| ₦2,100/$ | ₦6,100,000 | ₦3,100,000 | 7.7 months |
Between the first and fourth scenarios, estimated runway falls by about 3.2 months.
No additional cloud usage. No lost customers. The dollar bill stays flat.
This is a static sensitivity model. It assumes each rate and the monthly cash flows remain constant. It excludes growth, new funding, one-off payments and changes in collection timing. It is not a forecast of when a particular company will run out of cash.
Reproduce the calculation
This Python example uses the standard library. It varies the exchange rate while holding the workload and dollar bill constant.
from decimal import Decimal
cloud_usd = Decimal("1000")
transactions = 100_000
revenue_per_tx_ngn = Decimal("30")
cash_ngn = Decimal("24000000")
other_expenses_ngn = Decimal("4000000")
# Hypothetical conversion rates. Fees and taxes are excluded.
rates = [
Decimal("1200"),
Decimal("1500"),
Decimal("1800"),
Decimal("2100"),
]
# Assume all revenue is collected in the same month.
monthly_receipts_ngn = transactions * revenue_per_tx_ngn
for rate in rates:
cloud_ngn = cloud_usd * rate
unit_cost_ngn = cloud_ngn / transactions
revenue_remaining_after_cloud_pct = (
(revenue_per_tx_ngn - unit_cost_ngn)
/ revenue_per_tx_ngn
) * 100
total_expenses_ngn = other_expenses_ngn + cloud_ngn
net_burn_ngn = total_expenses_ngn - monthly_receipts_ngn
runway = (
f"{cash_ngn / net_burn_ngn:.1f} months"
if net_burn_ngn > 0
else "No net cash burn under these assumptions"
)
print(
f"FX: NGN {rate:,.0f}/USD | "
f"Cloud/transaction: NGN {unit_cost_ngn:.2f} | "
f"Revenue left after cloud: "
f"{revenue_remaining_after_cloud_pct:.1f}% | "
f"Monthly net burn: NGN {net_burn_ngn:,.0f} | "
f"Runway: {runway}"
)
For an actual cash forecast, add the relevant settlement charges and tax cash flows explicitly, avoiding double counting. For mixed-currency reserves, track each balance and when conversions occur.
A discounted commitment can still become unaffordable
AWS Savings Plans and Google Cloud committed use discounts exchange commitments for lower eligible usage prices. Terms and savings depend on the product, workload and payment option.
A currency movement does not erase the discount against equivalent on-demand usage at the same exchange rate.
Suppose a fully used commitment reduces an eligible $1,000 monthly cost to $700. Then suppose the naira-per-dollar rate rises from ₦1,200 to ₦1,920, an increase of 60%.
| Comparison | Monthly naira cost |
|---|---|
| Original $1,000 cost at ₦1,200/$ | ₦1,200,000 |
| Discounted $700 cost at ₦1,920/$ | ₦1,344,000 |
| Undiscounted $1,000 cost at ₦1,920/$ | ₦1,920,000 |
The discounted cost is 12% above the original naira cost. It is still 30% below the new undiscounted cost.
The saving remains. Affordability has changed.
The risk is committing to payments the company cannot comfortably fund or usage it may not need. Review utilisation, payment timing and cash capacity together. An upfront dollar payment and a future monthly dollar payment have different exposure to subsequent currency movements.
Evaluate hosting alternatives against the full cost
Predictable workloads can justify comparing hyperscalers with dedicated infrastructure or regional providers. That comparison should include more than the server invoice.
Account for migration work, staffing, connectivity, data transfer, backups, recovery testing, security and the cost of downtime.
A local database connected to public-cloud application services may introduce latency, network dependencies or additional transfer charges. Those effects need measurement before migration.
A naira invoice also does not guarantee stable naira prices. Examine the provider’s repricing terms and underlying currency exposure.
Hybrid infrastructure may fit a workload. It is not a guaranteed route to lower cost or equivalent reliability.
Before taking on a migration, address waste in the current environment. Review unattached disks and forgotten staging resources after confirming ownership and retention needs. Schedule non-production capacity around actual usage. Set storage lifecycle policies against retrieval costs, retention obligations and recovery targets.
Every saving should preserve the service the business needs.
Architecture must survive the business’s reality
Can the business continue to afford the technical system it depends on?
A system can meet its performance targets while the assumptions used to fund it stop working.
For a startup earning in naira and settling in dollars, currency exposure belongs in infrastructure planning. It affects the cost of serving customers, the cash needed to operate and the time available to build.
That is the connection I want Runway Architect to make visible.
Your cloud dashboard tracks what your application consumed. Your business must account for what it costs to stay alive.
Top comments (1)
tr.ee/dev-to