agentleFS
moronireismoronireis/agent-system-partners/.claude/skills/offer-design/SKILL.md

offer-design

Skill0 starsChanged 2 months agoMITView on GitHub

Framework for constructing high-conversion offers — value equation, dream outcome, value stack, guarantees, ethical scarcity/urgency, pricing psychology, and naming. Use when mkt-strategist is building or refining an offer, or when any agent needs to diagnose why an existing offer isn't converting.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every offer decision should push one of these four levers: raise the dream outcome, raise perceived likelihood, shrink time to value, or …

    line 12
  2. Distinctive:

    Every scarcity claim must tie to a REAL constraint: cohort size, calendar capacity, inventory, delivery capacity.

    line 35
  3. Distinctive:

    Every urgency claim must tie to a REAL event: an enrollment close date, a price change, a bonus expiration.

    line 36
  4. Very specific:

    NEVER fabricate countdown timers, invented "X spots left" claims, or fake purchase notifications.

    line 37
  5. Distinctive:

    If no real constraint exists, don't manufacture one.

    line 38
  6. Distinctive:

    Run the Value Equation check — identify the lowest-scoring lever.

    line 86
  7. Distinctive:

    Check the guarantee — specific and provable, or vague filler?

    line 87
  8. Very specific:

    Check scarcity — real, or does it read as manufactured?

    line 88
  9. Distinctive:

    Check the price-to-stack ratio — does the stack visibly outweigh the ask?

    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

Value Equation

Value = (Dream Outcome × Perceived Likelihood of Achievement) / (Time to Value × Effort/Sacrifice)

Every offer decision should push one of these four levers: raise the dream outcome, raise perceived likelihood, shrink time to value, or shrink effort. When an offer underperforms, score each variable 1-10 — the lowest score is the lever to fix first, not the whole offer.

Dream Outcome

  • Translate vague desires into a sharp, specific, future-state scenario, in the ICP's own language (pull from mkt-research voice-of-customer findings, never invent it).
  • Specificity beats generality: a quantified outcome with a timeframe beats an adjective ("3 new revenue channels in 90 days" beats "grow the business").
  • Anchor the dream outcome to the single most urgent problem the ICP faces — the one they'd pay a premium to solve today, not a secondary nice-to-have.

Value Stack

  • Core offer + bonuses, each bonus solving a specific objection or accelerating time-to-value — no bonus should be generic filler.
  • Assign an honest value to every stack item. Never inflate a bonus's worth to manufacture a bigger discount illusion.
  • Order matters: lead with the highest-value item, close the stack with the easiest-to-consume item.
  • The stack's job is to make the price feel like the smaller number in the room — through real value, never through fake anchoring.

Guarantees

  • Two shapes: unconditional (removes all risk — use when confident and margin allows) and conditional/performance (tied to a specific, provable outcome — protects against misuse while still reversing risk).
  • Performance guarantees ("if X hasn't happened by Y, then Z") beat refund-only guarantees whenever the outcome is measurable and time-boxed.
  • Guarantees must be specific and provable. "Satisfaction guaranteed" is not a guarantee — it's a placeholder for one.

Scarcity & Urgency — Ethics (non-negotiable)

  • Every scarcity claim must tie to a REAL constraint: cohort size, calendar capacity, inventory, delivery capacity.
  • Every urgency claim must tie to a REAL event: an enrollment close date, a price change, a bonus expiration.
  • NEVER fabricate countdown timers, invented "X spots left" claims, or fake purchase notifications. This is a hard line — it destroys trust permanently and is a mkt-editor veto condition (see that agent's veto table).
  • If no real constraint exists, don't manufacture one. Sell on the strength of the value stack instead.

Pricing Psychology

  • Anchor pricing (showing a reference price before the offer price) only when the reference is real — a genuine prior price, a genuine market comparison.
  • Price against the value of the dream outcome, not against competitors' price points.
  • Payment structures — one-time, installments, performance-based — should match the price tier and the buyer's risk tolerance, not be a default.
  • Discounting is not the default lever for a stalling offer; adding value to the stack is. Habitual discounting trains buyers to wait for the next one.
  • Specific price bands and approval thresholds are defined per project pack (brain/projects/<x>/offer.md). This skill governs the psychology; the pack governs the numbers.

Naming

  • Specific beats generic — a name that encodes the mechanism and the outcome beats a category label ("90-Day Revenue Channel Sprint" beats "Growth Program").
  • A useful naming formula: magnetic reason why (why this exists now) + avatar (who it's for) + goal (the outcome) + interval (the timeframe) + container (the delivery format).
  • Names must be speakable in a real conversation. Clever wordplay that needs an explanation has already failed.

Offer Canvas (fill-in template)

OFFER: <name>
ICP segment: <from mkt-research / mkt-strategist>
Price tier: <tripwire / mid-ticket / high-ticket / application-only — per project pack>

Dream Outcome: <specific, quantified, time-boxed>

Value Equation Check:
- Dream Outcome: <1-10 + why>
- Perceived Likelihood: <1-10 + why — proof, guarantee, track record>
- Time to Value: <1-10 + why>
- Effort/Sacrifice: <1-10 + why>

Core Offer: <what the buyer gets>

Value Stack:
1. <item> — <honest value> — <objection it resolves>
2. ...

Guarantee: <type + exact terms + proof mechanism>

Scarcity/Urgency: <real constraint + how it's proven real>

Pricing: <anchor if used> / <offer price> / <payment structure>

Name: <final name> — <formula breakdown>

Diagnosing an Underperforming Offer

  1. Run the Value Equation check — identify the lowest-scoring lever; that's where the fix starts.
  2. Check the guarantee — specific and provable, or vague filler?
  3. Check scarcity — real, or does it read as manufactured? (mkt-editor will block fake urgency regardless of how well the rest of the copy performs.)
  4. Check the price-to-stack ratio — does the stack visibly outweigh the ask?
  5. Rebuild only the weakest lever first. A full offer rebuild is justified only when two or more levers score below 5.

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.