AWS Unit Economics Calculator
Is your infrastructure eating your margins? Calculate your cost per customer and cost per request to see your real unit economics.
What's your monthly AWS spend?
Include compute, database, networking, and all AWS services.
Tip: Use AWS Cost Explorer (Billing Dashboard) to find your total monthly spend across all services.
Who This Tool Is For
SaaS founders, finance teams, and CTOs who need to understand the true cost of their infrastructure relative to their revenue. If you're pricing your product, fundraising, or wondering if your gross margins are healthy, this calculator gives you immediate visibility into unit economics.
Why We Built This Tool
Most SaaS companies know their burn rate but not their unit economics. They see a $10k AWS bill and a $50k MRR, but they don't connect them. This tool makes it obvious: if your cost per customer exceeds 25% of ARPU, your pricing or architecture is broken. Startups that know this early can fix it. Those that don't often discover it too late.
What Problem It Solves
- Pricing blind spots. You can't price your product intelligently without knowing unit economics.
- Margin confusion. Finance doesn't know why gross margins are lower than expected. This reveals the infrastructure cost component.
- Scaling anxiety. Founders fear that growth will destroy margins. This shows whether that's true.
- Architecture decisions. Should you use Lambda or EC2? Serverless or managed? This helps you choose.
Learn more about our AWS cost optimization services or architecture consulting.
How to Use This Tool
- Enter your monthly AWS spend. Find this in AWS Billing Dashboard.
- Tell us your usage metrics. How many paying customers? How many API requests per month?
- Enter your MRR. Your total monthly recurring revenue.
- Get your unit economics. See cost per customer, cost per request, and margin health.
Frequently Asked Questions
What counts as "customers"?
Paying customers who generate revenue. If you have free tier users, don't include them here. This is your revenue-generating base.
What if my costs vary wildly month to month?
Use your average. Take the last 3 months of AWS billing and average them. This smooths out one-time costs and gives you a realistic baseline.
How do I know if my unit economics are healthy?
A rule of thumb: your cost per customer should be less than 25–30% of ARPU. If it's higher, you're either underpriced or over-architected. If it's lower, you have pricing power.
Can I use this if I'm not yet profitable?
Yes. This is especially useful for early-stage companies. Understanding unit economics early helps you avoid building an unprofitable product. If your cost per customer already exceeds your ARPU, fixing that now is cheaper than fixing it at scale.