pricing-packaging
Design or evaluate pricing and packaging strategy. Use when setting prices for a new tier, adjusting existing pricing, or restructuring packages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Design or evaluate pricing and packaging strategy. Use when setting prices for a new tier, adjusting existing pricing, or restructuring packages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build a complete business case for a product investment — strategic rationale, financial model, risk assessment, and recommendation. Use when you need executive approval for a major initiative.
Run ROI, IRR, NPV, payback period, and cost-benefit analysis for product investments. Use when you need to quantify the financial case for building something.
Decompose a large problem, epic, or initiative into independently shippable slices. Use when work is too big to build in one sprint and you need to find the seams.
Deep dive into product analytics — investigate a question, surface insights, build a data narrative. Use when you need to go beyond dashboards to understand what's happening.
Define an epic with strategic context, feature breakdown, milestones, and success metrics. Use when scoping a large body of work for planning and tracking.
Write a detailed feature spec with requirements, edge cases, and technical constraints. Use when a feature needs formal documentation before engineering begins.
| name | pricing-packaging |
| description | Design or evaluate pricing and packaging strategy. Use when setting prices for a new tier, adjusting existing pricing, or restructuring packages. |
Structure a pricing and packaging analysis in 1-2 days instead of a multi-week pricing project. Claude handles competitive research, tier modeling, and revenue scenario analysis. You handle the strategic positioning, customer conversations, and willingness-to-pay judgment.
| Step | Time | Claude Does | You Do |
|---|---|---|---|
| Define value metrics | 1-2 hrs | Analyze product usage to identify what users value most | Validate against your customer knowledge |
| Competitive landscape | 2-3 hrs | Survey competitor pricing, features, and positioning | Add context on competitors' strategies |
| Design tiers | 2-3 hrs | Model good-better-best tier structures with feature allocation | Decide strategic positioning per tier |
| Revenue modeling | 1-2 hrs | Run scenario analysis across price points | Validate assumptions, choose target |
| Design the test | 1 hr | Draft experiment brief for pricing change | Define risk tolerance and rollout plan |
A value metric is the unit your customers pay for — the thing that scales with the value they receive.
Here's our product context:
- [What the product does]
- [Current pricing model if it exists]
- [Key usage data — what features are used most, by whom, and how much]
- [Customer segments and their primary use cases]
Help me identify the right value metric(s):
- What do users do more of as they get more value?
- Which usage patterns correlate with retention and expansion?
- What metric is easy for customers to understand and predict?
- What metric aligns our revenue growth with customer success?
Evaluate: seats, usage volume, features, outcomes, or hybrid models.
For each option, flag the pros, cons, and which customer segments it favors.
Analyze the pricing landscape for [our category/competitors]:
For each competitor [list 3-5]:
- Pricing model (per seat, usage-based, flat rate, hybrid)
- Published price points and tier structure
- What's included at each tier
- Free tier or trial availability
- Enterprise/custom pricing signals
Then assess:
- Where is the market converging on pricing model?
- Are there underserved segments (priced out or overpaying)?
- What pricing moves would be expected vs. surprising?
- Where is there room to differentiate on packaging, not just price?
Based on our value metric analysis and competitive landscape, design a
good-better-best tier structure:
For each tier:
- Name and positioning (who is this for?)
- Features included (map to value realization stages)
- Price point range with rationale
- What makes someone upgrade to the next tier?
- What's explicitly excluded and why?
Constraints:
- [Your constraints — e.g., "free tier must exist", "enterprise requires SSO",
"can't exceed $X for SMB segment"]
Design principles:
- Each tier must deliver complete value for its segment (not crippled versions)
- The upgrade trigger should be natural (usage growth, team growth, feature need)
- Packaging should be easy to explain in one sentence per tier
Model revenue scenarios for the proposed tier structure:
Inputs:
- Current customer distribution: [segments, sizes, current spend]
- Assumed conversion rates between tiers: [estimates]
- Growth assumptions: [new customer acquisition rate, expansion rate]
Model three scenarios:
1. Conservative: [lower conversion, higher churn from price change]
2. Expected: [your best estimates]
3. Optimistic: [higher conversion, lower churn]
For each: project MRR impact at 3, 6, and 12 months.
Flag: which customer segments gain value, which might churn, and the net effect.
Draft an experiment brief for rolling out this pricing change:
- Who sees new pricing first (new customers only? specific segment? geography?)
- What's the control vs. variant?
- Success metrics: conversion rate, ARPU, revenue per visitor, churn rate
- Guardrail metrics: support ticket volume, cancellation rate, NPS
- Duration: minimum runtime for statistical significance
- Rollback criteria: what triggers reverting to current pricing
- Communication plan: how do we announce this to existing customers?