Revenue is Vanity, Margin is Sanity
Think of a lemonade stand. You charge $2 per cup. If the lemons, sugar, and cups cost you $1.50, you make $0.50 profit per sale. But if you forget to count the cost of the table, the sign, and the electricity for the refrigerator, you might think you're profitable when you're actually losing money. SaaS businesses face the same trap — but at cloud scale, the hidden costs can sink a company before anyone notices.
In the SaaS world, it is easy to be "Revenue Rich" but "Cash Poor." You might sign a customer for $100/month. But if your cloud infrastructure costs $110/month to serve that customer, every new sale accelerates your losses. This is not a hypothetical — it has killed real companies that grew fast, celebrated their ARR (Annual Recurring Revenue) milestones, and then ran out of cash.
The root cause is almost always the same: the engineering team optimized for features and scale, while nobody tracked the Cost Per Tenant (CPT) — the actual infrastructure cost to serve one customer. Without CPT, pricing is guesswork, and "growth" can be a liability.
The Black Box Problem
For traditional on-premise software, the customer paid for their own hardware. In SaaS, you pay for the hardware (cloud compute, storage, networking, managed services). This shifts enormous financial risk onto the vendor.
The problem compounds because most modern SaaS architectures are Multi-Tenant: you put 1,000 customers into a single database cluster or Kubernetes namespace to reduce overhead. When the AWS bill arrives, it shows "$50,000 for RDS." It does not tell you that Customer A consumed $40,000 of that capacity and Customer B consumed $10. The bill is a black box.
Without decomposing that black box into per-tenant costs, you cannot price your tiers correctly, you cannot identify "toxic" customers who cost more than they pay, and you cannot make rational decisions about which customer segments to pursue or abandon.
Interviewers at growth-stage SaaS companies often ask: "How would you determine if a pricing tier is profitable?" The answer they want is not "look at revenue vs. total AWS bill." The correct answer is: "Instrument the application to measure per-tenant consumption, allocate shared infrastructure costs proportionally, and compare Cost Per Tenant against the tier's monthly revenue. Gross Margin per tier is the key metric."