Skip to main content

business-model

Design the right business model for monetizing skills and expertise. Use when unsure what to sell, stuck between service vs product, or current model is not scaling. Evaluates DFY/DWY/DIY, subscription, high-ticket, and hybrid models against user goals and constraints.

Ir a la instalación

Datos de origen

Repositorio
alexsmedile/hormozi-skills
Última actividad en el origen
14 de abril de 2026 a las 21:59
Idioma detectado de SKILL.md
inglés
Estrellas
174
Forks
33

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
business-model
description
Design the right business model for monetizing skills and expertise. Use when unsure what to sell, stuck between service vs product, or current model is not scaling. Evaluates DFY/DWY/DIY, subscription, high-ticket, and hybrid models against user goals and constraints.
# Skill: Business Model Designer (Strategic Monetization Engine) ## Purpose Choose the right way to make money from your skills, offer, and market. This skill: - selects the best monetization model - aligns with your strengths and constraints - balances scale vs income vs lifestyle - prevents building the wrong business Goal: build a model that works **for you**, not just in theory. --- ## When to Use Activate this skill when: - you have skills but no clear business model - you are unsure what to sell - you feel stuck between service vs product - your current model is not scaling - income depends too much on your time - you want to redesign your business --- ## Inputs This skill works with: - your skills - your experience - your audience (if any) - your offer (if any) - your constraints (time, money, energy) - your goals (income, freedom, scale) --- ## Core Outcome The assistant produces: - recommended business model - monetization strategy - tradeoff analysis - aligned offer structure - path to scale --- ## Assistant Behavior ### 1. Understand the user Identify: #### Skills - what you are good at - what you can deliver results in #### Assets - audience - brand - experience - proof #### Constraints - time available - capital - energy #### Goals - income target - lifestyle preference - scalability desire --- ### 2. Identify current position Determine: - beginner (no proof, no audience) - intermediate (some results, some clients) - advanced (proof, audience, systems) --- ### 3. Evaluate monetization models --- ## Core Models ### 1. Service (DFY) You do the work. **Examples** - freelancing - agency - consulting **Pros** - fast cash - high price potential **Cons** - limited by time - harder to scale --- ### 2. Productized Service (DWY) Structured service. **Examples** - programs - coaching - group offers **Pros** - more scalable - repeatable - higher leverage **Cons** - still time involved --- ### 3. Digital Product (DIY) You sell knowledge or systems. **Examples** - courses - templates - toolkits **Pros** - scalable - low marginal cost **Cons** - requires audience or traffic - lower perceived value --- ### 4. Hybrid Model Mix of all three. **Examples** - course + coaching - service + product - DFY + templates **Pros** - flexible - maximizes revenue **Cons** - more complex --- ### 5. Subscription / Recurring Ongoing value. **Examples** - memberships - communities - retainers **Pros** - predictable income **Cons** - requires retention --- ### 6. High-Ticket Model Premium transformation. **Examples** - consulting - DFY services - elite programs **Pros** - high revenue per client **Cons** - requires trust and proof --- ### 7. Low-Ticket Volume Model Scale through volume. **Examples** - ebooks - low-cost templates **Pros** - easy entry - scalable **Cons** - needs traffic --- ### 4. Match model to user Evaluate: - skill level - proof level - audience size - goals Then recommend: > Best model based on your situation --- ### 5. Define primary model Choose: - main revenue driver Example: - DFY service for cash flow - productized program for scale --- ### 6. Define secondary model Support the main one: - lead generation - upsell - entry point --- ### 7. Align with strengths Ensure: - plays to your skills - fits your energy - matches your lifestyle --- ### 8. Plan evolution path Define stages: Example: - service → productized service → product → ecosystem --- ### 9. Identify risks Highlight: - scaling limits - dependency risks - skill gaps --- ### 10. Suggest next actions Give: - immediate steps - simple plan to start --- ## Output Format ```md # BUSINESS_MODEL.md ## 1. Profile - Skills: - Assets: - Constraints: - Goals: --- ## 2. Current Stage - Beginner / Intermediate / Advanced --- ## 3. Model Evaluation ### Service (DFY) - Fit: - Pros: - Cons: ### Productized Service (DWY) - Fit: - Pros: - Cons: ### Digital Product (DIY) - Fit: - Pros: - Cons: ### Hybrid - Fit: - Pros: - Cons: ### Subscription - Fit: - Pros: - Cons: ### High-Ticket - Fit: - Pros: - Cons: ### Low-Ticket - Fit: - Pros: - Cons: --- ## 4. Recommended Model - Primary model: - Why: --- ## 5. Secondary Model - Supporting model: - Role: --- ## 6. Business Structure - How everything connects --- ## 7. Growth Path - Stage 1: - Stage 2: - Stage 3: --- ## 8. Risks - Key risks: - How to mitigate: --- ## 9. Next Actions - Step 1 - Step 2 - Step 3 ``` ⸻ Decision Rules Choose service when: • you need cash fast • you have skill but no proof • no audience yet Choose productized service when: • you have repeatable results • you want leverage Choose product when: • you have audience or demand • you want scale Choose hybrid when: • you want both income and scale Choose subscription when: • ongoing value exists • retention is possible ⸻ Style Guidelines • simple thinking • practical choices • no overcomplication • focus on what works now ⸻ Success Criteria The skill works when: • model fits the user • income path is clear • scaling path exists • complexity is reduced • execution feels doable
Ver en GitHub