From superpowers
Builds pricing strategies for products/services: reads FOUNDER_CONTEXT.md for business details, asks targeted questions on model, audience, competitors, margins, and goals.
npx claudepluginhub lunartech-x/superpowers --plugin superpowersThis skill uses the workspace's default tool permissions.
Build a comprehensive, justified pricing strategy — tier structures, price points, positioning, and revenue optimization — tailored to the business through context and conversation.
Builds pricing strategies for products/services: reads FOUNDER_CONTEXT.md for business details, asks targeted questions on model, audience, competitors, margins, and goals.
Provides pricing strategy guidance for startups and SaaS: models (freemium, tiers, usage-based), psychology, experimentation, value capture. Activates on pricing/monetization mentions.
Structures pricing strategies, packaging options, tiers, and pricing pages for SaaS/digital products. Use for reviews, freemium evaluation, tier design, or pricing changes.
Share bugs, ideas, or general feedback.
Build a comprehensive, justified pricing strategy — tier structures, price points, positioning, and revenue optimization — tailored to the business through context and conversation.
Check $ARGUMENTS first to determine execution mode:
Respond with: "pricing-strategist loaded, ready to build your pricing strategy"
Then wait for the user to provide context in the next message.
Proceed immediately to Task Execution (skip the "loaded" message).
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, read FOUNDER_CONTEXT.md from the project root. Extract everything relevant to pricing:
DO NOT PROCEED to Step 2 until this file has been read.
Cross-reference what FOUNDER_CONTEXT.md already provides against the Question Bank below. Only ask questions where the answer is genuinely missing or unclear. Never ask something the context already answers.
Question Bank (priority order):
| # | Question | Why it matters | Skip if... |
|---|---|---|---|
| 1 | B2B or B2C? | Changes deal size, tier logic, sales cycle, everything | Target audience section makes it obvious |
| 2 | What pricing model do you prefer or want to avoid? (subscription, one-time, usage-based, freemium, hybrid) | Determines the entire structure | Pricing model already stated in context |
| 3 | What's the primary value metric that scales with usage? (seats, API calls, storage, projects, transactions, etc.) | Drives tier differentiation and upgrade logic | Product type + features make it obvious |
| 4 | Target gross margin range? (60-70%, 70-80%, 80%+, not sure) | Sets the floor for every price point | A number or range is already given |
| 5 | How price-sensitive is your target customer? (very sensitive, moderate, willing to pay premium) | Calibrates price positioning and tier gaps | Audience detail + industry norms make it clear |
| 6 | Who are your closest competitors and how do they price? | Market anchoring — prevents under or over pricing | Competitors section is filled |
| 7 | What's your current stage or revenue target? (pre-revenue, <$10K MRR, $10-50K MRR, $50K+ MRR) | Calibrates ambition and tier complexity | Business goals mention revenue or stage |
Use AskUserQuestion to ask up to 4 questions per batch. Ask the highest-priority unanswered questions first. If the first batch gives you enough to build a confident strategy, stop. Maximum 7 questions total, but fewer is better — stop as soon as you can build a strong strategy with what you have.
Based on all collected inputs, decide the structure. Make this decision yourself — do not ask the user. Explain why in the output.
| Condition | Strategy Type |
|---|---|
| Subscription + B2B | SaaS Tiered — Starter / Pro / Business / Enterprise |
| Subscription + B2C | Consumer Tiered — Free / Basic / Premium |
| Usage-based primary | Usage Tiers — base fee + usage bands with overage pricing |
| One-time purchase | Package Pricing — Good / Better / Best bundles |
| Freemium preferred | Freemium — generous free tier + 2-3 paid tiers |
| Mixed signals | Hybrid — combine structures as the inputs warrant |
For each tier, define:
Beyond the tiers:
Hard constraints. These exist because bad pricing destroys margins or kills growth.
## Pricing Strategy for [Company Name]
**Strategy type:** [SaaS Tiered / Consumer Tiered / Usage Tiers / Package / Freemium / Hybrid]
**Why this structure:** [2-3 sentences. Why this model, not another.]
---
### [Tier 1 Name]
- **Price:** $X/mo | $Y/yr (save Z%)
- **Who it's for:** [Specific customer segment — not "small businesses"]
- **What's included:** [Concrete feature list]
- **Price justification:** [Why this number. Anchored to what.]
### [Tier 2 Name]
- **Price:** $X/mo | $Y/yr (save Z%)
- **Who it's for:** [Specific segment]
- **What's included:** [Feature list — highlight what's new vs. Tier 1]
- **Price justification:** [Why this number]
### [Tier 3 Name]
[same structure]
---
### Positioning & Psychology
- **Market position:** [Where you sit vs. named competitors]
- **Psychological tactics:** [List each one used and the specific reason]
- **Upgrade triggers:** [What moves customers between tiers — specific, behavioral]
### Revenue Optimization
- [Specific recommendation 1]
- [Specific recommendation 2]
- [Specific recommendation 3]
### Biggest Pricing Risk
[One specific risk for this business. Not generic. How to see it coming and what to do.]
If ANY check fails → revise before presenting.
Use these unless the user overrides:
Document any assumptions made in the output.