.claude/skills/pricing-strategy/SKILL.md
Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.
npx skillsauth add omeragaakbas/zoyare pricing-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design a pricing strategy grounded in value delivery, competitive positioning, and willingness to pay.
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.
Understand the value delivered:
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:
Design the pricing structure:
Estimate price sensitivity:
Plan pricing experiments:
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.
development
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
data-ai
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
development
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
documentation
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.