agentleFS
mia-pppmia-ppp/PMM-Skills/skills/pricing-strategy/SKILL.md

pricing-strategy

Skill2 starsChanged 28 days agoMITView on GitHub

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.

110 other projects use a version of this, 56 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • skytiger6724Skill

    brainstorm-okrs

    Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 103 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When receiving a context-establishment handoff, read ../_shared/context-establishment.md.

    line 12
  2. Distinctive:

    Use decision-specific evidence readiness.

    line 17
  3. Very specific:

    Use the company SSOT when present: follow ../_shared/ssot-consumption.md and the project manifest to load only relevant approved context.

    line 23
  4. Very specific:

    Read ../_shared/behavioral-principles.md only when useful.

    line 29
  5. Very specific:

    Load the evidence labels: read ../_shared/evidence-gaps.md (relative to this skill's folder) and follow it.

    line 34
  6. Very specific:

    If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions.

    line 37
  7. Distinctive:

    Your cost to serve: Only a baseline, not the basis

    line 89
  8. Distinctive:

    Ask: "As a customer uses more of [metric], do they get more value?"

    line 120
  9. Distinctive:

    If yes → good value metric

    line 121
  10. Distinctive:

    If no → price doesn't align with value

    line 122
  11. Distinctive:

    Ask: Most important? Least important?

    line 161
  12. Distinctive:

    No em dashes in output.

    line 250
  13. Distinctive:

    Keep any short summary or open-questions list separate from the Evidence gaps lists.

    line 254

“Common” is measured: kept by at least 6 in 10 of the 103 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

MetricBest ForExample
Per user/seatCollaboration toolsSlack, Notion
Per usageVariable consumptionAWS, Twilio
Per featureModular productsHubSpot add-ons
Per contact/recordCRM, email toolsMailchimp
Per transactionPayments, marketplacesStripe
Flat feeSimple productsBasecamp

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:

  1. Too expensive (wouldn't consider)
  2. Too cheap (question quality)
  3. Expensive but might consider
  4. 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

  1. Grandfather existing: New price for new customers only
  2. Delayed increase: Announce 3-6 months out
  3. Tied to value: Raise price but add features
  4. 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

  1. What pricing research have you done?
  2. What's your current ARPU and conversion rate?
  3. What's your primary value metric?
  4. Who are your main pricing personas?
  5. Are you self-serve, sales-led, or hybrid?
  6. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.