PricingNest

Usage-Based Pricing Calculator - Price per Unit, Delta & CSV | PricingNest

Free usage based pricing calculator for price per unit, delta comparison, and a delta CSV template export.

Inputs

Scenarios

Applies to the selected input only; adjust other inputs manually if needed.
Examples: API calls, minutes, events, GB, messages.
Support, tooling, baseline infra - anything not per-unit.

Results

Required price per unit
-
-
Estimated monthly revenue
-
-
Estimated monthly gross profit
-
-
Gross margin
-
-

Insights

Auto-generated from your inputs.
Adjust inputs to see recommendations.

Compare

Save a baseline to see deltas for every output.
Required price per unit
Baseline -
Delta -
Estimated monthly revenue
Baseline -
Delta -
Estimated monthly gross profit
Baseline -
Delta -
Gross margin
Baseline -
Delta -

Sensitivity

Adjust the input to see how outputs respond to small changes.
Required price per unit
Low -
Base -
High -
Estimated monthly revenue
Low -
Base -
High -
Estimated monthly gross profit
Low -
Base -
High -
Gross margin
Low -
Base -
High -

Guide

This page is a calculator first, but it's also a quick reference you can share internally. Start with the presets, then adjust inputs and copy the share link. Example defaults for this tool are shown below.

Example Inputs Outputs How it works Modeling tips Validation checks Common mistakes Interpretation Use cases Mini walkthroughs Scenarios Edge cases FAQ

Example (defaults)

Example inputs: Monthly units = 100000, Cost per unit = 0.0002, Monthly fixed cost = 500

Required price per unit
$0.026
Estimated monthly revenue
$2,600.00
Estimated monthly gross profit
$2,080.00
Gross margin
80%

Inputs explained

Input Default Notes
Currency USD Adjust to match your product assumptions.
Monthly units 100000 Examples: API calls, minutes, events, GB, messages.
Cost per unit 0.0002 Adjust to match your product assumptions.
Monthly fixed cost 500 Support, tooling, baseline infra - anything not per-unit.
Target gross margin (%) 80 Adjust to match your product assumptions.

Outputs explained

Output What it means
Required price per unit A money value based on your selected currency.
Estimated monthly revenue A money value based on your selected currency.
Estimated monthly gross profit A money value based on your selected currency.
Gross margin A percentage value derived from the inputs.

How it works

  • We convert fixed monthly cost into a per-unit cost by dividing by monthly units.
  • We add per-unit variable cost to get all-in cost per unit.
  • We solve for price using your target gross margin: price = cost / (1 - margin).

Modeling tips

  • Start with a typical monthly usage level (p50) before modeling higher-volume scenarios.
  • Choose one billable unit customers can forecast (per API call, per 1,000 calls, per GB, or per event).
  • Use a blended unit cost that includes infra, vendor APIs, and any per-unit third-party fees.
  • Put support, on-call, and tooling into fixed cost unless they scale directly with usage.
  • Align target gross margin with your finance policy so pricing is comparable across tools.
  • If you have a free tier, reduce paid units to reflect expected free usage.
  • If usage ramps during onboarding, use a lower initial unit volume to avoid underpricing.

Validation checks

  • Required price per unit should be above unit cost; if not, check margin or fixed cost inputs.
  • Fixed cost per unit = fixed cost / monthly units. Compare it to unit cost for sanity.
  • Estimated gross margin should be close to your target; large gaps suggest a math or input issue.
  • Compare implied price per unit against competitor ranges to confirm market realism.
  • If fixed cost per unit dominates total cost, consider a base platform fee.

Common mistakes

  • Choosing a usage unit that customers cannot estimate.
  • Ignoring free-tier usage when modeling paid units.
  • Using only p50 usage and skipping p90 stress tests.
  • Setting margin targets without including all COGS inputs.
  • Skipping a base fee when fixed costs are material.

Interpretation

  • Treat the required unit price as your floor, not necessarily your list price.
  • If the unit price looks high, shift more revenue to a base platform fee.
  • If required price per unit swings between p50 and p90, use tiered breakpoints and clear overage guardrails.
  • Use p50 and p90 scenarios to decide tier boundaries and overage rates.
  • Compare the implied price to competitors to confirm market fit.

Use cases

API metering
Price per call or per 1,000 calls and validate the margin with blended unit costs.
Event analytics
Charge per event or per million events while recovering fixed overhead with a base fee.
Per-GB pricing
Estimate a per-GB floor for storage or bandwidth when cost and usage are metered monthly.

Mini walkthroughs

Set a margin-safe unit price
  1. Enter p50 monthly units and your blended unit cost.
  2. Add fixed overhead and target gross margin.
  3. Use required unit price as the pricing floor.
Validate with heavy usage
  1. Increase monthly units to a p90 scenario.
  2. Check if margin holds at scale.
  3. Adjust base fee or tiering if needed.
Convert API cost estimate to price per 1,000 calls
  1. Set monthly units to total API calls and divide your variable cost to a per-call value.
  2. Use target margin to calculate required price per call.
  3. Multiply by 1,000 to convert to a price per 1,000 calls for packaging.

Scenarios

Event-driven SaaS
Model 100k events per month at $0.0002 cost and $500 fixed overhead to price an analytics API.
High-volume platform
Use 5M units per month with lower unit cost to see if price can stay competitive while hitting margin.
Low-volume premium
Use 20k units and higher cost to validate whether a minimum fee or tier is needed.
Free tier impact
Reduce paid units to reflect free usage and test whether a platform fee is needed.

Edge cases

  • If monthly units are 0, pricing will be undefined; use a minimum platform fee instead.
  • If target margin is 100%, the required price will be infinite. Use a realistic margin ceiling.
  • If unit cost is 0, price is driven only by fixed cost allocation.
  • If monthly units are very low, price per unit can be misleading without a base fee.

FAQ

How do I calculate price per unit?
Price per unit = (unit cost + fixed cost per unit) / (1 - target gross margin). This calculator applies that formula using your inputs.
Can I use this as a cost per use calculator?
Yes. If one customer action maps to one billable unit, this works as a cost per use calculator.
How do I estimate usage cost before setting price?
Estimate usage cost from monthly units x cost per unit, then add fixed overhead and apply your target margin.
How do I build a price-per-unit delta CSV template?
Save a baseline scenario, adjust your inputs, review output deltas, then use Download CSV to export a reusable price-per-unit delta CSV template.
How do I choose a usage metric customers can understand?
Use a unit customers already monitor in dashboards and invoices, such as API calls, events, minutes, or GB. Avoid internal metrics users cannot forecast.
Is this a usage based pricing calculator?
Yes. It estimates a per-unit price from costs and a target margin, which is the core pricing step for usage-based models.
What is usage-based pricing?
Usage-based pricing charges customers based on consumption (calls, events, GB, minutes) instead of seats or flat tiers.
What should I use for cost per unit?
Use your marginal cost for one unit (compute time, bandwidth, storage requests, vendor fees) in your chosen currency.
Can I use this for per-GB pricing?
Yes. Set monthly units to your total billable GB, use your blended cost per GB, and the calculator will return a required per-GB price at your target margin.
Why does the required unit price change so much?
Fixed costs get spread across monthly units. Lower volume means higher fixed cost per unit and a higher required price to hit the same margin.
Should I include payment fees or taxes in unit cost?
Include any fees that scale with revenue or usage if they materially affect margin. Taxes are usually excluded from pricing models.
How do I model a minimum fee with usage pricing?
Set a base platform fee outside this calculator and then price the usage units based on the required per-unit price.