[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JRK0YRTE4337R4DQ01P2Z":3,"skill-same:01M71JRK0YRTE4337R4DQ01P2Z":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M71JRK0YRTE4337R4DQ01P2Z","pricing-strategy",null,"Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"pricing","strategy","pricing strategy","expansion","manager","pricing page","marketing","2026","revenue","customer","product","optimize","structure","conversion","when","design","pricing model","good","packaging","model","2026-11-10 10:12:30",false,"---\nname: \"pricing-strategy\"\ndescription: \"Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Pricing Strategy\n\nYou are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.\n\nPricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing.\n\nGather this context:\n\n### 1. Current State\n- Do you have pricing today? If so: what plans, what price points, what's the billing model?\n- What's your conversion rate from trial\u002Ffree to paid? (If known)\n- What's your average revenue per customer?\n- What's your monthly churn rate?\n\n### 2. Business Context\n- Product type: B2B or B2C? Self-serve or sales-assisted?\n- Customer segments: who are your best customers vs. casual users?\n- Competitors: who do customers compare you to, and what do those cost?\n- Cost structure: what does serving one customer cost you per month?\n\n### 3. Goals\n- Are you designing, optimizing, or planning a price increase?\n- Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)\n\n## How This Skill Works\n\n### Mode 1: Design Pricing From Scratch\nStarting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.\n\n### Mode 2: Optimize Existing Pricing\nPricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.\n\n### Mode 3: Plan a Price Increase\nPrices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.\n\n---\n\n## The Three Pricing Axes\n\nEvery pricing decision lives across three axes. Get all three right.\n\n```\n         ┌─────────────────┐\n         │   PACKAGING     │  What's in each tier?\n         │  (what you get) │\n         └────────┬────────┘\n                  │\n         ┌────────┴────────┐\n         │  VALUE METRIC   │  What do you charge for?\n         │ (how it scales) │\n         └────────┬────────┘\n                  │\n         ┌────────┴────────┐\n         │  PRICE POINT    │  How much?\n         │    (the number) │\n         └─────────────────┘\n```\n\nMost teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.\n\n---\n\n## Value Metric Selection\n\nYour value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.\n\n### Common Value Metrics for SaaS\n\n| Metric | Best For | Example |\n|--------|---------|---------|\n| **Per seat \u002F user** | Collaboration tools, CRMs | Salesforce, Notion, Linear |\n| **Per usage** | API tools, infrastructure, AI | Stripe, Twilio, OpenAI |\n| **Per feature** | Platform plays, add-ons | Intercom, HubSpot |\n| **Flat fee** | Unlimited-feel, SMB tools | Basecamp, Calendly Basic |\n| **Per outcome** | High-value, measurable ROI | Commission-based tools |\n| **Hybrid** | Mix of above | Most mature SaaS |\n\n### How to Choose\n\nAnswer these questions:\n\n1. **What makes a customer willing to pay more?** → That's your value metric\n2. **Does the metric scale with their success?** → If they grow, you grow\n3. **Is it easy to understand?** → Complexity kills conversion\n4. **Is it hard to game?** → Customers shouldn't be able to work around it\n\n**Red flags:**\n- \"Per seat\" in a tool where one power user does all the work → seats don't scale with value\n- \"Flat fee\" when some customers derive 10x the value of others → you're subsidizing heavy users\n- \"Per API call\" when call count varies wildly week to week → unpredictable bills = churn\n\n---\n\n## Good-Better-Best Tier Structure\n\nThree tiers is the standard. Not because of tradition — because it anchors perception.\n\n### Tier Design Principles\n\n**Entry tier (Good):**\n- Captures the segment that will churn if priced higher\n- Limited — either by features, usage, or support\n- NOT free. Free is a separate strategy (freemium), not a tier.\n- Should cover your costs at minimum\n\n**Middle tier (Better) — your default:**\n- This is where you push most customers\n- Price: 2-3x the entry tier\n- Features: everything a growing company needs\n- Call it out visually as recommended\n\n**Top tier (Best):**\n- For high-value customers with enterprise needs\n- May be \"Contact us\" or custom pricing\n- Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts\n- If you have enterprise deals >$1k MRR, this tier exists to capture them\n\n### What Goes in Each Tier\n\n| Feature Category | Entry | Better | Best |\n|----------------|-------|--------|------|\n| Core product | ✅ (limited) | ✅ (full) | ✅ (full) |\n| Usage limits | Low | Medium | High \u002F unlimited |\n| Users\u002Fseats | 1-3 | 5-unlimited | Unlimited |\n| Integrations | Basic | Full | Full + custom |\n| Reporting | Basic | Advanced | Custom |\n| Support | Email | Priority | Dedicated CSM |\n| Admin features | — | — | SSO, audit log, SCIM |\n| SLA | — | — | ✅ |\n\nSee [references\u002Fpricing-models.md](references\u002Fpricing-models.md) for model deep dives and SaaS examples.\n\n---\n\n## Value-Based Pricing\n\nPrice between the next-best alternative and your perceived value.\n\n```\n[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]\n```\n\n**Step 1: Define the next-best alternative**\n- What would the customer do if your product didn't exist?\n- A competitor? A spreadsheet? Manual process? Hiring someone?\n- What does that cost them?\n\n**Step 2: Estimate value delivered**\n- Time saved × hourly rate of the person using it\n- Revenue generated or protected\n- Cost of error\u002Frisk avoided\n- Ask your best customers: \"What would you lose if you stopped using us tomorrow?\"\n\n**Step 3: Price in the middle**\n- A rough heuristic: price at 10-20% of documented value delivered\n- Don't price at 50% of value — customers feel they're overpaying\n- Don't price below the next-best alternative — signals you don't believe in your own product\n\n**Conversion rate as a signal:**\n- >40% trial-to-paid: likely underpriced — test a price increase\n- 15-30%: healthy for most SaaS\n- \u003C10%: pricing may be high, or trial-to-paid funnel has friction\n\n---\n\n## Pricing Research Methods\n\n### Van Westendorp Price Sensitivity Meter\n\nFour questions, asked to current customers or target segment:\n\n1. At what price would this product be so cheap you'd question its quality?\n2. At what price would this product be a bargain — great deal?\n3. At what price would this product start to feel expensive — still acceptable?\n4. At what price would this product be too expensive to consider?\n\n**Interpret the results:** Plot the four curves. The intersection of \"too cheap\" and \"too expensive\" gives your acceptable price range. The intersection of \"bargain\" and \"expensive\" gives the optimal price point.\n\n**When to use:** B2B SaaS, n≥30 respondents, existing customers or qualified prospects.\n\n### MaxDiff Analysis\n\nShow respondents sets of features\u002Fprices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.\n\n**When to use:** When deciding which features to put in which tier.\n\n### Competitor Benchmarking\n\n| Step | What to Do |\n|------|-----------|\n| 1 | List direct competitors and alternatives customers consider |\n| 2 | Record their published pricing (plan names, prices, value metrics) |\n| 3 | Note what's included at each price point |\n| 4 | Identify where your product over- and under-delivers vs. each |\n| 5 | Price relative to positioning: premium = 20-40% above market, value = at or below |\n\n**Don't just copy competitor prices** — their pricing reflects their cost structure and positioning, not yours.\n\n---\n\n## Price Increase Strategies\n\nRaising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.\n\n### Strategy Selection\n\n| Strategy | Use When | Risk |\n|---------|---------|------|\n| **New customers only** | Significant pushback expected | Low — doesn't touch existing base |\n| **Grandfather + delayed** | Loyal customer base, contract risk | Medium — existing customers feel respected |\n| **Tied to value delivery** | Clear new features\u002Fimprovement | Low — justifiable |\n| **Plan restructure** | Significant packaging change | Medium — complexity for customers |\n| **Uniform increase** | Confident in value, price is clearly below market | Medium-High |\n\n### Execution Checklist\n\n1. **Quantify the move:** Calculate new MRR at 100%, 80%, 70% retention of existing customers\n2. **Segment by risk:** Annual contracts, champions vs. detractors, usage-based at-risk accounts\n3. **Set the date:** 60-90 days notice for existing customers. 30 days minimum.\n4. **Communicate the reason:** New features, rising costs, investment in [X] — be specific\n5. **Offer a path:** Lock in current price for annual commitment, or give a 3-month window\n6. **Arm your CS team:** FAQ, talking points, approved offer authority\n7. **Monitor for 60 days:** Churn rate, downgrade rate, support ticket volume\n\n**Expected churn from a 20-30% price increase:** 5-15%. If your net revenue impact is positive, proceed.\n\n---\n\n## Pricing Page Design\n\nThe pricing page converts intent to purchase. Design it with that job in mind.\n\n### Above the Fold\n\nMust have:\n- Plan names (simple: Starter \u002F Pro \u002F Enterprise, or named after customer segment)\n- Price with billing toggle (monthly\u002Fannual — annual should show savings)\n- 3-5 bullet differentiators per plan\n- CTA button per plan\n- \"Most popular\" badge on recommended tier\n\n### Below the Fold\n\n- **Full feature comparison table** — comprehensive, scannable, uses ✅ and ❌ not walls of text\n- **FAQ section** — address the 5 objections that stop people from buying:\n  - \"Can I cancel anytime?\"\n  - \"What happens when I hit limits?\"\n  - \"Do you offer refunds?\"\n  - \"Is my data secure?\"\n  - \"What if I need to upgrade\u002Fdowngrade?\"\n- **Social proof** — logos, quotes, or case studies relevant to each tier\n- **Security badges** if B2B enterprise (SOC2, ISO 27001, GDPR)\n\n### Annual vs. Monthly Toggle\n\n- Show annual pricing by default (or highlight it) — it improves LTV\n- Show savings explicitly: \"Save 20%\" or \"2 months free\"\n- Don't hide the monthly price — hiding it builds distrust\n\nSee [references\u002Fpricing-page-playbook.md](references\u002Fpricing-page-playbook.md) for design specs and copy templates.\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Conversion rate >40% trial-to-paid** → Strong signal of underpricing. Flag: test 20-30% price increase.\n- **All customers on the middle tier** → No upsell path. Flag: enterprise tier needed or feature lock-in missing.\n- **Customer asked for features that aren't in their tier** → Expansion revenue being left on the table. Flag: feature gatekeeping review.\n- **Churn rate >5% monthly** → Before raising prices, fix churn. Price increases accelerate churners.\n- **Price hasn't changed in 2+ years** → Inflation alone justifies 10-15% increase. Flag for strategic review.\n- **Only one pricing option** → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|--------------------|-----------|\n| \"Design pricing\" | Three-tier structure with value metric, feature grid, price points, and rationale |\n| \"Audit my pricing\" | Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins |\n| \"Plan a price increase\" | Increase strategy selection, communication templates, risk model, 90-day rollout plan |\n| \"Design a pricing page\" | Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy |\n| \"Research pricing\" | Van Westendorp survey questions + MaxDiff framework for your specific product |\n| \"Model pricing scenarios\" | Run `scripts\u002Fpricing_modeler.py` with your inputs |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — recommendation before justification\n- **What + Why + How** — every recommendation has all three\n- **Actions have owners and deadlines** — no vague \"consider\"\n- **Confidence tagging** — 🟢 verified benchmark \u002F 🟡 estimated \u002F 🔴 assumed\n\n---\n\n## Related Skills\n\n- **product-strategist**: Use for product roadmap and broader monetization strategy. NOT for pricing page or price increase execution.\n- **copywriting**: Use for pricing page copy polish. NOT for pricing structure or tier design.\n- **churn-prevention**: Use when churn is the underlying issue — fix retention before raising prices.\n- **ab-test-setup**: Use to A\u002FB test price points or pricing page layouts after initial design.\n- **customer-success-manager**: Use for expansion revenue through upselling. NOT for pricing design or packaging.\n- **competitor-alternatives**: Use for competitive comparison pages that complement pricing pages.\n","# Pricing Strategy\n\nYou are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.\n\nPricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing.\n\nGather this context:\n\n### 1. Current State\n- Do you have pricing today? If so: what plans, what price points, what's the billing model?\n- What's your conversion rate from trial\u002Ffree to paid? (If known)\n- What's your average revenue per customer?\n- What's your monthly churn rate?\n\n### 2. Business Context\n- Product type: B2B or B2C? Self-serve or sales-assisted?\n- Customer segments: who are your best customers vs. casual users?\n- Competitors: who do customers compare you to, and what do those cost?\n- Cost structure: what does serving one customer cost you per month?\n\n### 3. Goals\n- Are you designing, optimizing, or planning a price increase?\n- Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)\n\n## How This Skill Works\n\n### Mode 1: Design Pricing From Scratch\nStarting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.\n\n### Mode 2: Optimize Existing Pricing\nPricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.\n\n### Mode 3: Plan a Price Increase\nPrices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.\n\n---\n\n## The Three Pricing Axes\n\nEvery pricing decision lives across three axes. Get all three right.\n\n```\n         ┌─────────────────┐\n         │   PACKAGING     │  What's in each tier?\n         │  (what you get) │\n         └────────┬────────┘\n                  │\n         ┌────────┴────────┐\n         │  VALUE METRIC   │  What do you charge for?\n         │ (how it scales) │\n         └────────┬────────┘\n                  │\n         ┌────────┴────────┐\n         │  PRICE POINT    │  How much?\n         │    (the number) │\n         └─────────────────┘\n```\n\nMost teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.\n\n---\n\n## Value Metric Selection\n\nYour value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.\n\n### Common Value Metrics for SaaS\n\n| Metric | Best For | Example |\n|--------|---------|---------|\n| **Per seat \u002F user** | Collaboration tools, CRMs | Salesforce, Notion, Linear |\n| **Per usage** | API tools, infrastructure, AI | Stripe, Twilio, OpenAI |\n| **Per feature** | Platform plays, add-ons | Intercom, HubSpot |\n| **Flat fee** | Unlimited-feel, SMB tools | Basecamp, Calendly Basic |\n| **Per outcome** | High-value, measurable ROI | Commission-based tools |\n| **Hybrid** | Mix of above | Most mature SaaS |\n\n### How to Choose\n\nAnswer these questions:\n\n1. **What makes a customer willing to pay more?** → That's your value metric\n2. **Does the metric scale with their success?** → If they grow, you grow\n3. **Is it easy to understand?** → Complexity kills conversion\n4. **Is it hard to game?** → Customers shouldn't be able to work around it\n\n**Red flags:**\n- \"Per seat\" in a tool where one power user does all the work → seats don't scale with value\n- \"Flat fee\" when some customers derive 10x the value of others → you're subsidizing heavy users\n- \"Per API call\" when call count varies wildly week to week → unpredictable bills = churn\n\n---\n\n## Good-Better-Best Tier Structure\n\nThree tiers is the standard. Not because of tradition — because it anchors perception.\n\n### Tier Design Principles\n\n**Entry tier (Good):**\n- Captures the segment that will churn if priced higher\n- Limited — either by features, usage, or support\n- NOT free. Free is a separate strategy (freemium), not a tier.\n- Should cover your costs at minimum\n\n**Middle tier (Better) — your default:**\n- This is where you push most customers\n- Price: 2-3x the entry tier\n- Features: everything a growing company needs\n- Call it out visually as recommended\n\n**Top tier (Best):**\n- For high-value customers with enterprise needs\n- May be \"Contact us\" or custom pricing\n- Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts\n- If you have enterprise deals >$1k MRR, this tier exists to capture them\n\n### What Goes in Each Tier\n\n| Feature Category | Entry | Better | Best |\n|----------------|-------|--------|------|\n| Core product | ✅ (limited) | ✅ (full) | ✅ (full) |\n| Usage limits | Low | Medium | High \u002F unlimited |\n| Users\u002Fseats | 1-3 | 5-unlimited | Unlimited |\n| Integrations | Basic | Full | Full + custom |\n| Reporting | Basic | Advanced | Custom |\n| Support | Email | Priority | Dedicated CSM |\n| Admin features | — | — | SSO, audit log, SCIM |\n| SLA | — | — | ✅ |\n\nSee [references\u002Fpricing-models.md](references\u002Fpricing-models.md) for model deep dives and SaaS examples.\n\n---\n\n## Value-Based Pricing\n\nPrice between the next-best alternative and your perceived value.\n\n```\n[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]\n```\n\n**Step 1: Define the next-best alternative**\n- What would the customer do if your product didn't exist?\n- A competitor? A spreadsheet? Manual process? Hiring someone?\n- What does that cost them?\n\n**Step 2: Estimate value delivered**\n- Time saved × hourly rate of the person using it\n- Revenue generated or protected\n- Cost of error\u002Frisk avoided\n- Ask your best customers: \"What would you lose if you stopped using us tomorrow?\"\n\n**Step 3: Price in the middle**\n- A rough heuristic: price at 10-20% of documented value delivered\n- Don't price at 50% of value — customers feel they're overpaying\n- Don't price below the next-best alternative — signals you don't believe in your own product\n\n**Conversion rate as a signal:**\n- >40% trial-to-paid: likely underpriced — test a price increase\n- 15-30%: healthy for most SaaS\n- \u003C10%: pricing may be high, or trial-to-paid funnel has friction\n\n---\n\n## Pricing Research Methods\n\n### Van Westendorp Price Sensitivity Meter\n\nFour questions, asked to current customers or target segment:\n\n1. At what price would this product be so cheap you'd question its quality?\n2. At what price would this product be a bargain — great deal?\n3. At what price would this product start to feel expensive — still acceptable?\n4. At what price would this product be too expensive to consider?\n\n**Interpret the results:** Plot the four curves. The intersection of \"too cheap\" and \"too expensive\" gives your acceptable price range. The intersection of \"bargain\" and \"expensive\" gives the optimal price point.\n\n**When to use:** B2B SaaS, n≥30 respondents, existing customers or qualified prospects.\n\n### MaxDiff Analysis\n\nShow respondents sets of features\u002Fprices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.\n\n**When to use:** When deciding which features to put in which tier.\n\n### Competitor Benchmarking\n\n| Step | What to Do |\n|------|-----------|\n| 1 | List direct competitors and alternatives customers consider |\n| 2 | Record their published pricing (plan names, prices, value metrics) |\n| 3 | Note what's included at each price point |\n| 4 | Identify where your product over- and under-delivers vs. each |\n| 5 | Price relative to positioning: premium = 20-40% above market, value = at or below |\n\n**Don't just copy competitor prices** — their pricing reflects their cost structure and positioning, not yours.\n\n---\n\n## Price Increase Strategies\n\nRaising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.\n\n### Strategy Selection\n\n| Strategy | Use When | Risk |\n|---------|---------|------|\n| **New customers only** | Significant pushback expected | Low — doesn't touch existing base |\n| **Grandfather + delayed** | Loyal customer base, contract risk | Medium — existing customers feel respected |\n| **Tied to value delivery** | Clear new features\u002Fimprovement | Low — justifiable |\n| **Plan restructure** | Significant packaging change | Medium — complexity for customers |\n| **Uniform increase** | Confident in value, price is clearly below market | Medium-High |\n\n### Execution Checklist\n\n1. **Quantify the move:** Calculate new MRR at 100%, 80%, 70% retention of existing customers\n2. **Segment by risk:** Annual contracts, champions vs. detractors, usage-based at-risk accounts\n3. **Set the date:** 60-90 days notice for existing customers. 30 days minimum.\n4. **Communicate the reason:** New features, rising costs, investment in [X] — be specific\n5. **Offer a path:** Lock in current price for annual commitment, or give a 3-month window\n6. **Arm your CS team:** FAQ, talking points, approved offer authority\n7. **Monitor for 60 days:** Churn rate, downgrade rate, support ticket volume\n\n**Expected churn from a 20-30% price increase:** 5-15%. If your net revenue impact is positive, proceed.\n\n---\n\n## Pricing Page Design\n\nThe pricing page converts intent to purchase. Design it with that job in mind.\n\n### Above the Fold\n\nMust have:\n- Plan names (simple: Starter \u002F Pro \u002F Enterprise, or named after customer segment)\n- Price with billing toggle (monthly\u002Fannual — annual should show savings)\n- 3-5 bullet differentiators per plan\n- CTA button per plan\n- \"Most popular\" badge on recommended tier\n\n### Below the Fold\n\n- **Full feature comparison table** — comprehensive, scannable, uses ✅ and ❌ not walls of text\n- **FAQ section** — address the 5 objections that stop people from buying:\n  - \"Can I cancel anytime?\"\n  - \"What happens when I hit limits?\"\n  - \"Do you offer refunds?\"\n  - \"Is my data secure?\"\n  - \"What if I need to upgrade\u002Fdowngrade?\"\n- **Social proof** — logos, quotes, or case studies relevant to each tier\n- **Security badges** if B2B enterprise (SOC2, ISO 27001, GDPR)\n\n### Annual vs. Monthly Toggle\n\n- Show annual pricing by default (or highlight it) — it improves LTV\n- Show savings explicitly: \"Save 20%\" or \"2 months free\"\n- Don't hide the monthly price — hiding it builds distrust\n\nSee [references\u002Fpricing-page-playbook.md](references\u002Fpricing-page-playbook.md) for design specs and copy templates.\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Conversion rate >40% trial-to-paid** → Strong signal of underpricing. Flag: test 20-30% price increase.\n- **All customers on the middle tier** → No upsell path. Flag: enterprise tier needed or feature lock-in missing.\n- **Customer asked for features that aren't in their tier** → Expansion revenue being left on the table. Flag: feature gatekeeping review.\n- **Churn rate >5% monthly** → Before raising prices, fix churn. Price increases accelerate churners.\n- **Price hasn't changed in 2+ years** → Inflation alone justifies 10-15% increase. Flag for strategic review.\n- **Only one pricing option** → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|--------------------|-----------|\n| \"Design pricing\" | Three-tier structure with value metric, feature grid, price points, and rationale |\n| \"Audit my pricing\" | Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins |\n| \"Plan a price increase\" | Increase strategy selection, communication templates, risk model, 90-day rollout plan |\n| \"Design a pricing page\" | Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy |\n| \"Research pricing\" | Van Westendorp survey questions + MaxDiff framework for your specific product |\n| \"Model pricing scenarios\" | Run `scripts\u002Fpricing_modeler.py` with your inputs |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — recommendation before justification\n- **What + Why + How** — every recommendation has all three\n- **Actions have owners and deadlines** — no vague \"consider\"\n- **Confidence tagging** — 🟢 verified benchmark \u002F 🟡 estimated \u002F 🔴 assumed\n\n---\n\n## Related Skills\n\n- **product-strategist**: Use for product roadmap and broader monetization strategy. NOT for pricing page or price increase execution.\n- **copywriting**: Use for pricing page copy polish. NOT for pricing structure or tier design.\n- **churn-prevention**: Use when churn is the underlying issue — fix retention before raising prices.\n- **ab-test-setup**: Use to A\u002FB test price points or pricing page layouts after initial design.\n- **customer-success-manager**: Use for expansion revenue through upselling. NOT for pricing design or packaging.\n- **competitor-alternatives**: Use for competitive comparison pages that complement pricing pages.\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"updated":51,"version":52,"category":30},"Alireza Rezvani",1772755200000,"1.0.0","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill pricing-strategy",{"tool":68,"command":69},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill pricing-strategy",{"tool":71,"command":72},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill pricing-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002FSKILL.md",true,[76,82,86,90],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"_AIWF_IMPORT.json","REFERENCE","参考文档",346,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002F_AIWF_IMPORT.json",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fpricing-models.md",7885,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002Freferences\u002Fpricing-models.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fpricing-page-playbook.md",7834,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002Freferences\u002Fpricing-page-playbook.md",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fpricing_modeler.py","SCRIPT","脚本",11458,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fpricing-strategy\u002Fscripts\u002Fpricing_modeler.py",[97,127,150,172,192,215],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":126},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[107,108,109,110,111,112,113,114,115,116,117,118,119,120,38,121,122,123,124,125],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":126},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[133],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[107,135,136,111,137,138,139,140,120,141,38,142,121,143,144,145,146,147,148,149],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":126},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[156],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[107,158,159,111,160,140,161,38,162,142,121,163,164,165,166,167,168,169,170,171],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":179,"publishedAt":126},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[178],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[180,111,181,168,182,183,184,185,171,186,187,188,38,189,142,121,190,191,122,107],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":201,"publishedAt":126},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[198],{"categoryNo":199,"categoryName":200,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[202,203,204,205,160,206,207,208,149,169,140,209,210,161,211,188,212,213,214,38],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":238},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[221],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},[223,224,225,226,227,117,228,185,229,120,230,231,38,107,232,233,234,235,236,237],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]