Claude-Skills pricing-strategy

install
source · Clone the upstream repo
git clone https://github.com/borghei/Claude-Skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/borghei/Claude-Skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/business-growth/pricing-strategy" ~/.claude/skills/borghei-claude-skills-pricing-strategy && rm -rf "$T"
manifest: business-growth/pricing-strategy/SKILL.md
source content

Pricing Strategy

Production-grade SaaS pricing framework covering the three pricing axes (value metric, packaging, price point), value-based pricing methodology, tier architecture, pricing research methods, pricing page design, price increase execution, and competitive pricing positioning. Pricing is positioning -- the right price communicates as much about your product as your marketing does.


Table of Contents


Operating Modes

Mode 1: Design From Scratch

No pricing exists or full rebuild needed. Work through value metric, tier structure, price points, and page design.

Mode 2: Optimize Existing Pricing

Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. Audit, benchmark, and identify specific improvements.

Mode 3: Price Increase

Prices need to go up. Design a strategy that increases revenue without burning customer relationships.


The Three Pricing Axes

Every pricing decision lives across three axes. Most teams skip to price point. That is backwards.

     ┌──────────────────┐
     │   VALUE METRIC    │  What do you charge for?
     │  (how it scales)  │  (per seat, per usage, per feature)
     └────────┬─────────┘
              │
     ┌────────┴─────────┐
     │   PACKAGING       │  What is in each tier?
     │  (what you get)   │  (feature bundles, limits, support levels)
     └────────┬─────────┘
              │
     ┌────────┴─────────┐
     │   PRICE POINT     │  How much?
     │  (the number)     │  (actual dollar amount)
     └──────────────────┘

Lock in the value metric first, then packaging, then test the price point.


Value Metric Selection

Common Value Metrics

MetricBest ForExamplesScales With Value?
Per seat / userCollaboration tools, CRMsSalesforce, Notion, LinearYes if all users are active
Per usageAPIs, infrastructure, AIStripe, Twilio, OpenAIYes
Per featurePlatform plays, modular productsHubSpot, IntercomSomewhat
Flat feeSimple products, SMB marketBasecamp, CalendlyNo (subsidizes heavy users)
Per outcomeMeasurable ROI productsCommission-based toolsPerfectly
HybridMost mature SaaSBase fee + usage, seat + featuresYes

Selection Criteria

Answer these 4 questions:

QuestionAnswer Points To
What makes a customer willing to pay MORE?That is your value metric
Does the metric scale with their success?If they grow, you should grow
Is it easy to understand?Complexity kills conversion
Is it hard to game?Customers should not be able to work around it

Value Metric Red Flags

Red FlagProblemFix
Per-seat in a tool where 1 power user does all the workSeats do not scale with valueSwitch to usage or feature-based
Flat fee when some customers get 10x the value of othersSubsidizing heavy usersAdd usage tiers or hybrid model
Per-API-call when volume varies wildly week to weekUnpredictable bills cause churnAdd usage bands or committed minimums
Per-feature when core value requires multiple featuresNickel-and-diming perceptionBundle core features, gate advanced only

Tier Architecture

Good-Better-Best (3 Tiers)

Three tiers is the standard because it anchors perception.

TierRolePricing RuleFeature Rule
Entry (Good)Captures price-sensitive segmentCovers your costs minimumCore product, limited usage
Middle (Better)Where you push most customers2-3x entry tierEverything a growing company needs
Top (Best)High-value enterprise customers3-5x entry or customSSO, audit logs, SLA, dedicated support

Feature Allocation Framework

Feature CategoryEntry TierMiddle TierTop Tier
Core productLimitedFullFull
Usage limitsLowMediumHigh/Unlimited
Users/seats1-35-25 or unlimitedUnlimited
IntegrationsBasic (3-5)FullFull + custom
ReportingBasicAdvancedCustom
SupportEmail (48h)Priority (24h)Dedicated CSM
Admin features----SSO, SCIM, audit logs
SLA----99.9% uptime
Data retention90 days1 yearUnlimited
API access--Rate-limitedFull

Tier Naming

ApproachExamplesBest For
Size-basedStarter, Growth, EnterpriseUniversal SaaS
Capability-basedBasic, Pro, EnterpriseFeature-differentiated products
Audience-basedIndividual, Team, OrganizationCollaboration tools
Persona-basedFreelancer, Agency, EnterpriseAudience-segmented products

Naming rules:

  • Names should be instantly understandable
  • Avoid jargon or made-up words
  • The default/recommended plan should be visually highlighted

Value-Based Pricing

The Pricing Corridor

[Cost floor] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value]

Step-by-Step

Step 1: Define the next-best alternative

  • What would the customer do without your product?
  • What does that cost them? (competitor, manual process, hiring)

Step 2: Estimate value delivered

  • Time saved x hourly rate of the person using it
  • Revenue generated or protected
  • Cost of errors/risk avoided
  • Ask customers: "What would you lose if you stopped using us?"

Step 3: Price in the corridor

  • Price at 10-20% of documented value delivered
  • Above the next-best alternative (signals confidence)
  • Below the perceived value ceiling (customer feels good ROI)

Conversion Rate as a Pricing Signal

Trial-to-Paid RateSignalAction
> 40%Likely underpricedTest a 20-30% price increase
15-30%Healthy for most SaaSOptimize packaging, not price
< 10%Possibly overpriced OR trial experience is brokenInvestigate whether the issue is price or activation

Pricing Research Methods

Van Westendorp Price Sensitivity Meter

Four questions asked to 30+ current customers or qualified prospects:

  1. At what price would this be so cheap you would question its quality?
  2. At what price would this be a great deal?
  3. At what price would this start to feel expensive but still acceptable?
  4. At what price would this be too expensive to consider?

Interpretation: Plot four curves. The intersection of "too cheap" and "too expensive" gives the acceptable range. The intersection of "bargain" and "expensive" gives the optimal price point.

MaxDiff Analysis

Show respondents sets of features and ask which they value most and least. Reveals relative value of each feature for tier allocation decisions.

When to use: Deciding which features go in which tier.

Competitor Benchmarking

StepAction
1List direct competitors and alternatives customers compare you to
2Record published pricing (plans, prices, value metrics)
3Note what is included at each tier
4Identify where you over-deliver and under-deliver vs each
5Position relative to market: premium (+20-40%), parity, value (-10-20%)

Do not copy competitor prices. Their pricing reflects their cost structure and positioning, not yours.

Customer Willingness-to-Pay Interview

Ask existing customers (especially champions):

  • "How would you describe the ROI of [product] to your CFO?"
  • "What would you do if the price doubled? Tripled?"
  • "What is the most you would pay before you would switch?"
  • "If you had to cut 50% of your budget, would this survive?"

Pricing Page Design

Above the Fold

Required elements:

  • Plan names with clear positioning
  • Prices with monthly/annual toggle (annual shows savings: "Save 20%" or "2 months free")
  • 3-5 bullet differentiators per plan
  • CTA button per plan
  • "Most Popular" or "Recommended" badge on the middle tier
  • "Most Popular" plan should be the default tab/column

Below the Fold

  • Full feature comparison table -- Comprehensive, scannable, uses checkmarks and X marks
  • FAQ section -- The 5 objections that stop purchases:
    1. "Can I cancel anytime?"
    2. "What happens when I hit limits?"
    3. "Do you offer refunds?"
    4. "Is my data secure?"
    5. "Can I switch plans later?"
  • Social proof -- Logos, testimonials, case studies relevant to each tier
  • Security badges -- SOC2, ISO 27001, GDPR (if applicable)

Annual vs Monthly Toggle

  • Default to showing annual pricing (it improves LTV)
  • Show savings explicitly: "Save 20%" or "$X/year (saves $Y)"
  • Do NOT hide monthly pricing -- hiding it creates distrust
  • Monthly/annual toggle should be above the plan cards

Enterprise Tier Design

ApproachWhen to Use
Published priceWhen enterprise pricing is standardized
"Contact Sales"When pricing requires custom scoping
"Starting at $X"Balance transparency with flexibility

Price Increase Playbook

Strategy Selection

StrategyRisk LevelUse When
New customers onlyLowTesting market response, significant uncertainty
Grandfather + scheduled increaseMediumLoyal customer base, want to preserve relationships
Tied to new valueLowClear product improvements justify the increase
Plan restructureMediumPackaging changes alongside price changes
Uniform increaseMedium-HighPrice is clearly below market, confident in value

Execution Timeline

WeekAction
Week -12Decide strategy, model revenue impact at 80%, 90%, 100% retention
Week -8Segment customers by risk (annual contracts, champions vs detractors, usage level)
Week -6Prepare communication (email, in-app, FAQ, CS talking points)
Week -4Announce to existing customers (60+ day notice for annual contracts)
Week -4Offer lock-in: "Keep current price for 12 months with annual commitment"
Week 0New pricing goes live for new customers
Week +4Existing customer pricing changes (if not grandfathered)
Week +12Review: churn rate, downgrade rate, support ticket volume, revenue impact

Communication Template

Subject: "Changes to your [Product] plan"

  • Paragraph 1: What is changing and when
  • Paragraph 2: Why (new features, investment in X, market alignment)
  • Paragraph 3: What this means for them specifically (old price -> new price)
  • Paragraph 4: Options (lock in current price with annual, downgrade, contact support)
  • CTA: "View your options" or "Talk to your account manager"

Expected Impact

For a 20-30% price increase:

  • Expected churn: 5-15% of affected customers
  • Revenue impact: Net positive if churn < (increase % / (100% + increase %))
  • Example: 25% increase is net positive if churn < 20%

Freemium vs Free Trial Decision

FactorFreemiumFree Trial
Product complexitySimple, quick time-to-valueComplex, needs exploration
Network effectsStrong (value increases with users)Weak
Market sizeVery large TAM, need top-of-funnelFocused market
Sales motionSelf-serve, product-ledSales-assisted
Conversion rate target2-5% free-to-paid15-30% trial-to-paid
Revenue urgencyCan afford long paybackNeed revenue sooner

Freemium Tier Design Rules

  • Free tier must deliver real, ongoing value (not a crippled experience)
  • The limit that triggers upgrade should be a natural success indicator
  • Free users should be able to see what paid features look like (soft gates, previews)
  • Do not remove value from free tier once established (erodes trust)

Competitive Pricing Analysis

Pricing Position Map

                    Premium ($$$)
                         │
                         │
     [Competitor B]      │    [Your Product?]
                         │
 Narrow ─────────────────┼──────────────────── Broad
 Feature Set             │                Feature Set
                         │
     [Competitor C]      │    [Competitor A]
                         │
                         │
                    Value ($)

Positioning Strategy

Your PositionPricing ApproachMessaging
Premium20-40% above market average"The [category] built for teams that demand the best"
Value leaderAt or slightly below market"Enterprise features at [segment] prices"
DisruptorRadically different model"Why pay per seat? [Product] is [price] for unlimited users"
ChallengerSlightly below the leader"Everything [Leader] does, at half the price"

Pricing Signals and Diagnostics

Pricing Health Check

SignalDiagnosisAction
Trial-to-paid > 40%UnderpricedTest 20-30% increase
All customers on middle tierNo upsell pathAdd enterprise features or higher tier
Customers never ask about priceToo cheapIncrease price
Churn rate > 5% monthlyFix churn before pricing changesUse churn-prevention first
Price unchanged for 2+ yearsInflation alone justifies 10-15% increasePlan an increase
Only one pricing optionNo anchoring, no upsellAdd tiers
Frequent discount requestsPossible overpricing or poor value communicationAudit value proposition

Output Artifacts

ArtifactFormatDescription
Pricing Strategy DocumentStructured analysisValue metric, packaging, price points with rationale
Tier ArchitectureFeature allocation tableWhat goes in each tier with justification
Pricing Page SpecificationLayout + copyAbove-fold design, feature table, FAQ, toggle behavior
Price Increase PlanTimeline + communicationsStrategy selection, rollout schedule, email templates
Competitive Pricing AnalysisComparison table + position mapMarket pricing landscape with positioning recommendation
Van Westendorp SurveyQuestion set + interpretation guideReady-to-deploy pricing research
Pricing Health ScorecardSignal + diagnosis tableCurrent pricing health assessment with action items

Tool Reference

1. pricing_model_analyzer.py

Analyzes a SaaS pricing model against best practices. Evaluates value metric alignment, tier architecture, feature allocation, and identifies pricing anti-patterns. Outputs a health scorecard with prioritized recommendations.

python scripts/pricing_model_analyzer.py pricing.json --format text
python scripts/pricing_model_analyzer.py pricing.json --format json
FlagTypeDescription
pricing.json
positionalPath to JSON file with pricing model configuration
--format
optionalOutput format:
text
(default) or
json

2. price_sensitivity_calculator.py

Implements the Van Westendorp Price Sensitivity Meter. Takes survey responses (too cheap, bargain, expensive, too expensive) and calculates the optimal price point, acceptable price range, and indifference price point.

python scripts/price_sensitivity_calculator.py survey.json --format text
python scripts/price_sensitivity_calculator.py survey.json --format json
FlagTypeDescription
survey.json
positionalPath to JSON file with Van Westendorp survey responses
--format
optionalOutput format:
text
(default) or
json

3. price_increase_modeler.py

Models the revenue impact of price increases at various retention scenarios. Takes current customer base, pricing, and proposed increase, then projects revenue impact at 80%, 90%, and 100% retention with break-even analysis.

python scripts/price_increase_modeler.py increase.json --format text
python scripts/price_increase_modeler.py increase.json --format json
FlagTypeDescription
increase.json
positionalPath to JSON file with price increase scenario data
--format
optionalOutput format:
text
(default) or
json

Troubleshooting

ProblemLikely CauseResolution
Trial-to-paid conversion above 40%Product is likely underpriced -- customers convert too easily because price is well below perceived valueTest a 20-30% price increase on new customers first; monitor conversion rate and revenue per user
All customers concentrate on middle tierNo compelling reason to upgrade to top tier; enterprise features missing or unclearAdd SSO, audit logs, dedicated support, SLA, and custom integrations to top tier; ensure 3-5x price jump from middle
Frequent discount requests from prospectsPrice may exceed perceived value, or value proposition is poorly communicatedAudit sales collateral for ROI messaging; consider adding a lighter entry tier rather than discounting
Price unchanged for 2+ yearsInflation alone justifies 10-15% increase; likely leaving significant revenue on the tablePlan a structured price increase using the execution timeline; start with new customers only to test
High involuntary churn on usage-based pricingUnpredictable bills cause customers to cancel; usage spikes create bill shockAdd usage bands, committed minimums, or spending caps with alerts at 80% threshold
Customers game the value metricPer-seat pricing with shared logins, or usage metrics that can be artificially reducedSwitch to a harder-to-game metric; add audit capabilities; consider hybrid model
Pricing page has low conversion but product is strongPricing page design issues (too many tiers, unclear differentiation, hidden annual toggle)Simplify to 3 tiers, highlight recommended plan, show annual savings prominently, add FAQ

Success Criteria

  • Trial-to-paid conversion rate stabilizes at 15-30% (healthy SaaS range) after pricing optimization
  • Tier distribution shows healthy spread: 20-30% entry, 50-60% middle, 15-25% top tier
  • Net revenue retention exceeds 110% (expansion revenue from upsells outpaces contraction)
  • Price increase execution retains 85%+ of affected customers within 90 days
  • Annual plan adoption reaches 50%+ when toggle defaults to annual pricing
  • Van Westendorp survey confirms current price falls within the acceptable range for 70%+ of respondents
  • Pricing page conversion rate improves by 15%+ after redesign implementing best practices

Scope & Limitations

In scope: Value metric selection, tier architecture design, price point research (Van Westendorp, competitor benchmarking, willingness-to-pay interviews), pricing page design specifications, price increase strategy and execution, freemium vs free trial decision frameworks, competitive pricing analysis and positioning, and pricing health diagnostics.

Out of scope: Pricing page visual design and CRO (use page-cro), in-app upgrade prompts and paywalls (use paywall-upgrade-cro), signup flow optimization after pricing page (use signup-flow-cro), churn intervention when churn is the root cause (use churn-prevention), and full competitive analysis beyond pricing (use competitive-teardown). Scripts do not integrate with billing systems (Stripe, Chargebee, etc.) or analytics platforms.

Limitations: Van Westendorp analysis requires minimum 30 survey respondents for statistical validity. Pricing benchmarks are based on aggregate SaaS industry data and vary significantly by vertical, company stage, and geography. Credit-based and usage-based pricing models (growing to 38% of SaaS in 2026) have different optimization dynamics than flat-rate or per-seat models. Price elasticity varies by customer segment -- enterprise buyers are less price-sensitive than SMB.


Integration Points

  • page-cro -- Pricing page layout, CTA placement, and social proof design should follow page-cro best practices
  • paywall-upgrade-cro -- In-app upgrade screens must reflect the same tier structure and messaging as the public pricing page
  • competitive-teardown -- Competitive pricing data from teardowns feeds directly into pricing position map and tier design
  • churn-prevention -- Churn analysis by price point and tier informs whether pricing is causing retention issues
  • signup-flow-cro -- Signup flow design depends on pricing model (CC-required vs free trial vs freemium)
  • revenue-operations -- GTM efficiency metrics (LTV:CAC, Magic Number) validate whether pricing supports unit economics

Related Skills

  • page-cro -- Use for optimizing the pricing page conversion rate (layout, CTA, social proof). Not for pricing structure or tier design.
  • churn-prevention -- Use when churn is the underlying issue. Fix retention before raising prices.
  • competitive-teardown -- Use for comprehensive competitive analysis. Feed teardown pricing data into this skill.
  • paywall-upgrade-cro -- Use for in-app upgrade prompts and paywalls. Different from public pricing page design.
  • signup-flow-cro -- Use for optimizing the signup flow that follows pricing page conversion.