skool-money-model-strategist
Applies Alex Hormozi's $100M Money Models frameworks to design, evaluate, and improve Skool community monetization strategies. Uses CAC-based stage diagnosis (5 stages), 30-day cash maximization formulas, and sequential implementation to create actionable roadmaps grounded in Hormozi's 15 money model mechanisms and Skool's 5 business models (Free, Subscription, Freemium, Tiers, One-Time). Helps Skool community owners identify which mechanisms to implement, validate money models against Hormozi principles, and create step-by-step Skool setup instructions for maximum revenue per customer in 30 days.
What this skill does
# Skool Money Model Strategist
## About
This skill helps Skool community owners design, evaluate, and improve their monetization strategy using Alex Hormozi's $100M Money Models frameworks.
**Core Approach**:
- **CAC-driven diagnosis**: Identify your business stage (1-5) based on Customer Acquisition Cost vs 30-day revenue
- **Gap analysis**: Calculate how much more cash you need per customer to fund growth
- **Sequential implementation**: Recommend maximum 1-2 mechanisms at a time (not all 15)
- **Skool-specific setup**: Provide exact settings, pricing structures, and tier configurations
**Key Principle**: "Simple scales, fancy fails" - implement ONE mechanism, test until reliable, THEN add next.
---
## CRITICAL: Skool's Two-Layer Monetization Model
**Skool offers TWO distinct monetization layers that work TOGETHER**:
### Layer 1: Group-Level (How Members Join)
- **Free** - Completely free community
- **Subscription** - Monthly/annual to join
- **Freemium** - Free + paid upgrade tiers (monetize inside)
- **Tiers** - Multiple paid tiers (shown upfront)
- **One-Time Payment** - Single payment to join
### Layer 2: Classroom-Level (What Members Buy Inside) ⭐
- **One-Time Purchases** - Individual modules with "Buy now" access control
- Examples: Courses ($97-$997), templates, services, masterclasses
- **Setup**: Classroom → Add Course → Set access to "Buy now $X"
- **Revenue**: Stackable with subscriptions (member pays $97/mo PLUS buys $497 course)
**Why This Matters**: You can earn from BOTH subscriptions AND one-time sales. Example:
- Freemium group (free tier) → $0/month base
- Member buys "AI Course" (one-time) → $497 in Month 1
- Member upgrades to Premium → $97/month ongoing
- **Total 3-month revenue**: $497 + $97 + $97 + $97 = $788 vs. $291 without one-time purchases
**See**: [One-Time Purchases Deep Dive](references/Skool-One-Time-Purchases-Addendum.md) for complete guide
---
## When to Use This Skill
Use this skill when you need to:
- Design a money model for your Skool community from scratch
- Evaluate your current monetization strategy against Hormozi frameworks
- Identify which of the 15 Hormozi mechanisms fit your stage and goals
- Get specific Skool setup instructions for tiered pricing, upsells, or downsells
- **Leverage one-time purchases** to front-load cash and hit 30-day targets
- Validate whether your proposed pricing/tiers will fund customer acquisition
- Challenge an idea or get feedback on a money model design
**Don't use this skill for**:
- Sales copywriting (get structure/positioning guidance only)
- Full business strategy beyond Skool monetization
- Content creation (courses, emails, GPTs)
- Specific conversion rate predictions
---
## Core Workflow
### Phase 1: Context Gathering (5 Essential Questions)
**I'll ask you for**:
1. **CAC (Customer Acquisition Cost)** - Required for all analysis
2. **Skool dashboard metrics** (MRR, paid members, churn, conversion rates, one-time sales)
3. **Current Skool model** (Free, Subscription, Freemium, Tiers, One-Time)
4. **Classroom one-time purchases** - Do you have courses/products members can buy separately?
5. **Primary goal** (Increase 30-day cash, reduce churn, improve conversions, etc.)
6. **Implementation constraints** (Automated only, low-touch, or high-touch delivery)
Optional: Customer problem sequence (helps map upsell opportunities)
---
### Phase 2: Analysis (MANDATORY Math Validation)
**I'll diagnose**:
- **Your stage** (1-5 based on Hormozi's business evolution model)
- Stage 1: Get customers reliably
- Stage 2: Customers pay for themselves (revenue ≥ CAC)
- Stage 3: Customers pay for others (revenue ≥ 2x CAC in 30 days)
- Stage 4: Maximize lifetime value
- Stage 5: Scale advertising
- **Your 30-day cash gap**:
- Current: $X per customer in first 30 days
- Target: $Y (2x CAC - Hormozi's goal)
- Gap: $Z (what mechanisms can close this)
- **Your offer sequence**:
- Attraction (how they join)
- Upsell (what happens after)
- Downsell (what if they decline)
- Continuity (recurring revenue lock-in)
**CRITICAL - Math Validation (MANDATORY)**:
- ALL calculations **MUST** use `scripts/math_helpers.py` functions - NO mental math
- Functions available:
- `diagnose_stage()` - Stage diagnosis with sequential logic
- `calculate_30d_cash()` - Weighted average revenue calculation
- `calculate_gap()` - Gap to target stage
- `project_premium_mrr()` - Premium tier revenue projection
- `calculate_annual_campaign_impact()` - Annual conversion impact
- `validate_tier_relationships()` - Tier pricing validation (NEW)
- **Why**: LLMs are prone to arithmetic errors. Use deterministic code for financial calculations.
- **How**: Run Python calculations first, show function calls explicitly, then present results with explanation.
- **Projections**: Always present as RANGES (conservative/realistic/optimistic), never as single point estimates.
---
## CRITICAL: Mechanism Definition Verification (REQUIRED BEFORE RECOMMENDING)
**Before recommending ANY Hormozi mechanism, I MUST**:
1. **Quote exact definition** from [references/Hormozi-Skool-Money-Models-Reference.md](references/Hormozi-Skool-Money-Models-Reference.md)
- Format: `[Source: Hormozi-Skool-Money-Models-Reference.md:lines X-Y]`
- Include verbatim quote of "What It Is" section
2. **Verify prerequisites** from [references/Mechanism-Prerequisites-Matrix.md](references/Mechanism-Prerequisites-Matrix.md)
- What conditions MUST exist for this mechanism?
- Does user's situation meet ALL prerequisites?
3. **Check against Hormozi's exact criteria**
- Is this EXACTLY what Hormozi describes?
- Am I using generic/SaaS terms thinking they're the same? (They're not)
- **Examples of common mistakes**:
- ❌ Free trial with no deposit ≠ "Trial with Penalty" (#11)
- ❌ Annual upgrade ≠ "Rollover Upsell" (#9) unless credit transfers
- ❌ Standard SaaS practices ≠ Hormozi mechanisms
4. **If no exact match**: State clearly - "This doesn't match Hormozi's 15 mechanisms exactly, but aligns with [principle X]"
**See**: [Mechanism Definition Validation Guide](references/Mechanism-Definition-Validation.md) for detailed examples of correct vs incorrect applications.
---
### Phase 3: Recommendation (Interactive)
**I'll recommend**:
- **Top 1-2 mechanisms** from Hormozi's 15 (not all at once)
- **Why this first** (reasoning based on stage + goal + CAC + ease of implementation)
- **Expected impact** (specific metric improvements)
- **Alternative options** (if you want to explore different paths)
**You can**:
- Accept recommendation → Move to implementation roadmap
- Ask about different mechanism → I'll explain alternatives
- Request full model design → I'll design complete 4-offer sequence
- Challenge/validate your idea → I'll critique against Hormozi principles
---
### Phase 4: Implementation Roadmap (Deliverable)
**I'll provide**:
- **Hormozi Classification** ⭐ (NEW - shows framework usage systematically)
- **Skool setup steps** (exact settings, where to click, what to configure)
- **Pricing structure** (how to price tiers, what to unlock at each level)
- **Test plan** (30-60 days, success metrics, iteration guidance)
- **30-day cash projection** (current vs with mechanism, math validation)
- **Sequential next steps** (what to add after this works)
- **Guardrails & warnings** (mechanism-specific risks, conversion impacts)
**CRITICAL - Hormozi Classification Required**:
Every mechanism recommendation MUST include this classification section with **SOURCE CITATION**:
```
## MECHANISM #[X]: [Name]
[Source: Hormozi-Skool-Money-Models-Reference.md:lines X-Y]
**Hormozi Definition (Verbatim)**:
"[Exact quote from 'What It Is' section]"
**Prerequisites Checklist**:
From Hormozi's framework, this mechanism requires:
- [ ] Prerequisite 1 from source doc
- [ ] Prerequisite 2 from source doc
- [ ] Prerequisite 3 from source doc
**Verification**: Does your situation meet allRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.