#	Lesson	Why it hits	Outcome	Install	Len
01	Build & Release AI	If it is not released, it is not leverage.	Explain Cook Truth OS equation and what done looks like for your business.	Write your 1-page done definition (revenue, hours, systems, release cadence).	10m
02	The Road That Lays Ahead	Identity decides who survives hard weeks.	Separate owner vs operator beliefs; name the constraints that kill agencies.	B&R worksheet: 5 beliefs you hold vs 5 realities you will measure.	12m
03	Seek Truth, Find Your Market	Research first. Then lock the market you can win.	Find and lock a service market with clear ICP, problem, and proof path.	Market card: research notes / who / problem / offer angle / 90-day scoreboard.	15m
04	Who Does the Work? You or AI	Wrong tool = wasted week.	Route work to Claude, Cursor, or GHL automation with a decision tree.	Fill the AI decision tree for your top 10 recurring tasks.	12m

#	Lesson	Why it hits	Outcome	Install	Len
05	Own the Scroll	Attention is rented. Ownership is earned with a system.	Build a content / attention system that feeds your offer daily.	Scroll ownership card: platform, cadence, hook bank, CTA rule.	12m
06	Build an Offer They Can't Refuse	Weak offers make sales feel like begging.	Build a value stack for your service offer that feels unfair in your favor.	Offer gravity sheet: core offer, bonuses, guarantees, price anchor.	15m
07	Turn Cold Into Cooking	Most deals die in silence, not on the call.	Design nurture that warms inbound and outbound until they book.	Draft a 7-touch nurture map (channel + message + CTA).	12m
08	The Appointment Magnet	Traffic without a booking path is theater.	Ship a minimum viable landing / VSL / booking stack that books.	Checklist + wire the booking page linked from your primary CTA.	14m
09	Dominate One Channel	Scattered channels = slow death.	Pick 1–2 channels and map inbound vs outbound for your niche.	Battlefield card: primary channel, secondary, weekly volume target.	12m

#	Lesson	Why it hits	Outcome	Install	Len
10	Speak Truth	You cannot fix what you will not measure.	Track pipeline stages, show rate, and close rate on a simple dashboard.	Build a 1-screen sales math board (leads → booked → showed → closed).	12m
11	Read Their Mind on the Call	Diagnosis beats persuasion theater.	Run discovery questions that qualify and surface real pain.	X-ray script: 8 questions + disqualify rules.	14m
12	Collect The Cash	Ambiguous closes leave money on the table.	Deliver the offer cleanly and ask for the sale without sleaze.	Close card: offer order, ask line, payment path, next-step confirmation.	12m
13	Objection Assassin	Objections are information, not insults.	Handle the top objections without collapsing price or conviction.	Objection pack: top 5 objections + clarify / isolate / resolve lines.	14m

#	Lesson	Why it hits	Outcome	Install	Len
14	Blueprints Before Buttons	Software without SOPs is expensive chaos.	Map lists, flowcharts, and SOPs before touching tools.	One-page flowchart: lead → booked → closed → onboarded.	12m
15	GHL Systems & AI	CRM + AI as one command center, not a graveyard.	Operate GHL pipelines, calendars, conversations, and AI assist as one system.	Configure pipeline stages + calendar + conversation labels for your offer.	15m
16	From First Click to First Invoice	Manual handoffs leak deals.	Automate lead → booked → show → close → onboard on one path.	Ship one end-to-end automation path in GHL with a test contact.	15m
17	Architect the Engine	Integrations multiply you if they do not break you.	Connect tokens, webhooks, and AI hooks without breaking ops.	Integration map: what connects, where tokens live, who owns them.	12m
18	Speed-to-Lead God Mode	First reply wins. Brand voice still matters.	Use AI in GHL for speed-to-lead without sounding like a bot.	AI reply pack + tagging rules + human escalate triggers.	12m

#	Lesson	Why it hits	Outcome	Install	Len
19	Claude: Your Unfair Advantage	Most people use AI like Google. You will use it like staff.	Know when to use Chat vs Cowork vs Code.	Run the same business task in Chat and Cowork; log which won.	12m
20	Prompts That Print	Reusable systems beat clever one-offs.	Build prompt packs for offer, ads, sales, and SOPs.	Save 4 prompt templates in your vault with inputs + outputs.	14m
21	GitHub: Your Second Brain Vault	If it is not versioned, it is not an asset.	Use repos, commits, and branches as operator memory.	Create a personal ops repo; commit your offer + SOP pack.	15m
22	Vercel: .env's & Deployments	Live tools beat local demos.	Understand deploys, secrets, and why env vars matter.	.env checklist for any client tool you touch; no secrets in chat.	12m
23	Cursor Is a Cheat Code	IDEs turn ideas into shipped systems.	Compare Cursor, VS Code, Antigravity; know when to graduate.	Open Cursor; complete one real edit on a file in your ops repo.	15m
24	Cook Truth OS: Build Once, Fulfill Forever	Fulfillment software is the real moat.	See how Cook Truth OS turns delivery into leverage instead of labor.	Map your current fulfillment steps; mark which should become software.	12m

#	Lesson	Why it hits	Outcome	Install	Len
25	High-End Fulfillment	Retention dies in messy delivery.	Design a delivery experience that feels premium and clear.	Delivery scorecard: kickoff, cadence, status, win definition.	12m
26	Receipts That Sell	Proof is the cheapest sales team.	Install a proof capture loop that feeds content and closes.	Proof vault: 5 receipt slots (metric, quote, screenshot, Loom, before/after).	12m

#	Lesson	Why it hits	Outcome	Install	Len
27	90 Days to Unrecognizable	Focus compounds. Dabbling delays.	Build a 90-day scoreboard and weekly operating rhythm.	90-day plan one-pager: targets, weekly blocks, kill list.	15m
28	The Fast Lane	Some owners should not DIY every layer.	Decide honestly whether to DIY Cook Truth OS or buy speed with Cook delivery.	Decision memo: DIY path vs partner path with budget and timeline.	10m

#	Lesson	Len
01	Build & Release AI	10m
02	The Road That Lays Ahead	12m
03	Seek Truth, Find Your Market	15m
04	Who Does the Work? You or AI	12m

#	Lesson	Len
05	Own the Scroll	12m
06	Build an Offer They Can't Refuse	15m
07	Turn Cold Into Cooking	12m
08	The Appointment Magnet	14m
09	Dominate One Channel	12m

#	Lesson	Len
10	Speak Truth	12m
11	Read Their Mind on the Call	14m
12	Collect The Cash	12m
13	Objection Assassin	14m

#	Lesson	Len
14	Blueprints Before Buttons	12m
15	GHL Systems & AI	15m
16	From First Click to First Invoice	15m
17	Architect the Engine	12m
18	Speed-to-Lead God Mode	12m

#	Lesson	Len
19	Claude: Your Unfair Advantage	12m
20	Prompts That Print	14m
21	GitHub: Your Second Brain Vault	15m
22	Vercel: .env's & Deployments	12m
23	Cursor Is a Cheat Code	15m
24	Cook Truth OS: Build Once, Fulfill Forever	12m

#	Lesson	Len
25	High-End Fulfillment	12m
26	Receipts That Sell	12m

#	Lesson	Len
27	90 Days to Unrecognizable	15m
28	The Fast Lane	10m

Source	Steal this
Sam Ovens	Linear systems path: niche → offer → acquisition → delivery. Each lesson ends with a concrete install.
Iman Gadzhi	Agency-operator swagger. Simple SOPs. Do this week checkpoints that feel elite.
Hormozi	Offer math, value equation, objection handling. Ruthless, memorable titles.
Dan Koe	Leverage fantasy. One-person empire energy. AI as unfair advantage.

L01 Build & Release AI

Install

Model And Mindset · L01

Build & Release AI

Building with AI without a release habit is theater. Ship, or it does not count.

10m Install required

What we will cover

The Cook Truth OS equation
Twin pillars: Structure + Technology
Build vs release: the loop that creates leverage
What done looks like in this program
Watch → Install → Flex

Why this matters

Without a done definition and a release cadence, you will grind forever and call it work.

Model · Build → Release → Leverage

Build = unfinished until it touches the business
Release = live in ops, not stuck in chat history
Leverage = same effort, more output next week

Teaching beats

Info-product → knowledge transfer = leverage
Structure without tech stays slow; tech without structure stays chaotic
Define done: revenue, hours, systems, proof, release cadence
Program map: 7 chapters, 28 drops
Your job is installs, not binge-watching

Done definition template

Revenue target (90 days):
Hours/week max:
Systems that must be live:
Proof I will collect:
Release cadence (what ships weekly):

Anti-patterns

Watching every drop before installing anything
Calling local demos done
Collecting tools instead of shipping installs

Install

Write your 1-page done definition (revenue, hours, systems, release cadence).

Walk-away

You can explain Cook Truth OS and what build + release means for your business.

L02 The Road That Lays Ahead

Install

Model And Mindset · L02

The Road That Lays Ahead

Freelancer identity keeps you stuck in the work. Owner identity builds the machine. This is the road that lays ahead.

12m Install required

What we will cover

Owner vs operator beliefs
Constraints that kill agencies
Beliefs vs realities scoreboard
Where identity leaks into pricing and delivery

Why this matters

If you believe you are the product, you cannot productize. Growth dies in your calendar.

Model · Beliefs & Realities (B&R)

Belief: story you tell about how work must happen
Reality: measurable constraint (hours, cash, capacity)
Upgrade: replace beliefs that fight the numbers

Teaching beats

List 5 beliefs you operate from
List 5 realities you will measure weekly
Mark which beliefs contradict the realities
Rewrite one belief into an owner rule
Set a 7-day experiment to prove the new rule

Owner rule examples

I do not sell hours. I sell outcomes.
I do not be the bottleneck for delivery.
I review numbers weekly, not vibes.

Anti-patterns

Hero mode on every client fire
Pricing based on insecurity
Avoiding metrics because they feel cold

Install

B&R worksheet: 5 beliefs you hold vs 5 realities you will measure.

Walk-away

You can name owner vs operator beliefs and the constraints that kill agencies.

L03 Seek Truth, Find Your Market

Install

Model And Mindset · L03

Seek Truth, Find Your Market

Guessing a niche is expensive. Research finds the market. Then you lock it.

15m Install required

What we will cover

Research loops that surface real demand
How to find your market (not invent one)
ICP + problem + proof path
90-day lock after research says yes

Why this matters

Scattered markets scatter attention, offer, and proof. Research before you commit.

Model · Research → Find → Lock

Research: where buyers already talk, pay, and complain
Find: money + pain + urgency in one sentence
Lock: 90 days unless data forces a pivot

Teaching beats

Scan forums, ads, reviews, competitor comments for paid pain
Write ICP in one sentence
Name the problem they already pay to solve
Draft offer angle that is specific, not generic
Lock 90-day scoreboard: leads, booked, closed, cash

Market card

Who (ICP):
Problem they pay for:
Offer angle:
Where I found demand (links/notes):
90-day scoreboard:

Anti-patterns

Picking a niche because it is trendy
Serving everyone who can pay something
Pivoting weekly without data

Install

Market card: research notes / who / problem / offer angle / 90-day scoreboard.

Walk-away

You research, find your market, and lock ICP, problem, and proof path.

L04 Who Does the Work? You or AI

Install

Model And Mindset · L04

Who Does the Work? You or AI

Wrong tool = wasted week. AI is staff only if you route work correctly.

12m Install required

What we will cover

Decision tree: human, Claude, Cursor, GHL
Recurring task audit
When automation is premature
Quality bar for AI output

Why this matters

If everything is you, you have a job. If everything is AI with no judgment, you have garbage.

Model · Route Tree

Judgment / relationship → you
Thinking / drafts / research → Claude
Code / repo edits → Cursor
Repeatable CRM moves → GHL

Teaching beats

List top 10 recurring tasks
Score each: judgment, creativity, repetition, risk
Assign primary owner (you / Claude / Cursor / GHL)
Define review step for AI-owned tasks
Kill one task you should not be doing at all

Routing line

Task:
Owner:
Review by:
Done looks like:

Anti-patterns

Using ChatGPT as Google forever
Automating before the SOP exists
Letting AI talk to clients without guardrails

Install

Fill the AI decision tree for your top 10 recurring tasks.

Walk-away

You route work with a decision tree instead of vibes.

L05 Own the Scroll

Install

Offer And Attention · L05

Own the Scroll

If you do not own attention, you rent it from algorithms and hope.

12m Install required

What we will cover

Hook bank
Cadence that compounds
CTA discipline
Proof in public

Why this matters

Silent calendars start as silent feeds. Attention is the top of the pipe.

Model · Hook → Proof → Ask

Hook stops the scroll
Proof earns trust
Ask books the call

Teaching beats

Pick one primary feed
Write 20 hooks for your ICP pain
Set weekly cadence you can keep for 90 days
One CTA rule: every piece points to book or DM
Review weekly: what earned saves/replies

Hook bank starter

If you are still [pain] in 2026…
Stop doing [common mistake].
The real reason [ICP] stay stuck:

Anti-patterns

Posting randomly
No CTA
Chasing every platform

Install

Scroll ownership card: platform, cadence, hook bank, CTA rule.

Walk-away

You own a scroll system, not a hope strategy.

L06 Build an Offer They Can't Refuse

Install

Offer And Attention · L06

Build an Offer They Can't Refuse

Strong offers make sales feel obvious. Weak offers make closers look desperate.

15m Install required

What we will cover

Value equation
Core + bonuses
Risk reversal
Price anchor

Why this matters

You cannot close what people do not want. Offer gravity comes first.

Model · Hormozi Value Equation

Dream outcome × perceived likelihood
Divided by time delay × effort/sacrifice
Stack bonuses that remove friction, not fluff

Teaching beats

Write dream outcome in one line
List what raises likelihood of success
Cut time delay and effort with delivery design
Add 2–3 bonuses that remove objections
Set price next to the stack, not before it

Offer gravity sheet

Core offer:
Dream outcome:
Bonuses:
Guarantee:
Price + payment terms:

Anti-patterns

Discounting before stacking
Bonuses nobody wants
Vague outcomes

Install

Offer gravity sheet: core offer, bonuses, guarantees, price anchor.

Walk-away

You have an offer stack that feels unfair in your favor.

L07 Turn Cold Into Cooking

Install

Offer And Attention · L07

Turn Cold Into Cooking

Nurture is where trust compounds. One pitch is not a pipeline.

12m Install required

What we will cover

Cold / warm / hot states
7-touch map
Trust assets
CTA per touch

Why this matters

If you only pitch once, you leave money in the unread pile.

Model · 7-Touch Cook Map

Value
Proof
Clarify
Ask
Repeat with new angle

Teaching beats

Define cold / warm / hot for your offer
Map 7 touches across DM, email, content, call
Assign message + CTA per touch
Build 2 trust assets (case, teardown, Loom)
Run the map; stop random follow-ups

Touch line

Touch #:
Channel:
Message angle:
CTA:
Next if no reply:

Anti-patterns

Nagging without value
Same message 7 times
No CTA

Install

Draft a 7-touch nurture map (channel + message + CTA).

Walk-away

You run nurture that turns cold into cooking.

L08 The Appointment Magnet

Install

Offer And Attention · L08

The Appointment Magnet

Calendars are the conversion. Everything else is decoration until they book.

14m Install required

What we will cover

MVP booking stack
Primary CTA discipline
Friction kill list
Show-rate basics

Why this matters

If booking is hard, your ads and content pay a silent tax.

Model · Hook → Page → Calendar

One primary CTA
One page job
One calendar path

Teaching beats

List every place you ask for a booking
Collapse to one primary path
Strip form fields to the minimum
Confirm page + calendar + reminder
Test the path on mobile yourself

Booking stack checklist

[ ] Primary CTA copy
[ ] Landing or VSL live
[ ] Calendar connected
[ ] Confirmation + reminder
[ ] Mobile tested

Anti-patterns

Five CTAs on one page
Manual scheduling DMs
No reminders

Install

Checklist + wire the booking page linked from your primary CTA.

Walk-away

You have a booking path that actually books.

L09 Dominate One Channel

Install

Offer And Attention · L09

Dominate One Channel

Depth beats dabbling. Focus creates reps. Reps create pipeline.

12m Install required

What we will cover

Inbound vs outbound
Channel score
Volume targets
Kill criteria

Why this matters

Touching five channels halfway is how you stay average forever.

Model · Primary + Optional Secondary

Score by access, cost, proof fit
Set weekly volume
Kill in 14 days if dead

Teaching beats

List channels you touch today
Score access / cost / proof fit
Choose primary + optional secondary
Set weekly volume (posts, DMs, calls)
Review in 14 days: keep, fix, or kill

Battlefield card

Primary:
Secondary:
Weekly volume:
Kill criteria:
Review date:

Anti-patterns

Starting ads and organic and partnerships in week one
No volume target
Never killing a dead channel

Install

Battlefield card: primary channel, secondary, weekly volume target.

Walk-away

You dominate one channel instead of dabbling in five.

L10 Speak Truth

Install

Pipeline And Close · L10

Speak Truth

Opinions are not a pipeline. If the numbers do not speak, you are guessing with your livelihood.

12m Install required

What we will cover

Pipeline stages that matter
Show rate and close rate formulas
1-screen sales math board
How to diagnose leaks without drama
Weekly 15-minute truth ritual

Why this matters

Without numbers, coaching is vibes and growth is accidental. Teams fight about feelings instead of levers.

Model · Sales Math Truth Board

Stages: lead → booked → showed → closed → cash
Show rate = showed / booked
Close rate = closed / showed
Cash per lead = cash / leads
Only change one lever at a time

Teaching beats

Draw the four stages on one screen (Notion, Sheet, or GHL dashboard)
Pull last 14–30 days of real counts (no estimates)
Calculate show rate and close rate
Circle the biggest leak (booked→showed or showed→closed)
Set one weekly lever and one owner for it
Schedule a recurring 15-minute Friday truth review

Truth board columns

Week of:
Leads:
Booked:
Showed:
Closed:
Cash:
Show rate:
Close rate:
Cash/lead:
Biggest leak:
This week's lever:

Friday truth ritual (15 min)

1) Update counts
2) Recalc rates
3) Name the leak in one sentence
4) Pick one lever (reminders, offer, discovery, follow-up)
5) Assign owner + deadline
6) Do not add a second lever

Anti-patterns

Tracking vanity metrics (impressions, likes) instead of booked/showed/closed
Changing ads, offer, and script in the same week
Hiding bad weeks instead of diagnosing them
Using CRM stages that do not match the math board

Install

Build a 1-screen sales math board (leads → booked → showed → closed).

Walk-away

You track pipeline stages, show rate, and close rate on a simple dashboard you actually open.

L11 Read Their Mind on the Call

Install

Pipeline And Close · L11

Read Their Mind on the Call

Talking too soon is how you discount and get ghosted. Questions find the sale or kill it early.

14m Install required

What we will cover

X-ray discovery framework
Qualify vs disqualify rules
Pain, impact, urgency ladder
How to listen without pitching early
Permission-based agenda open

Why this matters

If you pitch before you understand, you sell the wrong thing to the wrong person at the wrong time.

Model · X-Ray Discovery

Agenda + permission first
Situation → Problem → Impact → Urgency
Disqualify is a win (protects calendar)
Pitch only after pain is vivid and owned

Teaching beats

Open with agenda and permission to ask hard questions
Situation: context of their business and current stack
Problem: what is broken in their words
Impact: cost of inaction (money, time, stress, status)
Urgency: why now vs later
Run disqualify rules out loud in your head before presenting
Only then bridge to the offer

Agenda open

Thanks for jumping on. Agenda is simple: I will ask a few questions to see if we are even a fit. If we are, I will show you how we help. If we are not, I will tell you straight. Sound good?

X-ray 8

1) What does the business look like today (offer, traffic, team)?
2) What made you book this call now?
3) What have you already tried?
4) What is the most expensive problem this is creating?
5) If nothing changes in 90 days, what happens?
6) Who else is involved in the decision?
7) What does a win look like in numbers?
8) On a 1–10, how ready are you to fix this in the next 30 days?

Disqualify rules

DQ if: no budget path, no decision authority, curiosity-only, wrong ICP, wants magic without install work, abusive vibe.
Script: Based on what you shared, we are not the right fit because __. Here is what I would do instead: __.

Anti-patterns

Pitching in the first five minutes
Leading the witness with your offer language
Fear of disqualifying (protecting ego over calendar)
Note-taking that kills eye contact and listening

Install

X-ray script: 8 questions + disqualify rules.

Walk-away

You run discovery that qualifies, surfaces real pain, and earns the right to present.

L12 Collect The Cash

Install

Pipeline And Close · L12

Collect The Cash

Ask for the sale. Take the money. Ambiguity is not kindness; it is unfinished business.

12m Install required

What we will cover

Offer delivery order
The ask line
Payment path readiness
Next-step confirmation
Handling silence after the ask

Why this matters

You can diagnose perfectly and still lose if you never ask. Soft closes create soft pipelines.

Model · Present → Ask → Path → Confirm

Present the stack against their stated pain
Ask clearly once
Have payment path ready
Confirm next step in calendar language

Teaching beats

Recap their pain and desired outcome in their words
Present core offer + key bonuses tied to that pain
State price and terms without apologizing
Ask: Are you ready to move forward with this?
If yes: payment link / invoice / contract path immediately
Confirm kickoff date and first deliverable
If not yet: isolate the real blocker (next lesson)

Bridge from discovery

Based on what you said about __, here is exactly how we solve that.

Ask line

The investment is __. That includes __. Are you ready to move forward with this?

Close card

Pain recap:
Offer one-liner:
Price / terms:
Ask line:
Payment path ready? Y/N
Kickoff date:
First deliverable:

Silence rule

After the ask: shut up. Count to 8 in your head. Do not discount into the silence.

Anti-patterns

Asking Would you maybe want to think about it?
Discounting before they object
No payment link ready
Celebrating verbal yes without next step booked

Install

Close card: offer order, ask line, payment path, next-step confirmation.

Walk-away

You can take the money cleanly: present, ask, path, confirm.

L13 Objection Assassin

Install

Pipeline And Close · L13

Objection Assassin

Amateurs defend. Operators clarify, isolate, and resolve. Most objections are confusion or timing, not true no.

14m Install required

What we will cover

Clarify → Isolate → Resolve
Top 5 objections for service offers
Price vs value vs timing
When to walk away
Post-objection re-ask

Why this matters

If objections scare you, you will pre-discount. If you steamroll them, you get refunds and resentment.

Model · C.I.R. Objection Loop

Clarify: what do you mean by that?
Isolate: aside from that, are we good?
Resolve: specific answer + proof + re-ask

Teaching beats

List your real top 5 objections from last 20 calls
Write clarify question for each
Write isolate line for each
Write resolve: proof, story, or process
Practice re-ask after resolve
Define walk-away conditions

C.I.R. skeleton

Clarify: When you say __, what specifically concerns you?
Isolate: If we solved __, would you be ready to move forward?
Resolve: Here is how we handle that: __.
Re-ask: Given that, are you ready to move forward?

Top 5 pack starters

1) Too expensive → What are you comparing it to? What does inaction cost?
2) Need to think → What specifically do you need to think through?
3) Talk to partner → Can we get them on a 10-min together today/tomorrow?
4) Bad timing → What happens if this waits 90 days?
5) Tried something like this → What failed, and how is this different?

Anti-patterns

Arguing with the objection
Stacking discounts
Accepting I need to think with no next step
Answering a smoke objection while the real one stays hidden

Install

Objection pack: top 5 objections + clarify / isolate / resolve lines.

Walk-away

You have an objection pack and a C.I.R. loop you can run under pressure.

L14 Blueprints Before Buttons

Install

Systems And CRM · L14

Blueprints Before Buttons

Draw the machine before you buy the tools. Buttons without blueprints multiply mess.

12m Install required

What we will cover

Flowchart first
Lists and stages
SOP stubs
Tool selection last

Why this matters

Jumping into GHL without a map creates zombie automations and confused teams.

Model · Map → Stages → SOP → Tool

Happy path first
Exceptions second
Automation third

Teaching beats

Draw lead → booked → closed → onboarded on one page
Name each handoff owner
List data you must capture at each stage
Write a 5-line SOP stub per stage
Only then open the CRM

Flowbox

Stage:
Trigger in:
Owner:
Done looks like:
Next stage:

Anti-patterns

Building 12 workflows on day one
No owner on stages
Copying someone else's GHL snapshot blindly

Install

One-page flowchart: lead → booked → closed → onboarded.

Walk-away

You have a blueprint before buttons.

L15 GHL Systems & AI

Install

Systems And CRM · L15

GHL Systems & AI

Your CRM is the command center. AI only helps if the system is clean.

15m Install required

What we will cover

Pipelines
Calendars
Conversation labels
AI assist boundaries
Hygiene

Why this matters

If the CRM is messy, AI multiplies the mess. Pipeline reflects mind.

Model · One Offer, One System

Stages match sales math
One booking path
AI drafts, humans decide

Teaching beats

Build stages that match Speak Truth board
Connect the only booking calendar
Label conversations for status
Enable AI assist for replies/tagging with escalate rules
Daily hygiene: open, move, close

Hygiene checklist

[ ] Open conversations cleared
[ ] Stages updated
[ ] No shadow trackers
[ ] AI replies reviewed if live

Anti-patterns

Parallel spreadsheets
AI auto-sending without review at first
Ten pipelines for one offer

Install

Configure pipeline stages + calendar + conversation labels for your offer.

Walk-away

You operate GHL systems with AI assist as one command center.

L16 From First Click to First Invoice

Install

Systems And CRM · L16

From First Click to First Invoice

Every manual hop is a place a lead disappears. Automation moves money while you sleep.

15m Install required

What we will cover

Thinnest end-to-end path
Stage moves
Reminders
Test contact discipline

Why this matters

Manual CRM work does not scale and silently kills show rate.

Model · Thin Path Automation

Automate notifications + stage moves first
Test before traffic
Watch failure points

Teaching beats

Pick the thinnest happy path
Automate stage moves + notifications
Confirm show reminders
Close → onboard trigger
Test with a fake contact before live traffic

Test contact script

Create test lead → book → mark showed → mark closed → confirm onboard tag/email fired.

Anti-patterns

Automating edge cases first
No test contact
Silent workflow failures

Install

Ship one end-to-end automation path in GHL with a test contact.

Walk-away

You automate lead to onboard on one clean path.

L17 Architect the Engine

Install

Systems And CRM · L17

Architect the Engine

Tokens are power and risk. Architect the engine before you wire chaos.

12m Install required

What we will cover

Integration map
Token ownership
Webhook failure plans
Least privilege

Why this matters

One leaked key or dead webhook can stop billing, booking, or delivery overnight.

Model · Map · Own · Monitor

What connects to what
Who owns each token
How you know it broke

Teaching beats

List every tool touching clients or cash
Draw arrows for data flow
Record where tokens live (never in chat)
Assign an owner per integration
Add a failure alert or weekly ping test

Integration row

System A ↔ System B:
Data moved:
Token location:
Owner:
Break symptom:
Fix path:

Anti-patterns

Tokens in Slack/Discord
Nobody owns Zapier
No alert when webhooks die

Install

Integration map: what connects, where tokens live, who owns them.

Walk-away

You have an integration map with owners and failure plans.

L18 Speed-to-Lead God Mode

Install

Systems And CRM · L18

Speed-to-Lead God Mode

Speed wins the lead. Tone wins the brand. You need both.

12m Install required

What we will cover

Reply SLA
AI draft pack
Escalate triggers
Brand voice rules

Why this matters

Slow follow-up is the most expensive silent leak in most books.

Model · Fast Draft → Human Judgment

AI drafts in seconds
Human sends until trusted
Escalate on price, legal, anger

Teaching beats

Set reply SLA (e.g. under 5 minutes during hours)
Write 5 AI reply templates in your voice
Define tags for hot / warm / junk
List escalate triggers
Review first 20 AI drafts before full auto

Escalate triggers

Escalate if: pricing negotiation, refund threat, legal language, abuse, VIP name, unclear ICP.

Anti-patterns

Instant auto-send with no review period
Robotic tone
No SLA

Install

AI reply pack + tagging rules + human escalate triggers.

Walk-away

You run speed-to-lead with AI assist and human judgment.

L19 Claude: Your Unfair Advantage

Install

AI And Leverage · L19

Claude: Your Unfair Advantage

Claude is staff only if you give it jobs, constraints, and a definition of done.

12m Install required

What we will cover

Chat vs Cowork vs Code
Job briefs for AI
Review loop
When not to use AI

Why this matters

Shallow prompts create shallow leverage. Staff-level use creates compounding output.

Model · Brief → Draft → Review → Release

Role + context + constraints + output format
Human review on risk
Save what works

Teaching beats

Pick one recurring business task
Run it in Chat with a tight brief
Run it in Cowork / multi-step if available
Log time, quality, edits required
Keep the winner as a saved pack

Staff brief

Role:
Context:
Constraints:
Output format:
Definition of done:

Anti-patterns

One-line prompts forever
Accepting first draft on client work
No saved winners

Install

Run the same business task in Chat and Cowork; log which won.

Walk-away

You use Claude like staff, not search.

L20 Prompts That Print

Install

AI And Leverage · L20

Prompts That Print

If your best prompt lives in chat history, you do not own it.

14m Install required

What we will cover

Pack structure
Four print packs
Versioning
Vault habit

Why this matters

One-off cleverness does not scale. Packs do.

Model · Role · Context · Constraints · Format

Inputs labeled
Outputs specified
Version like SOPs

Teaching beats

Template the four fields
Build offer / ads / sales / SOP packs
Test each on a real task
Store in vault/repo
Version when you improve

Pack header

Name:
Version:
Inputs:
Output:
Example:

Anti-patterns

Untitled chat genius
No inputs section
Never reusing winners

Install

Save 4 prompt templates in your vault with inputs + outputs.

Walk-away

You own prompt packs that print.

L21 GitHub: Your Second Brain Vault

Install

AI And Leverage · L21

GitHub: Your Second Brain Vault

Chat scrolls die. Repos remember. Versioned docs are business assets.

15m Install required

What we will cover

Ops repo
Commits as memory
Branches for experiments
No secrets in git

Why this matters

Lost docs and overwritten SOPs are a silent tax on your business.

Model · Vault Repo

Offer + SOPs + prompts live here
Commit messages explain why
Secrets never committed

Teaching beats

Create personal ops repo
Add folders: offer, sops, prompts, clients
Commit offer + SOP pack
Use branches for experiments
Add .gitignore for env files

First commits

feat: add offer gravity sheet
chore: add prompt packs v1
docs: add lead-to-cash SOP stub

Anti-patterns

Secrets in repo
No commit messages
Desktop folder as source of truth

Install

Create a personal ops repo; commit your offer + SOP pack.

Walk-away

You use GitHub as operator memory.

L22 Vercel: .env's & Deployments

Install

AI And Leverage · L22

Vercel: .env's & Deployments

If it is not deployed, it is a story. Secrets in the wrong place beat your business.

12m Install required

What we will cover

What a deploy is
Env vars
Preview vs prod
Secret hygiene

Why this matters

Local-only tools do not serve clients. Leaked keys create incidents.

Model · Build → Deploy → Configure secrets

Preview for tests
Prod for clients
Env for secrets

Teaching beats

Explain deploy in plain English
List secrets your stack needs
Put secrets in env, never in code/chat
Confirm preview vs production URLs
Write .env checklist for your next ship

.env checklist

[ ] Names documented
[ ] Values only in host env
[ ] Not in git
[ ] Not pasted in Discord
[ ] Rotated if exposed

Anti-patterns

API keys in screenshots
Shipping without env
Using prod for experiments

Install

.env checklist for any client tool you touch; no secrets in chat.

Walk-away

You can ship with Vercel: env hygiene and real deployments.

L23 Cursor Is a Cheat Code

Install

AI And Leverage · L23

Cursor Is a Cheat Code

Cursor is a cheat code when you give it a real repo and a real task.

15m Install required

What we will cover

When to use an IDE
Repo-aware edits
Small safe changes
Graduate path

Why this matters

Staying in chat forever caps what you can ship for clients and yourself.

Model · Task → File → Diff → Commit

Narrow task
Review diff
Commit when good

Teaching beats

Open ops repo in Cursor
Pick one real edit (README, SOP, prompt pack)
Let Cursor propose; you review
Accept only what you understand
Commit the change

IDE task brief

File(s):
Change:
Do not touch:
Done when:

Anti-patterns

Blind accept all
Huge unrelated refactors
No commit after success

Install

Open Cursor; complete one real edit on a file in your ops repo.

Walk-away

You used Cursor to ship one real change.

L24 Cook Truth OS: Build Once, Fulfill Forever

Install

AI And Leverage · L24

Cook Truth OS: Build Once, Fulfill Forever

If fulfillment is heroics, growth hurts. Build once. Fulfill forever.

12m Install required

What we will cover

Fulfillment map
Software vs SOP vs human
Client self-serve path
Moat thinking

Why this matters

Agencies die in delivery. Software and systems keep margin alive.

Model · Build Once → Fulfill Forever

Repeatable steps become product
Exceptions stay human
Proof loops into sales

Teaching beats

List fulfillment steps for one offer
Tag each: human / SOP / software
Pick one step to productize next
Define client-visible status
Connect proof capture to L26

Fulfillment row

Step:
Today owner:
Should become:
Client sees:
Proof captured:

Anti-patterns

Custom everything forever
No status for clients
Delivery knowledge only in one brain

Install

Map your current fulfillment steps; mark which should become software.

Walk-away

You see fulfillment as a productizable system.

L25 High-End Fulfillment

Install

Delivery And Proof · L25

High-End Fulfillment

Premium pricing without premium delivery creates churn and screenshots you will hate.

12m Install required

What we will cover

Kickoff ritual
Cadence
Status visibility
Win definition

Why this matters

Clients do not churn from price alone. They churn from confusion and silence.

Model · Kickoff → Cadence → Visible Wins

Clarity on day one
Rhythm they can trust
Wins they can see

Teaching beats

Write kickoff checklist
Set communication cadence
Define status the client can check
Agree win metrics in week one
Close each week with a short win note

Delivery scorecard

Kickoff date:
Cadence:
Status channel:
Win metrics:
Weekly win note template:

Anti-patterns

Ghosting between deliverables
No kickoff
Moving goalposts

Install

Delivery scorecard: kickoff, cadence, status, win definition.

Walk-away

Your fulfillment feels expensive on purpose.

L26 Receipts That Sell

Install

Delivery And Proof · L26

Receipts That Sell

If you do not capture receipts, your future self has to re-sell from scratch.

12m Install required

What we will cover

Proof types
Capture moments
Permission
Reuse in sales/content

Why this matters

No receipts means longer sales cycles and weaker content.

Model · Capture → Permission → Publish / Close

Capture in the moment
Ask permission
Reuse everywhere

Teaching beats

Create proof vault folder
Define 5 receipt types
Add capture trigger after each win
Ask for testimonial permission script
Reuse one receipt in content this week

Permission ask

Mind if I share this win (anonymized or named) as a case for other owners in your space?

Anti-patterns

Waiting until year-end for testimonials
No metrics, only vibes
Never asking

Install

Proof vault: 5 receipt slots (metric, quote, screenshot, Loom, before/after).

Walk-away

You have a proof vault that sells for you.

L27 90 Days to Unrecognizable

Install

Plan And Scale · L27

90 Days to Unrecognizable

Ninety days of locked focus will change the business more than a year of dabbling.

15m Install required

What we will cover

90-day targets
Weekly blocks
Kill list
Review cadence

Why this matters

Without a horizon, every shiny object wins. With one, you become dangerous.

Model · Target → Weekly Blocks → Review

Few targets
Protected time
Honest review

Teaching beats

Set 3 numeric 90-day targets
Block weekly time for installs
Write a kill list (what you will not do)
Schedule weekly review
Tie targets to Speak Truth board

90-day one-pager

Targets:
Weekly blocks:
Kill list:
Review day:
Chapter focus order:

Anti-patterns

20 priorities
No kill list
Skipping reviews

Install

90-day plan one-pager: targets, weekly blocks, kill list.

Walk-away

You have a 90-day plan that can make you unrecognizable.

L28 The Fast Lane

Install

Plan And Scale · L28

The Fast Lane

Skipping the line is not cheating. It is capital and taste. Do it with eyes open.

10m Install required

What we will cover

DIY vs partner
What you still must own
Budget / timeline honesty
No shame path

Why this matters

Wrong DIY burns runway. Wrong outsourcing burns trust. Choose on purpose.

Model · Own the Judgment, Buy the Leverage

You still own market, offer, ask
Partners can own build speed
Numbers still speak truth

Teaching beats

List layers you can execute weekly
List layers that stall you
Price your time vs partner speed
Write DIY vs partner memo
Pick a path for the next 90 days

Decision memo

DIY because:
Partner because:
Budget:
Timeline:
I still own:
Review date:

Anti-patterns

Outsourcing thinking
DIY pride that bankrupts you
No decision, endless limbo

Install

Decision memo: DIY path vs partner path with budget and timeline.

Walk-away

You chose DIY or skip-the-line with eyes open.

COOK TRUTH OS

Program map

Chapter 01 — Model And Mindset

Chapter 02 — Offer And Attention

Chapter 03 — Pipeline And Close

Chapter 04 — Systems And CRM

Chapter 05 — AI And Leverage

Chapter 06 — Delivery And Proof

Chapter 07 — Plan And Scale

A–Z drop list

Watch → Install → Flex

Watch

Install

Flex

Your arsenal

Beginner · Claude

Core · Go High Level

Intermediate · GitHub

Intermediate · Vercel

Advanced · Cursor

Platform · Cook Truth OS

Sources

What we will cover

Why this matters

Model · Build → Release → Leverage

Teaching beats

Done definition template

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · Beliefs & Realities (B&R)

Teaching beats

Owner rule examples

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · Research → Find → Lock

Teaching beats

Market card

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · Route Tree

Teaching beats

Routing line

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · Hook → Proof → Ask

Teaching beats

Hook bank starter

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · Hormozi Value Equation

Teaching beats

Offer gravity sheet

Anti-patterns

Install

Walk-away

What we will cover

Why this matters

Model · 7-Touch Cook Map

Teaching beats

Touch line

Anti-patterns

Install

Walk-away

What we will cover

Why this matters