Cost at scale: unit economics and FinOps
The bill says how much; the unit cost says whether. Price each line per unit before cutting anything.
Predict first
Before you read: predict
A video-course platform has 50,000 active learners a month. It runs 40 instances at $400 a month each, and each learner streams 3 GB of lessons a month from object storage that charges $0.05 per GB sent to the internet (scenario prices). Storage costs the same per GB at every provider.
Which one change cuts the cost per active learner the most?
The 30-second version
Divide each month's cost by the units of value it delivered: per sitting, per user, per order. Fixed lines spread thinner as units grow; per-unit lines do not. At scale the growing lines are data sent out, data kept, logs and per-request services, which cheaper instances never touch. Inform, then optimize, then operate, and measure again.
The bill says how much; the unit cost says whether. Price each line per unit before cutting anything.
How it works
Step 1 of 12
In the kitchen
- the costs per bed-night, not the month's pile of invoices → unit cost (steps 1–2)
Analogy: A youth hostel's cost per bed-night
The warden is asked why the costs keep rising when the beds are no fuller.
| At the hostel | In the bill |
|---|---|
| the costs per bed-night, not the month's pile of invoices | unit cost (steps 1–2) |
| the lease and the warden's salary are the same in a full or empty month; breakfasts and sheets grow with every guest | fixed and per-unit lines (step 3) |
| the guest wifi is billed per GB over the plan, and one coach party streaming the football fills the bill | data sent out (step 4) |
| every guest's registration card is boxed and stored at a records firm that charges per box per month, and nobody ever shreds a box | storage held with no expiry (steps 5–6) |
| shredding cards once they are two years old caps the shelf | an expiry rule (step 6) |
| the contract laundry charges per sheet washed | per-request services (step 8) |
| a cheaper boiler saves little when the laundry and the wifi are what grew | right-sizing (step 9) |
| the manager splits every invoice by dormitory first, then lists the cuts, then writes the winners into the season's house rules | Inform, Optimize, Operate (steps 10–12) |
Breaks down when: a hostel's invoices are a handful of paper bills; a cloud bill has thousands of lines metered by the hour, so allocation needs tags, not the warden's memory.
Contrasting case: a campsite with a flat pitch fee and no services: nothing grows per guest, so the cost per night only falls as it fills (step 3 with no per-unit line).
In real terms: price every line per unit of value, find the line that grows with each unit, and pull the lever on that line.
Examples, run for real
Prices are scenario values: $0.09 per GB sent out and $0.023 per GB-month at the first store, nothing sent out and $0.015 per GB-month at the second, instances $2,000 a month.
4.1 ExamHall EXH-4290: the review player's egress
Each ECON-201 sitting records 2,400 candidates for 120 minutes at 0.5 Mbit/s, and reviewers stream every recording once. ExamHall holds 40 sittings a month and keeps recordings 90 days.
4.1 per sitting: 1,080 GB of video · before: instances $50 + playback out $97.20 + storage $74.52 = $221.72 · instances 30% cheaper: $206.72
4.1 MR: zero-egress store at $0.015/GB-month, 90-day rule · instances $50 + playback out $0 + storage $48.60 = $98.60
The proposal on the table was cheaper instances: $15 a sitting. MR !4590 moves the recordings to a store with free egress instead, and the cost per sitting falls by more than half (steps 4, 9).
4.2 Fixed lines spread thinner
4.2 cost per sitting after the MR: 20 sittings $148.60 · 40 sittings $98.60 · 80 sittings $73.60
The instances are fixed; the storage grows with each sitting (step 3).
4.3 What is kept
4.3 storage bill at 40 sittings a month · no rule: month 1 $648, 3 $1,944, 6 $3,888, 12 $7,776 · 90-day rule: month 1 $648, 3 $1,944, 6 $1,944, 12 $1,944
Same sittings every month, with and without the rule (steps 5–6).
4.4 The loop on ExamHall
Optimize ranks the options by dollars per sitting: egress path, then retention, then instances. Operate makes the lifecycle rule and the new store every board's default, and checks next month's cost per sitting against $98.60 (steps 10–12).
Try it
Answer first, then check. Nothing is saved.
Question 1 of 6
A ticketing platform's cluster, database and support plan cost $24,000 a month and carry up to 60 on-sales; beyond 60, a second cluster adds $18,000 a month. Each on-sale adds $300 of egress, queue and payment-API charges. Last month it ran 40 on-sales; this month it runs 80.
What is this month's cost per on-sale?
Question 2 of 6
A chat app has 2 million monthly active users. It runs 20 instances at $600 a month each, and each user's requests write 15 MB of logs a month, 90% of them written by requests that succeed. Logs cost $0.50 per GB ingested and $0.03 per GB-month, kept for 30 days (scenario prices; 1 GB = 1,000 MB).
Which one change cuts the cost per user the most?
Question 3 of 6
In a design round you priced a payments app's API gateway at $3.50 per million calls (a scenario price): 2 million orders a month, 4 calls each, $28 a month. The interviewer asks: next year orders triple, and the order page polls for status, so an order makes 20 calls instead of 4.
What does the gateway line cost a month then?
Question 4 of 6
A video app wrote 1,000 GB of logs in month 1, and each month it writes 500 GB more than the month before (1,500 GB in month 2, 2,000 GB in month 3). Storage is priced at $0.02 per GB-month and measured at the end of each month (a scenario price). A lifecycle rule deletes every log older than six months.
What is the log-storage bill for month 18?
Question 5 of 6
A ticketing company's FinOps team sends each event promoter a monthly sheet: the cloud spend its events caused, and what that comes to per ticket sold.
In the FinOps Framework, which phase is this work?
Question 6 of 6
A payments app's monthly bill rose from about $28,900 to about $43,600 while active users grew from 100,000 to 120,000. Compute autoscales at $0.25 a month per active user. Each user downloads statements, and a new statement viewer raised that from 0.5 GB to 2 GB a month, at $0.05 per GB sent out. Logs: 10,000 GB written each month since launch and never deleted, at $0.02 per GB-month; this is month 8 (scenario prices).
Which line accounts for most of the rise?
Go deeper
Pro tips
- In a design round, name the one cost line that scales with your core unit and one lever for it (retention period, egress path, sampling rate).
When: asked what a design costs or what trade-off you made (steps 1, 4–8). Verify:
Status: RAN.tip before the MR · the line that scales with each sitting: playback out $97.20 of $221.72 · its lever: the egress path
Source
quote-check.mjs finds every passage below verbatim in its saved text. Valid as of 2026-10-15.
- FinOps Foundation, FinOps Framework: FinOps Phases: https://www.finops.org/framework/phases/ (
finops-phases.txt). The row's first source. Quoted: "FinOps is performed by working iteratively on the Framework Capabilities through three phases: Inform, Optimize and Operate." · "The FinOps activities in Data Ingestion, Allocation, Reporting & Analytics, Forecasting, and Unit Economics provides information to assess budgeting, forecasting trends, analyze KPIs, benchmark, and report on metrics" · "In the Optimize phase, FinOps activities involve identifying opportunities to improve efficiency and value using the view of the technology landscape gathered in the Inform Phase." · "Optimization options may include both usage optimization (using fewer resources to achieve an acceptable outcome) and rate optimization (paying an appropriate amount for the resources we must use)." · "In the Operate phase, FinOps activities involve implementing changes identified in the Optimize phase to improve the state of the technology estate." - Cloudflare R2 pricing: https://developers.cloudflare.com/r2/pricing/ (
r2-pricing.txt). The row's second source. Quoted: "There are no charges for egress bandwidth for any storage class." and "Storing 3 GB constantly for 30 days will be charged as 3 GB-month." - AWS, Amazon EC2 On-Demand Pricing, Data Transfer (the row's third source names the AWS data transfer price): https://aws.amazon.com/ec2/pricing/on-demand/ (
aws-ec2-pricing.txt). The fetched text fills its prices in a browser script, so the saved text shows the tiers but no figure: "First 10 TB / Month" is followed by a template placeholder, not a price.
Related lessons
Checked against the tools and docs as of 2026-10-15.