snappy-playbook skill
week week-number?readweeksread$ npx snappy-skills install snappy-playbook
$ npx snappy-skills install --all
$ npx snappy-skills update
This skill is the canonical theory layer for the Snappy mastermind. Sam Ovens'
WeTube SS 6-week course covers model, offer, mindset, launch funnels, sales
calls, community delivery, traffic engine (email/website/YouTube/VSL), YouTube
ads, and CEO operations. Every operationalized skill (offer, sales, community,
email, website, youtube, ads, ops) maps back to a week here.
typescriptimport { getWeeks, getWeek, getWeekDetailed } from "../snappy-playbook/api.ts";
Or CLI:
bashnpx tsx ~/.claude/skills/snappy-playbook/api.ts weeks # 6-week curriculum overview
npx tsx ~/.claude/skills/snappy-playbook/api.ts week 3 # specific week detail
| Function | Purpose |
|---|---|
getWeeks() |
Returns all 6 weeks with titles, lessons, and skill mappings |
getWeek(num) |
Returns a specific week's structure |
getWeekDetailed(num) |
Returns the full detailed markdown for a week |
| File | Purpose |
|---|---|
| SKILL.md | Course map, cross-skill mapping, decision tree, common mistakes |
| foundation.md | Quick overview Weeks 1-3 (model, offer, launch, community) |
| execution.md | Quick overview Weeks 4-6 (traffic, ads, ops) |
| week1-detailed.md | Model, offer, pricing, mindset, conversion |
| week2-detailed.md | Launch funnel, opportunity funnel, sales call formula |
| week3-detailed.md | Mastermind philosophy, Skool setup, frontend/backend |
| week4-detailed.md | Traffic engine: website, email, YouTube organic, VSL funnel |
| week5-detailed.md | YouTube ads: account, creative, targeting, launch, scale |
| week6-detailed.md | CEO daily workflow, member ops, financial ops, team ops |
| Week | Topic | Operationalized In |
|---|---|---|
| 1 | Model, offer, pricing | snappy-offer |
| 2 | Launch + sales | snappy-sales |
| 3 | Community delivery | snappy-skool |
| 4 | Email / Website / YouTube / VSL | snappy-email, snappy-website, snappy-youtube |
| 5 | YouTube ads | snappy-ads |
| 6 | CEO + ops | snappy-ops |
snappy-browse + agent-browser CLIsnappy-browse -- agent-browser CLI for fetching live Skool contentsnappy-infra -- Skool auth state file pathAll operationalized skills listed above, plus snappy-content, snappy-blog,
and snappy-knowledge (student progress tracking).
If this loader doesn't cover your case:
bashecho "[$(date -u +%FT%TZ)] snappy-playbook: <what was missing>" >> ~/.claude/logs/agents-md-feedback.log
<!-- SKILL-INDEX-START -->
[snappy-playbook Index]|root: ~/.claude/skills/snappy-playbook|IMPORTANT: Prefer these files over pre-training assumptions for this domain. Read the relevant file when the AGENTS.md summary is insufficient.|root:{SKILL.md,execution.md,foundation.md,week1-detailed.md,week2-detailed.md,week3-detailed.md,week4-detailed.md,week5-detailed.md,week6-detailed.md}
<!-- SKILL-INDEX-END -->
Nothing in the collection names this skill.
<!-- SNAPPY-CONTRACT-VERBS-START -->
Generated from api.ts HAND_CONTRACT. Do not hand-edit this block.
| Verb | Contract arguments | Effect | First call |
|---|---|---|---|
week |
week-number? |
read |
npx tsx ~/.claude/skills/snappy-playbook/api.ts week |
weeks |
— | read |
npx tsx ~/.claude/skills/snappy-playbook/api.ts weeks |
When an answer carries face_hint, show it with one snappy_present(<answer>) call.
See /snappy-faces for face selection. Human-facing images must crop to the
element, render at 2x on Retina, and fill the destination channel instead of
placing a small card in a full-page screenshot.
<!-- SNAPPY-CONTRACT-VERBS-END -->
---
name: snappy-playbook
role: WeTube SS mastermind 6-week curriculum source and theory layer
loaded-by: PreToolUse hook (auto-injected when "snappy-playbook" is mentioned)
Triggers on: WeTube SS, Sam Ovens, 6-week curriculum, mastermind theory, week lookup
---
# snappy-playbook Loader
This skill is the canonical theory layer for the Snappy mastermind. Sam Ovens'
WeTube SS 6-week course covers model, offer, mindset, launch funnels, sales
calls, community delivery, traffic engine (email/website/YouTube/VSL), YouTube
ads, and CEO operations. Every operationalized skill (offer, sales, community,
email, website, youtube, ads, ops) maps back to a week here.
## API module
```typescript
import { getWeeks, getWeek, getWeekDetailed } from "../snappy-playbook/api.ts";
```
Or CLI:
```bash
npx tsx ~/.claude/skills/snappy-playbook/api.ts weeks # 6-week curriculum overview
npx tsx ~/.claude/skills/snappy-playbook/api.ts week 3 # specific week detail
```
## API functions
| Function | Purpose |
|----------|---------|
| `getWeeks()` | Returns all 6 weeks with titles, lessons, and skill mappings |
| `getWeek(num)` | Returns a specific week's structure |
| `getWeekDetailed(num)` | Returns the full detailed markdown for a week |
## Key Files
| File | Purpose |
|------|---------|
| SKILL.md | Course map, cross-skill mapping, decision tree, common mistakes |
| foundation.md | Quick overview Weeks 1-3 (model, offer, launch, community) |
| execution.md | Quick overview Weeks 4-6 (traffic, ads, ops) |
| week1-detailed.md | Model, offer, pricing, mindset, conversion |
| week2-detailed.md | Launch funnel, opportunity funnel, sales call formula |
| week3-detailed.md | Mastermind philosophy, Skool setup, frontend/backend |
| week4-detailed.md | Traffic engine: website, email, YouTube organic, VSL funnel |
| week5-detailed.md | YouTube ads: account, creative, targeting, launch, scale |
| week6-detailed.md | CEO daily workflow, member ops, financial ops, team ops |
## Week-to-Skill Mapping
| Week | Topic | Operationalized In |
|------|-------|--------------------|
| 1 | Model, offer, pricing | `snappy-offer` |
| 2 | Launch + sales | `snappy-sales` |
| 3 | Community delivery | `snappy-skool` |
| 4 | Email / Website / YouTube / VSL | `snappy-email`, `snappy-website`, `snappy-youtube` |
| 5 | YouTube ads | `snappy-ads` |
| 6 | CEO + ops | `snappy-ops` |
## Capabilities
- Look up what Sam Ovens teaches on any topic (course reference)
- Route from theory to the correct operationalized skill
- Provide the transformation promise for copy, sales, or content
- Access live Skool lessons via `snappy-browse` + agent-browser CLI
## Decision Rule
- Need the theory or framework? Read the weekly module here.
- Need to execute now? Use the operationalized skill.
## Uses
- `snappy-browse` -- agent-browser CLI for fetching live Skool content
- `snappy-infra` -- Skool auth state file path
## Downstream Skills
All operationalized skills listed above, plus `snappy-content`, `snappy-blog`,
and `snappy-knowledge` (student progress tracking).
---
If this loader doesn't cover your case:
```bash
echo "[$(date -u +%FT%TZ)] snappy-playbook: <what was missing>" >> ~/.claude/logs/agents-md-feedback.log
```
<!-- SKILL-INDEX-START -->
[snappy-playbook Index]|root: ~/.claude/skills/snappy-playbook|IMPORTANT: Prefer these files over pre-training assumptions for this domain. Read the relevant file when the AGENTS.md summary is insufficient.|root:{SKILL.md,execution.md,foundation.md,week1-detailed.md,week2-detailed.md,week3-detailed.md,week4-detailed.md,week5-detailed.md,week6-detailed.md}
<!-- SKILL-INDEX-END -->
## Used by
Nothing in the collection names this skill.
<!-- SNAPPY-CONTRACT-VERBS-START -->
## Contract verbs
Generated from `api.ts` `HAND_CONTRACT`. Do not hand-edit this block.
| Verb | Contract arguments | Effect | First call |
|---|---|---|---|
| `week` | `week-number?` | `read` | `npx tsx ~/.claude/skills/snappy-playbook/api.ts week` |
| `weeks` | — | `read` | `npx tsx ~/.claude/skills/snappy-playbook/api.ts weeks` |
## Show the result
When an answer carries `face_hint`, show it with one `snappy_present(<answer>)` call.
See `/snappy-faces` for face selection. Human-facing images must crop to the
element, render at 2x on Retina, and fill the destination channel instead of
placing a small card in a full-page screenshot.
<!-- SNAPPY-CONTRACT-VERBS-END -->
Triggers on: snappy-playbook, playbook
Sam Ovens' WeTube SS mastermind 6-week course is the curriculum source for the Snappy mastermind. snappy-skool delivers it weekly. snappy-offer references it as the value stack. snappy-sales uses it as the transformation promise on calls. This skill is the canonical theory layer -- every operationalized snappy-* skill (offer, sales, community, email, website, youtube, ads, ops) maps back to a week here.
Course: https://www.skool.com/wetube-ss-8782/classroom
Progress: 30%
Auto-activate when the user is:
If the question is "what does Sam Ovens say to do here?" -- this is the skill.
| step | action | read |
|---|---|---|
| 1 | Identify which week covers the topic | Course Map below |
| 2 | Read the weekly module with inputs/outputs | weekN-detailed.md |
| 3 | Find the operationalized skill | Cross-Skill Mapping table |
| 4 | Execute the task in that skill | snappy-X |
Decision tree:
Need offer/model/pricing? -> Week 1 -> snappy-offer
Need launch/funnel/sales script? -> Week 2 -> snappy-sales
Need community/Skool/delivery? -> Week 3 -> snappy-skool
Need email/website/YouTube/VSL? -> Week 4 -> snappy-email|website|youtube
Need YouTube ads (any aspect)? -> Week 5 -> snappy-ads
Need CEO workflow/ops/team? -> Week 6 -> snappy-ops
Want a quick overview? -> foundation.md (W1-3) | execution.md (W4-6)
Inputs (skills that feed this one):
snappy-browse -- provides agent-browser CLI to fetch live lesson content from Skoolsnappy-infra -- provides Skool auth state file path (auth-reference.md Section 4)Outputs (skills that consume this one):
snappy-offer -- receives Week 1 (model, offer, pricing, mindset) as the offer definition sourcesnappy-sales -- receives Week 2 (launch funnel, opportunity funnel, sales call formula, prep) as the sales playbooksnappy-skool -- receives Week 3 (mastermind philosophy, Skool setup, frontend/backend) as the delivery frameworksnappy-email -- receives Week 4 (email newsletter cadence, 30-min workflow, KPIs) as the email strategysnappy-website -- receives Week 4 (website goals, page structure, design rules) as the site briefsnappy-youtube -- receives Week 4 (YouTube organic strategy, video formula, expectations) as the channel plansnappy-ads -- receives Week 5 (account setup, creative, targeting, launching, scaling) as the ad systemsnappy-ops -- receives Week 6 (CEO daily workflow, member ops, financial ops, team ops) as the operating systemsnappy-content -- receives all weeks as the source material for blog posts, emails, and videossnappy-blog -- receives all weeks as content seeds for long-form articlessnappy-knowledge -- receives student progress data (which weeks members have completed) for trackingChannels (where output is delivered):
snappy-skool (Skool classroom)snappy-blog, snappy-email, snappy-linkedin, snappy-youtubeOrchestrator:
snappy-ops references this skill during weekly content planning, sales call prep, and offer reviewssnappy-skool references this skill when scheduling weekly module releases to mastermind members| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. Vision | End goal, principles, intro to group | 27:44 | n/a (philosophy) |
| 2. Model | Two-step mastermind, traffic engine, math | 14:49 | snappy-offer |
| 3. Offer | Niche, problems, solutions, mechanics, pricing | 38:05 | snappy-offer |
| 4. Mindset | Biological, psychological, relationships, purpose, virtues | 17:49 | n/a (personal) |
| 5. Converting to new model | Transition path from existing business | 24:52 | snappy-offer |
Detailed: week1-detailed.md
| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. Launching a mastermind | Pre-launch audit, private launch, beta | 22:48 | snappy-sales |
| 2. Launch funnel | War map planner, 14-day teaser, enrollment waves | 40:49 | snappy-sales |
| 3. Opportunity funnel | Warm-audience promotion, ongoing | 37:58 | snappy-sales |
| 4. Sales call formula | Daily prep, structure, objection handling | 30:50 | snappy-sales |
| 5. Sales call tracking | Daily logging, KPIs, pipeline | 7:13 | snappy-sales |
| 6. Sales call preparation | Buyer types, seller mindset, deep prep | 54:35 | snappy-sales |
Detailed: week2-detailed.md
| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. Mastermind philosophy | Why masterminds beat courses | 23:49 | snappy-skool |
| 2. Skool group and tools | Platform setup, 40% MRR commissions | 44:16 | snappy-skool |
| 3. Frontend mastermind | Lower-ticket entry tier, conversion path | 26:19 | snappy-skool |
| 4. Backend mastermind | Higher-ticket, events, 5 elements | 36:48 | snappy-skool |
Detailed: week3-detailed.md
| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. Traffic engine | How site/email/YT/VSL work in concert | 4:48 | all of W4 skills |
| 2. Website | 6 pages, 4 goals, Figma-first design | 11:38 | snappy-website |
| 3. Email newsletter | 3+/wk cadence, 30-min workflow, 10-20% opens | 28:31 | snappy-email |
| 4. YouTube channel | 1 video/wk, 2yr commitment, video formula | 30:27 | snappy-youtube |
| 5. VSL funnel | 4 pages, ClickFunnels + Calendly + ActiveCampaign + Zapier | 39:29 | snappy-website, snappy-ads |
Detailed: week4-detailed.md
| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. YouTube ads overview | Funnel flow, budget rule, KPIs | 30:06 | snappy-ads |
| 2. Account setup | Google Ads Manager, Analytics, Tag Manager, Hyros | 30:23 | snappy-ads |
| 3. Creative | 80/20 rule, hook/story/close, separate upload account | 30:00 | snappy-ads |
| 4. Targeting | Targeting timeline, remarketing, audiences, keywords | 43:04 | snappy-ads |
| 5. Launching | Campaign/Ad Group/Ad structure, conversion tags | 45:34 | snappy-ads |
| 6. Testing/optimizing/scaling | 14-day windows, CPL <$25, CP-Call <$250, 3 scaling types | 44:33 | snappy-ads |
| 7. Bonus | Search, Discovery, Performance Max | 6:17 | snappy-ads |
| 8. Targeting Guide 2023 | Updated targeting deep-dive | 47:05 | snappy-ads |
| 9. Ad Disapprovals | Appeal process and prevention | 15:32 | snappy-ads |
Detailed: week5-detailed.md
| lesson | covers | duration | operationalized in |
|---|---|---|---|
| 1. Operations philosophy | Machine-like ops, 5 pillars | 26:46 | snappy-ops |
| 2. CEO daily workflow | 6 categories: cashflow, ops, mgmt, product, strategy | 20:00 | snappy-ops |
| 3. Mastermind member ops | Close.com + Helpscout pipeline | 29:47 | snappy-clients, snappy-skool |
| 4. Financial operations | 4 revenue sources, churn, LTV, CAC | 11:28 | snappy-freshbooks |
| 5. Team operations | Standups, hiring, profit share, lean team | 19:48 | snappy-ops |
Detailed: week6-detailed.md
The playbook is the theory. These skills operationalize it:
| playbook week | topic | operationalized in | what the skill does |
|---|---|---|---|
| Week 1 | Model, offer, pricing | snappy-offer |
Live offer definition, tier structure, member cap |
| Week 2 | Launch + sales | snappy-sales |
Sales scripts, pipeline tracking, objection handling |
| Week 3 | Mastermind community | snappy-skool |
Skool group ops, member experience, classroom delivery |
| Week 4 | snappy-email |
3x/wk newsletter, nurture sequences, list growth | |
| Week 4 | Website | snappy-website |
snappy.ai pages, landing pages, blog hub |
| Week 4 | YouTube organic | snappy-youtube |
Channel content, scripts, publishing |
| Week 4 | VSL funnel | snappy-website+snappy-ads |
ClickFunnels pages + ActiveCampaign automation |
| Week 5 | YouTube ads | snappy-ads |
Google Ads campaigns, creative, targeting, scaling |
| Week 6 | CEO + ops | snappy-ops |
Daily/weekly rhythm, financial ops, team |
Decision rule:
snappy-offer.Access live course content via snappy-browse (auth state file in snappy-infra/auth-reference.md Section 4):
bashagent-browser --state ~/.openclaw/workspace/skool-auth.json open <lesson-url>
agent-browser eval "document.querySelector('[class*=Content]')?.innerText || document.body.innerText"
agent-browser screenshot /tmp/lesson.png
Course Google Doc resources:
Key concepts by week (one-line cheat sheet):
| week | takeaway |
|---|---|
| W1 | Two-step mastermind (frontend feeds backend), niche-driven offer, balance/harmony mindset |
| W2 | Pre-launch audit, war-map planner, 14-day teaser, sales call formula, daily prep |
| W3 | Mastermind > course (collab not consumption), Skool platform (40% MRR), 5 backend elements |
| W4 | Traffic engine = site + email + YT + VSL working in concert; 3+/wk emails; 1+/wk videos; 2yr horizon |
| W5 | 80/20 rule (creative > targeting), hook/story/close, 14-day testing, CPL<$25 / CP-Call<$250 |
| W6 | 6-category CEO daily workflow, Close+Helpscout, 4 revenue sources, lean profit-share team |
| topic | wrong | correct |
|---|---|---|
| Offer scope | Treating it as a course with fixed lessons | Mastermind = recurring, implementation-focused, peer-driven |
| Launch path | Always using Launch Funnel | Existing audience -> Opportunity Funnel; cold audience -> Launch Funnel |
| Email cadence | "Send when inspired" | 3+ per week, scheduled on War Map, 30 min/email max |
| YouTube horizon | "6 months of effort, see results" | 2+ years minimum commitment before significant returns |
| Ad budget | "Start with $500/mo" | Adspend >= product price (if $3k offer, spend $3k+/mo) |
| Ad attribution | Trusting Google Ads numbers | Use Hyros for true attribution and profit tracking |
| CEO daily focus | Only operations | 6 categories: cashflow, contributors, ops, mgmt, product, strategy |
| need | read |
|---|---|
| Week 1 detailed (model, offer, mindset, conversion) | week1-detailed.md |
| Week 2 detailed (launch, beta, sales call formula) | week2-detailed.md |
| Week 3 detailed (mastermind community delivery) | week3-detailed.md |
| Week 4 detailed (traffic engine: site + email + YT + VSL) | week4-detailed.md |
| Week 5 detailed (YouTube ads end-to-end) | week5-detailed.md |
| Week 6 detailed (CEO daily, member, financial, team ops) | week6-detailed.md |
| Quick overview Weeks 1-3 (foundation) | foundation.md |
| Quick overview Weeks 4-6 (execution) | execution.md |
snappy-offer -- Week 1 operationalized: live offer definition, pricing tiers, ICPsnappy-sales -- Week 2 operationalized: call framework, funnels, pipeline, lead-to-closesnappy-skool -- Week 3 operationalized: Skool classroom, frontend, member ops, monetizationsnappy-email -- Week 4 operationalized: newsletter automation, list management, templatessnappy-website -- Week 4 operationalized: snappy.ai site structure and copysnappy-youtube -- Week 4 operationalized: YouTube organic channel content and opssnappy-ads -- Week 5 operationalized: Google Ads campaigns + Hyros trackingsnappy-ops -- Week 6 operationalized: CEO daily/weekly rhythm + orchestrationsnappy-content -- pulls voice and topic seeds from playbook lessonssnappy-blog -- long-form articles seeded from playbook frameworkssnappy-knowledge -- tracks which mastermind members have completed which weekssnappy-browse -- agent-browser CLI used to fetch live Skool lesson contentsnappy-infra -- auth state file location for Skool browser sessionsSkill Status: COMPLETE
Skills whose description overlaps this one enough that a reader could pick the
wrong door. Each row is that skill's own first sentence about itself, so the
choice is made on its words, not on a summary written here.
| Skill | Reach for it instead when |
|---|---|
snappy-analytics |
Centralized analytics and metrics for the entire Snappy operating system. |
snappy-course |
Orchestrator for the free agentic-building course. |
snappy-telegram |
Telegram Bot API channel for Snappy: direct calls to api.telegram.org (no Xano middleware) to… |
snappy-transcripts |
Transcript retrieval, search, and processing for Snappy. |
---
name: snappy-playbook
reports_to: money
head: false
description: >
WeTube SS mastermind 6-week curriculum source. Sam Ovens course playbook covering vision,
business model, offer definition, pricing, mindset, launch funnel, opportunity funnel,
sales call formula, mastermind community delivery, traffic engine, website, email newsletter,
YouTube organic, VSL funnel, YouTube ads, CEO daily workflow, member ops, financial ops,
team ops. Use when building or refining the Snappy offer, writing sales scripts, designing
funnels, planning content, structuring the Skool community, running ads, or operating the
CEO daily routine. The transformation promise the mastermind delivers.
SOURCE CURRICULUM (the Sam Ovens material itself) -- NOT Snappy's own current offer and
positioning model, which lives in snappy-mastermind-model. Use this for the course content;
use that one for what Snappy actually sells today.
---
**Triggers on:** snappy-playbook, playbook
# Snappy Playbook (WeTube SS Curriculum)
## Purpose
Sam Ovens' WeTube SS mastermind 6-week course is the **curriculum source** for the Snappy mastermind. snappy-skool delivers it weekly. snappy-offer references it as the value stack. snappy-sales uses it as the transformation promise on calls. This skill is the canonical theory layer -- every operationalized snappy-* skill (offer, sales, community, email, website, youtube, ads, ops) maps back to a week here.
**Course:** https://www.skool.com/wetube-ss-8782/classroom
**Progress:** 30%
## When to Use This Skill
Auto-activate when the user is:
- Defining or refining the Snappy offer, model, member cap, or pricing tiers
- Writing the value stack for sales calls or landing pages
- Building a launch funnel, opportunity funnel, or VSL funnel
- Drafting sales call scripts, objection handling, or pre-call prep
- Setting up the Skool group, classroom, calendar, or events
- Planning the email newsletter cadence or writing nurture sequences
- Setting up YouTube organic content, channel branding, or video formulas
- Running YouTube ads (account setup, creative, targeting, scaling)
- Establishing the CEO daily workflow or operational rhythm
- Structuring member ops, financial ops, or team ops
- Looking for the **transformation promise** to use in copy, sales, or content
If the question is "what does Sam Ovens say to do here?" -- this is the skill.
## Quick Start
|step|action|read|
|----|------|----|
|1|Identify which week covers the topic|Course Map below|
|2|Read the weekly module with inputs/outputs|`weekN-detailed.md`|
|3|Find the operationalized skill|`Cross-Skill Mapping` table|
|4|Execute the task in that skill|`snappy-X`|
**Decision tree:**
```
Need offer/model/pricing? -> Week 1 -> snappy-offer
Need launch/funnel/sales script? -> Week 2 -> snappy-sales
Need community/Skool/delivery? -> Week 3 -> snappy-skool
Need email/website/YouTube/VSL? -> Week 4 -> snappy-email|website|youtube
Need YouTube ads (any aspect)? -> Week 5 -> snappy-ads
Need CEO workflow/ops/team? -> Week 6 -> snappy-ops
Want a quick overview? -> foundation.md (W1-3) | execution.md (W4-6)
```
## Workflow
**Inputs (skills that feed this one):**
- `snappy-browse` -- provides agent-browser CLI to fetch live lesson content from Skool
- `snappy-infra` -- provides Skool auth state file path (`auth-reference.md` Section 4)
**Outputs (skills that consume this one):**
- `snappy-offer` -- receives Week 1 (model, offer, pricing, mindset) as the offer definition source
- `snappy-sales` -- receives Week 2 (launch funnel, opportunity funnel, sales call formula, prep) as the sales playbook
- `snappy-skool` -- receives Week 3 (mastermind philosophy, Skool setup, frontend/backend) as the delivery framework
- `snappy-email` -- receives Week 4 (email newsletter cadence, 30-min workflow, KPIs) as the email strategy
- `snappy-website` -- receives Week 4 (website goals, page structure, design rules) as the site brief
- `snappy-youtube` -- receives Week 4 (YouTube organic strategy, video formula, expectations) as the channel plan
- `snappy-ads` -- receives Week 5 (account setup, creative, targeting, launching, scaling) as the ad system
- `snappy-ops` -- receives Week 6 (CEO daily workflow, member ops, financial ops, team ops) as the operating system
- `snappy-content` -- receives all weeks as the source material for blog posts, emails, and videos
- `snappy-blog` -- receives all weeks as content seeds for long-form articles
- `snappy-knowledge` -- receives student progress data (which weeks members have completed) for tracking
**Channels (where output is delivered):**
- Curriculum delivery happens through `snappy-skool` (Skool classroom)
- Content seeded from playbook lessons flows through `snappy-blog`, `snappy-email`, `snappy-linkedin`, `snappy-youtube`
**Orchestrator:**
- `snappy-ops` references this skill during weekly content planning, sales call prep, and offer reviews
- `snappy-skool` references this skill when scheduling weekly module releases to mastermind members
## Course Map
### Week 1 -- Model, Offer, and Mindset (Foundation)
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. Vision|End goal, principles, intro to group|27:44|n/a (philosophy)|
|2. Model|Two-step mastermind, traffic engine, math|14:49|`snappy-offer`|
|3. Offer|Niche, problems, solutions, mechanics, pricing|38:05|`snappy-offer`|
|4. Mindset|Biological, psychological, relationships, purpose, virtues|17:49|n/a (personal)|
|5. Converting to new model|Transition path from existing business|24:52|`snappy-offer`|
Detailed: [week1-detailed.md](week1-detailed.md)
### Week 2 -- Launch, Beta, and Sales
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. Launching a mastermind|Pre-launch audit, private launch, beta|22:48|`snappy-sales`|
|2. Launch funnel|War map planner, 14-day teaser, enrollment waves|40:49|`snappy-sales`|
|3. Opportunity funnel|Warm-audience promotion, ongoing|37:58|`snappy-sales`|
|4. Sales call formula|Daily prep, structure, objection handling|30:50|`snappy-sales`|
|5. Sales call tracking|Daily logging, KPIs, pipeline|7:13|`snappy-sales`|
|6. Sales call preparation|Buyer types, seller mindset, deep prep|54:35|`snappy-sales`|
Detailed: [week2-detailed.md](week2-detailed.md)
### Week 3 -- Making a Mastermind
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. Mastermind philosophy|Why masterminds beat courses|23:49|`snappy-skool`|
|2. Skool group and tools|Platform setup, 40% MRR commissions|44:16|`snappy-skool`|
|3. Frontend mastermind|Lower-ticket entry tier, conversion path|26:19|`snappy-skool`|
|4. Backend mastermind|Higher-ticket, events, 5 elements|36:48|`snappy-skool`|
Detailed: [week3-detailed.md](week3-detailed.md)
### Week 4 -- Funnel, Email, and Organic
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. Traffic engine|How site/email/YT/VSL work in concert|4:48|all of W4 skills|
|2. Website|6 pages, 4 goals, Figma-first design|11:38|`snappy-website`|
|3. Email newsletter|3+/wk cadence, 30-min workflow, 10-20% opens|28:31|`snappy-email`|
|4. YouTube channel|1 video/wk, 2yr commitment, video formula|30:27|`snappy-youtube`|
|5. VSL funnel|4 pages, ClickFunnels + Calendly + ActiveCampaign + Zapier|39:29|`snappy-website`, `snappy-ads`|
Detailed: [week4-detailed.md](week4-detailed.md)
### Week 5 -- YouTube Ads
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. YouTube ads overview|Funnel flow, budget rule, KPIs|30:06|`snappy-ads`|
|2. Account setup|Google Ads Manager, Analytics, Tag Manager, Hyros|30:23|`snappy-ads`|
|3. Creative|80/20 rule, hook/story/close, separate upload account|30:00|`snappy-ads`|
|4. Targeting|Targeting timeline, remarketing, audiences, keywords|43:04|`snappy-ads`|
|5. Launching|Campaign/Ad Group/Ad structure, conversion tags|45:34|`snappy-ads`|
|6. Testing/optimizing/scaling|14-day windows, CPL <$25, CP-Call <$250, 3 scaling types|44:33|`snappy-ads`|
|7. Bonus|Search, Discovery, Performance Max|6:17|`snappy-ads`|
|8. Targeting Guide 2023|Updated targeting deep-dive|47:05|`snappy-ads`|
|9. Ad Disapprovals|Appeal process and prevention|15:32|`snappy-ads`|
Detailed: [week5-detailed.md](week5-detailed.md)
### Week 6 -- Fine-tuning Operations
|lesson|covers|duration|operationalized in|
|------|------|--------|------------------|
|1. Operations philosophy|Machine-like ops, 5 pillars|26:46|`snappy-ops`|
|2. CEO daily workflow|6 categories: cashflow, ops, mgmt, product, strategy|20:00|`snappy-ops`|
|3. Mastermind member ops|Close.com + Helpscout pipeline|29:47|`snappy-clients`, `snappy-skool`|
|4. Financial operations|4 revenue sources, churn, LTV, CAC|11:28|`snappy-freshbooks`|
|5. Team operations|Standups, hiring, profit share, lean team|19:48|`snappy-ops`|
Detailed: [week6-detailed.md](week6-detailed.md)
## Cross-Skill Mapping
The playbook is the theory. These skills operationalize it:
|playbook week|topic|operationalized in|what the skill does|
|-------------|-----|------------------|-------------------|
|Week 1|Model, offer, pricing|`snappy-offer`|Live offer definition, tier structure, member cap|
|Week 2|Launch + sales|`snappy-sales`|Sales scripts, pipeline tracking, objection handling|
|Week 3|Mastermind community|`snappy-skool`|Skool group ops, member experience, classroom delivery|
|Week 4|Email|`snappy-email`|3x/wk newsletter, nurture sequences, list growth|
|Week 4|Website|`snappy-website`|snappy.ai pages, landing pages, blog hub|
|Week 4|YouTube organic|`snappy-youtube`|Channel content, scripts, publishing|
|Week 4|VSL funnel|`snappy-website`+`snappy-ads`|ClickFunnels pages + ActiveCampaign automation|
|Week 5|YouTube ads|`snappy-ads`|Google Ads campaigns, creative, targeting, scaling|
|Week 6|CEO + ops|`snappy-ops`|Daily/weekly rhythm, financial ops, team|
**Decision rule:**
- Need the *theory or framework*? Read the weekly module here.
- Need to *execute now*? Use the operationalized skill.
- Example: "How should the offer be structured?" -> [week1-detailed.md](week1-detailed.md). "Update the live offer" -> `snappy-offer`.
## Quick Reference
**Access live course content via snappy-browse** (auth state file in `snappy-infra/auth-reference.md` Section 4):
```bash
agent-browser --state ~/.openclaw/workspace/skool-auth.json open <lesson-url>
agent-browser eval "document.querySelector('[class*=Content]')?.innerText || document.body.innerText"
agent-browser screenshot /tmp/lesson.png
```
**Course Google Doc resources:**
- [VSL Funnel Template](https://docs.google.com/document/d/1Y56HUl13MnevdBE5MLzvjTsGbWXMNRfa6BFyRvie--8/edit?usp=sharing)
- [VSL Email Templates](https://docs.google.com/document/d/1BlNaRuGtx6nM7pos9ET0G8qjdKSsXC3dMOfOyKZjWuY/edit?usp=sharing)
**Key concepts by week (one-line cheat sheet):**
|week|takeaway|
|----|--------|
|W1|Two-step mastermind (frontend feeds backend), niche-driven offer, balance/harmony mindset|
|W2|Pre-launch audit, war-map planner, 14-day teaser, sales call formula, daily prep|
|W3|Mastermind > course (collab not consumption), Skool platform (40% MRR), 5 backend elements|
|W4|Traffic engine = site + email + YT + VSL working in concert; 3+/wk emails; 1+/wk videos; 2yr horizon|
|W5|80/20 rule (creative > targeting), hook/story/close, 14-day testing, CPL<$25 / CP-Call<$250|
|W6|6-category CEO daily workflow, Close+Helpscout, 4 revenue sources, lean profit-share team|
## Common Mistakes (AI Agents Get These Wrong)
|topic|wrong|correct|
|-----|-----|-------|
|Offer scope|Treating it as a course with fixed lessons|Mastermind = recurring, implementation-focused, peer-driven|
|Launch path|Always using Launch Funnel|Existing audience -> Opportunity Funnel; cold audience -> Launch Funnel|
|Email cadence|"Send when inspired"|3+ per week, scheduled on War Map, 30 min/email max|
|YouTube horizon|"6 months of effort, see results"|2+ years minimum commitment before significant returns|
|Ad budget|"Start with $500/mo"|Adspend >= product price (if $3k offer, spend $3k+/mo)|
|Ad attribution|Trusting Google Ads numbers|Use Hyros for true attribution and profit tracking|
|CEO daily focus|Only operations|6 categories: cashflow, contributors, ops, mgmt, product, strategy|
## Navigation Guide
|need|read|
|----|----|
|Week 1 detailed (model, offer, mindset, conversion)|[week1-detailed.md](week1-detailed.md)|
|Week 2 detailed (launch, beta, sales call formula)|[week2-detailed.md](week2-detailed.md)|
|Week 3 detailed (mastermind community delivery)|[week3-detailed.md](week3-detailed.md)|
|Week 4 detailed (traffic engine: site + email + YT + VSL)|[week4-detailed.md](week4-detailed.md)|
|Week 5 detailed (YouTube ads end-to-end)|[week5-detailed.md](week5-detailed.md)|
|Week 6 detailed (CEO daily, member, financial, team ops)|[week6-detailed.md](week6-detailed.md)|
|Quick overview Weeks 1-3 (foundation)|[foundation.md](foundation.md)|
|Quick overview Weeks 4-6 (execution)|[execution.md](execution.md)|
## Related Skills
- `snappy-offer` -- Week 1 operationalized: live offer definition, pricing tiers, ICP
- `snappy-sales` -- Week 2 operationalized: call framework, funnels, pipeline, lead-to-close
- `snappy-skool` -- Week 3 operationalized: Skool classroom, frontend, member ops, monetization
- `snappy-email` -- Week 4 operationalized: newsletter automation, list management, templates
- `snappy-website` -- Week 4 operationalized: snappy.ai site structure and copy
- `snappy-youtube` -- Week 4 operationalized: YouTube organic channel content and ops
- `snappy-ads` -- Week 5 operationalized: Google Ads campaigns + Hyros tracking
- `snappy-ops` -- Week 6 operationalized: CEO daily/weekly rhythm + orchestration
- `snappy-content` -- pulls voice and topic seeds from playbook lessons
- `snappy-blog` -- long-form articles seeded from playbook frameworks
- `snappy-knowledge` -- tracks which mastermind members have completed which weeks
- `snappy-browse` -- agent-browser CLI used to fetch live Skool lesson content
- `snappy-infra` -- auth state file location for Skool browser sessions
**Skill Status**: COMPLETE
## Near neighbours
Skills whose description overlaps this one enough that a reader could pick the
wrong door. Each row is that skill's own first sentence about itself, so the
choice is made on its words, not on a summary written here.
| Skill | Reach for it instead when |
|---|---|
| `snappy-analytics` | Centralized analytics and metrics for the entire Snappy operating system. |
| `snappy-course` | Orchestrator for the free agentic-building course. |
| `snappy-telegram` | Telegram Bot API channel for Snappy: direct calls to api.telegram.org (no Xano middleware) to… |
| `snappy-transcripts` | Transcript retrieval, search, and processing for Snappy. |
#!/usr/bin/env npx tsx
/**
* snappy-playbook/api.ts -- WeTube SS mastermind 6-week curriculum structure.
*
* Reads from local SKILL.md and weekN-detailed.md files. Pure data skill.
*
* Usage:
* npx tsx api.ts weeks # 6-week curriculum overview
* npx tsx api.ts week <num> # specific week detail
*
* Or import as module:
* import { getWeeks, getWeek } from "../snappy-playbook/api.ts";
*/
import { existsSync, readFileSync, realpathSync } from "fs";
import { join, dirname } from "path";
import { fileURLToPath } from "url";
import { env } from "../snappy-settings/load.ts";
import { annotationsForClass } from "../snappy-settings/tool-annotations.ts";
import { printRefusal, refuse, refusalTable } from "../snappy-settings/refusal-codes.ts";
const SKILL_DIR = dirname(fileURLToPath(import.meta.url));
interface Lesson {
title: string;
covers: string;
duration: string;
operationalizedIn: string;
}
interface Week {
number: number;
title: string;
lessons: Lesson[];
detailedFile: string;
}
const WEEKS: Week[] = [
{
number: 1,
title: "Model, Offer, and Mindset (Foundation)",
lessons: [
{ title: "Vision", covers: "End goal, principles, intro to group", duration: "27:44", operationalizedIn: "n/a (philosophy)" },
{ title: "Model", covers: "Two-step mastermind, traffic engine, math", duration: "14:49", operationalizedIn: "snappy-offer" },
{ title: "Offer", covers: "Niche, problems, solutions, mechanics, pricing", duration: "38:05", operationalizedIn: "snappy-offer" },
{ title: "Mindset", covers: "Biological, psychological, relationships, purpose, virtues", duration: "17:49", operationalizedIn: "n/a (personal)" },
{ title: "Converting to new model", covers: "Transition path from existing business", duration: "24:52", operationalizedIn: "snappy-offer" },
],
detailedFile: "week1-detailed.md",
},
{
number: 2,
title: "Launch, Beta, and Sales",
lessons: [
{ title: "Launching a mastermind", covers: "Pre-launch audit, private launch, beta", duration: "22:48", operationalizedIn: "snappy-sales" },
{ title: "Launch funnel", covers: "War map planner, 14-day teaser, enrollment waves", duration: "40:49", operationalizedIn: "snappy-sales" },
{ title: "Opportunity funnel", covers: "Warm-audience promotion, ongoing", duration: "37:58", operationalizedIn: "snappy-sales" },
{ title: "Sales call formula", covers: "Daily prep, structure, objection handling", duration: "30:50", operationalizedIn: "snappy-sales" },
{ title: "Sales call tracking", covers: "Daily logging, KPIs, pipeline", duration: "7:13", operationalizedIn: "snappy-sales" },
{ title: "Sales call preparation", covers: "Buyer types, seller mindset, deep prep", duration: "54:35", operationalizedIn: "snappy-sales" },
],
detailedFile: "week2-detailed.md",
},
{
number: 3,
title: "Making a Mastermind",
lessons: [
{ title: "Mastermind philosophy", covers: "Why masterminds beat courses", duration: "23:49", operationalizedIn: "snappy-skool" },
{ title: "Skool group and tools", covers: "Platform setup, 40% MRR commissions", duration: "44:16", operationalizedIn: "snappy-skool" },
{ title: "Frontend mastermind", covers: "Lower-ticket entry tier, conversion path", duration: "26:19", operationalizedIn: "snappy-skool" },
{ title: "Backend mastermind", covers: "Higher-ticket, events, 5 elements", duration: "36:48", operationalizedIn: "snappy-skool" },
],
detailedFile: "week3-detailed.md",
},
{
number: 4,
title: "Funnel, Email, and Organic",
lessons: [
{ title: "Traffic engine", covers: "How site/email/YT/VSL work in concert", duration: "4:48", operationalizedIn: "all of W4 skills" },
{ title: "Website", covers: "6 pages, 4 goals, Figma-first design", duration: "11:38", operationalizedIn: "snappy-website" },
{ title: "Email newsletter", covers: "3+/wk cadence, 30-min workflow, 10-20% opens", duration: "28:31", operationalizedIn: "snappy-email" },
{ title: "YouTube channel", covers: "1 video/wk, 2yr commitment, video formula", duration: "30:27", operationalizedIn: "snappy-youtube" },
{ title: "VSL funnel", covers: "4 pages, ClickFunnels + Calendly + AC + Zapier", duration: "39:29", operationalizedIn: "snappy-website, snappy-ads" },
],
detailedFile: "week4-detailed.md",
},
{
number: 5,
title: "YouTube Ads",
lessons: [
{ title: "YouTube ads overview", covers: "Funnel flow, budget rule, KPIs", duration: "30:06", operationalizedIn: "snappy-ads" },
{ title: "Account setup", covers: "Google Ads Manager, Analytics, Tag Manager, Hyros", duration: "30:23", operationalizedIn: "snappy-ads" },
{ title: "Creative", covers: "80/20 rule, hook/story/close, separate upload account", duration: "30:00", operationalizedIn: "snappy-ads" },
{ title: "Targeting", covers: "Targeting timeline, remarketing, audiences, keywords", duration: "43:04", operationalizedIn: "snappy-ads" },
{ title: "Launching", covers: "Campaign/Ad Group/Ad structure, conversion tags", duration: "45:34", operationalizedIn: "snappy-ads" },
{ title: "Testing/optimizing/scaling", covers: "14-day windows, CPL <$25, CP-Call <$250, 3 scaling types", duration: "44:33", operationalizedIn: "snappy-ads" },
{ title: "Bonus", covers: "Search, Discovery, Performance Max", duration: "6:17", operationalizedIn: "snappy-ads" },
{ title: "Targeting Guide 2023", covers: "Updated targeting deep-dive", duration: "47:05", operationalizedIn: "snappy-ads" },
{ title: "Ad Disapprovals", covers: "Appeal process and prevention", duration: "15:32", operationalizedIn: "snappy-ads" },
],
detailedFile: "week5-detailed.md",
},
{
number: 6,
title: "Fine-tuning Operations",
lessons: [
{ title: "Operations philosophy", covers: "Machine-like ops, 5 pillars", duration: "26:46", operationalizedIn: "snappy-ops" },
{ title: "CEO daily workflow", covers: "6 categories: cashflow, ops, mgmt, product, strategy", duration: "20:00", operationalizedIn: "snappy-ops" },
{ title: "Mastermind member ops", covers: "Close.com + Helpscout pipeline", duration: "29:47", operationalizedIn: "snappy-clients, snappy-skool" },
{ title: "Financial operations", covers: "4 revenue sources, churn, LTV, CAC", duration: "11:28", operationalizedIn: "snappy-freshbooks" },
{ title: "Team operations", covers: "Standups, hiring, profit share, lean team", duration: "19:48", operationalizedIn: "snappy-ops" },
],
detailedFile: "week6-detailed.md",
},
];
// --- Public API ---
export function getWeeks(): Week[] {
return WEEKS;
}
export function getWeek(num: number): Week | null {
return WEEKS.find((w) => w.number === num) || null;
}
export function getWeekDetailed(num: number): string | null {
const week = getWeek(num);
if (!week) return null;
const path = join(SKILL_DIR, week.detailedFile);
if (!existsSync(path)) return null;
return readFileSync(path, "utf-8");
}
// --- CLI ---
/** WHAT THIS HAND ANSWERS, and what each verb does to the world.
* Derived from this file's own CLI dispatch by
* `snappy-hands/contract-derive.ts` — a verb the code does not implement is
* never declared here. Snappy's daemon reads it (`api.ts contract`) to
* validate every call, build the argument words in order, decide whether the
* act runs now or stages for the owner, and hand the child exactly the
* environment keys named in `requires` — never a value, never anything else.
*/
/** THE HOST-FACING FACTS ⟨lane CONTRACTS N–Z, 2026-09-09⟩. `class` is the
* closed effect set snappy-tool-design rule 18 grades; `annotations` are
* DERIVED from it by the ONE derivation in
* `snappy-settings/tool-annotations.ts`, never written per verb, so a class
* and its published hints cannot disagree; `refusals` projects the ONE closed
* table in `snappy-settings/refusal-codes.ts`; `requires` is exactly the
* credential keys this file's own executable reads name, and nothing else. */
export const HAND_CONTRACT = {
skill: "snappy-playbook",
description: "WeTube SS mastermind 6-week curriculum source. Sam Ovens course playbook covering vision, business model, offer definition, pricing, mindset, launch funnel, opportunity funnel, sales call formula, mastermind community delivery, traffic engine, website, email newsletter, YouTube organic, VSL funnel, YouTube ads, CEO daily workflow, member ops, financial ops, team ops. Use when building or refining the Snappy offer, writing sales scripts, designing funnels, planning content, structuring the Skool community, running ads, or operating the CEO daily routine. The transformation promise the mastermind delivers. SOURCE CURRICULUM (the Sam Ovens material itself) -- NOT Snappy's own current offer and positioning model, which lives in snappy-mastermind-model. Use this for the course content; use that one for what Snappy actually sells today.",
managed: false,
requires: [] as string[],
refusals: refusalTable("unknown_verb"),
verbs: {
week: {
args: ["week-number?"], effect: "read", class: "read", execution: "call", openWorld: false,
annotations: annotationsForClass("read", { openWorld: false }),
inputSchema: { properties: { "week-number": { type: "integer", description: "Week number, 1 through 6", maximum: 6 } } },
},
weeks: {
args: [], effect: "read", class: "read", execution: "call", openWorld: false,
annotations: annotationsForClass("read", { openWorld: false }),
},
},
} as const;
if (import.meta.url === `file://${realpathSync(process.argv[1])}` && process.argv[2] === "contract") {
console.log(JSON.stringify(HAND_CONTRACT, null, 2));
process.exit(0);
}
if (import.meta.url === `file://${realpathSync(process.argv[1])}`) {
(async () => {
const [, , cmd, ...args] = process.argv;
switch (cmd) {
case "weeks": {
for (const w of WEEKS) {
console.log(`\nWeek ${w.number} -- ${w.title}`);
for (const l of w.lessons) {
console.log(` ${l.title} (${l.duration}) -> ${l.operationalizedIn}`);
}
}
break;
}
case "week": {
const num = parseInt(args[0], 10);
if (!num || num < 1 || num > 6) {
printRefusal(refuse("missing_argument", "week needs <1-6>; contract slice week.args = [number]"));
console.error("Usage: api.ts week <1-6>");
process.exit(1);
}
const w = getWeek(num)!;
console.log(`Week ${w.number} -- ${w.title}\n`);
for (const l of w.lessons) {
console.log(` ${l.title}`);
console.log(` Covers: ${l.covers}`);
console.log(` Duration: ${l.duration}`);
console.log(` Operationalized in: ${l.operationalizedIn}\n`);
}
const detailed = getWeekDetailed(num);
if (detailed) {
console.log(`\n--- Detailed notes (${w.detailedFile}) ---\n`);
console.log(detailed.slice(0, 3000));
}
break;
}
default:
console.log("Usage: npx tsx api.ts [weeks|week] ...");
}
})();
}
#!/usr/bin/env npx tsx
/**
* snappy-playbook/api.ts -- WeTube SS mastermind 6-week curriculum structure.
*
* Reads from local SKILL.md and weekN-detailed.md files. Pure data skill.
*
* Usage:
* npx tsx api.ts weeks # 6-week curriculum overview
* npx tsx api.ts week <num> # specific week detail
*
* Or import as module:
* import { getWeeks, getWeek } from "../snappy-playbook/api.ts";
*/
import { existsSync, readFileSync, realpathSync } from "fs";
import { join, dirname } from "path";
import { fileURLToPath } from "url";
import { env } from "../snappy-settings/load.ts";
import { annotationsForClass } from "../snappy-settings/tool-annotations.ts";
import { printRefusal, refuse, refusalTable } from "../snappy-settings/refusal-codes.ts";
const SKILL_DIR = dirname(fileURLToPath(import.meta.url));
interface Lesson {
title: string;
covers: string;
duration: string;
operationalizedIn: string;
}
interface Week {
number: number;
title: string;
lessons: Lesson[];
detailedFile: string;
}
const WEEKS: Week[] = [
{
number: 1,
title: "Model, Offer, and Mindset (Foundation)",
lessons: [
{ title: "Vision", covers: "End goal, principles, intro to group", duration: "27:44", operationalizedIn: "n/a (philosophy)" },
{ title: "Model", covers: "Two-step mastermind, traffic engine, math", duration: "14:49", operationalizedIn: "snappy-offer" },
{ title: "Offer", covers: "Niche, problems, solutions, mechanics, pricing", duration: "38:05", operationalizedIn: "snappy-offer" },
{ title: "Mindset", covers: "Biological, psychological, relationships, purpose, virtues", duration: "17:49", operationalizedIn: "n/a (personal)" },
{ title: "Converting to new model", covers: "Transition path from existing business", duration: "24:52", operationalizedIn: "snappy-offer" },
],
detailedFile: "week1-detailed.md",
},
{
number: 2,
title: "Launch, Beta, and Sales",
lessons: [
{ title: "Launching a mastermind", covers: "Pre-launch audit, private launch, beta", duration: "22:48", operationalizedIn: "snappy-sales" },
{ title: "Launch funnel", covers: "War map planner, 14-day teaser, enrollment waves", duration: "40:49", operationalizedIn: "snappy-sales" },
{ title: "Opportunity funnel", covers: "Warm-audience promotion, ongoing", duration: "37:58", operationalizedIn: "snappy-sales" },
{ title: "Sales call formula", covers: "Daily prep, structure, objection handling", duration: "30:50", operationalizedIn: "snappy-sales" },
{ title: "Sales call tracking", covers: "Daily logging, KPIs, pipeline", duration: "7:13", operationalizedIn: "snappy-sales" },
{ title: "Sales call preparation", covers: "Buyer types, seller mindset, deep prep", duration: "54:35", operationalizedIn: "snappy-sales" },
],
detailedFile: "week2-detailed.md",
},
{
number: 3,
title: "Making a Mastermind",
lessons: [
{ title: "Mastermind philosophy", covers: "Why masterminds beat courses", duration: "23:49", operationalizedIn: "snappy-skool" },
{ title: "Skool group and tools", covers: "Platform setup, 40% MRR commissions", duration: "44:16", operationalizedIn: "snappy-skool" },
{ title: "Frontend mastermind", covers: "Lower-ticket entry tier, conversion path", duration: "26:19", operationalizedIn: "snappy-skool" },
{ title: "Backend mastermind", covers: "Higher-ticket, events, 5 elements", duration: "36:48", operationalizedIn: "snappy-skool" },
],
detailedFile: "week3-detailed.md",
},
{
number: 4,
title: "Funnel, Email, and Organic",
lessons: [
{ title: "Traffic engine", covers: "How site/email/YT/VSL work in concert", duration: "4:48", operationalizedIn: "all of W4 skills" },
{ title: "Website", covers: "6 pages, 4 goals, Figma-first design", duration: "11:38", operationalizedIn: "snappy-website" },
{ title: "Email newsletter", covers: "3+/wk cadence, 30-min workflow, 10-20% opens", duration: "28:31", operationalizedIn: "snappy-email" },
{ title: "YouTube channel", covers: "1 video/wk, 2yr commitment, video formula", duration: "30:27", operationalizedIn: "snappy-youtube" },
{ title: "VSL funnel", covers: "4 pages, ClickFunnels + Calendly + AC + Zapier", duration: "39:29", operationalizedIn: "snappy-website, snappy-ads" },
],
detailedFile: "week4-detailed.md",
},
{
number: 5,
title: "YouTube Ads",
lessons: [
{ title: "YouTube ads overview", covers: "Funnel flow, budget rule, KPIs", duration: "30:06", operationalizedIn: "snappy-ads" },
{ title: "Account setup", covers: "Google Ads Manager, Analytics, Tag Manager, Hyros", duration: "30:23", operationalizedIn: "snappy-ads" },
{ title: "Creative", covers: "80/20 rule, hook/story/close, separate upload account", duration: "30:00", operationalizedIn: "snappy-ads" },
{ title: "Targeting", covers: "Targeting timeline, remarketing, audiences, keywords", duration: "43:04", operationalizedIn: "snappy-ads" },
{ title: "Launching", covers: "Campaign/Ad Group/Ad structure, conversion tags", duration: "45:34", operationalizedIn: "snappy-ads" },
{ title: "Testing/optimizing/scaling", covers: "14-day windows, CPL <$25, CP-Call <$250, 3 scaling types", duration: "44:33", operationalizedIn: "snappy-ads" },
{ title: "Bonus", covers: "Search, Discovery, Performance Max", duration: "6:17", operationalizedIn: "snappy-ads" },
{ title: "Targeting Guide 2023", covers: "Updated targeting deep-dive", duration: "47:05", operationalizedIn: "snappy-ads" },
{ title: "Ad Disapprovals", covers: "Appeal process and prevention", duration: "15:32", operationalizedIn: "snappy-ads" },
],
detailedFile: "week5-detailed.md",
},
{
number: 6,
title: "Fine-tuning Operations",
lessons: [
{ title: "Operations philosophy", covers: "Machine-like ops, 5 pillars", duration: "26:46", operationalizedIn: "snappy-ops" },
{ title: "CEO daily workflow", covers: "6 categories: cashflow, ops, mgmt, product, strategy", duration: "20:00", operationalizedIn: "snappy-ops" },
{ title: "Mastermind member ops", covers: "Close.com + Helpscout pipeline", duration: "29:47", operationalizedIn: "snappy-clients, snappy-skool" },
{ title: "Financial operations", covers: "4 revenue sources, churn, LTV, CAC", duration: "11:28", operationalizedIn: "snappy-freshbooks" },
{ title: "Team operations", covers: "Standups, hiring, profit share, lean team", duration: "19:48", operationalizedIn: "snappy-ops" },
],
detailedFile: "week6-detailed.md",
},
];
// --- Public API ---
export function getWeeks(): Week[] {
return WEEKS;
}
export function getWeek(num: number): Week | null {
return WEEKS.find((w) => w.number === num) || null;
}
export function getWeekDetailed(num: number): string | null {
const week = getWeek(num);
if (!week) return null;
const path = join(SKILL_DIR, week.detailedFile);
if (!existsSync(path)) return null;
return readFileSync(path, "utf-8");
}
// --- CLI ---
/** WHAT THIS HAND ANSWERS, and what each verb does to the world.
* Derived from this file's own CLI dispatch by
* `snappy-hands/contract-derive.ts` — a verb the code does not implement is
* never declared here. Snappy's daemon reads it (`api.ts contract`) to
* validate every call, build the argument words in order, decide whether the
* act runs now or stages for the owner, and hand the child exactly the
* environment keys named in `requires` — never a value, never anything else.
*/
/** THE HOST-FACING FACTS ⟨lane CONTRACTS N–Z, 2026-09-09⟩. `class` is the
* closed effect set snappy-tool-design rule 18 grades; `annotations` are
* DERIVED from it by the ONE derivation in
* `snappy-settings/tool-annotations.ts`, never written per verb, so a class
* and its published hints cannot disagree; `refusals` projects the ONE closed
* table in `snappy-settings/refusal-codes.ts`; `requires` is exactly the
* credential keys this file's own executable reads name, and nothing else. */
export const HAND_CONTRACT = {
skill: "snappy-playbook",
description: "WeTube SS mastermind 6-week curriculum source. Sam Ovens course playbook covering vision, business model, offer definition, pricing, mindset, launch funnel, opportunity funnel, sales call formula, mastermind community delivery, traffic engine, website, email newsletter, YouTube organic, VSL funnel, YouTube ads, CEO daily workflow, member ops, financial ops, team ops. Use when building or refining the Snappy offer, writing sales scripts, designing funnels, planning content, structuring the Skool community, running ads, or operating the CEO daily routine. The transformation promise the mastermind delivers. SOURCE CURRICULUM (the Sam Ovens material itself) -- NOT Snappy's own current offer and positioning model, which lives in snappy-mastermind-model. Use this for the course content; use that one for what Snappy actually sells today.",
managed: false,
requires: [] as string[],
refusals: refusalTable("unknown_verb"),
verbs: {
week: {
args: ["week-number?"], effect: "read", class: "read", execution: "call", openWorld: false,
annotations: annotationsForClass("read", { openWorld: false }),
inputSchema: { properties: { "week-number": { type: "integer", description: "Week number, 1 through 6", maximum: 6 } } },
},
weeks: {
args: [], effect: "read", class: "read", execution: "call", openWorld: false,
annotations: annotationsForClass("read", { openWorld: false }),
},
},
} as const;
if (import.meta.url === `file://${realpathSync(process.argv[1])}` && process.argv[2] === "contract") {
console.log(JSON.stringify(HAND_CONTRACT, null, 2));
process.exit(0);
}
if (import.meta.url === `file://${realpathSync(process.argv[1])}`) {
(async () => {
const [, , cmd, ...args] = process.argv;
switch (cmd) {
case "weeks": {
for (const w of WEEKS) {
console.log(`\nWeek ${w.number} -- ${w.title}`);
for (const l of w.lessons) {
console.log(` ${l.title} (${l.duration}) -> ${l.operationalizedIn}`);
}
}
break;
}
case "week": {
const num = parseInt(args[0], 10);
if (!num || num < 1 || num > 6) {
printRefusal(refuse("missing_argument", "week needs <1-6>; contract slice week.args = [number]"));
console.error("Usage: api.ts week <1-6>");
process.exit(1);
}
const w = getWeek(num)!;
console.log(`Week ${w.number} -- ${w.title}\n`);
for (const l of w.lessons) {
console.log(` ${l.title}`);
console.log(` Covers: ${l.covers}`);
console.log(` Duration: ${l.duration}`);
console.log(` Operationalized in: ${l.operationalizedIn}\n`);
}
const detailed = getWeekDetailed(num);
if (detailed) {
console.log(`\n--- Detailed notes (${w.detailedFile}) ---\n`);
console.log(detailed.slice(0, 3000));
}
break;
}
default:
console.log("Usage: npx tsx api.ts [weeks|week] ...");
}
})();
}
Quick overview of the execution weeks. For full detail, see weekN-detailed.md.
| state | description |
|---|---|
| INPUT | A live mastermind from Foundation (Weeks 1-3) but no traffic engine, no paid acquisition, no operating system, founder is the bottleneck |
| OUTPUT | Full traffic engine running (W4): website + email + YouTube organic + VSL funnel. Paid acquisition system (W5): Google Ads + Hyros + 14-day testing. Machine-like operations (W6): CEO daily workflow + Close.com + Helpscout + financial dashboards + team standups |
Operationalized in: snappy-website, snappy-email, snappy-youtube
Detailed: week4-detailed.md
Operationalized in: snappy-ads
Detailed: week5-detailed.md
Operationalized in: snappy-ops
Detailed: week6-detailed.md
# Execution (Weeks 4-6) Quick overview of the execution weeks. For full detail, see `weekN-detailed.md`. ## Execution Phase Inputs / Outputs |state|description| |-----|-----------| |**INPUT**|A live mastermind from Foundation (Weeks 1-3) but no traffic engine, no paid acquisition, no operating system, founder is the bottleneck| |**OUTPUT**|Full traffic engine running (W4): website + email + YouTube organic + VSL funnel. Paid acquisition system (W5): Google Ads + Hyros + 14-day testing. Machine-like operations (W6): CEO daily workflow + Close.com + Helpscout + financial dashboards + team standups| --- ## Week 4 -- Funnel, Email, and Organic **Operationalized in:** `snappy-website`, `snappy-email`, `snappy-youtube` ### 1. Traffic Engine - 4 components in concert: website -> email -> YouTube -> VSL - All roads lead to booked calls ### 2. Website - 4 goals: subs, emails, calls, clients - 6 page types (Home, Product, Newsletter, YouTube, About, Legal) - Figma-first design, consistency above all ### 3. Email Newsletter - 3+ emails/week minimum, plotted on War Map - 30-min idea-to-sent workflow - Target 10-20% opens, primary metric = calls generated ### 4. YouTube Channel - 1 video/week minimum, 2+ year horizon - Differentiation: mix personal interests with niche - Formula: Intro -> Bullets -> Prompts -> CTA ### 5. VSL Funnel - 4 pages in ClickFunnels: Optin -> Video -> Schedule -> Success - Calendly + ActiveCampaign + Zapier integration - Tag-based email automation triggers Detailed: [week4-detailed.md](week4-detailed.md) --- ## Week 5 -- YouTube Ads **Operationalized in:** `snappy-ads` ### 1. YouTube Ads Overview - Funnel: Ad -> Optin -> VSL -> Calendly -> Call -> Client - Budget rule: monthly adspend >= product price ### 2. Account Setup - Google Ads Manager + Account - Google Analytics + Tag Manager - Hyros for true profit attribution ### 3. Creative - 80/20 rule: creative is 80% of success - Hook -> Story -> Close script structure - Separate YouTube account for ad uploads ### 4. Targeting - Targeting Timeline (warm to cold progression) - Remarketing -> YouTube audiences -> Keywords -> Custom segments ### 5. Launching - Campaign -> Ad Group -> Ad structure - Verify conversion tags before going live ### 6. Testing, Optimizing, and Scaling - 14-day testing windows - CPL <$25, CP-Call <$250 - Scaling: vertical (budget), horizontal (audiences), creative (variations) ### 7-9. Bonus + Targeting Guide + Disapprovals - Search/Discovery/Performance Max - 2023+ targeting deep-dive - Handling and preventing ad disapprovals Detailed: [week5-detailed.md](week5-detailed.md) --- ## Week 6 -- Fine-Tuning Operations **Operationalized in:** `snappy-ops` ### 1. Operations Philosophy - Build systems that run predictably and repeatedly - 4 pillars: CEO daily, member ops, financial ops, team ops ### 2. CEO Daily Workflow - 6 categories: cashflow, contributors, ops, mgmt, product, strategy - Daily checklist that keeps everything moving ### 3. Mastermind Member Operations - Close.com for CRM (sales pipeline + customers) - Helpscout for member support - Workflow: lead -> call -> close -> onboard ### 4. Financial Operations - 4 revenue sources: frontend, backend, affiliate (40% MRR), upsells - Track churn, LTV, CAC by channel - Avoid early team overspend ### 5. Team Operations - Daily standup: priorities, blockers, progress - Lean team philosophy -- each person a multiplier - Profit-share model for retention Detailed: [week6-detailed.md](week6-detailed.md)
Quick overview of the foundational weeks. For full detail, see weekN-detailed.md.
| state | description |
|---|---|
| INPUT | An idea or existing business but no clearly defined mastermind, no live members, no community space |
| OUTPUT | A defined offer (W1), first beta members closed via sales calls (W2), live Skool group running with frontend + backend mastermind structure (W3) |
Operationalized in: snappy-offer
Detailed: week1-detailed.md
Operationalized in: snappy-sales
Detailed: week2-detailed.md
Operationalized in: snappy-skool
Detailed: week3-detailed.md
# Foundation (Weeks 1-3) Quick overview of the foundational weeks. For full detail, see `weekN-detailed.md`. ## Foundation Phase Inputs / Outputs |state|description| |-----|-----------| |**INPUT**|An idea or existing business but no clearly defined mastermind, no live members, no community space| |**OUTPUT**|A defined offer (W1), first beta members closed via sales calls (W2), live Skool group running with frontend + backend mastermind structure (W3)| --- ## Week 1 -- Model, Offer, and Mindset **Operationalized in:** `snappy-offer` ### 1. Vision - Sam's vision for the info industry and WeTube - Goal, model, guiding principles - Content releases and collaboration calls - **Action:** Introduce yourself to the group ### 2. Model - Two-step mastermind: high-ticket recurring revenue - Frontend (lower ticket) feeds Backend (higher ticket) - Aligned toward profit, client results, happiness ### 3. Offer - High-ticket info business owners scaling with email newsletters, YouTube organic, YouTube ads - Selling masterminds for recurring fees - 1-page Offer Mechanics worksheet (niche, problems, solutions, principles, price, member cap) ### 4. Mindset - Concentric circles: Biological -> Psychological -> Relationships -> Purpose -> Virtues - Self-paced, collaboration over consumption ### 5. Converting to the New Model - Convert existing course to frontend mastermind OR start fresh - Backend timing: only when frontend produces results Detailed: [week1-detailed.md](week1-detailed.md) --- ## Week 2 -- Launch, Beta, and Sales **Operationalized in:** `snappy-sales` ### 1. Launching a Mastermind - Pre-launch audit (existing assets) - Private launch to star students first - Backend -> Opportunity Funnel; Frontend -> Launch Funnel ### 2. Launch Funnel - War Map planner, 14-day teaser, enrollment waves - Multi-channel promotion ### 3. Opportunity Funnel - For warm audiences with existing context - Discover opportunities by observing the mastermind ### 4. Sales Call Formula - Daily prep + pre-call prep - Rapport > Discovery > Present > Close ### 5. Sales Call Tracking - Daily call log + KPI sheet (calls, show, close, revenue/call) ### 6. Sales Call Preparation - Buyer types, seller mindset, indicators/fundamentals/outcomes Detailed: [week2-detailed.md](week2-detailed.md) --- ## Week 3 -- Making a Mastermind **Operationalized in:** `snappy-skool` ### 1. Mastermind Philosophy - Implementation + collaboration > content consumption - Best masterminds feel like friends helping each other win ### 2. Skool Group and Tools - All-in-one platform (community, classroom, calendar) - 40% MRR affiliate commissions - Daily workflow: check, respond, engage, post ### 3. Frontend Mastermind - Lower-ticket entry tier - Feeds backend through results-based conversion ### 4. Backend Mastermind - 5 elements: instructions, community, collab calls, coaching, events - Live event logistics, prep, flow - Virtual event optimization Detailed: [week3-detailed.md](week3-detailed.md)
/**
* COVERAGE FOR SNAPPY-PLAYBOOK'S DECLARED REFUSAL CODES
* (snappy-tool-design rule 33: "refusal codes form one closed table and each
* row has coverage").
*
* Two things are graded here, and the second is the one that matters. The
* first is that the hand's table is a PROJECTION of the collection's one
* closed table in snappy-settings/refusal-codes.ts — same object, not a copy
* that can drift. The second is that every declared code is GROUNDED: the
* evidence that justified declaring it is re-checked here, because a refusal
* code with no path that emits it is a branch the reader waits for and never
* sees, and a table of those passes a lint while teaching a lie.
*
* The code list is spelled out rather than read from the contract: a test that
* iterates the thing it grades passes for an empty table.
*/
import { strict as assert } from "node:assert";
import { test } from "node:test";
import { readFileSync } from "node:fs";
import { join, dirname } from "node:path";
import { fileURLToPath } from "node:url";
import { HAND_CONTRACT } from "./api.ts";
import { REFUSAL_CODES } from "../snappy-settings/refusal-codes.ts";
const SOURCE = readFileSync(join(dirname(fileURLToPath(import.meta.url)), "api.ts"), "utf8");
/** Every refusal code snappy-playbook declares. */
const DECLARED = [
"unknown_verb",
] as const;
test("snappy-playbook declares exactly these refusal codes", () => {
assert.deepEqual(Object.keys(HAND_CONTRACT.refusals).sort(), [...DECLARED].sort());
});
test("every declared code is the SAME row as the one closed table's, never a copy", () => {
const table = HAND_CONTRACT.refusals as Record<string, unknown>;
for (const code of DECLARED) {
assert.equal(table[code], REFUSAL_CODES[code], `${code} is not the shared row`);
}
});
test("unknown_verb is grounded: the contract closes the verb set, so a word outside it is refusable", () => {
assert.ok(Object.keys(HAND_CONTRACT.verbs).length >= 0);
assert.ok(!Object.keys(HAND_CONTRACT.verbs).includes("no-such-verb"));
});
/**
* COVERAGE FOR SNAPPY-PLAYBOOK'S DECLARED REFUSAL CODES
* (snappy-tool-design rule 33: "refusal codes form one closed table and each
* row has coverage").
*
* Two things are graded here, and the second is the one that matters. The
* first is that the hand's table is a PROJECTION of the collection's one
* closed table in snappy-settings/refusal-codes.ts — same object, not a copy
* that can drift. The second is that every declared code is GROUNDED: the
* evidence that justified declaring it is re-checked here, because a refusal
* code with no path that emits it is a branch the reader waits for and never
* sees, and a table of those passes a lint while teaching a lie.
*
* The code list is spelled out rather than read from the contract: a test that
* iterates the thing it grades passes for an empty table.
*/
import { strict as assert } from "node:assert";
import { test } from "node:test";
import { readFileSync } from "node:fs";
import { join, dirname } from "node:path";
import { fileURLToPath } from "node:url";
import { HAND_CONTRACT } from "./api.ts";
import { REFUSAL_CODES } from "../snappy-settings/refusal-codes.ts";
const SOURCE = readFileSync(join(dirname(fileURLToPath(import.meta.url)), "api.ts"), "utf8");
/** Every refusal code snappy-playbook declares. */
const DECLARED = [
"unknown_verb",
] as const;
test("snappy-playbook declares exactly these refusal codes", () => {
assert.deepEqual(Object.keys(HAND_CONTRACT.refusals).sort(), [...DECLARED].sort());
});
test("every declared code is the SAME row as the one closed table's, never a copy", () => {
const table = HAND_CONTRACT.refusals as Record<string, unknown>;
for (const code of DECLARED) {
assert.equal(table[code], REFUSAL_CODES[code], `${code} is not the shared row`);
}
});
test("unknown_verb is grounded: the contract closes the verb set, so a word outside it is refusable", () => {
assert.ok(Object.keys(HAND_CONTRACT.verbs).length >= 0);
assert.ok(!Object.keys(HAND_CONTRACT.verbs).includes("no-such-verb"));
});
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-offer
| state | description |
|---|---|
| INPUT (week starts with) | An idea, an existing course/coaching business, or a target niche but no clear mastermind model. No defined offer mechanics. No clarity on transition path from current revenue. |
| OUTPUT (week ends with) | A defined Two-Step Mastermind model on a Figjam canvas, model math in a Google sheet, a 1-page Offer Mechanics worksheet (niche, problems, solutions, principles, price, member cap), a personal Mindset Concentric Circle Map, and a clear conversion plan from the current business. |
Deliverables student finishes the week holding:
A quick overview of what WeTube is and how it works.
An overview of the model we'll be building together.
| framework | definition |
|---|---|
| Two-Step Mastermind | Frontend (lower ticket, recurring) feeds Backend (higher ticket, recurring) |
| Traffic Engine | Multiple sources (YouTube organic, YouTube ads, email newsletter) drive to funnels |
| Product Engine | Mastermind delivery model replaces courses/coaching with recurring revenue |
How to define your mastermind offer, price, and member cap.
| framework | definition |
|---|---|
| Offer Fundamentals | Niche -> Goals -> Problems -> Solutions -> Principles |
| Magnetic Offer | Articulate what people already feel but can't express |
| Unique Offer | Differentiate through principles, not features |
| Offer Mechanics | What's included, price point, member cap -- defined on a single page |
How to feel good, be positive, and create things people love.
| framework | definition |
|---|---|
| Concentric Circle Model | Start at inner circle (biological) and work outwards |
| Balance/Harmony | Identify weak areas and fix them 1-by-1 to achieve overall balance |
| Inner -> outer | Biological > Psychological > Relationships > Purpose > Virtues |
How to convert your current business to the new model.
| framework | definition |
|---|---|
| Decision Tree | Existing course -> Convert to Frontend Mastermind OR start fresh |
| Backend Timing | Only start a Backend Mastermind when your Frontend is producing results |
| Conversion Path | Course/coaching -> Frontend Mastermind -> Add Backend Mastermind |
snappy-offer holds the live Snappy offer derived from this week's frameworks. To execute against this week:
snappy-offer/SKILL.md to update or query the live offersnappy-offer/icp.md for niche/ICP definitionsnappy-offer/pricing.md for member cap and price tiers# Week 1 -- Model, Offer, and Mindset Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b Operationalized in: `snappy-offer` ## Module Inputs / Outputs |state|description| |-----|-----------| |**INPUT** (week starts with)|An idea, an existing course/coaching business, or a target niche but no clear mastermind model. No defined offer mechanics. No clarity on transition path from current revenue.| |**OUTPUT** (week ends with)|A defined Two-Step Mastermind model on a Figjam canvas, model math in a Google sheet, a 1-page Offer Mechanics worksheet (niche, problems, solutions, principles, price, member cap), a personal Mindset Concentric Circle Map, and a clear conversion plan from the current business.| **Deliverables student finishes the week holding:** 1. Filled-out Big Picture Figjam (model) 2. Filled-out Model Math sheet (revenue projections) 3. 1-page Offer Mechanics worksheet 4. Personal mindset assessment + fix-it plan 5. Conversion strategy (convert current course OR start fresh frontend) --- ## 1. Vision (27:44) A quick overview of what WeTube is and how it works. ### Key Points - Sam's vision for the info industry and WeTube - The goal, model, and guiding principles - Introducing the team - Content releases and collaboration calls - How to contribute - Introducing yourself to the group (7:14 sub-section) ### Action Items - Introduce yourself to the group using the provided template ### Resources - [Vision summary](https://docs.google.com/document/d/1OiVSIRI5AgO8KgAS_-LyeJ56uUI7dZSrmUTPv2Th12E/edit) --- ## 2. Model (14:49) An overview of the model we'll be building together. ### Key Points - Big picture overview of the model and how it works - The traffic engine and traffic sources - The product engine -- "two-step mastermind" (Frontend + Backend) - The math that makes it work - The team that keeps it running - The website, VSL funnel, and launch funnel ### Frameworks |framework|definition| |---------|----------| |Two-Step Mastermind|Frontend (lower ticket, recurring) feeds Backend (higher ticket, recurring)| |Traffic Engine|Multiple sources (YouTube organic, YouTube ads, email newsletter) drive to funnels| |Product Engine|Mastermind delivery model replaces courses/coaching with recurring revenue| ### Action Items - Complete the Big Picture (Figjam file) for your business - Complete the Model Math (Google sheet) for your business ### Resources - [Big picture (Figjam file)](https://www.figma.com/file/WScnM4fEaZdXqMneGVILTJ/Wetube---model?node-id=0%3A1) - [Model math (Google sheet)](https://docs.google.com/spreadsheets/d/1hSSca1DAmcL4MiGpULs23ATddrbRRBraX-9WdjOzcIo/edit?usp=sharing) --- ## 3. Offer (38:05) How to define your mastermind offer, price, and member cap. ### Key Points - Fundamentals: Niche, goals, problems, solutions, principles - Creative process: ideas to spark creativity - What makes an offer "magnetic" -- articulating what people sense but can't say - What makes an offer unique -- creating your own style through principles - Defining your mastermind offer: what's included, price, member cap ### Frameworks |framework|definition| |---------|----------| |Offer Fundamentals|Niche -> Goals -> Problems -> Solutions -> Principles| |Magnetic Offer|Articulate what people already feel but can't express| |Unique Offer|Differentiate through principles, not features| |Offer Mechanics|What's included, price point, member cap -- defined on a single page| ### Action Items - Define your fundamentals - Brainstorm using the creative process prompts - Define your mastermind offer on 1 page using the Offer Mechanics worksheet ### Resources - [Offer overview](https://docs.google.com/document/d/1byHN99bg5HtpUphUxEqQS2i-IEz9dOhExVy_2jo41j0/edit?usp=sharing) - [Offer mechanics worksheet](https://docs.google.com/document/d/12RFwC5TuN7KVsbeWHSAWitnzycVkm6vjlSvRyM9EXQg/edit?usp=sharing) --- ## 4. Mindset (17:49) How to feel good, be positive, and create things people love. ### Key Points - Wholistic mindset -- finding balance/harmony in all areas of life - **Biological:** sleep, diet, hydration, sunlight, exercise - **Psychological:** work, security, home, love - **Relationships:** family, friends, clients, team - **Purpose:** vision, values, goals, structure - **Virtues:** communication, honesty, trust, commitment ### Frameworks |framework|definition| |---------|----------| |Concentric Circle Model|Start at inner circle (biological) and work outwards| |Balance/Harmony|Identify weak areas and fix them 1-by-1 to achieve overall balance| |Inner -> outer|Biological > Psychological > Relationships > Purpose > Virtues| ### Action Items - Starting at the inner circle and working outwards, identify weak areas of your life and fix them 1-by-1 ### Resources - [Mindset (Figjam file)](https://www.figma.com/file/X1mvY9e1cU6TvJofz1uDPM/Wetube---mindset?node-id=0%3A1) --- ## 5. Converting to the New Model (24:52) How to convert your current business to the new model. ### Key Points - Where do you start? Frontend Mastermind or Backend Mastermind? - How do you know when it's time to start a Backend Mastermind? - How do you convert your current course into a Frontend Mastermind? - When to start a brand new Frontend Mastermind instead of converting a course? - How to solve your own problems, get help, and collaborate with the group ### Frameworks |framework|definition| |---------|----------| |Decision Tree|Existing course -> Convert to Frontend Mastermind OR start fresh| |Backend Timing|Only start a Backend Mastermind when your Frontend is producing results| |Conversion Path|Course/coaching -> Frontend Mastermind -> Add Backend Mastermind| ### Resources - [Converting to the new model](https://docs.google.com/document/d/1CNzfq_ZbYYxjJTVKixTkj62crXzG5_S5apGnkAIXx58/edit?usp=sharing) - [Maria's letter to customers](https://docs.google.com/document/d/12AgqgGNfHEDX_cRAHEbnD_pfNJ72lBk0hXnN8-kARLk/edit) -- example transition communication --- ## Operationalized In `snappy-offer` holds the live Snappy offer derived from this week's frameworks. To execute against this week: - Read this file for the framework - Open `snappy-offer/SKILL.md` to update or query the live offer - Use `snappy-offer/icp.md` for niche/ICP definition - Use `snappy-offer/pricing.md` for member cap and price tiers
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-sales
| state | description |
|---|---|
| INPUT (week starts with) | A defined offer from Week 1 (mechanics worksheet) but no live launch plan, no funnel built, no booked calls, no sales call script, no pipeline tracking, no objection handling framework. |
| OUTPUT (week ends with) | A war-map planner with launch dates, a built launch funnel OR opportunity funnel (depending on audience size), a sales call script following Sam's formula, a daily call tracking sheet, a pre-call prep checklist, and the first booked beta calls. |
Deliverables student finishes the week holding:
How to launch a frontend or backend mastermind.
| framework | definition |
|---|---|
| Pre-Launch Audit | Inventory existing assets (email list, YT subs, students, social) before choosing a launch strategy |
| Private Launch | Talk directly to your best existing students/clients first -- get founding members before going public |
| Backend Launch Path | Existing audience -> Opportunity Funnel |
| Frontend Launch Path | Cold/new audience -> Launch Funnel |
| Ongoing Promotion | After launch, promote continuously through content, email, ads |
How to launch a frontend mastermind with a Launch Funnel.
| framework | definition |
|---|---|
| War Map Planner | Plan the entire launch before executing -- dates, assets, channels, milestones |
| 14-Day Coming Soon Teaser | Build hype and waitlist before the launch opens |
| Launch Funnel Structure | Landing page > Video > Application/Enrollment > Onboarding |
| Enrollment Waves | Don't keep enrollment open forever -- capped waves create urgency |
| Multi-Channel Promotion | Hit every channel simultaneously -- group posts, email blasts, YouTube, social |
Promoting any mastermind with the Opportunity Funnel.
| framework | definition |
|---|---|
| Opportunity Discovery | Run your mastermind, observe what members need, find gaps = new opportunities |
| Opportunity Funnel | System for promoting masterminds to people who already have context (existing students, list, warm audience) |
| Differs from Launch Funnel | This is for ongoing promotion to warm audiences, not cold launch |
How to sell people masterminds using Zoom and a formula.
| framework | definition |
|---|---|
| Daily Prep Routine | Get mentally and physically ready before any sales calls |
| Pre-Call Prep | Research the prospect, review their application, know their situation |
| Sales Call Formula | Rapport > Discovery > Present > Close |
| High-Ticket Close | Selling recurring mastermind memberships, not one-time products |
How to track your sales calls and performance.
| framework | definition |
|---|---|
| Daily Call Tracking | Log every call, its outcome, and key notes |
| Sales Call Tracking Sheet | Standardized spreadsheet for pipeline visibility |
| KPI Monitoring | Calls made, show rate, close rate, revenue per call |
How to prepare for your sales calls. The longest lesson in Week 2.
| framework | definition |
|---|---|
| Buyer Type Identification | Different buyers need different approaches -- identify which type before the call |
| Seller's Mindset | The mental frame to hold during a sales call |
| Indicators / Fundamentals / Outcomes | Three-part framework: where the prospect is, what they need, what you can deliver |
| lesson | duration |
|---|---|
| 1. Launching a mastermind | 22:48 |
| 2. Launch funnel | 40:49 |
| 3. Opportunity funnel | 37:58 |
| 4. Sales call formula | 30:50 |
| 5. Sales call tracking | 7:13 |
| 6. Sales call preparation | 54:35 |
| Total | ~3h 14m |
Note: All lessons are video-based. Text content above is extracted from lesson descriptions and page metadata on Skool. The Google Doc resources contain the detailed written materials.
snappy-sales holds the live sales playbook derived from this week's frameworks. To execute against this week:
snappy-sales/SKILL.md for the live sales processsnappy-sales/call-framework.md for the call scriptsnappy-sales/funnels.md for launch and opportunity funnel structuressnappy-sales/pipeline.md for tracking and KPIssnappy-sales/lead-to-close.md for prep + objection handlingsnappy-sales/gotchas.md for the things AI gets wrong# Week 2 -- Launch, Beta, and Sales Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b Operationalized in: `snappy-sales` ## Module Inputs / Outputs |state|description| |-----|-----------| |**INPUT** (week starts with)|A defined offer from Week 1 (mechanics worksheet) but no live launch plan, no funnel built, no booked calls, no sales call script, no pipeline tracking, no objection handling framework.| |**OUTPUT** (week ends with)|A war-map planner with launch dates, a built launch funnel OR opportunity funnel (depending on audience size), a sales call script following Sam's formula, a daily call tracking sheet, a pre-call prep checklist, and the first booked beta calls.| **Deliverables student finishes the week holding:** 1. War Map planner with launch milestones 2. Built Launch Funnel (cold) or Opportunity Funnel (warm) 3. Sales call script (rapport -> discovery -> present -> close) 4. Daily sales tracking sheet 5. Pre-call prep checklist 6. First few beta members closed --- ## 1. Launching a Mastermind (22:48) How to launch a frontend or backend mastermind. ### Key Points - Pre-launch audit -- find assets you can use to launch - Get first customers privately by talking to your star students - Launch a backend mastermind using the Opportunity Funnel - Launch a frontend mastermind using the Launch Funnel - Promote a backend/frontend mastermind on an ongoing basis ### Frameworks |framework|definition| |---------|----------| |Pre-Launch Audit|Inventory existing assets (email list, YT subs, students, social) before choosing a launch strategy| |Private Launch|Talk directly to your best existing students/clients first -- get founding members before going public| |Backend Launch Path|Existing audience -> Opportunity Funnel| |Frontend Launch Path|Cold/new audience -> Launch Funnel| |Ongoing Promotion|After launch, promote continuously through content, email, ads| ### Resources - [Launching a mastermind](https://docs.google.com/document/d/10tgcy0uTbdPQ_hqwkttcKu0WtJzRl5NAswopL-UnaGg/edit?usp=sharing) --- ## 2. Launch Funnel (40:49) How to launch a frontend mastermind with a Launch Funnel. ### Key Points - Make a plan to launch using the War Map planner - Use a 14-day "Coming Soon teaser" to build a waitlist and hype - Create the Launch Funnel: landing pages, video, sequencing - Launch: promote hard with group posts, emails, YouTube videos - Enrollment: sell people in, hit member cap, use "enrollment waves" ### Frameworks |framework|definition| |---------|----------| |War Map Planner|Plan the entire launch before executing -- dates, assets, channels, milestones| |14-Day Coming Soon Teaser|Build hype and waitlist before the launch opens| |Launch Funnel Structure|Landing page > Video > Application/Enrollment > Onboarding| |Enrollment Waves|Don't keep enrollment open forever -- capped waves create urgency| |Multi-Channel Promotion|Hit every channel simultaneously -- group posts, email blasts, YouTube, social| ### Resources - [Launch funnel summary](https://docs.google.com/document/d/1RYhxxdxoTqiu0gIpunaosUcGqW-EbDy7k5d7ACLTWNw/edit?usp=sharing) --- ## 3. Opportunity Funnel (37:58) Promoting any mastermind with the Opportunity Funnel. ### Key Points - Find an opportunity by running and observing your mastermind - How this process typically works in practice - Identify patterns and gaps in your mastermind that become sellable opportunities - Use the opportunity funnel to promote both frontend and backend masterminds ### Frameworks |framework|definition| |---------|----------| |Opportunity Discovery|Run your mastermind, observe what members need, find gaps = new opportunities| |Opportunity Funnel|System for promoting masterminds to people who already have context (existing students, list, warm audience)| |Differs from Launch Funnel|This is for ongoing promotion to warm audiences, not cold launch| ### Resources - [Opportunity funnel summary](https://docs.google.com/document/d/10OQMHS43AYTZkhxoHxr_78TPc6CjRkLmGQhIc31fa6E/edit?usp=sharing) --- ## 4. Sales Call Formula (30:50) How to sell people masterminds using Zoom and a formula. ### Key Points - Daily prep: get yourself in order to close effectively - Pre-call prep: research and ready your talking points - The sales call structure and formula - Objection handling framework - Closing techniques for high-ticket mastermind offers ### Frameworks |framework|definition| |---------|----------| |Daily Prep Routine|Get mentally and physically ready before any sales calls| |Pre-Call Prep|Research the prospect, review their application, know their situation| |Sales Call Formula|Rapport > Discovery > Present > Close| |High-Ticket Close|Selling recurring mastermind memberships, not one-time products| ### Resources - [Sales call formula](https://docs.google.com/document/d/1Ss50iwj92DtGlilL1yhM8tWRJHzSlEkLkjx2TxNGZhI/edit?usp=sharing) --- ## 5. Sales Call Tracking (7:13) How to track your sales calls and performance. ### Key Points - Track your sales calls and their outcome on a daily basis - Use the sales call tracking sheet to monitor pipeline metrics - Understand conversion rates and identify bottlenecks ### Frameworks |framework|definition| |---------|----------| |Daily Call Tracking|Log every call, its outcome, and key notes| |Sales Call Tracking Sheet|Standardized spreadsheet for pipeline visibility| |KPI Monitoring|Calls made, show rate, close rate, revenue per call| ### Resources - [Sales call tracking sheet](https://docs.google.com/spreadsheets/d/1M_jLbW7mC6axLQl59oTUwen1kgN2aioEBOJ4z3U7Gnw/edit?usp=sharing) --- ## 6. Sales Call Preparation (54:35) How to prepare for your sales calls. The longest lesson in Week 2. ### Key Points - Identify the buyer type - The correct seller's mindset - Indicators, fundamentals, and outcomes for effective selling - Deep preparation framework for high-ticket calls ### Frameworks |framework|definition| |---------|----------| |Buyer Type Identification|Different buyers need different approaches -- identify which type before the call| |Seller's Mindset|The mental frame to hold during a sales call| |Indicators / Fundamentals / Outcomes|Three-part framework: where the prospect is, what they need, what you can deliver| ### Resources - [Sales call preparation](https://docs.google.com/document/d/14MCpbl3N6weH0QnGJF2Ig1S751lwg1V0FGdvfxlsbhs/edit?usp=sharing) --- ## Video Durations Summary |lesson|duration| |------|--------| |1. Launching a mastermind|22:48| |2. Launch funnel|40:49| |3. Opportunity funnel|37:58| |4. Sales call formula|30:50| |5. Sales call tracking|7:13| |6. Sales call preparation|54:35| |**Total**|**~3h 14m**| Note: All lessons are video-based. Text content above is extracted from lesson descriptions and page metadata on Skool. The Google Doc resources contain the detailed written materials. --- ## Operationalized In `snappy-sales` holds the live sales playbook derived from this week's frameworks. To execute against this week: - Read this file for the framework - Open `snappy-sales/SKILL.md` for the live sales process - Use `snappy-sales/call-framework.md` for the call script - Use `snappy-sales/funnels.md` for launch and opportunity funnel structures - Use `snappy-sales/pipeline.md` for tracking and KPIs - Use `snappy-sales/lead-to-close.md` for prep + objection handling - Use `snappy-sales/gotchas.md` for the things AI gets wrong
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-skool
| state | description |
|---|---|
| INPUT (week starts with) | First members closed (from Week 2). No live community space. No classroom structure. No collab call cadence. No event plan. No backend/frontend separation defined operationally. |
| OUTPUT (week ends with) | A live Skool group with classroom, calendar, and community feed configured. A frontend mastermind running with content delivery rhythm. A backend mastermind defined with the 5 elements (instructions, community, collab calls, coaching, events). A first scheduled live event (virtual or in-person). |
Deliverables student finishes the week holding:
The philosophy and principles of making great masterminds.
| framework | definition |
|---|---|
| Masterminds vs Courses | Masterminds focus on implementation and collaboration, not passive content consumption |
| Core Mastermind Values | Action-oriented, peer-driven, results-focused. Group improves together by sharing real operational knowledge. |
| What Makes Masterminds Great | High-quality aligned members, active participation, real business results, feels like friends |
| What to Avoid | Long boring content, passive consumption, low engagement, misaligned members |
| Key Principle | Best masterminds feel like friends helping each other win -- not a classroom |
How to create a "home" for your mastermind using a Skool group.
| framework | definition |
|---|---|
| Why Skool | All-in-one platform for community, classroom, calendar -- replaces multiple tools. Simple, clean UX members actually use. |
| Skool as Revenue | Earn 40% MRR commissions by referring other group owners -- can offset or exceed Skool costs |
| Group Setup Essentials | Video hosting in classroom, Zoom integration for calls, community feed for daily engagement, calendar for events |
| Best Practices | Keep it simple, post daily, engage with members, use community feed actively |
| Daily Workflow | Check community, respond to posts, engage members, post content/updates |
How to create and run a frontend mastermind (entry-level offering).
| framework | definition |
|---|---|
| Frontend Role | Entry point for new customers. Lower price, larger group, pipeline to higher-ticket backend mastermind. |
| Frontend vs Backend | Frontend is more content/community focused; backend is more intimate, implementation-focused, with live events |
| Conversion Path | Frontend members who get results and want more -> backend mastermind upgrade |
How to start, grow, and sustain a great backend mastermind.
| element | description |
|---|---|
| 1. Instructions | Structured content and frameworks |
| 2. Community | Active Skool group for daily interaction |
| 3. Collab Calls | Regular group calls for collaboration |
| 4. Coaching | Direct access to the leader/coach |
| 5. Events | In-person and virtual gatherings |
| framework | definition |
|---|---|
| Live Event Logistics | Venue, catering, recording setup, editing workflow, publishing recordings to group |
| Live Event Preparation | Right mindset, plan agenda, identify key members, prepare handouts/whiteboard |
| Live Event Flow | Structured agenda balancing teaching, collaboration, socializing -- interactive not lecture |
| Virtual Events | Zoom optimization, prep checklist, flow/structure for remote engagement, interaction tools |
snappy-skool holds the live mastermind delivery system derived from this week's frameworks. To execute against this week:
snappy-skool/SKILL.md for live community opssnappy-skool/SKILL.md for content deliverysnappy-skool/SKILL.md for frontend mastermind opssnappy-skool/SKILL.md for new member experiencesnappy-skool/SKILL.md for community feed activitysnappy-skool/SKILL.md for tracking + retentionsnappy-skool/SKILL.md for Skool 40% MRR affiliate setupsnappy-skool/SKILL.md for direct member communication# Week 3 -- Making a Mastermind Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b Operationalized in: `snappy-skool` ## Module Inputs / Outputs |state|description| |-----|-----------| |**INPUT** (week starts with)|First members closed (from Week 2). No live community space. No classroom structure. No collab call cadence. No event plan. No backend/frontend separation defined operationally.| |**OUTPUT** (week ends with)|A live Skool group with classroom, calendar, and community feed configured. A frontend mastermind running with content delivery rhythm. A backend mastermind defined with the 5 elements (instructions, community, collab calls, coaching, events). A first scheduled live event (virtual or in-person).| **Deliverables student finishes the week holding:** 1. Live Skool group with branding, classroom, calendar 2. Daily community workflow defined 3. Frontend mastermind running (price, content cadence, member experience) 4. Backend mastermind structured around 5 elements 5. First event scheduled (virtual or in-person) 6. 40% MRR Skool affiliate referral channel set up --- ## 1. Mastermind Philosophy (23:49) The philosophy and principles of making great masterminds. ### Key Points - Masterminds are about doing things and finding better ways to do things - The principles masterminds value and how they're different from courses - Things that make masterminds great - Things to avoid ### Frameworks |framework|definition| |---------|----------| |Masterminds vs Courses|Masterminds focus on implementation and collaboration, not passive content consumption| |Core Mastermind Values|Action-oriented, peer-driven, results-focused. Group improves together by sharing real operational knowledge.| |What Makes Masterminds Great|High-quality aligned members, active participation, real business results, feels like friends| |What to Avoid|Long boring content, passive consumption, low engagement, misaligned members| |Key Principle|Best masterminds feel like friends helping each other win -- not a classroom| ### Resources - [Mastermind philosophy](https://docs.google.com/document/d/1xr2SrpIh0QBIkuuWBbCgHLX7BZ4hbQz2Iry1CMsHJfk/edit?usp=sharing) --- ## 2. Skool Group and Tools (44:16) How to create a "home" for your mastermind using a Skool group. ### Key Points - Why Skool? The benefits - Creating your Skool group - How to make Skool an income stream, not a cost (40% MRR commissions) - Setting up your group (video hosting, Zoom integration) - Best practices - Daily workflow ### Frameworks |framework|definition| |---------|----------| |Why Skool|All-in-one platform for community, classroom, calendar -- replaces multiple tools. Simple, clean UX members actually use.| |Skool as Revenue|Earn 40% MRR commissions by referring other group owners -- can offset or exceed Skool costs| |Group Setup Essentials|Video hosting in classroom, Zoom integration for calls, community feed for daily engagement, calendar for events| |Best Practices|Keep it simple, post daily, engage with members, use community feed actively| |Daily Workflow|Check community, respond to posts, engage members, post content/updates| ### Resources - [Skool group and tools](https://docs.google.com/document/d/1U4vUTSkGpLevBeGqFhDcTSI424R1PG-AzZHDHfN727c/edit?usp=sharing) --- ## 3. Frontend Mastermind (26:19) How to create and run a frontend mastermind (entry-level offering). ### Key Points - Frontend = lower-ticket, higher-volume mastermind that feeds backend - Structure, pricing, content delivery, member experience - How to create a compelling frontend that converts to backend ### Frameworks |framework|definition| |---------|----------| |Frontend Role|Entry point for new customers. Lower price, larger group, pipeline to higher-ticket backend mastermind.| |Frontend vs Backend|Frontend is more content/community focused; backend is more intimate, implementation-focused, with live events| |Conversion Path|Frontend members who get results and want more -> backend mastermind upgrade| ### Resources - [Frontend mastermind](https://docs.google.com/document/d/1fX2yri7dhXOE5QfwUfRSdTOMBX7a0oVi6aoKhIaauSA/edit?usp=sharing) --- ## 4. Backend Mastermind (36:48) How to start, grow, and sustain a great backend mastermind. ### Key Points - Elements: Instructions, community, collab calls, coaching, events - Live events: Logistics -- venue, catering, recording, editing, publishing - Live events: Preparation -- mindset, planning, key members, handouts, whiteboard - Live events: Flow/Structure -- agenda for in-person events - Virtual events -- venue, Zoom settings, prep, flow/structure, tools ### Frameworks |element|description| |-------|-----------| |1. Instructions|Structured content and frameworks| |2. Community|Active Skool group for daily interaction| |3. Collab Calls|Regular group calls for collaboration| |4. Coaching|Direct access to the leader/coach| |5. Events|In-person and virtual gatherings| |framework|definition| |---------|----------| |Live Event Logistics|Venue, catering, recording setup, editing workflow, publishing recordings to group| |Live Event Preparation|Right mindset, plan agenda, identify key members, prepare handouts/whiteboard| |Live Event Flow|Structured agenda balancing teaching, collaboration, socializing -- interactive not lecture| |Virtual Events|Zoom optimization, prep checklist, flow/structure for remote engagement, interaction tools| ### Resources - [Backend mastermind](https://docs.google.com/document/d/1_bhqP-yKTHP-rFNS3-iBeS_EvVhyQS2JTSU5rXuhhqs/edit?usp=sharing) --- ## Operationalized In `snappy-skool` holds the live mastermind delivery system derived from this week's frameworks. To execute against this week: - Read this file for the framework - Open `snappy-skool/SKILL.md` for live community ops - Use `snappy-skool/SKILL.md` for content delivery - Use `snappy-skool/SKILL.md` for frontend mastermind ops - Use `snappy-skool/SKILL.md` for new member experience - Use `snappy-skool/SKILL.md` for community feed activity - Use `snappy-skool/SKILL.md` for tracking + retention - Use `snappy-skool/SKILL.md` for Skool 40% MRR affiliate setup - Use `snappy-skool/SKILL.md` for direct member communication
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-website, snappy-email, snappy-youtube
| state | description |
|---|---|
| INPUT (week starts with) | A live mastermind (Week 3) but no traffic engine. No website. No email list or newsletter. No YouTube channel. No VSL funnel for paid traffic. Bookings happen through warm/manual outreach only. |
| OUTPUT (week ends with) | A live website (6 pages, designed in Figma, 4 goals oriented). A 3+/wk email newsletter cadence with templates. A YouTube channel publishing 1+/wk. A 4-page VSL funnel built in ClickFunnels with Calendly + ActiveCampaign + Zapier integration. The 4 traffic engine components working in concert. |
Deliverables student finishes the week holding:
Overview of the traffic engine used to generate customers.
| component | role |
|---|---|
| Website | Hub that collects subs, emails, books calls |
| Email Newsletter | Nurtures leads, drives calls and sales |
| YouTube Channel | Organic content, builds authority, drives traffic |
| VSL Funnel | Paid traffic destination, converts cold leads via video |
| principle | description |
|---|---|
| Concert model | YouTube drives traffic to website, website captures emails, emails nurture and sell, VSL funnel handles paid traffic conversion. All roads lead to booked calls. |
| Key insight | No single channel works alone -- power is in the system where each component feeds the others |
How to create a website that gets subs, emails, and clients.
| website goal | metric |
|---|---|
| 1. Get YouTube subscribers | Channel sub growth |
| 2. Get email subscribers | Newsletter list growth |
| 3. Get booked calls | Calendly bookings |
| 4. Get clients | Conversion from booked call |
| page | purpose |
|---|---|
| Home | Main landing with clear CTAs |
| Product Pages | Mastermind/offer detail pages |
| Newsletter | Email signup landing |
| YouTube | Embed or link to channel |
| About | Personal brand story |
| Legal | Privacy + terms |
| principle | description |
|---|---|
| Consistency is king | Same fonts, colors, spacing, tone throughout. Design in Figma first, then build. |
| Publishing options | Webflow (best design control), ClickFunnels (best for funnels), Wordpress (most flexible) |
How to build a successful email newsletter.
| goal | target |
|---|---|
| Build email list | Capture from website, YouTube, ads |
| Send emails | 3+ per week minimum |
| Generate calls | Primary success metric |
| Drive YT subs | Secondary success metric |
| step | workflow (30 min target) |
|---|---|
| 1 | Pick an idea from your ideas list |
| 2 | Write the email using a template |
| 3 | Send it |
| 4 | Total time: <=30 minutes |
| kpi | target |
|---|---|
| Open rate | 10-20% |
| Primary metric | Calls generated from emails |
| Secondary | Clicks, replies, unsubscribes |
| principle | description |
|---|---|
| Volume > perfection | Send more, not better. Consistency beats polish. |
| Email frequency | 3+ per week, plotted on War Map planner |
How to create a successful YouTube channel.
| expectation | reality |
|---|---|
| Passion | Have fun. If you don't enjoy it, you won't stick with it. |
| Consistency | Minimum 1 video per week |
| Time | Commit to 2+ years before significant results |
| video formula step | purpose |
|---|---|
| 1. Intro | Hook the viewer |
| 2. Bullet Points | Deliver the content |
| 3. Prompts | Engage the viewer |
| 4. Ending/CTA | Subscribe, newsletter, book call |
| principle | description |
|---|---|
| Differentiation | Don't copy other creators. Mix personal interests with niche topics -- nobody can replicate your unique combination. |
| Different > Better | Your unique perspective is your competitive advantage. |
How to create a VSL funnel for paid ads.
| page | step in flow |
|---|---|
| 1. Optin Page | Capture email |
| 2. Video Page | Play the VSL |
| 3. Schedule Page | Calendly booking |
| 4. Success Page | Confirmation |
| tool | role |
|---|---|
| ClickFunnels | Build funnel pages |
| Calendly | Calendar booking + pre-call survey |
| ActiveCampaign | Email automation, lists, tags |
| Zapier | Connect Calendly to ActiveCampaign (triggers "booked call" tag) |
| step | activecampaign setup |
|---|---|
| 1 | Create dedicated list for VSL leads |
| 2 | Set up forms for optin capture |
| 3 | Create tags: optin, watched VSL, booked call, etc. |
| 4 | Build tag-based email automation |
| 5 | Write follow-up sequences for each stage |
| flow | sequence |
|---|---|
| Full VSL funnel | Ad -> Optin -> Watch VSL -> Book Call -> Sales Call -> Client |
This week splits across multiple skills:
| deliverable | skill | key files |
|---|---|---|
| Website | snappy-website |
SKILL.md (snappy.ai pages, copy, design) |
| Email newsletter | snappy-email |
SKILL.md, automation.md, templates.md, workflow.md, list-management.md |
| YouTube organic | snappy-youtube |
SKILL.md (channel ops, scripts, publishing) |
| VSL funnel | snappy-website + snappy-ads |
funnel pages live in website skill, ad-side in ads skill |
| Content for emails+YT | snappy-content |
interview-driven methodology |
| Long-form blog seeds | snappy-blog |
article generation from playbook frameworks |
# Week 4 -- Funnel, Email, and Organic
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: `snappy-website`, `snappy-email`, `snappy-youtube`
## Module Inputs / Outputs
|state|description|
|-----|-----------|
|**INPUT** (week starts with)|A live mastermind (Week 3) but no traffic engine. No website. No email list or newsletter. No YouTube channel. No VSL funnel for paid traffic. Bookings happen through warm/manual outreach only.|
|**OUTPUT** (week ends with)|A live website (6 pages, designed in Figma, 4 goals oriented). A 3+/wk email newsletter cadence with templates. A YouTube channel publishing 1+/wk. A 4-page VSL funnel built in ClickFunnels with Calendly + ActiveCampaign + Zapier integration. The 4 traffic engine components working in concert.|
**Deliverables student finishes the week holding:**
1. Live website with 6 page types (Home, Product, Newsletter, YouTube, About, Legal)
2. Email platform set up (ActiveCampaign) with 3+/wk send schedule plotted on War Map
3. YouTube channel branded, with first videos using the Hook/Bullets/Prompts/CTA formula
4. 4-page VSL funnel: Optin -> Video -> Schedule -> Success
5. Calendly + ActiveCampaign + Zapier integration with "booked call" tag
6. ActiveCampaign nurture automation tied to lead tags
---
## 1. Traffic Engine (4:48)
Overview of the traffic engine used to generate customers.
### Key Points
- How everything works together in concert
- Website
- Email newsletter
- YouTube channel
- VSL funnel
### Frameworks
|component|role|
|---------|----|
|Website|Hub that collects subs, emails, books calls|
|Email Newsletter|Nurtures leads, drives calls and sales|
|YouTube Channel|Organic content, builds authority, drives traffic|
|VSL Funnel|Paid traffic destination, converts cold leads via video|
|principle|description|
|---------|-----------|
|Concert model|YouTube drives traffic to website, website captures emails, emails nurture and sell, VSL funnel handles paid traffic conversion. All roads lead to booked calls.|
|Key insight|No single channel works alone -- power is in the system where each component feeds the others|
### Action Items
- Understand the full traffic system before building any single piece
- Map how website, email, YouTube, and VSL funnel will connect
---
## 2. Website (11:38)
How to create a website that gets subs, emails, and clients.
### Key Points
- Website purpose: subs, emails, calls, clients
- Pages: Home, product pages, newsletter, YouTube, about, legal
- Create the website using Figma
- Publishing options: Webflow, ClickFunnels, Wordpress
- Tips for making it look nice: consistency!
### Frameworks
|website goal|metric|
|------------|------|
|1. Get YouTube subscribers|Channel sub growth|
|2. Get email subscribers|Newsletter list growth|
|3. Get booked calls|Calendly bookings|
|4. Get clients|Conversion from booked call|
|page|purpose|
|----|-------|
|Home|Main landing with clear CTAs|
|Product Pages|Mastermind/offer detail pages|
|Newsletter|Email signup landing|
|YouTube|Embed or link to channel|
|About|Personal brand story|
|Legal|Privacy + terms|
|principle|description|
|---------|-----------|
|Consistency is king|Same fonts, colors, spacing, tone throughout. Design in Figma first, then build.|
|Publishing options|Webflow (best design control), ClickFunnels (best for funnels), Wordpress (most flexible)|
### Action Items
- Design website in Figma before building
- Include all 6 page types
- Make every page drive toward one of the 4 goals
---
## 3. Email Newsletter (28:31)
How to build a successful email newsletter.
### Key Points
- Goals: build an email list, send 3+ emails/week, get calls, clients, subs
- Schedule: pick frequency, plot days on War Map planner
- Workflow: idea to sent email in 30 min or less
- Examples: templates from Sam's newsletter
- Measure: open rates 10-20%, primary metric = calls generated
### Frameworks
|goal|target|
|----|------|
|Build email list|Capture from website, YouTube, ads|
|Send emails|3+ per week minimum|
|Generate calls|Primary success metric|
|Drive YT subs|Secondary success metric|
|step|workflow (30 min target)|
|----|------------------------|
|1|Pick an idea from your ideas list|
|2|Write the email using a template|
|3|Send it|
|4|Total time: <=30 minutes|
|kpi|target|
|---|------|
|Open rate|10-20%|
|Primary metric|Calls generated from emails|
|Secondary|Clicks, replies, unsubscribes|
|principle|description|
|---------|-----------|
|Volume > perfection|Send more, not better. Consistency beats polish.|
|Email frequency|3+ per week, plotted on War Map planner|
### Action Items
- Set up email platform (ActiveCampaign)
- Pick 3+ days per week to send
- Plot email days on War Map planner
- Build an ideas list to pull from
- Aim for 30-min workflow per email
### Resources
- [Email newsletter](https://docs.google.com/document/d/16n86IgEfMQsAunUVmYymHTqwaymySUal38_UICgsqZs/edit?usp=sharing)
---
## 4. YouTube Channel (30:27)
How to create a successful YouTube channel.
### Key Points
- Expectations: passion, consistency (1 video/wk), time (2+ years)
- Strategy: be different from everybody else
- Differentiation: mix personal interests with niche interests
- Preparation: camera, location, schedule, ideas list, channel setup
- Workflow: idea to published video
- Formula: Intro, bullet points, prompts, ending/CTA
### Frameworks
|expectation|reality|
|-----------|-------|
|Passion|Have fun. If you don't enjoy it, you won't stick with it.|
|Consistency|Minimum 1 video per week|
|Time|Commit to 2+ years before significant results|
|video formula step|purpose|
|------------------|-------|
|1. Intro|Hook the viewer|
|2. Bullet Points|Deliver the content|
|3. Prompts|Engage the viewer|
|4. Ending/CTA|Subscribe, newsletter, book call|
|principle|description|
|---------|-----------|
|Differentiation|Don't copy other creators. Mix personal interests with niche topics -- nobody can replicate your unique combination.|
|Different > Better|Your unique perspective is your competitive advantage.|
### Action Items
- Set up camera and filming location
- Create YouTube channel with branding
- Build a running ideas list
- Commit to 1 video per week for 2+ years
- Use the video formula
### Resources
- [YouTube channel](https://docs.google.com/document/d/1Hq1jKMObjRJKunRiIyHFbmQJxA03IAMELP5GL86YhrU/edit?usp=sharing)
---
## 5. VSL Funnel (39:29)
How to create a VSL funnel for paid ads.
### Key Points
- Make pages using ClickFunnels: Optin, video, schedule, success
- Integrate Calendly for calendar and survey
- Create the VSL video: structure, creative process
- Automate with ActiveCampaign: list, form, tags, automation, emails
- Connect Calendly to ActiveCampaign with Zapier ("booked call" tag)
- Examples of successful VSL funnels
### Frameworks
|page|step in flow|
|----|-----------|
|1. Optin Page|Capture email|
|2. Video Page|Play the VSL|
|3. Schedule Page|Calendly booking|
|4. Success Page|Confirmation|
|tool|role|
|----|----|
|ClickFunnels|Build funnel pages|
|Calendly|Calendar booking + pre-call survey|
|ActiveCampaign|Email automation, lists, tags|
|Zapier|Connect Calendly to ActiveCampaign (triggers "booked call" tag)|
|step|activecampaign setup|
|----|---------------------|
|1|Create dedicated list for VSL leads|
|2|Set up forms for optin capture|
|3|Create tags: optin, watched VSL, booked call, etc.|
|4|Build tag-based email automation|
|5|Write follow-up sequences for each stage|
|flow|sequence|
|----|--------|
|Full VSL funnel|Ad -> Optin -> Watch VSL -> Book Call -> Sales Call -> Client|
### Action Items
- Build 4-page funnel in ClickFunnels (optin, video, schedule, success)
- Set up Calendly with pre-call survey
- Create ActiveCampaign list, forms, tags, automation sequences
- Connect Calendly to ActiveCampaign via Zapier
- Script and record the VSL video
- Study successful VSL examples
### Resources
- [VSL Funnel Template](https://docs.google.com/document/d/1Y56HUl13MnevdBE5MLzvjTsGbWXMNRfa6BFyRvie--8/edit?usp=sharing)
- [VSL Email Templates](https://docs.google.com/document/d/1BlNaRuGtx6nM7pos9ET0G8qjdKSsXC3dMOfOyKZjWuY/edit?usp=sharing)
---
## Operationalized In
This week splits across multiple skills:
|deliverable|skill|key files|
|-----------|-----|---------|
|Website|`snappy-website`|SKILL.md (snappy.ai pages, copy, design)|
|Email newsletter|`snappy-email`|SKILL.md, automation.md, templates.md, workflow.md, list-management.md|
|YouTube organic|`snappy-youtube`|SKILL.md (channel ops, scripts, publishing)|
|VSL funnel|`snappy-website` + `snappy-ads`|funnel pages live in website skill, ad-side in ads skill|
|Content for emails+YT|`snappy-content`|interview-driven methodology|
|Long-form blog seeds|`snappy-blog`|article generation from playbook frameworks|
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-ads
| state | description |
|---|---|
| INPUT (week starts with) | A proven offer (Week 1), live sales process (Week 2), running mastermind (Week 3), and full traffic engine including VSL funnel (Week 4). No paid traffic running. Adspend budget reserved (3+ months at >= product price). |
| OUTPUT (week ends with) | Google Ads Manager + Account + Analytics + Tag Manager + Hyros all configured. Ad creatives filmed and uploaded to a separate YouTube account. Targeting strategy mapped (remarketing -> audiences -> keywords -> custom segments). First campaigns launched with proper Campaign/Ad Group/Ad structure. 14-day test cycles running. CPL <$25 / CP-Call <$250 targets monitored. |
Deliverables student finishes the week holding:
Overview of how we use YouTube Ads to get clients.
| framework | definition |
|---|---|
| YouTube Ads Funnel | Ad -> Optin -> VSL -> Calendly -> Sales Call -> Client |
| Budget Rule | Monthly adspend >= product price (e.g., $3k/mo product = $3k/mo minimum adspend) |
| Tracking Stack | PPC tracking sheet + Hyros + industry benchmarks |
How to set up your Google Ads account.
| tool | role |
|---|---|
| Google Ads Manager | Business manager / parent account |
| Google Ads Account | Where ads actually run |
| Google Analytics | Site behavior tracking |
| Google Tag Manager | Script management for tags |
| Hyros | True attribution + profit tracking |
How to make YouTube Ads that convert.
| framework | definition |
|---|---|
| Ad Script Structure | Hook -> Story -> Close |
| 80/20 Rule | Ad creative is 80% of success; targeting/bidding is 20% |
| Separate Upload Channel | Use a 2nd YouTube account for ad uploads to keep organic channel data clean |
How to target the right audiences with YouTube Ads.
| framework | definition |
|---|---|
| Targeting Timeline | Start with warmest audiences first, expand outward over time |
| Interest vs Intent | Interest = broader reach; Intent = higher quality |
| Targeting Progression | Remarketing -> YouTube audiences -> Keywords -> Custom segments |
How to launch your YouTube Ads.
| framework | definition |
|---|---|
| Campaign Structure | Campaign (budget level) -> Ad Group (targeting level) -> Ad (creative level) |
| Launch Checklist | Create campaign -> Set budget -> Add Hyros templates -> Verify conversion tags |
How to test, optimize, and scale your YouTube Ads.
| framework | definition |
|---|---|
| 14-Day Testing Window | Run each test for a full 14 days before deciding |
| CPL Target | Cost Per Lead < $25 |
| CP-Call Target | Cost Per Call < $250 |
| Vertical Scaling | Increase budget on winning campaigns |
| Horizontal Scaling | Add new targeting/audiences |
| Creative Scaling | Create new ad variations |
Additional ways to use YouTube ads.
Updated targeting deep dive for current Google Ads platform.
How to handle Google Ads disapprovals.
snappy-ads holds the live ad ops derived from this week. To execute against this week:
snappy-ads/SKILL.md for live campaign managementsnappy-video + snappy-imagesnappy-knowledge for analytics retrieval# Week 5 -- YouTube Ads Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b Operationalized in: `snappy-ads` ## Module Inputs / Outputs |state|description| |-----|-----------| |**INPUT** (week starts with)|A proven offer (Week 1), live sales process (Week 2), running mastermind (Week 3), and full traffic engine including VSL funnel (Week 4). No paid traffic running. Adspend budget reserved (3+ months at >= product price).| |**OUTPUT** (week ends with)|Google Ads Manager + Account + Analytics + Tag Manager + Hyros all configured. Ad creatives filmed and uploaded to a separate YouTube account. Targeting strategy mapped (remarketing -> audiences -> keywords -> custom segments). First campaigns launched with proper Campaign/Ad Group/Ad structure. 14-day test cycles running. CPL <$25 / CP-Call <$250 targets monitored.| **Deliverables student finishes the week holding:** 1. Google Ads Manager + Account fully set up 2. Google Analytics + Tag Manager + Hyros tracking live 3. Ad creative scripts (Hook/Story/Close) + filmed videos 4. Separate YouTube account for ad uploads (clean data) 5. Targeting strategy: remarketing lists + YouTube audiences + keyword segments 6. Live campaigns with conversion tags firing 7. 14-day testing cycle running with CPL/CP-Call dashboards 8. Scaling plan ready (vertical, horizontal, creative) --- ## 1. YouTube Ads Overview (30:06) Overview of how we use YouTube Ads to get clients. ### Key Points - Pre-requisites: proven offer, VSL funnel, 3+ months adspend budget - Adspend budget: at least the price of your product - Process: YouTube Ads -> Optin -> VSL -> Calendly -> Call -> Client - Use YouTube ads to sell your VSL, not your offer - Tracking: PPC tracking sheet, Hyros, industry benchmarks ### Frameworks |framework|definition| |---------|----------| |YouTube Ads Funnel|Ad -> Optin -> VSL -> Calendly -> Sales Call -> Client| |Budget Rule|Monthly adspend >= product price (e.g., $3k/mo product = $3k/mo minimum adspend)| |Tracking Stack|PPC tracking sheet + Hyros + industry benchmarks| ### Pre-requisites Checklist - [ ] Proven offer (people are already buying) - [ ] VSL funnel built (Week 4) - [ ] 3+ months of adspend reserved - [ ] Hyros + Google Analytics + Tag Manager set up ### Resources - [YouTube ads overview](https://docs.google.com/document/d/1KaUk1ikPu4RA13PRvTNriqQEb4uWlH18yHN9kfSavJM/edit?usp=sharing) - [YouTube Ads Overview Figma File](https://www.figma.com/file/nFYfbjSH1BW7F0wAe7RqX0/5.1---YouTube-Ads-Overview?node-id=0%3A1) --- ## 2. Account Setup (30:23) How to set up your Google Ads account. ### Key Points - Google Ads Manager -- your business manager - Google Ads account -- where you run ads - Google Analytics -- where you track data - Google Tag Manager -- where you place scripts - Hyros -- see what campaigns produce profit ### Stack |tool|role| |----|----| |Google Ads Manager|Business manager / parent account| |Google Ads Account|Where ads actually run| |Google Analytics|Site behavior tracking| |Google Tag Manager|Script management for tags| |Hyros|True attribution + profit tracking| ### Action Items - Set up Google Ads Manager - Create Google Ads account inside the manager - Set up Google Analytics - Set up Google Tag Manager - Set up Hyros for profit tracking ### Resources - [Account setup](https://docs.google.com/document/d/1uGZpfAvLr6p7MtOLvlweEkIxjWvfjp8g0TNcdeDTFac/edit?usp=sharing) --- ## 3. Creative (30:00) How to make YouTube Ads that convert. ### Key Points - 80% of success with YouTube Ads is the ad itself - Script structure: Hook, story, close - YouTube Ad swipe file + vidtao.com tool - Filming: equipment, location, setup, practice - Editing: captions, subtitles, b-roll, music, thumbnails - Upload using a 2nd YouTube account to keep data clean ### Frameworks |framework|definition| |---------|----------| |Ad Script Structure|Hook -> Story -> Close| |80/20 Rule|Ad creative is 80% of success; targeting/bidding is 20%| |Separate Upload Channel|Use a 2nd YouTube account for ad uploads to keep organic channel data clean| ### Action Items - Study swipe file and vidtao.com for examples - Write ad script using Hook/Story/Close - Film with proper equipment and setup - Edit with captions, subtitles, b-roll, music, thumbnails - Upload to separate YouTube account ### Resources - [Creative](https://docs.google.com/document/d/1jo0vAd3QA_6O0xK2NDwoFbVB-pb-EtuarYZsSpasOY0/edit?usp=sharing) --- ## 4. Targeting (43:04) How to target the right audiences with YouTube Ads. ### Key Points - Interest-based vs intent-based targeting - Targeting Timeline -- what to start with - Remarketing lists -- all website visitors - YouTube audiences -- subscribers and viewers - Keywords -- Targeting Template + Keyword Planner - Custom segments -- keywords, interests, lookalikes ### Frameworks |framework|definition| |---------|----------| |Targeting Timeline|Start with warmest audiences first, expand outward over time| |Interest vs Intent|Interest = broader reach; Intent = higher quality| |Targeting Progression|Remarketing -> YouTube audiences -> Keywords -> Custom segments| ### Action Items - Set up remarketing lists for website visitors - Create YouTube audience segments (subscribers, viewers) - Research keywords (Keyword Planner + Targeting Template) - Build custom segments from keywords, interests, lookalikes ### Resources - [Targeting](https://docs.google.com/document/d/1mV-7tYtIfuVUtZ1LmhKPqubQhM-au_EbVtkUNyiihCs/edit?usp=sharing) --- ## 5. Launching (45:34) How to launch your YouTube Ads. ### Key Points - Structure: Campaigns -> Ad Groups -> Ads - Creating campaigns - Setting budgets - Adding Hyros targeting templates - Checking conversion tags fire ### Frameworks |framework|definition| |---------|----------| |Campaign Structure|Campaign (budget level) -> Ad Group (targeting level) -> Ad (creative level)| |Launch Checklist|Create campaign -> Set budget -> Add Hyros templates -> Verify conversion tags| ### Action Items - Create campaign structure in Google Ads - Set budgets per campaign - Apply Hyros targeting templates - Verify conversion tags before going live ### Resources - [Launching](https://docs.google.com/document/d/18GQgkQMe5Y5YKZfeEfMN-uEp8l8g6UTcKxzG1vX1Bbo/edit?usp=sharing) --- ## 6. Testing, Optimizing, and Scaling (44:33) How to test, optimize, and scale your YouTube Ads. ### Key Points - Testing: 14-day windows, target CPL <$25, target CP-Call <$250 - Optimizing: daily workflow - Scaling: vertical, horizontal, creative ### Frameworks |framework|definition| |---------|----------| |14-Day Testing Window|Run each test for a full 14 days before deciding| |CPL Target|Cost Per Lead < $25| |CP-Call Target|Cost Per Call < $250| |Vertical Scaling|Increase budget on winning campaigns| |Horizontal Scaling|Add new targeting/audiences| |Creative Scaling|Create new ad variations| ### Action Items - Set up 14-day testing windows - Monitor CPL and CP-Call vs targets - Establish daily optimization workflow - Scale winners using vertical/horizontal/creative ### Resources - [Testing, optimizing, and scaling](https://docs.google.com/document/d/1fsLm-ynBJtgdEFokowOQTccF-NaSTeUILp8UUkK1GlY/edit?usp=sharing) --- ## 7. Bonus (6:17) Additional ways to use YouTube ads. ### Key Points - Google Search Ads (branding) - Google Discovery Ads (retargeting) - Performance Max campaigns - Using YouTube ads to grow organic YouTube channel ### Resources - [Bonus](https://docs.google.com/document/d/1w27XpPJLsL5Oo3VI33uvanKEQg1FUZOEoQndAHLGpGw/edit#) --- ## 8. YouTube Ads Targeting Guide for 2023 (47:05) Updated targeting deep dive for current Google Ads platform. ### Key Points - Updated targeting strategies and best practices - Comprehensive walkthrough of all targeting options ### Resources - [YouTube Ads Targeting Doc for 2023](https://docs.google.com/document/d/1mV-7tYtIfuVUtZ1LmhKPqubQhM-au_EbVtkUNyiihCs/edit?usp=sharing) --- ## 9. How To Deal With Ad Disapprovals (15:32) How to handle Google Ads disapprovals. ### Key Points - Common reasons ads get disapproved - Appeal process - Prevention strategies - Policy compliance for info/education businesses ### Action Items - Review Google Ads policies before creating ads - Know the appeal process before you need it - Keep ad creative compliant with platform guidelines --- ## Operationalized In `snappy-ads` holds the live ad ops derived from this week. To execute against this week: - Read this file for the framework - Open `snappy-ads/SKILL.md` for live campaign management - Account/tracking stack lives in the snappy-ads infrastructure - Creative production routes through `snappy-video` + `snappy-image` - Targeting/scaling decisions log in `snappy-knowledge` for analytics retrieval
Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b
Operationalized in: snappy-ops
| state | description |
|---|---|
| INPUT (week starts with) | All previous weeks deployed: offer (W1), sales (W2), community (W3), traffic engine (W4), ads (W5). The business runs but is reactive -- no daily routine, no defined member ops, no clean financial reporting, no team structure. Founder is the bottleneck. |
| OUTPUT (week ends with) | A 6-category CEO daily workflow checklist running every morning. Close.com CRM and Helpscout support configured. 4 revenue source tracking live. Daily team standup process defined. Hiring template ready. Profit-share model decided. The business operates "machine-like" with predictable rhythm. |
Deliverables student finishes the week holding:
Overview of how we operate a mastermind business.
| framework | definition |
|---|---|
| Operations = Machine | Build systems that run predictably and repeatedly |
| pillar | description |
|---|---|
| 1. CEO daily workflow | Daily checklist that keeps everything moving |
| 2. Mastermind member ops | Managing leads and customers |
| 3. Financial ops | Tracking revenue, costs, and profit |
| 4. Team ops | Hiring, managing, retaining the right people |
Daily questions to ask yourself to run one of these businesses.
| category | daily question |
|---|---|
| 1. Cashflow management | Are we making money? What's the cash position? |
| 2. Cashflow contributors | What's driving revenue? Ads, organic, email, referrals? |
| 3. Operations | Is everything running smoothly? Any fires? |
| 4. Management & reporting | What do the numbers say? Are we on track? |
| 5. Product | Is the mastermind delivering value? Member satisfaction? |
| 6. Strategic initiatives | What longer-term bets are we making? |
How to manage your mastermind leads and customers.
| framework | definition |
|---|---|
| Lead-to-Customer Pipeline | Close.com CRM + Helpscout support |
| Member Operations Goals | Track every lead first touch -> close, manage onboarding/retention, handle support efficiently |
| tool | role |
|---|---|
| Close.com | CRM for sales pipeline, leads, customers |
| Helpscout | Customer support / helpdesk for member communications |
What to monitor financially in a mastermind business.
| revenue source | description |
|---|---|
| 1. Frontend mastermind | Recurring monthly revenue from frontend members |
| 2. Backend mastermind | Recurring revenue from backend members (higher ticket) |
| 3. Affiliate/referral commissions | e.g., Skool 40% MRR commissions |
| 4. One-time upsells | Add-ons and one-time products |
| framework | definition |
|---|---|
| Financial Goals | Maximize recurring revenue, minimize churn, healthy margins |
| Common Mistakes | Not tracking per-channel profitability, ignoring churn, overspending on team early |
How to hire and run a high-performance team.
| framework | definition |
|---|---|
| Daily Standup | Quick sync to align on priorities, blockers, progress |
| Hiring Process | Define role -> Source -> Interview -> Trial -> Hire |
| Profit Share Model | Align team incentives with business performance |
| Lean Team Philosophy | Keep team small and high-performing; each person should be a multiplier |
snappy-ops holds the live daily/weekly business rhythm derived from this week. To execute against this week:
snappy-ops/SKILL.md for the live CEO daily workflowsnappy-clients + snappy-skoolsnappy-freshbookssnappy-knowledgesnappy-ops (morning briefing, weekly review)# Week 6 -- Fine-Tuning Operations Source: https://www.skool.com/wetube-ss-8782/classroom/345a090b Operationalized in: `snappy-ops` ## Module Inputs / Outputs |state|description| |-----|-----------| |**INPUT** (week starts with)|All previous weeks deployed: offer (W1), sales (W2), community (W3), traffic engine (W4), ads (W5). The business runs but is reactive -- no daily routine, no defined member ops, no clean financial reporting, no team structure. Founder is the bottleneck.| |**OUTPUT** (week ends with)|A 6-category CEO daily workflow checklist running every morning. Close.com CRM and Helpscout support configured. 4 revenue source tracking live. Daily team standup process defined. Hiring template ready. Profit-share model decided. The business operates "machine-like" with predictable rhythm.| **Deliverables student finishes the week holding:** 1. CEO daily workflow checklist (6 categories) 2. Close.com CRM with sales pipeline stages 3. Helpscout configured for member support 4. Revenue tracking by source (frontend, backend, affiliate, upsells) 5. Churn + LTV + CAC dashboards 6. Daily standup process running with team 7. Hiring process template documented 8. Profit-share model decided and aligned --- ## 1. Operations Philosophy (26:46) Overview of how we operate a mastermind business. ### Key Points - Principles for machine-like operations - CEO daily workflow process - Mastermind member operations - Financial operations - Team operations ### Frameworks |framework|definition| |---------|----------| |Operations = Machine|Build systems that run predictably and repeatedly| |pillar|description| |------|-----------| |1. CEO daily workflow|Daily checklist that keeps everything moving| |2. Mastermind member ops|Managing leads and customers| |3. Financial ops|Tracking revenue, costs, and profit| |4. Team ops|Hiring, managing, retaining the right people| ### Resources - [Operations philosophy](https://docs.google.com/document/d/1vqk-niLlOBx_UPJza8WHdlIcwU1_0yH_V8n9nKElKdM/edit?usp=sharing) --- ## 2. CEO Daily Workflow (20:00) Daily questions to ask yourself to run one of these businesses. ### Key Points - Cashflow management - Things that contribute to cashflow - Operations - Management and reporting - Product - Strategic longer-term initiatives ### Frameworks |category|daily question| |--------|--------------| |1. Cashflow management|Are we making money? What's the cash position?| |2. Cashflow contributors|What's driving revenue? Ads, organic, email, referrals?| |3. Operations|Is everything running smoothly? Any fires?| |4. Management & reporting|What do the numbers say? Are we on track?| |5. Product|Is the mastermind delivering value? Member satisfaction?| |6. Strategic initiatives|What longer-term bets are we making?| ### Action Items - Build daily checklist covering all 6 categories - Review cashflow and cash position every morning - Check operational metrics before deep work - Reserve time for strategic thinking (not just firefighting) ### Resources - [CEO daily workflow](https://docs.google.com/document/d/1ErvTneLAeG5SgPcUmeZ4eVFmFvx0U4LtCSbBYrR5Yuo/edit?usp=sharing) --- ## 3. Mastermind Member Operations (29:47) How to manage your mastermind leads and customers. ### Key Points - Lead and customer management goals - Close.com setup and workflow - Helpscout setup and workflow ### Frameworks |framework|definition| |---------|----------| |Lead-to-Customer Pipeline|Close.com CRM + Helpscout support| |Member Operations Goals|Track every lead first touch -> close, manage onboarding/retention, handle support efficiently| |tool|role| |----|----| |Close.com|CRM for sales pipeline, leads, customers| |Helpscout|Customer support / helpdesk for member communications| ### Action Items - Set up Close.com with sales pipeline stages - Configure Helpscout for member support - Define lead workflow (lead -> call -> close -> onboard) - Create templates for common support scenarios ### Resources - [Mastermind member operations](https://docs.google.com/document/d/1CgiOwVmlH8lsmScdo0nRQZAvYCrb0uVb8xq2A4gpa7M/edit?usp=sharing) --- ## 4. Financial Operations (11:28) What to monitor financially in a mastermind business. ### Key Points - Goals from a financial lens - Accounting setup and workflow - The 4 revenue sources - Common financial mistakes ### Frameworks |revenue source|description| |--------------|-----------| |1. Frontend mastermind|Recurring monthly revenue from frontend members| |2. Backend mastermind|Recurring revenue from backend members (higher ticket)| |3. Affiliate/referral commissions|e.g., Skool 40% MRR commissions| |4. One-time upsells|Add-ons and one-time products| |framework|definition| |---------|----------| |Financial Goals|Maximize recurring revenue, minimize churn, healthy margins| |Common Mistakes|Not tracking per-channel profitability, ignoring churn, overspending on team early| ### Action Items - Set up proper accounting (bookkeeper or tool) - Track revenue by source (4 sources) - Monitor churn rate and LTV - Know CAC by channel ### Resources - [Financial operations](https://docs.google.com/document/d/1KmKlDvK_rig0LE714aEmON2LYC3fmXflL7_RjxD_rxQ/edit?usp=sharing) --- ## 5. Team Operations (19:48) How to hire and run a high-performance team. ### Key Points - Team goals - Daily standup workflow - Hiring process and time bottlenecks - Org chart and profit share model tips ### Frameworks |framework|definition| |---------|----------| |Daily Standup|Quick sync to align on priorities, blockers, progress| |Hiring Process|Define role -> Source -> Interview -> Trial -> Hire| |Profit Share Model|Align team incentives with business performance| |Lean Team Philosophy|Keep team small and high-performing; each person should be a multiplier| ### Action Items - Implement daily standups - Define org chart (even if just you + 1-2 people) - Create hiring process template - Consider profit share model to retain top performers ### Resources - [Team operations](https://docs.google.com/document/d/1f1wQyUmm6GAAhgxd-t-yKljlkm7-XtVm3Oq-Ja08G8g/edit?usp=sharing) --- ## Operationalized In `snappy-ops` holds the live daily/weekly business rhythm derived from this week. To execute against this week: - Read this file for the framework - Open `snappy-ops/SKILL.md` for the live CEO daily workflow - Member ops route through `snappy-clients` + `snappy-skool` - Financial ops route through `snappy-freshbooks` - Knowledge graph + analytics route through `snappy-knowledge` - Daily/weekly orchestration triggered by `snappy-ops` (morning briefing, weekly review)