# Unit Economics for Cloud Cost: Per-MAU, Per-Order, Per-Request > Why unit economics changes how engineering teams prioritize cloud cost work. Source: https://zop.dev/learn/unit-economics-for-cloud-cost Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, learn --- Raw cloud cost answers "how much do we spend." Unit economics answers "how much do we spend per unit of business value." A team that spends $200,000 a month sounds expensive until you learn the product serves ten million monthly active users at two cents each. A team that spends $30,000 a month sounds cheap until you learn the product serves only fifty thousand users at sixty cents each. Unit economics is the bridge between cloud cost and product or business outcomes. It turns infrastructure spend into a metric that finance and product care about, and it changes how engineering teams prioritize cost work. A recommendation that drops cost per MAU by ten percent is more interesting than one that saves more dollars but barely moves the per-user cost. This article covers the four standard unit metrics, how to set them up, and how unit economics changes optimization priorities. This guide keeps the theory short and spends most of its length on what you can actually do. Every recommendation here is one ZopNight can help you execute, starting from a read-only connection. ## The four standard unit metrics Cost per MAU is the most widely tracked metric for SaaS and consumer products. It is total cloud cost divided by monthly active users. Cost per order is the equivalent for e-commerce and marketplace products. Cost per request is closer to the metal: cloud cost divided by total served requests, useful for API products and platform teams. Cost per signup measures cloud spend against new user acquisition, useful for products in growth mode where MAU lags signups by months. ## Setting up the data pipeline Each unit metric needs two streams: cost (already available from the cloud bill) and a business event count (from the analytics platform, the e-commerce platform, the application logs, or the signup pipeline). The join cadence depends on the metric. MAU is monthly. Orders and signups can be daily. Requests can be sub-hourly. Most platforms support three ingestion modes: CSV upload for monthly numbers, Push API for real-time events, and Pull API for systems that publish their own metrics on a schedule. ## How unit economics changes prioritization Without unit economics, recommendations rank by dollar savings. The biggest savings get the most attention. With unit economics, recommendations rank by their impact on the unit metric. A $5,000-per-month savings on an idle dev cluster is still useful but ranks below a $5,000-per-month savings on the production database fleet, which actually drops cost per request. The same dollar amount produces a different priority because one moves the unit metric and the other does not. ## Composing with showback and budgets Unit economics composes with team-level showback. Cost per MAU at the platform team versus the product team is more useful than the global average. It also composes with budgets: a team can set a budget on cost per MAU rather than on raw cloud cost, which captures the goal more precisely. Engineering excellence under unit economics looks like cost per request that drops as request volume grows, rather than cost that grows linearly. ## Key takeaways - Unit economics turns infrastructure spend into a metric finance and product care about. - Four standard unit metrics: cost per MAU, per order, per request, per signup. - Three ingestion modes: CSV for monthly cadence, Push API for real-time, Pull API for scheduled sources. - Unit-economics-aware recommendations rank by impact on cost-per-unit, not raw dollars. - Compose with showback to get cost per MAU per team or per segment. ## Where ZopNight fits ZopNight turns this from reading into doing. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided, and it starts read-only so you can see the opportunity before you act on any of it. The most direct place to begin is scheduling non-production resources to your working hours, which is covered in the [FinOps](https://zop.dev/learn/finops) guide and shown concretely for [AWS EC2](https://zop.dev/zopnight/aws/ec2). ## How ZopNight schedules non-production resources The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled. Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like "dev-cluster" or "staging-db" so a whole environment follows one cadence. Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it. ## Getting started Getting started is intentionally low-stakes: - Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage. - Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status. - Create a schedule in your timezone and attach the non-production resources or groups you want it to cover. - Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing. Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action. ## Frequently asked questions ### Do I need a separate finance team to use unit economics? No. Engineering teams can adopt unit economics independently. The metric is useful for prioritization regardless of whether finance is in the loop. Adding finance later is straightforward because the data and dashboards are already in place. ### Can I track multiple unit metrics simultaneously? Yes. Most teams track at least cost per MAU and cost per order or cost per request. Custom metrics are also supported for product-specific outcomes.