본문으로 건너뛰기
cccskills
무료GitHub에 공개

pricing-strategy

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,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Pricing Strategy

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.

Before Starting

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

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?

Related Skills

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

ai-seo

무료

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

autoplan

무료

Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wants to run the full review gauntlet without answering 15-30 intermediate questions. (gstack) Voice triggers (speech-to-text aliases): "auto plan", "automatic review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

benchmark

무료

Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mostafasudo/appilot32026년 9월 14일 업데이트

mostafasudo의 스킬 모두 보기

이 스킬의 문제 신고