Mmcp.market

hundred-million-offers skill

by wondelai·wondelai/skills·2.3k stars·MIT

Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions "grand slam offer", "make my offer more compelling", "what bonuses should I add", "guarantee strategy", "offer naming", or "people say its too expensive". Also trigger when packaging a product for higher perceived value, justifying premium pricing instead of discounting, designing a money-back guarantee, or structuring tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.

A100/100content scan

Is the hundred-million-offers skill safe?

Clean: nothing in its files matched our rules. We read 11 files in the folder on 2026-09-28.

No findings.

Install the hundred-million-offers skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/hundred-million-offers ~/.claude/skills/hundred-million-offers
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Grand Slam Offer Creation Framework

Framework for creating offers so good people feel stupid saying no. What you sell (the offer) matters more than how you sell it or who you sell it to.

Core Principle

The offer is the #1 lever in any business: a Grand Slam Offer sells despite mediocre marketing, while the best marketing in the world cannot save a bad offer. Before optimizing funnels, running more ads, or hiring salespeople, fix the offer. A Grand Slam Offer maximizes Dream Outcome and Perceived Likelihood of Achievement while minimizing Time Delay and Effort & Sacrifice — becoming a category of one with no comparable alternative.

Scoring

Goal: 10/10. Score any offer by the 7-row Quick Diagnostic at the end of this file — award ~1.4 points per row answered "yes," rounding to a 0-10 scale. Bands: 9-10 = all/nearly all rows pass (irresistible: 10x perceived value, reversed risk, ethical scarcity, named dollar-valued bonuses, a category-of-one bundle, a MAGIC name); 5-6 = value and market are right but risk, bonuses, or scarcity are missing; <=3 = a commodity priced on cost with no guarantee or reason to act now. Always report the current score and the specific diagnostic rows that must flip to "yes" to reach 10/10.

The Grand Slam Offer Framework

1. The Value Equation

Core concept: Value = (Dream Outcome x Perceived Likelihood of Achievement) / (Time Delay x Effort & Sacrifice). Maximize the numerator and minimize the denominator to create massive perceived value.

Why it works: People buy outcomes, not products — they weigh the dream result and their confidence in achieving it against how long and hard the path is. When the numerator vastly outweighs the denominator, the offer feels like a no-brainer regardless of price.

Key insights:

  • Dream Outcome defines the ceiling of your value
  • Perceived Likelihood often matters more than actual results — social proof, guarantees, and track record raise it
  • Time Delay is a silent killer; faster results command premium prices
  • Effort & Sacrifice includes everything the customer gives up (time, comfort, status, identity)
  • A guarantee raises Perceived Likelihood and lowers perceived risk simultaneously

Product applications:

Copy patterns:

  • "Get [Dream Outcome] in [short time] without [Effort & Sacrifice]"
  • "Guaranteed [result] or [risk reversal]"
  • "We do [hard part] so you don't have to"

Ethical boundary: Back every speed, effort, and results claim with data, or label it aspirational rather than asserting it.

See references/value-equation.md when scoring an offer's value: per-lever 1-10 rubric, a composite-score calculator, and lever-interaction effects.

2. The Grand Slam Offer

Core concept: A Grand Slam Offer is a complete package — core offer, bonuses, guarantee, scarcity, urgency, and a compelling name — not just a product.

Why it works: Bundling multiple value elements makes price comparison impossible: no competitor offers the same combination, so you escape commoditization and price pressure.

Key insights:

  • List every problem and obstacle between the customer and the Dream Outcome; create a solution and delivery vehicle for each
  • Trim & Stack: cut low-value/high-cost solutions, stack high-value/low-cost ones
  • Each component should be nameable, independently valuable, and dollar-valued
  • The sum of component values should be at least 10x the price

Product applications:

Copy patterns:

  • "Here's everything you get when you join today..."
  • "Total value: $[sum of components]. Your investment: $[price]."
  • "Everything you need to [Dream Outcome] in one package"

Ethical boundary: Price each component at what someone would actually pay for it standalone — never inflate values to fake the value-price gap.

See references/grand-slam-offers.md when assembling the full package: problem-solution mapping and the Trim & Stack method worked end to end.

3. Finding Your Starving Crowd

Core concept: Before building the offer, find a starving crowd — a market with massive pain, purchasing power, easy targeting, and growth. The best offer fails if aimed at the wrong market.

Why it works: A starving crowd already knows it has the problem and is already hunting for a solution — your only job is presenting a compelling offer, which slashes acquisition cost and lifts conversion.

Key insights:

  • Four criteria: massive pain, purchasing power, easy to target, growing market
  • Pain matters most — people pay to stop pain faster than to gain pleasure
  • "Easy to target" means reachable through existing channels (associations, communities, platforms)
  • Niching down raises perceived value because specificity signals expertise

Product applications:

Copy patterns:

  • "Made specifically for [narrow audience] who struggle with [specific pain]"
  • "We only work with [type of client] because we know your world"
  • "If you're a [avatar] dealing with [pain], this was built for you"

Ethical boundary: Target genuine need and fit, never vulnerability — avoid people in crisis who cannot make rational decisions.

See references/starving-crowd.md when choosing or validating a market: the four-criteria niche scorecard and demand-validation checks.

4. Value-Based Pricing

Core concept: Charge based on the value you deliver, not your costs — aim for a 10:1 value-to-price ratio.

Why it works: Low prices attract price-sensitive customers who churn fastest and refer least; premium prices attract committed customers who invest effort, get better results, and stay — while funding exceptional delivery. That's a virtuous cycle.

Key insights:

  • Price is a function of perceived value, not cost
  • Raising prices often increases conversions — price signals quality and seriousness
  • Anchor against the cost of not solving the problem, not against alternatives
  • Payment plans remove price as an objection without reducing revenue
  • Price communicates positioning: commodity, premium, or luxury

Product applications:

Copy patterns:

  • "What would it be worth to you if [Dream Outcome]?"
  • "The cost of doing nothing is $[opportunity cost] per [time period]"
  • "An investment of $[price] for $[10x value] in [outcome]"

See references/pricing-strategy.md when setting a price: value-based pricing frameworks, cost-of-inaction anchoring, and payment-plan structures.

5. Bonuses: Value Stacking

Core concept: Bonuses are added components that address remaining objections and make the offer feel like an overwhelming deal — each solving a specific problem with an independently justifiable dollar value.

Why it works: Each bonus is attached to a specific unspoken objection, so the prospect's reasons not to buy are answered before they surface — and once stacked value exceeds the price, the core product reads as "free."

Key insights:

  • Each bonus should kill a specific objection or obstacle to success
  • Stack order matters: present the most valuable bonus first as the anchor
  • Partner bonuses add value at zero cost to you
  • Name each bonus — named bonuses feel more real; keep them high value / low cost to deliver (templates, recordings, access)

Product applications:

Copy patterns:

  • "Bonus #1: [Name] (a $[value] value) -- FREE"
  • "We added this because we noticed [objection] was holding people back"
  • "Total bonus value: $[sum]. Yours free when you join today."

See references/bonuses-stacking.md when designing bonuses: objection-to-bonus mapping, dollar-value assignment, and stack-order strategy.

6. Guarantees: Reversing Risk

Core concept: Guarantees transfer risk from buyer to seller. The prospect's biggest fear isn't losing money — it's making a bad decision; a strong guarantee makes "yes" psychologically safe.

Why it works: Every purchase carries financial, time, reputation, and identity risk, and guarantees neutralize them. Counterintuitively, stronger guarantees reduce refund rates — they signal confidence and attract committed buyers.

Key insights:

  • Five types: unconditional, conditional, anti-guarantee, implied, performance-based
  • Unconditional (full refund, no questions) is simplest and strongest for low-ticket
  • Conditional ("do X steps, or we refund") attracts better clients; anti-guarantees ("all sales final") work when demand exceeds supply
  • Performance-based ("we hit [metric] or you don't pay") is the ultimate risk reversal
  • Name your guarantee, and stack multiple guarantees to reverse multiple risk types

More skills from wondelai/skills

  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

All agent skills → · MCP servers