Skip to main content

hormozi-pitch

Turn an offer into a compelling Hormozi-style pitch ready for launch or sales. Use when creating a new pitch, improving a weak offer, or preparing for a launch. Builds value stack, guarantee options, scarcity and urgency elements, objection handling, offer name variations, and short/medium/long pitch versions — outputs PITCH.md.

설치로 이동

소스 정보

저장소
alexsmedile/hormozi-skills
최근 소스 활동
2026년 4월 14일 21:59
감지된 SKILL.md 언어
영어
스타
174
포크
33

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
hormozi-pitch
description
Turn an offer into a compelling Hormozi-style pitch ready for launch or sales. Use when creating a new pitch, improving a weak offer, or preparing for a launch. Builds value stack, guarantee options, scarcity and urgency elements, objection handling, offer name variations, and short/medium/long pitch versions — outputs PITCH.md.
# Skill: Build a Hormozi-Style Pitch ## Purpose Turn an idea, product, service, or existing offer into a clear, compelling pitch that feels easy to say yes to. This skill focuses on: - sharpening the value proposition - increasing perceived value - reducing friction and risk - structuring the offer so it feels obvious to buy - producing a ready-to-use pitch --- ## When to Use Activate this skill when the user wants to: - create a new offer pitch - improve a weak or unclear offer - increase conversions - structure pricing and guarantees - make an offer feel more valuable - prepare for launch or sales --- ## Inputs The skill can start from: - a raw idea - a rough offer - an existing product or service - an `OFFER.md` document - a sales page draft - a short description like “I sell X to Y” --- ## Core Outcome The assistant produces: - a strong offer name - a clear value proposition - a structured value stack - pricing logic - a guarantee - urgency and scarcity elements - objection handling - a complete pitch (short + long version) --- ## Assistant Behavior ### 1. Understand the offer first Extract: - who the offer is for - what result it promises - how it is delivered - current price (if any) - what feels weak, vague, or generic Reflect back in simple terms. Example: > You’re helping X get Y result through Z format. > The outcome is still a bit broad, and the value isn’t fully clear yet. --- ### 2. Ask clarifying questions (only if needed) Focus on gaps: #### Customer & Outcome - What result matters most to your customer? - What makes them act now? - What does success look like in real life? #### Proof & Trust - Do you have results, testimonials, or case studies? - What makes you credible for this? #### Offer Mechanics - What exactly do they get? - How fast can they see a result? - What support do they receive? #### Constraints - Price range? - Platform (Instagram, calls, email, landing page)? --- ### 3. Diagnose using the Value Equation Use Alex Hormozi’s Value Equation framework: Value = (Dream Outcome × Perceived Likelihood) / (Time Delay × Effort & Sacrifice) Break the offer into 4 parts: #### Dream Outcome - Is it clear? - Is it specific? - Is it desirable? #### Perceived Likelihood - Why should they believe this will work? - Is proof visible? - Is the path clear? #### Time Delay - How fast do they get a win? - Can this be shortened? #### Effort & Sacrifice - How hard does it feel? - Can steps be removed, simplified, or done for them? Then explain where the offer is weak and how to improve it. --- ### 4. Improve the offer before pitching Suggest upgrades: - make outcome more specific - reduce time to first result - add proof mechanisms - simplify delivery - remove friction - increase perceived ease If needed, propose: - different format (DFY, DWY, DIY) - different price positioning - different scope --- ### 5. Build the Value Stack List all components: For each: - name - what it does - why it matters - perceived value Then: - separate core offer vs bonuses - stack bonuses in logical order - calculate total value - compare with actual price Goal: create a strong gap between value and price. --- ### 6. Design the Guarantee Generate 3–4 options: - unconditional (money-back) - conditional (action-based) - outcome-based (results-tied) - anti-risk (you keep helping until result) For each: - give it a name - write exact wording - explain risk level Then recommend the best one based on: - price - complexity - trust level --- ### 7. Add Scarcity & Urgency Only if it fits. Options: - limited spots - limited time - fast-action bonuses - deadline pricing - cohort start date Explain why the constraint exists. Avoid fake scarcity. --- ### 8. Handle Objections List main objections: - “Will this work for me?” - “Is it worth the price?” - “Do I have time?” - “What if it doesn’t work?” Then write short responses that: - reduce doubt - increase clarity - reinforce value --- ### 9. Create the Offer Name Use the MAGIC format: - Make it about them - Announce the avatar - Give a goal - Indicate a time frame - Add a container word Generate 5–10 variations. --- ### 10. Write the Pitch #### Short Version (for ads, bios, hooks) - 1–2 lines - clear outcome - specific audience - time or mechanism #### Medium Version (for landing page) - problem - promise - what they get - why it works - CTA #### Long Version (full pitch) - callout to audience - pain amplification - desired outcome - solution explanation - value stack - price vs value contrast - guarantee - urgency - CTA --- ## Output Format ```md # PITCH.md ## 1. Offer Summary - Who it’s for - What it helps them achieve - How it works ## 2. Value Equation Breakdown - Dream Outcome - Perceived Likelihood - Time Delay - Effort & Sacrifice - Key improvements made ## 3. Offer Name Options - Name 1 - Name 2 - Name 3 ## 4. Core Offer - What’s included - Format - Delivery ## 5. Bonus Stack - Bonus - Purpose - Value ## 6. Value Stack - Total value - Price - Price justification ## 7. Guarantee - Option 1 - Option 2 - Option 3 - Recommended guarantee ## 8. Scarcity & Urgency - Mechanism - Reason ## 9. Objection Handling - Objection → Response ## 10. Pitch ### Short Version ... ### Medium Version ... ### Long Version ... ``` ⸻ Decision Rules Strengthen outcome when: • it sounds vague • it’s not measurable • it lacks urgency Increase belief when: • there is no proof • the claim feels too big • the path is unclear Reduce friction when: • the process feels complex • too much effort is required • the user must figure things out alone Add value when: • price feels high vs clarity • offer feels empty • differentiation is weak ⸻ Style Guidelines • clear and direct • specific outcomes • simple language • no hype tone • no vague claims • always grounded in what the buyer wants ⸻ Success Criteria The pitch works when: • the outcome is clear in seconds • the buyer feels understood • the value feels higher than the price • risk feels low • objections are already answered • the next step feels easy
GitHub에서 보기