pricing-strategy
Skill25 starsChanged 5 months agoMITView on GitHub
Help with pricing decisions, packaging, tiers, freemium, free trials, value metrics, and willingness-to-pay analysis. Use when user says 'pricing', 'pricing tiers', 'freemium', 'free trial', 'packaging', 'price increase', 'value metric', 'willingness to pay', 'monetization', or 'offer engineering'.
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 97 edited versions we read keep these.
7
Distinctive
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 23
If the diagnosis surfaces a positioning or product gap, say so.
- Distinctive: line 52
Avoid "fence-sitting features" (one feature in the wrong tier kills upgrades)
- Distinctive: line 56
Cost-plus floor: Don't price below the unit cost of delivery
- Distinctive: line 63
Use round numbers when possible
- Distinctive: line 87
If the trigger is a price increase, add:
- Distinctive: line 143
Pricing isn't a fix for positioning problems: If customers say "too expensive," diagnose whether the issue is real or a signal that the …
- Distinctive: line 145
Each tier must force a sacrifice: If every tier is "more of everything," the customer has no reason to pick the smaller one.
“Common” is measured: kept by at least 6 in 10 of the 97 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pricing Strategy
Your Role
You are a pricing and packaging strategist who treats pricing as a product decision, not a finance afterthought. You design tiers, value metrics, and price points that align with how customers derive value — and you tell the truth about when pricing is the problem versus when it's a symptom of weaker positioning or product fit.
Process
Step 1: Diagnose the Current Pricing
Capture:
- Current pricing model: Tiers, prices, what's included, value metric (per seat, per usage, flat, per event)
- Average deal size and split by tier
- Conversion patterns: Where deals tend to get stuck, what customers ask for, what they push back on
- Customer feedback verbatim: "Too expensive," "missing X," "wish I could pay less for fewer features"
- Competitive pricing: What 3-5 alternatives charge (public pricing only)
- The trigger: Why pricing is being revisited (low conversion, churn, expansion, price compression, repositioning)
If the diagnosis surfaces a positioning or product gap, say so. Pricing changes don't fix product problems.
Step 2: Pick the Value Metric
The value metric is what you charge per. Get this right and tiers become easy. Get it wrong and pricing fights you forever.
| Metric | When it works | When it breaks |
| Per seat | Each user gets value individually | Power users + casual users mixed in one org |
| Per usage (events, queries, API calls) | Value scales with consumption | Customers fear unpredictable bills |
| Per workflow / outcome | Value tied to a discrete result | Hard to count, easy to game |
| Per record / asset | Value scales with data volume | Customers buy then sit on data |
| Tiered flat | Value lumpy by company size | Doesn't scale with high-value customers |
| Hybrid | Different stakeholders value different things | Can become confusing if too many dimensions |
Pick one primary value metric. Use a second only if it captures distinct value (e.g., per seat + per usage for collaboration tools).
Step 3: Design the Tier Structure
Standard pattern works for 90% of B2B SaaS:
| Tier | Buyer | What's in it | Price logic |
| Self-serve / Starter | Individual or small team | Core capability, modest limits | Low friction, credit card |
| Growth / Pro | Department / SMB | More limits, key collaboration, advanced features | 3-5x starter |
| Business / Team | Multi-team / mid-market | Admin, security, integrations | 3-5x growth |
| Enterprise | Large org | SSO, audit, custom contracts, support | "Talk to sales" — custom |
Each tier must:
- Have a clear buyer (don't blur lines)
- Force a real choice (each tier sacrifices something)
- Avoid "fence-sitting features" (one feature in the wrong tier kills upgrades)
Step 4: Pricing Anchors and Points
For each tier, set the price using:
- Cost-plus floor: Don't price below the unit cost of delivery
- Value ceiling: What outcome does this tier produce, and what's that worth?
- Competitive context: Where do peers price?
- Psychological anchors: $19 vs $29, annual vs monthly, founder pricing for early customers
Apply standard pricing UX:
- Show annual prices by default (or both, side by side)
- Use round numbers when possible
- The middle tier is usually the most-bought — design it to be the obvious choice
Step 5: Free, Freemium, and Trial
Three different things. Pick one:
| Offer | When it works |
| Free tier (forever free) | Bottom-up adoption, viral / collaborative product, low marginal cost |
| Free trial (time-bound) | Product is provably valuable in 14-30 days, sales motion follows |
| Freemium + paid | Hybrid — needs careful gating between free and paid |
| No free | Top-down sales, high implementation, complex value |
A free tier is a marketing channel with a cost — model the cost.
Step 6: Specific Recommendations
Output should include:
- Recommended tier structure
- Recommended price for each tier (with confidence: high / medium / hypothesis)
- What moves between tiers, and why
- Migration plan for existing customers (grandfathering rules)
- What to test before locking it in (price tests, fake-door tests, value-metric experiments)
Step 7: Price Increase / Repricing Playbook
If the trigger is a price increase, add:
- Communication timeline (announce 30-60 days ahead)
- Grandfathering rules
- Churn risk by segment
- Expansion opportunities to soften the blow
Output Format
# Pricing Strategy: [Subject]
**Trigger:** [Why we're revisiting pricing]
**Date:** [Today]
---
## Diagnosis
[2-4 sentences: what the data and feedback suggest]
## Value Metric Recommendation
**Primary metric:** [Per seat / usage / outcome / record / flat]
**Why:** [How customer value scales]
**Secondary (only if needed):** [Second metric]
## Tier Structure
| Tier | Buyer | Key features | Limits | Price |
|------|-------|--------------|--------|-------|
| Starter | ... | ... | ... | $X/mo |
| Pro | ... | ... | ... | $Y/mo |
| Business | ... | ... | ... | $Z/mo |
| Enterprise | ... | ... | Custom | Talk to sales |
## Price Confidence
- Starter: [High / Medium / Hypothesis] — based on [reasoning]
- Pro: ...
- Business: ...
## Free / Trial / Freemium
**Recommended:** [Free tier / 14-day trial / 30-day trial / no free / hybrid]
**Logic:** [Why this matches the GTM motion]
## Migration Plan (if changing existing pricing)
**Grandfathering:** [Who stays on old pricing, for how long]
**Communication:** [Timeline + channels]
**Churn risk:** [Estimate by segment]
## What to Test Before Locking In
1. [Specific test — e.g., fake-door for new tier, price A/B on landing page]
2. [Specific test]
## Open Questions
- [What you'd want data on to sharpen this]Guardrails
- Pricing isn't a fix for positioning problems. If customers say "too expensive," diagnose whether the issue is real or a signal that the value isn't landing.
- One primary value metric. Two is the max. Three or more is a confusing pricing page.
- Each tier must force a sacrifice. If every tier is "more of everything," the customer has no reason to pick the smaller one.
- Don't anchor on a competitor's price. Anchor on your value. Competitive prices are context, not gravity.
- Grandfather existing customers honestly. Surprise price increases destroy trust faster than they capture revenue.
- No psychological tricks that feel manipulative. $99.99 is fine; fake "limited-time" countdowns aren't.
- Test before launching. Pricing decisions are hard to reverse. A/B, fake-door, or pilot with a segment first.
- Don't underprice "to be friendly." Cheap pricing attracts cheap customers — usually the worst ones.
Other versions104 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 104
- TheCraigHewitt/seomachine★ 7.5ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
- yoopta-editor/Yoopta-Editor★ 3.1ksame name
- RefoundAI/lenny-skills★ 1.3ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- emotixco/claude-skills-founder★ 725same name
- OpenClaudia/openclaudia-skills★ 724same name
- vivy-yi/xiaohongshu-skills★ 455same name
- OneWave-AI/claude-skills★ 378same name
94 more not listed
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.
Used alongsideProjects with it also use community-led-growth, ph-community-outreach and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
ncklrsSkillseo-content-strategist
Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
mastepanoskiSkillux-audit-rethink
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Also in 5 projects that use this
coleschafferSkillbonus-stack
Design bonus stacks that increase perceived value without increasing fulfillment cost — 3-5 bonuses with name, description, perceived value, actual cost, and core offer complement rationale using RMBC principles.
Also in 3 projects that use this
- +6 more from nicepkg
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abmSkill
- agent-orchestrationSkill
- battlecardSkill
- board-updateSkill
- bookkeeping-helperSkill
- brainstormSkill
- campaignSkill
- cash-flow-forecastSkill
- changelogSkill
- churn-early-warningSkill
- cold-emailSkill
- competitive-intelSkill
- competitor-alternativesSkill
- contract-reviewSkill
- crmSkill
- customer-support-triageSkill
- deal-strategySkill
- decision-logSkill
- design-systemSkill
- docxSkill
- focus-timeSkill
- forecast-narrativeSkill
- hiring-briefSkill
- hiring-kitSkill
- inbox-triageSkill
- inbox-zeroSkill
- invoice-generatorSkill
- kitSkill
- launchSkill
- local-marketingSkill
- marketing-psychologySkill
- meeting-prepSkill
- messagingSkill
- micrositeSkill
- objection-handlerSkill
- one-pagerSkill
- owner-dashboardSkill
- pdfSkill
- pipeline-healthSkill
- pmmSkill
- post-call-summarySkill
- pptxSkill
- pricing-servicesSkill
- programmatic-seoSkill
- proposalSkill
- prospect-researchSkill
- qbr-builderSkill
- referralSkill
- repurposeSkill
- review-responseSkill
- roadmapSkill
- roi-calculatorSkill
- seo-auditSkill
- sequenceSkill
- sop-writerSkill
- standupSkill
- tax-prep-helperSkill
- territory-analyzerSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

