11.05 · Concept
Economics, and When to Leave
Weigh cloud spend against the cost of moving, and say why premature infrastructure work kills more startups than cloud bills do.
No video curated for this lesson yet
This lesson is written, ordered and part of the path - the video slot is the only thing still open. We are working through Deployment lesson by lesson; 29 of 56 have their video so far.
The written notes below cover this idea in full - you lose nothing by reading instead of watching.
Cloud migration economics is a break-even decision: compare realistic monthly savings with engineering cost, operational risk, downtime risk, and lost product work. For most startups, optimising the current platform beats moving early, because premature infrastructure projects turn uncertain future savings into immediate payroll and execution cost.
What this lesson answers
- when is cloud migration worth the cost
- how do I calculate cloud migration break even
- why premature Kubernetes adoption hurts startups
Notes
Economics, and When to Leave — Cloud cost economics exists to decide whether engineering time should be spent reducing infrastructure bills or building the product, because moving too early can burn scarce startup runway faster than AWS, GCP, or Azure invoices do.
Key Concepts: - A move is only economically justified when expected savings exceed migration cost: . - If cloud spend is and a migration saves , the gross saving is ; a migration takes…
Common questions
- When should a startup leave a managed cloud platform?
- Leave when the expected savings clearly repay the migration cost within a useful timeframe, after including engineering time, downtime risk, operational burden, and delayed product work. The strongest cases have predictable workloads, high infrastructure cost relative to revenue, and a team ready to own backups, patching, monitoring, incidents, and capacity planning.
- Why is reducing cloud spend often the wrong priority?
- Cloud spend is visible, so it attracts attention, but engineering time is usually more scarce. If a team spends months rebuilding infrastructure before demand and unit economics are proven, it may burn more runway than it saves. In-place improvements such as rightsizing, caching, indexing, lifecycle rules, and autoscaling usually come first.
- What costs are missed when comparing cloud with owned infrastructure?
- Simple price comparisons often ignore the work managed services were doing for you. Owned or self-managed systems need on-call coverage, patching, backups, failover testing, security work, observability, incident response, capacity planning, and compliance evidence. Those labour and reliability costs can outweigh cheaper compute or storage line items.
Short definition: what is Economics, and When to Leave?