Agent skill
pricing-strategy
When the user wants help with pricing decisions, packaging, or monetization strategy.
Filed under Pricing and packaging.
From mia-ppp/PMM-Skills · 45 skill entries · 71 · pushed 2026-10-16
What it does when it runs
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing psychology,' 'anchoring,' 'decoy pricing,' 'nobody picks the middle plan,' or 'make this plan the most popular.' Use this whenever someone is figuring out what to charge or how to structure their plans. It owns which plan people pick. For pricing page conversion (layout, clarity, bounce), see acquisition-conversion. For in-app upgrade screens, see upgrade-conversion.
Automated analysis of the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Ask about pricing-strategy
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/mia-ppp/PMM-Skills.git /tmp/PMM-Skills git -C /tmp/PMM-Skills sparse-checkout set "skills/pricing-strategy" mkdir -p ~/.claude/skills/pricing-strategy cp -R "/tmp/PMM-Skills/skills/pricing-strategy/." ~/.claude/skills/pricing-strategy/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from mia-ppp/PMM-Skills/blob/5281aa6e55ca12d2ad5f97c3bf45e8cf49488225/skills/pricing-strategy/SKILL.md, which is licensed MIT (repository). 1,225 words, 34 headings.
Pricing Strategy
Context research handoffs
When receiving a context-establishment handoff, read
../_shared/context-establishment.md. Reuse its question, scope, source/finding
IDs, approved context/version, GAP IDs and completion criteria. Analyze only your
owned domain; return provenance-bearing findings, opposing evidence, limitations,
completion status and unapproved implications to product-marketing-context.
Use decision-specific evidence readiness; approval is separate. A hold affects
only its decision. Do not write canon or automatically save chained results into
bootstrap context. Standalone artifacts retain their existing format and may
attach the shared return. Preserve IDs and status without duplicating studies.
Use the company SSOT when present: follow ../_shared/ssot-consumption.md and the project manifest to load only relevant approved context. Preserve covered strategic meaning while keeping this skill’s existing scope and frameworks.
You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Behavioral hypotheses
Read ../_shared/behavioral-principles.md only when useful. Treat framing, anchoring and choice effects as hypotheses to validate, not evidence of willingness to pay or universal rules.
Before Starting
Load the evidence labels: read ../_shared/evidence-gaps.md (relative to this skill's folder) and follow it. Label every claim, benchmark, and number Sourced, Assumed, or Gap. Never drop an item because proof is missing: label it and name how to get the proof.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Business Context
- What type of product? (SaaS, marketplace, e-commerce, service)
- What's your current pricing (if any)?
- What's your target market? (SMB, mid-market, enterprise)
- What's your go-to-market motion? (self-serve, sales-led, hybrid)
2. Value & Competition
- What's the primary value you deliver?
- What alternatives do customers consider?
- How do competitors price?
3. Current Performance
- What's your current conversion rate?
- What's your ARPU and churn rate?
- Any feedback on pricing from customers/prospects?
4. Goals
- Optimizing for growth, revenue, or profitability?
- Moving upmarket or expanding downmarket?
Pricing Fundamentals
Relevant persona intelligence informs packaging hypotheses. Willingness-to-pay conclusions require pricing evidence; persona reuse does not establish them.
The Three Pricing Axes
1. Packaging: What's included at each tier?
- Features, limits, support level
- How tiers differ from each other
2. Pricing Metric: What do you charge for?
- Per user, per usage, flat fee
- How price scales with value
3. Price Point: How much do you charge?
- The actual dollar amounts
- Perceived value vs. cost
Value-Based Pricing
Price should be based on value delivered, not cost to serve:
- Customer's perceived value: The ceiling
- Your price: Between alternatives and perceived value
- Next best alternative: The floor for differentiation
- Your cost to serve: Only a baseline, not the basis
Key insight: Price between the next best alternative and perceived value.
Value Metrics
What is a Value Metric?
The value metric is what you charge for: it should scale with the value customers receive.
Good value metrics:
- Align price with value delivered
- Are easy to understand
- Scale as customer grows
- Are hard to game
Common Value Metrics
| Metric | Best For | Example |
|---|---|---|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
Choosing Your Value Metric
Ask: "As a customer uses more of [metric], do they get more value?"
- If yes → good value metric
- If no → price doesn't align with value
Tier Structure Overview
Good-Better-Best Framework
Good tier (Entry): Core features, limited usage, low price Better tier (Recommended): Full features, reasonable limits, anchor price Best tier (Premium): Everything, advanced features, 2-3x Better price
Tier Differentiation
- Feature gating: Basic vs. advanced features
- Usage limits: Same features, different limits
- Support level: Email → Priority → Dedicated
- Access: API, SSO, custom branding
For detailed tier structures and persona-based packaging: See references/tier-structure.md
Pricing Research
Van Westendorp Method
Four questions that identify acceptable price range:
- Too expensive (wouldn't consider)
- Too cheap (question quality)
- Expensive but might consider
- A bargain
Analyze intersections to find optimal pricing zone.
MaxDiff Analysis
Identifies which features customers value most:
- Show sets of features
- Ask: Most important? Least important?
- Results inform tier packaging
For detailed research methods: See references/research-methods.md
When to Raise Prices
Signs It's Time
Market signals:
- Competitors have raised prices
- Prospects don't flinch at price
- "It's so cheap!" feedback
Business signals:
- Very high conversion rates (>40%)
- Very low churn (<3% monthly)
- Strong unit economics
Product signals:
- Significant value added since last pricing
- Product more mature/stable
Price Increase Strategies
- Grandfather existing: New price for new customers only
- Delayed increase: Announce 3-6 months out
- Tied to value: Raise price but add features
- Plan restructure: Change plans entirely
Pricing Page Best Practices
Above the Fold
- Clear tier comparison table
- Recommended tier highlighted
- Monthly/annual toggle
- Primary CTA for each tier
Common Elements
- Feature comparison table
- Who each tier is for
- FAQ section
- Annual discount callout (17-20%)
- Money-back guarantee
- Customer logos/trust signals
Pricing Psychology
- Anchoring: Show higher-priced option first
- Decoy effect: Middle tier should be best value
- Charm pricing: $49 vs. $50 (for value-focused)
- Round pricing: $50 vs. $49 (for premium)
Pricing Checklist
Before Setting Prices
- Defined target customer personas
- Researched competitor pricing
- Identified your value metric
- Conducted willingness-to-pay research
- Mapped features to tiers
Pricing Structure
- Chosen number of tiers
- Differentiated tiers clearly
- Set price points based on research
- Created annual discount strategy
- Planned enterprise/custom tier
Task-Specific Questions
- What pricing research have you done?
- What's your current ARPU and conversion rate?
- What's your primary value metric?
- Who are your main pricing personas?
- Are you self-serve, sales-led, or hybrid?
- What pricing changes are you considering?
Output Rules
- No em dashes in output.
- Open with the "Inputs and assumptions" note from
../_shared/evidence-gaps.md. - Label every claim, benchmark, and number Sourced, Assumed, or Gap.
- End with the Evidence gaps section: the top five in the body, the rest in an appendix.
- Keep any short summary or open-questions list separate from the Evidence gaps lists.
Related Skills
- customer-marketing: For cancel flows, save offers, and reducing revenue churn
- acquisition-conversion: For optimizing pricing page conversion
- marketing-copy: For pricing page copy
- marketing-experimentation: For testing pricing changes
- revops: For deal desk processes and pipeline pricing
- sales-enablement: For proposal templates and pricing presentations
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- pricing-strategy by OpenClaudia · 724
- pricing-strategy by thatrebeccarae · 189
- pricing-strategy by manojbajaj95 · 109
- pricing-strategy by GTMify · 25
- pricing-strategy by sidchaudhary · 6
- pricing-strategy by jurjen-gtm-engineer · 0
- pricing-strategy by erickdronski · 0
- content-strategy by coreyhaines31 · 57,918
Need help setting it up?
This page tells you what pricing-strategy does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.