/pricing
Use this skill when the user needs to set pricing, design pricing tiers, choose value metrics, build a pricing page, or test price changes. Also use when the user mentions 'how much should I charge,' 'freemium vs free trial,' 'pricing page,' or 'monetization.' Covers pricing
$ npx -y skills add whawkinsiv/claude-code-superpowers --skill pricing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pricing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill when the user needs to set pricing, design pricing tiers, choose value metrics, build a pricing page, or test price changes. Also use when the user mentions 'how much should I charge,' 'freemium vs free trial,' 'pricing page,' or 'monetization.' Covers pricing
SKILL.md
pricing.SKILL.mdname: pricing
description: "Use this skill when the user needs to set pricing, design pricing tiers, choose value metrics, build a pricing page, or test price changes. Also use when the user mentions 'how much should I charge,' 'freemium vs free trial,' 'pricing page,' or 'monetization.' Covers pricing psychology, tier design, anchoring, self-selection mechanisms, and monetization strategy for SaaS."
Pricing & Monetization
Price is a signal. Too low says "toy." Too high says "enterprise." Your price tells customers who this product is for. This skill helps you choose what to charge, how to structure tiers, and how to build a pricing page that converts.
Core Principles
- Pricing is a psychology problem, not a math problem.
- Align price with the value metric — the unit of value your customer receives.
- Three tiers is the default for a reason: anchoring, self-selection, and upgrade paths.
- The best pricing is simple to understand and hard to outgrow.
- Most SaaS companies underprice by 2-3x. Revisit pricing every 6 months.
---
Workflow
Pricing Setup:
- [ ] Choose your value metric
- [ ] Design tier structure (Free → Pro → Business)
- [ ] Set price points
- [ ] Build the pricing page
- [ ] Plan expansion revenue mechanics
---
Step 1: Choose Your Value Metric
The value metric is what you charge for. It should be:
1. **Easy to understand:** The customer can predict their bill. 2. **Aligned with value:** As they get more value, they pay more. 3. **Scalable:** It grows with their usage naturally.
| SaaS Type | Good Value Metric | |-----------|------------------| | Collaboration tools | Per seat/user | | Developer tools | API calls, compute time, builds | | Marketing tools | Contacts, emails sent, campaigns | | Analytics | Events tracked, data points, queries | | Storage/infra | GB stored, bandwidth |
**Bad value metrics:** Features-only gating (bloated top tiers), flat pricing (no expansion revenue), complex formulas nobody can predict.
**Tell AI:**
Help me choose a value metric for my SaaS:
- Product: [what it does]
- Users: [who uses it and how]
- Core value: [what outcome users get]
- Current model: [if any — flat rate, per user, etc.]
Recommend a value metric that's easy for users to understand, scales with the value
they receive, and creates natural expansion revenue. Show 2-3 options with tradeoffs.
---
Step 2: Design Tier Structure
**Free / Starter:**
- Purpose: Acquisition. Get users in the door.
- Include: Core value prop, limited quantity (not crippled features).
- Limit: 1 user, 3 projects, 1,000 events, etc.
- Avoid: Time-limited free tiers for bottom-up SaaS. Use quantity limits.
**Pro / Team:**
- Purpose: Conversion. This is your primary revenue tier.
- Include: Everything in Free + collaboration + higher limits + integrations.
- Price: $10-30/user/month for SMB, $30-80 for mid-market.
- This tier should feel like an obvious upgrade when they hit Free limits.
**Business / Scale:**
- Purpose: Expansion. Capture more value from power users.
- Include: Everything in Pro + advanced features (SSO, audit logs, API access, priority support).
- Price: 2-3x the Pro tier.
**Enterprise (optional for now):**
- Purpose: Large deals. Custom pricing = "Contact us."
- Gate: SSO, SAML, SCIM, advanced security, SLA.
**Tell AI:**
Design pricing tiers for my SaaS:
- Product: [what it does]
- Value metric: [what you're charging for — users, projects, events, etc.]
- Target customer: [SMB, mid-market, enterprise]
- Competitors charge: [list 2-3 competitor prices if known]
Create 3 tiers with:
- Tier name, price, and what's included
- Clear differentiation between tiers (not just "more of the same")
- A reason to upgrade at each level (hit a limit, need a feature)
- The specific limits for the free tier
---
Step 3: Set Price Points
Psychological Pricing Tactics
- **Anchoring:** Display the most expensive plan prominently to make mid-tier feel reasonable.
- **Decoy effect:** Make the middle tier clearly the best value relative to the others.
- **Charm pricing:** $29 vs $30 — the effect is real, especially for SMB.
- **Per-day framing:** "Less than $1/day" for higher-priced plans.
- **Loss aversion:** On trial expiry, emphasize what they'll lose, not what they'll gain.
Freemium vs. Free Trial
**Choose Freemium when:**
- Your product has viral/network effects (users invite others)
- The free tier drives organic growth or word-of-mouth
- Your marginal cost per free user is very low
- You're selling bottom-up (PLG)
**Choose Free Trial when:**
- The product's value requires setup/investment to experience
- You sell to decision-makers who evaluate then buy
- You can't afford to support large numbers of free users
**Reverse Trial (best of both):** Give FULL access for 14 days, then downgrade to free tier. Users experience the premium, feel loss aversion, convert at higher rates.
---
Industry Pricing Anchors
If you're building for your own profession, you already know what your peers pay for tools. Use this knowledge.
**Tell AI:**
Help me set pricing for my SaaS. Context about my industry:
- My target users are [profession/role]
- They currently pay for these tools: [list tools and rough prices]
- Their typical budget for software: [$ range per month, or "they expense it"]
- Buying decision made by: [individual practitioner / office manager / firm partner]
- Price sensitivity: [very price-sensitive / moderate / "if it works, cost doesn't matter"]
Based on these industry anchors, what price range makes sense?
Position my product relative to what they already pay.
**Key insight:** Your peers' existing software spending sets the anchor, not your costs. If every dentist already pays $300/month for practice management software, a $49/month add-on feels trivial. If your audience pays $0/month for tools, $29/month feels like a big ask.
---
Step 4: Build the Pricing Page
**Tell AI:**
Build a pricing page
Read more
name: pricing description: "Use this skill when the user needs to set pricing, design pricing tiers, choose value metrics, build a pricing page, or test price changes. Also use when the user mentions 'how much should I charge,' 'freemium vs free trial,' 'pricing page,' or 'monetization.' Covers pricing psychology, tier design, anchoring, self-selection mechanisms, and monetization strategy for SaaS."
Pricing & Monetization
Price is a signal. Too low says "toy." Too high says "enterprise." Your price tells customers who this product is for. This skill helps you choose what to charge, how to structure tiers, and how to build a pricing page that converts.
Core Principles
- Pricing is a psychology problem, not a math problem.
- Align price with the value metric — the unit of value your customer receives.
- Three tiers is the default for a reason: anchoring, self-selection, and upgrade paths.
- The best pricing is simple to understand and hard to outgrow.
- Most SaaS companies underprice by 2-3x. Revisit pricing every 6 months.
---
Workflow
Pricing Setup: - [ ] Choose your value metric - [ ] Design tier structure (Free → Pro → Business) - [ ] Set price points - [ ] Build the pricing page - [ ] Plan expansion revenue mechanics
---
Step 1: Choose Your Value Metric
The value metric is what you charge for. It should be:
1. **Easy to understand:** The customer can predict their bill. 2. **Aligned with value:** As they get more value, they pay more. 3. **Scalable:** It grows with their usage naturally.
| SaaS Type | Good Value Metric | |-----------|------------------| | Collaboration tools | Per seat/user | | Developer tools | API calls, compute time, builds | | Marketing tools | Contacts, emails sent, campaigns | | Analytics | Events tracked, data points, queries | | Storage/infra | GB stored, bandwidth |
**Bad value metrics:** Features-only gating (bloated top tiers), flat pricing (no expansion revenue), complex formulas nobody can predict.
**Tell AI:**
Help me choose a value metric for my SaaS: - Product: [what it does] - Users: [who uses it and how] - Core value: [what outcome users get] - Current model: [if any — flat rate, per user, etc.] Recommend a value metric that's easy for users to understand, scales with the value they receive, and creates natural expansion revenue. Show 2-3 options with tradeoffs.
---
Step 2: Design Tier Structure
**Free / Starter:**
- Purpose: Acquisition. Get users in the door.
- Include: Core value prop, limited quantity (not crippled features).
- Limit: 1 user, 3 projects, 1,000 events, etc.
- Avoid: Time-limited free tiers for bottom-up SaaS. Use quantity limits.
**Pro / Team:**
- Purpose: Conversion. This is your primary revenue tier.
- Include: Everything in Free + collaboration + higher limits + integrations.
- Price: $10-30/user/month for SMB, $30-80 for mid-market.
- This tier should feel like an obvious upgrade when they hit Free limits.
**Business / Scale:**
- Purpose: Expansion. Capture more value from power users.
- Include: Everything in Pro + advanced features (SSO, audit logs, API access, priority support).
- Price: 2-3x the Pro tier.
**Enterprise (optional for now):**
- Purpose: Large deals. Custom pricing = "Contact us."
- Gate: SSO, SAML, SCIM, advanced security, SLA.
**Tell AI:**
Design pricing tiers for my SaaS: - Product: [what it does] - Value metric: [what you're charging for — users, projects, events, etc.] - Target customer: [SMB, mid-market, enterprise] - Competitors charge: [list 2-3 competitor prices if known] Create 3 tiers with: - Tier name, price, and what's included - Clear differentiation between tiers (not just "more of the same") - A reason to upgrade at each level (hit a limit, need a feature) - The specific limits for the free tier
---
Step 3: Set Price Points
Psychological Pricing Tactics
- **Anchoring:** Display the most expensive plan prominently to make mid-tier feel reasonable.
- **Decoy effect:** Make the middle tier clearly the best value relative to the others.
- **Charm pricing:** $29 vs $30 — the effect is real, especially for SMB.
- **Per-day framing:** "Less than $1/day" for higher-priced plans.
- **Loss aversion:** On trial expiry, emphasize what they'll lose, not what they'll gain.
Freemium vs. Free Trial
**Choose Freemium when:**
- Your product has viral/network effects (users invite others)
- The free tier drives organic growth or word-of-mouth
- Your marginal cost per free user is very low
- You're selling bottom-up (PLG)
**Choose Free Trial when:**
- The product's value requires setup/investment to experience
- You sell to decision-makers who evaluate then buy
- You can't afford to support large numbers of free users
**Reverse Trial (best of both):** Give FULL access for 14 days, then downgrade to free tier. Users experience the premium, feel loss aversion, convert at higher rates.
---
Industry Pricing Anchors
If you're building for your own profession, you already know what your peers pay for tools. Use this knowledge.
**Tell AI:**
Help me set pricing for my SaaS. Context about my industry: - My target users are [profession/role] - They currently pay for these tools: [list tools and rough prices] - Their typical budget for software: [$ range per month, or "they expense it"] - Buying decision made by: [individual practitioner / office manager / firm partner] - Price sensitivity: [very price-sensitive / moderate / "if it works, cost doesn't matter"] Based on these industry anchors, what price range makes sense? Position my product relative to what they already pay.
**Key insight:** Your peers' existing software spending sets the anchor, not your costs. If every dentist already pays $300/month for practice management software, a $49/month add-on feels trivial. If your audience pays $0/month for tools, $29/month feels like a big ask.
---
Step 4: Build the Pricing Page
**Tell AI:**
Build a pricing page
43 expert skills for non-technical founders building SaaS with AI tools (Claude Code, Lovable, Replit, Cursor). Covers the full lifecycle of planning, building, launching, and growing a software business — actionable guides, checklists, and copy-paste prompts.
Other skills on solo-founder-superpowers.
- /about-me
Use this skill when the user wants to create a founder profile, establish their personal voice for content, or set up context so other skills produce personalized output instead of generic AI copy. Also use when the user says 'set up my voice,' 'create my profile,' 'who am I,'
Open skill - /accounting
Use this skill when the user needs to set up bookkeeping, track revenue and expenses, prepare for taxes, choose accounting software, understand SaaS revenue recognition, or manage the financial operations of their bootstrapped business. Covers bookkeeping setup, tax preparation,
Open skill - /ads
Use this skill when the user needs to run Google Ads, write ad copy, select keywords, optimize CAC/LTV, or manage a small paid acquisition budget. Covers Google Ads strategy, keyword selection, ad copywriting, and conversion tracking for bootstrapped SaaS.
Open skill - /ai-features
Use this skill when the user needs to add AI-powered features to their SaaS product, integrate LLM APIs, build AI assistants, implement RAG, or use AI to differentiate their product. Covers API selection, prompt engineering for product features, cost management, and building AI
Open skill - /analytics
Use this skill when the user needs to set up analytics, design event tracking, define key metrics, build funnels, or instrument their SaaS product for data-driven decisions. Covers event naming conventions, tracking strategy, funnel analytics, and data quality.
Open skill - /beautify
Use this skill when the user wants to make their app look better, says it looks like a template, asks how to achieve Stripe/Linear quality, or says something looks off. Covers visual hierarchy, whitespace, composition, color application, and typography in practice.
Open skill

