Usage based pricing simulator

Use this tool alongside the saas pricing guide. Estimate recurring revenue and gross profit from included usage, overage rates and serving costs.

Which inputs do you need?

Before entering numbers, choose the unit of analysis. An account, a user and a paying subscription are different objects. Counting users in one field and accounts in another can produce a precise answer to the wrong question. Record the start and end dates beside your source export so another person can reproduce your work.

What formulas does the calculator use?

Monthly bill per account

bill = base + Math.max(0, usage - included) * rate

This output is expressed as currency in the same units as the inputs.

Monthly recurring revenue

mrr = accounts * bill

This output is expressed as currency in the same units as the inputs.

Monthly gross profit

profit = accounts * (bill - usage * cost)

This output is expressed as currency in the same units as the inputs.

Gross margin

margin = mrr > 0 ? profit / mrr * 100 : NaN

This output is expressed as a percentage.

Percent fields use whole percentages: enter 5 for five percent. The formula divides by 100 where a decimal rate is needed. Values in the formulas correspond to the labelled inputs above; earlier outputs can be used by later formulas.

Worked example

The defaults are a constructed scenario, not results from a named company or survey. With the example inputs above, the calculation produces:

Change one assumption at a time and watch the main result. Then test a conservative case by reducing the expected benefit or increasing the associated cost. If a decision works only at the most optimistic settings, investigate the uncertain input before committing the budget.

How should you interpret the result?

• Average usage conceals heavy users. Run the calculation again for a low-usage and a high-usage account. A flat average cannot model a tiered distribution.

A formula describes the assumptions entered into it. It cannot establish that a channel caused a sale, that historical retention will continue, or that a projected cost is achievable. Compare the output with your own previous cohorts before using a broad market comparison.

For a management review, save the result together with the source date, segment, owner and planned action. Recalculate when the underlying input changes. Keep a separate copy of the original scenario so the team can explain the difference between the plan and the observed outcome.

Continue the analysis

Use the metrics guide to align definitions, browse all calculators for adjacent calculations, and keep a measurement worksheet beside the model. The pricing hub and growth hub cover decisions that often change these inputs.

Apply usage based pricing simulator in a working review

Record the source and unit of every input before using the result. Change one assumption at a time to understand which inputs matter most. Keep outputs that describe money, time and percentages distinct, and preserve undefined cases rather than converting them into plausible-looking zeroes.

For this topic, involve the pricing owner with finance, product and customer-facing input and work from offer scope, charging unit and scenario assumptions. The relevant unit is a defined customer segment and comparable commercial offer. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

A price is meaningful only with its package, quantity, terms and serving requirements. Test whether buyers can predict the bill and whether the charging unit supports useful adoption. Keep willingness-to-pay statements separate from observed purchasing behavior.

Two situations that can change the interpretation

When buyers cannot predict the pricing unit

A contact-based plan needs a clear definition of which contacts count rather than relying on a familiar-sounding label.

Use this check: Ask a suitable buyer to estimate an ordinary and high-usage invoice from the page. Do not imply that a public example covers every contract or usage case.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When the pricing model ignores assisted delivery

A product that needs repeated specialist intervention may have different economics from a self-serve offer at the same advertised price.

Use this check: Estimate the actual support, implementation and maintenance effort for comparable cohorts. Do not treat every employee hour as removable cash cost.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

An account may object to price because the required integration or implementation support is unclear. Discounting without resolving that concern can create a lower-priced failure. Compare the complete offer and the customer’s actual alternatives before treating every objection as a request for a concession.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.

A reproducible sensitivity exercise

The usage based pricing simulator tool provides a related numerical exercise. Its current default inputs are constructed examples, not industry observations. Under those defaults, the output labelled Monthly bill per account is 149 in the tool’s displayed units. The table changes one input at a time and leaves the others at their defaults.

The alternative inputs are sensitivity cases, not recommended targets. A result marked not defined means the proposed combination does not satisfy the model or produces an undefined ratio. Keep that state visible. If the output changes sharply after a small input change, investigate the uncertain input before using the model to justify a larger commitment.

Compare the model’s scope with the concept on this page. The calculator may represent one particular application rather than every use of the term. Record the reporting period, currency where relevant, and the source of the real values you enter.