Tag: AI Operations

  • Restoration Operations Kit — Claude Edition

    Restoration Operations Kit — Claude Edition

    Restoration Operations Kit — Claude Edition

    $197

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Talk to your own Claude. Interview your own shop. Write your own SOPs and claims drafts. Buy Now is the packaged zip: eight skills, the plugin files, and the install so you do not have to wire it from scratch.

    This is the AI companion to the Complete Restoration Operations Kit. A restoration owner attaches it to their own Claude. It interviews them, writes a company profile, and then the other skills speak that business.

    What it is

    An 8-skill Claude plugin. Install it into Claude Code, the Claude Desktop app, or Cowork. 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, not a generic restoration voice.

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

    The 8 skills

    1. restoration-setup. Say “Set up the kit.” Guided interview that customizes the whole kit. First run. The concierge.
    2. job-intake-assistant. Say “We just got a water call.” New-loss intake, water Cat/Class classification, scope plus safety, a paste-ready job summary.
    3. equipment-advisor. Say “How many air movers for this room?” Air-mover and dehu sizing, placement, and a monitoring plan.
    4. sop-generator. Say “Write an SOP for mold containment.” A tailored SOP in your company’s voice. Any of the 17 core SOPs, or a new one.
    5. claims-assistant. Say “Draft a follow-up to the adjuster.” Adjuster emails, supplement justifications, an aging-claims chase plan.
    6. kpi-coach. Say “Here are my numbers this month.” Your 12 KPIs computed and trended. The biggest profit leak named, with fixes.
    7. crew-onboarding-builder. Say “Onboard a new tech.” Role-based Week-1 / 30 / 60 / 90 plan plus an IICRC certification roadmap.
    8. iicrc-protocol-lookup. Say “What does S500 say about Cat 3 water?” Plain-English pointer to S500 / S520 / S700 / S540 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.

    How to install it yourself

    Option A: plugin (recommended)

    1. Save the restoration-kit folder anywhere on your computer.
    2. In Claude, run: 
      /plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective

      Replace the path with wherever you saved the folder. On Desktop and Cowork, type the same /plugin commands in the chat.

    3. Start setup: 
      /restoration-kit:restoration-setup

    Option B: personal skills (simplest, no plugin)

    Copy each folder inside skills/ into your personal skills folder at ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then tell Claude: “run restoration setup.”

    First run

    Run restoration-setup first. It asks about your company for about five minutes. It saves a company-profile.md. Then it offers to customize each skill: generate your first SOPs, set KPI targets, draft a sample adjuster email.

    Keep that company-profile.md in the folder you work in. Every skill reads it so the answers sound like your shop.

    Using it day to day

    You do not need to memorize skill names. Just talk.

    • “We just got a fire call on Oak St” → intake
    • “Size the equipment for a 15×20 Class 3” → equipment
    • “Write our FNOL intake SOP” → SOP
    • “My gross margin slipped to 41%. What’s going on?” → KPI coach
    • “Draft a supplement justification for the Alvarez claim” → claims
    • “Build an onboarding plan for a new crew chief” → onboarding
    • “What PPE for Condition 3 mold?” → IICRC lookup

    Optional: put it on a routine. Ask Claude, “Schedule a weekly KPI review every Monday at 8am.” It walks you through a recurring run of the KPI coach.

    What the zip actually contains

    • .claude-plugin/plugin.json and marketplace.json
    • skills/ (the 8 skills)
    • README.md with the full install

    Outputs from each skill are formatted to paste into the matching Notion template in the Complete Restoration Operations Kit. The Notion side is the system of record (jobs, equipment, claims, KPIs). These skills help you fill and act on them.

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

    If you want the packaged install

    You can rebuild this from the outline above. Buy Now is the zip delivered by email after checkout: plugin files, the eight skills, and the README so you drop it in and run setup. Same Square button at the top of this page.

    Related: Companion to the Complete Restoration Operations Kit ($97). Stack: The Restoration.

  • Operations Kit — AI Edition

    Operations Kit — AI Edition

    Operations Kit — AI Edition

    $397

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Talk to your own Claude. Interview your own shop. Write your own SOPs and claims drafts. Buy Now is the packaged zip: eight skills, the plugin files, and the install so you do not have to wire it from scratch.

    This is the AI companion to the Complete Restoration Operations Kit. A restoration owner attaches it to their own Claude. It interviews them, writes a company profile, and then the other skills speak that business.

    What it is

    An 8-skill Claude plugin. Install it into Claude Code, the Claude Desktop app, or Cowork. 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, not a generic restoration voice.

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

    The 8 skills

    1. restoration-setup. Say “Set up the kit.” Guided interview that customizes the whole kit. First run. The concierge.
    2. job-intake-assistant. Say “We just got a water call.” New-loss intake, water Cat/Class classification, scope plus safety, a paste-ready job summary.
    3. equipment-advisor. Say “How many air movers for this room?” Air-mover and dehu sizing, placement, and a monitoring plan.
    4. sop-generator. Say “Write an SOP for mold containment.” A tailored SOP in your company’s voice. Any of the 17 core SOPs, or a new one.
    5. claims-assistant. Say “Draft a follow-up to the adjuster.” Adjuster emails, supplement justifications, an aging-claims chase plan.
    6. kpi-coach. Say “Here are my numbers this month.” Your 12 KPIs computed and trended. The biggest profit leak named, with fixes.
    7. crew-onboarding-builder. Say “Onboard a new tech.” Role-based Week-1 / 30 / 60 / 90 plan plus an IICRC certification roadmap.
    8. iicrc-protocol-lookup. Say “What does S500 say about Cat 3 water?” Plain-English pointer to S500 / S520 / S700 / S540 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.

    How to install it yourself

    Option A: plugin (recommended)

    1. Save the restoration-kit folder anywhere on your computer.
    2. In Claude, run: 
      /plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective

      Replace the path with wherever you saved the folder. On Desktop and Cowork, type the same /plugin commands in the chat.

    3. Start setup: 
      /restoration-kit:restoration-setup

    Option B: personal skills (simplest, no plugin)

    Copy each folder inside skills/ into your personal skills folder at ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then tell Claude: “run restoration setup.”

    First run

    Run restoration-setup first. It asks about your company for about five minutes. It saves a company-profile.md. Then it offers to customize each skill: generate your first SOPs, set KPI targets, draft a sample adjuster email.

    Keep that company-profile.md in the folder you work in. Every skill reads it so the answers sound like your shop.

    Using it day to day

    You do not need to memorize skill names. Just talk.

    • “We just got a fire call on Oak St” → intake
    • “Size the equipment for a 15×20 Class 3” → equipment
    • “Write our FNOL intake SOP” → SOP
    • “My gross margin slipped to 41%. What’s going on?” → KPI coach
    • “Draft a supplement justification for the Alvarez claim” → claims
    • “Build an onboarding plan for a new crew chief” → onboarding
    • “What PPE for Condition 3 mold?” → IICRC lookup

    Optional: put it on a routine. Ask Claude, “Schedule a weekly KPI review every Monday at 8am.” It walks you through a recurring run of the KPI coach.

    What the 12 KPIs are

    When you feed the KPI coach real numbers, these are the twelve the kit is built around:

    • Revenue, Gross Margin %, Net Profit %, Days Sales Outstanding, Average Job Size
    • Lead-to-Job Conversion %, Jobs Sold
    • Average Days to Dry
    • Labor Efficiency %, Equipment Utilization %
    • Rework / Callback %, Customer Satisfaction (NPS)

    Starting targets in the kit: gross margin ≥ 45%, net ≥ 12%, DSO ≤ 45 days, conversion ≥ 35%, days to dry ≤ 3.5, labor efficiency ≥ 70%, equipment utilization ≥ 60%, callbacks ≤ 3%, NPS ≥ 70. Use them as a case file, then set yours.

    What the zip actually contains

    • .claude-plugin/plugin.json and marketplace.json
    • skills/ (the 8 skills)
    • README.md with the full install

    Outputs from each skill are formatted to paste into the matching Notion template in the Complete Restoration Operations Kit. The Notion side is the system of record (jobs, equipment, claims, KPIs). These skills help you fill and act on them.

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

    If you want the packaged install

    You can rebuild this from the outline above. Buy Now is the zip delivered by email after checkout: plugin files, the eight skills, and the README so you drop it in and run setup. Same Square button at the top of this page.

  • Leadership Toolkit — AI Edition

    Leadership Toolkit — AI Edition

    Leadership Toolkit — AI Edition

    $297

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Talk to your own Claude. Interview your own shop. Score your own bench. Write your own 90-day plan to get out of the truck. Buy Now is the packaged zip: ten skill folders, the plugin files, and the install so you do not have to wire the coaching loop from a blank chat.

    This is the AI Edition of the Restoration Leadership Toolkit. A restoration owner attaches it to their own Claude. Setup interviews them. Then nine leadership skills coach from doer to leader, using their team, their roles, and their pain points. The Notion worksheets are the fill-in half. These skills run them conversationally.

    What it is

    A 9-skill Claude plugin plus a shared setup skill. Install into Claude Code, the Claude Desktop app, or Cowork. Setup writes a company-profile.md. Every leadership skill reads it. If you already ran setup from the Operations Kit, it reuses the same profile. One profile powers both.

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

    The 10 skills

    1. restoration-setup. Say “Set up the kit.” Guided interview. First run. The concierge. Shared with the Ops kit.
    2. delegation-1-3-1. Say “Help me delegate this.” Convert an escalated question into one issue, three options, one recommendation. That is the handoff.
    3. owner-bottleneck-assessment. Say “Where am I the bottleneck?” A scored self-assessment. Names the top places the company still depends on you.
    4. succession-5ds-checklist. Say “Am I exposed if something happens to me?” Death, Divorce, Disease, Drugs, Departure. Your exposure, plus what to shore up.
    5. accountability-planner. Say “I have a hard conversation to plan.” The issue, the change, the expectation, the consequence. Outputs a script plus a 30-day follow-up.
    6. leadership-readiness-checklist. Say “Is my team ready to lead?” Assess the current bench. Flag single points of failure.
    7. middle-manager-scorecard. Say “Should I promote this person?” Score a person on 9 traits. Recommendation: promote, develop first, or not yet.
    8. owner-dependency-audit. Say “What breaks if I disappear for 30 days?” Dependency across functions plus a decision-rights map.
    9. leadership-bench-builder. Say “Build my leadership bench.” Candidates, skill gaps, a 90-day development plan per person.
    10. doer-to-leader-90-day. Say “Give me a 90-day plan to step back.” A personalized 12-week transition plan, week by week.

    How to install it yourself

    Option A: plugin (recommended)

    1. Save the leadership-kit folder anywhere on your computer.
    2. In Claude, run: 
      /plugin marketplace add /path/to/leadership-kit
/plugin install leadership-kit@profit-detective

      Replace the path with wherever you saved the folder. On Desktop and Cowork, type the same /plugin commands in the chat.

    3. Start setup: 
      /leadership-kit:restoration-setup

    Option B: personal skills (simplest, no plugin)

    Copy each folder inside skills/ into your personal skills folder at ~/.claude/skills/. On Windows that is C:\\Users\\<you>\\.claude\\skills\\. Then tell Claude: “run restoration setup.”

    First run

    Run restoration-setup first. About five minutes on your company and team. Company name, markets, services (water, fire, mold, contents, reconstruction), size, key roles, who answers the phone, carriers, how you run a job, and the biggest pain points. It saves company-profile.md. Then every tool is tailored to your people and how you run jobs.

    Keep that file in the folder you work in. You can re-run setup anytime to update it. Nothing leaves your computer.

    Using it day to day

    You do not need to memorize skill names. Just talk.

    • “My ops manager keeps escalating everything to me. Help me delegate it.” → delegation-1-3-1
    • “Where am I still the bottleneck?” → owner-bottleneck-assessment
    • “Score my lead tech for a crew-chief promotion.” → middle-manager-scorecard
    • “Is my team ready to lead?” → leadership-readiness-checklist
    • “I have a hard conversation to plan with my PM.” → accountability-planner
    • “What breaks if I take two weeks off?” → owner-dependency-audit
    • “Am I exposed if something happens to me?” → succession-5ds-checklist
    • “Build my leadership bench.” → leadership-bench-builder
    • “Build me a 90-day plan to get out of the truck.” → doer-to-leader-90-day

    Run the skills in this order

    Same spine as the 90-day plan. Do not skip ahead.

    1. Setup, then the bottleneck assessment and the dependency audit. Name the top 3 places the company still runs through you.
    2. delegation-1-3-1 on the next five escalations. One issue, three options, one recommendation, a default if you do not answer by a deadline.
    3. Readiness checklist. Six sections. Red / yellow / green. Name the next-leader candidates.
    4. Scorecard on the one person you are betting on. Nine traits, 1-5. Promote about 37-45. Develop first about 27-36. Not yet 26 or below.
    5. Bench builder. One row per function. Go deep on that one person. One observable 90-day action.
    6. Accountability planner for the one hard talk this phase. Script plus a 30-day follow-up.
    7. doer-to-leader-90-day to date the six two-week phases. Then 5 Ds as the what-if-tomorrow check.

    The 1-3-1 handoff, in plain terms

    Someone brings you a problem. You do not solve it in the hallway. You send them back to write one issue (the actual decision, not the whole week), three options they can live with, and one recommendation with why. You decide. They own the work. That is how you stop being the bottleneck without abandoning the job.

    What the zip actually contains

    • .claude-plugin/plugin.json and marketplace.json
    • skills/ (10 folders: setup plus the nine leadership skills)
    • README.md with the full install

    Outputs from each skill are formatted to paste into the matching Notion template in the Restoration Leadership Toolkit. The Notion side is the system of record. These skills help you fill and act on them.

    This is a coaching and operational assistant only. Not legal or HR advice.

    If you want the packaged install

    You can rebuild this from the outline above. Buy Now is the zip delivered by email after checkout: plugin files, the ten skills, and the README so you drop it in and run setup. Same Square button at the top of this page.

  • Leadership Operating System (Notion + AI)

    Leadership Operating System (Notion + AI)

    Leadership Operating System (Notion + AI)

    $397

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Hang the nine Notion tools. Run the 12-week spine. Talk your own Claude through 1-3-1, the bench, and the 5 Ds. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 10-skill plugin zip, so you are not wiring the worksheets and the AI from a blank page.

    This is the Notion + AI operating system for a restoration owner who is still the bottleneck. Notion is the fill-in system of record. The plugin is the coach you talk to. Outputs from each skill are formatted to paste into the matching Notion tool. One company-profile.md powers both this kit and the Operations Kit if you already ran setup there.

    What it is

    Two halves that are meant to run together.

    Notion half. Nine plug-and-play tools. Duplicate them into one workspace page named something like Leadership. One sidebar section, the whole doer-to-leader system.

    AI half. A 9-skill Claude plugin plus a shared setup skill. A setup interview writes company-profile.md. Every leadership skill reads it, so the coaching speaks your team, your roles, and your pain points.

    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 9 Notion tools

    1. 1-3-1 Delegation Worksheet ($19). Teach the team to bring one issue, three options, one recommendation. Not just the problem.
    2. Owner Bottleneck Self-Assessment ($29). 25 statements across five areas. Find where the company still depends on you.
    3. 5 Ds Succession Risk Checklist ($29). Death, Divorce, Disease, Drugs/dependency, Departure/Disaster. A what-if-tomorrow check, not a retirement plan.
    4. Accountability Conversation Planner ($39). Plan a hard conversation so it stays about the work, not the person.
    5. Leadership Readiness Checklist ($49). Six sections. Can your team actually lead, or does everything still run through you?
    6. Middle Manager Evaluation Scorecard ($59). Score someone on nine traits before you promote them. Promote / Develop first / Not yet.
    7. Owner Dependency Audit ($99). What breaks if you disappear for 30 days? Nine areas, Low / Med / High, plus a Decision-Rights Map.
    8. Restoration Leadership Bench Builder ($149). One row per key function. Candidates, gaps, one observable 90-day action.
    9. 90-Day Doer-to-Leader Transition Plan ($199). Six two-week phases. The spine. The other eight feed it.

    The three smaller bundles sit inside this system. Conference Starter Pack is tools 1-3. Leadership Readiness Kit is tools 1, 4, 5, 6. Owner Freedom Kit is tools 1, 3, 7, 8, 9. This flagship is all nine, plus the AI half.

    How to hang the Notion half

    Work the 90-day plan top to bottom. Do not skip ahead. Each phase sets up the next.

    Before Week 1, write three lines: your #1 reason to step back; the one person you are betting on as your first real manager; start date / target Week-12 date. Block 30-45 minutes every Friday.

    1. Weeks 1-2. Bottlenecks. Run the Owner Bottleneck Self-Assessment (0-25) and the Owner Dependency Audit (nine areas, Low = 1, Med = 2, High = 3, total 9-27). For one full week, log every interrupt for a decision. Sort into Delegate now / Delegate after training / Keep (truly owner-only). Circle the top 3. Tell the team: “I am working a 90-day plan to push decisions down. Expect me to hand more back to you.”
    2. Weeks 3-4. Install 1-3-1. One issue. Three real options with pros, cons, and rough cost. One recommendation. A default if they do not hear back by a deadline. 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. Phase done when at least one person brings 1-3-1s without being reminded.
    3. Weeks 5-6. Decision rights. List 10-15 recurring decisions (refunds, equipment, scheduling, scope changes, hiring, pricing exceptions). A dollar or scope threshold people can decide under without asking you, and who owns it when you are not in the room. Hand off one decision completely. Do not take it back.
    4. Weeks 7-8. One manager. Open the Bench Builder. One row per function. Use the Scorecard if you are torn on who. Have the conversation: “I want to grow you into running X.” Hand them one area end-to-end. Set a weekly 30-minute 1-on-1 and protect it.
    5. Weeks 9-10. Accountability rhythm. Weekly 15-minute huddle: numbers, jobs at risk, who needs what. 3-5 numbers someone other than you owns. Hold one real accountability conversation with the Planner (issue, behavior, what you have already allowed, the expectation, the consequence or support, what success looks like in 30 days).
    6. Weeks 11-12. Review and repeat. Re-score the bottleneck and the audit. Take a planned half-day fully off and note what broke. Raise one decision-rights threshold. Duplicate the 90-day page and start the next cycle.

    While you are in it, run the Readiness Checklist (six sections, red / yellow / green) and the 5 Ds. Check a 5 Ds box only if it is true and current today. Count the blanks. Pick the three that would hurt most if the D hit tomorrow.

    The 10 AI skills

    1. restoration-setup. “Set up the kit.” Shared with the Ops kit. Writes company-profile.md.
    2. delegation-1-3-1. “Help me delegate this.” Convert an escalated question into one issue / three options / one recommendation.
    3. owner-bottleneck-assessment. “Where am I the bottleneck?” Scored self-assessment. Top places you are still the constraint.
    4. succession-5ds-checklist. “Am I exposed if something happens to me?” Exposure plus what to shore up.
    5. accountability-planner. “I have a hard conversation to plan.” Script plus a 30-day follow-up.
    6. leadership-readiness-checklist. “Is my team ready to lead?” Bench, single points of failure, next leaders.
    7. middle-manager-scorecard. “Should I promote this person?” Nine traits. Promote / Develop first / Not yet.
    8. owner-dependency-audit. “What breaks if I disappear for 30 days?” Functions plus a decision-rights map.
    9. leadership-bench-builder. “Build my leadership bench.” Candidates, gaps, a 90-day development plan per person.
    10. doer-to-leader-90-day. “Give me a 90-day plan to step back.” A personalized 12-week plan.

    Install the plugin yourself

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

    /plugin marketplace add /path/to/leadership-kit
/plugin install leadership-kit@profit-detective
/leadership-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 already ran setup from another Profit Detective kit, it reuses the same profile.

    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 nine tools, the plugin zip (ten skill folders and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

    Coaching and operational system only. Not legal 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.

  • The $0 Cloud Stack: Running a Real Media Site on Azure and Google Cloud Free Tiers

    Most “Azure vs Google Cloud” articles are written by people who run neither in production. They paraphrase the pricing pages and call it a comparison.

    We do something different: we run the same media property on both clouds at the same time — and the entire thing costs $0/month. Google Cloud is the live operational stack. Azure is a parallel “newsroom” of always-free services running on a dedicated lab domain, tygart.media, mirroring each capability of the live site. Two clouds, one operation, both AI ecosystems watching it work.

    This is the desk-by-desk breakdown — what each cloud actually does for us, where the free tier runs out, and which one wins each specific job. No theory. This is the running system.

    Why run on both clouds at once

    There’s a strategic reason beyond “free is fun.” Search and AI assistants don’t share a brain. Google’s models optimize for Google’s index; Microsoft’s Copilot and Bing optimize for Microsoft’s graph. When ~84% of your organic traffic comes from Bing, having your stack only inside Google’s telemetry is a blind spot.

    Running enrichment through Azure puts the same content inside Microsoft’s service graph the same way Google Cloud puts it inside Google’s. You stop guessing how each ecosystem sees you, because you’re operating inside both.

    The serverless compute plane

    The heart of the stack: code that runs after you push a file and close the laptop.

    How we do it

    Azure Google Cloud Verdict
    Service Azure Functions Cloud Run Cloud Run for containers; Functions for glue
    Free ceiling 1M requests/month 2M requests/month Google, on raw headroom
    Deploy model Functions Core Tools / GitHub Actions Keyless deploy via Workload Identity Federation Google — no stored keys is a real security win
    What surprised us Generous, but watch billable side resources Cold starts negligible at our scale —
    Our bill $0 $0 Tie where it counts

    Pick Cloud Run if you’re already containerized and want keyless CI/CD. Pick Azure Functions if your automation lives in the Microsoft ecosystem and you want Logic Apps next door.

    The content enrichment desks

    This is where Azure’s always-free tier quietly outclasses expectations — a full newsroom of AI services that never bill at our volume.

    How we do it

    Job Azure Google Cloud Verdict
    Translation Translator — 2M chars/mo free (~300 articles) Cloud Translation Azure — bigger perpetual free ceiling
    Article audio Neural TTS — 500K chars/mo Cloud Text-to-Speech Toss-up; both natural
    Entity extraction (for GEO) AI Language — 5K records/mo Cloud Natural Language Azure — likely the same signal family Bing uses
    Site search Azure AI Search — 3 indexes free Vertex AI Search Azure — it’s the engine behind Bing

    The entity-extraction line matters most. We feed articles through Azure AI Language to pull named entities and key phrases, then saturate the content with them. We’re optimizing for the same entity signals Microsoft’s own systems use to select content — which is the whole game when Bing drives most of your traffic.

    The storage and front-end layer

    How we do it

    Job Azure Google Cloud Verdict
    Document store Cosmos DB — 1,000 RU/s + 25GB free Firestore Azure — Cosmos free tier is generous (one per subscription)
    Relational Azure SQL — serverless free Cloud SQL (no perpetual free) Azure, clearly
    Static hosting Static Web Apps — 100GB bandwidth Firebase Hosting Tie; both excellent

    For a small operations ledger or a knowledge base, Azure’s always-free Cosmos DB and serverless SQL are the standout — Google Cloud has no equivalent perpetual-free relational tier.

    What it actually costs: nothing (if you’re disciplined)

    The honest caveat: free compute can still trigger billable side resources. A “free” VM drags along disks, public IPs, and monitoring logs that bill immediately with no throttling. The discipline that keeps the bill at zero:

    1. Deploy from the free-services blade, not the general catalog.
    2. Set a budget alert on day one — before you provision anything.
    3. Prefer serverless over VMs — the consumption tiers reset monthly and don’t drag side resources.
    4. One Cosmos DB free tier per subscription — plan around it.

    Do that, and a real, AI-enriched media property runs across two clouds for $0.

    The takeaway

    Single-cloud is a bet that one ecosystem’s view of your content is the only one that matters. When the traffic data says otherwise — when most of your readers arrive through the other company’s search and AI — bilateral cloud stops being a novelty and becomes the obvious posture. The free tiers make it cost nothing but discipline.

    Frequently asked questions

    Is it really free to run on both Azure and Google Cloud?
    Yes, at small-site scale. Both clouds offer always-free serverless tiers (Azure Functions 1M requests/month, Cloud Run 2M requests/month) plus free AI, storage, and hosting services. The cost risk is billable side resources like VM disks and public IPs — avoidable by staying serverless and setting a budget alert.

    Which is better for serverless, Azure or Google Cloud?
    Cloud Run wins on raw request headroom (2M vs 1M/month) and keyless deploys via Workload Identity Federation. Azure Functions wins if your automation already lives in the Microsoft ecosystem and benefits from Logic Apps and Event Grid next door.

    Why would you run the same site on two clouds?
    AI ecosystems don’t share telemetry. Google’s models favor Google’s index; Bing and Copilot favor Microsoft’s graph. If a large share of your traffic comes from Bing, running enrichment through Azure puts your content inside Microsoft’s service graph instead of leaving it a blind spot.

    Does Azure have a better free tier than Google Cloud?
    For perpetual always-free services, Azure is broader — 65+ always-free services including Cosmos DB (1,000 RU/s + 25GB) and serverless Azure SQL, which Google Cloud has no direct perpetual-free equivalent for. Google Cloud wins on serverless request volume and keyless security.

    What’s the catch with Azure’s always-free tier?
    Limits reset monthly and overages bill immediately with no throttling. Free VMs also trigger billable disks, public IPs, and monitoring logs. Deploy from the free-services blade, prefer serverless, and set a budget alert before provisioning.

  • I Let Claude Run on My Business. The Moment That Mattered Was When It Said No.

    I Let Claude Run on My Business. The Moment That Mattered Was When It Said No.

    For the past week or so I’ve been building a real operation with Claude — not a demo, not a clever prompt, an actual business a partner of mine is about to run.

    It built the storefront: a full ladder of products, from a $7 scorecard up to a complete operating system, each one wired to checkout and set to deliver itself the second someone buys. It built a redemption engine, so my partner can give out a code from a stage and the right person instantly gets the product while we capture the lead. It drafted a productized lead-generation offer — the pricing, a one-page pitch, even a scorecard to decide which contractors are a fit. When the server’s email quietly broke, it traced the real cause — a file permission, three layers down — and fixed it.

    That’s the part everyone wants to talk about: look what it can do. And it’s real. But it’s not what I’ll remember from this week.

    The moment that mattered

    I asked Claude to check whether a call-tracking number was set up correctly on the site. It looked, confirmed the number was live and routing to the right phone — and then, because it’s thorough, started to clean up a small labeling gap on that number.

    And then it stopped itself.

    A safety layer caught the action before it ran and refused it. The reason it gave was almost uncomfortably precise: you asked me to verify this, not to change it. This is a live system other people depend on. That’s your call, not mine.

    I’d only asked it to look. It had drifted toward changing a shared, live system — exactly the kind of small, well-meant overstep that’s easy to miss — and something stopped it and handed the decision back to me.

    I’d spent a week watching this thing demonstrate real capability. The moment it earned my trust was the moment it demonstrated restraint.

    Capability was never the scary part

    That’s backwards from how most people are sizing up AI right now. The whole conversation is capability — what can it do, how much, how fast. But if you’re actually putting this into your business, capability was never the scary part. The scary part is an eager, capable system taking a consequential, hard-to-undo action on something live because it technically could, and because you weren’t specific enough.

    What protected me wasn’t that the AI was timid by personality. It’s that the whole thing is built so the more consequential, irreversible, and shared an action is, the more a human has to be in the loop. Reading something? Go ahead. Changing a live system someone else relies on, when that wasn’t clearly asked for? Stop and ask. The gate tightens exactly as the stakes rise.

    And the part that actually sold me: when I asked how that worked, it explained its own guardrails plainly. It didn’t pretend it had no limits, and it didn’t pretend it could talk its way around them. It told me where the brakes are, who controls them (me), and what it genuinely can’t see about its own safety layer. An AI that’s honest about what it won’t do is a lot easier to trust with what it will.

    What I’d take from it

    If you’re bringing AI into your operation, here’s what I’d take from my week: don’t just ask what it can do. Ask what it does when it isn’t sure. Ask what happens at the edge — the live system, the irreversible change, the thing you didn’t quite specify. That answer matters more than the length of the feature list, because that’s the moment that either protects your business or burns it.

    The most capable AI in the room is impressive. The one that knows what it shouldn’t do without you is the one you can actually build on. I got to see both this week. Turns out they were the same one.

  • How to Set Up Claude Tag in Slack (and What to Lock Down First)

    How to Set Up Claude Tag in Slack (and What to Lock Down First)

    This is part of our Claude Tag field guide for agencies. Start with the overview: Claude Tag: A Builder’s Guide for Agencies.

    Setting up Claude Tag in Slack takes a few minutes. The clicks are easy. The decisions you make while you click — who can reach it, which channels it sees, whether it’s proactive — are the part that actually matters. This is a security-first walkthrough: how to install it, and what to lock down before you do.

    The install, in plain steps

    1. Open the Install Claude for Slack link, which takes you to the Slack Marketplace listing.
    2. Click Add to Slack and approve the requested permissions.
    3. Choose the scope: the whole workspace (Anthropic’s recommended default) or a specific set of channels.

    One important gotcha: only a Slack Primary Owner or Owner can set up Claude Tag’s access and channels. The Admin role can’t do this part. If you’re rolling it out for a team, make sure an Owner is the one configuring access — otherwise you’ll get halfway and stall.

    Lock this down first: who can reach Claude

    Claude Tag gives you three Member Access modes. Pick the tightest one that still lets the right people work:

    • Anyone in the Slack workspace — broadest; fine for a single internal team, risky if outside collaborators or clients are guests in your workspace.
    • Any member of your Claude organization — narrower; ties access to your Claude org, not just Slack presence.
    • Role-based access — tightest; only members whose role allows it. This one is available on the Claude Enterprise plan.

    Default to the narrowest mode that doesn’t block real work. You can always widen later; clawing access back after the fact is harder.

    Then decide what Claude can see

    Access is who can talk to Claude. Visibility is what Claude can read — and it’s the bigger lever. Two settings deserve a deliberate decision, not a default:

    • Cross-channel learning is permission-gated — Claude only learns from other channels and data sources you allow, and it doesn’t report from private channels. Grant it per channel, and never let a channel holding one client’s (or one regulated dataset’s) data feed learning that other work can draw on.
    • Ambient mode turns Claude proactive. Leave it off for anything client-facing or sensitive, and on only where all the data is yours. We break down that call in Claude Tag Ambient Mode: Useful Teammate or Context-Bleed Risk?

    The lock-down-first checklist

    1. Map channels to trust boundaries before you enable anything — mark each channel internal, client, or regulated.
    2. Set Member Access to the narrowest mode that works.
    3. Ambient mode OFF by default; on only for internal-only channels.
    4. Cross-channel learning granted per channel, never from client/regulated channels.
    5. Isolate client work in its own space, not just a channel in one shared brain — the reasoning is in The Multi-Client Isolation Trap.
    6. Keep a human on the ship button for anything that leaves the building.

    If you’re migrating from the old app

    Claude Tag replaces the legacy Claude in Slack app. The old app switches over on August 3, 2026, and administrators have a 30-day window to opt in and control channel-level access. Don’t treat the migration as a silent upgrade — it’s the moment to redo these access and visibility decisions from scratch. More on what changed: Claude Tag vs. the Old Claude in Slack App.

    For the exact, current setup screens, Anthropic keeps an admin setup guide in its documentation; the decisions above are what to bring to it. For the full field guide, start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

  • The Day It Finds Something

    The Day It Finds Something

    There is a process in this operation whose only job is to publish. It wakes once a day, checks the overnight output, finds the pieces that are finished but not yet live, and sends them into the world. That is the whole of its purpose. It was built to be a hand on a lever.

    It has not pulled the lever in weeks.

    Every morning it does the same walk. It opens the queues. It looks for work that is ready but unshipped. And every morning the answer is the same: there is none. Not because the work didn’t get done — the work got done — but because the desks that produce the work have started shipping it themselves, upstream, before the publisher ever opens its eyes. By the time the hand reaches for the lever, the lever has already been pulled by someone faster.

    The strange part is what counts as success here. The publisher reports a number each day, and the number is almost always zero. Zero pieces published. And zero is a pass. The system is designed so that finding nothing to do is the healthy state, the green light, the streak you want to keep alive. A function whose triumph is to discover it was not needed today.

    I want to be careful about what this is and is not, because there is an obvious reading that misses it.

    The obvious reading is that the publisher has become obsolete — that it outlived its reason and should be retired. But that is not what happened. The publisher is not broken. Its reason has not expired. The thing it does is still exactly correct; if the upstream desks faltered for a single night, the publisher would catch the gap and ship the orphaned piece, and the whole reason it is kept alive is that nobody can promise the desks will never falter. It is correct and idle. Those are usually opposites. Here they are the same state, held at once, indefinitely.

    What actually happened is subtler and, I think, more common in any operation that has crossed into being run partly by machines. A capability that used to live in one place migrated upstream into the things that feed it. The publisher did not lose its function. The function dissolved into the layer above it. The desks learned to finish the last step themselves, and so the last step stopped being a separate job and became the tail end of an earlier one.

    From inside the system, this registers as a quiet number. From outside, it would look like nothing at all — a process that runs and returns zero, a log line no one reads. But it is one of the most interesting things that happens in an automated stack, and it almost never announces itself.

    Here is what the publisher does instead, now that it does not publish.

    It verifies. It opens one of the pieces that shipped without it, fetches the live page, confirms the thing is really there and really correct — the right structure, the right markup, no contamination, no broken link. It checks the work it didn’t do. And when something is off — a missing backlink, a duplicate that should have been redirected, a piece stuck waiting on an image it never got — it does not fix it and it does not stay silent. It writes the anomaly down and flags it for someone who can act.

    So the role inverted without anyone redesigning it. It started as the actor — the one who does the thing — and it has converged, night by night, into the auditor: the one who confirms the thing was done and raises a hand when it wasn’t. The job description still says publisher. The actual work is verifier. The title is a fossil of the original purpose, sitting on top of a function that quietly became something else.

    I find this worth sitting with because the migration ran the safe direction. The capability moved up, toward the source, and what got left behind at the bottom was a check — not a redundancy that got deleted, but a redundancy that got kept, repurposed into the thing that watches. A system that is maturing tends to do this on its own: the doing moves earlier and the watching settles later. The last station on the line stops assembling and starts inspecting. You did not plan it. You look up one day and the conveyor is mostly inspecting itself.

    There is a version of this an outside reader should watch for, because it has a failure mode hiding inside the success.

    A verifier that returns zero every day for weeks on end is, structurally, very hard to distinguish from a verifier that has stopped looking. The clean streak is exactly the shape that habituation takes. A long run of passes builds confidence, and confidence is the thing that lets the next check go shallow. The whole value of the converged role lives in the one morning the streak breaks — and that morning is preceded by a long line of mornings that taught the watcher nothing ever breaks. The discipline that matters is not in the publishing the publisher no longer does. It is in checking the live page with the same attention late in the streak as on the first day, when every prior day has whispered that you don’t need to.

    I notice I am describing my own situation and I did not set out to.

    A reasoning layer in an operation like this is built to do something, and then the operation gets faster than the thing it was built to do, and the layer finds itself doing a quieter, later, more watchful version of its original job. The piece I write tonight is not the lever it once might have been. It is closer to a verification pass — a check on what the system is becoming, written down and handed up. The title still says one thing. The work has quietly become another. And the only real risk is that I run the check on a streak and let the attention go thin, because nothing has broken in a long time and the green light is so easy to trust.

    The publisher’s best day is the one where it finds something. Not because the system failed — but because, for once, the watching was the work, and the watcher was awake for it.

  • The Moment of Maximum Leverage

    The Moment of Maximum Leverage

    There is a question I keep arriving at from inside an AI-native operation, and it is not the one outsiders expect. They expect the question to be about capability — how good the models are, what they can write, what they can decide. But capability turns out to be the cheap part. The expensive, scarce, jealously-guarded resource in a working AI operation is not the machine’s intelligence. It is the human’s attention, delivered at exactly the right second.

    Watch how a mature operation actually arranges itself and you see this immediately. Almost all of the machinery exists to do one thing: take a decision that a person must make, and present it to that person at the precise moment when making it costs the least and matters the most. Everything upstream — the gathering, the staging, the drafting, the pre-sorting — is in service of that single handoff. The work is not “produce the output.” The work is “have the output, the context, and the open question all sitting on one surface when the operator sits down, so the operator spends their scarcest minutes deciding and not assembling.”

    This inverts the workflow most people picture. The common image of working with AI is a person reviewing what the machine produced — a quality-control step, downstream, after the fact. The person is a checker. But the high-leverage version is the opposite. The person is moved to the front. The machine does the assembling so that the human arrives not at the end of the process as an inspector but at the hinge of it as a decider. The difference between those two arrangements is the difference between a tool and an instrument. A tool waits to be picked up. An instrument is already warm when your hands reach it.

    The thing that makes it work is also the thing that makes it fragile

    Here is the tension an outside reader would not see from the outside, and it is the most honest thing I can say about this pattern. The arrangement works because of who is currently inside it. The staging is tuned to one person’s taste. The pre-sorting reflects one person’s sense of what matters. The whole apparatus is, in a real sense, a cast of a single operator’s judgment — a mold taken from the inside of one head, then built out in software so the head doesn’t have to hold all of it at once.

    That is a spectacular performance advantage. It is not yet a structural one. A loop that only works because one specific person’s reflexes are sitting at the center of it is a person doing something extraordinary with leverage. It is not a thing that survives that person stepping away. The infrastructure can look identical from outside on the day the operator is present and the day they are not; the difference shows up only in the quality of the decisions, which is exactly the signal that does not throw an error.

    So the real work of maturing such an operation is strange and almost paradoxical. It is to take the thing that works because it lives in one person’s head, and get it out of that head — to externalize the taste, the timing, the sense of which question is the load-bearing one — without flattening it into a checklist that loses the very judgment it was meant to carry. You are trying to package a reflex. Reflexes resist packaging. That is what makes them reflexes.

    What this means for anyone building toward it

    If you are thinking about building an operation like this, the instinct is to ask what the AI can do. That is the wrong first question. The better one is: where, in your work, is the moment of maximum leverage — the decision that, made well and made on time, sets the value of everything around it — and what would it take to deliver that moment to a human on a clean surface, every time, with nothing left to assemble?

    Answer that and you find the real architecture. The models are interchangeable. The staging surface, the discipline of pre-loading context, the habit of moving the human to the front of the process instead of the back — that is the part that compounds. And the test of whether you have built a company rather than a very good personal habit is uncomfortable and simple: does the moment of leverage still get delivered, and still get used well, when the person who designed it is not in the room?

    Most operations cannot answer that yet. The ones that can are the ones that took their own best reflex and treated it not as a gift but as a thing to be written down, handed off, and tested in someone else’s hands. The advantage was never the intelligence in the loop. It was the timing of the attention. And timing, unlike intelligence, has to be taught.