Infrastructure Cost Dashboard: Tracking Cloud Spend Per Customer

AWS and GCP show you your total monthly bill broken down by service: EC2, RDS, S3, data transfer. They don't show you that Customer A costs $340/month to serve and Customer B costs $12, that your enterprise tier operates at 62% gross margin while your growth tier is at 71%, or that three accounts in your free tier collectively consume more compute than your entire paid base.

This information exists in your infrastructure — it just requires connecting billing data to usage data to surface it.

Why per-customer cost attribution matters

Gross margin isn't meaningful as a company-wide average if it varies significantly by customer size, plan tier, or usage pattern. A SaaS company with 60% blended gross margin might have enterprise customers at 45% and SMB customers at 75% — a difference that should drive pricing, packaging, and sales motion decisions.

Without per-customer cost attribution, you can't answer: Is it worth serving the long tail of small customers? Which plan tier should we grow? Are the three hyperscaler accounts worth the infrastructure headache?

How cost attribution works

The approach varies by product architecture, but the pattern is consistent:

Tag your infrastructure. Most cloud providers support resource tagging. Tagging compute resources, databases, and storage by customer ID or customer tier is the prerequisite for any cost attribution. For multi-tenant architectures where resources are shared, attribution requires usage-based allocation — proportional to API calls, data stored, or compute consumed.

Connect billing to usage. Pull your cloud cost data (AWS Cost Explorer, GCP Billing, or your cost management tool of choice) and join it to your usage logs. The join key is the customer or tenant identifier.

Build the attribution model. Decide how to allocate shared infrastructure costs — by seat count, by compute consumption, by revenue weight, or by a hybrid. Document the model so the finance team understands what the numbers represent.

What the dashboard shows

At the customer level:

• Monthly infrastructure cost to serve this account
• Revenue / cost ratio — the inverse of infrastructure cost margin
• Cost trend — is this account's cost growing faster than their ARR?
• Cost breakdown by service — compute-heavy vs. storage-heavy vs. data-transfer-heavy

At the cohort level:

• Cost per customer by plan tier — enterprise vs. growth vs. self-serve
• Infrastructure gross margin by tier
• High-cost outliers — accounts whose cost-to-revenue ratio is outside normal range

The free tier economics problem

Free tier accounts often cost money to serve without generating revenue. The dashboard quantifies exactly how much — which makes the business case for either monetizing high-usage free accounts or restricting free tier resource consumption.

One SaaS team we worked with discovered that 12% of their free tier accounts consumed 40% of their free-tier infrastructure spend. Identifying and converting those accounts — or imposing usage limits — was worth more than any other efficiency initiative they ran that year.

When to build this

The trigger is usually a board question: "What's our gross margin by customer segment?" and the realization that no one can answer it. Infrastructure cost attribution is the prerequisite for that answer. Building the dashboard typically takes 4–8 weeks depending on the complexity of the infrastructure architecture.