Usage Billing Unit Explanation Card
Define the customer-visible unit behind a usage-based offer, including counted events, exclusions, reporting delay and a reproducible example.
Read this resource as Markdown
When to use this template
Use this when an existing usage-based software offer needs a plain explanation of what counts toward its bill. Obtain the actual metering rules rather than turning a vague feature label into a charge unit.
Choose another approach when: You need to choose a billing platform, plan to bill an undefined activity, or want to represent a provisional usage display as a final invoice.
Gather these inputs
- The actual commercial unit, implemented meter definition and billing-owner confirmation.
- Counted and excluded event examples, reporting delay and period boundaries.
- The current rate/allowance rules and a safe reproducible sample without customer data.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
Fictional example: an app defines one unit as a successfully completed document export. A controlled trace contains seven completed exports, two failures and a repeated notification for an already counted export. Under this explicitly fictional verified rule, the result is seven units, not ten. At an illustrative USD0.20 per unit with no included allowance, that trace has a USD1.40 base usage amount before any other charges. These are invented teaching inputs, not observed customer activity or a real offer. The public explanation must also state the actual display freshness. Stripe documents asynchronous summaries for its existing Billing Meters path; that behavior cannot be assumed for every provider or a different integration.
How to use it
- Map the public unit to the real event and resolve counting exclusions with the billing owner.
- Reproduce a controlled trace including a duplicate and a failed activity.
- Explain period boundaries, display freshness and the distinction from a finalized charge.
Check before using it
- The marketing unit and the implemented billing unit refer to the same activity.
- Retry and failure treatment comes from evidence rather than a convenient assumption.
- A provider-specific reporting delay is not applied universally.
What to measure
Track disputes caused by undefined units, inconsistent counts or stale displays. Reconcile controlled examples with actual configured behavior before publication. This explanation neither selects a provider nor certifies invoice correctness for real customers.
Research and sources
Stripe distinguishes usage-based charging and documents asynchronous event summaries for its existing Billing Meters path. The event-rule card and arithmetic trace are original illustrative tools; current guidance for new integrations is not replaced with legacy implementation advice.
- Stripe: Recurring pricing models — checked 2026-10-24. Products, prices, currency, service interval and broad pricing-model distinctions. No invented public Crany plan or price.
- Stripe: Record usage for billing — checked 2026-10-24. Existing Billing Meters event summaries process asynchronously. Current documentation directs new integrations to Metronome; no legacy-path recommendation or implementation is made.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.