saas-pricing
Skill1 starsChanged 39 days agoMITView on GitHub
Designs a SaaS pricing model - the value metric, three-tier packaging with feature gates, list prices, annual discount, and a built-in expansion path targeting net revenue retention - delivered as a pricing page spec. Use when a founder asks "how should we price our SaaS", "per seat or usage-based", "what features go in each tier", or is building or overhauling a pricing page. Do NOT use for pricing strategy outside SaaS packaging - use pricing-strategy instead; for the upsell motion after pricing exists, use expansion-revenue.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SkillMedev/saas-growth-stackword for word, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 1
- SkillMedev/saas-growth-stack★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- competitive-intelligenceSkill
- go-to-market-plannerSkill
- landing-page-copySkill
- launch-day-runbookSkill
- launch-plan-sequencerSkill
- messaging-hierarchySkill
- plg-motion-designerSkill
- positioning-statementSkill
- press-release-writerSkill
- pricing-strategySkill
- sales-enablement-kitSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Use three tiers as the default.
- Distinctive: line 47
Add expansion seats, premium modules, and usage overages.
- Distinctive: line 54
Use round, confident numbers.
- Distinctive: line 55
Always offer annual billing at a 15-20% discount to improve cash and retention.
- Distinctive: line 60
Run the "too cheap / too expensive" Van Westendorp survey on real prospects.
- Distinctive: line 61
Check that fewer than ~20% of deals close without a single objection - if nobody balks, you are underpriced.
- Distinctive: line 63
Test price increases on new logos first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SaaS Pricing Model
Pricing is the highest-leverage growth lever and the least-tested. A 1% price improvement often beats a 1% gain in acquisition or retention. This skill designs pricing that aligns what you charge with the value you create.
Step 1: Choose the Value Metric
The value metric is the unit you charge by - seats, events, GB, transactions. A good value metric:
- Scales with the value the customer receives.
- Is easy for the customer to predict and budget.
- Grows naturally as the customer succeeds (this is your expansion engine).
Per-seat is simple but caps with headcount. Usage-based aligns with value but hurts predictability. Hybrid (platform fee + usage) is increasingly standard.
Step 2: Package into Tiers
Use three tiers as the default. The middle tier should be the one you want most customers to choose - anchor it with a deliberately under-featured low tier and a premium high tier.
- Good: removes friction for the self-serve buyer; gates the features that signal you are ready to pay.
- Better: the target. Includes the features 70% of buyers need.
- Best / Enterprise: security, SSO, SLAs, support. Price on value, often "contact us."
Gate features by buyer sophistication and willingness to pay, not by cost to build. SSO and audit logs belong in the top tier because they signal budget.
Step 3: Design Expansion
Net revenue retention above 100% is the engine of SaaS compounding. Build expansion in from the start:
- The value metric should grow with usage so good customers pay more naturally.
- Add expansion seats, premium modules, and usage overages.
- Price the first unit to land, price expansion to monetize.
Step 4: Set the Numbers
- Anchor on value delivered, not cost-plus. Estimate the dollar value the customer captures and price at 10-25% of it.
- Use round, confident numbers. Odd prices read as consumer, not B2B.
- Always offer annual billing at a 15-20% discount to improve cash and retention.
Validation
- Run the "too cheap / too expensive" Van Westendorp survey on real prospects.
- Check that fewer than ~20% of deals close without a single objection - if nobody balks, you are underpriced.
- Test price increases on new logos first; never surprise existing customers.
Anti-Patterns
- Charging by a metric the customer wants to minimize (e.g. per-API-call when they want fewer calls).
- Too many tiers - analysis paralysis kills conversion.
- Grandfathering forever; build price-increase rights into contracts.
Deliverable
Produce a pricing page spec: the value metric and its rationale, three tiers with feature gates, list prices, annual discount, and the expansion path with target net revenue retention.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

