Skip to main content

Methodology

Seat-based vs Usage-based Pricing Planner methodology

Compare seat-based and usage-based revenue and contribution on one shared service-cost scenario.
Duc Nguyen X.By Duc Nguyen X.· Founder, Margin101Last reviewed: View update historyMethodology

Educational only: Business decision support, not accounting, tax or legal advice.

Privacy: Calculations run locally; Margin101 does not receive your commercial inputs.

Update policy: Reviewed when formulas or official dependencies change.

Scope: Market-neutral small-business planning using your own assumptions.

1. Formulas and units

Seat-based revenue
seatRevenue = accounts × seats per account × price per seat

Where

accounts
Accounts (whole or operational units)Source: Business record
seatsPerAccount
Seats per account (whole or operational units)Source: User assumption
seatPrice
Price per seat (currency units on one consistent basis)Source: User decision
seatRevenue
Seat-based revenue (money)Source: Calculated output
Usage-based revenue
usageRevenue = accounts × max(0, usage per account − included usage) × usage price

Where

accounts
Accounts (whole or operational units)Source: Business record
usagePerAccount
Usage per account (whole or operational units)Source: User assumption
usageUnitPrice
Price per billable usage unit (currency units on one consistent basis)Source: User decision
includedUsage
Included usage per account (whole or operational units)Source: User decision
usageRevenue
Usage-based revenue (money)Source: Calculated output
Shared service cost
serviceCost = accounts × (usage per account × variable unit cost + support cost)

Where

accounts
Accounts (whole or operational units)Source: Business record
usagePerAccount
Usage per account (whole or operational units)Source: User assumption
variableCostPerUsageUnit
Variable cost per usage unit (currency units on one consistent basis)Source: Business record
supportCostPerAccount
Support cost per account (currency units on one consistent basis)Source: Business record
serviceCost
Shared service cost (money)Source: Calculated output
Seat-based contribution
seatContribution = seat-based revenue − shared service cost

Where

seatRevenue
Seat-based revenue (money)Source: Calculated output
serviceCost
Shared service cost (money)Source: Calculated output
seatContribution
Seat-based contribution (money)Source: Calculated output
Usage-based contribution
usageContribution = usage-based revenue − shared service cost

Where

usageRevenue
Usage-based revenue (money)Source: Calculated output
serviceCost
Shared service cost (money)Source: Calculated output
usageContribution
Usage-based contribution (money)Source: Calculated output
Usage contribution difference
contributionDifference = usage-based contribution − seat-based contribution

Where

seatContribution
Seat-based contribution (money)Source: Calculated output
usageContribution
Usage-based contribution (money)Source: Calculated output
contributionDifference
Usage contribution difference (money)Source: Calculated output

Money inputs and outputs use the currency selected in the scenario without changing the canonical methodology. Rates, margins, utilisation and buffers are entered as percentages and converted to decimal values for calculation.

2. Worked example

Input assumptions

Worked values below come from the same registered engine and visible default assumptions.

Calculation and outputs

Example

Worked values below come from the same registered engine and visible default assumptions.

Seat-based revenue
1,000.00 currency units
Usage-based revenue
1,600.00 currency units
Shared service cost
600.00 currency units
Seat-based contribution
400.00 currency units
Usage-based contribution
1,000.00 currency units
Usage contribution difference
600.00 currency units

The exact engine-derived outputs are shown in the labelled rows below.

Interpretation

Use the contribution difference to compare pricing mechanics on a shared service-cost scenario; it does not forecast customer preference or usage.

3. Validation and boundary checks

  • Accounts must be a finite non-negative whole number and all other assumptions must be finite and non-negative.
  • Billable usage floors at zero after included usage.
  • Both pricing models subtract the exact same service-cost result.
  • Contribution difference reconciles usage contribution less seat contribution.

4. Assumptions and source classification

  • Seat and usage scenarios share the same account population, usage, service-cost and period basis.
  • Usage, included units and seats are user-entered scenarios rather than forecasts.

This planner has no current policy-data dependency. Its commercial assumptions are user supplied. Registered family-level regression suites exercise the shared business-logic engine and worked-result reconciliation.

5. Limitations

  • The comparison does not forecast demand, account growth, usage or customer preference.
  • It does not replace financial, accounting, tax or legal advice.

This is educational decision support, not tax, accounting, legal or financial advice. Check the treatment of your actual transactions under the rules that apply to your business and seek qualified advice where appropriate.

6. Update and evidence policy

Registered family-level suites test formula invariants and example reconciliation; the release ledger records that coverage without claiming a separate oracle for every line of public copy. There is no official threshold or benchmark to refresh for this planner. Commercial inputs remain user-supplied because they vary by business and contract.

Change history

  1. : Initial public release of the Seat-based vs Usage-based Pricing planner and methodology.

Related reading

Guides to interpret the decision and its assumptions.

Return to the planner