SAAS INFRASTRUCTURE COST PER CUSTOMER
SaaS Infrastructure Cost per Customer & Revenue
Revenue alone does not show whether a SaaS product is becoming more expensive to operate. Project Economics is designed to put attributable technical cost beside revenue context.
What problem does it solve?
- Project-level attribution
- Exact, estimated and Unallocated cost
- Forecasts, budgets and anomaly context
- Read-only by default
What to check first
- Establish current spend, previous-period spend and forecast using the same scope.
- Use Spend velocity versus the previous hour/day/week as the first provider-specific check, then attribute spend by project or service. Leave uncertain cost unallocated instead of guessing.
- Rank the top cost drivers by absolute money and growth rate, then investigate the first few deeply.
- Attach every saving or budget action to an owner, expected impact and a verification date.
Metrics and signals that matter
- Spend velocity versus the previous hour/day/week
- Cost by provider, project, service and environment
- Deployment, traffic, retry and job timestamps around the first inflection
- Exact, estimated and unallocated cost separated instead of blended
Likely causes
Deployment or configuration regression
A release can change request fan-out, runtime, memory, model choice, logging volume or cache behavior without obvious user-facing breakage.
Missing ownership creates blind spots
Project, team, environment and customer dimensions must survive ingestion; otherwise shared spend becomes impossible to act on.
Billing dimension changed
For your cloud/AI stack, investigate Spend velocity versus the previous hour/day/week and Cost by provider, project, service and environment before assuming the total moved for a single reason.
How it works
Measure technical economics, not only spend
Automatic Project Map, provider evidence and technical activity are combined to narrow the investigation while ambiguous spend remains Unallocated.
Preserve attribution confidence
CostNerve preserves exact versus estimated provenance, uses read-only access by default and exposes incomplete discovery rather than manufacturing certainty.
Worked example with explicit assumptions
Illustrative allocation: of 1,000 USD, 600 USD has direct project evidence, 300 USD uses a documented shared-cost rule and 100 USD remains unallocated. Coverage is 90%; that does not make the 300 USD allocation direct billing evidence.
Frequently asked questions
Which your cloud/AI stack signals should I inspect first?
Start with Spend velocity versus the previous hour/day/week, Cost by provider, project, service and environment, Deployment, traffic, retry and job timestamps around the first inflection. Compare the same time window before and after the change so volume and unit-cost effects do not get mixed.
What belongs in cost per customer?
State which infrastructure, AI and shared-service costs are included, the allocation rule and the matching period. Report excluded and unallocated amounts. Technical contribution margin is not net profit: salaries, taxes and other business costs may be outside the calculation.
Should uncertain cost be forced into a project?
No. Keep it unallocated until tags, project IDs, resource IDs or another reliable signal justify attribution. False precision produces worse decisions than visible uncertainty.