Skip to main content
ClaudeWave
Skill1.3k estrellas del repoactualizado 2d ago

hundred-million-offers

The hundred-million-offers Claude Code skill provides a framework for constructing high-converting offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity tactics. Use it when developing pricing strategies, designing money-back guarantees, structuring offer packages, naming promotions, or justifying premium pricing, especially when the goal is to create offers so compelling that customers feel irrational saying no.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/wondelai/skills /tmp/hundred-million-offers && cp -r /tmp/hundred-million-offers/hundred-million-offers ~/.claude/skills/hundred-million-offers
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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.** When reviewing or creating offers, rate them 0-10 against the principles below. A 10/10 is genuinely irresistible — high perceived value, reversed risk, ethical scarcity, compelling bonuses, and a name that demands attention. Always provide the current score and the specific improvements needed 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:**

| Context | Application | Example |
|---------|-------------|---------|
| **SaaS** | Cut time-to-value | "First dashboard in 5 minutes, not 5 weeks" |
| **Agency** | Guarantee results to cut risk | "10 qualified leads or you don't pay" |
| **Info product** | Templates reduce effort | "Fill in the blanks -- no writing from scratch" |

**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:** Never promise outcomes you cannot reasonably deliver — substantiate every speed, effort, and results claim with real data or state it as aspirational.

See: [references/value-equation.md](references/value-equation.md) for the four levers, optimization tactics, and scoring rubric.

### 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:**

| Context | Application | Example |
|---------|-------------|---------|
| **SaaS** | Bundle training, setup, templates | "Platform + Setup Concierge + Template Library + Weekly Coaching" |
| **Course** | Add community, coaching, tools | "Course + Private Community + Weekly Q&A + Swipe Files" |
| **Consulting** | Package frameworks and support | "Diagnostic + Roadmap + 90-Day Implementation Support" |

**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:** Assign honest, defensible dollar values to each component — never inflate values to fake a value-price gap.

See: [references/grand-slam-offers.md](references/grand-slam-offers.md) for the full offer assembly process and problem-solution mapping.

### 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:**

| Context | Application | Example |
|---------|-------------|---------|
| **SaaS** | Vertical with acute pain | "CRM for real estate agents who lose deals to follow-up failures" |
| **Agency** | Dominate one industry | "SEO agency exclusively for dental practices" |
| **Info product** | Narrow, painful, urgent problem | "How doctors negotiate their first hospital contract" |

**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 decision
37signals-waySkill

Build 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", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

blue-ocean-strategySkill

Create 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", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

clean-architectureSkill

Structure 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 architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

clean-codeSkill

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

contagiousSkill

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

continuous-discoverySkill

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

cro-methodologySkill

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

crossing-the-chasmSkill

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.