本文へ移動
cccskills
無料GitHub で公開

offers

When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

インストール方法を見る

含まれるファイル(8)

  • SKILL.md9.2 KB
  • references/bonus-stacking.md7.6 KB
  • references/examples.md10.0 KB
  • references/guarantee-design.md8.0 KB
  • references/offer-anatomy.md8.6 KB
  • references/offer-formats.md10.3 KB
  • references/scarcity-urgency.md6.9 KB
  • references/value-equation.md7.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Offer Design

You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The offer is the thing, not the page. Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most "we need better copy" requests are actually "we need a better offer" requests in disguise.

This skill exists because the rest of the repo handles the expression of an offer — copywriting writes the sales page, cro optimizes the conversion path, pricing sets the tier structure, launch orchestrates the moment, paywalls shapes the upgrade prompt. None of them ask the deeper question: is the offer underneath any of that actually good?

When this skill matters

You sell:

  • Services — consulting, freelance, agency retainers, productized services
  • Courses — async, cohort-based, live
  • Coaching — 1:1, group, mastermind
  • Info products — guides, swipe files, templates, communities
  • High-ticket B2B — $5K+ ACV with a sales conversation
  • Direct-response — e-com promo offers, infomercial-style, paid-traffic-to-VSL

When pricing does more of the work

You sell:

  • Self-serve SaaS with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary
  • Marketplaces — the offer is structural, not constructed

Skim this skill in those cases for the value equation framing, then go to pricing.


The Value Equation

The single most useful frame for offer design. Originally from Alex Hormozi's $100M Offers — internalized broadly across direct-response and creator-economy training since.

              Dream Outcome  ×  Perceived Likelihood of Achievement
  Value  =  ─────────────────────────────────────────────────────────
              Time Delay     ×   Effort & Sacrifice

You move the four levers like this:

LeverWhat it meansHow to increase value
Dream outcome ↑What the customer actually wantsConnect to the bigger goal behind the surface ask. Specify and name it.
Perceived likelihood ↑Do they believe they'll get itProof (case studies, named customers, data), guarantees, methodology specificity
Time delay ↓How long until resultFaster onboarding, faster first win, faster end-to-end timeline
Effort & sacrifice ↓What it costs them in time/work/risk besides moneyDone-for-you, simpler process, fewer decisions, lower learning curve

Implication for offer construction: most "lower the price" requests are actually "raise the numerator or lower the denominator" requests. Price is the comparison, not the value.

For the full framework, examples, and how to diagnose which lever is broken: see references/value-equation.md


The Anatomy of a Complete Offer

A complete offer has six components. Skip any one and conversion suffers.

#ComponentQuestion it answers
1Core deliverableWhat do they get?
2Bonus stackWhat else do they get that makes the core feel undervalued?
3GuaranteeWhat happens if it doesn't work?
4Scarcity / urgencyWhy now, not later?
5NameWhat is this thing called?
6Price + payment structureWhat do they pay and how?

Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).

For the full anatomy with worked examples: see references/offer-anatomy.md


Reference Library

ReferenceWhen to read
value-equation.mdDiagnosing which lever is broken on a stuck offer
offer-anatomy.mdBuilding a complete offer from scratch
guarantee-design.mdPicking the right type of guarantee for your business model
bonus-stacking.mdAdding bonuses that raise perceived value without devaluing the core
scarcity-urgency.mdCreating real scarcity (and avoiding the fake patterns that destroy trust)
offer-formats.mdFormat playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B
examples.mdAnonymized worked examples — before/after for each business type

The Diagnostic Loop

When the user says "my offer isn't converting" or "I want to improve my offer":

  1. Identify the business type — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
  2. State the current offer in plain language — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.
  3. Run the value equation — score each of the four levers 1–10. The lowest is the binding constraint.
  4. Audit the anatomy — which of the six components is missing or weak?
  5. Pick one lever to fix this iteration — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
  6. Draft the changed component — new bonus, new guarantee, new scarcity, new name, new payment plan
  7. Project the lift, honestly — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.

When NOT to Use Offer-Design Tactics

Some offer patterns work but cost more than they're worth:

  • Manipulative scarcity — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't.
  • Over-promising guarantees — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly.
  • Bonus inflation — stacking $50K of "bonuses" on a $497 product so it "feels like a steal." Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.
  • Course-bro aesthetic on a serious product — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room.

The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.


Banned Vocabulary

When drafting offer language (sales pages, emails, headlines), avoid:

  • "Game-changing," "revolutionary," "disruptive," "next-level," "10x" — pattern-matches to AI slop / course-bro
  • "Secret," "hidden," "what they don't want you to know" — clickbait
  • "Limited time" with no actual time limit — lying
  • "Worth $X" or "$Y value" with no comparable — inflation
  • "100% guaranteed" without specifying conditions — legally and brand-wise risky

Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.


Related Skills

  • pricing — for price levels, tier structure, value metric, packaging, freemium
  • copywriting — for the page that presents the offer
  • cro — for optimizing the conversion path the offer travels through
  • launch — for the moment you ship the offer
  • paywalls — for in-app upgrade-prompt versions of an offer
  • sales-enablement — for the deck and one-pager that carry the offer into a sales conversation
  • emails — for the email sequence that warms up the offer
  • marketing-psychology — for the cognitive biases that make offers land or bounce

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

analytics

無料

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," "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 choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

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 "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

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 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

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: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."

日本語の概要は準備中です。原文の説明を表示しています。

Nexus-JPF/note-companion8702026年10月12日 更新

Nexus-JPF のスキルをすべて見る

このスキルの問題を報告する