IG Reel Outlines — 30 NEVER Statements
Each reel has one job: stop the scroll, name the mistake, show the fix, drive to the Leak Check. Short-form drives to YouTube hub videos. YouTube drives to the booking page.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never build next month's payroll on one ad that can die tomorrow."
One ad stops performing. CPL doubles overnight. Suddenly there's no budget to test anything new because all the spend was in one place. Lead volume collapses. The calendar empties. And it was completely predictable.
They found a winner and held on. No testing system, no backup creative, no rotation plan. One good ad became a single point of failure.
- Rotate at least 3–5 hooks in market at all times
- Drop a new angle every 2 weeks — before the old one dies
- Test one variable at a time: hook, fear angle, format, spokesperson
- Kill anything under your CPL threshold after 7 days. Scale what holds.
One winning ad isn't a creative strategy.
It's a single point of failure.
The week it stops working — CPL spikes, leads drop, calendar empties.
The fix is a rotation system. Multiple hooks in market. New creative testing every 2 weeks. You're never dependent on one ad.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never optimize for cheap leads when you need booked inspections."
You get 80 leads a month. Cost looks great. But half never answer. A quarter aren't homeowners. The ones who do book are price-shopping tire-kickers. Your cost per booked inspection is actually double what it looks like.
They optimize for form fills because the pixel fires on every one and the dashboard looks healthy. Nobody connected that signal to actual job quality.
- Fire your conversion event on a qualified conversation — not a form submit
- Qualified = project confirmed, zip confirmed, homeowner confirmed, urgency captured
- That signal trains Meta to find people who actually convert
- Your CPL goes up slightly. Your cost per closed job drops significantly.
Cheap leads aren't cheap.
If they don't answer, don't qualify, and don't book — you paid full price for nothing.
The fix: fire your conversion event on a qualified conversation, not a form submit.
Now Meta trains on the signal that actually produces jobs.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never make a scared homeowner fill out a form and wait."
A homeowner notices a crack on a Sunday evening. They're nervous. They Google. They find you. They fill out your form. Monday morning someone sees it and calls. Voicemail. They already booked two estimates from contractors who responded that night.
Forms are easy to set up. Everyone uses them. Nobody questioned whether a homeowner in problem-solving mode actually wants to fill out a form and wait 12 hours.
- Route paid traffic to a conversation — Messenger, SMS, or a live chat widget
- AI opens the conversation immediately, regardless of time or day
- Four questions: what's going on, zip code, homeowner, urgency
- Qualified? Calendar opens. Not qualified? Clean exit. No form. No lag.
A homeowner with a foundation problem isn't browsing.
They're worried. They want answers now.
A form and a 12-hour wait is the worst possible response to that emotion.
A conversation that starts in 60 seconds — any time of day — is the right one.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never wait more than 2 minutes to respond. Text or lose the job."
They reached out to three contractors. You called back four hours later. The other two already talked to them. One has an estimate scheduled. You spent money on that lead and got a voicemail.
The office is busy. The estimator's on a job. Nobody's watching the inbox at 7 PM. So the lead waits. And moves on. It's not laziness — it's a missing system.
- AI fires a text the second the lead comes in — no human needed
- One conversational opener, one question, keeps them engaged
- Speed-to-lead becomes a system, not a person's responsibility
- First contractor to have a real conversation almost always books the estimate.
2 minutes.
That's how long you have before a homeowner moves to the next contractor.
They submitted the form. They're waiting. First real conversation usually wins the estimate.
The fix isn't more office staff. It's a system that fires instantly, every time, no matter what.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never leave a voicemail and call it follow-up."
You called. No answer. Left a voicemail. Checked the box. Felt like you did the job. The homeowner saw one missed call and a voicemail notification and moved on. You lost that lead the second you hit record.
It's what they've always done. Call. Leave message. Wait. It worked 15 years ago. Homeowners were less busy and had fewer options. Now it's a dead channel.
- Text immediately after the missed call — conversational, one question
- "Hey, tried calling — saw you had a question about your foundation. What's going on?"
- If no reply in 4 hours: one more text
- 24-hour follow-up: final touch. That's the sequence. No voicemails.
Voicemails are a dead channel for contractor lead follow-up.
Nobody listens. Nobody calls back.
Text immediately. One human question. Keep it warm.
4-hour follow-up if no reply. 24-hour final touch.
That's the sequence. Simple. No voicemails.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never buy more leads before fixing follow-up."
You spend $8,000 on ads. Get 60 leads. Contact 30. Book 12. Six show. Three close. The math looks fine until you realize you had 60 opportunities and turned 57 of them into nothing. The problem isn't the 60. It's everything that happens after.
More leads feels like action. It's easier to increase spend than to audit a system. And agencies will happily take your money to send more leads into the same broken funnel.
- Audit each stage first: lead → contact → book → show → close
- Find the biggest drop-off. That's your constraint. Fix that first.
- Usually it's contact rate or show rate — not lead volume
- Once the funnel converts consistently, then scale spend.
More leads into a broken follow-up system doesn't grow your business.
It just makes the leak more expensive.
60 leads. 3 jobs. That's a funnel problem, not a volume problem.
Audit first. Fix the drop-off. Then scale.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never confuse lead volume with revenue."
The dashboard shows 80 leads this month. The owner feels good. But close rate is 12%, show rate is 55%, and average job value is down. Revenue is flat. Leads were up. Something doesn't add up — because lead volume and revenue aren't the same metric.
Lead count is easy to report and feels like progress. Revenue per lead tells a different story. Most teams report what's easiest, not what's most useful.
- Track cost per closed job — not cost per lead
- Track revenue per lead source — not just volume per source
- The number that matters: how much did we spend to produce each closed job?
- Everything else is a vanity metric.
80 leads and flat revenue is not a win.
Lead volume is an input metric.
The metric that actually matters: cost per closed job.
How much did we spend — across ads, labor, and time — to produce each job on the calendar?
That's the number. Everything else is noise.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let your estimator walk into a house blind."
Estimator drives 40 minutes. Walks in. Homeowner's renting the place. Job is outside your service area. Or they want a quote for a $400 crack repair. Two hours gone. A real opportunity missed.
The intake process didn't qualify. Someone booked the appointment because the homeowner seemed interested. Interest isn't qualification. A qualified lead has a real project, a real address, and is the actual decision-maker.
- Collect project type, zip code, homeowner status, and urgency before any calendar access
- AI handles this in the first conversation — no manual screening needed
- Estimator gets a brief before every appointment: what the job is, what the homeowner said, what the urgency level is
- They walk in prepared. Not guessing.
An estimator walking in blind is an expensive problem.
Wrong service area. Not the homeowner. $400 job. 40-minute drive each way.
The fix: qualify before the calendar opens. Project, zip, homeowner status, urgency.
Estimator walks in with a brief. They already know the job before they knock.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never send trucks to unqualified appointments."
Truck, fuel, crew time, estimator time — each appointment costs real money before a single dollar comes in. Send that to a non-homeowner, a wrong-service-area job, or a tire-kicker, and you just burned $200–$400 on nothing.
The booking process was optimized for volume, not quality. More appointments on the calendar feels like momentum. Unqualified appointments feel like leads until the estimator shows up.
- Never open the calendar until project, zip, homeowner, and urgency are confirmed
- AI screens every inbound — nights, weekends, overflow — before a slot is offered
- Unqualified? Clean exit with a reason and a referral if applicable
- Qualified? Booked, briefed, confirmed.
Every unqualified appointment is a real dollar spent for zero return.
Truck. Fuel. Estimator time. Admin time.
The fix: screen before the calendar opens. Every time. Automatically.
Qualified lead gets a slot. Everyone else gets a clean exit.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never present one price. One price makes it yes-or-no."
You send a number. They compare it to two other numbers. Cheapest wins. You just turned a $14,000 job into a price war you didn't have to be in — because one price gives homeowners nothing to choose between except your number and someone else's.
Contractors think the homeowner wants a number. They don't. They want to feel like they made the right decision. One option doesn't give them that — it just creates friction.
- Good — solves the core problem, gets them stable
- Better — stronger protection, longer warranty, fewer callbacks
- Best — complete long-term fix, eliminates the issue permanently
- Present all three in person. Now they're deciding between your options, not comparing your price to a competitor's.
One price creates a yes-or-no decision.
Three options create a which-one decision.
Good / Better / Best presented in person changes the frame completely.
They stop comparing your number to a competitor's. They start deciding which level of protection makes sense for their home.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never email a quote and pray."
You did the estimate. Great walkthrough. Built trust. Sent the PDF. Three days later: nothing. "Just checking in" text. Still nothing. That job went to someone who followed up with a reason — not a better price.
They think if the homeowner's interested, they'll reach out. They won't. Life gets in the way. The urgency fades. Competitors stay in their inbox. You don't.
- Recap — confirm what you found and what the fix is
- Risk — what happens if they wait 6–12 months (concrete, structural, cost)
- Proof — a local before/after or review from a similar job
- Next step — one clear ask. Not "let me know."
The PDF isn't the close. The follow-up is.
Recap what you found. Remind them of the risk of waiting. Show proof from a similar job nearby. Give them one clear next step.
Not "just checking in."
Not "let me know if you have questions."
A reason to say yes.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never compete on price before building trust."
You walk in and lead with your process, your price, your warranty. The homeowner smiles and says they'll think about it. They didn't trust you yet. And without trust, price is the only variable left to compare.
Contractors pitch what they're proud of — their work, their method, their materials. But the homeowner doesn't care about any of that until they believe you understand their specific problem.
- Start with what you saw and what it means for their home specifically
- Show you've solved the exact same problem for someone nearby
- Risk first — what happens if they don't fix it and when
- Then the solution. Trust is built before price is ever mentioned.
Price only beats you when trust isn't there yet.
When a homeowner trusts you, price becomes a conversation about which option — not whether to hire you at all.
Build trust before you pitch. Show you understand their specific problem. Then present the solution.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never explain your process before the homeowner understands the risk."
You explain the helical piers, the waterproofing membrane, the drainage system. Their eyes glaze. They nod politely. They have no idea why it matters. So when they get a cheaper quote, they pick it — because they don't understand what they're actually choosing between.
Contractors are proud of their craft. They want to explain how it works. But process detail without context of risk lands as noise — especially to a homeowner who's never dealt with this before.
- Lead with the risk: what happens to this home's foundation if this goes unaddressed
- Translate into their language: resale value, structural safety, insurance implications, timeline
- Once they feel the weight of the problem — then show them how you solve it
- The solution lands differently when the risk is understood first.
Nobody cares about your process until they understand the risk.
Lead with what happens if they wait.
Resale value. Structural damage. Insurance implications. Timeline of deterioration.
Once they feel the weight of the problem, your solution makes sense. Without that context, it's just contractor jargon.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let your sales process stop after the estimate."
The estimate went well. You built rapport. Left feeling good. Three days later they went with someone else. Not because the other company was better — because they followed up and you didn't. The estimate was the start of the sale, not the end.
Most contractors treat the estimate as the deliverable. It's not. It's the opening of a sales window. What happens in the 48–72 hours after the estimate usually determines who gets the job.
- Same-day follow-up: thank you + recap of what you found
- Day 2: the risk of waiting — specific to their situation
- Day 3: proof — a review or before/after from a similar local job
- Day 5: final check-in with a clear close attempt
The estimate isn't the close. It's the beginning of the close.
Same day: recap.
Day 2: risk of waiting.
Day 3: social proof.
Day 5: close attempt.
That's 5 days of follow-up that most contractors skip entirely.
The job often goes to whoever stays in the conversation longest.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never assume the homeowner remembers what you said after you leave the driveway."
You gave a thorough walkthrough. Explained everything clearly. They nodded. You left confident. A week later they're comparing your PDF to two others and they've forgotten 80% of what you said. The conversation that built trust is gone. Now it's just numbers.
Homeowners are busy. They talk to multiple contractors. The walkthrough details blur together. If you don't give them something to reference — in writing, in their language — your explanation evaporates.
- Send a written recap the same day — what you found, why it matters, what you're proposing
- Include a photo or two from their actual home
- One sentence on the risk of waiting
- One sentence on what the job includes — in plain language, not technical specs
They nodded during your walkthrough.
A week later they're comparing PDFs and everything you said is gone.
Send a same-day recap. Their home, their problem, their risk, your solution.
In plain language. With a photo. In writing.
Trust doesn't survive on memory alone.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let a completed job pay you only once."
You paid to acquire a customer. Did great work. Left. Then paid again to get the next one. Same cost, same effort, no compounding. That job had at least 3 more opportunities attached to it — review, referral, content — and you left all of them on the table.
The mindset is: job done, move on. Get the next lead. There's no system for extraction because nobody built one. So the value of each completed job stays at one transaction.
- Referral seed before the job ends: "Know anyone else with a wet basement or crack issues?"
- Review ask from estimator's personal phone — not a mass text — right after the job
- Before/after video or photos captured by the crew
- Those assets go into ads, sales presentations, and the next follow-up sequence.
One completed job should create three more opportunities.
A review that shows up when the next homeowner Googles you.
A referral from a neighbor who saw your truck.
A before/after that becomes your next best ad.
None of that happens automatically.
You need a system that captures it every single time.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never finish a job without proof, reviews, referrals, and content."
Every job that leaves without capturing proof is a missed marketing asset. You spent money to get the customer. You did the work. You left with nothing to show the next one. The cost of acquiring new customers never drops because you never build social proof equity.
Crews are focused on the job. Office is focused on the next booking. Nobody's job is to extract value from completed work. So it doesn't happen.
- Crew checklist: before photo, after photo, 30-second walkthrough video — every job
- Estimator closes every completed job with a review ask and a referral ask
- All assets land in a shared folder, tagged by job type and city
- Creative team pulls from this weekly — new ad content without new shoots.
Every completed job is a marketing asset.
Before photo. After photo. 30-second walkthrough. Review ask. Referral ask.
That's the checklist. Every job. No exceptions.
The companies with the best social proof didn't hire photographers. They built a system on the job site.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never need six logins to know if the business is making money."
You check ads. CRM. Calendar. Call tracking. QuickBooks. A spreadsheet someone started 18 months ago. Spend 45 minutes and still aren't sure what actually happened this week. The answer to one question required six tools and you're still not confident in the number.
Tools get added one at a time as the business grows. Nobody connects them. The owner just adds tabs to the morning routine.
- Eight numbers is all you need: leads → contact rate → booked → show rate → close rate → avg job value → revenue → cost per closed job
- One dashboard that reads all sources automatically
- You stop checking. The dashboard tells you.
- Alerts fire when anything drops — you don't find out at the end of the week.
The six-login morning is a tax on clarity.
By the time you've checked everything, you're already behind on the day.
8 numbers. One dashboard. Alerts when something breaks.
You stop checking. The system tells you.
That's what visibility looks like at scale.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let the owner become the human dashboard."
Every KPI question goes to the owner. Every exception goes to the owner. Every report gets pulled by the owner. The owner is doing the job of a system — manually, repeatedly, reactively. That's not leadership. That's bottleneck.
The business scaled without building reporting infrastructure. The owner filled the gap because they were the only one who knew where everything lived. Now that habit is calcified.
- Identify the 5 questions the owner gets asked most often — build automated answers for each
- Dashboard surfaces those answers every morning without being asked
- Anomaly alerts replace reactive check-ins
- Owner's job shifts from looking up data to acting on it.
If you're the one who knows where everything is — you're not the CEO. You're the filing cabinet.
The owner should be acting on information, not retrieving it.
Build the dashboard. Set the alerts. Answer the recurring questions automatically.
Then lead.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let customers become your quality-control system."
A bad review. A chargeback. A referral source that stopped sending. By the time you heard about it, the damage was done. Revenue dropped. Reputation took a hit. And the root cause had been building for weeks.
Without monitoring, everything is reactive. Problems surface when they can't be hidden anymore — usually from a customer complaint. That's quality control by failure.
- Monitor the metrics that predict complaints before complaints happen
- Show rate drops? That's a confirmation problem — fix it before it becomes a no-show spike
- Jobs taking longer than projected? That's a scope problem — address it before the customer calls
- The system catches the signal. You fix the cause.
Customers shouldn't be your QC system.
By the time they're telling you something went wrong, the damage is already done.
Monitor the metrics that predict problems: show rate, callback rate, job duration vs estimate, review velocity.
Fix the cause before it becomes a customer complaint.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never discover broken systems from angry homeowners."
One-star review goes live. You find out from a team member who saw it. You go investigate. Turns out the issue had been happening for three weeks — three callbacks, two missed follow-ups, one unresolved complaint. Revenue already impacted before you knew.
No monitoring. No alerts. No trip wire. Everything runs fine until a customer blows up, and that's when the problem becomes visible. By then it's a crisis, not a correction.
- Alert when a lead hasn't been contacted in 30+ minutes
- Alert when show rate drops more than 15% week over week
- Alert when no jobs close in 72 hours
- Alert when a callback appears twice for the same job
You should never find out something broke from an angry homeowner.
By then you're already in damage control.
Build the monitoring layer. Alerts for contact rate, show rate, job closures, callbacks.
You fix it before the customer has a reason to complain.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never solve recurring mistakes with "more training." Fix the workflow."
Same mistake. Third time this quarter. Owner calls a training meeting. Everybody nods. It happens again next month. Not because the team is bad — because the workflow still allows the mistake. Training is a patch. Workflow is the fix.
"More training" feels productive and avoids the harder work of auditing why the process keeps failing. It's easier to coach people than to redesign the system they're working inside.
- When a mistake happens: log it, find the root cause, identify where the workflow allowed it
- Update the workflow — checklist, automation trigger, or approval gate
- Confirm the fix held: check in 2 weeks
- If it happens again, the workflow fix wasn't complete.
"More training" is the most expensive recurring mistake in contracting.
If the workflow allows the error, training doesn't fix it. It just delays the next occurrence.
Log → root cause → workflow update → verify.
Systems don't forget. People do.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never yell at people for problems your system keeps allowing."
Owner escalates. Team apologizes. Owner resolves it. Everyone moves on. Next week: same issue. The team isn't malicious — the system has no guardrail. Frustration doesn't fix the root cause. A workflow update does.
It's easier and more immediate to hold people accountable than to audit the process they're working inside. But accountability without system change produces the same outcome every time.
- When you find yourself repeating the same correction: stop and ask why the system allows this
- Is there a missing checklist? A missing confirmation step? A missing ownership assignment?
- Fix that. The team didn't fail — the process did.
- Then verify: did the fix hold for 30 days?
If it keeps happening, it's not a people problem. It's a system problem.
The system is allowing the mistake. Every time you correct without fixing the system, you're just resetting the clock.
Log it. Find the workflow gap. Fix the gap. Verify.
Stop managing symptoms. Fix the cause.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let your business run on staff memory."
Sarah's out today. Nobody knows where the Jones follow-up sits. Three callbacks didn't happen. Two leads went cold. One estimate got missed. All because the process lived in Sarah's head — not in the system.
The company grew fast through hustle. People figured things out. It worked until it didn't. Now the knowledge is distributed across whoever's been there longest, and nothing is written down.
- Every repeatable process gets documented and automated where possible
- Follow-up sequences run in the CRM, not in someone's head
- Checklists exist for every stage: estimate, install, follow-up, review ask
- New person walks in, picks up the system, leads don't go cold.
Memory-based operations have a single point of failure: the person who holds all of it.
When they're out, everything slows or stops.
Document every repeatable process. Put follow-up sequences in the CRM. Build checklists for every stage.
Systems don't call in sick.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never rely on hustle to hold the operation together."
The owner works 60-hour weeks keeping everything from falling apart. Leads don't slip through because he's personally watching. Jobs don't get missed because she's manually checking. It works until it doesn't — and when it breaks, everything breaks at once.
The company grew because of the founder's hustle. That became the operating model. And because it works well enough at small scale, nobody questions whether it can scale — until it can't.
- Identify the 3 things only you do manually that a system could do instead
- Build or automate each one
- Your job is to build systems, not to be the system
- When you're out, the business should not feel it.
Hustle built the business. Hustle will also cap it.
At some point the owner can't add more hours. They're already working all of them.
The shift: build the system that does what you're doing manually.
When you're out, the business doesn't feel it.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never scale chaos."
Revenue doubles. So does the confusion. More leads means more missed calls. More jobs means more scheduling errors. More crews means more communication breakdowns. Growth made the chaos louder, not quieter. Now it's expensive chaos.
They scaled what they had because the opportunity was there. Nobody stopped to fix the foundation of the operation before building on top of it. Scaling works until the chaos becomes the cost.
- Before scaling: audit what breaks at current volume
- Fix the systems that are already failing
- Then scale — with infrastructure underneath the growth
- Growth on a solid system compounds. Growth on chaos multiplies the problems.
Scaling a chaotic operation doesn't fix chaos.
It funds it.
More leads into a broken follow-up system. More jobs into scheduling chaos. More revenue into a business the owner can barely hold together.
Fix the foundation. Then scale.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never let growth create more confusion than revenue."
Revenue went up 40% this year. Profit margin dropped. Owner stress went up. Team is stretched. Communication is worse. The business grew into a harder version of itself — not a better one.
They optimized for top-line growth without building the operational infrastructure to support it. More revenue without more systems means more complexity without more control.
- Track gross margin per job — not just revenue
- Track owner hours per week — if it goes up as the business grows, something is wrong
- For every growth lever pulled, build the system that supports it
- Growth should create margin and bandwidth — not consume both.
Revenue is not the goal. Profitable, sustainable revenue is.
If growth is creating confusion, margin compression, and owner burnout — the operation isn't keeping pace with the top line.
Build the infrastructure. Then grow.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never treat AI tools like a business strategy."
Subscription after subscription. ChatGPT, a chatbot, an AI receptionist, a dashboard tool. $800/month in AI tools. Response time is still slow. Booking rate didn't move. The tools didn't connect to anything. They were toys, not infrastructure.
AI gets pitched as magic. Contractors buy the pitch. But isolated tools without workflow integration don't change business outcomes — they change nothing except the credit card statement.
- The only question that matters: does this change response time, booking rate, show rate, or close rate?
- If not — who cares
- AI infrastructure connects the dots: intake → CRM → calendar → follow-up → reporting
- The tool is irrelevant. The workflow it powers is everything.
Buying AI tools doesn't make your company AI-enabled.
That's like buying a hammer and saying you built a house.
The tools don't matter. The outcomes do.
Did response time improve? Did booking rate go up? Did close rate move?
If not — the tool is a subscription, not a strategy.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never automate a broken process."
The follow-up sequence was slow and inconsistent manually. They automated it. Now it's fast and inconsistently wrong — wrong timing, wrong message, wrong context. The AI is efficiently delivering a broken process to every lead.
Automation feels like a fix. It's not. It's an accelerator. If the process was broken before, automation makes it fail faster and at scale.
- Before automating anything: manually run it 10 times and see what breaks
- Fix the process until it works consistently by hand
- Then automate the working version
- Automation should make a good process faster — not replace the design work of building one.
Automation isn't the fix. It's the amplifier.
Automate a broken process and it breaks faster, at scale, on every lead.
Fix the process manually first. Run it 10 times. Find what breaks. Fix that.
Then automate the version that works.
→ Leak Check in bio.
"If you run a foundation repair or waterproofing company doing $1M–$10M… never use AI to sound smarter. Use it to respond faster and close more jobs."
They used AI to write better marketing copy. Fancier proposals. Smarter-sounding emails. Revenue didn't move. Because the homeowner doesn't care how smart your emails sound. They care how fast you showed up and whether you earned their trust.
AI gets used for the visible, impressive stuff — content, copy, presentations. The invisible, high-leverage stuff — response automation, follow-up sequences, lead routing — gets ignored because it's less exciting.
- Use AI to respond to leads in under 2 minutes, 24/7
- Use AI to run the post-estimate follow-up sequence automatically
- Use AI to alert you when a lead hasn't been contacted or a job hasn't closed
- Sound as plain as you want. Close more jobs.
AI that makes your emails sound smarter doesn't close more jobs.
AI that responds in 2 minutes closes more jobs.
AI that runs follow-up sequences closes more jobs.
AI that alerts you before a lead goes cold closes more jobs.
Use it where the revenue actually is.
→ Leak Check in bio.