pricing-strategy▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Design a pricing strategy grounded in value delivery, competitive positioning, and willingness to pay.
Pricing Strategy
Design a pricing strategy grounded in value delivery, competitive positioning, and willingness to pay.
Context
You are developing a pricing strategy for $ARGUMENTS.
If the user provides files (competitor pricing, survey data, financial models, or usage data), read them first. Use web search to research competitor pricing if needed.
Instructions
-
Understand the value delivered:
- What is the core value proposition?
- What is the customer's alternative (and its cost)?
- What quantifiable outcomes does the product deliver? (time saved, revenue gained, cost reduced)
- What is the customer's willingness to pay based on that value?
-
Evaluate pricing models — recommend the best fit:
Model Best For Example Flat-rate Simple products, predictable costs Basecamp ($99/mo flat) Per-seat Collaboration tools, team products Slack, Figma Usage-based Infrastructure, API products AWS, Twilio Tiered Products with distinct user segments Most SaaS (Free/Pro/Enterprise) Freemium Products with viral/network effects Spotify, Notion Freemium + usage Platform products Vercel, OpenAI API Value-based High-impact enterprise tools Salesforce, Palantir -
Analyze competitive pricing:
- Map competitor pricing tiers and what's included
- Identify where your product sits (premium, mid-market, budget)
- Find pricing gaps or opportunities
- Note any industry pricing conventions
-
Design the pricing structure:
- Tiers: Define 2-4 tiers with clear differentiation
- Feature gating: Which features go in which tier? (Use value metrics, not arbitrary limits)
- Value metric: What unit do you charge on? (users, events, storage, API calls)
- Anchor pricing: Set the most popular tier to feel like the obvious choice
- Annual discount: Typically 15-20% off monthly pricing
-
Estimate price sensitivity:
- Van Westendorp Price Sensitivity Meter (if survey data available):
- Too cheap → quality concerns
- Cheap → good value
- Expensive → starting to hesitate
- Too expensive → won't buy
- Alternatively, estimate based on competitor pricing and value delivered
- Van Westendorp Price Sensitivity Meter (if survey data available):
-
Plan pricing experiments:
- A/B test pricing pages (different price points, tier names, feature bundles)
- Founder-led sales conversations to test willingness to pay
- Landing page tests with different price anchors
- Cohort analysis of conversion rates by price point
-
Output a pricing recommendation:
Recommended Model: [Model type] Value Metric: [What you charge on] | Tier | Price | Target Segment | Key Features | Positioning | |---|---|---|---|---| Key Assumptions: - [Assumption] → [How to test] Risks: - [Risk] → [Mitigation]
Think step by step. Save as markdown. Flag any assumptions that need validation before launch.
Further Reading
How to use pricing-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add pricing-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches pricing-strategy from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate pricing-strategy. Access the skill through slash commands (e.g., /pricing-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★55 reviews- ★★★★★Naina Torres· Dec 28, 2024
pricing-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yuki Khanna· Dec 8, 2024
Keeps context tight: pricing-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Camila Mehta· Dec 4, 2024
Registry listing for pricing-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yuki White· Dec 4, 2024
pricing-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yuki Jackson· Nov 27, 2024
pricing-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yusuf Malhotra· Nov 23, 2024
Solid pick for teams standardizing on skills: pricing-strategy is focused, and the summary matches what you get after install.
- ★★★★★Yuki Srinivasan· Nov 23, 2024
Keeps context tight: pricing-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Brown· Oct 18, 2024
Useful defaults in pricing-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kiara Li· Oct 18, 2024
Solid pick for teams standardizing on skills: pricing-strategy is focused, and the summary matches what you get after install.
- ★★★★★Kiara Wang· Oct 14, 2024
We added pricing-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 55