Credits and Honest Metering: How Usage-Based Pricing Should Work

The Core Problem with Opaque Usage Pricing

Most SaaS platforms claim usage-based pricing but obscure the actual unit cost. A customer may see 'pay per API call' but the invoice includes overage multipliers, seat minimums, feature tiers, and monthly minimums that disconnect the stated price from the actual bill.

Honest metering requires three non-negotiable elements: (1) a single, published unit cost (e.g., $0.001 per API call), (2) real-time usage visibility (customer sees current month spend before billing), and (3) no retroactive rate changes mid-cycle.

The trust cost of opacity is measurable. Customers who cannot predict monthly spend within 5% will either avoid the product or spend engineering time building usage caps and alerts instead of using the core product.

Defining the Credit System

A credit system converts consumption into a single accounting unit. One credit = one unit of work (one API call, one email sent, one GB stored). The credit-to-dollar ratio must be fixed and published.

Example: 1 credit = $0.01. A customer with a $100/month plan receives 10,000 credits. If they use 8,000 credits, they have 2,000 remaining. Overage is charged at the same $0.01 per credit.

The system fails if credits have variable exchange rates, expire, or carry hidden fees. Expiration dates on credits are a red flag - they convert a usage product into a subscription trap.

Published credit cost: $0.01 per credit (example). No tiers, no multipliers.
Monthly reset: Credits reset on the same day each month. Unused credits do not roll over.
Overage pricing: Same per-credit rate as base plan. No 1.5x or 2x multipliers.
Real-time counter: Customer dashboard shows current month usage and remaining credits before billing.

Transparency Checklist for Honest Metering

Transparency is operational, not marketing. The following must be documented and auditable:

Unit definition: What counts as one unit? (One API call? One request? One transaction?) Define edge cases (failed requests, retries, timeouts).
Measurement method: How is usage counted? (Server-side logs, client-side reporting, third-party meter?) Specify the source of truth.
Billing frequency: Monthly, daily, or real-time? State the cutoff time and timezone.
Invoice granularity: Can the customer download a line-item report showing usage by day, endpoint, or feature?
Audit rights: Can the customer request a usage audit? Within what timeframe?
Rate changes: Any price increase requires 30 days written notice. Existing usage in the current month is grandfathered at the old rate.

Overage Pricing: The Honest Model

Overage should never be punitive. The most honest model charges the same per-unit rate for usage above the plan limit as below it.

Example: A $100/month plan includes 10,000 API calls at $0.01 per call. If the customer makes 12,000 calls, they pay $100 + (2,000 × $0.01) = $120. No multiplier, no surprise.

Tiered overage (e.g., 1.5x the base rate above 150% usage) is dishonest because it punishes growth and creates perverse incentives to stay under thresholds rather than use the product.

Flat overage rate: Same $/unit above plan limit as within it.
Soft cap vs. hard cap: Soft cap allows overage and charges for it. Hard cap cuts off usage. Disclose which model applies.
Overage visibility: Show overage charges in real time, not as a surprise on the invoice.

Real-Time Usage Reporting

Honest metering requires customers to see their usage before the bill arrives. A dashboard that updates hourly (or better, in real time) is the baseline.

The dashboard must show: (1) current month usage to date, (2) projected month-end usage (if trend continues), (3) remaining credits or budget, and (4) a 90-day usage history.

Customers should be able to export raw usage logs (CSV or JSON) for audit and reconciliation. If a customer disputes a charge, the logs are the source of truth.

Update frequency: Hourly minimum. Real-time is better.
Projection: Show 'if usage continues at this rate, you will use X credits by month-end.'
Alerts: Allow customers to set usage thresholds (e.g., alert at 80% of budget).
Export: Provide raw usage data in machine-readable format for at least 12 months.

Detecting Dishonest Metering

Red flags that indicate a metering system is not honest:

Hidden minimums: 'Pay per API call' but there is a $50/month minimum that is not mentioned in the pricing page.
Retroactive rate changes: The per-unit cost changes mid-month or without 30 days notice.
Opaque multipliers: Overage costs 1.5x or 2x the base rate, or the multiplier is buried in the terms.
Expiring credits: Credits issued in month 1 expire in month 2 if unused. This is a subscription trap.
Bundled pricing: Usage is bundled with features, seats, or support tiers, making the per-unit cost impossible to calculate.
Delayed reporting: Usage is reported weekly or monthly instead of in real time.
No audit rights: The customer cannot request a usage report or dispute a charge with supporting data.

Honest Metering in Practice

A DTC brand using an email service provider with honest metering knows that each email costs $0.001. If they send 100,000 emails in a month, the bill is $100. No surprises, no multipliers, no minimum spend.

The provider publishes the unit cost on the pricing page. The customer's dashboard shows emails sent today, this week, and this month. The customer can download a CSV of all sends for the past year.

If the customer disputes a charge, the provider can produce server logs showing the exact send time, recipient, and status of each email. The customer can audit the logs themselves.

This model works because trust is the product. A customer who knows their costs will scale usage without fear. A customer who fears surprise bills will leave or cap usage artificially.

Questions

FAQ

Is honest metering the same as pay-as-you-go?

No. Pay-as-you-go is a billing model (you pay only for what you use). Honest metering is a transparency standard (you know exactly what you are paying for and can audit it). A product can have a flat monthly fee and still practice honest metering if it discloses what that fee covers and how overages are charged.

What if my product has variable costs that don't map cleanly to usage?

Honest metering requires a measurable unit. If your cost structure is truly opaque (e.g., infrastructure scales non-linearly), disclose that. Publish the unit cost you have settled on, explain the reasoning, and commit to not changing it mid-cycle. Transparency about constraints is better than false precision.

Can I use credits as a marketing tool (e.g., free credits for new customers)?

Yes, but disclose the terms clearly. 'New customers receive 10,000 free credits (worth $100) in month 1' is honest. 'New customers receive 10,000 credits that expire after 30 days' is a trap. Free credits are fine; expiring credits are not.

How do I handle usage spikes or abuse?

Honest metering does not require you to allow unlimited usage. You can set hard caps, require approval for usage above a threshold, or charge at the published rate and then contact the customer if usage is anomalous. The key is that the rate is the same for all customers and does not change retroactively.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo