9 Mechanism Script Structures

The 97% Rule: at any given moment, only 3% of homeowners in your market are actively searching for foundation repair or waterproofing. You and every competitor are fighting over that same 3%. The other 97% will need your service — they just don't know you exist yet.

The only way to reach the 97% before they start shopping is to have a testing system that's always loading the next angle. Never rely on a winning ad. I don't care if it's booking 15 estimates a week. The moment you stop testing, you're one algorithm shift away from a dead week and a crew sitting idle. Most contractors have one ad working and 12 that aren't. That's not a testing system. That's a gamble with a good streak.

The ad dies — fatigue, platform change, season shifts. Nothing behind it. Estimator calendar goes from full to three appointments. At $8K average job, that's two or three crew days lost. Not because the market dried up — because the pipeline was a single lane. "We found what works" is a warning, not a finish line.

When something works you leave it alone — that's triage, not laziness. The problem is "leave it alone" only works if a system is loading the next angle in the background. Most contractors think testing means guessing. What this flips: the homeowner market tells you which angles work. You just give it enough to vote on.

Estimator calendar stops being a source of anxiety. Multiple angles loaded — when one softens another picks up. CPL stabilizes instead of drifting up. After 8 weeks of clean scoring, you know your market: which fear closes fastest in your geography, which persona books fastest, which format your algorithm rewards. You're not guessing anymore. The system loads angles, the market scores them, you review a one-pager and make one call: cut or scale. That's the demand flywheel running — and it gets tighter every week because last week's data informs this week's test.

The 97% Rule says stop fishing in the 3% pond. But you can run 20 angles and the demand flywheel still won't tighten if the algorithm is optimizing for the wrong person. Meta optimizes for exactly what you tell it. Six months of Lead Gen objective = pixel trained on people who fill out every free form they see. That's not your customer.

Two rules before anything else: never use your business name as your Facebook page name. And never use Lead Gen as your campaign objective. Here's how to train the algorithm on booked jobs instead — so each rotation of the demand flywheel is cheaper than the last.

Meta's algorithm optimizes for exactly what you told it. You said "get me form fills" — it found people who fill out every free form they see. That's the algorithm's model of your customer. Every dollar you spend going forward finds more people who look like them. The longer you run it that way, the deeper the hole. Meta isn't broken — it's doing exactly what you told it to do.

"Facebook leads are just low quality now" — that's not a Meta problem, that's a signal problem. Meta can only optimize for what you send it. The fix isn't a new platform or more budget. It's changing what you send back. When you send it booked jobs, closed jobs, real job values — the algorithm builds a model of your actual customer. That's when the demand flywheel starts tightening on its own.

CPL goes up short term — fewer leads but they're real. Setter converts 8/10 instead of 3/10. Cost per booked estimate drops month over month as Meta builds a model from your actual closed jobs. The 14M+ closed-won jobs anchor accelerates the whole thing — you're not starting from scratch. That's the demand flywheel tightening: same ad spend, better leads, better algorithm, better leads again next month.

The 97% Rule says you can reach homeowners before they're shopping. The demand flywheel generates that interest. But if that interest hits a form at 7:14 PM on a Thursday and nobody sees it until Friday morning — the homeowner's already booked with a competitor and the signal that just fired was a form fill, not a booked job. The intake is where the demand flywheel either captures what it generates or leaks it. Never send paid traffic to a form.

Lead hits a form, goes to an inbox, someone has to decide: is this real? Either they respond slow or they put a tire-kicker on the calendar — estimator drives 45 minutes to quote a $600 crack fill for a price shopper. Not a people problem. A process problem. Costing you booked estimates, estimator hours, and the clean signal the algorithm needs to tighten the demand flywheel.

"My office already handles this." The question isn't whether they're doing it — it's how fast and how consistently. Variables leak. The AI isn't diagnosing anything. It collects four pieces of information. The moment someone asks "is this serious?" the AI says "that's exactly what we want our estimator to find out — let me grab a couple details first."

9:47 PM Wednesday. Homeowner DMs "FOUNDATION." AI responds in 20 seconds. By 10:02, all 4 collected. Setter gets a Slack notification. Thursday 8:15 AM, setter calls. Lead picks up, expecting the call. Estimate booked for Friday. Job closes. Booked estimate fires back to Meta as a signal. Algorithm notes: DM at 9:47 PM, this fear bucket, this zip, this urgency level — find more people like this. That's the demand flywheel running: intake isn't just catching leads, it's feeding the signal that makes next month's leads better.

The 5-Handoff Rule: every job has exactly 5 handoffs between when a homeowner first shows interest and when you get paid. Lead to first contact. First contact to qualified. Qualified to booked estimate. Booked estimate to show. Show to closed job. Each one leaks. Most contractors fix zero of them.

This mechanism patches the first two — and they're the ones that bleed most silently. Never wait more than 2 minutes. Never leave a voicemail. Here's how to respond in under 60 seconds, qualify the job before anyone opens a calendar, and book the estimate — without your office watching anything.

The 2-minute window is real. Inside 2 minutes, contact rate is roughly 8× higher than waiting 30 minutes. The homeowner didn't submit one form — they submitted three. First one to talk to them wins the estimate. If your process is: lead sits in inbox, office checks it in the morning, calls during business hours, leaves voicemail — you've already lost Handoff 1. And when you lose Handoff 1 consistently, the sales flywheel never starts spinning.

"Our office follows up when they can" — at a growing company, that's 3–5 hours after the lead came in. Speed is how you prove yourself before you've ever met them.

Show rate goes from 55–70% to 80–85%. At 20 estimates a month, that's 3–4 more jobs you're actually in the room for. The sales flywheel starts spinning: fast contact → qualified estimate → more shows → more closes → more proof. Each closed job feeds Mechanism 06, which feeds the next close. When Handoffs 1 and 2 are airtight, the compounding effect downstream becomes visible in your close rate within 30 days.

The 5-Handoff Rule. Mechanism 04 patched Handoffs 1 and 2. This one patches the back end — the estimate and the close. Most contractors think they have this handled. But if you drove off without presenting options in person, you handed the decision to a PDF. That PDF is competing against two other PDFs. They all look the same. Never leave without good/better/best. Never present one price.

Homeowner gets your PDF, two other PDFs. All three have a number, a scope line, a signature box. They're calling back the guy who felt right. The quote-to-job gap isn't about price — it's about trust. Trust starts dying the second you drive off without presenting options.

"The appointment went great — I sold it in the home." You didn't sell it if you left without a signature. You had a good conversation. One price says the only thing that matters is that number. Three prices let them buy up and feel like they made a choice instead of just agreeing to a number.

Close rate up 10–15 points — not because you got cheaper, but because you stopped being forgettable. The sales flywheel tightens: more closes → more proof → proof used in next follow-up → next follow-up easier → higher close rate → more closes again. Contractors stop saying "we lost it on price" and start saying "we lost it because follow-up was too slow" — which is a fixable problem with a measurable fix.

The 5-Handoff Rule has a sixth move that nobody talks about — and it's the one that connects the sales flywheel back to the demand flywheel. After the job closes, most contractors pack up and drive to the next one. No before. No after. No review ask. No referral ask. That job paid you once. But it could have loaded the algorithm with a real closed-job signal, given the estimator proof for the next kitchen table close, and referred two neighbors with the same problem. When you capture that, one job becomes the catalyst for the next three — and the signal from that job makes future ads find better homeowners. That's what makes this mechanism the bridge between both flywheels.

You spent $8K–$40K getting that homeowner to say yes. Job is done. You pack up. No before. No after. No review. No referral ask. That job is dead — paid you once. And the algorithm never got the signal that would've made the next lead like that one cheaper to find.

"Word of mouth handles it." Word of mouth is invisible. Can't track it, can't scale it, can't turn it into an ad. "We'll remember to ask for reviews." No you won't — not consistently. The reason isn't laziness — nobody built the play.

$3M waterproofing company, 15 jobs/month. Before: 3–4 Google reviews/month, ad creative unchanged for 6 months, algorithm starved of real job signals. After: 12–15 new reviews/month, rating 4.1 → 4.6, two referral jobs a week, ad account rotating fresh before/after every two weeks, estimator pulling up local job proof at the kitchen table. Close rate goes up. Cost per booked job drops. Both flywheels tighter — simultaneously — from the same mechanism.

The Rule of One: one source of truth, one brain, one view of the full business. If you need more than one login to answer one question, there's no brain — there's just you. And a business where the owner is the integration layer can only grow as fast as the owner can run.

This is Mechanism 07, and it's the one that makes the Demand and Sales flywheels self-improving. Without it, both loops run until they break and nobody notices. With it, every problem that surfaces makes the next rotation of both flywheels tighter.

The "6-login morning": ad account, CRM, call tracker, calendar, QuickBooks, spreadsheet — 45 minutes and you still don't know if your show rate dropped this week or which leads from Monday are still alive. The Demand Flywheel could be leaking at the algorithm. The Sales Flywheel could be leaking at Handoff 3. You won't find out until a week of bad data shows up in a report you only pulled because something felt off.

"More dashboards means more control." The problem isn't complexity — nobody set it up to be seen in one place.

Monday morning. One view: 14 leads last week, 11 contacted in 5 min, 8 booked, 6 showed, 4 closed, $8,400 average job, $610 cost per closed job. Show rate dipped 75% vs 84% — confirmation texts didn't go out Thursday. Fix: automate the confirmation. One sales guy closed 1 of 3 estimates. Another closed 3 of 3. Coaching conversation, not a "leads are bad" conversation. Didn't log into 6 places. Looked at one screen, made 2 decisions. That's the Operations Flywheel starting to spin.

The Rule of One also means one place where problems surface — while they're happening, not after a customer calls. Most contractors running automated systems don't know when they stop working. They find out two weeks later when close rate is down and they're reverse-engineering what happened. By then the leads are gone, the jobs are gone, and you're just doing math on a loss. The AI Second Brain sees the business. This mechanism watches it and fires the moment something deviates. The alert fires first. Always.

Automated follow-up breaks Thursday. 12–18 leads get zero contact in their first 5 minutes. Contact rate drops by half. At $8K average ticket: $30K–$50K in potential revenue gone and you didn't feel it happen. A dashboard tells you what happened. A fire alarm tells you what's happening. That distinction is worth 6 figures a year at volume.

"We review the monthly report." That's a post-mortem. You built the system, it worked, you assumed it would keep working. Systems drift. Integrations break. Workflows fall out of sync. The fire alarm is the layer that watches for you.

Wednesday afternoon, workflow silently stops. Old world: you find out Friday morning. Two days gone. New world: 40 minutes after the workflow stops, Slack alert fires. Ops person checks, restarts integration, manually pushes the 6 leads. Total downtime: 40 minutes. Another: show rate drops 18 points in 4 days. Alert fires on day 2. Pull the booked calls — all from a new Facebook campaign targeting outside your service area. Shut it down Wednesday, not Friday. The Operations Flywheel is spinning: Brain sees the deviation, Fire Alarm catches it in real time, Self-Improvement Loop logs the fix.

The Rule of One has a third dimension most people miss: memory. A business can only improve what it can see — and it can only fix what it can remember broke. The AI Second Brain gives it sight. The AI Fire Alarm gives it detection. This mechanism gives it memory. And memory is what makes the Operations Flywheel the meta-flywheel — the one that makes the Demand and Sales flywheels permanently tighter every week, not just operational.

Never make the same mistake twice. The system catches it, the system fixes it, the system checks that it's fixed. Three moves to build that memory.

Lead falls through a crack Monday. You catch it Wednesday, say something in the group chat. Next Monday — same crack, different lead. The mistake lives in your head, not the workflow. When you scale that workflow, you scale the mistakes. At 30 clients, 10 recurring errors are manageable. At 100, those same 10 errors are running everywhere simultaneously and nobody can tell you which ones keep repeating because nothing was ever written down.

"They just need to pay more attention." If paying attention were the fix, you'd have fixed it already. The process never told them what to do when something went sideways. The workflow has no memory. That's what we're building.

Tuesday. CSM notices three appointments this week had wrong crew lead assigned. Logs it — customer impact, caught internally. 3 questions: process exists but reassignment column is buried. Workflow gap. Fix: reassignment column becomes a required field before an appointment can be confirmed. 20 minutes to set up. One week later, ops checks the log — zero crew lead assignment errors. Fix held. Logged resolved. Nobody got yelled at. The process got smarter. Multiply that by one fix per week for a year: 52 workflow gaps closed. Every one of them tightening the Demand or Sales flywheel in ways that compound silently.