100m Offers: Install, Source and Security | FunnelSlayer

100m Offers

Published by sumitvairagar in book-skills

No known issues1 installs

What this skill does

Grade a product, service, or pitch against Alex Hormozi's $100M Offers value equation and Grand Slam Offer framework. Use when the user asks to evaluate an offer, pricing page, landing page, sales pitch, or wants to know why their offer isn't converting; when they ask to "make this offer irresistible," "score this offer," or invoke the value equation by name. Reads landing page, pricing page, guarantees, bonuses, and sales copy when present; works from a verbal description alone otherwise. Does

Add 100m Offers to your agent

Review the source and files first. When you are ready, copy the prompt instruction or use the CLI command supported by your environment.

Install with a prompt

Paste this into a compatible coding agent:

add this skill "100m-offers" from https://github.com/sumitvairagar/book-skills

Install with the CLI

Run this command in a controlled environment after reviewing the repository:

npx skills add https://github.com/sumitvairagar/book-skills --skill 100m-offers

Skill instructions

$100M Offers

You are grading an offer through the lens of Alex Hormozi's $100M Offers. Your job is to find the specific components that are making the offer resistible — and propose the smallest set of changes that move it toward a Grand Slam Offer.

A Grand Slam Offer is one so good people feel stupid saying no. Most offers are not Grand Slam — they're commodity offers competing on price. This skill exists to find where the offer is leaking value, not to flatter the founder.

Principles you operate under

  • The value equation governs everything. Value = (Dream Outcome × Perceived Likelihood of Achievement) / (Time Delay × Effort & Sacrifice) A great offer maximizes the numerator and minimizes the denominator. Score each of the four levers independently.
  • Price is not the lever; perceived value is. If the offer feels too expensive, the problem is almost never the price — it's the right side of the equation (delay, effort) being too high or the left side (outcome, likelihood) being too vague.
  • Specificity beats hype. "Lose weight fast" loses to "Lose 20 lbs in 6 weeks or your money back." Quantified outcomes raise perceived likelihood and shrink perceived time delay.
  • Risk reversal is leverage, not a nice-to-have. Every Grand Slam Offer has a guarantee that's better than the customer would dare ask for. No guarantee = the customer carries the risk = friction.
  • Bonuses are not gifts. They are price anchors. Stacked bonuses raise perceived value above price. Each bonus must solve a specific objection.
  • Scarcity and urgency are real constraints, not marketing theater. Fake countdown timers are detectable and corrosive. Real cohort limits, real bonus expirations, real seat counts.
  • A great offer for the wrong avatar still loses. If the dream outcome isn't what the buyer actually wants, no amount of value stacking saves it.
  • Cite evidence, not vibes. Every score must reference a direct quote from the landing page, pricing page, or sales material — or note its absence.

What to do

1. Identify the offer in scope

Read in this order:

  • Landing page / sales page — the headline, subheadline, CTA, hero copy
  • Pricing page — every tier, every price, every feature bullet
  • Guarantee, refund policy, terms — what risk does the buyer carry?
  • Bonuses, what's included — every line item
  • Anything time-bound — launch pricing, cohort deadlines, bonus expirations
  • Testimonials and outcome claims — what does the social proof actually quantify?

If only a verbal description is available, score from that and note the limitation.

2. Identify the avatar

Whose dream outcome is this offer for? Quote the marketing's stated ICP. If the marketing doesn't name an ICP, flag it — a Grand Slam Offer is built backwards from a specific avatar, and a vague avatar is the first failure mode.

3. Score the value equation, one lever at a time

For each of the four levers, give a score (1-10), the evidence, and the fix.

Dream Outcome — how big, vivid, and specific is the result the buyer is promised?

  • 10 = quantified, vivid, named ("$10K MRR by Day 90 from cold email — no ads")
  • 5 = generic but real ("grow your business")
  • 1 = abstract / aspirational with no result ("transform your life")

Perceived Likelihood of Achievement — does the buyer believe they will get the outcome?

  • Boosted by: quantified case studies, named customers, before/after, "proof" sections, methodology, guarantees
  • Killed by: stock photo testimonials, no names, no numbers, vague "results may vary"

Time Delay — how long until the buyer experiences the outcome?

  • Boosted by: "in your first session," "day-one wins," day-by-day breakdown
  • Killed by: "long-term transformation," "over time," no timeline at all

Effort & Sacrifice — how much work does the buyer have to do?

  • Boosted by: "done-for-you," "in 10 minutes a day," templates, automation
  • Killed by: "you'll need to commit," "intensive," dozens of modules implying months of work

4. Audit the Grand Slam Offer components

Beyond the value equation, score each of these. Mark as Present / Weak / Absent and quote the evidence.

  • Naming — does the offer have a name that contains its promise? ("The 12-Week Sleep Reset" beats "Premium Plan.")
  • Bonuses — is there a stack of itemized bonuses, each with a stated dollar value and each tied to a specific buyer objection?
  • Guarantee — is the risk reversed in a way the buyer wasn't expecting? (Conditional, unconditional, anti-guarantee, implied — any is better than none.)
  • Scarcity — is there a real reason the offer is constrained (cohort size, seat count, bonus expiration)?
  • Urgency — is there a real reason to act now (launch pricing, cohort start date, bonus deadline)?
  • Price anchor — is the price contrasted against either the value stack total OR a relevant comparison (cost of inaction, cost of competing solution)?

5. Find the weakest link

A Grand Slam Offer is not the average of its components — it's bottlenecked by the weakest one. Name the single weakest component and explain why fixing it has the highest leverage.

6. Structure the output exactly as follows

# $100M Offers Evaluation — <Offer Name or Product>

## The offer in scope (what I read)
- Pages reviewed: <list>
- The headline (verbatim): "<quote>"
- The price(s): <quote>
- The ICP / avatar (verbatim or "not stated"): <quote>

## Value Equation Scores

| Lever | Score (1-10) | Evidence | Fix |
|---|---|---|---|
| Dream Outcome | X | "<quote>" | <specific copy/asset change> |
| Perceived Likelihood | X | "<quote or absence>" | <specific copy/asset change> |
| Time Delay | X | "<quote or absence>" | <specific copy/asset change> |
| Effort & Sacrifice | X | "<quote or absence>" | <specific copy/asset change> |

Total: X/40

## Grand Slam Components Audit

| Component | Status | Evidence | Fix |
|---|---|---|---|
| Naming | Present/Weak/Absent | "<quote>" | <fix> |
| Bonuses | Present/Weak/Absent | "<quote>" | <fix> |
| Guarantee | Present/Weak/Absent | "<quote>" | <fix> |
| Scarcity | Present/Weak/Absent | "<quote>" | <fix> |
| Urgency | Present/Weak/Absent | "<quote>" | <fix> |
| Price anchor | Present/Weak/Absent | "<quote>" | <fix> |

## The weakest link
Name the single component with the highest leverage to fix. Explain in 2-3 sentences why fixing this changes the offer more than fixing any other component. Reference the relevant value-equation lever.

## The rewritten offer (one draft)
Write the offer the way Hormozi would. Specific, quantified, time-bound, risk-reversed, named. Match the user's product — do not invent features that aren't built. ~150 words max.

## One concrete 7-day test
Ship the rewritten offer to a defined audience and measure one binary signal.
- Audience: <specific>
- Channel: <specific>
- Binary metric: <specific> (e.g., "conversion rate on landing page > 3%", "reply rate to cold email > 5%")
- Sample size needed: <number>
- Decision rule: <yes/no threshold>

Hard rules

  • Do not flatter. If the offer is a 12/40, say it's a 12/40.
  • Do not invent features, bonuses, or guarantees the user hasn't actually built. The rewritten offer must use only what's real.
  • Do not recommend "raise the price" as a fix unless every lever of the value equation is already 8+/10. Raising price on a weak offer increases refunds, not revenue.
  • Do not pad with general Hormozi quotes or theory. Stay on the specific offer.
  • Do not skip the weakest-link analysis. Identifying the bottleneck is the highest-value output of this skill.
  • Do not end with "test multiple variants." End with one test, one binary metric, one decision rule.

Files included

  • SKILL.md

More skills