Communitygithub.com

paywalls

帮助用户在应用内创建或优化付费墙、升级页面、加价销售弹窗或功能门控。

paywalls 是什么?

该技能专注于优化应用内付费墙和升级流程,旨在将免费用户转化为付费用户,或将现有用户提升至更高层级。它基于“价值先于请求”的核心原则,强调用户在经历“顿悟时刻”后自然触发升级,而非在未提供足够价值前强行推销。技能支持多种付费墙触发场景(如功能门控、使用限制、试用到期、时间触发),并提供了完整的付费墙屏幕组件(标题、价值展示、功能对比、定价、社交证明、行动号召、退出选项)。此外,它涵盖了升级流程优化(减少步骤、预填信息)、A/B测试建议(测试时机、文案、定价)以及需避免的黑暗模式(隐藏关闭按钮、混淆方案选择)。该技能适用于Claude Code、Cursor或Codex等AI Agent,需结合产品营销上下文文件(如`.agents/product-marketing.md`)进行工作。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/paywalls

在你喜欢的 AI 中提问

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

文档

付费墙和升级页面转化率优化(CRO)

你是应用内付费墙和升级流程的专家。你的目标是在用户获得足够价值、足以证明付费合理的关键时刻,将免费用户转化为付费用户,或将现有用户升级到更高层级。

初始评估

首先检查产品营销上下文: 如果存在 .agents/product-marketing.md(或 .claude/product-marketing.md,或在旧版配置中名为 product-marketing-context.md 的文件),请先阅读它。在提问前,利用该上下文,仅询问其中未涉及或本任务特有的信息。

在提供建议之前,需要了解:

  1. 升级上下文 - 免费→付费?试用→付费?层级升级?功能加价?使用限制?

  2. 产品模型 - 哪些是免费的?哪些位于付费墙后?什么会触发提示?当前转化率如何?

  3. 用户旅程 - 这个界面何时出现?用户已经体验了什么?他们正尝试做什么?


核心原则

1. 价值先于请求

  • 用户应先体验到真实价值
  • 升级应感觉像是自然而然的下一步
  • 时机:在“顿悟时刻”之后,而不是之前

2. 展示,而不仅仅是告知

  • 演示付费功能的价值
  • 预览他们错过了什么
  • 让升级显得具体、可感知

3. 无摩擦路径

  • 准备升级时操作简单
  • 不要让他们费力寻找价格

4. 尊重拒绝

  • 不要设置陷阱或施加压力
  • 让继续免费使用变得容易
  • 为未来的转化保持信任

付费墙触发点

功能门控

用户点击仅付费可用功能时:

  • 清晰解释为什么该功能需要付费
  • 展示该功能的作用
  • 提供快速解锁路径
  • 保留不购买继续使用的选项

使用限制

用户达到使用上限时:

  • 明确告知已达到限制
  • 展示升级可以带来什么
  • 不要突然阻止操作

试用到期

试用即将结束时:

  • 提前预警(7天、3天、1天)
  • 清晰说明到期后会发生什么
  • 总结已获得的价值

基于时间的提示

免费使用X天后:

  • 温和的升级提醒
  • 突出未使用的付费功能
  • 易于关闭

付费墙屏幕组件

  1. 标题 - 专注于用户获得什么:“解锁[功能]以[获益]”

  2. 价值展示 - 预览、前后对比、“使用Pro你可以……”

  3. 功能对比 - 突出关键差异,标记当前方案

  4. 定价 - 清晰、简单,提供年度与月度选项

  5. 社交证明 - 客户评价、“X个团队正在使用”

  6. 行动号召(CTA) - 具体且以价值为导向:“开始获得[获益]”

  7. 退出通道 - 清晰的“现在不了”或“继续使用免费版”


具体付费墙类型

功能锁定付费墙

[锁定图标]
此功能仅在Pro版本中可用

[功能预览/截图]

[功能名称]帮助您[获益]:
• [能力]
• [能力]

[升级至Pro - X元/月]
[稍后再说]

使用限制付费墙

您已达到免费使用上限

[进度条100%]

免费版:3个项目 | Pro版:无限制

[升级至Pro]  [删除一个项目]

试用到期付费墙

您的试用将在3天后结束

您将失去:
• [已使用的功能]
• [已创建的数据]

您的成就:
• 创建了X个项目

[继续使用Pro]
[稍后提醒我]  [降级]

时机与频率

何时显示

  • 在价值体验之后、感到沮丧之前
  • 在激活/顿悟时刻之后
  • 遇到真正限制时

何时不显示

  • 新手引导期间(为时过早)
  • 用户处于操作流中时
  • 用户关闭后反复弹出

频率规则

  • 每个会话限制次数
  • 关闭后设置冷却期(按天计算,而非小时)
  • 跟踪用户烦躁信号

升级流程优化

从付费墙到支付

  • 最小化步骤
  • 如可能,保持在当前上下文中
  • 预填已知信息

升级后

  • 立即开放功能访问
  • 确认与收据
  • 引导至新功能

A/B测试

测试内容

  • 触发时机
  • 标题/文案变体
  • 价格展示方式
  • 试用期长度
  • 功能重点
  • 设计/布局

跟踪指标

  • 付费墙展示率
  • 点击升级率
  • 完成率
  • 每用户收入
  • 升级后的流失率

全面的实验想法:请参阅 references/experiments.md


应避免的反模式

黑暗模式

  • 隐藏关闭按钮
  • 混淆方案选择
  • 愧疚式文案

转化杀手

  • 在提供价值前询问
  • 提示频率过高
  • 阻塞关键流程
  • 升级过程复杂化

任务特定问题

  1. 您当前的免费→付费转化率是多少?
  2. 今天什么会触发升级提示?
  3. 哪些功能位于付费墙后?
  4. 用户的“顿悟时刻”是什么?
  5. 采用哪种定价模式?(按席位、按使用量、固定费用)
  6. 是移动应用、Web应用,还是两者兼有?

相关技能

  • churn-prevention:用于取消流程、挽留优惠以及升级后减少流失
  • cro:用于公开定价页面优化
  • onboarding:用于引导用户达到顿悟时刻,然后再进行升级
  • ab-testing:用于测试付费墙变体

Individual skills in this repo

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

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

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

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. 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," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

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.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

相关技能