本文へ移動
cccskills
無料GitHub で公開

pricing-strategy

When the user wants help with pricing, packaging, or monetization — 'pricing tiers,' 'freemium,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'how much should I charge,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan.' For in-app upgrade screens, see paywall-upgrade-cro.

日本語の概要は準備中です。原文の説明を表示しています。

インストール方法を見る

含まれるファイル(4)

  • SKILL.md5.9 KB
  • evals/evals.json6.4 KB
  • references/research-methods.md4.7 KB
  • references/tier-structure.md7.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Pricing Strategy

Design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Before Starting

Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.

Gather (ask if not provided):

  1. Business Context — product type (SaaS, marketplace, e-commerce, service); current pricing; target market (SMB, mid-market, enterprise); GTM motion (self-serve, sales-led, hybrid)
  2. Value & Competition — primary value delivered; alternatives customers consider; competitor pricing
  3. Current Performance — conversion rate, ARPU, churn; pricing feedback from customers/prospects
  4. Goals — optimizing for growth, revenue, or profitability? Moving upmarket or downmarket?

Pricing Fundamentals

The Three Pricing Axes

  1. Packaging — what's included at each tier (features, limits, support level) and how tiers differ
  2. Pricing Metric — what you charge for (per user, per usage, flat fee) and how price scales with value
  3. Price Point — actual dollar amounts; perceived value vs. cost

Value-Based Pricing

Price on value delivered, not cost to serve: customer's perceived value is the ceiling; next best alternative is the floor for differentiation; your cost to serve is only a baseline, not the basis.

Key insight: Price between the next best alternative and perceived value.


Value Metrics

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 the customer grows, and 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?" Yes → good value metric; no → price doesn't align with value.


Tier Structure Overview

Good-Better-Best Framework

Good (Entry): core features, limited usage, low price. Better (Recommended): full features, reasonable limits, anchor price. Best (Premium): everything, advanced features, 2-3x Better price.

Tier differentiation: feature gating (basic vs. advanced), 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 the 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 the optimal pricing zone.

MaxDiff Analysis

Show sets of features; ask which is most/least important; results inform tier packaging.

For detailed research methods: See references/research-methods.md


When to Raise Prices

Signs It's Time

  • Market: competitors raised prices; prospects don't flinch; "It's so cheap!" feedback
  • Business: very high conversion (>40%); very low churn (<3% monthly); strong unit economics
  • Product: 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 per tier.

Common elements: feature comparison table, who each tier is for, FAQ, annual discount callout (17-20%), money-back guarantee, customer logos/trust signals.

Psychology: anchoring (show higher-priced option first); decoy effect (middle tier = 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. Current ARPU and conversion rate?
  3. Primary value metric?
  4. Main pricing personas?
  5. Self-serve, sales-led, or hybrid?
  6. What pricing changes are you considering?

Related Skills

  • churn-prevention — cancel flows, save offers, reducing revenue churn
  • page-cro — pricing page conversion
  • copywriting — pricing page copy
  • marketing-psychology — pricing psychology principles
  • ab-test-setup — testing pricing changes
  • revops — deal desk processes and pipeline pricing
  • sales-enablement — proposal templates and pricing presentations

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

ai-seo

無料

When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

architect

無料

Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.

日本語の概要は準備中です。原文の説明を表示しています。

rajitsaha/100xprism102026年10月14日 更新

rajitsaha のスキルをすべて見る

このスキルの問題を報告する