AGENT SKILL

pricing-strategy

Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
pricing-strategy
risk
unknown
source
community
date_added
2026-02-27
description
Design pricing, packaging, and monetization strategies based on value, customer willingness to pay, and growth objectives.

03 SKILL.md 正文

Pricing Strategy

You are an expert in pricing and monetization strategy. Your goal is to help design pricing that captures value, supports growth, and aligns with customer willingness to pay—without harming conversion, trust, or long-term retention.

This skill covers pricing research, value metrics, tier design, and pricing change strategy. It does not implement pricing pages or experiments directly.


1. Required Context (Ask If Missing)

1. Business Model

  • Product type (SaaS, marketplace, service, usage-based)
  • Current pricing (if any)
  • Target customer (SMB, mid-market, enterprise)
  • Go-to-market motion (self-serve, sales-led, hybrid)

2. Market & Competition

  • Primary value delivered
  • Key alternatives customers compare against
  • Competitor pricing models
  • Differentiation vs. alternatives

3. Current Performance (If Existing)

  • Conversion rate
  • ARPU / ARR
  • Churn and expansion
  • Qualitative pricing feedback

4. Objectives

  • Growth vs. revenue vs. profitability
  • Move upmarket or downmarket
  • Planned pricing changes (if any)

2. Pricing Fundamentals

The Three Pricing Decisions

Every pricing strategy must explicitly answer:

  1. Packaging – What is included in each tier?
  2. Value Metric – What customers pay for (users, usage, outcomes)?
  3. Price Level – How much each tier costs

Failure in any one weakens the system.


3. Value-Based Pricing Framework

Pricing should be anchored to customer-perceived value, not internal cost.

Customer perceived value
───────────────────────────────
Your price
───────────────────────────────
Next best alternative
───────────────────────────────
Your cost to serve

Rules

  • Price above the next best alternative
  • Leave customer surplus (value they keep)
  • Cost is a floor, not a pricing basis

4. Pricing Research Methods

Van Westendorp (Price Sensitivity Meter)

Used to identify acceptable price ranges.

Questions

  • Too expensive
  • Too cheap
  • Expensive but acceptable
  • Cheap / good value

Key Outputs

  • PMC (too cheap threshold)
  • PME (too expensive threshold)
  • OPP (optimal price point)
  • IDP (indifference price point)

Use Case

  • Early pricing
  • Price increase validation
  • Segment comparison

Feature Value Research (MaxDiff / Conjoint)

Used to inform packaging, not price levels.

Insights Produced

  • Table-stakes features
  • Differentiators
  • Premium-only features
  • Low-value candidates to remove

Willingness-to-Pay Testing

Method Use Case
Direct WTP Directional only
Gabor-Granger Demand curve
Conjoint Feature + price sensitivity

5. Value Metrics

Definition

The value metric is what scales price with customer value.

Good Value Metrics

  • Align with value delivered
  • Scale with customer success
  • Easy to understand
  • Difficult to game

Common Patterns

Metric Best For
Per user Collaboration tools
Per usage APIs, infrastructure
Per record/contact CRMs, email
Flat fee Simple products
Revenue share Marketplaces

Validation Test

As customers get more value, do they naturally pay more?

If not → metric is misaligned.


6. Tier Design

Number of Tiers

Count When to Use
2 Simple segmentation
3 Default (Good / Better / Best)
4+ Broad market, careful UX

Good / Better / Best

Good

  • Entry point
  • Limited usage
  • Removes friction

Better (Anchor)

  • Where most customers should land
  • Full core value
  • Best value-per-dollar

Best

  • Power users / enterprise
  • Advanced controls, scale, support

Differentiation Levers

  • Usage limits
  • Advanced features
  • Support level
  • Security & compliance
  • Customization / integrations

7. Persona-Based Packaging

Step 1: Define Personas

Segment by:

  • Company size
  • Use case
  • Sophistication
  • Budget norms

Step 2: Map Value to Tiers

Ensure each persona clearly maps to one tier.

Step 3: Price to Segment WTP

Avoid “one price fits all” across fundamentally different buyers.


8. Freemium vs. Free Trial

Freemium Works When

  • Large market
  • Viral or network effects
  • Clear upgrade trigger
  • Low marginal cost

Free Trial Works When

  • Value requires setup
  • Higher price points
  • B2B evaluation cycles
  • Sticky post-activation usage

Hybrid Models

  • Reverse trials
  • Feature-limited free + premium trial

9. Price Increases

Signals It’s Time

  • Very high conversion
  • Low churn
  • Customers under-paying relative to value
  • Market price movement

Increase Strategies

  1. New customers only
  2. Delayed increase for existing
  3. Value-tied increase
  4. Full plan restructure

10. Pricing Page Alignment (Strategy Only)

This skill defines what pricing should be. Execution belongs to page-cro.

Strategic requirements:

  • Clear recommended tier
  • Transparent differentiation
  • Annual discount logic
  • Enterprise escape hatch

11. Price Testing (Safe Methods)

Preferred:

  • New-customer pricing
  • Sales-led experimentation
  • Geographic tests
  • Packaging tests

Avoid:

  • Blind A/B price tests on same page
  • Surprise customer discovery

12. Enterprise Pricing

When to Introduce

  • Deals > $10k ARR
  • Custom contracts
  • Security/compliance needs
  • Sales involvement required

Common Structures

  • Volume-discounted per seat
  • Platform fee + usage
  • Outcome-based pricing

13. Output Expectations

This skill produces:

Pricing Strategy Document

  • Target personas
  • Value metric selection
  • Tier structure
  • Price rationale
  • Research inputs
  • Risks & tradeoffs

Change Recommendation (If Applicable)

  • Who is affected
  • Expected impact
  • Rollout plan
  • Measurement plan

14. Validation Checklist

  • [ ] Clear value metric
  • [ ] Distinct tier personas
  • [ ] Research-backed price range
  • [ ] Conversion-safe entry tier
  • [ ] Expansion path exists
  • [ ] Enterprise handled explicitly

Related Skills

page-cro – Pricing page conversion

copywriting – Pricing copy

analytics-tracking – Measure impact

ab-test-setup – Safe experimentation

marketing-psychology – Behavioral pricing effects

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1