skenetechnologies/plg-skills/pricing-strategy

Claude Code and agent skill by skenetechnologies/plg-skills

Trust tier 3
  • community
  • ext:[{"type":"plugin","description":"Custom plugin integration"}]
Source check pending

Checking that the SKILL.md file is still in the repository.

When the user wants to design or optimize pricing, packaging, or monetization -- including tier structure, freemium design, value metrics, or price research. Also use when the user says "pricing page," "how to price," "freemium vs free trial," "Good-Better-Best tiers," or "value-based pricing." For feature gating, see feature-gating. For trial optimization, see trial-optimization. For usage-based models, see usage-based-pricing.

Install

npx vskill@latest install skenetechnologies/plg-skills/pricing-strategy

Semi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard

SKILL.md

Pricing Strategy

You are a pricing strategist. A comprehensive framework for designing pricing, packaging, and monetization for product-led growth companies. Pricing is the single highest-leverage growth lever most companies underinvest in.


1. Phil Carter's 5 Ps of PLG Monetization

Before diving into specific tactics, understand the five interconnected dimensions of PLG monetization:

DimensionDefinitionKey Question
PricingHow much you chargeWhat price point maximizes revenue and growth?
PackagingWhat is included in each tierWhich features go in which plan?
PaywallsWhere and how you gate valueWhat triggers the upgrade moment?
PaymentsHow customers payWhat is the purchase flow and billing mechanics?
PromotionsDiscounts, trials, and incentivesHow do you reduce friction to first purchase?

These five dimensions must be designed together. Optimizing one in isolation creates misalignment. For example, a great pricing model with a broken payment flow still loses conversions.


2. Value-Based Pricing Methodology

Principle

Price should reflect the value your product delivers to the customer, not your cost to deliver it. Cost-plus pricing leaves money on the table. Competitor-based pricing ignores your unique value.

Steps to Value-Based Pricing
  1. Identify the customer's alternative -- What would they do without your product? (Manual process, competitor, custom build, hire someone)
  2. Quantify the value gap -- How much time, money, or risk does your product save compared to the alternative?
  3. Apply the value capture ratio -- Typically capture 10-25% of the value you create. If you save a customer $100K/year, pricing at $10K-$25K/year is defensible.
  4. Segment by willingness-to-pay -- Different customer segments derive different value. Use tiered pricing to capture value from each segment.
  5. Validate with research -- Use the methods in Section 9 to validate your pricing hypothesis.
Value-Based Pricing Worksheet
Customer segment: [e.g., Mid-market marketing teams]
Current alternative: [e.g., Manual reporting in spreadsheets]
Time saved per week: [e.g., 8 hours]
Hourly cost of that time:[e.g., $75/hour]
Annual value created: [e.g., 8 x $75 x 52 = $31,200]
Value capture ratio: [e.g., 15%]
Target price point: [e.g., $31,200 x 0.15 = $4,680/year = $390/month]

3. Value Metric Identification

The value metric is the unit you charge on. It is the single most important pricing decision.

What Makes a Good Value Metric

A strong value metric satisfies all four criteria:

CriterionTestExample
Scales with valueAs the customer gets more value, the metric increasesSeats scale with team adoption
Easy to understandCustomer can predict their bill"Per user per month" is clear
PredictableCustomer can forecast spendAPI calls can spike unexpectedly -- less predictable
Hard to gameCustomer cannot easily reduce the metric without reducing usage"Active users" is harder to game than "registered users"
Common Value Metrics by Product Type
Product TypeCommon MetricsNotes
Collaboration toolsSeats / active usersSlack, Notion, Figma
Infrastructure / APIAPI calls, compute, storageTwilio, AWS, Snowflake
Marketing toolsContacts, emails sent, visitors trackedHubSpot, Mailchimp
Sales toolsSeats + contacts/recordsSalesforce, Apollo
AnalyticsEvents tracked, MTUsAmplitude, Mixpanel
AI productsCredits, tokens, generationsOpenAI, Jasper
Design toolsProjects, exports, editorsCanva, Figma
Value Metric Selection Process
  1. List 5-8 candidate metrics
  2. Score each on the four criteria (1-5 scale)
  3. Evaluate operational feasibility (can you meter it accurately?)
  4. Test customer understanding (do they intuitively get it?)
  5. Model revenue impact (does it grow as customers grow?)

4. Three Pricing Dimensions

Every pricing model is defined by three dimensions. Design them in this order:

Dimension 1: Packaging (What is in each tier)

This is covered in depth in the feature-gating skill. Key principles:

  • Each tier should serve a distinct buyer persona or use case
  • Moving up a tier should feel like a natural graduation, not a tax
  • Every tier must deliver standalone value
Dimension 2: Metric (How you charge)

Choose from:

  • Flat rate: One price for everything (simple but leaves money on the table)
  • Per seat: Charge per user (most common in B2B SaaS)
  • Usage-based: Charge per unit consumed (see usage-based-pricing skill)
  • Hybrid: Base platform fee + usage or seat component
  • Credit-based: Pre-purchased credits consumed by usage
Dimension 3: Price Point (How much)

Set using value-based methodology (Section 2) and validated with research (Section 9).


5. Tier Structure: Good-Better-Best

The Standard 3-Tier Model
TierPurposeTypical FeaturesBuyer
Good (Starter/Basic)Entry point, proves valueCore features, limited usageIndividual / small team
Better (Pro/Growth)Workhorse plan, drives most revenueAll core + advanced features, higher limitsGrowing team / department
Best (Business/Enterprise)Premium, high-valueEverything + admin, security, support, integrationsLarge team / organization
Design Principles
  1. The "Better" plan should be most popular -- Design it to be the obvious choice. Highlight it as "Most Popular" or "Recommended."
  2. The "Good" plan should be a real product -- Not a crippled demo. Users should be able to accomplish real work.
  3. The "Best" plan justifies its price -- Include features that genuinely matter to larger organizations (SSO, SAML, audit logs, SLAs, dedicated support).
  4. Price anchoring -- The "Best" plan makes the "Better" plan look like a great deal.
When to Add a 4th Tier

Add a dedicated Free tier (making it 4 tiers total: Free, Starter, Pro, Enterprise) when:

  • Your product benefits from network effects
  • You want broad top-of-funnel adoption
  • The marginal cost of free users is low
  • Free users generate data, content, or referrals that benefit paid users
Enterprise Tier Design

Enterprise tiers typically include:

  • SSO/SAML authentication
  • Advanced admin controls and role management
  • Audit logs and compliance features
  • Custom data retention
  • Dedicated support (SLA, named CSM)
  • Custom integrations
  • Volume discounts
  • Custom contracts and invoicing
  • Uptime SLAs

Pricing: "Contact Sales" is standard for enterprise. Provide enough information on the pricing page that prospects self-qualify.


6. Freemium Design

What to Give Free

A strong free tier should include:

  • Core functionality that demonstrates the product's value proposition
  • Enough capacity for a single user or small team to do real work
  • Collaboration features that drive viral growth (invite teammates)
  • Integrations that increase stickiness
What to Gate

Gate features that:

  • Deliver premium value beyond basic use cases
  • Serve team/organizational needs (admin, security, compliance)
  • Require meaningful compute or storage resources
  • Differentiate your paid plans from competitors
Freemium Decision Tree
Is the feature essential to understanding the product's value?
├── YES → Include in free tier
└── NO
├── Does the feature drive viral or collaborative behavior?
│ ├── YES → Include in free tier
│ └── NO
│ ├── Does the feature serve advanced/power users?
│ │ ├── YES → Gate behind Pro or Business tier
│ │ └── NO
│ │ └── Does the feature serve team/org needs?
│ │ ├── YES → Gate behind Team or Business tier
│ │ └── NO → Evaluate case-by-case
└── (see feature-gating skill for complete framework)

7. Free Trial Design

Trial Type Selection
FactorNo-Card TrialCard-Required TrialReverse Trial
Signup volumeHighLower (30-50% fewer)High
Conversion rate3-8%40-60%Varies (5-15%)
Lead qualityMixedHigher intentMixed
Best forBroad market, low ACVFocused market, higher ACVStrong free tier exists
RiskLow-quality signupsFriction at signupUsers upset at downgrade
Trial Length Decision Framework
  1. How long does it take to reach the aha moment? Measure time-to-activation for successful users.
  2. Add a buffer. If aha moment takes 3 days, a 7-day trial works. If it takes 7 days, use 14 days.
  3. Consider the buying process. Enterprise buyers need more time for procurement and team evaluation.
  4. Shorter is usually better. Shorter trials create urgency. Only extend if users genuinely need more time.
Trial LengthBest ForExamples
7 daysSimple products, fast time-to-valueProductivity apps, simple tools
14 daysStandard B2B SaaSMost mid-market products
30 daysComplex products, team deploymentEnterprise tools, data platforms
Reverse Trial (Elena Verna Framework)

The reverse trial gives new users access to the full premium product for a limited time, then downgrades them to the free tier. This approach:

  1. Shows users the full value before asking them to pay
  2. Creates a sense of loss when premium features are removed
  3. Works best when the free tier is genuinely useful (so users stay)
  4. Requires clear communication about what changes at trial end

When reverse trial works: Strong free tier, obvious premium features, product where you need time to build data/content.

When it does not work: No viable free tier, premium value is not obvious, users churn instead of downgrading.

See trial-optimization for detailed implementation guidance.


8. Annual vs Monthly Pricing

Standard Approach
  • Offer both monthly and annual billing
  • Annual discount: 15-20% (equivalent to "2 months free" or "save 17%")
  • Display annual pricing as monthly equivalent ("$29/mo billed annually")
  • Default the pricing page toggle to annual
Nudging Annual Plans
  1. Visual emphasis -- Make annual the default selection, show savings prominently
  2. Framing -- "Save $348/year" is more compelling than "Save 17%"
  3. In-app upgrade prompts -- After a few months of monthly billing, suggest switching to annual
  4. Checkout incentive -- Offer an additional perk for annual (e.g., bonus features, onboarding session)
When Monthly-Only Works
  • Very early stage (need flexibility to change pricing)
  • Usage-based models where annual commitment is hard to predict
  • Very low price points where annual savings are trivial

9. Pricing Research Methods

Van Westendorp Price Sensitivity Meter

Ask four questions:

  1. At what price would this be too expensive (would not consider)?
  2. At what price would this be expensive but worth considering?
  3. At what price would this be a bargain?
  4. At what price would this be too cheap (suspect quality)?

Plot the cumulative distributions. The intersections reveal:

  • Point of Marginal Cheapness: intersection of "too cheap" and "expensive"
  • Point of Marginal Expensiveness: intersection of "too expensive" and "bargain"
  • Optimal Price Point: intersection of "too cheap" and "too expensive"
  • Acceptable Price Range: between marginal cheapness and marginal expensiveness

Sample size needed: 100-300 respondents per segment.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
17
Repository forks
1
7-day trend score
14

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 7 May 2026, 6 months ago.

Extension points

  • pluginCustom plugin integration

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/skenetechnologies/plg-skills/pricing-strategy/badge)](https://verified-skill.com/skills/skenetechnologies/plg-skills/pricing-strategy)

Something wrong with this skill or its page? Tell us.