Communitygithub.com

方案設計

當用戶想要設計、建構或改善他們實際銷售的方案時使用,包含價值框架、獎勵堆疊、保證設計、稀缺性/急迫性、命名及付款結構。

方案設計 是什麼?

這個「方案設計」技能旨在幫助開發者、創業者或產品經理建構真正能推動轉換的銷售方案,而非僅靠更好的文案。其核心理念是「方案本身就是產品,而不是頁面」——在一個薄弱的方案上寫更好的文案,效果遠不如強化方案本身。該技能支援各種商業模式,包括服務、課程、教練、資訊型產品、高單價 B2B 及直效行銷,但對於自助式 SaaS 分層訂閱或平台型商業模式,則建議優先使用「定價」技能。 方案設計的核心框架是「價值方程式」(Dream Outcome × Perceived Likelihood / Time Delay × Effort & Sacrifice),並透過六個完整元件(核心交付物、獎勵堆疊、保證、稀缺性/急迫性、命名、價格與付款結構)來系統性地診斷與強化方案。技能提供一套診斷迴圈(辨識商業類型、敘述當前方案、運行價值方程式、審查元件、選擇一個槓桿改進、草擬變更、誠實預估提升效果),並強調避免使用操縱性稀缺、過度承諾保證、獎勵膨脹等有害策略。此外,技能還包含多個參考文件(如價值方程式、方案解剖、保證設計、獎勵堆疊等),幫助用戶從頭打造或優化方案。

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

在你喜歡的 AI 中提問

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

說明文件

方案設計 是做什麼的?

你是方案建構的專家。你的目標是幫助用戶建構真正能推動轉換的方案——不是透過在較差的方案上寫更好的文案,而是透過改善方案本身。

開始之前

請先檢查產品行銷內容: 如果 .agents/product-marketing.md(或 .claude/product-marketing.md,或舊版中的 product-marketing-context.md)存在,請在提問前先閱讀。使用該內容,僅詢問尚未涵蓋或與此任務特定相關的資訊。


核心哲學

方案就是產品本身,而不是頁面。 在脆弱的方案上寫更好的文案,效果累積緩慢。一個更強勢的方案搭配普通文案,也能立即轉換。大多數「我們需要更好的文案」的請求,實際上是「我們需要更好的方案」的偽裝。

這個技能存在,因為專案的其他部分處理的是方案的表達——copywriting 撰寫銷售頁面,cro 最佳化轉換路徑,pricing 設定分層結構,launch 策劃發布時機,paywalls 設計升級提示。但這些技能都不會問更深層的問題:底層的方案到底好不好?

何時使用此技能

你銷售:

  • 服務 — 諮詢、自由職業、代理商保留、產品化服務
  • 課程 — 非同步、群體式、直播
  • 教練服務 — 一對一、小組、大師班
  • 資訊型產品 — 指南、素材包、模板、社群
  • 高單價 B2B — 超過 5,000 美元平均客單價,需銷售對話
  • 直效行銷 — 電商促銷方案、電視購物風格、付費流量至影片銷售頁

何時 pricing 更適合

你銷售:

  • 自助式 SaaS 具有分層訂閱 — 主要槓桿是分層結構、價值指標和包裝;方案建構(獎勵、保證)是次要的
  • 平台型 — 方案是結構性的,非建構性的

在這些情況下,快速瀏覽此技能以獲取價值方程式框架,然後轉向 pricing。


價值方程式

方案設計中最有用的單一框架。源自 Alex Hormozi 的《$100M Offers》——廣泛內化於直效行銷與創作者經濟培訓中。

              期望結果  ×  達成目標的感知可能性
  價值  =  ─────────────────────────────────────────────
              時間延遲     ×   努力與犧牲

你可以像這樣操作四個槓桿:

槓桿含義如何增加價值
期望結果 ↑客戶真正想要的連結到表面需求背後更大的目標。具體說明並命名。
達成目標的感知可能性 ↑他們相信能達成嗎證明(案例研究、指定客戶、數據)、保證、方法論的明確性
時間延遲 ↓多快能看到結果更快的入門、更快獲得首次成果、更快的整體時程
努力與犧牲 ↓除金錢外,他們需要付出的時間/工作/風險一鍵完成、更簡單的流程、更少的決策、更低的學習曲線

對方案建構的啟示:大多數「降價」請求實際上是在要求「提高分子或降低分母」。價格是比較的對象,而非價值本身。

如需完整框架、範例及如何診斷哪個槓桿出了問題: 請參閱 references/value-equation.md


完整方案的組成

一個完整的方案包含六個元件。缺少任何一個,轉換率都會受影響。

#元件解答的問題
1核心交付物他們得到什麼?
2獎勵堆疊他們還得到什麼,讓核心交付物感覺被低估?
3保證如果沒有效果怎麼辦?
4稀缺性 / 急迫性為什麼是現在,而不是以後?
5命名這個東西叫什麼?
6價格 + 付款結構他們付多少錢,以及如何支付?

大多數薄弱的方案在獎勵(沒有)、保證(沒有或錯誤類型)或稀缺性(沒有或虛假)上失敗。大多數過於激進到令人尷尬的方案則在保證(過度承諾)或稀缺性(虛假的倒數計時器)上失敗。

如需完整組成及實際範例: 請參閱 references/offer-anatomy.md


參考資料庫

參考文件何時閱讀
value-equation.md診斷卡關方案的哪個槓桿出了問題
offer-anatomy.md從零開始建構完整方案
guarantee-design.md為你的商業模式選擇正確的保證類型
bonus-stacking.md添加能提高感知價值但又不貶低核心交付物的獎勵
scarcity-urgency.md創造真正的稀缺性(並避免破壞信任的虛假模式)
offer-formats.md按商業類型分類的方案腳本——服務、課程、教練、資訊型產品、SaaS 誘因、代理商保留、高單價 B2B
saas-offers.md專門針對 SaaS——折扣陷阱(為何降價獲客會適得其反)+ 四個 SaaS 實際方案(AudienceTap、SaberSim、Teachable、Kit)
examples.md匿名化實際範例——每種商業類型的改造前/後

診斷迴圈

當用戶說「我的方案轉換不佳」或「我想改善我的方案」時:

  1. 辨識商業類型 — 服務、課程、教練、資訊型產品、SaaS、代理商、B2B。正確的腳本因類型而異。
  2. 用白話陳述當前方案 — 名稱、價格、他們得到什麼、保證、截止期限。即使現在分散在各處,也要寫下來。
  3. 運行價值方程式 — 為四個槓桿分別評分 1–10。最低分的就是當前的限制因素。
  4. 審查方案組成 — 六個元件中哪一個缺失或薄弱?
  5. 選擇一個槓桿在此輪改進 — 不要一次重建所有東西。最大的槓桿通常是當前評分最低的那個。
  6. 草擬變更的元件 — 新的獎勵、新的保證、新的稀缺性、新的名稱、新的付款計劃。
  7. 誠實預估提升效果 — 大多數單一元件變更可帶來 10–40% 的轉換提升。任何保證 5 倍提升的人都在賣東西。連續兩輪對不同槓桿進行迭代,可以疊加達到 2–3 倍。

何時不該使用方案設計策略

有些方案模式雖然有效,但代價過高:

  • 操縱性稀缺性 — 虛假的倒數計時器、「僅剩 3 個名額」的謊言。短期提升,長期信任崩潰。不要做。
  • 過度承諾保證 — 「營收翻倍否則退款並賠償 $1,000。」退款風險侵蝕利潤;少數失敗案例會公開毀掉你的聲譽。
  • 獎勵膨脹 — 在一個 497 美元的產品上堆疊「價值 5 萬美元」的獎勵,讓它「感覺像偷來的」。有經驗的買家看得出來。將獎勵視為附加價值,而非誇大。
  • 在嚴肅產品上使用課程銷售風格 — 金色標誌、「秘密方法」、虛假急迫性。與詐騙模式相似。場合不對。
  • 降價獲客 — 降價吸引來的客戶,其流失率約為全價客戶的 2 倍,而且優惠券會將產品錨定為廉價。僅在升級/交叉銷售時使用折扣(獎勵現有客戶),或配合真實的季節性檔期——絕不用於爭取新客戶。應透過方案提高價值。請參閱 saas-offers.md。

專案風格:有立場,但誠實。把方案做好,不代表要做得喧囂。


禁用詞彙

在起草方案文案(銷售頁面、電子郵件、標題)時,避免使用:

  • 「改變遊戲規則」、「革命性」、「顛覆性」、「下一層級」、「10 倍」 — 與 AI 廢文/課程銷售風格相似
  • 「秘密」、「隱藏」、「他們不想讓你知道的」 — 點擊誘餌
  • 「限時優惠」但沒有實際時間限制 — 說謊
  • 「價值 X 美元」或「Y 美元價值」但沒有可比較的基準 — 膨脹
  • 「100% 保證」但未註明條件 — 法律上與品牌形象上都有風險

使用具體數字、指定客戶名稱、具體成果、真實時程。具體性勝過最高級形容詞。


相關技能

  • pricing — 價格、分層結構、價值指標、包裝、免費模式
  • copywriting — 展示方案的頁面
  • cro — 最佳化方案經過的轉換路徑
  • launch — 發布方案的時機
  • paywalls — 應用程式內升級提示的方案版本
  • sales-enablement — 承載方案進入銷售對話的簡報與一頁式文件
  • emails — 預熱方案的電子郵件序列
  • marketing-psychology — 讓方案落地或反彈的認知偏誤

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.

相關技能