本文へ移動
cccskills
無料GitHub で公開

prd-v09-offer-construction-hormozi

Construct a high-conversion offer using Alex Hormozi's value equation and Grand Slam Offer mechanics during PRD v0.9 Go-to-Market. Triggers on requests to design the offer, set up the pitch, build bonuses or guarantees, or when user asks "how do we package this?", "what's the offer?", "build a grand slam offer", "Hormozi", "$100M offers", "guarantee", "bonus stack". Outputs GTM-* entries with Type=Offer / Type=Guarantee and BR-PRICING-* updates.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md10.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Offer Construction (Hormozi $100M Offers)

Position in workflow: v0.9 Positioning (Dunford) → v0.9 Offer Construction (Hormozi) → v0.9 Launch Channels (ORB)

Execution Mode

Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.

ModeWhat this skill produces
quickOne offer; 1–2 named bonuses; one simple guarantee; price anchor
standardFull value equation calibrated; 3–5 bonuses with anchored values; one named guarantee; scarcity / urgency rule
deepMulti-tier offers (entry / mid / premium); guarantee experimentation plan; price anchor A/B; bonus value validation plan

Framework: Value Equation and Grand Slam Offer

From $100M Offers: How To Make Offers So Good People Feel Stupid Saying No (Alex Hormozi, 2021). An offer is the complete commercial proposition — what they get, what it costs, what's guaranteed, what's bundled, what's urgent — not just the product or the price.

The Value Equation

Perceived Value = (Dream Outcome × Perceived Likelihood of Achievement) / (Time Delay × Effort & Sacrifice)

Four levers — increase the numerator, decrease the denominator:

  1. Dream Outcome — What does the customer actually want? Express in their words. (Higher = better.)
  2. Perceived Likelihood of Achievement — How sure are they it will work? (Higher = better. Anchored by guarantees, social proof, case studies.)
  3. Time Delay — How long until they get the outcome? (Lower = better.)
  4. Effort & Sacrifice — How much work do they have to do? (Lower = better.)

If perceived value < price, the offer fails regardless of product quality.

Grand Slam Offer Components

A complete offer stacks five things:

  1. Core promise — the headline outcome (anchored in the value equation)
  2. Bonus stack — additional named items, each with anchored monetary value, that increase perceived value without proportionally increasing cost-to-deliver
  3. Guarantee — one of: unconditional refund, conditional ("if X doesn't happen, we Y"), anti-guarantee ("we don't refund — here's why we're so confident"), implied (case studies, results), or service-level
  4. Scarcity — limited supply (real: capacity, beta seats, custom service slots)
  5. Urgency — limited time (real: cohort start, price increase, bonus expiration)

Scarcity and urgency must be real. Manufactured scarcity erodes trust and is incompatible with Dunford's positioning (prd-v09-positioning-dunford).

Consumes

  • GTM-* positioning statement (from v0.9 Positioning) — Dream Outcome and Likelihood of Achievement language comes from the positioning's value claims; the offer cannot promise more than the positioning supports
  • BR-* pricing model (from v0.3 Pricing Model) — Existing price tiers; offer can stack on top but should not silently change the model
  • FEA-* features (from v0.3 Feature Value Planning) — Bonuses must be real product features or real services, not vapor
  • CFD-* value evidence (from v0.1–v0.4) — "Dream Outcome" wording comes from customer interviews; "Likelihood of Achievement" anchors come from case studies and usage data
  • PER-* best-fit segment (sharpened by Positioning) — Determines what "Dream Outcome" actually means to this buyer

This skill assumes Positioning is complete (positioning statement at confidence ≥ 3/5) and v0.3 Pricing Model is set.

Produces

  • GTM-* with Type=Offer — The full offer card: core promise, bonus stack with anchored values, guarantee reference, scarcity/urgency rule, price anchor
  • GTM-* with Type=Guarantee (separate ID) — The guarantee in standalone form so messaging can reference it directly
  • BR-PRICING-* updates — If the offer changes the pricing model (e.g., adds a one-time payment option, changes refund policy), update the BR- entries
  • CFD-* gaps surfaced — If the offer's Likelihood-of-Achievement claims can't be substantiated, log a CFD- research gap

Execution

Step 1: Calibrate the Value Equation

Write down each lever in the customer's words. Score each on a 1–5 scale:

LeverCurrentTargetGap
Dream Outcome
Likelihood of Achievement
Time Delay
Effort & Sacrifice

The largest gap = the lever to attack first.

Step 2: Design the core promise

State the headline outcome in one sentence: "You will [Dream Outcome] in [Time Delay] without [Effort & Sacrifice]." Test the sentence against the positioning statement — if they conflict, fix the offer, not the positioning.

Step 3: Build the bonus stack [standard+]

Aim for 3–5 bonuses. For each:

  • Name it concretely (not "additional support" — "1:1 setup call with founder, 30 min")
  • Assign an anchored value (what would this cost separately?)
  • Confirm it's deliverable at near-zero marginal cost (or factor cost into pricing)

Total stacked value should be ≥ 3× the price. If it isn't, the offer's perceived value is too low.

Step 4: Choose a guarantee

Pick the strongest guarantee you can deliver:

Guarantee TypeWhen to UseRisk
Unconditional refundConfident in product; low-touch saleRefund-fraud exposure
Conditional ("if X doesn't happen, we Y")Specific outcome promisedRequires clear measurement
Anti-guaranteePremium / high-status positioningLoses risk-averse buyers
Implied (case studies)Long sales cycle, B2BSlower trust-building
Service-levelOngoing relationshipOperational commitment

Write the guarantee in the customer's words. If you cannot stand behind it, choose a weaker one or fix the product.

Step 5: Add scarcity and urgency [standard+]

TypeExamples
Scarcity (supply)Beta seats (real cap), capacity-limited service tier, founding-member pricing
Urgency (time)Cohort start date, price increase scheduled, bonus expiration

Both must be real. Document the mechanism — what triggers the cap or deadline — in the GTM- entry. If you can't document the mechanism, drop the claim.

Step 6: Anchor the price [deep only]

Present the offer in this order: Dream Outcome → Stack value → Guarantee → Scarcity → Price. The price should feel inevitable given everything before it.

If running multiple offer tiers in deep mode, design the middle tier as the anchor (most buyers pick the option positioned next to the highest-priced option they almost-picked).

Output Template

GTM-XXX: Offer Card
Type: Offer
Owner: Founder / Sales
Status: Ready

Core promise: [One-sentence headline outcome]
Best-fit segment: PER-XXX
Linked positioning: GTM-YYY (Positioning Statement)

Value equation:
  Dream Outcome: [In customer words]
  Likelihood of Achievement: [What anchors this — case studies, guarantees]
  Time Delay: [Target]
  Effort & Sacrifice: [Target]

Bonus stack:
  1. [Bonus name] — anchored value: $X (real cost: ~$Y) — FEA-ZZZ or service
  2. [Bonus name] — ...
  3. ...

Total stacked value: $X (vs. price $Y — ratio ≥ 3:1)

Guarantee: GTM-ZZZ (separate entry)

Scarcity: [Real mechanism — beta cap, capacity limit, etc.]
Urgency: [Real deadline — cohort start, price change, etc.]

Price: $X (anchored against stacked value)
Payment terms: [One-time / monthly / annual / split]

Linked IDs: PER-XXX, GTM-YYY (positioning), FEA-ZZZ (bonus features), BR-PRICING-AAA, CFD-BBB (value evidence)
GTM-XXX: Guarantee
Type: Guarantee
Owner: Founder / Legal
Status: Approved

Guarantee type: [Unconditional refund | Conditional | Anti-guarantee | Implied | Service-level]
Stated in customer words: "[The exact wording]"
Eligibility: [Who, when, how]
Measurement: [How "did it work?" is determined]
Failure procedure: [What happens if invoked — refund process, etc.]

Linked IDs: GTM-YYY (Offer Card), BR-PRICING-ZZZ (if affects pricing model)

Anti-Patterns

PatternSignalFix
Manufactured scarcity"Only 7 spots left" reset every weekDrop the claim or make the cap real (e.g., one cohort per quarter)
Vapor bonusesBonus = "lifetime access" to a thing that costs you nothingReplace with something that has anchored value, even if cheap to deliver
Promise mismatchOffer promises more than positioning supportsFix the offer down; do not quietly upgrade positioning
Guarantee you can't honor"100% refund anytime" with 60% refund-fraud ratePick a stronger conditional guarantee instead
Stack ratio < 2:1Stacked value barely beats priceEither add more bonuses or drop the price; thin stacks don't convert
No best-fit segmentOffer designed for "everyone"Pull the PER- from positioning and design for them

Quality Gates

Before proceeding to Launch Channels:

  • Value equation calibrated with current vs. target per lever
  • Core promise written in one sentence
  • Stack value ≥ 3× price (standard+); ≥ 2× (quick)
  • Guarantee chosen and writable in customer's words
  • Scarcity and urgency mechanisms are real and documented
  • Offer does not contradict positioning statement
  • All bonuses trace to real FEA- or service deliverables

Downstream Connections

ConsumerWhat it usesExample
Launch Channels (ORB)Offer card = the unit being distributedOwned-channel emails sell the offer, not the product
Launch MetricsOffer becomes KPI- conversion targetKPI: offer page → purchase rate
Cold Outreach (Tactical)Tier 1/2/3 cold sequences end on the guaranteeGuarantee = reply-friction killer
v1.0 Crossing the Chasm (Moore)Offer shifts as adoption stage shiftsEarly-adopter offer ≠ early-majority offer

Detailed References

  • Alex Hormozi, $100M Offers (2021) — canonical source
  • Acquisition.com offer-construction resources
  • (No bundled references/ — read the book for depth)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check`.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

mattgierhart のスキルをすべて見る

このスキルの問題を報告する