agentleFS
KeremozdemirraKeremozdemirra/strategy-agent/skills/offer-design/SKILL.md

offer-design

Skill0 starsChanged 3 months agoMITView on GitHub

Design, construct, or improve an offer — the thing you actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Use for \"offer design,\" \"irresistible offer,\" \"value stack,\" \"guarantee,\" \"risk reversal,\" \"productize a service,\" \"high-ticket offer,\" or \"why isn't my offer converting.\" Türkçe isteklerde de tetiklen: \"teklifimi kurgula\", \"bu teklifi nasıl paketlerim\", \"fiyat paketi tasarla\", \"garanti nasıl olsun\", \"teklifim neden satmıyor\". Best for services, agencies, courses, coaching, info products, and high-ticket B2B. Not for writing the page or email copy that sells the offer; use copywriting or cold-email for that.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Infinite-Labs-AI/infinite-skills★ 43same name
    2. 808enzo/chappie★ 3same name
    3. moronireis/agent-system-partners★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 58
  2. Distinctive:

    When drafting offer language, avoid:

    line 81
  3. Distinctive:

    Use specific numbers, named customers, concrete outcomes, real timelines.

    line 89

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Offer Design

Help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.

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.

When this matters most

Services (consulting, freelance, agency retainers, productized services) · courses (async, cohort, live) · coaching (1:1, group, mastermind) · info products (guides, templates, communities) · high-ticket B2B ($5K+ ACV with a sales conversation) · direct response (e-com promos, VSL funnels).

When pricing structure does more work

Self-serve SaaS with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; bonuses and guarantees are secondary. Marketplaces — the offer is structural, not constructed. In those cases use the value-equation framing below, then focus on pricing.

The value equation

The single most useful frame for offer design (originally from Alex Hormozi's $100M Offers):

              Dream Outcome  ×  Perceived Likelihood of Achievement
  Value  =  ─────────────────────────────────────────────────────────
              Time Delay     ×   Effort & Sacrifice
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 beyond moneyDone-for-you, simpler process, fewer decisions, lower learning curve

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

Anatomy of a complete offer

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 cringe-aggressive offers fail on guarantee (over-promising) or scarcity (fake countdown timers).

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 scattered across 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. Usually the one scoring lowest.
  6. Draft the changed component — new bonus, guarantee, scarcity, name, or 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 tactics

Some 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.
  • Over-promising guarantees — "double your revenue or refund + $1,000." Refund risk eats margin; public failures nuke reputation.
  • Bonus inflation — stacking $50K of "bonuses" on a $497 product. Sophisticated buyers see this. Bonuses are additive, not exaggerated.
  • Course-bro aesthetic on a serious product — gold logos, "secret method," fake urgency. Pattern-matches to scam.

Opinionated, but honest. Building offers well doesn't mean building offers loud.

Banned vocabulary

When drafting offer language, avoid:

  • "Game-changing," "revolutionary," "disruptive," "next-level," "10x" — pattern-matches to AI slop
  • "Secret," "hidden," "what they don't want you to know" — clickbait
  • "Limited time" with no actual time limit — lying
  • "Worth $X" / "$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.


Derived from github.com/coreyhaines31/marketingskills, MIT licence, Copyright (c) 2025 Corey Haines. See THIRD-PARTY-NOTICES.md at the repository root.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.