Why cost per customer is the question that actually matters
A total monthly cloud-plus-AI-plus-SaaS bill tells you almost nothing about whether the business is getting more efficient or less — it just grows with usage, and a growing number in isolation isn't a signal either way. Divide that same spend by active customers and it becomes a number you can actually compare over time: is it costing more or less to serve the same customer as the product, its usage patterns, and the underlying infrastructure evolve?
This is also exactly where cloud spend and AI/LLM spend converge into one question. A per-request AI cost and a per-customer infrastructure cost are the same idea applied to two different meters — and as more products wrap an LLM around a core workflow, both meters increasingly bill the same customer.
How the calculator works
Cost to serve, per customer, is total monthly cloud, AI/LLM, and SaaS spend divided by active customers. Gross margin percentage is (MRR minus that same total spend) divided by MRR. Gross margin dollars per customer is revenue per customer (MRR divided by customers) minus cost per customer. All three update live as you move the sliders — nothing you enter is sent anywhere.
The verdict band is CostMon's own framing, built around Benchmarkit's 2025 SaaS Performance Metrics report, which puts median SaaS gross margin at 77% (subscription-specific margin runs 75–80%+ for the same cohort). Below 0% is underwater, below 60% is thin, 60–80% is healthy and roughly brackets that median, and 80%+ is strong, top-quartile territory.
What actually moves your cost per customer
Three things move this number, and only one of them is really about infrastructure spend. Customer count moving up while spend stays flat improves it automatically — economies of scale, not optimization. Spend moving down while customers hold steady is the classic FinOps lever: rightsizing idle cloud resources, catching AI cost regressions from a prompt that quietly grew or a model swap that didn't get evaluated for cost, cutting SaaS tools nobody's using.
The third lever is architectural, not operational: a feature that adds an LLM call to every customer request adds a per-customer cost that scales with usage in a way flat infrastructure spend doesn't. That's worth watching on its own, separate from the blended total — a rising AI share of the mix, even with a flat or improving total, is worth understanding before it compounds.
A single estimate isn't the point — the trend is
This calculator is a live, in-browser estimate for a single month's numbers — useful for a gut check, not a substitute for tracking the real trend over time. The number that actually matters is whether cost per customer is improving or degrading quarter over quarter, and answering that requires the real spend and the real customer count, not a manually re-entered guess every time someone wants to check.
CostMon's Unit Economics feature does that continuously: define a business denominator (active customers, requests, transactions), and it computes cost per unit automatically from your connected cloud, AI, and SaaS spend, broken out by connector or dimension and charted over time — so the answer is always current, not something you rebuild by hand.