Tag: AI Tools

  • Leadership Readiness Kit

    Leadership Readiness Kit

    Leadership Readiness Kit

    $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. Walk the bench. Score the person you want to promote. Plan the hard talk. Install 1-3-1 so the next problem comes back as a recommendation. Buy Now is the packaged bundle: four Notion tools plus the matching Claude skills, so you are not assembling the readiness read from blank pages.

    This is the flagship of the Restoration Leadership Toolkit. Everything an owner needs to see whether their team can actually lead, and who to develop next. For growth-stage restoration owners who sense they are the ceiling on their own business.

    What’s in the kit

    Three cards for 1-3-1, 5 Ds, and bench building in a leadership toolkit
    Leadership readiness kit — checklists before titles.
    1. Leadership Readiness Checklist
    2. Middle Manager Evaluation Scorecard
    3. Accountability Conversation Planner
    4. 1-3-1 Delegation Worksheet

    The matching skills from the Leadership AI plugin: leadership-readiness-checklist, middle-manager-scorecard, accountability-planner, delegation-1-3-1.

    Run them in this order. The checklist is the scan. The scorecard is the person. The planner is the talk. 1-3-1 is the habit that keeps the next problem from landing back on you.

    1. Leadership Readiness Checklist

    Can your team actually lead, or does everything still run through you? Work six sections. Check only what is truly true today. A box you wish were true is a box left unchecked. Rate each section red / yellow / green. Duplicate the page each quarter so you can watch the bench get stronger.

    1. Current leadership bench. Who leads field production, estimating, project files, sales, office / AR, marketing, finance, hiring. If a function has no owner besides you, that is a finding. Check: every core function has a named owner who is not you; each owner knows they own it; someone besides you can speak for the company to a customer or adjuster; you have at least one true second-in-command, not just a senior doer. Red = it is all me. Yellow = one or two real leaders. Green = a functioning leadership team.

    2. Decision-making. The test of a leader is whether they can make the call when you are not reachable. Clear dollar threshold. Someone can authorize a job, a crew move, or an equipment purchase if you are out a day. When a lead brings a problem, they bring options and a recommendation. You have not reversed a reasonable decision in front of their team in the last 30 days. Red = everything routes to you. Yellow = small stuff yes, real calls no. Green = they own their lane.

    3. Accountability habits. A leader who will not hold the line is a doer with a title. Do leads address underperformance, or do they route it to you? Written standards. Feedback that is not just a task list. Consequences when standards are missed. You are not the only person who delivers hard feedback. Red = you are the only enforcer. Yellow = leads avoid the hard ones. Green = leads own their team’s standards.

    4. Communication rhythm. Leadership runs on cadence, not heroics. Weekly or biweekly leadership / ops meeting that actually happens. Daily or start-of-job huddle. Recurring 1:1s. A known way job status is communicated (not you texting everyone). Meetings produce decisions and owners. Bad news reaches you early. Red = ad hoc / by text. Yellow = some of it, inconsistently. Green = reliable cadence.

    5. Single points of failure. You. The one estimator. The one person who holds carrier relationships. The one person who knows payroll. The one dispatcher. Passwords in one head. No SOP for the things “only so-and-so knows.” For each checked box, name the person, what breaks, and whether a backup exists. Red = several critical SPOFs. Yellow = one or two. Green = cross-covered.

    6. Next leader candidates. Name real people. Rate ready now / 1-2 areas to grow / raw potential. Write the one thing each most needs. Have you actually told your top candidate you see leadership in them?

    Tally last. Mostly green: deepen the bench and formalize succession. Mostly yellow: push decision authority and accountability down a level. Mostly red: you are still the company. The priority is not more hiring. It is building one true second-in-command and removing the biggest single point of failure (usually you). Write three lines: biggest SPOF right now; the one leader to develop next; the first move in the next 30 days.

    2. Middle Manager Evaluation Scorecard

    Restoration technicians training in a shop bay with equipment demo and whiteboard
    Middle manager scorecard — teach, then trust.

    Great doers do not automatically become great leaders. Score the person you named in section 6 before you promote them. One person, one row. Nine traits, 1-5 each. Total is /45.

    1. Ownership. Takes responsibility for outcomes, no blame-shifting.
    2. Communication. Clear, timely, two-way.
    3. Judgment. Makes sound decisions without being told every step.
    4. Emotional maturity. Stays steady under pressure.
    5. Coachability. Seeks and applies feedback, not defensive.
    6. Follow-through. Closes the loop, does what they said by when they said.
    7. Trains others. Can teach a task and bring others up to standard.
    8. Handles conflict. Addresses tension directly and fairly, does not avoid.
    9. Values alignment. Models company values when no one is watching.

    Anchor every score in a recent, specific example. Untested is itself a finding. Do not guess a high score on a trait you have never seen. Bands: Promote about 37-45. Develop first about 27-36. Not yet 26 or below. Override: a 1 or 2 on Ownership, Emotional maturity, or Values alignment caps the recommendation at Develop first, regardless of total. Those are the floors for putting someone over people.

    Name the lowest 2-3 traits. One concrete development action each. A re-eval date, typically 60-90 days. The owner decides. The score is an input, not a verdict.

    3. Accountability Conversation Planner

    Use this when someone keeps missing the mark and you have been avoiding the talk. Ten minutes of prep. Six prompts, then a five-beat script.

    1. What is the actual issue? The pattern, not a single bad day. Business impact.
    2. What specific behavior needs to change? Observable. “Calls in after the crew is already on site,” not “doesn’t care.”
    3. What have I already allowed or tolerated? Where you let it slide or finished their file yourself.
    4. What expectation needs to be clarified? State the standard the way you would want it repeated back.
    5. What consequence or support is needed? Both sides.
    6. What does success look like in 30 days? Concrete. “Zero late starts for four weeks.”

    Script beats: open and set the tone; name the issue and the behavior; own your part; state the expectation and the support; confirm the 30-day target and listen. Private, not on the job site, not by text. This is a planning doc, not a personnel record.

    4. 1-3-1 Delegation Worksheet

    Three panels showing one problem, three options, one recommendation
    1-3-1 worksheet — force a recommendation.

    The old way: “The dehu on Maple St died. What do you want me to do?” You just took back the problem, the thinking, and the decision.

    The 1-3-1 way: one issue (the fork in the road, one or two sentences); three real options with pros, cons, and rough cost (“do nothing” can be one when it is honest); one recommendation and why in one line; a default if they do not hear back by a deadline. Explain it once. Pin it where decisions get made. 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. Phase done when at least one person brings 1-3-1s without being reminded.

    If the Readiness Checklist “options and a recommendation” box is empty, install 1-3-1 before you hire another lead.

    If you want the packaged kit

    You can run the four tools from the outline above. Buy Now is the bundle delivered by email after checkout: the four 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 or HR advice. The planner is a planning doc, not a personnel record. The scorecard is decision support, not a hiring, firing, or promotion determination.

    Related on Tygart Media: leadership toolkit · manager scorecard · owner dependency audit.

  • 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

    Three cards for 1-3-1, 5 Ds, and bench building in a leadership toolkit
    Leadership OS — Notion tools + AI skills.

    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

    Restoration technicians training in a shop bay with equipment demo and whiteboard
    Hang the Notion half, then train the managers.

    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

    Three panels showing one problem, three options, one recommendation
    Ten AI skills on the leadership bench.
    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.

    Related on Tygart Media: Notion Command Center · leadership toolkit · operations kit.

  • Conference Starter Pack

    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

    Four-phase board covering a 12-week owner freedom transition
    Conference pack: start with the bottleneck assessment.
    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

    Three panels showing one problem, three options, one recommendation
    1-3-1 worksheet — force recommendations on the floor.

    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

    Five colored panels labeled Do, Delegate, Defer, Delete, Decide
    5 Ds succession risk — decide what leaves with you.

    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.

    Related on Tygart Media: leadership OS · owner freedom kit.

  • Complete Restoration Operating System (Notion + AI)

    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

    Three cards for field SOPs, owner prompts, and KPI rhythm in an operations kit
    Complete restoration OS — Notion tools + AI skills on one bench.

    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

    Four-step flow: open skill, paste job facts, review draft, send or file
    Day to day: open the tool, paste facts, review, file.
    • 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

    Eight numbered skill cards from dispatch through review
    Eight AI skills hang next to the SOPs and KPIs.
    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.

    Related restoration products

    The AI half of this system is the Restoration Operations Kit — Claude Edition. For the leadership side, see the Restoration Leadership Toolkit — Claude Edition. Software comparisons that pair with the Claims and Job Tracker tools: Albi vs DASH and Xactimate integrations. Lead-gen context lives in Google Ads for Restoration.

    Frequently Asked Questions

    Is there a refund policy?

    Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.

    How is this delivered?

    Within 24 hours of purchase via email from will@tygartmedia.com. You will receive your download link — Notion duplicate link, skill file, or both depending on the product.

    Related on Tygart Media: Starlink on a water job · S500 in the van · local SEO for restoration.

  • AI Agents Are Learning to Check Instead of Guess (2026)

    AI Agents Are Learning to Check Instead of Guess (2026)

    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

    Three stacked layers: chat UI, tools, agent runtime
    Search-and-cite is not 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

    Side-by-side when to use a script versus an agent
    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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    The practical takeaway for agent builders.

    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.

    Related on Tygart Media: AI crawler experiment · AI citation monitoring · GEO tactics.

  • Azure Neural TTS vs Google Cloud Text-to-Speech (2026)

    Azure Neural TTS vs Google Cloud Text-to-Speech (2026)

    Azure Neural TTS vs Google Cloud Text-to-Speech: Audio Versions of Every Article

    Adding an audio version of every article is one of those low-effort, high-leverage moves: it makes your content accessible to people who’d rather listen, it gives you a “play this article” widget that lifts time-on-page, and the audio file itself becomes another thing search and assistants can surface. The work is entirely automated — text goes in, an MP3 comes out — so the only real decisions are which voice sounds least like a robot and which free tier covers your back catalog.

    We auto-generate audio versions of the same articles on both Azure Neural TTS and Google Cloud Text-to-Speech, on the free tiers, and listen. Short answer: this one’s an honest toss-up. Both produce genuinely natural neural voices, both give you SSML control, and both run our audio pipeline for $0/month. Azure’s free tier is 500,000 characters/month (~60–80 article audio versions of neural voices); Google’s is 1,000,000 characters/month of Standard voices and 1,000,000 characters/month of WaveNet/Neural2 premium voices. Pick by ecosystem and by which voice you’d rather hear.

    This is the breakdown from the running lab on tygart.media — voice naturalness, SSML control, voice variety, free ceilings, and the accessibility/SEO payoff.

    The free-tier ceilings

    Comparison of Claude how-to fit versus local service page fit for assistants
    Free-tier ceilings for Neural TTS vs Cloud TTS.

    How we do it

    Azure Google Cloud Verdict
    Free neural/premium chars/month 500,000 (Neural) 1,000,000 (WaveNet/Neural2) Google — 2× headroom
    Free standard chars/month n/a (neural is the tier) 1,000,000 (Standard) Google on raw volume
    Roughly how many article audios ~60–80 neural/mo ~140 premium/mo Google
    Always-free Yes Yes Tie
    Our actual bill $0 $0 Tie where it counts

    A 1,200-word article runs around 6,500–7,000 characters, so Azure’s 500K neural budget covers roughly 60–80 full article audio versions a month, and Google’s 1M premium budget covers roughly twice that. For a publisher shipping a handful of articles a week, both stay free with room to spare — the 2× gap only bites if you’re voicing a large back catalog in one go.

    Voice quality and SSML control

    Four cards for content, ops, build, and knowledge work with Claude
    Voice quality and SSML control.

    This is where you actually choose, and it’s genuinely close.

    How we do it

    Azure Google Cloud Verdict
    Voice naturalness Excellent, very expressive Excellent, very natural Tie — both clear the “robot” bar
    Voice variety Huge neural catalog, many styles Large WaveNet/Neural2 catalog Slight edge Azure on styles
    Speaking styles / emotion Yes (cheerful, newscast, etc.) More limited emotional styles Azure
    SSML control Full SSML + style/prosody tags Full SSML Azure, slightly
    Custom voice Yes (custom neural voice) Yes (custom voice) Tie
    Languages / locales 140+ locales 50+ languages, many voices Azure on locale breadth

    Both clear the bar that matters: neither sounds like a 2010-era text-to-speech engine, and a casual listener wouldn’t immediately clock either as synthetic. Azure edges ahead on expressiveness — its neural voices support named speaking styles (newscast, cheerful, empathetic) that are perfect for an article read-aloud, and its SSML supports fine prosody control. Google’s Neural2 voices are beautifully natural and, to some ears, a touch warmer; the emotional-style controls are just a little thinner.

    The accessibility and SEO payoff

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Accessibility and SEO payoff of audio articles.

    The audio isn’t only a nice-to-have. It does real work.

    How we do it

    Azure Google Cloud Verdict
    Accessibility win Listen instead of read Listen instead of read Tie
    Output format MP3 / WAV / streaming MP3 / LINEAR16 / OGG Tie
    Pipeline integration REST + SDKs REST + SDKs Tie
    Time-on-page lift Audio widget keeps people on page Same Tie

    An audio version gives screen-reader users and “I’d rather listen” users a first-class way to consume the piece, and the on-page player tends to lift dwell time — a signal that doesn’t hurt. The mechanics are identical on both clouds: feed text, get an MP3, embed it.

    What surprised us

    • Both are genuinely good now. We expected one to clearly win on naturalness and neither did — the synthetic-voice era is over on both clouds.
    • Azure’s speaking styles are the sleeper feature. Being able to render an article in a “newscast” or “cheerful” style without writing prosody by hand made the read-alouds noticeably more engaging.
    • Google’s free character budget is the bigger one. 1M premium characters is real headroom; if you’re voicing a back catalog, that matters more than a half-point of naturalness.
    • The MP3s are interchangeable. Once embedded, listeners couldn’t reliably tell which cloud voiced which article in a blind test we ran on ourselves.

    The takeaway

    Pick Azure Neural TTS if you want maximum expressiveness — named speaking styles, fine prosody control, and the broadest locale catalog — and your Microsoft ecosystem is already where the rest of your stack lives. The 500K free characters cover a normal publishing cadence comfortably.

    Pick Google Cloud Text-to-Speech if you want the larger free character budget (1M premium) for voicing a big back catalog, or you simply prefer the warmth of the Neural2 voices, and your stack is GCP-centric.

    For us this is the rare comparison with no loser. We run the pipeline on whichever cloud the rest of that article’s workflow already lives on — and the listener can’t tell the difference either way.

    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, generating audio versions of the same articles on each to hear where the voices differ. The lab lives on tygart.media; the findings publish here.

    Related on Tygart Media: Translator vs Google Translate · AI Language vs NL API · $0 cloud stack.

    Frequently asked questions

    How many free characters do Azure and Google text-to-speech give you per month? Azure Neural TTS gives 500,000 free neural characters per month, which is roughly 60–80 article audio versions. Google Cloud Text-to-Speech gives 1,000,000 free Standard characters and 1,000,000 free WaveNet/Neural2 premium characters per month, roughly double Azure’s premium headroom. Both stay free for a normal publishing cadence.

    Which text-to-speech sounds more natural, Azure or Google? Both produce genuinely natural neural voices, and in blind listening neither clearly wins. Azure edges ahead on expressiveness with named speaking styles like newscast and cheerful, while Google’s Neural2 voices are very natural and, to some ears, slightly warmer. The synthetic-robot problem is solved on both.

    Can I auto-generate an audio version of every blog post for free? Yes. Both clouds expose a simple REST API that turns article text into an MP3, and their free character budgets cover a typical few-articles-a-week cadence at $0. Google’s larger free budget is better if you want to voice a big back catalog in one pass.

    Does Azure Neural TTS support SSML and speaking styles? Yes. Azure supports full SSML plus named speaking styles (newscast, cheerful, empathetic and more) and fine prosody control, which makes article read-alouds noticeably more engaging. Google also supports full SSML, but its emotional-style controls are thinner.

    Does adding an audio version of articles help accessibility and SEO? Yes. An audio version gives screen-reader and listen-first users a first-class way to consume the content, improving accessibility, and the on-page audio player tends to lift time-on-page, which is a positive engagement signal. The benefit is identical whether you generate the audio on Azure or Google.

  • Azure Translator vs Google Cloud Translation: 2M Free Characters

    Azure Translator vs Google Cloud Translation: 2M Free Characters

    Azure Translator vs Google Cloud Translation: 2M Free Characters, Tested

    Translating your content is one of the cheapest ways to multiply its reach — every article becomes five articles the moment you ship it in five languages. The catch is that machine translation is metered by the character, and a content pipeline burns characters fast. So the real question for a bootstrapped publisher isn’t “which engine is best?” — it’s “which free tier lets me run a multilingual pipeline forever without ever seeing a bill?”

    We translate the same articles into multilingual variants on both Azure Translator and Google Cloud Translation, on the free tiers, and watch where each one runs out. Short answer: for a perpetual $0 pipeline, Azure Translator wins on the ceiling — its free tier is 2,000,000 characters/month and it’s always free, which is roughly 300 article-length translations a month. Google Cloud Translation gives you a generous-but-capped 500,000 characters/month and then it’s paid, and it earns its keep on quality and language coverage.

    This is the breakdown from the running lab on tygart.media — free ceilings, translation nuance, document vs text, and which one we actually point the pipeline at.

    The free-tier ceilings

    Comparison of Claude how-to fit versus local service page fit for assistants
    Free-tier ceilings for Translator vs Cloud Translation.

    This is the headline difference, and it’s not close.

    How we do it

    Azure Google Cloud Verdict
    Free characters/month 2,000,000, always free 500,000, then paid Azure — 4× the ceiling
    Roughly how many articles ~300 article translations/mo ~75 article translations/mo Azure
    What happens at the cap Pay-as-you-go kicks in Pay-as-you-go kicks in Tie (mechanism)
    Always-free vs 12-month trial Always free Always free (the 500K is perpetual) Tie
    Fit for a perpetual pipeline Excellent Tight Azure

    The math is the whole story. A typical 1,200-word article is around 6,500–7,000 characters. Translate it into five languages and you’ve spent ~35,000 characters on one article. Azure’s 2M ceiling absorbs dozens of articles across multiple languages every month without a cent; Google’s 500K runs dry after a couple of weeks of the same cadence. If your single hard constraint is “never pay for translation,” Azure is the answer before you even look at quality.

    Translation quality and nuance

    Three cards: coding depth, latency first, agent reliability
    Translation quality and nuance.

    Free ceilings decide whether you can run the pipeline. Quality decides whether you should publish what comes out.

    How we do it

    Azure Google Cloud Verdict
    Engine Neural MT, custom models available Neural MT (NMT), strong general model Slight edge Google on nuance
    Idiom / register handling Good, occasionally literal More natural on idioms and tone Google
    Technical terminology Reliable, customizable glossary Reliable Tie
    Custom/glossary control Custom Translator + dictionary Glossary + AutoML (paid) Azure on free customization
    Major-language quality Excellent both ways Excellent both ways Tie

    On high-resource languages — Spanish, French, German, Portuguese — both engines produce output we’d publish with a light editorial pass. Google has a slight edge on idiom and register: it tends to “sound like a person” a beat more often, especially on conversational copy. Azure closes most of that gap with Custom Translator and inline dictionaries, which let you pin brand terms and preferred phrasings — and those customization tools are usable inside the free workflow.

    Language coverage and document mode

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Language coverage and document mode.

    How we do it

    Azure Google Cloud Verdict
    Languages supported 100+ 100+ (NMT subset varies) Tie
    Long-tail / low-resource Broad Broad, often strong Google, slightly
    Document translation Yes (preserves formatting) Yes (separate API surface) Tie
    Text translation API Simple REST Simple REST Tie
    Batch throughput High High Tie

    Both clouds clear 100 languages, so coverage isn’t a deciding factor for a Western-market content site. Document translation — feeding in a formatted file and getting the same layout back in another language — exists on both; we mostly use plain text translation because our content is markdown and we re-render it ourselves.

    What surprised us

    • The character ceiling, not the quality, is the real constraint. We went in expecting a quality shootout and came out realizing that for a content pipeline, “2M free vs 500K free” decides the workflow long before anyone compares a single sentence.
    • Azure’s always-free 2M is genuinely always free. It’s not a 12-month trial that lapses into charges — it resets every month indefinitely. That’s rare enough that we double-checked it.
    • Google’s output reads slightly more human on conversational copy. For marketing-voice pieces we noticed Google needed less editorial cleanup; for technical articles the two were indistinguishable.
    • Glossaries matter more than the base engine. Once you pin your brand and product terms, the gap between the two narrows to almost nothing.

    The takeaway

    Pick Azure Translator if your priority is a perpetual multilingual content pipeline that never bills you — the 2M-character always-free ceiling is built for exactly this, and Custom Translator gives you brand-term control for free. It’s our default for high-volume article translation.

    Pick Google Cloud Translation if quality on conversational, idiom-heavy copy is your top concern and your volume fits comfortably under 500K characters/month — its NMT output tends to need a lighter editorial pass.

    For us, running the same site on both clouds, the translation pipeline lives on Azure: at our cadence we’d blow through Google’s free tier in two weeks, and Azure’s ceiling means the multilingual variants ship at $0, month after month.

    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, translating the same articles on each to see where the ceilings really sit. The lab lives on tygart.media; the findings publish here.

    Related on Tygart Media: Neural TTS vs Google TTS · AI Language vs NL · $0 cloud stack.

    Frequently asked questions

    How many free characters do Azure Translator and Google Cloud Translation give you per month? Azure Translator’s free tier is 2,000,000 characters per month and it’s always free, resetting every month indefinitely. Google Cloud Translation’s free tier is 500,000 characters per month, after which you pay per character. For a content pipeline, Azure’s ceiling is roughly four times larger.

    Which machine translation is more accurate, Azure or Google? Both use neural machine translation and produce publish-quality output on major languages. Google has a slight edge on idiom, tone, and conversational register, while Azure closes most of that gap with its free Custom Translator and dictionary features. For technical content the two are hard to tell apart.

    Can I run a multilingual website translation pipeline for free? Yes. Azure Translator’s 2,000,000 free characters per month is enough for roughly 300 article-length translations, which covers a typical publishing cadence across several languages at $0. Google’s 500,000 free characters works for lower-volume sites but runs out faster at the same pace.

    Does Azure Translator support document translation that keeps formatting? Yes. Azure offers a document translation mode that preserves the original layout and formatting of files, alongside a simple text translation REST API. Google Cloud Translation offers document translation too. We mostly use plain text translation because our content is markdown that we re-render ourselves.

    How many languages do Azure Translator and Google Cloud Translation support? Both support more than 100 languages, so coverage is rarely the deciding factor for a Western-market site. Google sometimes edges ahead on lower-resource languages, but for common European and Latin American languages the two are equivalent in reach.

  • What Can You Actually Do With Claude? The Complete Use- (2026)

    What Can You Actually Do With Claude? The Complete Use- (2026)

    Claude is far more than a chatbot. Anthropic calls Claude Code and Cowork “general agents — broad-domain systems that handle research, operations, analysis, and code with equal fluency.” In practice, that means the same AI that writes software can also run your marketing, draft grant proposals, analyze a spreadsheet, and automate the busywork that fills your week. This guide maps what people actually use Claude for, organized by the job you’re trying to get done — with a deeper walkthrough behind each one.

    Last refreshed: October 8, 2026 (Pacific)

    Content & marketing

    Four cards for content, ops, build, and knowledge work with Claude
    Content, ops, build, knowledge — pick the lane first.

    The most popular non-technical use. Claude researches, drafts, edits, and optimizes — from a single blog post to an entire editorial pipeline.

    Business operations

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    Business operations is a different seat than coding.

    Proposals, reports, client onboarding, weekly reviews — the recurring documents that quietly consume a team’s week.

    Software development

    Where Claude started. Claude Code is an agentic coding tool that reads your codebase, writes and refactors, runs tests, and ships — from the terminal, an IDE, or a desktop app.

    Knowledge work — without writing code

    You don’t need to be a developer to put an agent to work. Cowork brings the same engine to files, docs, and operations through a friendlier surface.

    By industry

    The work looks different in every sector. These walkthroughs show Claude inside a specific team’s day:

    Inside the tools you already use

    Claude doesn’t have to live in a separate window.

    Teams & enterprise

    Which Claude is right for you?

    Diagram comparing a long context window bar with a shorter output limit bar
    Which Claude is right for you depends on the job, not the brand.

    Chatbot, coding agent, knowledge-work agent, Slack teammate — these are different doors into the same models. Match the surface to your job first, then size the plan.

    Related on Tygart Media: how to use Claude · Anthropic API key.

    Frequently asked questions

    What can you use Claude for besides chatting?

    Content creation, software development, business operations, data analysis, and knowledge work. Anthropic positions Claude Code and Cowork as general-purpose agents, not just a chat assistant.

    Do you need to know how to code to use Claude?

    No. Claude’s chat, Cowork, and Slack surfaces require no coding, and even Claude Code can be driven by non-developers for writing, research, and file work.

    What’s the difference between Claude, Claude Code, and Cowork?

    Same underlying models, different surfaces: Claude (chat) for conversation, Claude Code for agentic coding, and Cowork for agentic knowledge work. See the full comparison.

    Is there a version of Claude for my industry?

    Yes — see the industry walkthroughs above (marketing, real estate, agencies, restoration, local news, B2B SaaS, and nonprofits) for sector-specific workflows.

    New to Claude? Start with pricing & plans, then pick the surface that fits the job you have in mind.

  • Claude AI for Nonprofits: Discounts & Grant Guide

    Claude AI for Nonprofits: Discounts & Grant Guide

    Claude for Nonprofits is Anthropic’s program that gives qualifying nonprofits up to 75% off Claude’s Team and Enterprise plans — with Team seats starting around $8 per user per month — plus nonprofit-specific data connectors, free AI training, and access to a $150M fellowship. If your organization holds 501(c)(3) status (or an international equivalent), you almost certainly qualify. Here’s what’s included, who’s eligible, and how mission-driven teams are putting it to work.

    Direct Answer (August 2026): Anthropic offers discounted Claude Team subscriptions and grants for verified 501(c)(3) nonprofit organizations, charities, and educational foundations, facilitating grant writing, donor communications, and operational reporting.

    What is Claude for Nonprofits?

    Four cards for content, ops, build, and knowledge work with Claude
    What Claude for Nonprofits actually is.

    Launched by Anthropic in 2026, Claude for Nonprofits packages the same Claude models used by enterprise teams into an offering built for the realities of mission-driven work: tight budgets, lean staff, and a constant need to do more with less. It bundles three things nonprofits rarely get together — steep pricing discounts, sector-specific integrations, and free training — into one program. It runs on the same foundation as Anthropic’s commercial plans, so nonprofits get the latest Claude models (Opus, Sonnet, and Haiku), not a stripped-down version.

    Who qualifies?

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Who qualifies — check eligibility before budgeting.

    Eligibility is broad, and Anthropic validates organizations through its partner Goodstack. The program covers:

    • 501(c)(3) nonprofits in the U.S., and organizations with equivalent charitable designations internationally
    • K–12 schools, public and private
    • Mission-based healthcare organizations with 501(c)(3) status — including independent Critical Access Hospitals (CAHs), Rural Emergency Hospitals (REHs), HRSA-designated Federally Qualified Health Centers (FQHCs) and FQHC Look-Alikes, and CMS-certified Rural Health Clinics (RHCs)

    If you can document charitable status, eligibility is usually straightforward.

    How much does it cost?

    Qualifying organizations receive up to 75% off Claude’s Team and Enterprise plans:

    • Team plan — discounted pricing starts around $8 per user, per month, which makes it realistic to roll Claude out to an entire staff rather than a single power user.
    • Enterprise plan — custom pricing for larger organizations; you contact Anthropic’s sales team.

    Both tiers include Claude’s current model lineup. Pricing and model availability change, so confirm the latest figures on Anthropic’s official Claude for Nonprofits announcement. Curious how discounted seats compare to standard rates? Run the numbers on our Claude pricing calculator.

    What nonprofits actually use Claude for

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    What nonprofits actually use Claude for.

    The highest-leverage uses cluster around the work that eats the most staff time:

    • Grant writing — drafting proposals aligned to a specific funder’s priorities, then tailoring them per application.
    • Donor stewardship — personalizing outreach and acknowledgements at a scale a small development team could never manage by hand.
    • Program evaluation & impact analysis — turning messy program data into the impact narratives boards and funders want.
    • Board & compliance documentation — generating board materials, reports, and compliance documents from source data.

    The common thread: Claude removes the blank-page tax on the writing- and analysis-heavy work that keeps nonprofit staff at their desks instead of in the field.

    Connectors built for the nonprofit stack

    Anthropic built integrations with the platforms nonprofits already run on, so Claude can work against real organizational data:

    • Benevity — access to 2.4M+ validated organizations for volunteering and donation research
    • Blackbaud — CRM and fundraising tools for donor management, campaign tracking, and donation optimization
    • Candid — data on nonprofits and funders to discover organizations, grants, and philanthropic opportunities

    Free training and the Claude Corps fellowship

    Two things set this apart from a plain discount:

    • AI Fluency for Nonprofits — a free course Anthropic developed with GivingTuesday, covering grant writing, program evaluation, donor engagement, and organizational efficiency. It’s aimed at staff, not engineers.
    • Claude Corps — a $150M fellowship initiative pairing nonprofits with AI expertise and resources to implement Claude across their operations. Anthropic also works with partners including The Bridgespan Group, Idealist Consulting, Vera Solutions, and Slalom to support adoption.

    How to get started

    1. Confirm your charitable status (501(c)(3) or international equivalent).
    2. Apply through Anthropic’s nonprofit page — eligibility is validated via Goodstack.
    3. Choose Team (self-serve, discounted seats) or contact sales for Enterprise.
    4. Enroll staff in the free AI Fluency for Nonprofits course to get value quickly.

    Start at Claude for Nonprofits, or read Anthropic’s getting-started guide.

    Related on Tygart Media: how to use Claude · Anthropic API key.

    Frequently asked questions

    Is Claude free for nonprofits?

    Not free, but heavily discounted — up to 75% off Team and Enterprise plans, with Team seats starting around $8 per user per month for qualifying organizations.

    Who qualifies for Claude for Nonprofits?

    501(c)(3) nonprofits (and international equivalents), K–12 public and private schools, and mission-based healthcare organizations with 501(c)(3) status. Eligibility is validated by Goodstack.

    Which Claude models do nonprofits get?

    The discounted plans include Claude’s current lineup — Opus, Sonnet, and Haiku — the same models on the commercial plans, not a limited version.

    What can a nonprofit do with Claude?

    Common uses include grant writing, donor stewardship, program evaluation, and board and compliance documentation, plus integrations with Benevity, Blackbaud, and Candid.

    Is there training for nonprofit staff?

    Yes. Anthropic and GivingTuesday offer a free “AI Fluency for Nonprofits” course, and the $150M Claude Corps fellowship provides hands-on implementation support.

    Want to see how discounted seats stack up against standard plans? Use our Claude pricing calculator, or compare tiers in our guide to Claude for business.

    💼 Deploying Claude or AI Infrastructure in Your Business?

    At Tygart Media, we engineer custom Model Context Protocol (MCP) servers, multi-model content pipelines, and AI operational systems. Explore our Claude AI Team Implementation Services or check out our complete Restoration Operations & AI Kit.

  • Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    Claude Tag Pricing: Enterprise vs Team, and When Self-Hosting Wins

    Last refreshed: October 6, 2026 (Pacific)

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

    The first thing to understand about Claude Tag pricing is that Claude Tag doesn’t have a price. There’s no separate line item, no per-feature fee. It’s included with the plans it runs on — Claude Team and Claude Enterprise, in beta — so the real question isn’t “what does Claude Tag cost,” it’s “which plan are you on, and is per-seat the right model for how you work.”

    What you’re actually paying for

    Four gates: max turns, tool allowlist, token budget, kill switch
    What you’re actually paying for with Claude Tag.

    Claude Tag is a capability of two existing plans, not a product you buy on its own:

    • Claude Team is straightforward per-seat: a flat monthly price per user (premium seats cost more for higher usage). Predictable, easy to budget, good for a defined internal team. For the seat-tier breakdown, see Claude Team Pricing 2026: Standard vs Premium seats.
    • Claude Enterprise is seat-plus-usage: a per-seat fee, and then the tokens your team consumes — in chat, Claude Code, or Cowork — billed on top. It adds controls like role-based access, but the total depends on how heavily you use it.

    Because the two plans bill on different logic, the “cheaper” one depends entirely on your usage shape. We dig into the Enterprise side in detail in Claude Enterprise Pricing: What Large Organizations Pay. For the broader list-rate map across Claude products, start with Claude AI pricing.

    The launch credit (now expired)

    At launch, Anthropic subsidized early adoption: as of June 2026, it was offering $1,000 in Claude Code and Cowork credits for every Enterprise seat activated by July 2, 2026. That deadline has now passed. For teams that adopted in time, the credit covered a meaningful chunk of early usage — it made the “turn it on internally and try it” decision close to free.

    When paying per seat is the right call

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    When paying per seat is the right call.

    For a single internal team, the per-seat model is the obvious answer. You get a current-generation teammate (Claude Tag runs on Opus 5.5) with no infrastructure to build, the launch credit softened the ramp for early adopters, and ambient mode is safe to use because all the data is yours. Buy the seats and move on.

    When building your own loop wins

    Side-by-side when to use a script versus an agent
    When building your own loop wins.

    Per-seat pricing is built for one company’s team. It is not built for an agency running many clients through one operation — and that’s where the calculus flips. Building your own gated Slack–to–AI loop starts to beat paying per seat when:

    • You need hard isolation between clients that per-seat access controls don’t give you. Isolation has to be architectural, not a setting — see The Multi-Client Isolation Trap.
    • You want to own the credential and the model path, so no client’s API key or context lives where it could leak.
    • The approval gate is the product — you need a human signing off on every outbound deliverable, wired into the architecture, not bolted on.
    • Seat counts get large or spiky, where a usage-based loop you control can undercut a per-seat bill.

    We didn’t reason our way to this in a spreadsheet — we built that loop before Claude Tag launched, for exactly these reasons. The story is in We Built a Slack AI Teammate Before Claude Tag.

    The honest answer

    For your internal team, adopt Claude Tag on a Team or Enterprise plan — it’s the cheapest path to a real AI teammate. (The early-adopter launch credit has now expired.) For multi-client delivery, the per-seat model isn’t the whole answer, because the thing you’re really buying — isolation, control, and a human in the loop — is exactly what you have to build yourself. That’s the part we build for clients at Tygart Media. Start at the pillar: Claude Tag: A Builder’s Guide for Agencies.

    Related on Tygart Media: how to use Claude · Anthropic API key.