Offer Design
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add offersWho is stuck, and on what
People check out what I'm selling and just don't buy, even though it's genuinely good. I keep rewriting the words on my page but nothing actually moves.
What it gives you
A reworked offer with a clear name, one or two real bonuses, a fair guarantee, an honest reason to act now, and a suggested price with a payment option.
When NOT to use it
It won't write your full sales page or run your ads — it improves the deal itself, not the marketing wrapped around it.
The whole source
Frontmatter — 3 properties
| name | offers |
|---|---|
| description | 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. |
| metadata | version: 1.0.1 |
| 1 | --- |
| 2 | name: offers |
| 3 | description: "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."B1 — Line is 984 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 1.0.1 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Offer Design |
| 9 | |
| 10 | 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. |
| 11 | |
| 12 | ## Before Starting |
| 13 | |
| 14 | **Check for product marketing context first:** |
| 15 | 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. |
| 16 | |
| 17 | --- |
| 18 | |
| 19 | ## Core Philosophy |
| 20 | |
| 21 | **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. |
| 22 | |
| 23 | 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?** |
| 24 | |
| 25 | ### When this skill matters |
| 26 | |
| 27 | You sell: |
| 28 | - **Services** — consulting, freelance, agency retainers, productized services |
| 29 | - **Courses** — async, cohort-based, live |
| 30 | - **Coaching** — 1:1, group, mastermind |
| 31 | - **Info products** — guides, swipe files, templates, communities |
| 32 | - **High-ticket B2B** — $5K+ ACV with a sales conversation |
| 33 | - **Direct-response** — e-com promo offers, infomercial-style, paid-traffic-to-VSL |
| 34 | |
| 35 | ### When `pricing` does more of the work |
| 36 | |
| 37 | You sell: |
| 38 | - **Self-serve SaaS** with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary |
| 39 | - **Marketplaces** — the offer is structural, not constructed |
| 40 | |
| 41 | Skim this skill in those cases for the value equation framing, then go to `pricing`. |
| 42 | |
| 43 | --- |
| 44 | |
| 45 | ## The Value Equation |
| 46 | |
| 47 | 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. |
| 48 | |
| 49 | ``` |
| 50 | Dream Outcome × Perceived Likelihood of Achievement |
| 51 | Value = ───────────────────────────────────────────────────────── |
| 52 | Time Delay × Effort & Sacrifice |
| 53 | ``` |
| 54 | |
| 55 | You move the four levers like this: |
| 56 | |
| 57 | | Lever | What it means | How to increase value | |
| 58 | |-------|---------------|-----------------------| |
| 59 | | **Dream outcome** ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. | |
| 60 | | **Perceived likelihood** ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity | |
| 61 | | **Time delay** ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline | |
| 62 | | **Effort & sacrifice** ↓ | What it costs them in time/work/risk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve | |
| 63 | |
| 64 | **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. |
| 65 | |
| 66 | **For the full framework, examples, and how to diagnose which lever is broken:** see [references/value-equation.md](references/value-equation.md) |
| 67 | |
| 68 | --- |
| 69 | |
| 70 | ## The Anatomy of a Complete Offer |
| 71 | |
| 72 | A complete offer has six components. Skip any one and conversion suffers. |
| 73 | |
| 74 | | # | Component | Question it answers | |
| 75 | |---|-----------|---------------------| |
| 76 | | 1 | **Core deliverable** | What do they get? | |
| 77 | | 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? | |
| 78 | | 3 | **Guarantee** | What happens if it doesn't work? | |
| 79 | | 4 | **Scarcity / urgency** | Why now, not later? | |
| 80 | | 5 | **Name** | What is this thing called? | |
| 81 | | 6 | **Price + payment structure** | What do they pay and how? | |
| 82 | |
| 83 | 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). |
| 84 | |
| 85 | **For the full anatomy with worked examples:** see [references/offer-anatomy.md](references/offer-anatomy.md) |
| 86 | |
| 87 | --- |
| 88 | |
| 89 | ## Reference Library |
| 90 | |
| 91 | | Reference | When to read | |
| 92 | |-----------|--------------| |
| 93 | | [value-equation.md](references/value-equation.md) | Diagnosing which lever is broken on a stuck offer | |
| 94 | | [offer-anatomy.md](references/offer-anatomy.md) | Building a complete offer from scratch | |
| 95 | | [guarantee-design.md](references/guarantee-design.md) | Picking the right type of guarantee for your business model | |
| 96 | | [bonus-stacking.md](references/bonus-stacking.md) | Adding bonuses that raise perceived value without devaluing the core | |
| 97 | | [scarcity-urgency.md](references/scarcity-urgency.md) | Creating *real* scarcity (and avoiding the fake patterns that destroy trust) | |
| 98 | | [offer-formats.md](references/offer-formats.md) | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B | |
| 99 | | [saas-offers.md](references/saas-offers.md) | SaaS specifically — the discount trap (why discounting to acquire backfires) + four SaaS worked offers (AudienceTap, SaberSim, Teachable, Kit) | |
| 100 | | [examples.md](references/examples.md) | Anonymized worked examples — before/after for each business type | |
| 101 | |
| 102 | --- |
| 103 | |
| 104 | ## The Diagnostic Loop |
| 105 | |
| 106 | When the user says "my offer isn't converting" or "I want to improve my offer": |
| 107 | |
| 108 | 1. **Identify the business type** — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific. |
| 109 | 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. |
| 110 | 3. **Run the value equation** — score each of the four levers 1–10. The lowest is the binding constraint. |
| 111 | 4. **Audit the anatomy** — which of the six components is missing or weak? |
| 112 | 5. **Pick one lever to fix this iteration** — don't rebuild everything. The biggest lever is usually the one currently scoring lowest. |
| 113 | 6. **Draft the changed component** — new bonus, new guarantee, new scarcity, new name, new payment plan |
| 114 | 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. |
| 115 | |
| 116 | --- |
| 117 | |
| 118 | ## When NOT to Use Offer-Design Tactics |
| 119 | |
| 120 | Some offer patterns work but cost more than they're worth: |
| 121 | |
| 122 | - **Manipulative scarcity** — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't. |
| 123 | - **Over-promising guarantees** — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly. |
| 124 | - **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. |
| 125 | - **Course-bro aesthetic on a serious product** — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room. |
| 126 | - **Discounting to acquire** — discount-*askers* churn at ~2× the rate of full-price customers, and a coupon anchors the product as cheap. Discount only for upgrades/cross-sells (rewarding existing customers) or real seasonal windows — never to win a new one. Raise value with an offer instead. See [saas-offers.md](references/saas-offers.md). |
| 127 | |
| 128 | The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud. |
| 129 | |
| 130 | --- |
| 131 | |
| 132 | ## Banned Vocabulary |
| 133 | |
| 134 | When drafting offer language (sales pages, emails, headlines), avoid: |
| 135 | |
| 136 | - **"Game-changing," "revolutionary," "disruptive," "next-level," "10x"** — pattern-matches to AI slop / course-bro |
| 137 | - **"Secret," "hidden," "what they don't want you to know"** — clickbait |
| 138 | - **"Limited time" with no actual time limit** — lying |
| 139 | - **"Worth $X" or "$Y value" with no comparable** — inflation |
| 140 | - **"100% guaranteed" without specifying conditions** — legally and brand-wise risky |
| 141 | |
| 142 | Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives. |
| 143 | |
| 144 | --- |
| 145 | |
| 146 | ## Related Skills |
| 147 | |
| 148 | - **pricing** — for price levels, tier structure, value metric, packaging, freemium |
| 149 | - **copywriting** — for the page that presents the offer |
| 150 | - **cro** — for optimizing the conversion path the offer travels through |
| 151 | - **launch** — for the moment you ship the offer |
| 152 | - **paywalls** — for in-app upgrade-prompt versions of an offer |
| 153 | - **sales-enablement** — for the deck and one-pager that carry the offer into a sales conversation |
| 154 | - **emails** — for the email sequence that warms up the offer |
| 155 | - **marketing-psychology** — for the cognitive biases that make offers land or bounce |
| 156 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.●····●37/40Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.●····●35/40