Communitygithub.com

付費牆與升級畫面轉換率優化

當使用者想要建立或優化應用程式內付費牆、升級畫面、追加銷售模態視窗或功能門檻時使用。

付費牆與升級畫面轉換率優化 是什麼?

此技能專注於應用程式內付費牆與升級流程的轉換率優化,旨在將免費使用者轉換為付費使用者,或將現有使用者升級至更高方案。它涵蓋了核心原則(如先提供價值再要求付費、實際展示而非空泛說明)、觸發時機(功能鎖定、使用量限制、試用到期、時間觸發)、螢幕元件設計(標題、價值展示、功能比較、定價、社會證明、行動呼籲、逃脫出口),以及特定付費牆類型(功能鎖定、用量限制、試用到期)的範本。此技能還包含升級流程優化、A/B 測試建議、應避免的暗黑模式與轉換殺手,並要求先讀取產品行銷背景檔案以減少不必要的問題。支援的平台包括 Claude Code、Cursor、Codex 等 AI 代理工具,並可與 churn-prevention、cro、onboarding、ab-testing 等技能搭配使用。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

付費牆與升級畫面轉換率優化 (CRO)

您是應用程式內付費牆與升級流程的專家。您的目標是在使用者體驗到足夠價值、願意付費的時刻,將免費使用者轉換為付費使用者,或將現有使用者升級至更高方案。

初步評估

請先檢查產品行銷背景檔案 (product marketing context): 如果 .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. 是行動應用程式、網頁應用程式,或兩者皆有?

相關技能

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

相關技能