From pricing-monetization
Choose the pricing model — subscription, per-seat, usage/consumption, tiered, flat-rate, freemium, or hybrid — by tracing the value of the product against consumption variance and acquisition needs. Reach for this when a product needs its first model, when a per-seat model is capping growth, or when an AI/usage-cost feature breaks the existing model. Pairs with value-metric-design (decide the metric alongside the model).
How this skill is triggered — by the user, by Claude, or both
Slash command
/pricing-monetization:pricing-model-selectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The pricing model is *how* the customer is charged. It is downstream of the value
The pricing model is how the customer is charged. It is downstream of the value
metric (what you charge per) — so sketch the metric (see value-metric-design)
before locking the model. This skill traces a product to its best-fit model and
names the runner-up.
Hybrid is the default answer for anything consumption-driven. A committed base fee + an included allowance + metered overage gives the vendor a revenue floor and the customer a predictable bill while still aligning price with value at the margin. Reach for a pure model only when the product is genuinely simple (flat capability, predictable use) or genuinely metered (clean per-event value).
Answer three questions:
Traverse ../../knowledge/pricing-decision-trees.md §1
to a leaf. Record the path you took.
Ask: "If this product becomes 10× more valuable to the customer, does our revenue grow with it?" If the model says no, you've picked a metric/model that caps the company — go back to Step 1.
finance.value-metric-design (do it alongside, not after).willingness-to-pay-research.A model recommendation with: the tree path, the runner-up and why it lost, the model-specific cautions that apply, and the failure-question check.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub mcorbett51090/ravenclaude --plugin pricing-monetization