From pricing-monetization
Plan a price change as a migration, not an edit — grandfathering, cohort sequencing, renewal-timing, comms, and the guardrail metrics (GRR, contraction, leakage, win-rate) to watch. Reach for this when raising prices, repackaging, migrating models (e.g. seat to usage), or simplifying a price card. Pairs with packaging-and-tiering and the price-change-rollout-plan template.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pricing-monetization:price-change-rolloutThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A price change is a migration of an installed base, not an edit to a price card. The
A price change is a migration of an installed base, not an edit to a price card. The new number is the easy part; grandfathering, sequencing, timing, and comms are the deliverable. A new price card with no migration plan is half an answer.
Never migrate everyone at once. Sequence by cohort and renewal date so you can read the churn/contraction/leakage signal on the first cohort before you've committed the whole base.
Which change is this?
Decide who stays on the old price, for how long. A price increase that hits the loyal base first is how you manufacture churn. Common: existing customers grandfathered for a defined window (e.g. 12 months or until a major renewal), new customers on the new price immediately.
Watch on the changed cohort (definitions in ../../knowledge/monetization-metrics.md):
Have the concession ladder ready (what you'll offer a churning key account) and the rollback trigger defined. A change with no exit plan is a bet, not a plan.
A price-change migration plan using ../../templates/price-change-rollout-plan.md:
goal, grandfathering policy, cohort sequence + go/no-go, comms plan, guardrail metrics
finance.npx claudepluginhub mcorbett51090/ravenclaude --plugin pricing-monetizationGuides 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.