agentleFS
Infinite-Labs-AIInfinite-Labs-AI/infinite-skills/skills/offer-design/SKILL.md

offer-design

Skill43 starsChanged 4 months agoMITView on GitHub

Use when designing or improving an offer, package, pricing page argument, plan structure, guarantee, bonus, trial, annual discount, service bundle, or upgrade path.

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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    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:

    If the user asks for copy before the offer is clear, define the offer first.

    line 23
  2. Distinctive:

    Do not invent scarcity.

    line 52
  3. Distinctive:

    Do not recommend a guarantee the business cannot honor.

    line 53
  4. Distinctive:

    Use a value metric customers can understand and the business can support.

    line 55
  5. Distinctive:

    Keep plan differences based on customer maturity or usage, not arbitrary feature hiding.

    line 56

“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

Shape the offer around buyer anxiety, adoption path, fulfillment constraints, and plan boundaries.

Understand The Sale

Identify:

  • Buyer and user.
  • Desired outcome.
  • Current alternative.
  • Price or expected budget.
  • Purchase anxiety.
  • Fulfillment cost and margin risk.
  • Proof available.
  • Sales motion: self-serve, sales-led, product-led, service-led, marketplace.

If the user asks for copy before the offer is clear, define the offer first.

Inspect Offer Fit

Break it into fit dimensions:

  • Buyer anxiety: what makes the purchase feel risky.
  • Adoption path: what has to happen after purchase for value to appear.
  • Fulfillment constraint: what the business must deliver reliably.
  • Support burden: where customers will need help.
  • Abuse risk: how guarantees, trials, discounts, or unlimited use can be misused.
  • Plan boundary: what separates small, growing, and high-value customers.
  • Proof threshold: what evidence the buyer needs before paying.
  • Price logic: how price maps to value, usage, or urgency.

Flag weak spots: vague deliverables, fake urgency, unpriced complexity, guarantees that create abuse, discounts that train waiting, support promises the team cannot honor, or plan tiers that punish the best customers.

Redesign

Offer 2-3 structures:

  • Simple offer: easiest to understand and buy.
  • Proof-heavy offer: best when trust is the barrier.
  • Expansion offer: best when land-and-expand matters.

For each, define the promise, included pieces, exclusions, price logic, risk reversal, and reason to act now.

Watch Outs

  • Do not invent scarcity.
  • Do not recommend a guarantee the business cannot honor.
  • Tie bonuses to purchase anxiety, not random perceived value.
  • Use a value metric customers can understand and the business can support.
  • Keep plan differences based on customer maturity or usage, not arbitrary feature hiding.

Output

Offer fit diagnosis:
[what is clear, what is weak]

Purchase anxiety:
- [fear]
- [fear]

Recommended offer:
Name:
For:
Promise:
Includes:
Excludes:
Price logic:
Adoption support:
Risk handling:
Abuse boundary:
Plan boundary:

Alternative structures:
1. [option] - [when to use]
2. [option] - [when to use]

Copy-ready bullets:
- [bullet]
- [bullet]
- [bullet]

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.