Brief

Course 0 — Start Here (Onboarding) — Brief

Dream outcome (Hormozi value equation)

(Dream Outcome × Perceived Likelihood) ÷ (Time Delay + Effort)

• Dream Outcome: A new member knows exactly what to do in their first 30 minutes, exactly what's coming over the next 6 courses, and exactly where to show up — so the "I don't know where to start" feeling that kills most self-serve courses in week one never gets a chance to set in. They log in feeling like someone who has the office handled just walked them to their desk on day one.
• Perceived Likelihood: High, on purpose. This course asks for nothing hard — no new tool, no new habit, no homework that takes longer than a coffee break. It proves the whole program works the same way: small, specific, doable today. That first 30-minute win is the proof.
• Time Delay: Near zero. The roadmap is understood in one sitting. The Day-1 win is done inside 30 minutes of finishing this course.
• Effort: Minimal. Four short lessons, one template pointer, one place to show up. No setup, no software, no waiting on anyone else.

This course's entire job is to make that ratio as favorable as possible on day one, because Course 0 doesn't have to prove the business case — it has to prove the format isn't going to waste anyone's time.

Who this course is for

Every single person who just joined — before they've watched a single "real" lesson. Someone running a one-truck or small-crew service business (HVAC, plumbing, trades, events/rental, local services) who signed up because the Office Leak Quiz named a real pain, and who has 10 minutes right now, not an afternoon. They don't want a syllabus. They want to know: is this going to be worth my time, and what do I do right now.

Fastest believable win

Finishing lesson 0.3 and doing the 30-minute action it names: opening Course 1 and using the quote-in-10-minutes template on a real, live quote they currently owe a customer. Believable because it's not "watch 6 more courses first" — it's "one thing, today, on a job you already have sitting in your inbox."

The felt problem each lesson solves

• 0.1 Welcome — what this is and isn't: "I've signed up for stuff like this before and it turned into a slog of videos I never finished — is this different?" Solves the trust gap in the first 60 seconds by naming exactly what the course is (short, direct, built by someone who's run an office) and what it isn't (a certification program, a course you have to binge before it's useful).
• 0.2 Your roadmap — the 6 courses, in order, and why this order: "Where do I even start — invoices, reviews, follow-ups, all of it at once?" Solves the overwhelm of seeing six courses at once by explaining the order isn't arbitrary — it goes missed calls first because that's the leak bleeding the most money right now, then cash flow, then reputation, then follow-up, then the AI back office, then scaling — each one fixing the next-biggest leak once the last one's plugged.
• 0.3 Your Day-1 win — do this in the next 30 minutes: "I don't have time to 'get started,' I have a business to run." Solves the delay between signing up and getting value by pointing straight at Course 1's quote-in-10-minutes template — a single, concrete, 30-minute action with a real payoff today, not "someday."
• 0.4 Where to show up — the weekly live event, the community space, the pinned post: "Is this just another course I'll forget about in a folder somewhere?" Solves the disappearance problem by giving them a standing appointment (the weekly live event) and a home base (the community space, anchored by the pinned Start Here post) so the course has a pulse, not just a playlist.

How this connects to the course before and after it

• Before: There is no course before this one — Course 0 is the front door. The Office Leak Quiz is what gets someone here (it diagnoses their biggest leak and routes them in), but Course 0 is the first thing every member sees once they're inside the classroom, regardless of which leak the quiz flagged as worst.
• After: Course 0 hands off directly to Course 1 — Stop the Bleeding. Lesson 0.3 names Course 1's quote-in-10-minutes template by name as the Day-1 win, so there's no ambiguity about what to do next — a member finishes Course 0 and is already inside Course 1 doing the thing, not wondering which course to click.

Script

Course 0 — Start Here (Onboarding) — Script

Word-for-word lesson scripts, one section per lesson, matching the lesson list in _BLACKBOARD.md. Written to be read to camera or recorded as voiceover — short, plain, direct. No slides needed to follow along; visual treatment lives in visuals.md. Runtime target: under 15 minutes for all four lessons combined, per the brief's "takes about 15 minutes" promise.

---

Lesson 0.1 — Welcome — what this is and isn't

Format: Welcome video, to camera. ~2 minutes.

Script:

Hey — welcome to Back Office School.

Before you watch anything else, let me tell you what this is, and just as important, what it isn't.

This isn't a certification program. There's no test at the end, no 40-hour binge required before it's useful. You will never need to "finish" this to get value out of it.

This isn't a course library you're supposed to work through on your own with no one around. There's a live call every week and a community that's actually active — this comes with people in it, not just videos.

And this isn't theory from someone who's never run a service business. Every system in here — the callback scripts, the invoice chases, the review asks — is built by somebody who's actually run an office. Not a marketing agency's idea of what a plumber needs. The real thing.

Here's what it is. Six courses. Each one fixes one specific leak in your back office — missed calls, slow invoices, no reviews, no follow-up, no system for using AI without turning it into a toy, and eventually, how to grow without hiring your way into a headache. Each course ends with something you actually use that week — a script, a template, a sequence. Not a certificate. A tool.

You don't have to binge this. You don't have to do it in order to get something out of a single lesson. But it works best in order, because each leak you plug makes the next one easier to fix — and I'll show you exactly why in the next lesson.

Right now, all I need you to know is this: short lessons, real tools, a live call, and people in your corner. That's the whole deal.

Let's get you your first win. It's in the next lesson, and it takes about 30 minutes.

---

Lesson 0.2 — Your roadmap — the 6 courses, in order, and why this order

Format: Talking-head video with on-screen course list. ~3 minutes.

Script:

You've probably already scrolled the classroom and seen six courses sitting there. Here's the order, and more important, here's why it's this order and not some other one.

Course 1 is Stop the Bleeding. Missed calls, slow quotes. This goes first because it's the leak bleeding the most money right now, today, while you're watching this. A missed call isn't a missed conversation — it's a job that just booked with whoever picked up next. We start here because it's the fastest, most obvious win, and because fixing it is what pays for everything else you do this year.

Course 2 is Cash Flow Recovery. Once Course 1 is working, you're booking more jobs — which means more invoices out the door. Course 2 is what makes sure the jobs you just stopped losing actually turn into money you get paid. No point plugging the front door if cash still walks out the back.

Course 3 is the Reputation Engine. Once calls are answered and invoices are getting chased, you've got room to think past the current job — to the next ten customers who haven't found you yet. Reviews are how they find you. This is where we build that.

Course 4 is the Follow-Up System. Every business has a graveyard of old quotes and old customers who went quiet — not because they didn't like your work, but because nobody followed up. By Course 4 your intake and cash flow are solid enough that chasing old leads is worth your time again.

Course 5 is Your AI Back Office. This is new, and it's the one course where the word "AI" is actually allowed to show up without an eye-roll. Once the first four systems are running, you've got a real reason to want one place where every call, quote, and note lands — and one small automation doing a job you used to do by hand. We build both, plainly, with tools you probably already have.

Course 6 is Scale Without Hiring. The last stop. Once your back office runs itself most days, the real question becomes: do you hire, do you build more, or do you hand some of this to someone else? Course 6 lays out the honest version of that decision — no pressure either way.

That's the order: stop the leak, fix the cash, build the reputation, revive the old leads, get your systems talking to each other, then decide how you want to grow. Each one hands you something the next one needs.

You don't have to do them back to back. But do them in this order — it's built so each course is easier because of the one before it.

Next lesson: your first win, and it's not lesson 6 — it's 30 minutes from right now.

---

Lesson 0.3 — Your Day-1 win — do this in the next 30 minutes

Format: Talking-head video, direct-address. ~2 minutes. Ends in an on-screen action list (below).

Script:

I'm not going to make you wait to feel like this was worth it.

Here's your Day-1 win. It takes about 30 minutes, and you do it on a real quote you already owe a real customer right now — not a practice one.

Go open Course 1: Stop the Bleeding. Watch lesson 1.1 — it's a short walkthrough that gives you your Leak Score, a real number for what a missed call is costing you this month, in your own job value. Then go straight to lesson 1.2 and grab the quote-in-10-minutes template. Pick one quote you currently owe someone — a real person who's waiting to hear back from you — and fill it out. Send it today.

That's the whole assignment. One number, one quote, sent.

You didn't need to watch six courses first. You didn't need a new tool or a new process. You needed ten minutes and a template that already exists. That's true of almost everything in this program — small, specific, doable the same day you learn it.

If you do nothing else after this lesson, do this. It's the fastest proof that the rest of it works the same way.

On-screen action list (closing frame):

YOUR DAY-1 WIN — do this in the next 30 minutes

1. Open Course 1: Stop the Bleeding.
2. Watch lesson 1.1 — get your Leak Score (your real number).
3. Go to lesson 1.2 — grab the quote-in-10-minutes template.
4. Pick ONE quote you currently owe a real customer.
5. Fill it out. Send it. Today.

That's it. One quote, out the door, in the next half hour.

---

Lesson 0.4 — Where to show up — the weekly live event, the community space, the "Start Here" pinned-post copy

Format: Talking-head video. ~2-3 minutes. Ends in the exact pinned-post copy members are directed to (below), sourced verbatim from ops/community-and-cadence.md.

Script:

Last thing before you go do your Day-1 win: where do you actually show up after this?

Because here's the truth about courses like this one — most of them turn into a folder you forget about in three weeks. That's not going to happen here, because this isn't just a video library. It's a group of people, on a schedule.

Two places to know.

First, the community feed. That's where you introduce yourself, ask questions, and see what other owners are running into — real trades, real problems, not a comment section nobody reads. There's a post pinned at the top called Start Here. Go read it, then comment on it. Your trade, your city, and the one back-office problem that's bugging you the most this week. Not "everything" — pick the one that's actually costing you the most right now.

Second, the live call. We meet every [DAY] at [TIME] [TIMEZONE] — it's in the Events tab. Forty-five minutes. We open with wins from the week, we walk through whatever's live in the current course cycle, and then we open the floor to real problems — an invoice that won't get paid, a bad review that just landed, a backlog of missed calls. You bring the actual thing you're dealing with. That's what the call is for.

This group only works if you're actually in it — not just enrolled in it. So before you close this lesson: go comment on the Start Here post, and get that call on your calendar. Then go do your Day-1 win from the last lesson.

That's Course 0. Welcome in. See you in the comments.

Deliverable — the "Start Here" pinned-post copy (post this in the community feed):

Post title:

👋 Start Here — read this first (takes 2 minutes)

Post body:

Welcome to Back Office School.

If you run a service business — trades, HVAC, plumbing, events, cleaning, anything
where you're the one answering the phone AND doing the job — you're in the right
place.

Here's the deal: your tools are fine. Your back office is the leak. Missed calls,
slow quotes, invoices nobody chases, reviews nobody asks for — that's where the money
actually goes. This group fixes that, one system at a time, in an order that works.

**Do these 3 things right now:**

1️⃣ **Introduce yourself below.** Comment with your trade, your city, and the one
back-office problem that's bugging you most this week. (Not "everything" — pick one.)

2️⃣ **Go to Classroom → Course 0: Start Here.** It's four short lessons and takes
about 15 minutes. It tells you the order to do everything in and points you at your
first win — something you can finish in the next 30 minutes.

3️⃣ **Save the live call.** We meet every [DAY] at [TIME] [TIMEZONE] — link's in
Events. Come with a real problem from your business. That's what it's for.

That's it. No fluff, no "10 tips" listicle. Six courses, in order, each one ends in a
template or script you actually use that week. Start with Course 0.

See you in the comments. 👇

([DAY], [TIME], [TIMEZONE] are locked once the weekly live-event slot is set — per ops/community-and-cadence.md §7, fill in and keep identical across the pinned post, the welcome DM, and this lesson before launch.)

Visuals

Course 0 — Start Here: Visuals

Every visual below is grounded in the script's actual lines and structure — no generic stock-photo filler. Type options per the blackboard: stack / loop / step_diagram / comparison / matrix / stat / pull_quote / key_takeaway / statement / screenshot-mockup.

---

Lesson 0.1 — Welcome — what this is and isn't

Visual 1 — comparison: "What this ISN'T / What this IS"

Two-column card, built directly from the script's own three "isn't" beats vs. its "is" beat:

This ISN'T	This IS
A certification program — no test, no 40-hour binge required	Six courses, each fixing one specific leak
A course library you work through alone	A live weekly call + an active community
Theory from someone who's never run a service business	Built by somebody who's actually run an office

Bottom row spans both columns: Each course ends with a tool you actually use that week. Not a certificate. A tool. — the script's own closing line for this contrast.

Visual 2 — stat: "15 minutes in, one win out"

Small two-line stat card pairing the time investment against the payoff, both numbers pulled straight from the script's own promises: - Course 0: under 15 minutes (all four lessons) - Your first win: 30 minutes (next lesson) Reinforces the value-equation promise (low time delay, low effort) before the roadmap lesson even starts.

Visual 3 — key_takeaway: "The whole deal"

Closing card using the script's own line verbatim: "Short lessons, real tools, a live call, and people in your corner. That's the whole deal."

---

Lesson 0.2 — Your roadmap — the 6 courses, in order, and why this order

Visual 4 — step_diagram: "The 6-Course Chain" (on-screen course list)

This is the visual the script's own format note calls for directly ("talking-head video with on-screen course list") — build it as six sequential steps, each handing something to the next, using the script's exact one-line reason for each:

1. Course 1 — Stop the Bleeding → "the leak bleeding the most money right now"
2. Course 2 — Cash Flow Recovery → "makes sure the jobs you stopped losing actually turn into money"
3. Course 3 — Reputation Engine → "reviews are how they find you"
4. Course 4 — The Follow-Up System → "revive the graveyard of old quotes and old customers"
5. Course 5 — Your AI Back Office → "one place every call, quote, and note lands + one small automation"
6. Course 6 — Scale Without Hiring → "the honest version of the hire-or-not decision"

Connect each step to the next with the script's own hand-off phrase along the arrow: "Each one hands you something the next one needs."

Visual 5 — pull_quote

"A missed call isn't a missed conversation — it's a job that just booked with whoever picked up next." Full-bleed quote card — the single sharpest line in this lesson, and the thesis for why Course 1 goes first.

---

Lesson 0.3 — Your Day-1 win — do this in the next 30 minutes

Visual 6 — step_diagram: "Your Day-1 Win" (the script's own closing frame)

The script already specifies this as an on-screen action list — render it exactly as written, five numbered steps, no additions:

1. Open Course 1: Stop the Bleeding.
2. Watch lesson 1.1 — get your Leak Score (your real number).
3. Go to lesson 1.2 — grab the quote-in-10-minutes template.
4. Pick ONE quote you currently owe a real customer.
5. Fill it out. Send it. Today.

Closing line under the list, exactly as scripted: "One quote, out the door, in the next half hour."

Visual 7 — key_takeaway: "You didn't need six courses first"

Standalone card using the script's own reframe: "You didn't need to watch six courses first. You didn't need a new tool or a new process. You needed ten minutes and a template that already exists." This is the line doing the Hormozi "perceived likelihood" work — proving the whole program moves this fast before the learner has done anything else.

---

Lesson 0.4 — Where to show up

Visual 8 — comparison: "Two Places to Show Up"

Two-card comparison, one per place, using the script's own descriptions:

The community feed	The live call
Introduce yourself: your trade, your city, the one back-office problem bugging you most this week	Every [DAY] at [TIME] [TIMEZONE] — in the Events tab, 45 minutes
Read + comment on the pinned "Start Here" post	Opens with wins from the week, walks the current course cycle, then opens the floor to real problems
Real trades, real problems — not a comment section nobody reads	Bring the actual thing you're dealing with

Visual 9 — screenshot-mockup: The "Start Here" pinned post

Render the deliverable copy exactly as it will appear in the Skool community feed — title, emoji, the three numbered action items, and the closing "See you in the comments 👇" — so it reads as a real pinned post preview, not a blank template:

• Title: 👋 Start Here — read this first (takes 2 minutes)
• Body: the 1️⃣ Introduce yourself / 2️⃣ Go to Classroom → Course 0 / 3️⃣ Save the live call sequence, verbatim from the script's deliverable block, with [DAY], [TIME], [TIMEZONE] shown as literal placeholders (not filled in until the live-event slot is locked per ops/community-and-cadence.md §7).

Visual 10 — key_takeaway: "Enrolled vs. in it"

Closing card using the script's own distinction: "This group only works if you're actually in it — not just enrolled in it."

---

Total: 10 visuals across 4 lessons (2-3 per lesson, matching the "every course ships visuals" discipline in .claude/rules/ralph-wiggum.md — no lesson ships without at least one asset tied to its specific content).

Brief

Course 1 — Stop the Bleeding: Brief

Dream outcome (Value Equation terms)

Dream Outcome: Every call that rings your phone turns into a booked job or a quoted job — not a voicemail nobody calls back, and not a quote that sits for three days while the customer books someone else. The bleeding stops: no more work walking out the door because you were under a truck when the phone rang.

Perceived Likelihood: High, on purpose. This course doesn't ask the owner to buy software, hire someone, or change how they run jobs. It asks them to do three things a solo operator can do between jobs: know their real number (Leak Score), use one callback script, and run one week-long log. Believable because it's small and it's theirs to run today.

Time Delay: Same week. Lesson 1.1 gives them their number today. Lesson 1.2 gives them a habit they can start on the next quote they write. The deliverable — the quote-in-10-minutes template — is usable on the very next call, not after the course is "finished."

Effort: Low. No new tools, no new hires, no new software login. A callback script, a triage rule, and a 7-day log kept on paper or in their phone. The value equation math: Dream Outcome and Perceived Likelihood are both pushed up, Time Delay and Effort are both pushed down — that's what makes this the strongest first course in the stack, and why it's Course 1, not Course 4.

Who this course is for

The trades owner who is the business — plumber, HVAC tech, electrician, contractor, solo or small crew — answering their own phone between jobs, or letting it go to voicemail because both hands are full. They're not disorganized by nature; they're under-staffed by nature. This is the owner who has said, out loud or to themselves, "I know I'm losing jobs, I just don't know how many." They came in through the Office Leak Quiz already scored highest on the "missed calls / slow quotes" pain — this course is the direct answer to that score, not a general intro.

The fastest believable win

Inside the first 30 minutes of Course 0's Day-1 pointer, the owner runs the Leak Score walkthrough in 1.1 and gets a real number: what a missed call actually costs them, in their own average job value, this month. That number is the hook — it turns "I should probably follow up more" into "I am losing $X a week and here's the exact mechanism." Then they leave lesson 1.2 with the quote-in-10-minutes template already filled out for their own trade, ready to use on the very next call they take. No waiting for lesson 5, no waiting for the course to "build up" to something — the win is real by the end of the first sitting.

The felt problem each lesson solves

• 1.1 The real cost of a missed call (own Leak Score walkthrough) — solves "I have a vague, guilty feeling that I'm losing business, but no number to point at." Turns a feeling into a figure.
• 1.2 Same-day quote habit — solves "I meant to get that quote out today and then three days went by and they'd already hired someone else." Turns intention into a repeatable same-day routine.
• 1.3 "Not blocked, at a decision point" callback script — solves "I don't know what to say when I call someone back two hours late without sounding like I was ignoring them." Gives them the exact words that reframe lateness as being busy with paying work, not blowing them off.
• 1.4 Triage — what needs you vs. what doesn't — solves "Every call feels urgent when I'm mid-job, so I either drop the tool or let it ring — there's no middle option." Gives them a fast rule for which calls interrupt the work and which wait for the drive home.
• 1.5 Week 1 challenge: log every missed call for 7 days — solves "I don't actually know how often this happens to me specifically, versus trades in general." Makes the Leak Score personal and current instead of a one-time estimate.

Deliverable — quote-in-10-minutes template: solves the actual bottleneck behind the missed-call problem. Most quotes aren't slow because the owner is lazy — they're slow because building one from scratch every time takes longer than the job is worth chasing. The template removes the blank-page problem so "same-day quote" stops being aspirational and becomes a 10-minute task between jobs.

How this connects to the course before and after

Before — Course 0, Start Here: Course 0 hands the new member their roadmap and tells them their Day-1 win is inside Course 1 — specifically the quote-in-10-minutes template. Course 1 is the payoff of that promise. A member who skips straight here from onboarding should be able to get their Leak Score and template inside one sitting, no missing context.

After — Course 2, Cash Flow Recovery: Course 1 stops the leak at the front door — calls and quotes. Course 2 picks up the moment after: the job is booked, the work is done, and now the money has to actually come in. The same owner who used to lose jobs to a missed callback is now, by definition, running more jobs — which means more invoices in flight and a new version of the same root problem (no follow-up system) showing up on the money side instead of the lead side. Course 2 opens by naming that throughline directly: the follow-up gap that cost you the job in Course 1 is the same gap that lets an invoice go 45 days unpaid in Course 2.

Script

Course 1 — Stop the Bleeding: Script

Five lessons, one deliverable. Read straight through camera-ready — this is the word-for-word script, not an outline. Bracketed lines are on-screen text cues for whoever edits the lesson; everything else is spoken exactly as written.

---

Lesson 1.1 — The real cost of a missed call (own Leak Score walkthrough)

[ON SCREEN: "Your Leak Score"]

Grab a pen, or open the notes app on your phone. This one only works if you do it with me, using your own numbers — not an industry average, not somebody else's trade. Yours.

Here's the thing nobody tells you when you start a service business: the phone ringing isn't the sale. The phone ringing is the opportunity for a sale. Every time it rings and you don't answer, or you answer three hours later after the customer already called the next guy on the list, that's not a missed call. That's a job that walked out the door before you even knew it existed.

You already know this is happening. That's why you're here. What you don't have is a number. So let's get you one.

Three questions.

Question one: how many calls do you miss or let sit in a normal week? Not calls you call back in five minutes between jobs — those don't count. I mean calls that go to voicemail, calls you see and think "I'll get to that tonight," calls that sit for an hour or more. Count a normal week, not your worst week.

Question two: of the calls you do manage to call back, how many turn into a booked job? That's your close rate. If you book roughly four out of ten calls you return, your close rate is 40%. Don't round up. Be honest — this number is for you, nobody's grading it.

Question three: what's your average job value? Not your biggest job of the year, not the smallest. The job you write most often, on a normal week.

Now the math. It's one line:

Missed calls per week × your close rate × your average job value = what you're leaking in a week.

Let's run it once on a made-up example so you can see how it works, then you're going to run it again with your real numbers.

Say a plumber misses 6 calls a week, closes 40% of the calls he does return, and his average job is $450.

6 × 0.40 × $450 = $1,080 a week.

Multiply that by roughly 4.3 weeks and that plumber is looking at over $4,600 a month walking out the door — not because his work is bad, not because his pricing is wrong, but because of what happens (or doesn't happen) in the sixty seconds after the phone stops ringing.

[ON SCREEN: Leak Score formula — Missed calls/week × Close rate × Avg job value = Weekly leak]

That's the made-up example. Now do yours. Write down your three numbers, do the multiplication, and write the answer at the top of the page you're going to use for the rest of this course. That number is your Leak Score. It's not there to make you feel bad — it's there so the next four lessons have a target. You're not fixing "missed calls" in the abstract anymore. You're fixing a specific number of dollars, and you're going to watch it shrink week over week starting with Lesson 1.5's challenge.

One more thing before you move on: this number is almost always a floor, not a ceiling. It only counts calls you know you missed. It doesn't count the calls that rang through to a full voicemail box, or the customer who didn't bother leaving a message at all. Keep that in mind — your real leak is likely higher than what you just wrote down.

---

Lesson 1.2 — Same-day quote habit

[ON SCREEN: "The habit, not the hustle"]

Here's a pattern that shows up in almost every trade business, no matter what the trade is: the owner isn't losing jobs because they're lazy, and they're not losing jobs because their price is too high. They're losing jobs because the quote sat for two or three days while they meant to get to it, and by the time they did, the customer had already hired someone who called back first.

The fix isn't "work harder." The fix is a habit, and it's smaller than you think.

The rule: every quote goes out the same day the customer asks for it, or by end of day if the ask came in after your last job. Not "this week." Same day.

That sounds obvious when I say it out loud. It's hard to actually do for one reason: writing a quote from scratch, every single time, takes longer than most of these jobs are worth chasing. You're standing in your truck at 6pm trying to remember what you charge for a water heater swap versus what you charged the last guy, and it's easier to say "I'll do it tonight" and then not do it.

That's the actual bottleneck. Not time. Not laziness. The blank page.

So here's the habit, in three steps:

Step one — window it. Same day, or first thing the next morning if the call came in at night. That's the whole rule. Write it on your dash if you have to.

Step two — don't start from a blank page. You're going to get a quote-in-10-minutes template at the end of this course that has your standard line items, your standard pricing tiers, and your standard terms already sitting there. You're not writing a quote from nothing anymore. You're filling in three or four blanks specific to that one job — what it is, what it'll take, what it costs — and everything else is already done.

Step three — send it before you do anything else that isn't a paying job in front of you. Not after dinner. Not "when I get a chance." Before the next non-urgent task on your list. Make it the thing that happens right after you shut your truck door, not the thing that happens if there's time left over.

That's it. That's the habit. It costs you ten minutes and it's the single biggest lever in this entire course, because a same-day quote beats a better quote that shows up three days late, every time.

You'll get your actual template — filled out, ready to copy — at the end of this course. For now, just commit to the window: same day, no exceptions, starting with the next quote you write.

---

Lesson 1.3 — "Not blocked, at a decision point" callback script

[ON SCREEN: "What to say when you're calling back late"]

You already know the feeling. You look down, you've got three missed calls, and your gut reaction is guilt — like you got caught ignoring someone. That guilt is what makes people either avoid the callback altogether or open with an apology that makes the whole thing sound worse than it was.

Here's the reframe, and it's the whole lesson: you weren't ignoring anyone. You were at a decision point — doing paid work in front of you versus stopping to answer a phone. Every time. That's not an excuse, that's the actual truth of running a service business, and the second you say it like that instead of apologizing, the conversation changes.

So here's the script. Say it close to word for word the first few times, until it feels like yours.

If you're calling them back within the hour:

"Hey [Name], this is [Your Name] with [Business]. Sorry for the short delay — I was actually finishing up with a customer and wanted to call you back myself instead of leaving it for later. You mentioned [whatever they need] — walk me through what's going on and I'll get you a straight answer right now."

Notice what that does. It names the reason (with a customer, doing the job) without groveling, it credits them for reaching out, and it moves straight into solving their problem instead of dwelling on the delay.

If it's been longer — later that day, or the next morning:

"Hey [Name], [Your Name] with [Business] — got your message. Sorry it took me a bit to get back to you, we've had a full day of jobs. Is this still something you need help with, and if so, tell me what's going on."

That last question matters. It hands the conversation back to them instead of you guessing whether they're still interested, and it doesn't apologize twice.

If they say "I already called someone else":

"Totally understand, no hard feelings at all. If anything changes or you need a second opinion down the line, you've got my number now. Appreciate you giving me the shot."

Don't argue, don't undersell the other guy, don't get weird about it. You want this person calling you first next time, and the way you handle losing this one is what decides that.

If you're the one who has to leave the voicemail (they didn't pick up your callback):

"Hey [Name], it's [Your Name] with [Business] returning your call. I was tied up on a job earlier — didn't want you thinking I was blowing you off. Give me a call back whenever, or text me the details and I'll get you a number today."

That's four situations, four scripts, and one idea underneath all of them: you are not behind, you are not blocked, you are a business owner who was busy doing paid work, and now you're back. Say it like that and it stops sounding like an excuse and starts sounding like exactly what it is.

---

Lesson 1.4 — Triage: what needs you vs. what doesn't

[ON SCREEN: "Two questions, every call"]

The reason phone triage feels impossible mid-job is that it feels like every call is urgent. You're under a sink or up on a roof, the phone buzzes, and your brain gives you exactly two options: stop everything, or ignore it completely. There's no middle setting. That's the actual problem this lesson fixes — not "answer more calls," but give you a fast rule for the calls that genuinely can't wait versus the ones that can wait until you're back in the truck.

Two questions. Ask them about any call, in this order.

Question one: is this happening right now, and is it getting worse the longer it sits? Active water damage, no heat in freezing weather, a gas smell, no power to something that matters — that's a "yes." A cracked tile, a quote for a kitchen remodel next spring, a "can you call me back sometime today" — that's a "no."

Question two: is this someone who's already decided to hire you, or someone still deciding whether to? A current customer with an active job in progress outranks a brand-new lead every time, because you already have their money and their trust — protect that relationship first.

Put the two together and you get four boxes:

1. Urgent + current customer — stop what you safely can and take the call. This is the actual emergency, and it's also the person most likely to tell other people how you handled it.
2. Urgent + new lead — take it if you can do it safely in under two minutes; otherwise text back immediately: "Saw your call, is this an active emergency? Reply yes and I'll call you back in the next 10 minutes." That single text turns a missed call into a held place in line instead of a lost lead.
3. Not urgent + current customer — let it ring, but it goes to the very top of your callback list for your drive home. These are the easiest calls to lose by accident because nothing about them feels urgent, and they're the ones most likely to feel neglected if you sit on them too long.
4. Not urgent + new lead — this is exactly what Lesson 1.2's same-day quote habit exists for. It doesn't interrupt the job in front of you, and it doesn't sit for three days either. It gets the same-day window, no more, no less.

That's the whole rule: urgency first, relationship second, everything else waits for the drive home — but "waits" means hours, not days. You're not trying to answer every call the instant it rings. You're trying to make sure nothing falls through a crack that didn't need to be there in the first place.

---

Lesson 1.5 — Week 1 challenge: log every missed call for 7 days

[ON SCREEN: "7 days. Every call. No editing."]

Your Leak Score from Lesson 1.1 is an estimate — a good one, built off your real numbers, but still a guess about a normal week. This challenge turns the guess into a fact, and it takes seven days.

The rule for the week: every call you miss, or let go to voicemail, or answer late, gets written down. All of it. Even the ones you'd rather not count.

Here's the log. Six columns, one row per call. Use paper, your phone's notes app, or a sticky note stuck to your dash — the format doesn't matter, the discipline does.

DATE  |  TIME  |  CALLER / JOB TYPE  |  MISSED / LATE?  |  CALLED BACK BY  |  OUTCOME
------|--------|---------------------|------------------|------------------|----------
                |                     |                  |                  | Booked / Quoted / Lost / No answer

Fill in "OUTCOME" honestly, especially "Lost" and "No answer" — those two rows are the ones that teach you the most, because they're the leak in action, in real time, not in a formula.

At the end of the week, do three things:

1. Count the rows. How many calls actually came in that you missed or answered late? Compare that to the number you used in your Lesson 1.1 Leak Score. Most owners find their real number is higher, not lower — voicemail boxes and quiet no-answers don't show up until you're actually counting.
2. Re-run the Leak Score math with your real week's numbers. Missed calls × close rate × average job value. That's your updated, evidence-based leak, not an estimate.
3. Circle the "Lost" and "No answer" rows and ask one question of each: was this a triage miss (Lesson 1.4), a callback-script miss (Lesson 1.3), or a quote-speed miss (Lesson 1.2)? You're not looking for blame. You're looking for which one of the last three lessons would have saved that specific job — that's how you know which habit to tighten first.

Seven days from now you'll have something almost nobody in your position has: an actual, current, evidence-based number for what a missed call costs you, and a short list of exactly which fix would have caught each one. That's Course 1, finished — not because you read it, but because you ran it on your own week.

---

Deliverable — Quote-in-10-Minutes Template

This is the template referenced in Lesson 1.2. Copy it, fill in your standard line items once, and every quote after that is a fill-in-the-blanks job, not a blank page.

=====================================================
                    JOB QUOTE
=====================================================

[YOUR BUSINESS NAME]
[Phone] | [Email] | [License / Insurance # if applicable]

Quote #: __________          Date: __________
Valid for: 15 days from date above

-----------------------------------------------------
CUSTOMER
-----------------------------------------------------
Name: ______________________________________
Address: ____________________________________
Phone: _____________  Best time to reach: _______

-----------------------------------------------------
WHAT YOU CALLED ABOUT
-----------------------------------------------------
(One or two lines, in the customer's own words — this
is what makes the quote feel like it was written for
THEM, not copy-pasted.)

_______________________________________________
_______________________________________________

-----------------------------------------------------
THE JOB
-----------------------------------------------------
Description of work: __________________________
_______________________________________________

Estimated start: _______  Estimated duration: _______

-----------------------------------------------------
PRICE BREAKDOWN
-----------------------------------------------------
Labor:                                    $ _______
Materials/parts:                          $ _______
[Standard add-on line, e.g. disposal fee,
trip charge, permit fee — pre-fill your own]:
                                           $ _______
-----------------------------------------------------
TOTAL:                                    $ _______

Deposit required to schedule (if any):    $ _______
Balance due on completion:                $ _______

-----------------------------------------------------
TERMS
-----------------------------------------------------
- This quote is valid for 15 days from the date above.
- Price assumes [your standard assumption, e.g. "no
  hidden damage found once work begins" — pre-fill].
- Payment due on completion unless a deposit schedule
  is agreed above.

-----------------------------------------------------
READY TO BOOK?
-----------------------------------------------------
Reply YES to this text/email, or call [phone], and
I'll get you on the schedule for [earliest available
day]. First one to confirm gets the slot.

— [Your name]
=====================================================

How to make this a 10-minute job instead of a 30-minute one: before your next quote, sit down once and pre-fill everything that doesn't change call to call — your business name and contact info, your standard add-on line items, your standard terms paragraph, your standard deposit policy. Save that as your master copy. From then on, every quote is just: customer info, the one or two lines in their words, the job description, and the numbers. That's the whole habit from Lesson 1.2, built into a document instead of left to memory.

Visuals

Course 1 — Stop the Bleeding: Visuals

Every visual below is grounded in the script's actual numbers, lines, and structure — no generic stock-photo filler. Type options per the blackboard: stack / loop / step_diagram / comparison / matrix / stat / pull_quote / key_takeaway / statement / screenshot-mockup.

---

Lesson 1.1 — The real cost of a missed call

Visual 1 — step_diagram: "Three Questions → One Formula"

Three numbered steps building left to right (or top to bottom), each one a question box feeding into the next, ending in the formula: 1. Q1 — "How many calls do you miss or let sit in a normal week?" 2. Q2 — "Of the calls you call back, how many turn into a booked job? (your close rate)" 3. Q3 — "What's your average job value?" → arrows converge into: Missed calls/week × Close rate × Avg job value = What you're leaking in a week. This is the on-screen cue already marked in the script ("Leak Score formula") — make it literal and legible, not decorative.

Visual 2 — stat: The worked example reveal

Big-number stat card walking through the plumber example exactly as scripted: - Small line: "6 missed calls/week × 40% close rate × $450 avg job" - Large reveal number: $1,080/week - Secondary large reveal below it: $4,600+/month Use a two-step reveal (weekly number first, monthly number second/bigger) so it lands as the "oh" moment the script is building to — this is the single highest-leverage visual in the lesson.

Visual 3 — key_takeaway: "Your leak is a floor, not a ceiling"

Closing card for the lesson using the script's own line: "This number is almost always a floor, not a ceiling." Sub-line: "It doesn't count calls that rang through to a full voicemail box, or customers who didn't bother leaving a message." Keeps viewers from treating their Leak Score as a worst case.

---

Lesson 1.2 — Same-day quote habit

Visual 4 — step_diagram: "The Habit, Not the Hustle" (3 steps)

Three sequential steps, each with its own icon/label, matching the script verbatim: 1. Window it — same day, or first thing next morning if the call came in at night. 2. Don't start from a blank page — pre-filled template (line items, pricing tiers, terms already sitting there); you only fill 3-4 blanks. 3. Send it before anything else that isn't a paying job in front of you — not after dinner, not "when I get a chance."

Visual 5 — pull_quote

"A same-day quote beats a better quote that shows up three days late, every time." Full-bleed quote card — this is the lesson's thesis line and the strongest one-liner in the whole course.

---

Lesson 1.3 — "Not blocked, at a decision point" callback script

Visual 6 — comparison: Four callback situations, four scripts

Four-column (or four-card) comparison, one per scenario exactly as scripted, each showing the situation label + the opening line of its script so viewers can scan which one applies to them: 1. Calling back within the hour — "Sorry for the short delay — I was actually finishing up with a customer..." 2. Calling back later that day / next morning — "Got your message. Sorry it took me a bit to get back to you, we've had a full day of jobs." 3. They already called someone else — "Totally understand, no hard feelings at all... you've got my number now." 4. Leaving the voicemail yourself — "I was tied up on a job earlier — didn't want you thinking I was blowing you off."

Visual 7 — key_takeaway

"You are not behind, you are not blocked — you are a business owner who was busy doing paid work, and now you're back." Closing reframe line, standalone card.

---

Lesson 1.4 — Triage: what needs you vs. what doesn't

Visual 8 — matrix: The Four Boxes (2×2)

This is a literal 2×2 in the script ("put the two together and you get four boxes") — build it as an actual matrix, not a list:

	Current customer	New lead
Urgent	Stop and take the call — the real emergency	Take it if safe in under 2 min; otherwise text: "Is this an active emergency? Reply yes and I'll call in 10 min."
Not urgent	Top of your callback list for the drive home	Same-day quote window (Lesson 1.2) — no more, no less

Axis labels exactly as scripted: "Is this happening right now and getting worse?" (urgent/not) × "Have they already decided to hire you, or still deciding?" (current customer/new lead).

Visual 9 — key_takeaway

"Urgency first, relationship second, everything else waits for the drive home — but 'waits' means hours, not days." Closing rule card.

---

Lesson 1.5 — Week 1 challenge: log every missed call for 7 days

Visual 10 — screenshot-mockup: The 7-Day Call Log

Render the exact 6-column log format from the script as a filled-in mock (with 2-3 sample rows so it doesn't look empty), so viewers can see what "done right" looks like before they start their own: DATE | TIME | CALLER / JOB TYPE | MISSED / LATE? | CALLED BACK BY | OUTCOME — with OUTCOME options shown: Booked / Quoted / Lost / No answer. Sample row should echo the lesson's own emphasis: a "Lost" or "No answer" row filled in, since the script calls those the two that teach the most.

Visual 11 — step_diagram: "End of Week, Three Things"

Three-step sequence exactly as scripted: 1. Count the rows — compare to your Lesson 1.1 estimate (most owners find the real number is higher). 2. Re-run the Leak Score math — with your real week's numbers instead of the estimate. 3. Circle every "Lost"/"No answer" row — ask which lesson would've caught it: triage (1.4), callback script (1.3), or quote speed (1.2).

---

Deliverable — Quote-in-10-Minutes Template

Visual 12 — screenshot-mockup: The filled template

Full render of the actual template from the script — business header, customer block, "what you called about" (in the customer's own words), job description, price breakdown (labor / materials / standard add-on line / total / deposit / balance), terms, and the closing "Reply YES... first one to confirm gets the slot" line. Show it filled with a plausible sample job so it reads as a real document, not a blank form.

Visual 13 — comparison: Before / After the template

Two-sided comparison card: - Before: "Blank page, 30 minutes, standing in the truck at 6pm trying to remember your own pricing." - After: "Pre-filled master copy, 10 minutes, just customer info + the job + the numbers." Directly reinforces the lesson 1.2 promise that the template turns the habit into a document instead of leaving it to memory.

---

Total: 13 visuals across 5 lessons + 1 deliverable (2-3 per lesson, matching the "every course ships visuals" discipline — no lesson ships without at least one asset tied to its specific content).

Brief

Course 2 — Cash Flow Recovery — Brief

Dream outcome (Value Equation terms)

Dream Outcome: Money that's already been earned actually lands in the bank — without the owner turning into the person who hounds customers for cash.

Value Equation: (Dream Outcome × Perceived Likelihood) ÷ (Time Delay + Effort)

• Dream Outcome — invoices get paid close to on time, and the awkward "so, about that invoice" conversation stops living rent-free in the owner's head.
• Perceived Likelihood — high. This isn't "get better clients" or "raise your prices" (both true, both slow). It's "send the message you're already avoiding, on a schedule, in words that don't sound like a threat." That's believable in a way "fix your pricing" isn't.
• Time Delay — same week. The chase sequence gets built and sent to real overdue invoices before Course 2 is even finished.
• Effort — low. No new software, no accountant, no collections agency. Four message templates and a habit of running them on a schedule.

High likelihood, low delay, low effort — against a dream outcome the owner already wants every week (this is the one where the money question becomes a system question instead of a stomach-drop feeling).

Who this course is for

The owner who is good at the trade and bad at being the bank. They finished the job, the customer was happy, and now real money is sitting unpaid for weeks because following up feels like accusing a customer of stiffing them. They've eaten the cost of "I don't want to be that guy" more than once. They are not disorganized — they are avoidant, on exactly one task: asking for money that's already theirs.

The fastest believable win

By the end of Course 2, the owner has a written 3/15/30/45-day chase sequence — four messages, word for word, that go out automatically as an invoice ages — and they've run it against every invoice currently sitting past 30 days. The win isn't "better bookkeeping." It's watching one specific overdue invoice get paid because a pre-written message went out that they didn't have to compose in the moment, sitting with the cursor blinking, trying to sound polite and firm at the same time.

The felt problem each lesson solves

• 2.1 Why invoices go unpaid (follow-up gap, not the customer) — solves the self-blame spiral ("did I do something wrong, is this customer just a deadbeat"). Reframes it: most unpaid invoices aren't a character problem with the customer, they're a follow-up gap on the business's side. That reframe is what makes it okay to send message #2.
• 2.2 Friendly→firm chase sequence — solves "I don't know what to say and I don't want to sound like a bill collector." Gives the exact escalation ladder so the owner never has to improvise tone under pressure.
• 2.3 Deposit/progress-billing scripts — solves the version of this problem that shows up before the job is even done: getting paid in stages so the whole invoice never hits 45 days past due in the first place.
• 2.4 Collections texts that don't burn the relationship — solves the fear that chasing money will cost them the customer (and the referrals that customer would've sent). Shows how to be firm about money without being hostile about the relationship.
• 2.5 Week 2 challenge: chase every invoice past 30 days — solves "I know I should do this but I keep not doing it." Turns the whole lesson set into one dated action this week, against real invoices sitting in the owner's own books right now.

How this connects to the courses around it

• Before (Course 1 — Stop the Bleeding): Course 1 fixes the front door — missed calls and slow quotes, the leaks that lose a job before it's ever won. Course 2 picks up right after the job is done: the job got won, the work got done, and now the leak is on the back end — money earned but not collected. Same Leak Score logic, next leak in the sequence.
• After (Course 3 — Reputation Engine): Once an invoice actually gets paid on a predictable timeline, the relationship is in good enough shape to ask for something else: a review. Course 3 opens on the same insight that powers Course 2 — most customers don't ignore you, they just need to be asked, on a schedule, in the right words — and applies it to reviews instead of invoices.

Script

Course 2 — Cash Flow Recovery — Script

Word-for-word lesson script. Read this as spoken narration to camera/voiceover unless a line is explicitly marked as on-screen text or a template block.

---

Lesson 2.1 — Why invoices go unpaid (follow-up gap, not the customer)

Here's the invoice you're not thinking about right now. It's the one from six weeks ago. Job went fine. Customer was happy. You sent the invoice the same day you finished. And it's just... sitting there.

And somewhere in the back of your head, a story's already writing itself about why. Maybe they're broke. Maybe they didn't like the work as much as they said. Maybe they're the kind of person who stiffs contractors and you should've known better.

Put that story down. It's almost never true.

Here's what's actually true, most of the time: they meant to pay it. It landed in an inbox, or on a counter, next to four other bills, and it lost. Not because your invoice mattered less — because nothing happened after it. No reminder. No second touch. No nudge. Silence reads as "not urgent," and not urgent means it gets paid whenever, which in practice means it gets paid never, until somebody asks again.

So the problem you've got is not a customer problem. It's a follow-up gap. You built a business that's great at doing the job and hasn't built the second half — the part where you get paid for the job. Those are two different skills, and you're only missing one of them.

This matters because of what it changes about the next four lessons. If the problem were "the customer is bad," the fix would be to fire customers, which doesn't grow a business. But if the problem is "nobody followed up," the fix is a follow-up system — something you build once and run every time, instead of something you have to work up the nerve to do every time.

That's what the rest of this course hands you: a system, not a confrontation. You are not about to become the person who hounds people for money. You're about to become the person whose invoices get paid because a message went out on a schedule, the same way every time, whether you were thinking about that invoice or not.

One more thing before we move on, because it matters: following up on an invoice is not rude. It's not awkward. It's not accusing anyone of anything. It's finishing the transaction the customer already agreed to when they said yes to the job. You finished your half. This is just closing out theirs.

---

Lesson 2.2 — Friendly→firm chase sequence

You don't need to be a different person on day 3 than you are on day 45. You need four messages, each one turned up one notch from the last, so the tone does the escalating instead of you having to decide in the moment how mad to sound.

Here's the ladder:

• Day 3 — a reminder. Assume the best. They probably just haven't seen it.
• Day 15 — a check-in. Still friendly, but now it names the invoice number and asks directly if there's a problem.
• Day 30 — direct. No more "just checking in." This one states the amount, states how overdue it is, and asks for a payment date.
• Day 45 — firm. This one states what happens next if payment doesn't come, calmly, without threats you're not prepared to follow through on.

That's the whole ladder. Four touches. You're not calling every week hoping they feel guilty. You're running a schedule.

Here is the sequence, word for word. These go out by text or email — whichever this customer has used with you before.

Your 3/15/30/45-Day Chase Sequence

Day 3 — Reminder

Hi [Customer Name], this is [Your Name] with [Business Name]. Just a quick heads-up that invoice #[Invoice Number] for $[Amount] went out on [Invoice Date] — wanted to make sure it landed okay. No rush, just flagging it. Let me know if you need me to resend it or if you have any questions.

Day 15 — Check-in

Hi [Customer Name], following up on invoice #[Invoice Number] for $[Amount], sent [Invoice Date] — it's still showing as outstanding on my end. Is everything okay on your side, or is there something I can help sort out? Just want to make sure nothing fell through the cracks.

Day 30 — Direct

Hi [Customer Name], invoice #[Invoice Number] for $[Amount] is now 30 days past due. I want to get this squared away for both of us — can you let me know a date I can expect payment by? Happy to work with you on timing if something's come up. Here's the invoice again if you need it: [Payment Link].

Day 45 — Firm

Hi [Customer Name], this is a final notice on invoice #[Invoice Number] for $[Amount], now 45 days past due. If I don't hear back or receive payment by [Date — 7 days out], I'll need to [pause future work / send this to collections / apply a late fee per our agreement — pick the one that's true for your business]. I'd rather resolve this directly with you first. Please call or text me at [Your Number] so we can sort it out.

Two rules for using this ladder. One: never skip a rung. Going straight from day 3 to day 45 tone reads as unhinged, because the customer has no idea you were quietly stewing for six weeks. Two: as soon as they respond — even just to say "sorry, sending it Friday" — the sequence stops. This isn't a script you run on autopilot past the point it's doing its job. It's a script you run because you'd otherwise do nothing at all.

---

Lesson 2.3 — Deposit/progress-billing scripts

Everything in lesson 2.2 is about collecting money after the fact. This lesson is about never letting the full invoice hit day 45 in the first place — by getting paid in pieces, as the job happens, instead of one number at the end.

Two situations, two scripts.

Situation one: you require a deposit before starting. Say this before you schedule the job, not after:

Before I get you on the schedule, I collect a [deposit amount or percentage — e.g., "$200" or "30%"] deposit to lock in your date and cover materials. The rest is due when the work's complete. I can send you a link right now if you're ready to book.

Situation two: it's a bigger job, split into stages. Say this when you're quoting the job, before any work starts:

For a job this size, I split payment into three parts: [Amount 1] to get started and cover materials, [Amount 2] at the halfway point once [milestone — e.g., "rough-in is done"], and the final [Amount 3] when the job is complete and you've signed off. That way you're never fronting the whole cost, and I'm never doing the whole job on trust.

Here's the message that goes out the day you hit a milestone, so progress billing doesn't quietly turn into "I'll just invoice it all at the end":

Hi [Customer Name], quick update — we've hit [milestone], so this is the progress invoice for $[Amount] we talked about at the start. Here's the link: [Payment Link]. Next stage is [next milestone], and I'll check back in once we're there.

The point of all three of these: you're setting the payment schedule out loud, before the job starts, while the customer is in "yes, let's do this" mode — not introducing it as a surprise once you're already six weeks into a job and wondering when you'll see any of the money.

---

Lesson 2.4 — Collections texts that don't burn the relationship

Here's the fear underneath this whole course: if you chase the money too hard, you lose the customer — and worse, you lose every referral that customer would've sent you. So a lot of owners choose silence instead, and eat the invoice, because an awkward conversation feels more expensive than the money sitting on it.

It isn't. And you don't have to choose between getting paid and keeping the relationship. You just have to keep the target narrow: you're firm about the money, never about the person.

Rule one: never make it personal. "You never pay on time" is about them. "This invoice is 45 days past due" is about the invoice. Same information, completely different fight.

Rule two: always leave them a door. Every message below assumes there's a reasonable explanation and gives them a way to say so, instead of assuming bad faith on your side of the screen.

Rule three: keep dollar amounts and dates in every message. Vague messages ("hey just checking in on that thing") read as passive-aggressive. Specific messages read as business.

Here are three collections texts for situations that come up outside the regular 3/15/30/45 ladder:

When they've gone completely silent after multiple attempts:

Hi [Customer Name], I've sent a couple of reminders about invoice

[Invoice Number] for $[Amount] and haven't heard back. I'd rather talk this

through directly than keep sending texts — can you give me a call this week, or let me know a better way to reach you?

When they've asked for more time:

No problem, [Customer Name] — thanks for letting me know. Let's say [new date] for the $[Amount] balance on invoice #[Invoice Number]. I'll check back in around then.

When you need to be the most direct you'll ever be with this customer:

Hi [Customer Name], I need to close this out. Invoice #[Invoice Number] for $[Amount] is significantly past due and I haven't been able to reach you despite several attempts. Please call me by [date] to arrange payment — I want to resolve this with you directly before taking any further steps.

Notice none of these say anything about the person's character. All of them name the invoice, the amount, and a next step. That's what firm-without-hostile actually looks like in writing — and it's why sending these doesn't cost you the relationship the way you're afraid it will.

---

Lesson 2.5 — Week 2 challenge: chase every invoice past 30 days

You already have everything you need. You've got the 3/15/30/45 chase sequence from lesson 2.2. You've got the deposit and progress-billing scripts from 2.3 so this stops happening to future jobs. You've got the collections texts from 2.4 for the ones that go quiet.

Here's the challenge, and it's dated on purpose: this week, pull up every invoice in your books that's currently sitting past 30 days. Not "this month." Not "when I get a chance." This week.

For each one:

1. Check how many days past due it is.
2. Send the matching message from the chase sequence — day 30 or day 45, whichever fits.
3. Put a date on your calendar to send the next rung if you don't hear back.

That's it. You're not calling anyone. You're not having an awkward conversation. You're sending a message you already have written, to a person who already owes you the money, for work you already did.

The win you're looking for by the end of this week isn't a perfect bookkeeping system. It's one specific invoice — the one you've been avoiding — getting paid because a message went out that you didn't have to sit there and compose from scratch, wondering how to sound polite and firm at the same time.

Once that happens once, the whole thing stops being a confrontation you dread and starts being a habit you run. That's the shift this course is actually for.

Visuals

Course 2 — Cash Flow Recovery — Visuals

Every lesson ships at least one visual. Types match the taxonomy in .claude/rules/ralph-wiggum.md: stack / loop / step_diagram / comparison / matrix / stat / pull_quote / key_takeaway / statement / screenshot-mockup. Nothing below invents a stat or testimonial — every number and line of copy is pulled directly from script.md.

---

Lesson 2.1 — Why invoices go unpaid (follow-up gap, not the customer)

Visual 1 — comparison: "The story vs. what's actually true"

Two columns, side by side. - Left column, headed "The story you tell yourself": three lines, each struck through or greyed to signal "false" — "Maybe they're broke." / "Maybe they didn't like the work." / "Maybe they're the kind of person who stiffs contractors." - Right column, headed "What's actually true": one bolded line — "They meant to pay it. It landed next to four other bills and lost. Nothing happened after it." This is the lesson's opening reframe; it needs to land before anything else does.

Visual 2 — step_diagram: "How silence kills an invoice"

A 4-box horizontal chain with an arrow between each box: 1. Invoice sent 2. No reminder, no second touch 3. Silence reads as "not urgent" 4. Paid whenever → in practice, paid never (until someone asks again) Caption under the last box: "Not a customer problem. A follow-up gap."

Visual 3 — pull_quote

"Following up on an invoice is not rude. It's not awkward. It's not accusing anyone of anything. It's finishing the transaction the customer already agreed to when they said yes to the job." Pulled verbatim from the lesson's closing paragraph — the line that reframes collections as completion, not confrontation.

---

Lesson 2.2 — Friendly→firm chase sequence

Visual 4 — step_diagram: "The 3/15/30/45 ladder"

Four rungs, left to right, each rung visually turned up one notch (tone/color intensity increasing — e.g., calm blue → neutral → amber → red): 1. Day 3 — Reminder ("Assume the best") 2. Day 15 — Check-in ("Names the invoice number, asks directly") 3. Day 30 — Direct ("States amount, states how overdue, asks for a date") 4. Day 45 — Firm ("States what happens next, calmly") Small footer line under the diagram: "Never skip a rung. Stop the moment they respond." (ties directly to the lesson's two closing rules).

Visual 5 — screenshot-mockup: the chase sequence as a text thread

A phone-style text-message mockup showing all four messages from "Your 3/15/30/45- Day Chase Sequence" as sent texts in sequence (Day 3 reminder, Day 15 check-in, Day 30 direct, Day 45 firm), each bubble timestamped with its day label. This is the lesson's actual deliverable template — it should look like something the learner could screenshot and use, not an illustration.

Visual 6 — key_takeaway

Two-line callout box: - "Never skip a rung — jumping from Day 3 to Day 45 tone reads as unhinged." - "As soon as they respond, the sequence stops. Run it because you'd otherwise do nothing at all."

---

Lesson 2.3 — Deposit/progress-billing scripts

Visual 7 — comparison: "Deposit-only vs. progress billing"

Two columns: - Situation one — Deposit before starting: small job, one deposit (e.g. "$200 or 30%") to lock the date and cover materials, balance due on completion. - Situation two — Progress billing: bigger job, split into three payments tied to milestones, said out loud at the quoting stage, before work starts. Header line above both: "Say it before you schedule the job, not after."

Visual 8 — stack: the 3-part progress billing structure

Three stacked blocks, bottom to top or left to right: 1. Amount 1 — to get started, covers materials 2. Amount 2 — at the halfway point, tied to a named milestone (e.g. "rough-in is done") 3. Amount 3 — final payment, due on completion + sign-off Caption: "You're never fronting the whole cost. They're never doing the whole job on trust."

Visual 9 — screenshot-mockup: the milestone progress-invoice text

A single text-message mockup of the exact milestone-invoice line from the script: "Hi [Customer Name], quick update — we've hit [milestone], so this is the progress invoice for $[Amount] we talked about at the start. Here's the link: [Payment Link]. Next stage is [next milestone]..." — shown as a real sent text, reinforcing that progress billing is proactive, not a surprise invoice.

---

Lesson 2.4 — Collections texts that don't burn the relationship

Visual 10 — comparison: "About them vs. about the invoice"

Two short lines side by side, styled as a direct contrast (this is Rule One from the lesson, verbatim): - About the person (don't say this): "You never pay on time." - About the invoice (say this instead): "This invoice is 45 days past due." Caption: "Same information. Completely different fight."

Visual 11 — matrix: situation → collections text

A 3-row matrix mapping each of the three named situations to its purpose/tone:

Situation	What the message does
Gone silent after multiple attempts	Asks for a call instead of another text
Asked for more time	Confirms the new date, no friction
Needs the most direct message yet	States urgency, asks for a call by a date, before "further steps"

This mirrors the three scripted texts in the lesson without reprinting them in full inside the visual — the full text stays in script.md.

---

Lesson 2.5 — Week 2 challenge: chase every invoice past 30 days

Visual 12 — step_diagram: the 3-step challenge

1. Pull every invoice past 30 days in your books — this week, not "when I get a chance"
2. Send the matching message from the chase sequence (Day 30 or Day 45, whichever fits)
3. Put a date on your calendar to send the next rung if you don't hear back Footer: "You're not calling anyone. You're sending a message you already have written."

Visual 13 — statement

Large single-line statement, the lesson's closing reframe:

"Once that happens once, the whole thing stops being a confrontation you dread and starts being a habit you run."

---

Deliverable asset (course-level, closes the module)

Visual 14 — screenshot-mockup: the full chase-sequence cheat sheet

A single printable/saveable reference card — not a text thread this time, but a clean one-page layout — listing all four rungs (Day 3 / 15 / 30 / 45) with their full scripted copy and the two usage rules from Lesson 2.2 underneath. This is the actual "3/15/30/45-day chase sequence" deliverable named in the blackboard's Course 2 entry — the asset a learner saves and reuses on every invoice, distinct from the in-lesson text-thread mockup (Visual 5) which shows the sequence being used in context.

---

Count: 14 visuals across 5 lessons + 1 course-level deliverable asset.

Brief

Course 3 Brief — Reputation Engine

Dream outcome (value equation terms)

Dream Outcome: A steady stream of new 5-star reviews landing every week without the owner having to remember to ask, chase, or feel weird about it — so the business shows up stronger on Google than the guy who's actually better at the trade but never asks a single customer for a review.

Perceived Likelihood: High. This isn't "get better at the work" — the work is already good. It's one sentence, said at the right moment, using a script instead of winging it. The owner isn't being asked to become a marketer. They're being asked to say one line they already believe: "Hey, would you mind leaving us a review?"

Time Delay: Same day. The first review-ask can go out within the hour of finishing this course, on the very next job that closes out.

Effort: Low. No new software, no review-management platform, no design work — a text or email sent from the phone/inbox they already use, at the moment (48 hours post-job) when the customer is most likely to say yes.

Value equation, stated plainly: (A steady flow of 5-star reviews that out-ranks competitors × it's just one well-timed message) ÷ (same-day to start + five minutes per ask) = one of the highest-leverage, lowest-effort wins in the whole curriculum.

Who this is for

The owner who does great work and has happy customers — but has a handful of reviews on Google while a worse competitor down the road has hundreds. Not a reviews problem. An "I never actually asked" problem. This course is for the business that's been quietly losing jobs to a competitor with a fatter star count, not a better crew.

The fastest believable win

Send one review-request text to a customer from a job that closed in the last 48 hours, using the exact script from Lesson 3.3. Believable because it costs nothing, takes under two minutes, and the only "skill" required is copying and sending a sentence that's already been written for them.

Felt problem each lesson solves

• 3.1 Why nobody reviews unless asked — the felt problem: "I do good work, so why don't people just leave reviews on their own?" Answer: happy customers don't think about it unless prompted — the review isn't earned by the work, it's earned by the ask. This reframes the owner's quiet resentment ("nobody appreciates it") into an action they control.
• 3.2 The 48-hour ask window — the felt problem: asking feels like it has to be awkward, or the owner has tried once, gotten silence, and given up. This lesson fixes the timing mistake (asking too late, or not at all) that's the real reason past attempts fizzled.
• 3.3 Review-request scripts that don't sound needy — the felt problem: "I don't want to sound like I'm begging." This hands over exact wording so the owner never has to improvise a sentence that makes them cringe.
• 3.4 Turning a review into a referral — the felt problem: getting a review feels like the finish line, when it's actually a door to the next job. This lesson shows the one follow-up line that turns a 5-star review into a referral ask, so the same moment pays twice.
• 3.5 Week 3 challenge: 10 review requests — the felt problem: knowledge without a rep count doesn't change the business. This forces the habit into the calendar — 10 asks this week, using last week's actual closed jobs, so the system is proven on the owner's own customers, not hypothetical ones.

Connection to the course before and after

Before (Course 2 — Cash Flow Recovery): Course 2 fixed the leak where money the business already earned was walking out the door unpaid. Course 3 starts right where that ends — once an invoice is actually paid and the job is closed, that same moment is the highest-trust point in the whole customer relationship. Course 2 gets the money in the door; Course 3 gets the proof (the review) out the door while the customer is still glad they hired this business.

After (Course 4 — The Follow-Up System): Course 3 teaches the owner to ask for something small (a review) at the right moment and get a "yes." Course 4 takes that same follow-up muscle — the willingness to reach back out instead of assuming silence means no — and points it at bigger stakes: quotes that went quiet and customers who haven't called in six months. Reputation Engine proves the follow-up habit works on the easiest ask there is; The Follow-Up System scales that same habit to the harder ones.

Script

Course 3 — Reputation Engine

Word-for-word lesson script

How this course fits: Course 2 got the money in the door — every invoice chased down and paid. Course 3 picks up right there. The job's done, the invoice is paid, the customer is still glad they called you. That's the highest-trust five minutes you'll ever get with them. This course is about not wasting it.

---

Lesson 3.1 — Why nobody reviews unless asked

Here's the thing that's probably been bugging you for a while: you do good work. Your customers are happy. And you've still got a handful of reviews on Google while the outfit down the road — who you know for a fact isn't as good as you — has hundreds.

It feels unfair. It's not a reviews problem, though. It's an asking problem.

Think about the last time you had a great experience with a business. A mechanic who didn't upsell you. A restaurant that got everything right. Did you go home and leave them a review? Be honest. Most people don't. Not because the experience wasn't good enough — because leaving a review never crossed their mind. Life moved on. The dishwasher got fixed, the kids needed picking up, and by 8 PM that night the job you did is already three thoughts behind.

A happy customer isn't sitting there waiting to be asked. They're not sitting there at all. The review doesn't get left because it was earned by the work — it gets left because somebody asked at the right moment, with the right words, and made it take ten seconds.

That's the whole shift this course is asking you to make: stop treating reviews like something that happens to you, and start treating them like something you generate. Same work. Same happy customers. The only variable that changes is whether you ask.

One more thing, so this doesn't feel like extra work piled onto an already full day: you're not selling anything in this ask. You already did the selling — that was the job itself. All you're doing now is handing someone a very short, very easy way to say thank you. That's a different kind of conversation, and it should feel like one.

---

Lesson 3.2 — The 48-hour ask window

If you've tried asking for reviews before and it fizzled, it's probably not because your customers didn't like the work. It's because of when you asked — or that you never actually built asking into the job at all.

There's a window, and it's short. The best time to ask for a review is within 48 hours of the job closing out — the invoice is paid, the mess is cleaned up, and the relief of "that's handled" is still fresh. Ask inside that window and you're riding the high of a problem that just got solved. Ask a week later, or a month later when you finally remember, and you're asking someone to reconstruct a memory instead of react to a feeling. Way harder sell, and it's not even a sell — it's a favor at that point, and favors get put off.

Two ways this usually breaks, and both are timing mistakes, not likability mistakes:

1. Too late. You mean to ask, get busy, and by the time you think of it the job is old news. The ask never goes out at all.
2. Too awkward, too soon. You ask while you're still standing in their driveway packing up the truck, and it comes off like you're fishing for a tip. Right after the work is finished is actually the worst moment — the customer hasn't had time to enjoy the result yet. Give it a beat.

The fix is boring, on purpose: the ask happens 48 hours after the job closes, not whenever you remember. That means it needs a trigger, not a memory. The trigger is simple — when you mark an invoice paid or a job complete, that's the moment you set the 48-hour clock. A calendar reminder, a note on the job file, a recurring alarm on your phone at the end of each day to check "who closed out two days ago" — pick whichever one you'll actually use. The method doesn't matter. The window does.

Lock in the number: 48 hours. Not same-day, not "sometime this week." Say it back to yourself right now — 48 hours after close-out, every time. That's the habit this whole course is built on.

---

Lesson 3.3 — Review-request scripts that don't sound needy

This is the lesson that removes the only thing that's actually been stopping you: not knowing what to say.

Nobody wants to sound like they're begging. Nobody wants to send a text that reads like a guilt trip. So here's the good news — you don't have to write that message. It's already written. Copy it, drop in your details, send it. That's the whole job.

Three things make an ask land instead of landing awkward:

• It's short. One or two sentences, tops. A wall of text feels like a sales pitch. A short message feels like a person.
• It names the specific job, not "our service." Specific feels personal. Generic feels like a mail blast.
• It gives them one link, one click. Don't make them hunt for where to leave it.

Here are the actual messages. Use them exactly as written, or swap in your own business details where the brackets are.

Text message — the standard ask

Hey [First Name], it's [Your Name] from [Business Name]. Glad we got the [job type — e.g. "water heater"] sorted for you. If you've got 30 seconds, a Google review would really help us out: [Google review link]. Thanks again for having us out!

Text message — shorter version, for repeat customers

Hi [First Name], thanks again for having us back out for the [job type]. If you don't mind, a quick review here would mean a lot: [Google review link]

Email — the standard ask

Subject: Quick favor, [First Name]?

Hi [First Name],

Thanks for having us out to handle the [job type] at [address or "your place"] — glad it's sorted. If the work met your expectations, would you mind leaving us a quick review? It genuinely helps a small business like ours more than people realize.

Here's the link, it takes about 30 seconds: [Google review link]

Thanks again, [Your Name] [Business Name]

Email — for a job with no clean "before/after" (recurring service, maintenance visit)

Subject: How'd we do?

Hi [First Name],

Just wanted to check in after this week's [service type] visit — everything look good on your end? If so, we'd really appreciate a quick review here: [Google review link]. Takes less than a minute, and it helps us a lot.

Thanks, [Your Name] [Business Name]

If you don't have a review link handy yet

Go to your Google Business Profile, search "get more reviews," and Google will hand you a direct link built for exactly this. Save it in your phone's notes app right now, before you move to the next lesson — that link is what goes in every bracket above.

That's the deliverable for this lesson: four scripts, ready to copy-paste, the moment a job crosses the 48-hour mark.

---

Lesson 3.4 — Turning a review into a referral

Most owners treat a 5-star review as the finish line. It's not. It's a door, and it's open for about as long as that review notification is sitting on your phone.

Think about what just happened: someone liked your work enough to publicly say so. That's not a small thing — a review is somebody putting their name behind a recommendation of you. The same person who just did that is exactly the kind of person who knows other people who need what you do. Neighbors. Family. Coworkers who've complained about their own [trade] guy at some point. You've got a warm opening to ask for an introduction, and almost nobody uses it.

The move is simple: the moment you see a new review come in, reply to it — publicly if the platform allows it, or with a quick personal text if not — and tack on one line. Not a sales pitch. Just a door left open.

The referral line (reply to the review, or a follow-up text)

Thank you so much for the kind words, [First Name] — really appreciate you taking the time. If you ever know anyone who needs [service], we'd love the introduction. Referrals are the best compliment we get.

If you'd rather send it as a separate text a day or two after the review posts

Hey [First Name], saw your review — thank you, that means a lot. Small favor if it ever comes up: if you know anyone who needs [service], send them our way. Best compliment we get is a customer sending a friend.

Notice what this line does NOT do: it doesn't ask for a discount code to hand out, it doesn't turn into a formal referral program with tiers and tracking. It's one warm sentence that costs you nothing and plants the idea while the goodwill is still warm. Some people will act on it that week. Some won't act on it for months, until a friend happens to mention needing exactly what you do — and now you're the name that comes to mind, because you're the one who asked.

Same five minutes that got you the review just bought you a shot at the next job, too.

---

Lesson 3.5 — Week 3 challenge: 10 review requests

Reading the scripts doesn't change your review count. Sending them does. This week, the job is simple: send 10 review requests using the scripts from Lesson 3.3, to real customers from jobs you've actually closed in the last two weeks.

Not hypothetical customers. Not "the next ten that come in." Pull your job list right now, find the ten most recent closed-and-paid jobs, and send the ask today — even if some of them are past the 48-hour window already. Late is still better than never. Going forward, every new job that closes gets the ask at the 48-hour mark, starting now.

Use this log to run the challenge. Fill in a row every time you send one — it takes ten seconds and it's the only way you'll actually know if you hit ten.

Week 3 challenge tracker

#	Customer name	Job / service	Date job closed	Date ask sent	Channel (text/email)	Response (yes / no / no reply yet)
1
2
3
4
5
6
7
8
9
10

Three rules for the week:

1. Every ask uses a script from Lesson 3.3, word for word. This isn't the week to freelance your own version — you're testing whether the system works, not whether you can write a better text than the one already handed to you.
2. Every review that comes in gets the referral line from Lesson 3.4, same day it posts. Don't let the reply sit.
3. Log it as you go, not at the end of the week. If you wait until Friday to fill in the tracker, you'll have already forgotten which jobs you asked.

By the end of this week you'll have a real, current answer to a question most owners can only guess at: out of ten happy customers asked directly, how many will actually leave a review? Whatever that number is, it's higher than the number you get from doing nothing — which, until this week, was the plan.

Where to show up: drop your tracker results in the community when the week's done. Ten asks sent isn't a brag — it's proof the system runs on your own customers, not just the idea of it.

Visuals

Course 3 — Reputation Engine — Visual Assets

Every visual below is grounded in the actual script (script.md). One set per lesson, plus one course-opener. Types used: stack, loop, step_diagram, comparison, stat, pull_quote, key_takeaway, statement, screenshot-mockup.

---

Course opener — "How this course fits"

1. loop — The trust handoff, Course 2 → 3 → 4 Three-node loop/flow: "Invoice paid (Course 2)" → "Highest-trust 5 minutes (Course 3: ask for the review)" → "Warm relationship to reactivate later (Course 4)." Caption pulls the script's own framing: "That's the highest-trust five minutes you'll ever get with them. This course is about not wasting it." Purpose: orient the learner on why reviews sit here in the sequence, not just "review tips."

---

Lesson 3.1 — Why nobody reviews unless asked

2. comparison — a handful vs. hundreds Two-sided visual, side by side: "You: a handful of Google reviews" vs. "The outfit down the road (who isn't as good): hundreds of reviews." Deliberately unspecific — this is a relatable pattern, not a real stat about the viewer, so don't attach exact numbers to it. Small sub-line under each side: "Same quality of work isn't the variable."

3. statement — The reframe Large single-line statement card: "It's not a reviews problem. It's an asking problem." This is the pivot sentence of the whole lesson — give it its own full-bleed card, not buried in a paragraph.

4. loop — Why the happy customer never leaves the review Four-step loop showing the memory decaying across a single day: "Job finishes, customer is happy" → "Life moves on (dishwasher's fixed, kids need picking up)" → "By 8 PM, the job is three thoughts behind" → "Review never crosses their mind." This visualizes the script's specific timeline ("by 8 PM that night the job you did is already three thoughts behind") rather than a vague "people forget" claim.

5. key_takeaway — The only variable Key-takeaway card: "Same work. Same happy customers. The only variable that changes is whether you ask." Paired sub-point: "You're not selling — you already did that. You're handing someone a 10-second way to say thank you."

---

Lesson 3.2 — The 48-hour ask window

6. stat — 48 Big-number stat treatment: "48 hours" as the hero numeral, sub-label: "The best time to ask for a review — while the relief of 'that's handled' is still fresh." This is the single number the entire lesson pivots on; it should be the most visually dominant asset in the course.

7. step_diagram — The ask timeline Horizontal timeline from job close-out to day 7+, with two marked "danger zones" and one "sweet spot": "Job closes (too soon — looks like fishing for a tip)" → "48 hrs later (sweet spot — ask here)" → "1 week+ later (too late — they're reconstructing a memory, not reacting to a feeling)." Directly visualizes the script's two named failure modes (too soon / too late) around the correct window.

8. comparison — Two ways this breaks Two-column comparison, both labeled as timing mistakes, not likability mistakes: "Too late" (you get busy, job goes cold, ask never goes out) vs. "Too awkward, too soon" (asking mid-driveway while packing up the truck, before they've had time to enjoy the result). Header line: "Both timing mistakes. Neither is about your work."

9. key_takeaway — Trigger, not memory Key-takeaway card: "The ask happens 48 hours after the job closes, not whenever you remember. That means it needs a trigger, not a memory." Sub-line lists the three trigger options named in-script: calendar reminder / note on the job file / end-of-day phone alarm to check "who closed out two days ago."

---

Lesson 3.3 — Review-request scripts that don't sound needy

10. stack — Three things that make an ask land Three-item stack, each with a one-line explainer pulled straight from the script: "Short" (one or two sentences — a wall of text feels like a sales pitch) / "Specific" (names the job, e.g. "water heater" — not "our service") / "One link, one click" (don't make them hunt for where to leave it).

11. screenshot-mockup — Text message ask Phone-frame text-bubble mockup showing the standard text script rendered as an actual sent message: "Hey [First Name], it's [Your Name] from [Business Name]. Glad we got the [job type] sorted for you. If you've got 30 seconds, a Google review would really help us out: [Google review link]. Thanks again for having us out!" Shows learners exactly what this looks like landing in a real thread, not just as body copy on a page.

12. screenshot-mockup — Email ask Email-client-frame mockup of the standard email script, subject line visible: "Quick favor, [First Name]?" with the body text from the script rendered in the mockup. Pair it directly against visual 11 so learners see text vs. email side by side as two ready formats, not one preferred channel.

13. step_diagram — Getting your review link (if you don't have one) Three-step micro-diagram for the lesson's closing instruction: "Open Google Business Profile" → "Search 'get more reviews'" → "Save the link Google hands you, in your phone's notes app, right now." This is the one piece of software-adjacent instruction in the lesson and deserves its own quick visual so it isn't skipped.

---

Lesson 3.4 — Turning a review into a referral

14. statement — The reframe Full-bleed statement card: "Most owners treat a 5-star review as the finish line. It's not. It's a door — and it's only open as long as that notification is sitting on your phone."

15. pull_quote — The referral line Pull-quote treatment of the exact reply-to-review script: "Thank you so much for the kind words, [First Name] — really appreciate you taking the time. If you ever know anyone who needs [service], we'd love the introduction. Referrals are the best compliment we get." This is the one line the whole lesson is built to deliver — give it the same weight as the 48-hour stat in 3.2.

16. comparison — What this is / isn't Two-column contrast, direct from the script's own distinction: "NOT this" (a discount code to hand out, a formal referral program with tiers and tracking) vs. "IS this" (one warm sentence, costs nothing, said while the goodwill is still warm). Prevents learners from over-building what's meant to stay simple.

17. loop — Review → referral → next job Three-node loop closing the lesson: "New review posts" → "Reply same-day with the referral line" → "Warm intro (this week or months from now) → next job." Caption: "Same five minutes that got you the review just bought you a shot at the next job, too."

---

Lesson 3.5 — Week 3 challenge: 10 review requests

18. step_diagram — This week's challenge, in order Four-step diagram matching the script's exact instructions: "Pull your job list" → "Find the 10 most recent closed-and-paid jobs" → "Send the ask today (even if some are past 48 hrs — late beats never)" → "Log every send as you go, not at week's end."

19. screenshot-mockup — The tracker table Rendered mockup of the Week 3 challenge tracker exactly as it appears in the script: 10 numbered rows, columns # / Customer name / Job / Date job closed / Date ask sent / Channel / Response. Shown as a filled-in example row (fictional placeholder data, not a real customer) so learners see how to use it before their own copy is blank.

20. stack — Three rules for the week Three-item stack, numbered as in the script: "1. Every ask uses a script from 3.3, word for word" / "2. Every review that comes in gets the referral line from 3.4, same day" / "3. Log it as you go, not at the end of the week."

21. key_takeaway — The real number Key-takeaway / stat hybrid closing the course: "Out of ten happy customers asked directly, how many will actually leave a review? Whatever that number is, it's higher than the number you get from doing nothing — which, until this week, was the plan." Pairs with the "Where to show up" line — drop tracker results in the community when the week's done.

Brief

Course 4 — The Follow-Up System

Dream outcome (Hormozi value equation)

Dream Outcome: Money that's already sitting in your pipeline — quotes you sent and never heard back on, customers who used you once and vanished — turns back into booked jobs, without you having to sell anything. You stop losing work you already did the hard part on (the estimate, the first job, the trust) just because nobody followed up.

Perceived Likelihood: High, on purpose. This isn't "get better at sales." It's "send the message you were already going to send, on a day you actually remember to send it." The scripts are pre-written. The system is a list, not software. If a customer already said yes to you once, or already asked for a quote once, the hard part is done — this course just makes sure the ball doesn't get dropped a second time.

Time Delay: Same week. Lesson 4.2's 3-touch sequence can go out on a quote that's sitting cold right now. The Week 4 challenge (5 reactivated customers) is designed to close inside 7 days, not "someday."

Effort: Near zero new effort — this is recovering effort you already spent. No new skill, no new software, no new hires. A follow-up list on paper or in a phone notes app, three pre-written messages, and 10 minutes twice a week to send them.

Value equation, stated plainly: (Money already earned but not collected × "I could send a text today") ÷ (This week + 10 minutes twice a week) — the highest-leverage course in the curriculum because every dollar it recovers required zero new sales effort. It's not new customers. It's customers who were already yours.

Who this course is for

The owner who has never once followed up on a quote after sending it, or who follows up "when I think of it" — which means never. Someone with a phone full of past customers who did one job with them 8 months ago and haven't heard from since, not because the customer was unhappy, but because nobody asked them to come back. This is not the owner who needs to learn how to sell. It's the owner who needs a system so that following up isn't a thing they have to remember to feel like doing.

The fastest believable win

By the end of Lesson 4.2, the owner has sent a 3-message sequence to one cold quote sitting in their phone right now — and gotten a reply. The believability comes from the frame: this isn't a cold pitch, it's a nudge to someone who already asked for a price. "Just checking if you still need this done" reopens more doors than any new lead-gen tactic, because the prospect already raised their hand once.

The felt problem each lesson solves

• 4.1 — The quote you never heard back on: "I sent the price, they went quiet, and I told myself they went with someone else." The felt problem is the story owners tell themselves to avoid following up — assuming silence means no, when it usually means "I got busy and forgot," same as the owner did.
• 4.2 — 3-touch sequence (day 1/4/10): "I don't know what to say without sounding desperate, so I say nothing." The felt problem is the fear of looking needy — solved by a pre-written sequence that gets progressively lower-pressure, not higher.
• 4.3 — Reactivating 6-month-lapsed customers: "That customer probably found someone else by now, no point reaching out." The felt problem is writing off past customers as gone, when most people don't switch service providers — they just never get asked to come back.
• 4.4 — A no-software follow-up list: "I'd follow up if I had some kind of system, but I'm not buying software for this." The felt problem is treating "no CRM" as a dead end instead of building the simplest version — a list — that still works.
• 4.5 — Week 4 challenge: reactivate 5 lapsed customers: "I know the scripts now, but will I actually use them?" The felt problem is the gap between knowing and doing — closed by a small, countable, this-week target.

How this connects to the course before and after it

Before — Course 3, Reputation Engine: Course 3 taught the owner to ask happy customers for a review in the 48 hours right after the job. Course 4 is the same instinct — proactive, timed outreach instead of hoping the customer initiates — pointed at a different moment: not "ask right after," but "ask again after they've gone quiet." Reviews and follow-ups are both about the owner making the ask instead of waiting for the customer to.

After — Course 5, Your AI Back Office: Course 4 builds the follow-up list and the 3-touch sequence by hand — paper, phone notes, manual sends. Course 5 takes that exact system and automates the trigger for it: the "brain" doc in 5.2 is where the follow-up list actually lives long-term, and the "missed call → auto-text" recipe in 5.3 is the same reactivation instinct from Course 4, just running itself instead of waiting for the owner to remember Tuesday is follow-up day. Course 4 proves the system works by hand; Course 5 proves it works without you.

Script

Course 4 — The Follow-Up System

Word-for-word lesson scripts. Read straight into camera/voiceover, or lift lines directly for slides. Voice: plain, warm, direct — you're the owner who has the office handled talking to another owner who doesn't yet.

---

4.1 — The quote you never heard back on

Somewhere in your phone right now is a quote you sent that just... stopped.

You gave the price. You said "let me know." And then nothing. No text back, no call, no "we went with someone else" — just silence.

Here's what you told yourself about that silence: they found someone cheaper. They went with a buddy. They never really needed it done in the first place. Something that lets you stop thinking about it.

Here's what actually happened, most of the time: they got busy. The quote sat in a text thread under three other texts. Life happened, and following up became their job, not yours — except you never told them that. You just waited.

Silence doesn't mean no. Silence means you haven't asked again.

Think about how you behave as a customer. You've gotten quotes for things — a fence, a roof, a new water heater — and meant to follow up, and didn't, and then six weeks later you're still living with the broken thing because nobody nudged you. Not because you didn't want it fixed. Because it fell out of your head and nobody put it back in.

Your customers are doing the same thing to you. Every quote that went quiet is not a lost sale. It's an unfinished conversation. And the person who has to finish it is whoever remembers to speak next — which, until now, has never been you.

That's what this course fixes. Not your pitch. Not your pricing. Just the part where you go quiet right along with them, and both of you let a job that was already 90% decided just evaporate.

By the end of this course, you'll have three things: - A 3-touch sequence you send on autopilot when a quote goes cold. - A script for reaching customers you haven't heard from in 6 months. - A follow-up list you can run with nothing but a phone and 10 minutes, twice a week.

None of it requires you to get better at selling. It requires you to be the one who speaks first. That's the whole system.

---

4.2 — 3-touch sequence (day 1/4/10)

Here's the fear, said out loud: if you follow up, you'll sound desperate. Like you need the job. Like you're chasing them.

You're not chasing them. You quoted a job. They asked for a price, which means at some point they wanted it done. You're not selling — you're checking a box that's still open. That's a completely different energy, and the sequence below is built to sound like it, not like a salesman circling back.

Three touches. Each one lower-pressure than the last, not higher. The order matters — you start light and helpful, and you end giving them a clean, guilt-free way to say not right now.

Day 1 — the day after you send the quote (or the day it's clear they've gone quiet):

Text: "Hey [Name], following up on the quote I sent for [job] — any questions on it before you decide? Happy to walk through anything."

That's it. No pressure, no "are you still interested." You're offering help, not asking for a yes. This is the version of follow-up that feels normal because it is normal — it's what you'd want if you were the one who'd just gotten a quote for something you didn't fully understand.

Day 4 — three days later, if no reply:

Text: "Hey [Name], just checking in — still working through your decision on [job], or did the timing change on your end? No worries either way, just want to make sure I'm not sitting on your calendar spot if you need to move on it."

This one does two things. It gives them an easy out ("timing change" — always true, never awkward), and it plants urgency without saying "act now" — the calendar-spot line does that work for you, honestly, because it's usually true. You do have limited slots.

Day 10 — the last touch, and the lowest pressure of all:

Text: "Hey [Name], I'll close this quote out on my end for now so I'm not cluttering your inbox — but the offer stands whenever you're ready. Just reply and I'll get you back on the schedule."

Read that again. You're not asking anymore. You're telling them you're stepping back — which is the single most disarming thing you can do to someone who's been avoiding your texts out of guilt for not replying sooner. This message gets replies precisely because it asks for nothing.

Do this today: open your phone right now, find one quote that's gone quiet, and send the Day 1 text. Not tomorrow. Right now, before you finish this lesson. That's your fastest believable win in this whole course — one text, sent today, to a real quote sitting in your phone.

---

4.3 — Reactivating 6-month-lapsed customers

Different silence, same mistake.

This isn't a quote that never closed — this is a customer who already paid you once. They hired you, you did the work, they were happy enough not to complain, and then... nothing. No repeat call. No referral. Just gone, as far as you know.

Here's the story you tell yourself about that one: they found someone else. They moved. They didn't need the service again. Maybe. But ask yourself something more useful: did you ever actually ask them to come back?

Most people don't switch service providers because they're mad at you. They switch — or more accurately, they just don't come back — because nobody reminded them you exist when the next need came up. Your customer isn't loyal to whoever's cheapest. They're loyal to whoever's top of mind when the pipe leaks again, and if you went quiet for 6 months, you're not top of mind. You're a name in an old text thread.

This is the easiest sale you'll ever make, because it's not a sale. It's a tap on the shoulder from someone they already trust.

The reactivation script:

Text: "Hey [Name], it's [Your Name] from [Business] — did the [job you did, e.g. water heater / gutters / AC unit] we took care of back in [month] hold up okay? Was thinking of you and wanted to check in. Let me know if you ever need anything else."

Notice what's missing: no pitch, no "we have a special this month," no ask at all. This is a check-in, not a sales call, and that's exactly why it works. You're not asking for money. You're reminding a real person that a real human being who did good work for them once is still around, still thinking of them, still available.

Half the replies you get to this text will be some version of "actually, funny you should ask..." Because most people, when reminded you exist, will tell you about the thing they've been meaning to call someone about. You just have to be the name in front of them when they think of it.

Pull your last 6 months of completed jobs. Anyone you haven't heard from since — that's your list for this script.

---

4.4 — A no-software follow-up list

You don't need a CRM. You don't need an app. You need a list, and the reason most owners never build one isn't that lists don't work — it's that "build a follow-up system" sounds like a project, so it never starts.

Here's the version that actually gets used, because it takes 15 minutes to set up and zero training to run.

Option A — Notes app on your phone.

Make one note called "Follow-Up List." Every time you send a quote, add one line:

[Customer name] — [job] — quoted [date] — next touch [date]

When you check the note (twice a week — Tuesday and Friday mornings, pick two days and keep them), you scan for anything whose "next touch" date is today or past. Send the matching message from Lesson 4.2 or 4.3. Update the date. Move on. That's the entire system.

Option B — A physical notepad by the phone or in the truck.

Same four columns, written by hand: name, job, quoted date, next touch. If you're the kind of owner who never opens apps but always has a pen in the truck, this version works exactly as well. The tool doesn't matter. The habit does.

Option C — A simple spreadsheet, if you already live in one for invoicing.

Same four columns as a row. Nothing fancier than what you already have open for billing.

Whichever version you pick, the rule that makes it work is this: you only add two minutes to a job you were already doing. You already sent the quote. Writing one line in a note takes ten seconds. You already do the follow-up call in your head — this just makes sure it happens on your phone instead of in a thought you forget by lunch.

Pick one option right now. Don't research the "best" app. The list that exists beats the perfect system that's still a someday project.

---

4.5 — Week 4 challenge: reactivate 5 lapsed customers

You have three scripts and a list. The only thing left is doing it, and doing it is where most owners fall off — not because the scripts don't work, but because knowing and doing are two different things, and nothing closes that gap except a small, countable target with a deadline.

Here's the challenge: Reactivate 5 lapsed customers this week.

That's it. Five people. Here's exactly how:

1. Today: Build your follow-up list (Lesson 4.4) — notes app, notepad, or spreadsheet, whichever you picked. Takes 15 minutes.
2. Today: Pull 5 names — either quotes that went cold (Lesson 4.2) or customers you haven't heard from in 6+ months (Lesson 4.3). Write them on the list.
3. Today, before you close this lesson: Send the first-touch message to all 5. Copy-paste the scripts above. Swap in names and jobs. That's it — you don't need to write anything new.
4. This week, twice: Check the list on your two chosen follow-up days. Send the next touch to anyone who hasn't replied yet.
5. By day 10: Every one of the 5 has gotten all three touches, or has already replied and booked.

Five is the number for a reason — small enough that "I don't have time" doesn't hold up, big enough that at least one of them replies. And when one does — and one will — you'll have your proof that the silence was never a no. It was just a conversation nobody finished.

Deliverable: Follow-up + win-back scripts (copy-paste ready)

Cold quote — Day 1:

"Hey [Name], following up on the quote I sent for [job] — any questions on it before you decide? Happy to walk through anything."

Cold quote — Day 4:

"Hey [Name], just checking in — still working through your decision on [job], or did the timing change on your end? No worries either way, just want to make sure I'm not sitting on your calendar spot if you need to move on it."

Cold quote — Day 10:

"Hey [Name], I'll close this quote out on my end for now so I'm not cluttering your inbox — but the offer stands whenever you're ready. Just reply and I'll get you back on the schedule."

6-month-lapsed customer — reactivation:

"Hey [Name], it's [Your Name] from [Business] — did the [job] we took care of back in [month] hold up okay? Was thinking of you and wanted to check in. Let me know if you ever need anything else."

Follow-up list template (notes app, notepad, or spreadsheet — 4 columns):

Customer name	Job	Quoted / last-job date	Next touch date

Run it on two fixed days a week. Anything due today or overdue gets the next message in the sequence. Update the date. Close the note. That's the whole system.

Visuals

Course 4 — The Follow-Up System — Visuals

Every visual below is grounded in specific lines/moments from script.md. One producer picks up this file and knows exactly what to build — no generic stock-photo filler, no restating the lesson title as a "visual."

---

4.1 — The quote you never heard back on

Visual 1 — comparison: "What you tell yourself" vs. "What actually happened"

Two-column comparison, straight from the script's own framing: - Left column ("The story you tell yourself"): "They found someone cheaper." / "They went with a buddy." / "They never really needed it done." - Right column ("What actually happened, most of the time"): "They got busy." / "The quote sat in a text thread under three other texts." / "Following up became their job, not yours — except you never told them that." Visual should make the right column read as the calmer, more human explanation — this is the reframe the whole course rests on.

Visual 2 — pull_quote: "Silence doesn't mean no."

Pull the exact line: "Silence doesn't mean no. Silence means you haven't asked again." This is the single sentence the entire course is built on — treat it as the course's thesis statement, not just a lesson callout.

Visual 3 — stack: What you'll have by the end of this course

Three-card stack, pulled verbatim from the script's closing list: 1. A 3-touch sequence you send on autopilot when a quote goes cold. 2. A script for reaching customers you haven't heard from in 6 months. 3. A follow-up list you can run with nothing but a phone and 10 minutes, twice a week. Caption under the stack: "None of it requires you to get better at selling."

---

4.2 — 3-touch sequence (day 1/4/10)

Visual 4 — step_diagram: The 3-touch sequence, day by day

Three steps left to right, each labeled with the day AND the one-line job that touch is doing (not just "message 3" — the actual function): 1. Day 1 — Offer help, not a yes/no. "Any questions on it before you decide?" 2. Day 4 — Give them an easy out + plant urgency. "Did the timing change on your end?" + the calendar-spot line. 3. Day 10 — Step back, ask for nothing. "I'll close this quote out on my end for now... the offer stands whenever you're ready." Arrow annotation across the sequence: pressure goes DOWN each touch, not up — this inversion is the entire mechanic of why the sequence works and should be visually obvious (e.g., a descending intensity bar under the 3 steps).

Visual 5 — screenshot-mockup: The 3-touch sequence as a real text thread

Phone-frame mockup showing a single text conversation with the three actual messages from the script stacked as sent bubbles (Day 1, Day 4, Day 10, each timestamped days apart). Use the exact copy from the script verbatim in the bubbles. This is the "what this actually looks like on your phone" visual — makes the system feel real and copy-pasteable, not theoretical.

Visual 6 — key_takeaway: Do this before you finish the lesson

Callout box: "Open your phone right now, find one quote that's gone quiet, and send the Day 1 text. Not tomorrow. Right now." Frame this as the lesson's "fastest believable win," matching the blackboard's Hormozi value-equation language — this is the Day-4-of-course quick win.

---

4.3 — Reactivating 6-month-lapsed customers

Visual 7 — comparison: Quote-gone-cold vs. lapsed-customer silence

Two-row comparison clarifying the distinction the lesson opens with: - Row 1 — Cold quote (Lesson 4.2): Never became a customer. Silence = an unfinished conversation. - Row 2 — Lapsed customer (this lesson): Already paid you once, was happy enough not to complain, just never came back. Silence = you went quiet, not them. This visual exists to stop learners from running the wrong script on the wrong list — it's a "different silence, same mistake, different fix" distinction made explicit in the script's opening line.

Visual 8 — pull_quote: Loyal to whoever's top of mind

Pull the exact line: "Your customer isn't loyal to whoever's cheapest. They're loyal to whoever's top of mind when the pipe leaks again." This is the reframe that makes the reactivation ask feel non-desperate.

Visual 9 — screenshot-mockup: The reactivation text, sent

Phone-frame mockup of the single reactivation message from the script, with the bracketed fields filled in with a plausible example (e.g., "Hey Mike, it's Dave from Dave's Heating — did the water heater we took care of back in January hold up okay?"). Shows a business owner what a filled-in, real version looks like, not just a bracket template.

Visual 10 — statement: "This is the easiest sale you'll ever make"

Full-bleed statement card with the script's own line: "It's not a sale. It's a tap on the shoulder from someone they already trust." Sets up the "half the replies will be 'funny you should ask...'" payoff later in the lesson.

---

4.4 — A no-software follow-up list

Visual 11 — matrix: The 3 tool options, same 4 columns

3-row matrix comparing Option A (Notes app), Option B (Physical notepad), Option C (Spreadsheet) against the same 4 fields every version uses: Customer name / Job / Quoted date / Next touch date. Right-hand note column per row should carry the script's own qualifier for who each option fits (e.g., Option B: "for the owner who never opens apps but always has a pen in the truck"). This reinforces the script's core point — the columns are identical, only the medium changes, so there's no "best" option to research.

Visual 12 — screenshot-mockup: The Notes app entry, filled in

Phone Notes-app mockup showing one real filled-in line exactly as the script formats it: "Mike Torres — water heater — quoted 6/2 — next touch 6/6." This is the "here's literally what you type" visual, removing any ambiguity about format.

Visual 13 — key_takeaway: The two-minute rule

Callout: "You only add two minutes to a job you were already doing." Directly under it, the script's closing instruction as a CTA: "Pick one option right now. Don't research the 'best' app."

---

4.5 — Week 4 challenge: reactivate 5 lapsed customers

Visual 14 — step_diagram: The 5-step challenge, in order

Five-step horizontal flow using the script's own numbered list, each step labeled with its timing: 1. Today — Build your follow-up list (15 minutes). 2. Today — Pull 5 names (cold quotes or 6-month-lapsed customers). 3. Today, before closing this lesson — Send the first-touch message to all 5. 4. This week, twice — Check the list on your two chosen follow-up days. 5. By day 10 — All 5 have had all 3 touches, or already replied and booked. This should visually read as a checklist/timeline a learner can literally follow along and tick off — it's the operational spine of the whole course's Week 4 challenge.

Visual 15 — stat: The number 5

Large-numeral stat treatment on "5" with the script's own justification underneath as supporting copy: "Small enough that 'I don't have time' doesn't hold up. Big enough that at least one of them replies." Keep this to the exact framing from the script — no invented completion-rate stats (QA gate: no fabricated numbers).

Visual 16 — pull_quote: It was never a no

Closing pull-quote for the course: "The silence was never a no. It was just a conversation nobody finished." Use as the final-frame visual for this lesson — it's the callback that closes the loop opened in 4.1's thesis line.

---

Deliverable — Follow-up + win-back scripts (copy-paste ready)

Visual 17 — stack: The 4 scripts, card by card

Four-card stack, one card per script, each card showing the exact script label and full copy verbatim from the deliverable section: 1. Cold quote — Day 1 2. Cold quote — Day 4 3. Cold quote — Day 10 4. 6-month-lapsed customer — reactivation This is the "grab and go" reference card set a learner screenshots and keeps — should be visually distinct from the in-lesson phone mockups (this is the clean copy-paste reference version, not a simulated text thread).

Visual 18 — screenshot-mockup: The follow-up list template, blank and filled

Split visual: left half shows the blank 4-column table from the deliverable (Customer name / Job / Quoted or last-job date / Next touch date) as it would look printed or in a notes app; right half shows the same table with 2-3 example rows filled in (reusing the Mike Torres example from Visual 12 for consistency). Caption: "Run it on two fixed days a week."

---

Total: 18 visuals across 5 lessons + 1 deliverable.

Brief

Course 5 — Your AI Back Office — Brief

Dream outcome (Hormozi value equation)

Value = (Dream Outcome × Perceived Likelihood) ÷ (Time Delay + Effort)

• Dream Outcome: Every call, quote, and note about the business lives in ONE place you can search in ten seconds — and the one follow-up you always forget to send (the text after a missed call) now goes out by itself. Not "AI runs your business." Just: nothing falls out of your head, and one leak is already plugged before you open your phone.
• Perceived Likelihood: High, on purpose. This is the course that proves the "AI office" isn't a $10k software project — it's a Google Doc and a free Zapier account, set up in one sitting, using tools they can picture (a doc, a form, the phone they already have). No new platform to learn, no vendor pitch, no code.
• Time Delay: One sitting, same week. The brain doc gets built in one lesson (5.2). The one automation gets built in one lesson (5.3). By the Week 5 challenge they're not learning a concept — they're finishing a two-part setup they started days earlier.
• Effort: Deliberately low. One doc. One automation. Not a system overhaul. The brief for every lesson is "the smallest version of this that actually works," not the most impressive version.

Who this is for

The owner who has now fixed the four operational leaks (missed calls, unpaid invoices, no reviews, no follow-up) and is starting to feel a new, quieter problem: they're the only one who remembers anything. The customer's name, what was quoted, what was promised, who still owes a callback — it's all in their head, a notes app, three text threads, and a stack of Post-its on the dash. They've heard the word "AI" enough times to be either annoyed or curious, and they don't know what it actually does for a business their size. This course is for the owner who's ready to try ONE small automated thing without buying a whole new system to do it.

The fastest believable win

By the end of lesson 5.3, they have exactly one automation running: a missed call on their business line triggers an auto-text to the caller within a minute, built on tools they already have or can get free (their existing phone/CRM + a free Zapier or Make account). That's the whole win — one leak, plugged automatically, without hiring anyone or buying software. Lesson 5.2's brain doc is the second half of the win: a single Google Doc or Notion page, built in one sitting, that becomes the one place every call/quote/note gets logged from now on. Neither deliverable requires a subscription, a developer, or more than an hour of setup.

Felt problem each lesson solves

• 5.1 — What "AI office" actually means for a one-truck business (grounding, no hype): The felt problem is confusion and skepticism — every ad promises "AI will run your business" and none of them say what that means for someone with a truck, a phone, and no IT department. This lesson resets expectations before touching a single tool: no hype, no jargon, just what an "AI office" is actually FOR at this size (one brain, one automation) so the rest of the course lands as useful instead of gimmicky.
• 5.2 — Build your brain — one place every call, quote, and note lands: The felt problem is the mental tax of being the only file cabinet in the business — forgetting what was quoted, re-asking a customer something they already told you, losing a note scribbled on the back of an invoice. This lesson builds the single searchable doc that ends that, using a tool they already have (Google Docs or Notion), not new software.
• 5.3 — Your first agent — one automated follow-up recipe (missed call → auto-text): The felt problem is the missed call that never gets a follow-up because by the time they're off the ladder or out from under the truck, they've forgotten it happened. This lesson builds the one automation that catches it without them lifting a finger, using off-the-shelf tools (Zapier/Make + whatever phone system they already run).
• 5.4 — Where AI note-taking/summarizing actually saves time vs. where it's a toy: The felt problem is wasted time trying five different AI apps and not knowing which ones are actually worth the ten minutes it takes to learn them. This lesson draws the line plainly: which AI note/summary tools save real time on real tasks (call recaps, quote notes) and which ones are a novelty that adds a new step instead of removing one.
• 5.5 — Week 5 challenge: set up your brain doc + one starter automation: The felt problem is that "I'll set that up eventually" never happens without a deadline. This lesson turns the two builds from 5.2 and 5.3 into one week's homework with a clear finish line, so the brain doc and the automation are live, not just planned.

How this connects to the course before and after it

• Before (Course 4 — The Follow-Up System): Course 4 taught manual follow-up — the 3-touch sequence, the no-software follow-up list, reactivating lapsed customers by hand. Course 5 picks up exactly where that leaves off: once they've proven follow-up matters enough to do by hand, this course shows them the smallest way to make one piece of it automatic (missed-call auto-text) and gives the follow-up list itself a permanent home (the brain doc), instead of living on paper or in their head.
• After (Course 6 — Scale Without Hiring): Course 6 is the bridge/graduation course — real cost of the next hire, what to hand off first, DIY vs. done-for-you, and the exit-ramp decision. Course 5's honest, un-hyped tone about what DIY automation can and can't do (5.1 and 5.4 both draw that line on purpose) sets up Course 6's central question fairly: you've now felt what a DIY AI setup takes to build and maintain — so when Course 6 asks "hire, DIY, or done-for-you," you're answering from experience, not a sales pitch.

Script

Course 5 — Your AI Back Office — Script

Word-for-word lesson script. Read this as the actual talking-head/voiceover copy — say it close to as written, don't paraphrase the templates.

---

5.1 — What "AI office" actually means for a one-truck business (grounding, no hype)

You've heard the word "AI" about four hundred times in the last year. Half the ads say it'll run your whole business by itself. The other half say it's coming for your job. Neither one is talking to you — a guy or gal with a truck, a phone, and maybe one other person on payroll.

So let's throw out everything you've heard and start over with what's actually true at your size.

An "AI office" for a business like yours isn't a system. It's not software you buy, it's not a dashboard, it's not a robot answering your phone and closing deals while you sleep. At this size, an AI office is two things and two things only:

1. One place where every call, every quote, and every note about a customer lives — so you stop being the only filing cabinet in the business.
2. One automated task — a single thing that used to require you to remember to do it, and now happens by itself.

That's it. That's the whole course. One brain, one automation.

Here's why that's the right size for where you're at. You've already fixed the four big leaks — missed calls, slow invoices, no reviews, no follow-up. You did that by hand, with scripts and habits, in Courses 1 through 4. This course isn't asking you to throw that out and buy a system. It's asking you to take the one habit that's hardest to keep up by hand — remembering everything, and following up the second something falls through — and hand a small piece of it to a tool that doesn't forget and doesn't get tired.

What this course will NOT do: it will not turn your phone into a full-time receptionist. It will not write your quotes for you. It will not replace a person answering calls, and if anyone tells you a free automation does that, they're selling you something. What it WILL do is close one specific gap — the missed call that never gets a text back — and give you a place to put everything else so it's not living in three text threads and a notepad on your dash.

By the end of this course you'll have exactly two things running: a doc, and an automation. Nothing else. Let's build them.

---

5.2 — Build your brain — one place every call, quote, and note lands

Right now, ask yourself where the answer to this question lives: "What did I quote the Hendersons for the gutter job, and when did I say I'd call them back?"

If the honest answer is "it's in my head" or "it's somewhere in my texts" — that's the problem this lesson fixes.

You don't need software for this. You need one doc, and a habit of using it. A Google Doc works. A Notion page works. Even a plain notes app works, as long as you can search it. The tool doesn't matter. The structure does. Here's the exact structure to copy.

Open a blank doc right now and paste this in, editing the bracketed parts for your business:

THE BRAIN — [Your Business Name]

HOW TO USE THIS: Every call, every quote, every promise you make to a customer gets logged here within an hour of it happening. If it's not here, it didn't happen. Ctrl+F (or Cmd+F) to search a name before you call anyone back.

SECTION 1 — ACTIVE JOBS (One line per job. Update the status as it moves.)

[Date] — [Customer name] — [Job] — [Quoted price] — [Status: Quoted / Scheduled / In progress / Done] — [Next action + date]

Example:

7/10 — Denise Hall — gutter guard install, back of house — $840 quoted — Scheduled for 7/22 — Confirm morning of

SECTION 2 — QUOTES OUT (waiting to hear back) (This is your Course 4 follow-up list — it lives here now, not on paper.)

[Date quoted] — [Customer] — [Job] — [Amount] — [Follow-up dates: Day 1 / Day 4 / Day 10] — [Result]

SECTION 3 — CUSTOMER NOTES (searchable — this is the whole point) (One entry per customer, ever. This is what saves you from asking the same question twice.)

[Customer name]
— Phone: [number]
— Property/job type: [notes]
— Preferences: [gate code, dog in yard, prefers text over calls, etc.]
— History: [past jobs, dates, what was done]
— Last contact: [date] — [what was said/promised]

SECTION 4 — RECURRING / SEASONAL CUSTOMERS (Anyone who comes back on a cycle — quarterly service, seasonal jobs, annual maintenance.)

[Customer] — [Cycle: e.g. every spring] — [Last serviced] — [Next expected] — [Reminder set: Y/N]

SECTION 5 — THE 5-MINUTE RULE Every entry above gets written the same day the call, quote, or job happens — ideally within 5 minutes, before you move to the next thing. If you wait until end of day, it doesn't get written, and the doc becomes useless. Log it from your truck. Log it from the driveway. Log it before you start the next job.

That's the whole doc. Five sections, one habit: write it down the same day, in the same place, every time. In two weeks you'll have a searchable record of every customer you've ever quoted — something that used to only exist in your head, and now exists somewhere you can find it in ten seconds flat.

---

5.3 — Your first agent — one automated follow-up recipe (missed call → auto-text)

Here's the leak this lesson plugs: you're on a roof, under a sink, halfway through a job — the phone rings, you can't get to it, and by the time you're free again, you've forgotten the call ever happened. That caller hangs up, tries the next name on their list, and books with someone else. Not because your price was wrong. Because nobody texted them back in the first five minutes.

You're going to fix that with one automation. Not a system, not a subscription you'll forget you're paying for — one recipe, built once, that runs forever in the background.

What you need before you start: - Whatever phone system or CRM you already use for business calls (this could be your cell carrier's call log, a Google Voice number, or whatever system your business line runs on). - A free account with an automation tool — Zapier and Make are the two most common, both have free tiers, and this recipe works the same in either one. Pick whichever one your phone/CRM already lists as a connection option.

The recipe, step by step:

1. Pick your trigger. In your automation tool, start a new automation and choose your phone/CRM app as the trigger app. Look for an event called something like "Missed Call" or "Call Ended — No Answer." If your specific system doesn't have a missed-call trigger by name, look for "New Voicemail" instead — most systems that miss a call also log a voicemail, and that works just as well as the trigger.

2. Set the filter (optional but recommended). If you want the text to only go out during business hours, add a filter step: only continue if the call came in between your set hours (say 7am–6pm). This stops a 3am spam call from triggering a text nobody needed.

3. Pick your action. Choose an SMS-sending app as the action — this is usually the same phone/CRM system from step 1, or a plain SMS app your automation tool connects to. The action is: send a text message to the phone number that just called.

4. Write the message. Use the caller's phone number as a variable (your automation tool will show you how to insert it — usually a click-to-insert field). Here's the actual message to use, word for word:

"Hey, sorry we missed your call — this is [Business Name]. What can we help with? Reply here and we'll get right back to you, or call us back at [number]."

Keep it that short. Don't add anything salesy. The whole job of this text is to make the caller feel like a person is on the other end, fast — not to pitch them.

5. Turn it on and test it. Call your own business line from another phone and don't pick up. Confirm the text arrives within a minute. If it doesn't fire, the trigger step is usually the problem — go back and check that the trigger event actually matches what your phone/CRM calls a missed call.

6. Log every reply in the Brain doc from 5.2. When someone texts back, that reply goes straight into Section 3 (Customer Notes) the same day, same as any other call.

That's the whole automation. One trigger, one filter, one action, one message. It doesn't book the job for you, it doesn't quote a price, it doesn't replace you picking up the phone when you can. What it does is buy you the five minutes you needed but didn't have — automatically, every single time, for the life of the business.

---

5.4 — Where AI note-taking/summarizing actually saves time vs. where it's a toy

There's a flood of AI note-taking and call-summary apps out right now, and most of the noise online makes them sound like they'll transform your business. Some of them genuinely save time. Most of them add a step instead of removing one. Here's how to tell the difference before you spend an afternoon setting one up.

Where it actually saves time:

• Recapping a long call so you don't have to re-listen to it. If you take a 20-minute call with a customer walking through a complicated job, a tool that turns that recording into five bullet points of what was discussed and what was promised is a real time-save. You'd have had to write those notes by hand anyway — now they're done for you, and they go straight into Section 3 of your Brain doc.
• Turning a voice memo into text. If you're the type who talks a note into your phone while driving between jobs ("remind me the Petersons want the quote emailed, not texted") — a tool that transcribes that into readable text and drops it somewhere you can copy from is saving you actual typing time.
• Summarizing a long text thread with a customer before you call them back. If a customer has sent you eight texts over two weeks and you need the gist before you call, a summary tool that condenses that thread is faster than scrolling and re-reading.

Where it's a toy:

• Anything that requires you to learn a new app just to use it once a week. If the setup takes longer than the time it saves you over a month, skip it.
• "AI assistants" that promise to draft your quotes or emails for you from scratch. These usually produce something generic that you end up rewriting anyway — which means you did the work twice.
• Anything that needs you to change how you already take calls or notes. The whole point of the Brain doc and the missed-call text is that they slot into what you're already doing. A note-taking tool that asks you to record every call through a special app, remember to open it first, and then still copy the output somewhere else — that's three new habits to save you one.

The test to run before adopting any of these: would this save me time in the next 30 days, using it exactly the way it's meant to be used, with zero extra setup? If the honest answer is "maybe, eventually, once I get used to it" — it's a toy for you right now. Come back to it later. The Brain doc and the missed-call text from this course don't need that test. They're already the smallest version of "AI office" that pays for itself the same week you build it.

---

5.5 — Week 5 challenge: set up your brain doc + one starter automation

This week isn't a new concept. It's a deadline for the two things you already built the instructions for in 5.2 and 5.3. Here's the finish line, in order.

THE WEEK 5 CHECKLIST

Day 1-2 — Build the Brain - [ ] Copy the 5-section template from Lesson 5.2 into a Google Doc or Notion page. - [ ] Fill in Section 3 (Customer Notes) with your 10 most active customers — don't try to backfill every customer you've ever had, just start with who you're actively working with right now. - [ ] Bookmark the doc somewhere you'll actually open it — home screen, browser bar, wherever you already look ten times a day.

Day 3-4 — Build the Automation - [ ] Set up a free Zapier or Make account. - [ ] Follow the 6-step recipe from Lesson 5.3: trigger on missed call, filter by hours (optional), action sends the text, using the exact message from 5.3. - [ ] Test it by calling your own business line and letting it go to a missed call. Confirm the text lands within a minute.

Day 5 — The 5-Minute Rule, live - [ ] For every call, quote, and job today, log it in the Brain doc within 5 minutes of it happening — not at the end of the day. This is the habit that makes the doc worth anything.

Day 6-7 — Prove it - [ ] Let one real missed call hit your business line and confirm the auto-text fired on its own, with no one at the keyboard. - [ ] Search your Brain doc for a customer name using Ctrl+F / Cmd+F and confirm you can find their full history in under ten seconds.

When both boxes at the bottom are checked, you're done with Course 5. You now have one place that remembers what you used to have to remember yourself, and one leak — the missed call with no follow-up — that plugs itself, automatically, every time it happens, whether you're on the roof, under the truck, or asleep.

That's the whole "AI office" at your size. Not a system. Not a subscription you forget about. One doc, one automation, both built in a week, both already paying for themselves.

Visuals

Course 5 — Your AI Back Office — Visuals

Every visual below is grounded in specific lines/moments from script.md. One producer picks up this file and knows exactly what to build — no generic stock-photo filler, no restating the lesson title as a "visual." Course 5 is allowed to say "AI" and "automation" openly (per the blackboard's exception), but visuals should stay as grounded and unhyped as the script itself — no glowing brains, no robot hands, no sci-fi AI iconography.

---

5.1 — What "AI office" actually means for a one-truck business (grounding, no hype)

Visual 1 — stack: "Two things. Two things only."

Two-card stack, pulled verbatim from the script's own numbered list — this is the entire course compressed into one image, so it should look deliberately small and plain, not like a "system": 1. One place — where every call, every quote, and every note about a customer lives. 2. One automation — a single thing that used to require you remembering to do it, that now happens by itself. Caption under the stack, verbatim: "That's it. That's the whole course."

Visual 2 — comparison: What this course will NOT do vs. what it WILL do

Two-column comparison straight from the script's own framing, used to kill the hype before it starts: - Left column ("What this will NOT do"): "Turn your phone into a full-time receptionist." / "Write your quotes for you." / "Replace a person answering calls." - Right column ("What it WILL do"): "Close one specific gap — the missed call that never gets a text back." / "Give you one place to put everything else instead of three text threads and a notepad on your dash." Visual should read as a deflation, not a sales pitch — the left column is longer and more dramatic-sounding on purpose, the right column is short and concrete.

Visual 3 — pull_quote: "If anyone tells you a free automation does that, they're selling you something."

Pull the exact line from the script. Use this as the lesson's closing frame — it's the honesty check that separates this course from the "AI will run your business" noise named in the opening paragraph, and it sets up the tool-agnostic, no-hype tone for the rest of the course.

---

5.2 — Build your brain — one place every call, quote, and note lands

Visual 4 — stack: The 5 sections of the Brain doc

Five-card vertical stack, one card per section, using the script's own section names and one-line jobs: 1. Active Jobs — one line per job, status updated as it moves. 2. Quotes Out — the Course 4 follow-up list, now living in one place. 3. Customer Notes — searchable, one entry per customer, ever. 4. Recurring / Seasonal Customers — anyone who comes back on a cycle. 5. The 5-Minute Rule — the habit that makes the other four sections worth anything. Caption: "Five sections, one habit." This is the doc's skeleton — a learner should be able to rebuild the whole template just from this card.

Visual 5 — screenshot-mockup: The Brain doc, filled in

Google-Doc-style mockup showing Section 1 (Active Jobs) with the script's exact example row filled in: "7/10 — Denise Hall — gutter guard install, back of house — $840 quoted — Scheduled for 7/22 — Confirm morning of." Show the column template row directly above it in brackets so the mockup teaches the format at the same time it shows a real example. This is the "copy this exact structure" visual — no invented customer beyond the one already in the script.

Visual 6 — pull_quote: "If it's not here, it didn't happen."

Pull the exact line from the "HOW TO USE THIS" instructions at the top of the doc template. This is the doc's one governing rule — treat it as the thesis statement of the whole lesson, the way 4.1's "silence doesn't mean no" worked for Course 4.

Visual 7 — statement: The 5-Minute Rule

Full-bleed statement card with the script's own line: "Log it from your truck. Log it from the driveway. Log it before you start the next job." This is the behavior-change ask of the lesson — the doc only works if this rule holds, and the script says so directly ("if you wait until end of day, it doesn't get written, and the doc becomes useless").

---

5.3 — Your first agent — one automated follow-up recipe (missed call → auto-text)

Visual 8 — step_diagram: The 6-step recipe, in order

Six-step horizontal or vertical flow using the script's own numbered steps, each labeled with its function, not just its number: 1. Pick your trigger — "Missed Call" or "Call Ended — No Answer" event in your phone/CRM (fall back to "New Voicemail" if no missed-call trigger exists). 2. Set the filter (optional) — only continue if the call landed inside business hours. 3. Pick your action — send an SMS to the number that just called. 4. Write the message — the exact word-for-word text from the script (see Visual 9). 5. Turn it on and test it — call your own line from another phone, confirm the text arrives within a minute. 6. Log every reply in the Brain doc — straight into Section 3, same day. This is the deliverable's operational spine — a learner should be able to build the automation from this diagram alone, in either Zapier or Make.

Visual 9 — screenshot-mockup: The auto-text, as the customer sees it

Phone-frame mockup showing a missed-call notification followed immediately by the auto-text arriving as a message bubble, using the script's exact copy word for word: "Hey, sorry we missed your call — this is [Business Name]. What can we help with? Reply here and we'll get right back to you, or call us back at [number]." This is the "here's what actually lands on their phone" visual — it should look boring and human, not like a bot message, which is the whole point the script makes ("make the caller feel like a person is on the other end").

Visual 10 — loop: The automation running in the background, forever

Circular/loop diagram showing the cycle that repeats with no one at the keyboard: Call comes in → missed → auto-text fires within a minute → customer replies → reply gets logged in the Brain doc (Section 3) → loop resets for the next call. Caption: "Runs forever in the background — no subscription you'll forget you're paying for, no one at the keyboard." This is the payoff visual for "this is an agent," not a one-time script — it should visually loop back on itself, unlike the linear 6-step build diagram in Visual 8.

Visual 11 — key_takeaway: What you need before you start

Two-item checklist callout, pulled from the script's "What you need before you start" block: - Whatever phone system or CRM you already use for business calls. - A free Zapier or Make account (pick whichever your phone/CRM already lists as a connection option). Frame as "you already have most of this" — removes the most common reason someone skips the lesson (thinking they need to buy new software first).

---

5.4 — Where AI note-taking/summarizing actually saves time vs. where it's a toy

Visual 12 — comparison: Saves time vs. is a toy

Two-column comparison, straight from the script's own bulleted breakdown — this is the lesson's entire argument in one image: - Left column ("Actually saves time"): "Recapping a long call so you don't have to re-listen to it." / "Turning a voice memo into text." / "Summarizing a long text thread with a customer before you call them back." - Right column ("It's a toy"): "Anything that requires learning a new app just to use it once a week." / "'AI assistants' that draft quotes or emails from scratch — you rewrite them anyway." / "Anything that needs you to change how you already take calls or notes." Caption should note the script's own diagnostic for the right column: "Three new habits to save you one."

Visual 13 — pull_quote: The 30-day test

Pull the exact line: "Would this save me time in the next 30 days, using it exactly the way it's meant to be used, with zero extra setup?" Frame this as the filter a learner runs on any new AI tool going forward — the lesson's takeaway isn't a list of approved apps (which would go stale), it's this one question, matching the blackboard's non-goal of not hard-recommending specific vendors.

---

5.5 — Week 5 challenge: set up your brain doc + one starter automation

Visual 14 — step_diagram: The Week 5 timeline, day by day

Four-block horizontal timeline using the script's own checklist headers: 1. Day 1-2 — Build the Brain: copy the 5-section template, fill Section 3 with your 10 most active customers, bookmark it somewhere you'll actually open it. 2. Day 3-4 — Build the Automation: set up Zapier/Make, follow the 6-step recipe from 5.3, test with a call to your own line. 3. Day 5 — The 5-Minute Rule, live: log every call, quote, and job the same day, within 5 minutes. 4. Day 6-7 — Prove it: let one real missed call hit the line and confirm the auto-text fired with no one at the keyboard; search the Brain doc for a name and confirm you find it in under ten seconds. This should read as a literal, tickable checklist a learner follows day by day — it's the Week 5 operational spine, the same role Visual 14 played for Course 4.

Visual 15 — key_takeaway: The two proof checks that close out the course

Callout box with the script's own two closing tests: - "Let one real missed call hit your line — confirm the auto-text fired on its own, with no one at the keyboard." - "Search your Brain doc for a customer name — confirm you find their full history in under ten seconds." Frame as: "When both boxes are checked, you're done with Course 5." This is the lesson's own definition of done — use it, don't invent a different completion metric.

Visual 16 — pull_quote: The closing line of the course

Pull the exact closing sentence: "One doc, one automation, both built in a week, both already paying for themselves." Use as the final-frame visual for the whole course — the callback that closes the loop opened in 5.1's "that's the whole course" line.

---

Deliverable — Starter brain template + automation recipe, written out step by step

Visual 17 — stack: The two-part deliverable

Two-card stack matching the blackboard's deliverable spec exactly: 1. The starter Brain doc template — the 5-section structure from 5.2, ready to copy into a blank Google Doc or Notion page. 2. The missed-call automation recipe — the 6-step build from 5.3, written out plainly enough to follow in either Zapier or Make. Caption: "Copy the doc. Build the automation. That's the whole deliverable."

Visual 18 — screenshot-mockup: The Brain doc template, blank and filled

Split visual: left half shows the blank 5-section template exactly as formatted in 5.2 (bracketed fields, no data); right half shows the same template with the Denise Hall active-jobs row and one Customer Notes entry filled in, reusing the example from Visual 5 for consistency. Caption: "What you paste in" / "What it looks like two weeks in."

---

Total: 18 visuals across 5 lessons + 1 deliverable.

Brief

Course 6 Brief — Scale Without Hiring

Dream outcome (Hormozi value equation)

Value = (Dream Outcome × Perceived Likelihood) ÷ (Time Delay + Effort)

Dream outcome: You can grow past the ceiling one person creates — more jobs, more revenue, more nights off — without the first hire being the thing that grows the headaches instead of the business. You know exactly what to hand off, what to keep, and which of two honest paths gets you there.

Perceived likelihood: High, and rising through the whole course. By Course 6 the member has already automated the five biggest office leaks solo (missed calls, invoice chasing, reviews, follow-up, a starter AI brain). The "can I actually scale without adding payroll" question isn't theoretical anymore — they've been doing it for five weeks. This course just names what they've already proven and gives them the next decision.

Time delay: Near-zero for the decision itself. Lesson 6.1 is a 15-minute gut-check math exercise, not a research project. The chosen path (DIY further, or hand off) starts the same day.

Effort: Low. This course is not "go build another system." It's a decision framework — three short lessons of math and honest tradeoffs, then a fork in the road. The effort was already spent in Courses 1-5; this course just cashes it in.

Who this course is for

A one-truck or small-crew owner who has run the Leak Score gauntlet — missed calls plugged, invoices chased, reviews flowing, follow-up automated, a starter brain and one automation live — and is now hitting the next wall: there's more work than one person can do, and the obvious next move ("hire someone") feels expensive, risky, and slow. They're not looking for hustle-culture "scale to 7 figures" content. They want a clear, honest answer to "do I hire, do I keep DIY-ing, or do I pay someone else to run this for me" — with real numbers, not vibes.

The fastest believable win

Within the first lesson, before touching any tool: run the actual math on what a part-time office hire costs (wage + payroll tax + training time + management time + the mistakes a new hire makes in month one) versus what the last five weeks of DIY systems have been doing for free. Most owners have never run this math — they've only ever compared "hire" against "keep drowning," never "hire" against "the systems I already built." Seeing the real number is the win. It reframes the whole decision before lesson two even starts.

The felt problem each lesson solves

• 6.1 — Real cost of your next hire vs. doing it yourself: "I think I need to hire someone, but I have no idea what that actually costs me — in money or in my time training them." Solves the fear of running the numbers by just running them, in plain terms, side by side with what's already automated.
• 6.2 — What to hand off first, what never to: "If I do hire or outsource something, I don't know what's safe to let go of and what will blow up in my face if I'm not the one doing it." Solves the all-or-nothing trap — owners either try to hand off everything at once (chaos) or nothing at all (burnout) because no one ever showed them the order to do it in.
• 6.3 — DIY vs. done-for-you, honest breakdown: "Every option I've seen is either a sales pitch for software or a sales pitch for an agency — nobody's told me straight which one actually fits a business my size." Solves the trust gap with a plain, non-salesy comparison of continuing to DIY the systems from Courses 1-5 versus paying someone to run the whole back office for you.
• 6.4 — Your two options going forward: "Okay, so what do I actually do NOW?" Solves decision paralysis at the exact moment it would otherwise stall the member out — this is the exit ramp, routed by the member's own quiz answers, to whichever of the two paths (self-serve phone tool or concierge whole-office service) actually fits their leak profile. Never both, never a hard pitch — just "here's your fit."
• 6.5 — Graduation: "I've done five weeks of work — did any of it actually add up to something?" Solves the invisible-progress problem. Owners who've been heads-down fixing one leak at a time rarely stop to see the whole system they've built. This lesson makes them look back at it on purpose, names what they now have, and points at what's next instead of just ending.

How this connects to the course before and after it

Before (Course 5 — Your AI Back Office): Course 5 gave the member a working brain (a searchable notes system) and one live automation (missed call → auto-text) — proof that a one-person shop can run on systems, not headcount. Course 6 picks up exactly there: now that you've seen what one automation can do, what happens when you need more than automation can cover? That's the hiring question, and Course 6 is where it finally gets answered with real numbers instead of guesswork.

After — there is no Course 7. Course 6 is the bridge and the graduation moment at once. Lesson 6.4 is the honest exit ramp — routed by the member's own quiz answers to whichever path fits (the self-serve phone tool for someone who wants to keep DIY-ing with better tools, or the concierge whole-office service for someone who's decided their time is better spent running jobs than running the office) — and 6.5 closes the loop by naming what the member built across all six courses before sending them on to whichever path they picked. Nothing after this course is "more lessons" — it's "you're done here, here's where you go next."

Script

Course 6 Script — Scale Without Hiring

Word-for-word lesson script. Five lessons, no week-6 challenge (this course is the bridge and the graduation moment, not another system to build). No separate deliverable file for this course — the worksheet, handoff list, and comparison below are the deliverable, delivered inside the lessons themselves.

---

Course open (plays before 6.1)

You've fixed five leaks now. Missed calls stopped bleeding you money. Invoices get chased instead of forgotten. Reviews come in because you ask, on schedule, instead of hoping. Old customers get a text instead of falling off the list. And you've got a brain — one place every call and quote lands — plus one automation running in the background without you touching it.

So here's the question this course answers, and it's the one you've probably been sitting on since before you even signed up for this: now what — do I hire somebody?

This course doesn't tell you "yes, hire" or "no, don't." It gives you the real math, the real order of operations, and the real honest comparison, so the decision you make is yours, made with numbers instead of a gut feeling at 11pm. Fifteen minutes of math in the next lesson, and you'll know more about your own hiring decision than most owners ever bother to find out.

---

6.1 — Real cost of your next hire vs. doing it yourself

You've been running one number in your head for weeks. Maybe months. It goes something like: "I'd pay them 20 bucks an hour, that's not bad." That number is wrong. Not a little wrong — most owners are underestimating the real cost of a hire by two, sometimes three times. Not because they're bad at math. Because nobody ever showed them the full list of what's actually in that number.

So we're going to build it together, right now, with your numbers. Grab a piece of paper, or open a blank note. This takes fifteen minutes and it's the most useful fifteen minutes in this whole course.

The real cost of the hire. Write these five lines down:

1. Hourly wage — what you'd actually pay them, times 40 hours a week, times roughly 4.3 weeks in a month. That's your base.
2. Payroll tax and insurance — add about 12-15% on top of that base. That's not optional, that's the government's cut and your workers' comp, whether you remember it or not.
3. Training time — your hourly rate (what an hour of YOUR time is worth, not theirs), times the hours you'll spend training them in weeks one through four. Be honest — it's rarely under 20 hours total.
4. Ongoing management time — your hourly rate again, times roughly 3 hours a week, every week, forever. Checking their work, answering their questions, fixing what they missed. This one doesn't stop after month one.
5. The month-one mistake tax — a new hire will misquote a job, send a review request to the wrong person, or leave a customer on hold too long at least once in their first month. Put a real number on what one of those mistakes costs you. One redone job. One lost review. One customer who doesn't call back.

Add lines 1 through 5. That's the real monthly cost of the hire — not the number you've been carrying around, the actual one.

Now write down the second list: what the last five weeks have been doing for you, for free. Missed calls getting caught and answered. Invoices getting chased on a schedule so you don't have to remember. Reviews getting asked for at the 48-hour window instead of never. Old customers getting a text that brings some of them back. Every call and quote landing in one place instead of your head. None of that has a wage. None of it has payroll tax. It's already running.

Here's the point of this exercise, and it's not "don't ever hire." It's this: you've been comparing "hire someone" against "keep drowning." That's an easy comparison to win — of course hiring looks good against drowning. But that's not the real comparison anymore. The real comparison is "hire someone" against "the systems I already built, running for free." Run that comparison with your actual numbers, and the decision gets a lot clearer, one way or the other.

You don't need the answer today. You need the real number. Write it down, keep it, and carry it into the next lesson — because knowing the cost is only half of it. The other half is knowing what you'd actually hand off first.

---

6.2 — What to hand off first, what never to

Most owners get this part backwards in one of two ways. Either they try to hand everything off at once — the calls, the quotes, the pricing, the customer relationships, all in the first week — and it turns into chaos because nobody, not even you, can absorb that much change that fast. Or they hand off nothing, ever, because they're scared of getting burned once, and they stay the bottleneck in their own business forever.

There's a third way, and it's just an order of operations. Some things are safe to hand off on day one. Some things you only hand off once you've built real trust. And some things you should never hand off, full stop — not to an employee, not to a service, not to anybody but you.

Tier 1 — hand off first. Anything you've already turned into a script in this course. That's the whole point of a script: it removes the judgment call. The review-ask texts from Course 3, the invoice-chase sequence from Course 2, the follow-up touches from Course 4 — these are word-for-word already. Anyone who can read can run them without needing your instinct for the job. Low risk, because the hard thinking already happened when you wrote the script.

Tier 2 — hand off once you trust the person. Quoting simple, repeat jobs using your own template. Scheduling. Basic callbacks to customers you already know. These need a little judgment — reading a customer's tone, knowing when something's off — but the mistakes are forgivable. A slightly-off quote on a small job costs you an adjustment call, not the customer.

Tier 3 — never hand off, or hand off dead last, to someone you've vetted hard. Pricing judgment on custom or complicated jobs. The actual call on who gets a discount or an exception. Anything touching money that isn't already scripted. And your relationship with your best, longest customers — the ones who call you by name. That stays yours. Not because nobody else could ever learn it. Because the cost of getting it wrong once is bigger than the time it saves you.

Here's the rule of thumb to carry forward, whether you hire, outsource, or automate further: if it's already in a script, it's ready to hand off. If it's still a judgment call living in your head, script it first — then hand it off. That's the order. Script, then delegate. Never the other way around.

---

6.3 — DIY vs. done-for-you, honest breakdown

Every option you've probably run into online is trying to sell you something. Software wants you to believe you can DIY your way to a fully automated back office with the right app. Agencies want you to believe DIY is a trap and you should just pay someone to take it off your plate. Neither one is going to give you the straight comparison, because they both need you to land on their answer. This lesson isn't selling either side. It's laying both out so you can see which one actually fits a business your size.

Keep DIY-ing it (continue running what you built in Courses 1-5, yourself).

• Cost: Lowest. Mostly your time, plus whatever a template or two costs you.
• Your time: You're still the one running it — checking the follow-up list, tweaking the automation, making sure the brain doc stays current.
• Control: Total. Nothing changes unless you change it.
• Ceiling: Real, but it's your ceiling. What one person, running solid systems, can cover — that's the limit. More jobs than that, and something starts to slip again.
• Best fit: You've got the time to keep tending it, or the business isn't past what one disciplined person can run.

Pay someone to run the whole back office for you (done-for-you).

• Cost: Higher, in a straight line — you're paying for someone else's time and attention, not just a tool.
• Your time: Mostly freed up. You're not the one checking whether the follow-up went out.
• Control: Lower, by design — you're trusting someone else's process, not micromanaging your own.
• Ceiling: Higher. It's not bound by how many hours you personally have left in a day.
• Best fit: Your time is worth more running jobs and managing crews than running an office, and you've hit the point where "one more system to tend" isn't the answer anymore — you need it off your plate entirely.

Neither one is the smart choice and neither one is the naive choice. They fit different owners at different points. An owner with more time than money should probably keep DIY-ing it a while longer. An owner with more revenue than hours is usually better off paying someone else to run it. There's no wrong answer here — there's just your answer, and the next lesson helps you land on it.

---

6.4 — Your two options going forward

Back when you took the Leak Score quiz, before any of this started, you answered a set of questions about where your office actually leaks the worst, and what kind of owner you are — hands-on, or hands-off. That answer has been sitting quietly in the background this whole time. This is the lesson where it comes back into play.

There are two honest paths from here. Not five, not a menu — two. And you already lean toward one of them, whether you've said it out loud yet or not.

If you're the type who wants to keep doing this yourself, just with sharper tools — there's a self-serve phone tool built for exactly the job you've been doing by hand since Course 1: it answers the calls you can't get to, texts the caller back, and gets the job booked, so the front desk never goes quiet even when it's just you on the truck. You stay hands-on. You just stop being the bottleneck the phone waits on.

If you've decided your hours are worth more running jobs than running an office — there's a concierge, whole-office service that takes over everything you just spent five weeks proving out on your own: the calls, the follow-up, the review requests, the invoice chasing — run by real people, not just a doc and an automation. You hand off the office. You keep the jobs.

Both of these are good outcomes. Neither one is the "graduated" version of the other. The tool that fits you is the one that matches what you actually want your day to look like six months from now — still hands-on and lean, or fully out of the office and onto the tools. Your quiz answer already pointed at one of these. Look right below this lesson for the one that matches yours, and that's your next step — today, not "eventually."

---

6.5 — Graduation

Five weeks ago you had one job title and no idea how much of it was office work instead of the work you actually love doing. Look at what's sitting behind you now.

You know your Leak Score, and you know exactly where the money was slipping out — not a guess, a number. You've got a quote-in-10-minutes template so a missed call doesn't turn into a missed job. You've got a chase sequence running so invoices past 30 days don't just sit there hoping someone remembers them. You've got review-ask scripts that don't sound needy, going out at the 48-hour window every time. You've got a follow-up and win-back system pulling old customers back in instead of writing them off. You've got a brain — one place every call, quote, and note lands — and one automation running behind the scenes without you lifting a finger. And now, you've got a straight answer on hiring: the real cost, the right order to hand things off in, and an honest read on DIY versus paying someone else to take it over.

That's not five lessons. That's a business that runs differently than it did before you started. Most owners never stop moving long enough to notice they built something — they just keep fixing whatever's loudest that week. You didn't do that. You went leak by leak, on purpose, and it added up to this.

Here's what happens next: you already picked your path in the last lesson — either sharper tools to keep running it yourself, or handing the whole office to someone else so you can go run jobs. Go take that next step today, while the last five weeks are still fresh. The weekly live call and the community aren't going anywhere — that's still here for you, whichever path you're on. But this course is done. You finished it. Go use what you built.

Visuals

Course 6 — Scale Without Hiring — Visuals

Every lesson ships at least one visual. Types match the taxonomy in .claude/rules/ralph-wiggum.md: stack / loop / step_diagram / comparison / matrix / stat / pull_quote / key_takeaway / statement / screenshot-mockup. Nothing below invents a stat or testimonial — every line, number, and quote is pulled directly from script.md. This course has no separate deliverable file (the worksheet, handoff list, and comparison ARE the lesson content), so its visuals do double duty as the take-away artifacts.

---

Course open — plays before 6.1

Visual 1 — stack: "What you've already fixed" recap

Five stacked blocks, bottom to top, each labeled with the leak it plugged (pulled verbatim from the course-open copy): 1. Missed calls — stopped bleeding you money 2. Invoices — chased instead of forgotten 3. Reviews — come in because you ask, on schedule 4. Old customers — get a text instead of falling off the list 5. A brain + one automation — running in the background without you touching it Capstone line above the stack, set apart: "Now what — do I hire somebody?" This is the question the whole course answers, so it needs to land as the visual's payoff, not just a header.

---

Lesson 6.1 — Real cost of your next hire vs. doing it yourself

Visual 2 — stack: "The real cost of the hire" build-up

Five stacked line items building to a total, in the exact order the script gives them — each block should look like it's adding onto the one below it, ending in a bolded total bar: 1. Hourly wage — wage × 40 hrs/week × ~4.3 weeks/month (the base) 2. Payroll tax + insurance — +12-15% on top of the base 3. Training time — owner's hourly rate × hours spent training (rarely under 20 hours total across weeks 1-4) 4. Ongoing management time — owner's hourly rate × ~3 hrs/week, every week, forever 5. Month-one mistake tax — the real cost of one misquote, one botched review request, or one customer left on hold too long → Total bar: "The real monthly cost of the hire — not the number you've been carrying around."

Visual 3 — comparison: "Hire someone" vs. "what's already running for free"

Two columns, side by side: - Left, headed "Hire someone" (has a wage): the five cost lines from Visual 2, collapsed to their labels only (wage, payroll tax, training, management, mistake tax). - Right, headed "What the last five weeks built (no wage)": missed calls caught and answered / invoices chased on schedule / reviews asked at the 48-hour window / old customers getting a text back / every call and quote landing in one place. Each right-column line closes with "— $0/mo." Footer line under both columns, verbatim from the script: "None of that has a wage. None of it has payroll tax. It's already running."

Visual 4 — pull_quote

"You've been comparing 'hire someone' against 'keep drowning.' That's an easy comparison to win... The real comparison is 'hire someone' against 'the systems I already built, running for free.'" This is the lesson's reframe and the reason the 15-minute math exercise matters — it needs its own beat, separate from the two stacked/columned visuals above it.

---

Lesson 6.2 — What to hand off first, what never to

Visual 5 — matrix: the three hand-off tiers

A 3-row matrix, risk level increasing top to bottom:

Tier	Hand off when	Examples (from the script)	Why it's safe/risky
Tier 1 — hand off first	Day one	Review-ask texts (Course 3), invoice-chase sequence (Course 2), follow-up touches (Course 4)	Already scripted word-for-word — no judgment call left in it
Tier 2 — hand off once trusted	Once you trust the person	Quoting simple/repeat jobs from your template, scheduling, basic callbacks to known customers	Needs some judgment, but mistakes are forgivable — costs an adjustment call, not the customer
Tier 3 — never, or dead last	Only to someone vetted hard	Pricing judgment on custom jobs, discount/exception calls, your relationship with your best long-term customers	Cost of getting it wrong once outweighs the time it saves

Visual 6 — key_takeaway

Single bolded rule, verbatim from the lesson's closing line: "If it's already in a script, it's ready to hand off. If it's still a judgment call living in your head, script it first — then hand it off. Script, then delegate. Never the other way around."

---

Lesson 6.3 — DIY vs. done-for-you, honest breakdown

Visual 7 — comparison: DIY vs. done-for-you, side by side

A 2-column, 5-row comparison table, using the exact five dimensions and language from the script:

	Keep DIY-ing it	Pay someone to run it (done-for-you)
Cost	Lowest — mostly your time, plus a template or two	Higher, in a straight line — paying for someone else's time and attention
Your time	Still yours to run — checking the list, tweaking the automation, keeping the brain doc current	Mostly freed up — you're not the one checking whether it went out
Control	Total — nothing changes unless you change it	Lower, by design — you're trusting someone else's process
Ceiling	Real, but it's your ceiling — what one disciplined person can cover	Higher — not bound by your personal hours left in a day
Best fit	You've got time to keep tending it, or you're not past what one person can run	Your time is worth more running jobs than running an office

Header line above the table, verbatim: "Neither one is the smart choice and neither one is the naive choice." No winner declared inside the visual — the table is the comparison, not a verdict.

---

Lesson 6.4 — Your two options going forward

Visual 8 — step_diagram: the quiz-routed fork

A single fork diagram, not a linear chain: 1. Starting point: "Your Leak Score quiz answer" (taken before Course 1 even started) 2. Splits into two paths, side by side, no ranking between them: - Path A — "Keep doing this yourself, with sharper tools": a self-serve phone tool that answers calls you can't get to, texts the caller back, and gets the job booked. Caption: "You stay hands-on. You just stop being the bottleneck the phone waits on." - Path B — "Hand off the whole office": a concierge, whole-office service that runs the calls, follow-up, review requests, and invoice chasing — real people, not just a doc and an automation. Caption: "You hand off the office. You keep the jobs." 3. Closing instruction beneath both paths: "Your quiz answer already pointed at one of these. That's your next step — today, not 'eventually.'" This diagram IS the exit-ramp moment — render it so the member's own path is what they act on immediately below the lesson, per the blackboard's routing rule (never both, never named as brands inside the content).

---

Lesson 6.5 — Graduation

Visual 9 — stack: everything built, five weeks in

Seven stacked blocks recapping the full course arc, each pulled directly from the lesson's own recap paragraph: 1. Your Leak Score — you know exactly where the money was slipping out 2. Quote-in-10-minutes template — a missed call doesn't turn into a missed job 3. 3/15/30/45 chase sequence — invoices past 30 days don't just sit there 4. Review-ask scripts at the 48-hour window, every time 5. Follow-up + win-back system pulling old customers back in 6. A brain + one automation running behind the scenes 7. A straight answer on hiring — real cost, hand-off order, DIY vs. done-for-you Header above the stack: "That's not five lessons. That's a business that runs differently than it did before you started."

Visual 10 — statement

Large, single-line closing statement, the final words of the course, verbatim:

"This course is done. You finished it. Go use what you built." This is the graduation beat the blackboard calls out explicitly — it should feel like a closing screen, not another lesson card, and it's the last visual asset in the entire curriculum.

---

Count: 10 visuals across 1 course-open beat + 5 lessons (no separate course-level deliverable asset — this course's worksheet/matrix/comparison visuals above already double as the take-away artifacts).