Blog

  • Google Ads Analysis

    Google Ads Analysis

    Google Ads Analysis

    $250

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Split campaigns by service. Load negatives before you spend another week. Match every landing page to its ad group. Compute fully-loaded cost per acquired job, not just CPC. Buy Now is the packaged analysis delivered by email after checkout, so you are not assembling the read from a blank spreadsheet.

    Restoration PPC is an engineering problem, not a set-it-and-forget-it expense. Emergency water-damage keywords have been reported as high as $250 per click in competitive metros. Average emergency restoration keywords more commonly land in the $40-$150 range depending on geography. At those CPCs, structure and landing pages decide whether the phone pays you or you subsidize the auction.

    How to run the analysis

    1. Open the account. List every campaign, ad group, and the landing URL each ad actually hits.
    2. Mark the single-campaign trap if you see it: one campaign, one ad group, water / mold / fire / flood keywords fighting each other, every ad pointing at the homepage.
    3. Pull Search Terms for the last 30-60 days. Tag wasted queries (jobs, DIY, training, equipment rental).
    4. Check bidding against conversion volume. Under 30 conversions a month in a campaign is a different tool than 30+.
    5. Open each landing page on a phone. Does the H1 match the ad? Is click-to-call above the fold?
    6. Write fully-loaded cost per acquired job by channel: spend ÷ booked jobs from that channel, then layer close rate. CPC from the dashboard is not that number.

    1. Kill the single-campaign trap

    The most common setup: one campaign, one ad group, a mix of water damage, mold removal, fire restoration, and flood cleanup keywords all fighting each other. Every click gets the same generic ad. Every ad points to the homepage.

    Quality Score is built on expected click-through rate, ad relevance, and landing page experience. When you stuff water damage and fire restoration into the same ad group, ad relevance tanks for both. A Quality Score of 9 can outrank a competitor bidding twice as much at a 5. Poor structure can inflate CPC by 30% or more while delivering fewer qualified leads.

    Split by service. Each ad group 10-20 tightly related keywords. Every keyword in the group has to fit the same ad and the same landing page. If they do not, split them.

    • Campaign 1. Emergency water damage. Ad groups for emergency water extraction, burst pipe, basement flooding, sewage backup. Separate ad copy. Landing page that opens with emergency water damage, not the homepage.
    • Campaign 2. Fire and smoke restoration. Fire damage, smoke damage, soot removal. Different call to action. Fire jobs are longer projects, a different sales conversation.
    • Campaign 3. Mold remediation. Mold testing, black mold removal, mold inspection. Often a separate buyer with a different timeline.

    Give Performance Max its own campaign and its own budget if you run it. PMax black-box reporting will otherwise hide whether Search is working.

    2. Negative keywords: the bill you are not seeing

    Most restoration PPC campaigns have a weak or nonexistent negative list. Every day without one, you pay for job seekers (“water damage restoration jobs near me”), DIY researchers (“how to do water damage restoration yourself”), students looking for training, and equipment renters who are not calling you for service.

    Campaigns that actively manage negatives see a reported 10-20% lower wasted spend and a 5-15% conversion-rate lift. On a $10,000/month budget, that is $1,000-$2,000 a month currently going to irrelevant clicks.

    Build a seed negative list before the campaign launches. Pull Search Terms weekly for the first 60 days. Add exact-match negatives first. Only go broader if the data supports it. Over-blocking with broad-match negatives will starve volume you actually want.

    3. Bidding: stop fighting the machine

    A large share of Google Ads spend now runs through Smart Bidding (Target CPA, Target ROAS, Maximize Conversions). Advertisers using AI bidding have been reported at roughly 22% lower cost per conversion versus manual CPC on average. For restoration, the right tool depends on data:

    • Under 30 conversions per month in a campaign. Maximize Clicks with a CPC cap while you accumulate signal. Smart Bidding starved of conversions produces garbage.
    • 30+ conversions per month. Move to Target CPA. Set the target from actual job margins, not aspirational ones. If a water job averages $12,000 and you close 25% of qualified leads, a $300 CPL target can still profit. If you close under 15%, fix sales before you fix bidding.
    • Large campaigns with consistent job data. Target ROAS becomes viable only if revenue tracking is actually wired into Google Ads. Most restoration accounts do not have that configured.

    The problem is rarely the channel. It is losing track of where the leads went after the phone call.

    4. The landing page has to match the ad

    If the ad says “Emergency Basement Flooding, 24/7 Response” and the landing page is the homepage with a hero of a happy family and a form below the fold, you are burning the click you just paid for.

    A restoration PPC landing page needs: the emergency service name in the H1 above the fold; a click-to-call number prominent on mobile; a response-time claim only if you can back it up; one short form (name, phone, zip, issue); proof (reviews, IICRC, insurance logos).

    Do not send PPC traffic to the homepage. Do not build one landing page for all services. Match the ad to the page, the page to the ad group, the ad group to the keyword cluster. That chain is where Quality Score lives.

    5. Channel mix and the number that actually matters

    Three channels do the heavy lifting. LSA (pay per qualified call; reported restoration CPL roughly $80-$200 depending on the write-up) is the highest-ROI paid lever for most residential operators, with a catch: Google ended credits for “job type not serviced” and “geo not serviced” in 2025, so junk leads come out of your pocket. Search Ads (reported CPL $150-$400+ structured, $400-$700+ not) buy control LSA does not have: commercial work, specific service lines, overflow when LSA hits a daily cap, brand defense. If you are spending more than $5,000 a month on Search and you do not have LSAs set up, that is the first fix. SEO is the compounding asset. Restoration SEO in competitive metros typically takes 12-18 months. Treat reported ranges as ranges, not promises.

    Cost-per-lead is the number every vendor reports. The number that matters is fully-loaded cost per acquired job: CPL divided by channel-specific close rate, plus CSR labor on the call, plus processing, minus franchise or TPA fee if it applies. Most shops have CPL from the platform and revenue from the job software, and the two systems have never talked. Fix that before you change a single bid.

    Budget ballparks (Search only, reported)

    • Mid-size market (pop. 200K-500K): $3,000-$6,000/month to generate 15-30 leads
    • Major metro (pop. 1M+): $8,000-$15,000/month to maintain consistent visibility
    • Specific suburb or tight service area: $1,500-$3,000/month if geo is tight and Quality Score is managed

    These are Search figures. They are ballparks from the published method, not a quote for your market.

    Done when

    You can show separate service campaigns, a negative list with at least 50 entries, a dedicated landing page for each major service, and a fully-loaded acquired-job cost by channel. If your current agency cannot show those four, the account is not being run as an engineering problem.

    If you want the packaged analysis

    You can run the six steps from the outline above on your own login. Buy Now is the analysis delivered by email after checkout. Same Square button at the top of this page.

    Marketing and operational read only. Not a media-buy, legal, or insurance engagement. Reported CPC and CPL ranges move by metro and by month. Use your own numbers.

  • Conference Starter Pack

    Conference Starter Pack

    $97

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Score where you are still the bottleneck. Install 1-3-1 so the next problem comes back as a recommendation. Walk the 5 Ds as a what-if-tomorrow check. Buy Now is the packaged bundle: three Notion tools plus the matching Claude skills, so you are not assembling the starter pack from blank pages.

    The grab-and-go pack from the Restoration Leadership Toolkit. Three of the most-used tools, bundled. For restoration owners who just heard the doer-to-leader message and want something they can run this week, not a 12-week program on day one.

    What’s in the pack

    1. 1-3-1 Delegation Worksheet
    2. Owner Bottleneck Self-Assessment
    3. 5 Ds Succession Risk Checklist

    The matching skills from the Leadership AI plugin: delegation-1-3-1, owner-bottleneck-assessment, succession-5ds-checklist.

    Run them in this order. The bottleneck names the constraint. 1-3-1 is the first habit. The 5 Ds is the exposure you do not want to discover the hard way.

    1. Owner Bottleneck Self-Assessment

    Find out where your company still depends on you. An owner bottleneck exists when growth, decision speed, and consistency are limited by your personal involvement in day-to-day decisions. You become both the most important and the most constraining person in the business.

    Check the box for each statement that is true today. Count the checks in each section, then total them. Range is 0-25. Be honest. The value is in the truth.

    1. Decisions only you make. Estimate / pricing approvals over a set dollar amount. Hiring and firing. Vendor choices. Which jobs you take. Refunds, credits, concessions.
    2. Interruptions by department. Production calls daily. Office pulls you into billing or scheduling. Sales checks pricing before quoting. Techs call from job sites. Customer complaints land on you.
    3. Recurring questions. The same operational questions every week. People wait for you. “Ask the owner” is the default. You re-explain the same processes. Things stall when you are unavailable.
    4. Tasks that should be delegated. Estimates you could hand off. Scheduling / dispatch. Collections / AR. Ordering equipment. Work others could produce.
    5. Areas with no backup. No one else can run production. Only you hold key carrier relationships. Only you see the full financial picture. No written SOPs for the things you do. If you are gone a week, something breaks.

    Bands: 0-6 Mild (tighten the remaining gaps). 7-13 Moderate (you are the bottleneck in one or two areas; fix the worst one first). 14-19 Heavy (the business runs through you; start delegating now, deliberately). 20-25 Severe (you ARE the business; this is the #1 risk to growth and to an exit).

    Write your top 3 to delegate first. For one full week after you score, log every interrupt for a decision. Sort into Delegate now / Delegate after training / Keep (truly owner-only). The department with the most checks is this quarter’s target. Install 1-3-1 there first.

    2. 1-3-1 Delegation Worksheet

    The old way (escalation): “Hey boss, the dehu on the Maple St job died. What do you want me to do?” You just took back the problem, the thinking, and the decision. That is three jobs.

    The 1-3-1 way (delegation): “The dehu on Maple St died. Here are three options I looked at, here is the cost of each, and here is what I would do. Just need your yes.” You own one job: the decision.

    • 1. One issue. The decision that is actually needed, in one or two sentences. Not the whole story. The fork in the road.
    • 3. Three real options. Each with pros, cons, and a rough cost or effort. “Do nothing” can be one when it is honest. Stuck at two? Push for a third. Even “do nothing and revisit Friday” or “escalate to the carrier.”
    • 1. One recommendation. The option they would pick if it were their call, and why in one line.
    • A default. What they will do if they do not hear back by a deadline, so the job does not stall waiting on you.

    Explain the rule once, out loud. Pin the format where decisions get made (truck, office, group chat). When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait. Run at least five real conversations. Approve the recommendation whenever it is reasonable. Resist solving it yourself, even when you are faster. Note who takes to it quickly. That is a signal for a future-manager pick.

    The first few 1-3-1s will be lopsided. Three fake options, or a recommendation with no reasoning. Coach it. Do not grade it. Phase done when at least one person is bringing 1-3-1s without being reminded.

    Worksheet fields if you are copying it: prepared by, date, job / account, urgency (Today / This week / No rush); the issue; three options (what it is, two pros, two cons, rough cost); the recommendation and what they need from you; the default deadline; owner sign-off (Approved as recommended / Approved with changes / Chose a different option / Let’s talk).

    Owner gut-check before you sign: could this person have made this call without me? If yes, tell them so, and next time push it all the way down.

    3. 5 Ds Succession Risk Checklist

    Succession is not a retirement problem. It is a what-if-tomorrow problem. Check a box only if it is true and current today. Not “mostly.” Not “we talked about it once.” A box you want to be true is still a blank box. Half-true protections fail exactly when the D hits.

    1. Death. Current signed will that names the business. Funded buy-sell if there are partners. Key-person life payable to the company. A second check-signer on file at the bank. Someone who can legally bind the company. Passwords in a recoverable place. A named person who can run production 30+ days. Spouse / heirs know who to call.
    2. Divorce. Separate vs marital property actually confirmed, not guessed. Prenup, postnup, or buy-sell provision. Books not commingled. A valuation method in writing. Operating cash structured so a personal dispute cannot freeze payroll.
    3. Disease. Someone has actually run production on a vacation test. Backup estimator. Payroll / AP / AR without your hands. Carrier relationships that will not collapse if you are unreachable. Disability and business-overhead coverage. A one-page interim chain-of-command with dollar thresholds.
    4. Drugs / dependency. Dual approval over a dollar threshold. A second set of eyes on the books. No single point of failure, including you. A trusted advisor allowed to tell you the truth. Key roles documented and cross-covered.
    5. Departure / disaster. Tribal knowledge written down. Relationships not owned by one person. Off-site backups you have test-restored. A continuity plan for your own shop. Backup vendor / equipment list.

    Count the blanks. Published bands on the scored sheet: 0-6 resilient; 7-15 moderate; 16-27 high; 28+ you are the company. Pick the three blank boxes that would hurt most if the D hit tomorrow. Name an owner and a date. Re-run it every year, and after any life or business change. This is an awareness tool, not legal, financial, or insurance advice. Use it to walk into the attorney, agent, and CPA prepared.

    What to do after the three

    Take the top-3 bottleneck list into a 90-day doer-to-leader plan (Weeks 1-2 are this assessment). After 1-3-1 sticks, write decision rights so people stop defaulting to you out of habit. The 5 Ds blanks that are also “no backup” boxes on the bottleneck assessment are the same exposure. Name them once.

    If you want the next layer after this pack: Leadership Readiness Kit (checklist, scorecard, planner, 1-3-1) or Owner Freedom Kit (audit, bench, 90-day, 5 Ds, 1-3-1).

    If you want the packaged pack

    You can run the three tools from the outline above. Buy Now is the bundle delivered by email after checkout: the three Notion pages (duplicate each so the master stays clean), plus the matching skills if you want the interviews walked. Same Square button at the top of this page.

    Coaching and operational tools only. Not legal, financial, insurance, or HR advice.

  • Complete Restoration Operating System (Notion + AI)

    Complete Restoration Operating System (Notion + AI)

    $597

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Build the six Notion databases. Write the 17 SOPs. Hang the 12 KPIs. Talk your own Claude through intake, equipment, claims, and Friday numbers. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 8-skill plugin zip, so you are not wiring the system of record and the AI from a blank page.

    This is the Notion + AI operating system for a restoration shop. Notion is the system of record. The plugin is the expert you talk to. Outputs from each skill are formatted to paste into the matching Notion tool.

    What it is

    Two halves that are meant to run together.

    Notion half. Six plug-and-play tools plus an IICRC protocol lookup. Job tracking, equipment, claims, SOPs, KPIs, crew onboarding. Duplicate them into one workspace page named something like Operations. One sidebar section, whole business.

    AI half. An 8-skill Claude plugin. A setup skill runs a five-minute interview, writes a company-profile.md, and every other skill reads it. SOPs, KPI targets, claims drafts, and onboarding plans come out in your voice.

    You need a free Notion account and any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.

    The six Notion tools

    1. Restoration Job Tracker Pro. Every job from first notice of loss to final invoice, with live margin. This is the hub. Everything else hangs off jobs.
    2. Equipment Inventory & Deployment Tracker. Where every air mover and dehu is, and what each one is earning. Asset IDs, daily rates, current deployments.
    3. Insurance Claims Command Center. Claims, adjusters, documentation, supplements, and aging balances in one place.
    4. Restoration Company SOP Library (17 SOPs). The core procedures, written down. Status starts as Template. Flip to Adopted when you approve each one.
    5. Restoration Business KPI Dashboard. The 12 numbers that move profit. Friday 15 to update. One summary row on the first business day of the month.
    6. Crew Onboarding & Training Tracker. Roster, certifications with expiration dates, equipment sign-offs. Next hire, duplicate the checklist set.

    Plus IICRC Protocol Lookup. Ask “what does S500 say about Category 3 water?” and get a plain-English pointer plus PPE. It is a lookup assistant, not a substitute for the published standard. Defer to current IICRC text, local codes, and your certified judgment.

    The 17 SOPs to write (or adopt)

    If you are building this yourself, start a table with SOP #, title, category, owner role, linked standard, and status (Draft / In Review / Active / Needs Update). The kit’s 17 are:

    1. SOP-01 Water Damage: Initial Inspection & Scoping
    2. SOP-02 Water Extraction & Category Determination
    3. SOP-03 Structural Drying & Daily Monitoring / Psychrometry
    4. SOP-04 Antimicrobial Application
    5. SOP-05 Mold Remediation: Containment Setup
    6. SOP-06 Mold Remediation: Removal & Clearance
    7. SOP-07 Fire & Smoke: Soot Assessment & Cleaning
    8. SOP-08 Contents Pack-Out & Inventory
    9. SOP-09 Equipment Setup, Tracking & Retrieval
    10. SOP-10 PPE & Job-Site Safety
    11. SOP-11 Customer Communication & Daily Updates
    12. SOP-12 Photo Documentation & Moisture Logging
    13. SOP-13 Estimate Writing & Xactimate Scoping
    14. SOP-14 Insurance Adjuster Coordination & Supplements
    15. SOP-15 Job Completion, Walkthrough & Certificate of Satisfaction
    16. SOP-16 Invoicing & Collections
    17. SOP-17 New Job Intake / FNOL Handling

    Do not customize all 17 today. Adopt the water set first. The rest within the month. Swap in your company name, your equipment, your local disposal rules.

    The 12 KPIs

    Build a dashboard with KPI, category, definition, frequency, owner, target, this month, last month, trend. The kit tracks these twelve:

    • Revenue (Financial, monthly)
    • Gross Margin % (Financial, monthly, target ≥ 45%)
    • Net Profit % (Financial, monthly, target ≥ 12%)
    • Days Sales Outstanding / AR Aging (Financial, monthly, target ≤ 45 days)
    • Average Job Size (Financial, monthly)
    • Lead-to-Job Conversion % (Sales, weekly, target ≥ 35%)
    • Jobs Sold (Sales, weekly)
    • Average Days to Dry (Production, weekly, target ≤ 3.5 days)
    • Labor Efficiency % (Operations, weekly, target ≥ 70%)
    • Equipment Utilization % (Operations, weekly, target ≥ 60%)
    • Rework / Callback % (Customer, monthly, target ≤ 3%)
    • Customer Satisfaction / NPS (Customer, monthly, target ≥ 70)

    Those targets are the kit’s starting case file, not gospel. Mix of mitigation vs reconstruction will shift them. The habit is the product: fifteen minutes every Friday updating statuses.

    How to hang it yourself

    Set them up in this order. Each one feeds the next.

    1. Job Tracker (30-45 min). Add 2-3 active jobs. Real jobs, not test data. Log today’s moisture readings.
    2. Equipment Tracker (30-45 min). Every dehu, air mover, scrubber, and meter, with asset IDs. Set actual daily rates. Log where everything is deployed right now.
    3. Claims Command Center (20-30 min). Add adjusters first. Then a claim record for every active claim. Log outstanding supplements and unpaid balances.
    4. SOP Library (20 min now, ongoing after). Read, customize, flip Status to Adopted as you approve.
    5. Crew Tracker (20 min). Roster, certs, equipment sign-offs.
    6. KPI Dashboard (15 min, then 15 min every Friday). Enter this month’s jobs and leads, including the ones you lost.
    7. IICRC skill (5 min). Install, then ask something real: “Cat 2 toilet overflow into a carpeted hallway. What’s the protocol?”

    If a template ships with rows marked (Sample), keep them while you learn. Delete them once your real data is flowing.

    How the system runs day to day

    • Morning: Job Tracker board. What’s active, what needs a monitoring visit.
    • On every truck roll: equipment deployments updated; moisture readings logged to the job.
    • When the adjuster calls: Claims Command Center open. Every supplement, authorization, and dollar in front of you.
    • New hire starts: Crew Tracker checklist; SOP reading list; sign-offs gate the equipment.
    • Friday: the Friday 15 in the KPI ledger.
    • Month end: one KPI summary row. Review utilization before buying equipment.

    This does not replace JobNimbus, Encircle, or Xactimate. Those are job management, documenting, and estimating. This is the ops layer most shops never finish.

    The 8 AI skills

    1. restoration-setup. “Set up the kit.” Guided interview. First run. The concierge.
    2. job-intake-assistant. “We just got a water call.” New-loss intake, water Cat/Class, scope plus safety, a paste-ready job summary.
    3. equipment-advisor. “How many air movers for this room?” Sizing, placement, monitoring plan.
    4. sop-generator. “Write an SOP for mold containment.” Any of the 17, or a new one, in your voice.
    5. claims-assistant. “Draft a follow-up to the adjuster.” Emails, supplement justifications, aging-claims chase.
    6. kpi-coach. “Here are my numbers this month.” The 12 KPIs computed and trended. Biggest leak named, with fixes.
    7. crew-onboarding-builder. “Onboard a new tech.” Week-1 / 30 / 60 / 90 plus an IICRC certification roadmap.
    8. iicrc-protocol-lookup. “What does S500 say about Cat 3 water?” Plain-English pointer plus PPE.

    Install the plugin yourself

    Option A (recommended). Save the restoration-kit folder. In Claude run:

    /plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective
/restoration-kit:restoration-setup

    Option B. Copy each folder inside skills/ into ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then say “run restoration setup.”

    Keep company-profile.md in the folder you work in. Every skill reads it.

    If you want the packaged system

    You can rebuild this from the outline above. Buy Now is the flagship delivered by email after checkout: Notion duplicate links for the six tools plus IICRC lookup, the plugin zip (eight skills and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

    This is an operational system only. Not legal, insurance, or licensing advice.

  • Accountability Conversation Planner

    Accountability Conversation Planner

    $39

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Plan a hard conversation before you have it, so it stays about the work, not the person. Buy Now is the packaged Notion planner you duplicate for each talk, so you are not rebuilding the six prompts from a blank doc.

    Tool #4 of the Restoration Leadership Toolkit. Use this when an employee, manager, or family member in the business keeps missing the mark and you have been avoiding the talk. Ten minutes of prep keeps the conversation calm, specific, and fixable.

    Most restoration owners handle performance problems the same way. They tolerate underperformance for too long. They address it once, informally, in a conversation that does not result in change. They tolerate it some more. Then they either fire the person abruptly, often in response to a specific incident rather than the pattern, or they keep tolerating it because replacing people is painful. Neither outcome serves the business. The people who are performing well watch this and conclude that performance does not matter here.

    How to use it

    1. Duplicate a page so the blank stays clean for next time.
    2. Work through prompts 1 through 6 in order. Be specific. Vague prep makes for an emotional conversation.
    3. Draft your opening line and close from the script outline, then set a follow-up date.
    4. Keep your notes factual. This is a planning doc, not a personnel record. Log formal actions where your policies require.

    Fill the situation first: who this conversation is with; their role / relationship to the business; the date you plan to have it; where (private, not on the job site, not by text).

    You cannot hold someone accountable for expectations you have not communicated clearly. If the standard was never spelled out, that is on you to own in the room, and to fix going forward. Accountability without support is just pressure.

    The six prompts

    1. What is the actual issue?

    One or two sentences. The pattern, not a single bad day. Name the business impact: missed deadline, blown margin, safety, crew morale, a client complaint. Strip out the frustration and the personality read.

    Accountability is forward-looking: what went wrong, what is the standard, how do we close the gap? Blame is backward-looking and personal. Stay on the first one.

    2. What specific behavior needs to change?

    An observable action someone could see on a camera. “Calls in after the crew is already on site,” not “doesn’t care.” If you cannot point to the behavior, you are not ready to have the talk yet.

    “Do good work” is not an expectation. “Complete moisture documentation within 2 hours of equipment placement, using the standard form, with readings at all points on the moisture map” is an expectation. The more specific the expectation, the more possible accountability becomes.

    3. What have I already allowed or tolerated?

    Be honest. Where did I let this slide, stay quiet, or fix it myself instead of addressing it? Naming your part keeps the conversation fair and stops it from sounding like an ambush.

    The most powerful signal in any shop is what the leader does, not what the leader says. If you have been the one quietly finishing their job file, they learned the standard was optional.

    4. What expectation needs to be clarified?

    State the standard plainly, the way you would want it repeated back. “On site by 7:00, truck stocked the night before.” If this was never spelled out, own that in the room.

    For each role you eventually need written performance standards: output (what they produce), behavior (how they show up), and development (what they are working to improve). Share them at hire and review them at every performance discussion. The planner is the prep for one talk. The standards are what make the next talk shorter.

    5. What consequence or support is needed?

    Both sides. What changes if the behavior continues (the consequence) AND what you will provide to help them succeed (training, a checklist, a ride-along, clearer priorities).

    If doing good work and doing poor work produce the same outcome, the same pay, the same treatment, the same opportunities, there is no accountability mechanism. Consequences must exist and must be applied consistently. That cuts both ways: recognition for excellent work, and a real next step when the standard is missed.

    6. What does success look like in 30 days?

    Concrete and measurable, so you both know if it worked. “Zero late starts for four weeks.” “Job files closed within 48 hours.” This becomes the check-in agenda on the follow-up date.

    The longer the gap between a performance miss and the feedback, the weaker the feedback becomes. Address it in the moment or as soon as you can. Then put the 30-day target on a calendar so the talk is not a one-off.

    Conversation script outline

    Five beats. Keep it calm and short. Say your piece, then listen. Fill the blanks from your answers above.

    • Open (set the tone): “I want to talk through [issue] because I think you can do this well and I have not been clear. This is not about [personality].”
    • Name the issue + behavior (1 and 2): “What I am seeing is [behavior]. The impact on the business is [impact].”
    • Own my part (3): “I have let this go without saying anything, and that is on me. Clarifying now.”
    • State the expectation + support (4 and 5): “Going forward the standard is [standard]. To help, I will [support]. If it keeps happening, [consequence].”
    • Confirm the 30-day target + listen (6): “In 30 days, success looks like [target]. What is your take. What would help, and is any of this off?”

    Write their response under the script. Do not argue it in the room. Listen, then come back to the standard and the 30-day target.

    Follow-up

    • Follow-up check-in date
    • What I will look at on that date (from Prompt 6)
    • Outcome: On track / Needs another conversation / Resolved

    This planner is Weeks 9-10 of the 90-Day Doer-to-Leader Transition Plan: hold one real accountability conversation this phase, and have your developing manager run the huddle at least once while you sit in. A weekly 15-minute huddle with a fixed agenda (numbers, jobs at risk, who needs what) is the rhythm that makes the hard talk less of a surprise.

    A prompt you can give your own Claude if you want it walked: walk me through these six prompts for this specific situation and hand back a finished script and 30-day follow-up, in our company’s voice.

    If you want the packaged planner

    You can run the six prompts on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) for each conversation so the master stays clean. The situation block, the six prompts, the script outline, and the follow-up are already laid out. Same Square button at the top of this page.

    Pairs with the Leadership Readiness Checklist (does accountability live below you, or are you the only enforcer) and the 90-Day plan. Matching Claude skill: accountability-planner. Coaching and operational tool only. Not legal or HR advice. This is a planning doc, not a personnel record.

    Related: Restoration Leadership Toolkit — Claude Edition. Also 1-3-1 Delegation Worksheet.

  • 90-Day Doer-to-Leader Transition Plan

    90-Day Doer-to-Leader Transition Plan

    $199

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Run six two-week phases. By Week 12 the business runs a notch less on you and a notch more on your people. Buy Now is the packaged Notion plan you duplicate and date, so you are not assembling the 12-week spine from blank pages.

    The capstone of the Restoration Leadership Toolkit. This turns the doer-to-leader message into a plan you actually run. Work it top to bottom. Do not skip ahead. Each phase sets up the next. You cannot clarify decision rights (Weeks 5-6) until you know your bottlenecks (Weeks 1-2).

    How to use this plan

    • Duplicate a page and rename it “90-Day Plan – {start date}.”
    • Block 30-45 minutes every Friday to work the current phase and check boxes.
    • Start by running the Owner Bottleneck Self-Assessment and the Owner Dependency Audit. Their results feed Weeks 1-2 directly.
    • Fill the three setup lines before Week 1.

    Write these three lines now:

    • My #1 reason to step back (what I would do with the time)
    • The one person I am betting on as my first real manager
    • Start date / target Week-12 date

    Weeks 1-2. Identify your bottlenecks

    Goal: get brutally honest about where the company still runs through you. You cannot delegate what you have not named.

    1. Run the Owner Bottleneck Self-Assessment and write down your top 3 bottleneck areas.
    2. Run the Owner Dependency Audit. List every decision or task that only you can do today.
    3. For one full week, log every time someone interrupts you for a decision. A tally on your phone is fine.
    4. Sort that list into three buckets: Delegate now / Delegate after training / Keep (truly owner-only).
    5. Circle the top 3 bottlenecks that cost you the most time or money. These are your 90-day targets.
    6. Tell your team what you are doing and why: “I am working a 90-day plan to push decisions down. Expect me to hand more back to you.”

    Phase 1 done when you have a written top-3 bottleneck list and your team knows the shift is coming. The audit rates Low / Med / High across nine areas (sales, production, finance, customer-issue resolution, hiring, vendor relationships, estimating / project management, emergency response, decision rights). Low = 1, Med = 2, High = 3. Total is 9-27.

    Weeks 3-4. Install 1-3-1 conversations

    Goal: stop being the answer key. Train the team to bring one issue, three options, and one recommendation, so you coach instead of solve.

    1. Explain the 1-3-1 rule to the team: bring 1 issue, 3 options, 1 recommendation. Not just the problem.
    2. Print or pin the 1-3-1 format where decisions get made (truck, office, group chat).
    3. When someone brings you a raw problem, ask: “What are your three options, and which do you recommend?” Then wait.
    4. Run at least 5 real 1-3-1 conversations this phase and approve their recommendation whenever it is reasonable.
    5. Resist solving it yourself, even when you are faster. Let them carry it. This is the hard part.
    6. Note who takes to it quickly. That is a signal for your future-manager pick in Weeks 7-8.

    Phase 2 done when at least one person is bringing you 1-3-1s without being reminded. One issue, three real options (pros, cons, rough cost), one recommendation, and a default if they do not hear back by a deadline.

    Weeks 5-6. Clarify decision rights

    Goal: write down who decides what, and up to what dollar amount, so people stop defaulting to you out of habit.

    1. List the 10-15 recurring decisions your team faces (refunds, equipment, scheduling, scope changes, hiring, pricing exceptions).
    2. For each, write a dollar or scope threshold people can decide under without asking you.
    3. For each, name who owns it when you are not in the room.
    4. Capture it in one simple Decision Rights list (a shared doc or a section on the plan page).
    5. Walk the team through it and tell them: “Under this line, you do not need me. Decide and tell me after.”
    6. Pick one decision you currently own and hand it off completely this phase. Do not take it back.

    Phase 3 done when there is a written decision-rights list and at least one decision has fully left your plate. Starter rows live on the Owner Dependency Audit if you need them.

    Weeks 7-8. Develop one manager

    Goal: go deep on ONE person. A single real manager beats five people you are “keeping an eye on.”

    1. Choose one person to invest in as your first real manager. Use the Middle Manager Evaluation Scorecard if you are torn.
    2. Have a direct conversation: “I want to grow you into running X. Here is what that looks like.”
    3. Hand them one area to own end-to-end (a crew, a job type, scheduling, QC). Outcome, not task.
    4. Set a weekly 30-minute 1-on-1 with them and protect it like a paying job.
    5. Name the 1-2 skills they most need to build and how you will help (ride-along, training, a stretch job).
    6. Let them make a real decision this phase and coach the outcome instead of grading it.

    Open a bench list while you do this. One row per key function: role, current owner, candidate, backup depth, skill gaps, one observable 90-day action, delegation plan, check-in rhythm, status. A blank candidate is itself a finding. Phase 4 done when one person owns one area end-to-end and has a standing 1-on-1 with you.

    Weeks 9-10. Create an accountability rhythm

    Goal: replace you-chasing-everyone with a repeatable cadence that surfaces problems early, without you in the middle of every thread.

    1. Stand up a weekly 15-minute team huddle with a fixed agenda: numbers, jobs at risk, who needs what.
    2. Pick the 3-5 numbers the team reviews every week (jobs in WIP, days-to-dry, AR, callbacks, leads).
    3. Decide who owns each number and reports it. Not you.
    4. Use the Accountability Conversation Planner to prep any hard conversation so it stays about the work, not the person.
    5. Hold one real accountability conversation this phase using that structure.
    6. Have your Week 7-8 manager run the huddle at least once while you sit in and observe.

    Phase 5 done when the weekly huddle runs on schedule and someone other than you can run it. About the work, not the person.

    Weeks 11-12. Review, adjust, and repeat

    Goal: measure what changed, lock in the wins, and set the next 90 days. This is not the end. It is the first turn of the flywheel.

    1. Re-run the Owner Bottleneck Self-Assessment and compare to your Week 1 score.
    2. Take a planned half-day fully off and note what broke or escalated to you. That is your next bottleneck.
    3. List what got delegated successfully vs what bounced back to you, and why it bounced.
    4. Give your developing manager direct feedback on the quarter and agree on next-quarter goals.
    5. Update your Decision Rights list and raise one threshold now that the team has proven itself.
    6. Pick next quarter’s top bottleneck and start a fresh 90-day cycle (duplicate the page again).

    Phase 6 done when you have re-scored, taken real time off, and named the next quarter’s target.

    Success looks like

    By the end of 90 days, a healthy transition looks like:

    • You can take a full day off without the business stalling or your phone melting.
    • Your team brings you 1-3-1 recommendations, not raw problems to solve.
    • There is a written decision-rights list, and people decide under the line without asking.
    • One person owns one area end-to-end and has a standing 1-on-1 with you.
    • A weekly huddle runs on cadence, and someone other than you can run it.
    • Your re-scored bottleneck number is lower than it was in Week 1.
    • You have already named next quarter’s target, because doer-to-leader is a flywheel, not a finish line.

    Not every box will be checked, and that is fine. Progress on the top-3 bottlenecks matters more than a perfect scorecard. Run it, adjust, repeat.

    While you are in it, run the 5 Ds as a what-if-tomorrow check. Pick the three blank boxes that would hurt most if the D hit tomorrow.

    If you want the packaged plan

    You can run the six phases from the outline above. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) and rename it with the start date so the master stays clean. The setup lines, the phase checkboxes, and the success list are already laid out. Same Square button at the top of this page.

    The other four tools in the Owner Freedom Kit feed this spine: Owner Dependency Audit, Restoration Leadership Bench Builder, 5 Ds Succession Risk Checklist, 1-3-1 Delegation Worksheet. Matching Claude skill: doer-to-leader-90-day. Coaching and operational tool only. Not legal or HR advice.

    Related: Restoration Leadership Toolkit — Claude Edition. Also Owner Bottleneck Self-Assessment.

  • 5 Ds Succession Risk Checklist

    5 Ds Succession Risk Checklist

    $29

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Stress-test the company against Death, Divorce, Disease, Drugs/dependency, and Departure/Disaster. Check a box only if it is true and current today. Buy Now is the packaged Notion checklist with the scored sheet and mitigation notes, so you are not rebuilding the 5 Ds from a blank doc.

    Succession is not a retirement problem. It is a what-if-tomorrow problem. The blank boxes are your exposure. Honesty rule: a box you want to be true is still a blank box. Half-true protections fail exactly when the D hits.

    How to run it

    1. Walk each of the 5 Ds. Check a box only if it is true and current today. Not “mostly.” Not “we talked about it once.”
    2. Read the mitigation note under each D. That is the concrete fix for the boxes you left blank.
    3. Count the blanks. Find your band. Pick your top 3 shore-ups. Name an owner and a date.
    4. Re-run it every year, and immediately after any life or business change: a new partner, a marriage or divorce, a major new account, an acquisition, or a health scare.

    1. Death. If you died tomorrow

    If you were gone permanently, could the business survive the week, pay people, and not get sold for scraps?

    • There is a current, signed will and the business is named in it.
    • There is a buy-sell agreement (if there are partners) defining who buys your share, at what price, and how it is funded.
    • Key-person life insurance exists on you, payable to the company, sized to cover payroll plus obligations while it stabilizes.
    • At least one other person can sign checks (signatory on file at the bank, not just “knows the login”).
    • Someone other than you can legally bind the company (contracts, AOBs, subcontracts). Documented authority, not assumed.
    • Your spouse / heirs know who to call and where the documents live.
    • Passwords, accounts, and licenses are in a recoverable place a trusted person can reach.
    • A named person can run production and keep jobs moving for 30+ days without you.

    Mitigation. Get a buy-sell drafted by an attorney and fund it with life insurance. An unfunded buy-sell is a wish, not a plan. Add a second check-signer and a documented officer who can bind the company. Put credentials in a password manager with an emergency-access contact. Write a one-page “if I am gone” sheet. Tell your spouse where it is.

    2. Divorce. If your marriage ended

    A divorce can put your ownership stake, your cash, and your focus in play. A contested split can starve a cash-hungry shop.

    • You know whether the business is separate vs marital/community property in your state. Confirmed, not guessed.
    • There is a prenup, postnup, or buy-sell provision that addresses ownership in a divorce.
    • The business is not commingled with personal finances (clean books, separate accounts, documented owner pay).
    • A current, defensible valuation (or a method to set one) exists.
    • Your spouse’s role and any claim (employee, owner-on-paper, guarantor) is documented.
    • Operating cash and credit lines are structured so a personal dispute cannot freeze payroll.

    Mitigation. Talk to a business attorney about a postnuptial or a buy-sell clause that fixes ownership treatment now, while things are calm. Clean up commingling. Establish a valuation method in writing. Calm is the only time you can do it.

    3. Disease. If you were medically out for 30-90 days

    Not death. A heart attack, a serious diagnosis, a bad accident. You are alive but out. Does the company idle or run?

    • Someone can run daily production and dispatch without you for 30, 60, 90 days. Named, and they have actually done it (vacation test).
    • Estimates still get written and approved if you are the estimator. A backup exists.
    • Payroll, AP, and AR keep running without your hands on them.
    • Carrier / TPA relationships will not collapse if you are unreachable. Someone else has the relationships and portal access.
    • You carry disability income insurance so household income does not depend on you working.
    • Business overhead expense (BOE) insurance or a cash reserve can cover fixed costs while you recover.
    • A simple interim chain-of-command is written down, with dollar/decision thresholds.

    Mitigation. Run a real “two weeks off” test this quarter and watch what breaks. Cross-train a backup estimator. Look at disability and Business Overhead Expense coverage. Write a one-page interim chain-of-command with decision thresholds.

    4. Drugs / dependency. If you (or a key person) became unreliable

    The uncomfortable one. Substance issues, gambling, burnout, a mental-health crisis. Yours or a key person’s. The risk is a slow decline, not a clean exit.

    • No single person (including you) is a single point of failure whose impairment would quietly sink the company.
    • Financial controls exist (dual approval over a threshold, reconciliations, a second set of eyes on the books).
    • A trusted advisor or peer would tell you the truth if your performance was slipping, and has standing to.
    • Key roles have documented duties and cross-coverage.
    • There is an employee assistance path / clear policy for getting a valued person help without an instant, messy termination.
    • If a key person had to be removed fast, you could. Access and knowledge are not locked solely in their head.

    Mitigation. Dual approval over a dollar threshold, monthly reconciliations, a second set of eyes on the books. Document and cross-train so no one person can sink a function. Put a real advisor in your corner who is allowed to tell you the truth. Have a humane path to help and the access to act fast if you must.

    5. Departure / disaster. If a key person walked, or the building burned

    Two faces of the same risk: a critical person quits, or a fire/flood/storm/cyber event takes out your office, fleet, data, or a major account overnight.

    • Production runs if your best PM or lead tech quits Friday. Their knowledge is documented, not tribal.
    • Key customer and carrier relationships are not owned by one person who could walk and take the book with them.
    • A non-solicit / non-compete / confidentiality agreement is in place where appropriate and enforceable in your state.
    • Critical SOPs, pricing, and account knowledge are written down. Losing one person does not erase how the work gets done.
    • Data is backed up off-site (estimating files, photos, accounting, contacts) and you have actually tested a restore.
    • You have a business continuity / disaster plan for your own office or fleet. You restore others. Are you covered?
    • Business-interruption insurance would replace income if you could not operate for weeks.
    • A backup vendor/equipment plan exists so one lost truck, warehouse, or sub does not stall live jobs.

    Mitigation. Document tribal knowledge. Spread customer and carrier relationships across more than one person. Put reasonable non-solicit/confidentiality agreements in place (attorney confirms enforceability in your state). For disaster: off-site backups you have test-restored, a written continuity plan for your own shop, business-interruption coverage, and a backup equipment/vendor list.

    Overall exposure rating

    Count your blank boxes across all 5 Ds. The packaged checklist scores 45 boxes. Find your band:

    • 0-6 Low / Resilient. The business could survive a major shock to you. Maintain it. Review annually and after any big change.
    • 7-15 Moderate. You would survive a short absence but a permanent loss would hurt. Close the highest-stakes gaps (Death + Disease) first.
    • 16-27 High. A 30-day absence would seriously disrupt the company. A permanent loss could end it. Treat this as a current-quarter priority.
    • 28+ Critical / You are the company. If something happened to you tomorrow, the business likely does not survive intact. Start the top-3 shore-ups this week.

    Write three lines: blank-box total, exposure band, and which D scored worst.

    Top 3 shore-ups

    Pick the three blank boxes that would hurt most if the D hit tomorrow. Be specific. Name an owner. Set a date.

    Most shore-ups need one of these professionals: a business / estate attorney (buy-sell, will, non-competes, postnup); an insurance agent (key-person life, disability, BOE, business-interruption); a CPA / financial advisor (valuation, financial controls, continuity reserve).

    This is an awareness and planning tool, not legal, financial, or insurance advice. Use it to find your gaps and to walk into the attorney, agent, and CPA prepared.

    If you want the packaged checklist

    You can run the five lists on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) so the master stays clean. The boxes, the mitigation notes, the score table, and the top-3 shore-ups are already laid out. Same Square button at the top of this page.

    Pairs with the Owner Dependency Audit (what breaks if you vanish 30 days) and the Restoration Leadership Bench Builder (who can run production when a D hits). Matching Claude skill: succession-5ds-checklist.

    Related: Restoration Leadership Toolkit — Claude Edition. Also 90-Day Doer-to-Leader Transition Plan.

  • 1-3-1 Delegation Worksheet

    1-3-1 Delegation Worksheet

    $19

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Teach the team to bring one issue, three options, and one recommendation instead of a raw problem. Buy Now is the packaged Notion worksheet you duplicate for every decision they hand up, so you are not rebuilding the form from a blank doc.

    Tool 1 of the Restoration Leadership Toolkit. The line is: stop bringing me problems. Start bringing me decisions. The 1-3-1 method trains your people to think like owners. You keep one job: approve, tweak, or redirect.

    The old way vs the 1-3-1 way

    The old way (escalation): “Hey boss, the dehu on the Maple St job died. What do you want me to do?” You just took back the problem, the thinking, and the decision. That is three jobs.

    The 1-3-1 way (delegation): “The dehu on Maple St died. Here are three options I looked at, here is the cost of each, and here is what I would do. Just need your yes.” You own one job: the decision.

    The rule

    • 1. One issue. State the decision that is actually needed, in one or two sentences. Not the whole story. The fork in the road.
    • 3. Three real options. Three things you could actually do. Each with pros, cons, and a rough cost or effort. “Do nothing” can be one of the three when it is honest.
    • 1. One recommendation. The option they would pick if it were their call, and why in one line.
    • A default. What they will do on their own if they do not hear back by a deadline, so the job does not stall waiting on you.

    Stuck at two options? Push for a third. Even “do nothing and revisit Friday” or “escalate to the carrier.” A real third option is where the good thinking usually hides.

    How to install it

    1. Explain the rule to the team once, out loud. Pin the format where decisions get made: truck, office, group chat.
    2. When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait.
    3. Run at least five real 1-3-1 conversations before you decide it “isn’t working.” Approve the recommendation whenever it is reasonable.
    4. Resist solving it yourself, even when you are faster. Let them carry it. That is the hard part.
    5. Note who takes to it quickly. That is a signal for your future-manager pick.

    The first few times, the 1-3-1s will be lopsided. Three fake options, or a recommendation with no reasoning. Coach it. Do not grade it. The goal is a team that brings you thinking, not just questions. Phase done when at least one person is bringing 1-3-1s without being reminded.

    The worksheet (copy this)

    Duplicate a page or print a half-sheet for every decision that gets handed up. Fill it in this order.

    Who and when

    • Prepared by
    • Date
    • Job / account (if any)
    • How urgent: Today / This week / No rush

    1. The issue / decision needed

    One or two sentences. What decision are we actually making? Why does it need a decision now? Then one more line: what happens if we do nothing / decide nothing?

    3. The three options

    For each option write four lines:

    • What it is
    • Pros (two bullets)
    • Cons (two bullets)
    • Rough cost / effort

    1. My recommendation

    I recommend Option __. Why (one or two lines). What I need from you: a yes / a budget approval / a different call / a quick conversation.

    What I will do if I do not hear back

    • If I do not hear back by: (date / time)
    • I will go ahead and: (the default)
    • Owner is OK with me proceeding this way unless they say otherwise

    Owner decision / sign-off

    • Approved as recommended / Approved with changes / Chose a different option / Let’s talk
    • If changed, what
    • Any conditions or budget cap
    • Owner name and date

    Owner gut-check before you sign

    Could this person have made this call without me? If yes, tell them so, and next time push it all the way down to them. That is how the bottleneck clears.

    This worksheet is Weeks 3-4 of the 90-Day Doer-to-Leader Transition Plan. After it sticks, write decision rights (who decides what, up to what dollar amount) so people stop defaulting to you out of habit. Hand off one decision completely and do not take it back.

    A prompt you can give your own Claude if you want it walked: convert this escalated question into one issue, three options with pros/cons/cost, one recommendation, and a default if I do not answer by a deadline.

    If you want the packaged worksheet

    You can run 1-3-1 on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) for every decision so the master stays clean. The fields, the option tables, the default, and the sign-off are already laid out. Same Square button at the top of this page.

    Pairs with the 90-Day Doer-to-Leader Transition Plan (Weeks 3-4) and the Owner Dependency Audit when you are ready to map who should decide. Matching Claude skill: delegation-1-3-1. Coaching aid, not legal or HR advice.

    Related: Restoration Leadership Toolkit — Claude Edition. Also Owner Bottleneck Self-Assessment.

  • AI Agents Are Learning to Check Instead of Guess: The GitHub Context Problem

    AI Agents Are Learning to Check Instead of Guess: The GitHub Context Problem

    Most AI assistants still answer from memory. Ask one a question and it reasons from patterns baked in during training — useful, but static. The moment a question depends on something that changed yesterday, or something that only exists inside your own systems, that static knowledge runs out.

    The more interesting shift happening in AI tooling right now isn’t bigger models — it’s agents that can actually go check. Dispatch-style AI systems, the kind that can spin off an isolated task, open a real shell, browse a real page, or read an actual file, are starting to close the gap between “the AI’s best guess” and “what’s actually true right now.” GitHub is a good test case for why that distinction matters.

    Search-and-cite isn’t the same as read-and-act

    A lot of what gets marketed as an AI “GitHub integration” is really a search layer: the assistant can look up an issue or a pull request and summarize it, with a citation back to the source. That’s genuinely useful for answering “what did that PR change” — but it’s a dead end the moment you need the assistant to actually do something, like open an issue, comment, or verify what a repository’s current state really is.

    The more capable version of this connects an agent directly to real developer tooling: an actual shell, a real git client, real file access. Instead of summarizing a cached snapshot of a repo, the agent can clone it, read the current commit log, open the actual config files, and answer questions against what’s genuinely there today — including the uncomfortable cases, like when the live state doesn’t match what anyone assumed it would.

    Why “just check” is harder than it sounds

    The obvious rebuttal is: shouldn’t a good assistant just check before it answers? In practice, most AI tools default to answering from what they already “know,” because checking is slower and requires actual tool access, not just a knowledge base. The systems that skip the check tend to produce confident, plausible-sounding answers that are quietly wrong the moment reality has drifted from training data — a stale API, a renamed config path, a repo that moved.

    The fix isn’t a smarter model. It’s an agent willing to spend the extra step: open the real file, run the real command, read the real log, before saying anything with confidence. That habit is unglamorous, but it’s the difference between an assistant that sounds right and one that actually is.

    The practical takeaway

    For any business layering AI into real workflows, the question worth asking about a tool isn’t just “how smart is the model” — it’s “what can this thing actually go look at, and will it bother to.” An assistant that can search and summarize is a research aid. One that can open a shell, read your actual repository, and ground its answer in what’s really there is a different category of tool entirely — and it’s the direction the whole space is quietly moving.

  • Logic Apps vs Cloud Workflows: No-Code Automation Across Two Clouds

    Logic Apps vs Cloud Workflows: No-Code Automation Across Two Clouds

    Every content operation runs on small invisible chains of “when this happens, do that.” Publish an article → notify a channel → write a row to the ledger. None of it is hard, but you don’t want to babysit a script for it — you want a managed orchestrator that fires on an event, calls a few services, and logs the result, for free. Azure and Google each have one, and they take opposite philosophies to the same job.

    We wire the same publish → notify → log automation on both Azure Logic Apps and Google Cloud Workflows, on the free tiers, and compare. Short answer: Logic Apps wins when the work is gluing SaaS services together — its connector library and visual designer are unmatched, with a free grant of 4,000 built-in actions/month. Cloud Workflows wins when the work is lightweight, code-first orchestration inside GCP — its 5,000 internal + 2,000 external steps/month free tier pairs cleanly with Eventarc and Pub/Sub. One is a no-code SaaS glue gun; the other is a YAML orchestration engine.

    This is the breakdown from the running lab on tygart.media — connector ecosystems, visual designer vs YAML, triggers, and free ceilings.

    The free-tier ceilings

    How we do it

    Azure Google Cloud Verdict
    Free grant/month 4,000 built-in actions 5,000 internal + 2,000 external steps Comparable, units differ
    Billing model Per-action (Consumption) Per-step (internal vs external) Different mental models
    What counts Each connector/built-in action Each workflow step executed Tie at our volume
    Fit for a glue chain Generous Generous Tie
    Our actual bill $0 $0 Tie where it counts

    Both free grants comfortably cover a real automation cadence. A publish → notify → log chain is three or four actions/steps per run; at a few publishes a day, neither 4,000 actions nor 7,000 steps comes close to binding. The units differ — Azure counts actions, Workflows splits internal vs external steps (external = calls out to other services, which are scarcer) — but for our workload both run free.

    Connectors vs code-first

    This is the real fork in the road, and it decides the choice.

    How we do it

    Azure Google Cloud Verdict
    Connector library Hundreds (SaaS + Microsoft + 3rd-party) HTTP + GCP services, no big SaaS catalog Logic Apps, decisively
    Authoring model Visual designer (drag-and-drop) YAML (code-first) Logic Apps for no-code
    SaaS glue (Slack, email, etc.) Native connectors, prebuilt auth Roll your own via HTTP Logic Apps
    GCP-native orchestration Possible via HTTP First-class Cloud Workflows
    Versioning / review in git Exportable, but designer-first YAML lives in git naturally Cloud Workflows

    Logic Apps’ superpower is its connector library — hundreds of prebuilt, pre-authenticated connectors for Slack, Office, Salesforce, Twitter/X, databases, and most SaaS you’d name. Wiring “post to Slack when an article publishes” is point-and-click, with the OAuth handled for you. Cloud Workflows takes the opposite stance: it’s code-first YAML with no big SaaS catalog — you orchestrate GCP services and arbitrary HTTP endpoints, building any integration you need by hand. That’s less convenient for SaaS glue but cleaner for engineers who want their orchestration in git, reviewed like code.

    Triggers and event sources

    How we do it

    Azure Google Cloud Verdict
    Native triggers Many (HTTP, schedule, connector events) HTTP + Eventarc/Pub/Sub Logic Apps on built-in variety
    Event-driven on cloud events Via Event Grid Via Eventarc (first-class) Cloud Workflows for GCP events
    Schedule / cron Built-in recurrence Cloud Scheduler Tie
    SaaS event triggers Connector-based, prebuilt Roll your own Logic Apps
    Pub/Sub-style fan-out Event Grid Pub/Sub (native pairing) Cloud Workflows in GCP

    Logic Apps can be triggered by connector events directly — “when a new email arrives,” “when a row is added” — which keeps SaaS-driven automations entirely no-code. Cloud Workflows leans on Eventarc and Pub/Sub for event sources, which is the idiomatic, powerful path if your events originate in GCP. Each is strongest for events native to its own cloud.

    What surprised us

    • Logic Apps’ connector library is the whole ballgame for SaaS glue. Pre-authenticated connectors turned a “write a small integration” task into a five-minute drag-and-drop. Nothing on the GCP side matches that catalog.
    • Cloud Workflows’ YAML-in-git is quietly the better engineering experience. When the orchestration lives in the repo and gets code-reviewed, it stops being a clickable black box. We liked that more than expected.
    • The free grants are both ample. We worried about per-action metering and never came near either ceiling at a realistic publishing cadence.
    • External steps are the scarce currency on GCP. Workflows’ 2,000 external steps (calls out to other services) is the limit to watch, not the 5,000 internal steps.

    The takeaway

    Pick Azure Logic Apps if your automation is mostly gluing SaaS services together — Slack, email, CRMs, Microsoft 365 — and you want a visual, no-code designer with hundreds of pre-authenticated connectors. It’s the fastest path from “I wish X notified Y” to a running flow.

    Pick Google Cloud Workflows if your automation is lightweight orchestration inside GCP — coordinating Cloud Run, Functions, Pub/Sub, and HTTP endpoints — and you want it defined as code-first YAML that lives in git and pairs with Eventarc. It’s the cleaner engineering primitive when the events and services are already on Google’s side.

    For our publish → notify → log chain, the deciding factor is where the notify lands: a Slack or email notification leans Logic Apps for the free connector; a fan-out into Cloud Run or Pub/Sub leans Workflows. Running the same chain on both made the connector-vs-code-first trade concrete.

    This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, wiring the same automation on each to see which orchestrator fits which job. The lab lives on tygart.media; the findings publish here.

    Frequently asked questions

    What’s the free tier for Azure Logic Apps and Google Cloud Workflows?
    Azure Logic Apps (Consumption) includes a free grant of 4,000 built-in actions per month. Google Cloud Workflows includes 5,000 internal steps and 2,000 external steps per month free. Both comfortably cover a realistic automation cadence, so a small glue chain runs at $0 on either.

    Which is better for no-code automation, Logic Apps or Cloud Workflows?
    Logic Apps is the no-code choice — it has a visual drag-and-drop designer and hundreds of pre-authenticated connectors for SaaS services. Cloud Workflows is code-first YAML with no big SaaS catalog, so it suits engineers orchestrating GCP services rather than non-developers gluing apps together.

    Does Cloud Workflows have a connector library like Logic Apps?
    No. Cloud Workflows orchestrates GCP services and arbitrary HTTP endpoints, but it has no large prebuilt SaaS connector catalog the way Logic Apps does. To integrate a third-party SaaS in Workflows, you call its HTTP API and handle authentication yourself, whereas Logic Apps provides a ready-made connector.

    How do I trigger automation when an article is published?
    On Azure, a Logic App can be triggered by an HTTP request, a schedule, or a connector event, then call further connectors with no code. On Google Cloud, a Workflow is typically triggered via Eventarc or Pub/Sub for cloud-native events, or by HTTP. Each is strongest for events that originate inside its own cloud.

    Which is better for gluing SaaS and cloud events together?
    Logic Apps wins for SaaS glue thanks to its connector library and visual designer, making things like “notify Slack when X happens” nearly code-free. Cloud Workflows wins for lightweight, code-first orchestration of GCP services that lives in git and pairs with Eventarc and Pub/Sub. Pick by where your events and services already live.

  • Azure Static Web Apps vs Firebase Hosting: A Dashboard on Each

    Azure Static Web Apps vs Firebase Hosting: A Dashboard on Each

    A static front-end — an internal dashboard, a docs site, a landing page — is the most thankless thing to host badly and the most satisfying thing to host well. You want a global CDN, free SSL, a custom domain, and CI/CD that redeploys when you push, all without standing up a server or paying a cent. Both Azure and Google have a purpose-built free product for exactly this, and they’re both genuinely excellent.

    We host the same internal dashboard on both Azure Static Web Apps and Firebase Hosting, on the free tiers, and compare. Short answer: this is a toss-up — both are excellent, pick by ecosystem. Azure Static Web Apps free tier gives you 100 GB of bandwidth, 2 custom domains, 0.5 GB per app, free managed SSL, and built-in CI/CD straight from GitHub. Firebase Hosting’s free Spark plan gives you 10 GB of storage, 360 MB/day of transfer, free SSL, and custom domains. The right answer is whichever cloud your other services already live in.

    This is the breakdown from the running lab on tygart.media — bandwidth and limits, CI/CD, auth and functions integration, custom domains, and the CDN.

    The free-tier ceilings

    How we do it

    Azure Google Cloud Verdict
    Free bandwidth 100 GB total 360 MB/day (~10 GB/mo) transfer Azure on raw monthly headroom
    Free storage per app 0.5 GB 10 GB Firebase on storage
    Custom domains (free) 2 Multiple supported Firebase, slightly
    Free managed SSL Yes Yes Tie
    Built-in CI/CD Yes (GitHub Actions wired automatically) Yes (Firebase CLI / GitHub Action) Azure, slightly more turnkey

    The numbers favor different things. Azure leads on monthly bandwidth — 100 GB is a lot of dashboard traffic — while Firebase leads on storage, with 10 GB versus Azure’s 0.5 GB per app. For an internal dashboard, neither limit is close to binding: the assets are small and the audience is a handful of people. Firebase’s 360 MB/day transfer cap is the one to watch only if a dashboard goes unexpectedly viral, which an internal tool won’t.

    CI/CD, auth, and functions

    This is where “static hosting” stops being just a CDN and starts being a platform.

    How we do it

    Azure Google Cloud Verdict
    Deploy on git push Auto-wired GitHub Actions Firebase CLI or GitHub Action Azure on zero-config setup
    Built-in auth Yes (Entra, GitHub, social — built in) Via Firebase Authentication Azure for bundled, Firebase for depth
    Serverless functions Built-in Azure Functions integration Cloud Functions / pairs naturally Tie — both have a backend path
    Staging environments Free preview environments per PR Preview channels Tie
    Setup friction Connect repo, done CLI init, done Azure, slightly

    Azure Static Web Apps’ standout is how much it bundles by default: connect a GitHub repo and it writes the Actions workflow for you, provisions preview environments per pull request, and offers built-in authentication (Entra, GitHub, and social providers) without you wiring an auth service. Firebase matches the capability but composes it from named products — Firebase Authentication and Cloud Functions — which is more à la carte and, if you’re already deep in Firebase, more powerful and familiar.

    Custom domains and the CDN

    How we do it

    Azure Google Cloud Verdict
    Custom domain setup 2 free, managed cert Add domain, managed cert Tie
    Global CDN Yes, included Yes, included (Fastly-backed) Tie
    Cache control Configurable Configurable Tie
    TTFB at our scale Fast Fast Tie

    Both put your dashboard behind a real global CDN with automatic SSL on a custom domain, and at our scale the time-to-first-byte was indistinguishable. This part is genuinely a wash — both clouds have solved static delivery.

    What surprised us

    • Azure’s per-PR preview environments are a delight. Open a pull request and you get a live URL of that exact change, free, with no setup. For reviewing dashboard tweaks it’s better than we expected.
    • Firebase’s storage allowance is the bigger one. 10 GB versus 0.5 GB sounds dramatic, but for a static front-end neither limit matters — the assets are tiny.
    • Azure’s built-in auth saved real work. Adding GitHub login to an internal dashboard was nearly free of code on Azure; on Firebase it meant wiring Firebase Authentication, which is more capable but more steps.
    • The hosting itself is a non-event on both. Push, it’s live, it’s fast, it’s free. That’s the whole experience — exactly as it should be.

    The takeaway

    Pick Azure Static Web Apps if you want the most bundled experience — auto-wired GitHub CI/CD, free per-PR preview environments, and built-in authentication — and your stack already leans Microsoft. The 100 GB bandwidth is generous for any internal tool.

    Pick Firebase Hosting if you’re already in the Firebase/Google ecosystem and want its deeper, composable Authentication and Cloud Functions, or you value the larger 10 GB storage allowance. It pairs naturally with the rest of Firebase.

    Honestly, for a static dashboard you can’t go wrong. We run the dashboard on whichever cloud hosts the data and functions behind it — co-location beats cleverness. Both deliver the dashboard fast, on a custom domain, with free SSL, at $0.

    This is part of our “Two Clouds, One Site” series — we run the same media property on both Azure and Google Cloud on the free tiers, hosting the same dashboard on each to feel where the platforms differ. The lab lives on tygart.media; the findings publish here.

    Frequently asked questions

    What do the free tiers of Azure Static Web Apps and Firebase Hosting include?
    Azure Static Web Apps’ free tier includes 100 GB of bandwidth, 2 custom domains, 0.5 GB of storage per app, free managed SSL, and built-in GitHub CI/CD. Firebase Hosting’s free Spark plan includes 10 GB of storage, 360 MB/day of transfer, free SSL, and custom domains. Azure leads on bandwidth; Firebase leads on storage.

    Which is better for hosting a static site or dashboard for free?
    Both are excellent and the choice comes down to ecosystem. Azure Static Web Apps bundles more by default — auto-wired CI/CD, per-PR preview environments, and built-in authentication. Firebase Hosting pairs naturally with Firebase Authentication and Cloud Functions and offers more free storage. Pick the one matching the rest of your stack.

    Does Azure Static Web Apps include built-in authentication?
    Yes. Azure Static Web Apps offers built-in authentication with Entra ID, GitHub, and social providers without wiring a separate auth service, which makes adding login to an internal dashboard nearly code-free. Firebase achieves the same through Firebase Authentication, which is more capable but takes more setup.

    Do both Azure Static Web Apps and Firebase Hosting give free SSL and custom domains?
    Yes. Both provide free managed SSL certificates and support custom domains on the free tier — Azure includes 2 custom domains, and Firebase supports adding custom domains with managed certificates. Both also put your site behind a global CDN at no cost.

    Will I hit the free hosting limits with an internal dashboard?
    Almost certainly not. An internal dashboard serves small assets to a few people, so neither Azure’s 100 GB bandwidth nor Firebase’s 360 MB/day transfer comes close to binding. Firebase’s daily transfer cap would only matter if a public site went unexpectedly viral.