跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

pricing-strategy

SaaS pricing design and optimization covering value metric selection, tier architecture, price point research, pricing page design, price increase execution, and competitive pricing analysis.

文档与办公883business-growth/pricing-strategy/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/borghei/claude-skills/pricing-strategy/install.md ,按里面的步骤帮我安装这个 Skill。

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.

Core Capabilities

  • Three pricing axes (in order) — lock the value metric (how it scales), then packaging (what's in each tier), then test the price point (the number). Most teams skip to price point; that is backwards.
  • Value metric & tier design — select a metric that scales with customer value and is hard to game; architect Good-Better-Best tiers with deliberate feature allocation and naming.
  • Value-based pricing — price inside the corridor (above the next-best alternative, below perceived value), at 10-20% of documented value delivered.
  • Pricing research — Van Westendorp, MaxDiff, competitor benchmarking, willingness-to-pay interviews.
  • Pricing page, price increases & competition — page design (above/below fold, annual toggle), price-increase playbook (strategy, timeline, comms, impact), competitive positioning and health diagnostics.

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

Clarify First

Before designing the pricing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Operating mode — design from scratch, optimize existing, or price increase (each has a different validation gate and workflow)
  • Value metric — how price scales (seats, usage, etc.) (must be locked before tiers and price points)
  • Current pricing + the symptom — existing tiers and the specific failure, e.g. "middle tier too narrow" (optimize mode needs a named failure mode before any change)
  • Target segment + willingness-to-pay — SMB vs enterprise price sensitivity (sets the value corridor and price points)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the deliverable.

Operating Modes

  • Mode 1 — Design From Scratch: No pricing exists or full rebuild needed. Work value metric → tier structure → price points → page design. Validate: value metric chosen before tier design; tiers 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 flat, or customers feel mispriced. Audit, benchmark, find specific improvements. Validate: the diagnosis names a specific failure mode (e.g., "middle tier too narrow") before any change is proposed.
  • Mode 3 — Price Increase: Prices need to go up without burning relationships. Validate: grandfather policy defined, communication window set (90+ days for annual customers), and expected churn modeled before the first notice.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/pricing-models.md — the three pricing axes, value metric selection (table, criteria, red flags), tier architecture (Good-Better-Best, feature allocation, naming), and value-based pricing corridor. Read when designing or restructuring pricing.
  • references/research-and-page-design.md — Van Westendorp, MaxDiff, competitor benchmarking, WTP interviews, pricing page design, and the freemium vs free trial decision. Read when researching willingness-to-pay or designing the page.
  • references/price-increase-and-competitive.md — price increase strategy/timeline/comms/impact, competitive position map and positioning strategy, and pricing health signals. Read when raising prices or positioning against competitors.
  • references/tools-and-diagnostics.md — output artifacts, the three Python scripts (analyzer, sensitivity calculator, increase modeler), troubleshooting table, success criteria, and anti-patterns. Read when producing deliverables, running tools, or debugging a pricing problem.

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
  • 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.

相似的 Skill

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

文档与办公

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

文档与办公

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

文档与办公

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

文档与办公

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

文档与办公

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

文档与办公