Reprice to de-risk your revenue
Per-seat pricing bets your revenue on your customer's headcount. Reprice to capture the value you create and de-risk the base.
Reprice to de-risk your revenue
Per-seat pricing bets your revenue on your customer's headcount.
Reprice to capture the value you create and de-risk the base.
A value metric
Clean tiers validated with real buyers
The positioning that frames it
A business case for the accounts it hits hardest
Contraction risk down, deal size up
Repriced off per-seat to value-based packaging: contraction risk fell and average deal size grew, the two effects this play actually modeled.
Per-seat pricing means your revenue rises and falls with your customer's headcount, not with the value you deliver. A layoff at their company becomes a contraction at yours, and you find out the pricing model was never really yours to control.
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Move off pure per-seat, decide what to meter and what to bundle, set the tiers, and model the impact on deal size and win rate before you change a thing.
Who to talk to, a non-leading interview guide, and how to turn transcripts into positioning and messaging inputs.
Turns what you do, who it's for, and why you win into one positioning statement and a full message house.
Frames the cost of the problem, the change, the value model, and the risk of doing nothing, in the buyer's own numbers.
A value metric and clean tiers validated with real buyers, the positioning that frames it, a business case for the accounts it hits hardest, and the modeled impact before you change a thing.
- All 4 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: A founder on pure per-seat pricing is watching customer layoffs contract revenue and wants to reprice without guessing.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
If your revenue moves one-for-one with your customers' seat counts, you do not have a pricing model, you have a beta on their headcount. Package around the value. It de-risks the base and, done right, it makes the deal easier to say yes to.
Dig into the full build →One plugin. 4 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 4 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.