Menu

Individual skill

usage-based-pricing-model

0upvotes

Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill shock. Use when asked to design usage-based or metered pricing, move from seats to consumption, price an API or AI product per unit, or handle customers afraid of variable bills. Produces the value-metric selection, the tier structure with included volumes and overage rates, the bill-shock guardrails, revenue modelling at usage percentiles, and the migration plan from the current model.

skills/usage-based-pricing-model/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Usage-Based Pricing Model

Usage pricing done right means revenue grows when the customer's value grows. Done wrong it means a customer opens an invoice ten times last month's, screenshots it, and churns publicly. The difference is rarely the rate — it is whether the metric tracks value the customer recognises, and whether the guardrails make the worst-case bill survivable. This designs both, and models the revenue before you commit.

## What This Skill Produces

- **The value-metric decision** — the unit you charge for, tested against the four criteria that separate a good meter from a resented one
- **The tier structure** — included volumes, overage rates, and the flat platform fee that stabilises revenue
- **Bill-shock guardrails** — caps, alerts, forgiveness policies, and the commit-and-drawdown option for predictability-hungry buyers
- **Revenue modelling** — projected revenue at the P10/P50/P90 of the actual usage distribution, not at the average
- **The degenerate-case check** — who wins and who loses at the extremes of the usage curve, before a customer finds out for you
- **A migration plan** — how existing customers move from the current model without a revolt

## Required Inputs
Back to top