Unit Economics¶
Unit Economics helps you understand cloud cost in terms of useful units: customers, users, API calls, transactions, orders, tokens, GB processed, workflows, employees, or service-level usage.
CloudVerse AI separates Unit Economics into two views:
- Business Unit Economics — perspective-level cost divided by a business volume, such as cost per customer or cost per API call.
- Service Unit Cost — service-level technical cost divided by provider usage, such as cost per GB stored or cost per runtime hour.
When to use it¶
- You want to know whether cloud cost is scaling efficiently with business activity.
- You need cost per customer, user, API call, transaction, token, or another business unit.
- You want engineering teams to inspect technical cost per service usage unit.
- You need to compare business growth, usage growth, and cloud cost in one view.
- You want a simple metric that finance, product, and engineering teams can discuss together.
Before you start¶
Unit Economics starts from a Dynamic Perspective. The Perspective defines the cost scope: team, application, cost center, environment, product, or another business view.
Before configuring a business unit, confirm the Perspective includes the correct cloud accounts, projects, services, tags, virtual tags, or master tags.
The Perspective controls the numerator
Unit Economics uses the selected Perspective and page filters to calculate cost. If the Perspective rules are incomplete, the cost per unit will also be incomplete.
Open Unit Economics¶
Go to Cost Management > Unit Economics from product navigation.
Select:
- A Dynamic Perspective.
- A Date range.
- A Grain — Daily or Monthly.
- Any provider, account, region, service, cost type, or cost metric filters.
The cost shown in Unit Economics follows the same Perspective cost source used by Cost Explorer and dashboard-style cost views.
Choose the right tab¶
| Tab | Use it for | Example |
|---|---|---|
| Business Unit Economics | Business-facing cost per unit for the selected Perspective. | Cost per customer, API call, transaction, order, or token. |
| Service Unit Cost | Technical cost per service usage unit inside the Perspective. | Cost per GB stored, runtime hour, request, or slot hour. |
Use Business Unit Economics when you already know the business volume. Use Service Unit Cost when you want to inspect cloud service efficiency before choosing a business denominator.
Business Unit Economics¶
Business Unit Economics divides filtered Perspective cost by a business volume you provide.
For example:
Cost per customer = filtered Perspective cost / active customers
Cost per 1K API calls = filtered Perspective cost / (API calls / 1,000)
Cost per 1M tokens = filtered Perspective cost / (tokens / 1,000,000)
If no business unit is configured yet, the page still shows the selected Perspective and cost context, then guides you to configure a business unit.
Configure a Business Unit¶
Click Configure Business Unit.
The setup drawer has three steps.
1. Choose a business unit¶
Choose what you want to measure cost per.
| Option | Use it when |
|---|---|
| Cost per Customer | You track active customers, tenants, or paying accounts. |
| Cost per User | You track active users, monthly users, or seats. |
| Cost per API Call | You run APIs, gateways, inference endpoints, or request-driven systems. |
| Cost per Transaction | You process payments, workflows, events, or business transactions. |
| Cost per Order | You run commerce, marketplace, fulfillment, or order-processing systems. |
| Cost per GB Processed | You process data, files, logs, or analytics workloads. |
| Cost per Workflow | You run jobs, pipelines, automations, or completed workflows. |
| Cost per Employee | You measure internal tools or shared services by employee count. |
| Cost per Token | You track AI or LLM workloads by input/output token volume. |
| Custom | Your business unit is not covered by the standard templates. |
CloudVerse AI uses the selected template to prefill names, labels, and reporting defaults. You can still adjust the metric name and unit label before publishing.
Start simple
Choose one primary business unit first. Add more only after the first metric is stable and trusted.
Display rate¶
Display rate changes only how the final rate is shown. It does not convert or change the values you enter.
| Display rate | Example with 1,000,000 API calls and $10,000 cost |
|---|---|
| Per API call | $0.01 / API call |
| Per 1K API calls | $10 / 1K API calls |
| Per 1M API calls | $10,000 / 1M API calls |
Smart defaults are applied by template.
| Business unit | Typical display |
|---|---|
| Customer, user, order, GB processed, workflow, employee | Per unit |
| API call, transaction | Per 1K units |
| Token | Per 1M tokens |
2. Add values¶
Choose how business volume arrives.
| Source | What it does | Best for |
|---|---|---|
| Manual grid / CSV | Enter values in the drawer or upload the generated CSV template. | Fast setup, finance-owned monthly values, first backfill. |
| API push | Create a source that receives observations through the API. | Automated daily or monthly updates from an internal system. |
| Warehouse query push | Store query metadata and push query results into CloudVerse AI. | Teams that calculate business volume in a warehouse, then push the results. |
For Manual grid / CSV, choose:
- Grain — Daily or Monthly.
- Metric value date range — the period where you want to enter business values.
- Values for the generated periods.
You can also click Download CSV template, fill it, and upload it back with Upload filled CSV.
CSV format:
period,value,label
2026-06-01,12000,
2026-07-01,12600,
| CSV column | Required | Meaning |
|---|---|---|
period |
Yes | Date for the period. Monthly values are normalized to the first day of the month. |
value |
No | Business volume for that period. Blank means missing. |
label |
No | Optional label for future breakdowns. It is not used in the current report. |
Value rules¶
| Value | Meaning | Result |
|---|---|---|
| Blank | Missing period. | Excluded from cost-per-unit calculation and shown as a warning. |
0 |
Real zero denominator. | Accepted, but rate is hidden for that period. |
| Negative number | Invalid business volume. | Blocks preview and publish. |
| Positive number | Valid business volume. | Used in cost-per-unit calculation. |
You can publish with partial data if at least one valid period exists. Missing values reduce coverage and appear as warnings.
Blank is not zero
Leave a period blank when you do not have the value yet. Enter 0 only when the true business volume was zero.
3. Preview and publish¶
The preview shows:
- Total filtered cost.
- Entered business volume.
- Average cost per unit.
- Period coverage.
- Cost-weighted coverage.
- Missing period warnings.
- Zero-denominator warnings.
- Any blockers that must be fixed.
Click Publish when the preview looks correct. After publishing, the drawer closes and the Business Unit Economics dashboard refreshes.
Read the Business Unit Economics dashboard¶
When a business unit is configured, the dashboard shows:
| Field | Meaning |
|---|---|
| Cost per unit | Filtered cost divided by business volume, using the selected display rate. |
| Total Allocated Cost | Cost for the selected Perspective, date range, grain, and filters. |
| Business Volume | Sum of matching business values for the report period. |
| Status | Whether the metric is configured, pending data, partial, stale, or blocked by grain mismatch. |
| Business trend | Cost bars, business-volume line, and cost-per-unit line over time. |
| Guardrails | Warnings about missing values, zero denominators, low coverage, or incompatible grain. |
Grain rules¶
| Metric grain | Report grain | Result |
|---|---|---|
| Daily | Daily | Supported. |
| Daily | Monthly | Supported. Daily values roll up to monthly totals. |
| Monthly | Monthly | Supported. |
| Monthly | Daily | Blocked. Daily rates cannot be calculated from monthly-only business values. |
Monthly metrics cannot create daily rates
If your business data is monthly, use Monthly grain on the page. To see daily cost per unit, configure or import daily business values.
Service Unit Cost¶
Service Unit Cost helps engineering teams inspect technical cost efficiency inside the selected Perspective.
It groups Perspective cost by tower and service, then shows candidate usage units for the selected service.
Use it to answer questions like:
- Which services drive the selected Perspective cost?
- What usage units are available for each service?
- Is cost increasing because usage increased or because unit cost changed?
- Which service should be investigated before choosing a business metric?
Inspect service-level cost¶
- Open Service Unit Cost.
- Select a tower or service from Services by tower.
- Review the selected service cost.
- Choose a usage candidate.
- Read the trend: service cost, usage, and cost per unit.
Usage candidates¶
A usage candidate is a provider usage signal available for the selected service, such as requests, GB-month, hours, GB processed, or token count.
Some services have multiple candidates because providers expose multiple meters for the same service.
Do not compare unrelated units
A shared label such as byte-seconds or requests can mean different things across services. Service Unit Cost calculates usage candidates per service so unrelated units are not mixed together.
Common workflows¶
SaaS cost per customer¶
- Select the application or product Perspective.
- Open Business Unit Economics.
- Click Configure Business Unit.
- Choose Cost per Customer.
- Use Monthly grain if customer counts are monthly.
- Enter or upload active customer counts.
- Preview and publish.
API cost per 1K calls¶
- Select the API or platform Perspective.
- Choose Cost per API Call.
- Keep the suggested display rate, usually Per 1K API calls.
- Use Daily grain if API request counts are available daily.
- Enter values, upload CSV, or publish an API push source.
- Preview and publish.
Data platform cost per GB processed¶
- Select the data platform, pipeline, or analytics Perspective.
- Choose Cost per GB Processed.
- Enter daily or monthly processed GB values.
- Review cost per GB processed and coverage.
- Use Service Unit Cost to inspect which cloud services drive the result.
AI cost per 1M tokens¶
- Select the AI workload Perspective.
- Choose Cost per Token.
- Use the suggested display rate, usually Per 1M tokens.
- Import token volume from your application, API logs, or warehouse.
- Preview and publish.
Common questions¶
Why does Business Unit Economics need a Perspective?¶
The Perspective defines which cloud costs are included. Business volume is only meaningful when it is matched to the right cost scope.
Why is my cost per unit unavailable?¶
Common reasons:
- No business values exist for the selected period.
- The business metric is monthly but the page is set to Daily grain.
- The denominator is zero for the period.
- The selected filters return no cost.
Why does coverage matter?¶
Coverage shows how much of the selected cost period has matching business values. Low coverage means the cost-per-unit trend may not represent the whole period.
Why can I publish with missing values?¶
Missing values are allowed so teams can start with the data they have and backfill later. Missing periods are excluded from the rate calculation and shown as warnings.
Why do Service Unit Cost candidates show provider meters?¶
Provider billing data often has multiple meters per service. CloudVerse AI shows the candidates separately so you can choose the unit that best explains the service cost.
Troubleshooting¶
| Problem | What to check |
|---|---|
| No cost appears | Confirm the Perspective, date range, provider, account, region, service, cost type, and cost metric filters. |
| Business unit is not configured | Click Configure Business Unit and publish at least one valid value or source. |
| Cost per unit is unavailable | Check for missing values, zero denominators, or a monthly metric viewed with Daily grain. |
| API push source is pending | Push observations into the published source, then refresh the report. |
| CSV upload does not fill values | Confirm the period values are inside the selected date range and match the selected grain. |
| Service Unit Cost has no usage candidates | Usage data may be unavailable for the org, provider, service, or selected date range. |
| Unit Economics cost does not match another report | Compare the same Perspective, date range, provider, cost type, and cost metric. |
For missing provider data, see Missing or delayed data.
Best practices¶
- Confirm the Perspective scope before trusting cost per unit.
- Start with one business metric, then improve coverage over time.
- Use Monthly grain when business values are only available monthly.
- Use Daily grain only when daily values are reliable.
- Keep unit definitions stable. Changing what counts as a customer, order, or transaction breaks trend comparisons.
- Treat missing values as data-quality work, not as zero activity.
- Use Service Unit Cost to investigate technical drivers behind a business cost-per-unit change.
Related pages¶
- Cost Explorer — validate filtered cost using the same scope.
- Perspectives — create and maintain business cost scopes.
- Anomaly Detection — investigate unexpected spend changes.
- Budgets — compare spend against budget targets.
- Reports — share recurring cost views.