Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

pricing-strategy定价策略

Agent Skill

pricing-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,536

周安装

64

GitHub Stars

103

下载量

512
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pricing-strategy(定价策略)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/pricing-strategy
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill pricing-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill pricing-strategy

简介

pricing-strategy 构建 SaaS 定价体系,围绕价值度量、套餐结构与价格点展开三维设计。

  • 融合价值定价法、竞品分析与价格页 UX 优化,支持涨价执行与 tier 结构调整。
  • 输出可测试的价格假设与收益预测模型,降低试错成本。
  • 实施前应完成市场验证与客户访谈,防止脱离需求的定价决策。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

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.

Use when

  • The user asks to "design pricing", "set prices", or "choose a value metric"
  • Pricing tiers need to be restructured (Good-Better-Best, add/remove tiers, repackage features)
  • A price increase is planned and needs execution design (strategy, timing, communication, grandfathering)
  • Conversion on the pricing page is flat or declining
  • Freemium vs free trial decision needs to be made, or the freemium tier is cannibalizing paid
  • Competitor pricing shifts require a positioning response
  • The user says "our pricing feels off" or asks for a pricing audit

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.

  • *Validate:* value metric chosen before tier design; tier design locked before price points; price points tested against the corridor before 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.

  • *Validate:* the diagnosis names a specific failure mode (e.g., "middle tier too narrow", "value metric doesn't scale") before any change is proposed.

Mode 3: Price Increase

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

  • *Validate:* grandfather policy defined, communication window set (90+ days for annual customers), and expected churn modeled before sending the first notice.

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.jsonpositionalPath to JSON file with pricing model configuration
--formatoptionalOutput 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.jsonpositionalPath to JSON file with Van Westendorp survey responses
--formatoptionalOutput 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.jsonpositionalPath to JSON file with price increase scenario data
--formatoptionalOutput 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

Anti-patterns

Anti-patternFailure modeFix
Jumping to the price point before locking the value metricDiscounts and "just lower the price" become the only lever; packaging is stuckWork the axes in order: value metric → packaging → price point
Copying a competitor's pricing modelInherits their positioning and unit economics — which may not fit the productUse competitor pricing as a data point for the corridor, not a template
Per-seat pricing on a tool where one power user does the workUsage grows but seats don't; revenue stallsSwitch to usage-based, hybrid (base + usage), or per-feature
Raising prices to fix a churn problemChurn accelerates; pricing gets blamed for a retention problemDiagnose churn drivers first; if the product is the issue, price increases amplify the damage
Adding a fourth tier to "capture more willingness to pay"Paradox of choice collapses conversion; sales cycle lengthensKeep 3 tiers public; put the fourth behind "Contact Sales" if enterprise-specific
Announcing a price increase without grandfathering existing customersImmediate churn spike; NPS collapse; public backlashGrandfather for 6-12 months on annual plans; communicate 90+ days in advance
Using MSRP or list price internally for forecastingActual ACV diverges from list by 20-40% due to discounts; forecasts missForecast on expected-realized price net of standard discount, not list
Freemium tier that gives away the core value metricFree users never convert; paid tier cannibalizedGate the value metric (volume, seats, integrations) — not feature access only

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.04%
按下载量换算195

Claude

26.16%
按下载量换算134

Cursor

19.16%
按下载量换算98

Gemini CLI

8.54%
按下载量换算44

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills