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.
Overview
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 — 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.
- 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 10 files
- SKILL.mdMarkdown
- evals/evals.jsonFile
- references/bonus-stacking.mdMarkdown
- references/examples.mdMarkdown
- references/guarantee-design.mdMarkdown
- references/offer-anatomy.mdMarkdown
- references/offer-formats.mdMarkdown
- references/saas-offers.mdMarkdown
- references/scarcity-urgency.mdMarkdown
- references/value-equation.mdMarkdown
Install it by hand
Deska runs this for you, for every agent you pick. To run it yourself in a terminal:
npx skills add coreyhaines31/marketingskills --skill offersMore from coreyhaines31
- seo-auditcoreyhaines31When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.221.3K installs on skills.sh0
- copywritingcoreyhaines31When 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 "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.217.2K installs on skills.sh0
- marketing-psychologycoreyhaines31When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.153.5K installs on skills.sh0
- content-strategycoreyhaines31When 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 "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.151.7K installs on skills.sh0
- programmatic-seocoreyhaines31When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," "templated landing pages," or "which CMS for pSEO." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.140.4K installs on skills.sh0