Offers
Corey HainesCommunityCreated by Corey Haines
- Skill
- Guidelines
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to offer design, emphasizing that conversion issues are often rooted in the offer itself rather than the copy. It utilizes the Value Equation—Dream Outcome, Perceived Likelihood, Time Delay, and Effort & Sacrifice—to diagnose and improve the core components of an offer. The framework guides users through auditing their current offer, identifying the weakest lever, and systematically adding components like bonuses, guarantees, and scarcity to increase perceived value and conversion rates.
What it does
- Diagnoses the binding constraints of an existing offer using the Value Equation.
- Provides a six-part anatomy for building complete, high-converting offers.
- Offers strategies for designing effective guarantees and risk-reversal mechanisms.
- Guides the creation of bonus stacks that address specific customer objections.
- Helps structure pricing and payment plans to maximize conversion.
- Identifies when to use offer-design tactics versus pricing or copywriting strategies.
When to use it
- When an existing offer is failing to convert despite having decent traffic.
- When you need to build a new offer for services, courses, coaching, or high-ticket B2B.
- When you want to increase the perceived value of your product without simply lowering the price.
- When you need to address specific customer objections through strategic bonus stacking.
- When you are transitioning from selling time to selling productized services or outcomes.
Advantages
- Focuses on the structural integrity of the offer rather than just surface-level copy.
- Provides a clear, actionable diagnostic loop to identify the biggest lever for improvement.
- Uses a proven, logic-based framework to increase value perception.
- Helps avoid common pitfalls like manipulative scarcity or over-promising guarantees.
- Standardizes the components of an offer to ensure nothing critical is missing.
Usage examples
- “My agency retainer isn't converting. How do I improve the offer?”
- The agent will guide you through identifying your business type, scoring your current offer against the Value Equation, and pinpointing which of the six offer components is missing or weak.
- “How can I add bonuses to my course without making it look like cheap padding?”
- The agent will help you design a bonus stack where each item specifically targets a known customer objection, such as lack of time or fear of getting stuck.
- “I want to offer a guarantee for my coaching program but I'm afraid of refunds.”
- The agent will help you design a conditional guarantee that provides risk reversal for the client while protecting your business model and reputation.
- “Why is my high-ticket B2B offer not getting any bites?”
- The agent will audit your offer's anatomy, likely focusing on whether your dream outcome is clearly defined and if your perceived likelihood of achievement is supported by sufficient proof.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/coreyhaines31/offers/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip offers.zip -d .agents/skills
Documentation by Corey Haines
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 & SacrificeYou move the four levers like this:
| Lever | What it means | How to increase value |
|---|---|---|
| Dream outcome ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |
| Perceived likelihood ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |
| Time delay ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |
| Effort & sacrifice ↓ | What it costs them in time/work/risk besides money | Done-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.
| # | Component | Question it answers |
|---|---|---|
| 1 | Core deliverable | What do they get? |
| 2 | Bonus stack | What else do they get that makes the core feel undervalued? |
| 3 | Guarantee | What happens if it doesn't work? |
| 4 | Scarcity / urgency | Why now, not later? |
| 5 | Name | What is this thing called? |
| 6 | Price + payment structure | What 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
| Reference | When to read |
|---|---|
| value-equation.md | Diagnosing which lever is broken on a stuck offer |
| offer-anatomy.md | Building a complete offer from scratch |
| guarantee-design.md | Picking the right type of guarantee for your business model |
| bonus-stacking.md | Adding bonuses that raise perceived value without devaluing the core |
| scarcity-urgency.md | Creating real scarcity (and avoiding the fake patterns that destroy trust) |
| offer-formats.md | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |
| saas-offers.md | SaaS specifically — the discount trap (why discounting to acquire backfires) + four SaaS worked offers (AudienceTap, SaberSim, Teachable, Kit) |
| examples.md | Anonymized 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":
Identify the business type — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
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.
Run the value equation — score each of the four levers 1–10. The lowest is the binding constraint.
Audit the anatomy — which of the six components is missing or weak?
Pick one lever to fix this iteration — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
Draft the changed component — new bonus, new guarantee, new scarcity, new name, new payment plan
Project the lift, honestly — plan on 10–40% relative lift from one component change. Multiply the lifts, don't add them: +20% then +30% =
1.20 × 1.30 = 1.56(2% → 3.12%, +1.12 percentage points). Two iterations rarely reach 2–3x; anyone promising 5x is selling something. Confirm the combined offer with a test (see ab-testing).
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.
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.
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
Files
- ATTRIBUTION.mdAdded by AutoGineer873 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md9.9 KiB
- evals/evals.json3.1 KiB
- references/bonus-stacking.md7.6 KiB
- references/examples.md10.0 KiB
- references/guarantee-design.md8.0 KiB
- references/offer-anatomy.md8.6 KiB
- references/offer-formats.md10.4 KiB
- references/saas-offers.md7.7 KiB
- references/scarcity-urgency.md6.9 KiB
- references/value-equation.md7.7 KiB
references/offer-anatomy.md
Offer Anatomy
A complete offer has six components. Skip any one and conversion suffers — usually noticeably.
The six components
| # | Component | Question it answers | Where it fails |
|---|---|---|---|
| 1 | Core deliverable | What do they get? | Too vague, or pitched as features instead of outcome |
| 2 | Bonus stack | What else do they get that makes the core feel undervalued? | Either no bonuses, or inflated/fake bonuses |
| 3 | Guarantee | What happens if it doesn't work? | None, wrong type, or over-promising |
| 4 | Scarcity / urgency | Why now, not later? | None, fake, or destructively manipulative |
| 5 | Name | What is this thing called? | Generic, internal-jargon, or no name at all |
| 6 | Price + payment structure | What do they pay and how? | Single number with no payment flexibility |
1. Core deliverable
The thing they actually get.
Define it as an outcome, not a feature list
Feature-pitched (weak): "6 modules, 24 lessons, weekly calls, private community."
Outcome-pitched (strong): "A working customer-acquisition system that brings 5 qualified leads per week within 60 days — built with you, not handed to you."
The features still matter — buyers want to know what they're getting — but the frame is the outcome. Features support the outcome, they don't replace it.
Define the scope explicitly
What's in. What's out. What's optional. Buyers buy clarity; ambiguity erodes perceived likelihood.
Example scope statement:
Includes:
- 90-day program with weekly live calls (recorded)
- Private Slack with daily founder access
- 12 fill-in-the-blank templates
- 1 90-minute strategy session with a senior strategist
Doesn't include:
- 1:1 calls outside the strategy session
- Implementation of the work (you/your team does this; we coach)
- Tools and software (you provide; we recommend specific stacks)Match the depth to the buyer's stage of awareness
Sophisticated buyers want the methodology and scope. New-to-category buyers want the dream outcome and proof. Read your audience.
2. Bonus stack
What you add to make the core feel undervalued at the asking price.
Bonuses do three jobs at once:
Raise perceived value of the total offer
Lower perceived risk — even if the core underdelivers, "I got X for free"
Close specific objections — each bonus can target a different buying objection
How to construct bonuses
For each major objection your buyer has, add a bonus that closes it:
| Objection | Targeted bonus |
|---|---|
| "I don't have time to implement this" | Done-for-you setup, day 1 |
| "I don't know which tools to use" | Pre-vetted tool stack with discount codes |
| "What if I get stuck?" | 30-day async support |
| "I'm not sure my team will buy in" | Stakeholder pitch deck for your team |
| "I've tried something like this before and it didn't work" | Case study of someone in your exact situation |
A 4-bonus stack that closes 4 specific objections converts massively better than a 4-bonus stack of generic "extras."
Don't inflate
"$50,000 in bonuses!" on a $500 offer reads as scam. The asymmetry destroys trust.
Bonuses should:
Have a stated value the buyer can verify (compare to a comparable product)
Total to less than 2x the price (e.g., a $1K offer can have ~$1.5K in bonuses comfortably)
Be things you'd actually sell separately if you wanted
For the full bonus-stacking framework, see bonus-stacking.md.
3. Guarantee
What happens if it doesn't work.
A guarantee directly raises perceived likelihood of achievement (the buyer thinks: "they'll only offer this if they're sure"). It also lowers effort & sacrifice (less emotional risk).
The wrong guarantee can hurt:
Over-promising guarantees attract refund-seekers
Generic "100% guaranteed" with no conditions reads as legally unenforceable
No guarantee at all signals you're not confident
The right type depends on your business model, refund risk tolerance, and buyer sophistication. For the full taxonomy, see guarantee-design.md.
4. Scarcity / urgency
The reason to buy now, not later.
Two flavors:
Scarcity — limited quantity (cohort size, seats, inventory, batch)
Urgency — limited time (cohort deadline, season, bonus expiry)
The bar: the scarcity has to be real. Fake countdown timers and "only 3 spots left" lies work once and torch trust permanently. The internet is small; you will be caught.
Common honest scarcity formats:
Cohort closes Friday (because the cohort actually starts Monday)
Founding-member pricing for the first 20 customers (because you're capacity-constrained)
Seasonal product or service (because demand is seasonal)
Bonus expires at launch end (because the bonus is your time)
Capacity-based service tier (because you literally can't take more clients)
For full guidance on creating real scarcity, see scarcity-urgency.md.
5. Name
What this thing is called.
A named offer beats an unnamed offer for three reasons:
Repeatability — buyers can tell their friend about it
Distinction — a name makes it a thing, not a generic service
Pricing power — branded offers can charge more than the same delivery sold as a service
Naming patterns that work
Outcome-named: "The 30-Day Activation Sprint" — names what they get
Methodology-named: "The VAULT Framework" — names how you do it
Identity-named: "Founder Marketing OS" — names who it's for
Compression-named: "5-Day Cohort" — names the timing/structure
Naming patterns that don't work
Generic descriptors: "Marketing Coaching Program" — forgettable
Internal jargon: "Tier 2 Standard" — buyer can't repeat
Course-bro: "The Money-Making Machine" — pattern-matches to scam
Pun-overload: "GrowthGoGetter" — reads as low-status
Practical test
Can a buyer text a friend: "I just signed up for the [name]. It's $X and you get [one-line outcome]"? If yes, the name works. If no, rename.
6. Price + payment structure
The price is the obvious part. The structure is the underrated part.
Price isn't a number, it's a comparison
Buyers compare the price to:
The dream outcome (does this get me the result I want?)
The next-best alternative (what else could I buy?)
The cost of doing nothing (what does the status quo cost me?)
Other items in your own catalog (anchor pricing)
You can move price perception without changing the number by:
Showing the cost of doing nothing more vividly
Anchoring against a higher-priced alternative
Sequencing other items in your catalog at higher prices first
Payment structure is its own lever
Same total price, different structures convert very differently:
| Structure | When it works | Trade-off |
|---|---|---|
| Pay in full | High-trust buyers, lower price points | Highest perceived commitment, smallest buyer pool |
| Pay in 2-4 installments | Mid-range price, hesitant buyers | More buyers, payment defaults |
| Monthly subscription | SaaS, ongoing services | Annuity revenue, churn risk |
| Pay-after-results | High-confidence delivery, sophisticated buyers | Cash flow lag, fewer disputes |
| Down payment + balance on delivery | Services with milestone-based delivery | Balance risk on backend |
| Free trial → paid | Low-friction SaaS, info products | Conversion drop-off |
Often the right move isn't lowering price — it's adding a payment plan. Same $6K price, "$6K today" vs "$2K × 3 monthly" converts very differently.
Putting it together: an example
A B2B fractional CMO service.
| Component | Weak version | Strong version |
|---|---|---|
| Core | "Fractional CMO services" | "8-week marketing audit + 90-day execution plan, delivered by a CMO who's done it for 3+ similar companies" |
| Bonuses | None | (1) 1:1 weekly check-ins for 90 days; (2) pre-vetted execution-partner introductions; (3) board-deck for marketing strategy section |
| Guarantee | None | "If after the 8-week audit you don't have a clear 90-day plan you'd run yourself, you don't pay the audit fee" |
| Scarcity | None | "We take 2 engagements per quarter — next slot opens [date]" |
| Name | "fCMO Consulting" | "The 90-Day Marketing Reset" |
| Price | "$15K, paid up front" | "$15K → $5K to start, $5K at week 8, $5K at week 16" |
Same delivery. Same person. Different offer. Different conversion.
The point: most "we need to lower our price" conversations are actually "we have one of six components missing or weak" conversations.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Corey Haines
- Publisher
- Corey Haines (Community)
- Source
- coreyhaines31/marketingskills · skills/offers · commit 96798cf
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Corey Haines.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download offers.zip