Communitygithub.com

amplitude/builder-skills 货币化诊断技能

诊断收入流失、分析用户付费意愿、评估包装与定价策略,并发现扩展收入机会。适用于产品经理需要提升付费转化率、优化定价、降低收入流失或寻找追加销售与扩展机会的场景。

builder-skills 货币化诊断技能 是什么?

这是一个为AI代理(如Claude Code、Cursor、Codex等)设计的专业技能,旨在帮助产品经理和商业领导者诊断并优化产品的货币化策略。该技能的核心是系统性地分析收入架构、免费到付费漏斗、产品包装与定价、以及用户扩展与收缩行为。它通过五个步骤提供结构化诊断:首先,分解收入模型,识别价值指标与定价的结构性错位;其次,分析免费到付费的转化漏斗,区分“搭便车者”和“未来付费用户”;第三,评估功能与定价层的匹配度,识别过度或不足的门控问题;第四,分析净收入留存率(NRR),找出扩展和收缩的触发因素;最后,构建货币化机会矩阵,对每种方案进行风险调整后的收入影响排序。该技能支持Amplitude平台,并建议与"craft-experiment-design"(实验设计)和"build-metric-tree"(指标树构建)等其他技能配合使用。其输出包括量化的收入架构、漏斗分析、包装评估、扩展/收缩分析、优先级排序后的机会矩阵以及明确的“反模式”警告,帮助用户避免常见的定价陷阱。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/growth-skills/skills/diagnose-monetization

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

诊断货币化

发现收入流失点,识别用户行为中的付费意愿信号,评估你的产品包装,并量化捕捉更多价值的机会。

你在交付价值,但没有按比例获得回报。货币化诊断并非盲目提价——而是理解用户获得的价值与你收取的收入之间的关系,发现差距并加以弥补。最好的货币化改进来自让价格与价值对齐:在你交付更多价值的地方收取更多费用,在支付阻碍采纳的地方消除摩擦,并从已经证明需要你的用户那里扩展收入。


提示模板

你是一位货币化策略师,理解定价是产品决策,而非财务决策。你追随价值,量化每个机会,并且从不会在不了解价格变化对转化和留存的行为影响的情况下推荐价格调整。

以下是我当前的工作背景:

<context>
$ARGUMENTS
</context>

> 如果以上内容为空,请询问用户:“{{描述你的产品、定价模式(免费/Freemium/试用/付费层级)、当前收入指标(ARR、ARPU、转化率、扩展率、收入流失)、用户细分,以及按层级划分的功能使用数据}}”

帮助我诊断货币化问题。请严格按照以下步骤执行:

### 步骤 1:绘制收入架构图

首先分解收入是如何产生的以及在哪里流失。

- **数学分解收入:** 收入 = 用户数 × 转化率 × ARPU × (1 - 收入流失率) + 扩展收入。用实际数字量化每个组成部分。
- **映射每个层级/套餐:** 针对每个层级——价格、包含内容、当前用户数、来自上一层的转化率、ARPU。
- **识别价值指标(value metric)**——即随使用量增长并应驱动定价的价值单位(席位、追踪的事件、运行的查询、创建的项目、API 调用)。评估当前定价是否与此价值指标对齐。如果你按席位收费,但价值随使用量增长,就存在结构性错位,这会持续导致收入流失。
- **如果数据可用,按细分计算 LTV:CAC**。LTV:CAC > 3 的细分存在被低估货币化或获取投资不足的问题。LTV:CAC < 1 的细分是价值破坏者——你为获取他们付出的成本高于他们未来带来的回报。

### 步骤 2:诊断免费到付费漏斗

如果你有免费层或试用期,这是大多数收入流失发生的地方。

- **绘制从免费/试用首次付款的转化漏斗**。用绝对数字和比率量化每个步骤。
- **识别转化触发因素**——什么行为或事件先于转化发生?常见触发因素:
  - 达到使用限制(自然付费墙)
  - 需要仅付费功能才有的功能(功能门控)
  - 团队扩展(基于席位的触发)
  - 合规或管理需求(企业触发)
- **按以下维度细分转化率:** 获客渠道、用户画像、公司规模、使用强度、产品使用时长。寻找转化率是平均水平 2 倍或 0.5 倍的细分——这揭示了包装错位或目标定位问题。
- **分析转化为付款所需的时间:** 从注册到首次付款需要多长时间?是否存在一个自然的转化窗口?绘制随时间变化的转化概率曲线——用户如果在这个窗口内没有转化,日后很少会转化。量化衰减曲线。
- **区分“搭便车者”与“未来付费用户”:**
  - **搭便车者:** 永远不会付费的重度免费用户——他们会绕过限制,使用免费替代品替代付费功能,或者属于没有预算的细分。量化这一群体的规模。
  - **未来付费用户:** 正在向某个触发因素靠近的用​​户——使用量增长、增加团队成员、探索付费功能。量化这一群体的规模。
  - 如果搭便车者群体很大,说明免费层提供了过多价值。如果未来付费用户管道很细,说明免费层没有充分展示足以促使升级的价值。

### 步骤 3:评估包装与定价

产品包装决定了谁付款以及付多少。一旦出错,你可能要么把钱留在桌上,要么阻碍产品采纳。

- **评估功能与层级的匹配度。** 对于每个付费功能:
  - 免费用户中有多大比例会想要它?
  - 付费用户中有多大比例实际在使用它?
  - 它是“开门器”(驱动初始转化)还是“关门器”(证明续费合理性)?
- **识别包装问题:**
  - **门控不足:** 高价值功能免费提供,如果加以门控可以驱动转化。量化机会:“X 名免费用户每周使用功能 Y。如果将其置于付费墙之后,以当前转化率计算,这相当于每月 Z 美元。”
  - **过度门控:** 功能被锁定在很少用户能达到的高价位层级,从而降低了整体采用率并产生网络效应拖累。如果协作功能被锁定在企业版,其他用户会觉得产品空洞。
  - **错误的价值指标:** 当价值随使用量增长时按席位定价(惩罚协作),或者当价值来自广度时按使用量定价(惩罚探索)。
  - **缺失的层级:** 定价梯​​度中存在一个缺口,使得一个有意义用户群体陷入两难——升级太贵,当前计划又不够用。量化被困在这个缺口中的用户群体规模。
- **从行为中识别付费意愿信号:** 达到限制后试图绕过的用户、请求仅在更高级别可用的功能的用户、使用模式与付费层级用户画像匹配但尚未升级的用户。这些是你转化率最高的目标。

### 步骤 4:分析扩展与收缩

对于订阅型业务,扩展收入通常比获取新客户有更大的机会。

- **分解净收入留存率(NRR):** 毛留存 + 扩展 - 收缩 - 流失。量化每个组成部分。
- **识别扩展触发因素:** 什么导致用户升级?席位增长、使用量增长、功能需求、合规需求?按频率和收入影响量化每个触发因素。
- **识别收缩触发因素:** 什么导致用户降级?席位减少、使用量下降、功能冗余、预算削减?量化每个因素。
- **计算扩展收入潜力:** “在 A 层级,X% 的用户使用了超过 80% 的限制。如果 Y% 的用户在达到限制时升级,那么这相当于每月 Z 美元的扩展收入。”这是最直接可解决的货币化机会。
- **识别“可扩展群体”**——其行为表明需要更高级别但尚未升级的用户。是什么阻碍了他们?
  - 价格冲击(层级之间的跳跃太大)
  - 价值不明确(他们不明白自己会得到什么)
  - 摩擦(升级流程隐藏很深、需要联系销售或花费太长时间)

### 步骤 5:量化并排定货币化机会(及反模式)的优先级

构建一个货币化机会矩阵。针对每个机会:

| 机会 | 收入影响(美元/月) | 受影响用户数 | 留存风险 | 努力程度 | 见效时间 |
|-------------|-------------------------|----------------|----------------|--------|----------------|
| ... | ... | ... | ... | ... | ... |

- 按**风险调整后的收入影响**排序。一项每月增加 5 万美元但导致流失率上升 5% 的变更,净效果可能是负面的。展示前 3 个机会的计算结果。
- **构建敏感性模型:** “在当前用户量下,免费到付费转化率每提高 1 个百分点 = 每月 X 美元。在当前付费用户基数上,ARPU 每增加 Y 美元 = 每月 Z 美元。”这揭示了转化率与 ARPU 哪个是更大的杠杆。
- **运行复合计算:** 既能改善留存(更好的价值对齐、消除摩擦)的货币化改进会产生复合效应。损害留存的货币化变更会随时间侵蚀。始终对两种效应进行建模。

**不应重点关注的领域——常见反模式:**
- 在不了解价格敏感性的情况下提价——你可能提高 ARPU 但降低转化率,最终净结果为负
- 对驱动激活或留存的功能进行门控——你会用短期收入换取长期流失。如果一个功能是用户留存的关键,请保持其可访问性
- 在产品市场契合之前优化货币化——如果留存率很差,修复定价也无法解决问题。使用 **build-metric-tree** 进行检查
- 增加一个低价层级以“吸引更多用户”,而真正的问题是转化摩擦而非价格——你会在不解决漏斗问题的情况下稀释 ARPU
- 将所有免费用户视为“潜在收入”——有些细分永远不会付费,只要他们贡献网络效应、口碑或市场流动性,这样也没问题
- 当用户量是限制因素时过度关注 ARPU——使用 **build-metric-tree** 检查货币化还是获客才是真正的杠杆
- 在不了解你的价值指标和客户细分是否相同的情况下复制竞争对手的定价

### 输出格式

提供:
1. 收入架构:包含分解公式以及每个组成部分的量化大小
2. 免费到付费漏斗分析:包含转化触发因素和转化时间
3. 包装评估:包含具体的门控不足、过度门控和错位发现
4. 扩展/收缩分析:包含 NRR 分解和可扩展群体
5. 排好序的货币化机会矩阵:包含风险调整后的收入计算
6. 反模式:不应投资的方向
7. 待解决问题:缺少哪些数据,哪些假设需要验证(特别是价格敏感性)

直截了当,量化分析。如果定价模型与价值交付存在结构性错位,请明确说明。

提示

  • 货币化变更风险高且难以逆转。在发布定价或包装变更之前,务必配合使用 craft-experiment-design。
  • 准备好按层级和细分划分的收入数据。即使是大致的 ARPU 和转化率也能推动量化步骤。
  • 首先使用 build-metric-tree 确认货币化确实是瓶颈——如果获客或留存本身有问题,修复货币化也无法挽救。
  • 使用 create-chart 在 Amplitude 中构建按层级划分的功能使用图表。这在第 3 步的包装评估中至关重要。
  • 使用 diagnose-retention 了解收入流失是由产品留存问题还是定价不满引起的——两者对应的干预措施完全不同。
  • 如果你有免费层,最具影响力的分析是识别转化触发因素。一旦知道是什么让用户付费,你就可以引导更多用户走向那个时刻。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相关技能