CSE Roadmap

Specialist tier · about 2 hours · 8 parts

Part 4 of 8 · 1 min read

Watching spend

Common practice, not from the books.

Money needs monitoring like any other signal (module 2). Common practice:

  • Tag every resource with team and service, so the bill can be split. Unowned resources are the first to be forgotten.
  • Set budgets and alerts on spend, as burn-rate alerts do for error budgets: alert when the month's spend is running faster than planned.
  • Review the top five lines each month and ask whether each is worth it.
  • Show unit cost, such as cost per 1,000 requests or per active user, so growth that pays for itself looks different from waste.

Unit cost

Unit cost is the cost of one useful unit of work, such as one request or one order.

Example: a bill of 4,860 for 100 million requests is 0.0000486 per request, or 0.05 per 1,000.

Check yourself: 1. Why tag resources? 2. What does a spend alert resemble? 3. What does unit cost show that the total hides?