agentleFS
link7373link7373/agentic-sales-marketing/.claude/skills/design-offer/SKILL.md

design-offer

Skill1 starsChanged 3 months agoMITView on GitHub

Design or overhaul the offer — value proposition, packaging, bonuses, pricing, guarantee, urgency — so the product becomes dramatically more valuable than its price. Run after market research; rerun when conversions disappoint.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

/design-offer — Make the Offer Impossible to Ignore

Inputs: knowledge/business-context.md, knowledge/audience-profiles.md, knowledge/research/customer-language.md. Agents: offer-strategist leads; copywriter names and phrases. Method: knowledge/methods/offer-design.md; knowledge/methods/persuasion-principles.md within its ethical rules.

Steps

  1. Name the dream outcome. From research: the transformation the beachhead segment actually wants (not the product's features). State it in their words.
  2. Work the four value levers. (a) Outcome size — is the promise as big as honestly deliverable? (b) Belief it'll work for them — what proof exists or can be created (results, demonstrations, guarantee)? (c) Time to result — what would make first value arrive faster? (d) Effort required — what can we do for them instead of teaching them to do it?
  3. List the obstacles. Everything that stops this buyer from buying or succeeding after buying. Rank by frequency in research.
  4. Package against obstacles. Core product plus components/bonuses that each neutralize a named obstacle. Cut anything that answers no objection.
  5. Price from value. Set the anchor (cost of the problem, pricier alternatives), choose the price, sanity-check unit economics including the guarantee's cost. Underpricing is flagged as a positioning error, not prudence.
  6. Design the risk reversal. The strongest guarantee the economics survive, worded exactly. Model the abuse case honestly.
  7. True urgency, if any exists. Real deadline, cohort, or capacity limit — otherwise none. Compliance check on every element.
  8. Name and frame. Offer name and one-line pitch a stranger understands at scroll speed.
  9. Operator approval. Price and guarantee are money decisions — present the offer sheet, get sign-off, log it.

Before you start

  1. Required inputs: knowledge/audience-profiles.md at seeded+ and knowledge/research/customer-language.md present — if missing, offer to run /research-market first.
  2. Scan knowledge/decision-log.md for tags offer, pricing — a prior pricing decision stands until superseded with rationale.
  3. Gate check: price and guarantee are money decisions; the approval in step 9 is mandatory, not optional.

If things go wrong

  • Research too thin to name the dream outcome → route back to /research-market for targeted language mining rather than guessing.
  • Unit economics don't survive any honest guarantee → flag it as a product/pricing problem to the operator; don't ship a hollow guarantee.
  • Operator unavailable for sign-off → park the offer sheet in knowledge/pending.md; nothing downstream (copy, funnels, campaigns) uses an unapproved offer.

Outputs

knowledge/offer.md via templates/offer-sheet.md, operator-approved. Close with the report per templates/skill-report.md.

Writeback

knowledge/offer.md; pricing decision + rationale (tags: offer, pricing) to knowledge/decision-log.md; approval to knowledge/approvals-log.md.

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.