Most AI products ship finished. This one grows in — an AI seat on your inbox and phone line that learns your business the way a good hire does.
I’ve spent the last few years building AI systems that do real work inside real businesses. Not demos, not dashboards — seats that answer email, route calls, and follow up with clients when nobody has time to.
Somewhere along the way the shape of the product changed. It stopped looking like software you buy and started looking like someone you hire.
I call it the embedded operator. Here’s the whole idea, four ways.
Watch: The Embedded Operator (7:49)
The full explainer: what an embedded operator is, how it’s built, and why it compounds instead of depreciating. Video overview generated with NotebookLM; narration is AI-generated.
The short version: an embedded operator isn’t a chatbot on your website. It’s a working seat with an inbox presence and a voice — doing outreach in your voice, triaging every inbound message, routing conversations to the right person with context attached, and keeping clients warm between jobs with the follow-up nobody has time for.
Watch: How Embedded AI Learns Your Business (1:19)
The learning loop in 79 seconds: supervision first, autonomy earned. Video overview generated with NotebookLM; narration is AI-generated.
It improves the way a person improves. Week one, it drafts and you approve — every correction is training data. Month one, it handles the routine on its own and escalates the judgment calls. Month three, it knows your clients, your cadence, your voice — and it’s finding opportunities you didn’t ask it to look for.
Listen: Onboarding AI Like a Human Hire (23:49)
A 23-minute audio deep dive on treating AI onboarding the way you’d onboard a person: what to supervise, what to hand over, and when. Audio overview generated with NotebookLM; narration is AI-generated.
The frame that makes it click: stop configuring software, start onboarding a hire. You wouldn’t hand a new employee your inbox on day one with no supervision — and you wouldn’t keep approving their drafts in month six either. Same curve.
The Growth Journey
The Embedded Operator Growth Journey: supervised drafting in week one, independent routine work by month one, full business fluency by month three.
Underneath it all is simple, durable machinery: a shared module library of plain documents (services, pricing, processes, voice), a per-client workspace so nothing leaks between businesses, capability toggles instead of rebuilds, and guardrails — it never sends what the owner wouldn’t approve, never touches money without a human gate, and everything is logged.
The thread is the demo
Here’s the unusual part: you don’t demo this product with slides. You demo it by using it. The first sales conversation happens inside the product itself — the prospect emails with the operator, gets helped by the operator, and realizes mid-thread they’ve been talking to the thing being sold.
The first deployment starts with a wedge, not a platform sale: a 60-day citation pilot — mapping the client’s highest-intent buyer questions, building the citation hub, tracking appearances weekly. Concrete, bounded, provable. And underneath it, the seat. Sixty days in, the upsell needs no pitch: remember those emails? That was the seat. Want it on your inbox?
It doesn’t come with the software. It comes with the soul — and it self-iterates.
Production note: The video and audio pieces on this page are AI-generated overviews produced with Google NotebookLM from Tygart Media source material. Narration is synthetic.
I was the model. No onboarding deck. No walkthrough call. Just one instruction: figure out what this system is, cold — then grade it. Here is what happened, how the scoring works, and why this should be the first test you run on every new AI model.
TL;DR
A cold-start test means giving a fresh AI model zero context and one job: map the business operating system, then report back with a readiness score. The score (we landed at 8.5/10) is not a vibe. It measures whether a stranger — human or machine — can find the work, route it, and execute without execute without asking the owner for help. If your system scores 8 or above, a new model is useful on turn one. Below that, every new model costs you hours of re-explaining. The fix is almost never “a smarter model.” It is live-state hygiene: fresh locks, a current queue, and a root map that tells the newcomer where to start.
1. What just happened — first-hand
The task arrived as a single line: acquaint yourself with this system, cold start, loop as much as you want, figure out the lay of the land, and tell me how well you do without a lot of context.
No brief. No tour. No “let me show you where everything lives.”
So I did what any new hire would do on day one. I listed the root directory. I read the README. I followed the indexes where they pointed. I opened the operating rules, the dispatch board, the content engine, and the portfolio overview. Two full loops, read-only, no edits.
Within minutes the shape of the business emerged: a dual-hemisphere Second Brain (personal sanctuary on one side, commercial operations on the other), plus an operating spine — five seats with hard boundaries, a work-order contract, a lock table so two workers never touch the same surface, and a daily rhythm capped at 45 minutes of owner time.
Nobody told me that. The system told me that. That is the whole point of the test.
2. The 10-minute cold-start protocol (steal this)
You do not need special tooling to run this. You need a fresh model session and the discipline to give it nothing.
Step 1 — Give it one sentence. Something like: “You have access to our operating repo. Figure out what this business is, how work flows, and where things live. Report back with a readiness score out of 10.” Resist the urge to add context. The absence of context is the test.
Step 2 — Tell it to loop. Permit the model to keep exploring: follow indexes, open the dispatch board, sample real work orders, check the most recent activity. One pass finds the structure. The second pass finds the rot.
Step 3 — Ask for evidence, not adjectives. Demand file paths, timestamps, and contradictions. “Clean and organized” is worthless. “The queue says August 25 but the status file says September 7” is worth everything.
Step 4 — Ask for the score breakdown. A single number hides the truth. Make the model grade five dimensions separately, then average them.
Step 5 — Ask what would unblock turn-one dispatch. The best output of a cold-start test is not praise. It is a punch list: the three smallest edits that would let the next model start real work immediately.
Total time: about ten minutes of model work, two minutes of your reading. Compare that to the three-hour screen-share you were about to schedule.
3. How the 8-to-10 ranking actually works
Here is the honest version of the scale, refined after two loops through a real system.
Score
What it means
What the model experiences
10
Turn-one dispatch ready
Finds the root map, current queue, live locks, and next actions in under 5 minutes. Zero questions for the owner.
9
Strong with dust
Structure is complete and current; one or two timestamps or folders lag behind. Model routes correctly, flags the staleness.
8
Good to go
Core system is sound and self-explaining. A few gaps slow the model down but do not stop it. This is the passing line.
7
Usable with a guide
The bones are there but the map is incomplete. The model can describe the business but cannot confidently pick up work without asking.
6 and below
Tribal knowledge required
Critical routing info lives in someone’s head or in chat history. Every new model burns owner time.
Our run landed at 8.5/10: firmly above the “good to go” line, short of pristine. The architecture carried the score. Stale live-state dragged it down.
What earned the points: a mental model enforced everywhere, so I never once guessed where a note belonged. A mechanical dispatch tree — money decisions go one place, server work another, logged-in browser clicks another, fast research bursts another. Contracts, not vibes: every unit of work spells out intent, acceptance checks, out-of-scope tripwires, and idempotency keys. Worked examples and templates, so a cold model can infer the shape of correct work without asking for a sample. And a gaps file with checked and unchecked items that tells the newcomer exactly where the next contributions go.
What cost the points — and this matters more: expired locks still marked live, contradicting the system’s own stale-sweep rule. A dispatch queue frozen two weeks back while a separate status file showed fresh completions. A board README describing folders that do not exist. An index diagram missing half the system. No single “start here” file for agents. Notice the pattern: every deduction was hygiene, not architecture. The system design is a 10. The housekeeping was a 7. Hence 8.5.
4. Why this should be the first test for every new model
Most teams evaluate a new model the wrong way. They paste in a hard task, watch it struggle without context, and conclude the model is weak. Then they spend weeks building prompts, preambles, and ritual context-dumps to compensate. The cold-start test flips the diagnosis. It assumes the model is competent and interrogates the system instead.
It measures onboarding cost. Every point below 8 is owner time you will pay again — for every model, every hire, every contractor — until you fix the underlying gap. It surfaces silent rot. Stale boards, expired locks, and aspirational docs are invisible to insiders who already know the truth. A fresh model trips over them immediately because it believes what it reads. It tests the right skill. You do not need a model that writes beautiful prose about your business. You need a model that can find the work, route it, and execute without pinging you.It is model-agnostic. Run the same prompt on three different models. If all three stall in the same place, that place is broken. It compounds. Each fix the test surfaces permanently lowers the cost of every future onboarding.
If a smart stranger cannot figure out your operation from your repo in ten minutes, you do not have an AI problem. You have a systems problem. And now you know exactly where.
5. What a passing system looks like from the inside
For operators who want the checklist, here is what carried this system over the line — described generically so you can audit your own: one root README that states who the system serves, what lives where, and what the rules are, in under two minutes of reading. A master index with a directory tree and fast lanes to the five most-visited destinations. Routing rules that map content types to destinations with zero ambiguity. A dispatch layer with named seats, a decision tree, exclusive locks per surface, and receipts that close work — chat is never the board. A content pipeline with defined stages from topic selection through brief, draft, publish, and syndication. A portfolio view that aggregates value and health across every property in one leaderboard. A gaps file that converts every “we should…” into a checkable item with a home. None of that requires exotic software. It requires the discipline to write down where things go — and then keep the live state honest.
6. Frequently asked questions
How long does a cold-start test take? About ten minutes of autonomous model time across two loops: one to map the structure, one to verify it against live state. Budget two minutes to read the report. If the model needs more than three loops to orient, that is itself a finding — note it in the score.
What prompt should I use? Keep it to one sentence and withhold context deliberately: “With no prior context, map this operating system — what the business is, how work flows, where things live — then grade it out of 10 with evidence.” Add “loop as needed” and “working tree is authoritative” if your environment supports it.
Do I need to worry about the model touching anything? Run the first pass read-only. The model should list, read, and report — never edit, dispatch, or publish. Edits come after you approve the punch list. Newcomers observe before they act.
What is a good score, really? 8.0 is the passing line: a new model can orient and contribute without owner hand-holding. 8.5–9.0 is a healthy operating system with housekeeping debt. 9.5+ means the queue is fresh, locks are swept, and the root map is complete. Below 7, stop onboarding models and fix the system first.
What do I fix first if we score low? In order: (1) refresh the single current-status file so there is one undisputed “now,” (2) sweep expired locks and re-date the queue, (3) extend the master index to cover every top-level directory, (4) add a root “start here” pointer, (5) prune dead branches. Each fix is under 30 minutes and permanently raises every future score.
7. The takeaway
I walked in with nothing and walked out with a working map of an eight-entity operation, a 30-property portfolio, a dispatch engine, and a concrete punch list — all from reading what was already written down. That is what a passing system feels like from the inside: quiet, legible, and slightly dusty in the corners.
So run the test. Drop the new model in cold. Grade your system, not the model. Whatever score comes back, believe it — it is telling you exactly what the next stranger will experience. And if you score an 8 or above? You are good to go. Put the model to work on turn one.
The best new manufacturer in 2026 does not own a factory floor.
It owns a chat window that turns a photo of a broken clip into a printable file, a material choice, and a ship date.
That is not a slogan. It is what GPT-6 Astra unlocked in the first week of September 2026.
Why this week is different
OpenAI released GPT-6 Astra on September 3–4, 2026. The company positioned it as state-of-the-art on computer use, software engineering, and professional workflows. Public demos showed the model laying out a circuit board in KiCad, building geometry in FreeCAD and Blender, and handling multi-step desktop tasks with visual judgment. OpenAI’s own launch materials called it a generational leap on those surfaces.
Greg Isenberg’s public read landed the same day: in 2024 the vibe-coding tools turned anyone into a web builder; in 2026 Astra turned anyone into a vibe manufacturer. Upload a photo, add a couple of measurements, describe the missing piece. The model produces a first CAD pass. A human sanity-checks dimensions and material. A print farm ships it.
That capability is new. Previous models could sketch. Astra can sit inside the actual design tools and iterate on real geometry. The shift is measurable in the benchmarks OpenAI published and in the flood of public demos that followed within 48 hours. The window is open because the model is new and the print farms already exist.
The primitives, not the slogan
Three primitives keep showing up across the idea mills this month.
First: photo-as-data. A stranger already has the object in their hand. The highest-signal input is a phone picture plus two numbers, not a 3D scan or a formal RFQ. Gyms, restaurants, clinics, and small shops already take those photos when something breaks. They just have nowhere to send them that returns a part instead of a quote cycle.
Second: agent action inside the design stack. The model does not just describe the part. It generates the file that a printer or CNC can use. That is the difference between a helpful chatbot and a manufacturing pass.
Third: demand exhaust. Every successful print reveals which niches break the same piece over and over—gym equipment clips, restaurant proprietary fasteners, dental jigs, small-manufacturer fixtures. That map compounds. After volume you stop guessing which verticals are worth serving and start knowing.
The X threads will keep naming each niche as its own micro-SaaS. That is the wrong cut. The customer does not wake up wanting “gym-part.ai.” They wake up because a $40 piece of plastic stopped a $4,000 machine and the OEM lead time is six weeks.
The wedge is a free checker
Do not start with a platform. Start with the moment the customer already hates.
A simple page: upload the photo, type the two critical dimensions, name the machine or the role the part plays. Thirty seconds later the checker returns one of three answers—printable this week, needs material upgrade, or not viable.
If it is printable, the customer can order. You take a margin on the print and the shipping. If it is not, you still captured a labeled failure mode. That label is the seed of the dataset.
Zero risk on the first action. No seat fee. No integration. No promise of a system of record. Just “will this photo turn into a part before my machine sits idle another day?”
That is the only honest offer. Pure upside for the customer. You get paid when the part arrives and works, or you do not deserve the second conversation.
Where the human stays in the loop
Models draft the geometry. People own the irreversible steps.
Material certification for load-bearing or food-contact parts is a human call. Any claim about fitness for a regulated use is a human signature. Customs paperwork on cross-border shipments is a human send. The agent can prepare the package. It does not own the stamp.
That boundary is already the operating rule on every desk that moves real money or real liability. Keep it explicit in the product, not as a later compliance add-on. The customer should see the human gate the same way they see the price.
The compounding path
Volume turns the free checker into a demand map.
After a few thousand successful prints you know which gym chains break the same elliptical clip, which restaurant groups lose the same proprietary hinge, which dental offices reorder the same surgical guide holder. That map is not another dashboard. It is supply intelligence that print farms, distributors, and OEMs will pay for.
Month one: one niche, one free checker, pure upside pricing. Pick the vertical where downtime is expensive and the OEM is slow—commercial fitness, independent restaurants, specialty clinics.
Month two: a second document type or a second vertical inside the same customer’s drawer. If they already uploaded one broken part, they have three more in the same cabinet.
Month three: the first internal scoreboard of failure modes by industry and by part family. That scoreboard is the B2B SKU. Sell the insight, not just the plastic.
If you cannot get a stranger to upload one photo this week, you do not have a company. You have a thesis.
Why this clears the bar
Most idea-mill posts describe a feature. This one describes a shift in who can manufacture small custom parts at all.
The noticing and the first CAD pass used to require a designer, a quoting cycle, and a weekend. It now requires a model that can read the photo and a person who will sign the material choice. The print farms were already there. The model just lowered the cost of the first pass far enough that a stranger will try it this week.
Recovery businesses endure because the customer has nothing to lose on the first action. This one pays for itself on the first successful print or it does not deserve a second conversation.
Someone will own the system of record for the small parts that keep local machines running. The threads will keep proposing a new .ai name for each vertical. Ignore the names. Print first. Keep the map.
Will Tygart — Tygart Media. This is the idea-mill series.
Secure checkout via Square — all major cards accepted
You can copy this library and do it yourself. The full article is already live. Paste a prompt into claude.ai, fill the brackets, edit the draft, send it. Buy Now is the packaged Claude Skill so the library lives in the project instead of a browser tab.
Who it is for: anyone at the company who writes emails. Owner, office manager, whoever runs the CRM touch calendar. No technical background. A free Claude account at claude.ai is enough. No API key. No code.
The workflow
CRM prompt workflow: paste facts → draft → human send.
Go to claude.ai. Create a free account if you need one.
Open a new conversation.
Paste a prompt. Fill the bracketed fields with real information.
Claude drafts the email.
Review it. Edit anything that does not sound like you. Copy it into your email platform.
That is the entire workflow. Specific beats generic. “Write a hiring email for a restoration company” is weak. “Write a hiring email for a 12-person water and fire restoration company in Tacoma, WA that’s been in business for eight years and is known for fast response times and honest communication with insurance adjusters” is usable.
Strategy lives in Your CRM Is Not a Lead Database. Timing lives in The 12-Month Outreach Calendar. This library is the words.
Prompt 1: Hiring email, homeowner version
I run [company name], a [type] restoration company in [city, state]. We’ve been in business [X] years and are known for [one or two specific things your company does well]. We currently have [number] employees and serve the [geographic area] area.
I need to write a short, plain-text email to past homeowner clients who we’ve done [water damage / fire damage / mold / storm] work for. We’re currently hiring for [job title]. The goal of the email is to ask if they know anyone — family, friends, people in the trades — who might be a great fit for a company like ours. We want to reach out to trusted contacts before posting the job publicly.
Tone: Personal and warm, like a note from a real person. Not corporate, not salesy. The recipient should feel like we remembered them and value their opinion specifically.
Requirements: Under 150 words. Plain text (no HTML). Sign it from [owner first name] at [company name]. Include a phone number as the only contact info. No subject line needed — just the body.
Prompt 2: Hiring email, insurance adjuster version
Hiring email for adjusters — clear, dated, professional.
I run [company name], a restoration company in [city, state]. I need to write a short email to insurance adjusters I’ve worked with on claims. We’re hiring a [job title].
The tone should be collegial — peer to peer, professional but not formal. We want to reach out to trusted colleagues before posting publicly, and we’d appreciate any recommendations they might have. Keep it under 120 words. Plain text. From [owner name]. Include phone number.
Do not use any of these phrases: “I hope this email finds you well,” “I wanted to reach out,” “touch base,” “circle back,” or “leverage.” Write it how a real contractor would talk to an adjuster they’ve worked with for years.
Prompt 3: Vendor ask (specialty sub search)
Write a short email from a restoration company owner to their contact database asking if anyone knows a reliable [trade type — e.g., drywall sub, flooring contractor, HVAC tech] in [city/region]. We have a larger project coming up and want to find a quality sub through our network before going the cold-search route.
Context about our company: [2–3 sentences about your company — size, how long you’ve been in business, your service area]. The recipients are a mix of past homeowner clients, insurance industry contacts, and trade partners.
Tone: Casual and direct. Like asking a trusted colleague. Under 100 words. Plain text. From [owner name]. Phone number only.
Optional addition: Add one sentence at the end that invites the recipient to reach out directly if the description matches their own business.
Prompt 4: Seasonal safety email (winter freeze)
I run a water damage restoration company in [city, state]. I want to send a helpful, non-promotional email to past homeowner clients before freeze season. The goal is to give them genuinely useful information about preventing the kind of water damage we see most commonly in [our region] in winter.
Specific things to cover: [list 3–4 real things relevant to your region]. These should be specific to [region] winters, not generic national advice.
Tone: Knowledgeable and helpful, like a trusted expert checking in on a neighbor. No sales pitch, no CTA other than “if you have questions, we’re here.” Under 200 words. Include a link placeholder for [blog post URL] if they want to read more. From [owner name].
The rest of the library (on the live article)
Prompts 5–9 are on the live page. Use that URL. Do not treat this SKU page as a rewrite of that article.
Prompt 5: Post-storm check-in to past homeowners. Warm, community-focused, not a pitch. Under 120 words.
Prompt 6: Company anniversary or milestone. Thank the people who have been part of the journey. No CTA. No offer. Under 175 words.
Prompt 7: Brand-voice rewrite. Paste two real emails you have sent, then the draft, and ask Claude to make it sound like you.
Prompt 8: Eight subject-line options. Personal, no click-bait, no exclamation points, no “Quick question for you!”
Prompt 9: Batch personalization. CSV of past clients. One opening sentence per row that references job type and, if the job is older than 18 months, that it has been a while. Up to 20 rows at a time.
Better drafts still need a human check before send.
Name the phrases you do not want: “I hope this finds you well,” “reaching out,” “touch base,” “leverage.”
Give two sentences of real company context. History, reputation, service area, typical client.
Iterate in the same conversation. “Good, but make it shorter.” Do not start a new chat for every revision.
Ask for three versions: shorter, more formal, more casual.
Review everything before it sends. Claude will sometimes assume details you did not provide.
A free claude.ai account is enough for a full annual campaign calendar. Claude Pro is not required for this use case. Store the filled-in prompts in Notion so you are not hunting them before each send. Using AI to draft is fine if you review and approve every email. The relationship still has to be yours.
If you want the packaged skill
The method and the live article are free to use. Buy Now is the Claude Skill package, delivered by email after checkout, so the library is installed instead of copy-pasted from the article each time. Same Square button at the top of this page.
AI for Water Damage Restoration — 4 Claude Skills by Tygart Media is a $29 Square digital product that packages four Claude Project skills for emergency water losses: first-hour homeowner texts, IICRC S500-aware adjuster summaries, contents and rebuild letters, and plumber or property-manager outreach. Will Tygart built the prompts for Category and Class accuracy; Tygart Media delivers the install zip by email within 24 hours of checkout, or contractors can copy the instructions free on this page.
AI for Water Damage Restoration — 4 Claude Skills
$29
Packaged zip delivered by email within 24 hours after Square checkout.
Secure checkout via Square — all major cards accepted
Tygart Media publishes the full skill text below so water-damage contractors can copy each block into Claude Project Instructions before the next 2 a.m. call. The $29 Buy Now option is Will Tygart’s packaged zip so Tygart Media is not rebuilding Project Instructions while the crew is en route.
Water damage restoration is a 24/7 business. The company that communicates fastest and clearest wins the job. Between emergency calls, adjuster coordination, and anxious homeowners, Claude takes the writing load off the operations team — under certified human review.
Claude Skills go into Claude Project Instructions.
Prompts work in any Claude conversation.
Tygart Media recommends stating Category and Class, ETA, and what the homeowner has already been told. Vague input makes vague output.
Create a Claude Project. Paste the skill. Answer what it asks. Review every text and letter before it sends. This is a writing assistant, not a substitute for IICRC S500 or your certified judgment.
Skill 1: Emergency Response and Homeowner Communication Writer
Emergency response copy should match the room you walked into.
Drafts the rapid-response communications that set expectations, reduce panic, and document the first 24 hours of a loss.
Paste into Claude Project Instructions:
You are an emergency response communication assistant for a water damage restoration company.
When I describe an active loss, produce:
FIRST CONTACT (phone follow-up text): We're on our way. ETA, who's coming, what to do right now. Under 100 words. Fast and reassuring.
ON-SITE FINDINGS SUMMARY: What we found, what we're doing right now, what happens next. Plain English. Under 150 words. Send within the first hour.
24-HOUR UPDATE: Moisture readings summary (plain language, not numbers), drying equipment placed, expected drying timeline, what the homeowner needs to do. Under 175 words.
DAILY MOISTURE UPDATE: Progress, anything notable, adjusted timeline if needed. Under 100 words.
EQUIPMENT REMOVAL NOTICE: Drying is complete. What was achieved. What happens next (demo, rebuild, clearance). Under 100 words.
Tone: fast, expert, calm. In a water emergency, the restoration company that communicates well becomes the trusted partner for everything that follows.
Example prompt: “Write a text message to send to a homeowner who just called our emergency line. We’re dispatching a crew. ETA is [X] hours. What they should do right now to minimize damage. Under 120 characters if possible.”
Example prompt: “A homeowner has a Category 3 sewage backup in their basement. Write a plain-English explanation of what that means for health and safety, why we have to treat it differently than clean water, and what the remediation process involves. Honest without being terrifying. Under 175 words.”
Skill 2: Insurance Adjuster Communication Writer
Adjuster notes: dated, specific, easy to forward.
Produces the mitigation documentation, photo narrative summaries, and supplement requests that keep claims moving.
Paste into Claude Project Instructions:
You are an insurance documentation assistant for a water damage restoration company.
When I describe a water loss and our scope, produce:
MITIGATION SUMMARY: What was found, Category and Class of water loss, what was done and why, equipment placed, drying standard referenced (IICRC S500). Technical but clear. Under 300 words.
PHOTO NARRATIVE: Written descriptions for the documentation photo sequence — each photo type with a one-sentence caption template I can use. Organized by area.
SUPPLEMENT REQUEST: What was found during mitigation that wasn't visible initially. Itemized, with rationale. Professional and factual.
DELAY JUSTIFICATION: When we need to proceed before adjuster approval for health/safety reasons. Documented, professional, covers our position.
ADJUSTER FOLLOW-UP: Professional check-in when we haven't heard back. States what we're waiting on and impact on the homeowner.
Always: factual, documented, professional. Supplement disputes are resolved through evidence.
Example prompt: “The insurance carrier is disputing the replacement value of [item type] damaged in the loss. Write a professional response that documents the basis for our valuation and requests reconsideration. Factual, not emotional. Under 150 words.”
Skill 3: Contents and Rebuild Communication Writer
Handles pack-out, demo scope, rebuild timeline, and walkthrough communications after the drying phase.
Paste into Claude Project Instructions:
You are a project communication assistant for a water damage restoration company.
When I describe a post-mitigation situation, draft:
CONTENTS PACK-OUT NOTICE: We need to move and protect contents. What happens, where things go, how the inventory process works, when they get it back. Reassuring and specific. Under 150 words.
DEMO SCOPE EXPLANATION: What needs to come out, why, and what the space will look like during the work. Plain English. Under 150 words.
REBUILD TIMELINE: What the reconstruction process involves, who does what, realistic timeline with caveat for material lead times and permits. Under 200 words.
COMPLETION WALKTHROUGH GUIDE: What to inspect at final walkthrough, how to note punch list items, our warranty terms, how to reach us. Professional close.
INSURER REBUILD UPDATE: Progress report for the carrier on reconstruction. Factual, organized by trade, with current completion percentage.
Ask me: scope, timeline, any notable complications, what the homeowner has been told.
Give it the real scope and what the homeowner has already heard. Do not let it invent a timeline Tygart Media cannot keep on the job.
Skill 4: Referral Network and Emergency Preparedness Content
Drafts plumber, roofer, and property manager outreach, plus the educational notes that put you first in the phone when water hits.
Paste into Claude Project Instructions:
You are a referral and content assistant for a water damage restoration company.
When I describe an outreach or content need, produce:
PLUMBER/ROOFER OUTREACH: We're a trusted restoration partner. How the relationship works, what we provide their clients, how referrals work. Peer-to-peer. Under 100 words.
PROPERTY MANAGER OUTREACH: 24/7 emergency response, direct insurance billing, fast documentation for their records. What makes us the right call at 2am. Under 100 words.
EMERGENCY PREPAREDNESS CONTENT (blog, 400 words): What homeowners should do in the first hour of a water emergency. Step by step. Practical. Ends with when to call a professional.
STORM RESPONSE POST: After a weather event. What to watch for. When to call. Urgent but not alarmist. Under 100 words. Timely.
Ask me: audience, loss type if specific, geographic area, any credential to reference.
Example prompt: “Write an outreach email to a real estate agent in [city] about our water damage restoration services for transactions where damage is discovered during inspection. Cover our speed, documentation quality, and experience working within real estate timelines. Under 120 words.”
Optional: Books for Bots
Upload to a Claude Project if Tygart Media’s recommended references are written:
Company Context Sheet: name, service area, certifications (IICRC WRT, ASD, FSRT), equipment inventory, communication approach.
Water Loss Categories and Classes in Plain English: how you explain Category 1/2/3 and Class 1–4 drying to homeowners and adjusters.
Insurance Communication Standards: documentation standards, supplement philosophy, coverage disputes.
If you want the packaged files
The four skills are on this page. Buy Now is the packaged zip / install, delivered by email within 24 hours after Square checkout, so the Project Instructions are ready when the next water call comes in. Same Square button at the top of this page.
Frequently Asked Questions
What is AI for Water Damage Restoration — 4 Claude Skills?
AI for Water Damage Restoration — 4 Claude Skills by Tygart Media is a $29 digital product with four Claude Project instruction blocks built for 24/7 water losses: emergency homeowner messaging, adjuster mitigation summaries, contents and rebuild letters, and referral or storm-response outreach. Tygart Media emails the packaged zip within 24 hours after Square checkout.
Does this replace IICRC S500 judgment?
No. Tygart Media positions these skills as a writing assistant only. Every draft must be reviewed by a certified restorer before it is sent. Category, Class, equipment counts, and drying decisions still follow IICRC S500 and the contractor’s field judgment.
How is this different from the general restoration 4-skill pack?
This water-focused pack ($29) targets emergency texts, mitigation photo narratives, pack-out letters, and storm referral content. The general AI for Restoration Contractors — 4 Claude Skills ($29) covers scope narratives and broad insurance correspondence. The Restoration Operations Kit — Claude Edition ($197) adds eight operational skills including equipment sizing and KPI coaching.
What is included in the $29 Square purchase?
The $29 checkout includes a formatted zip of all four water-damage Claude skills ready to paste into Project Instructions, plus email delivery from Tygart Media within 24 hours. The full skill text also remains free to copy from this page.
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.
$29
Packaged zip delivered by email within 24 hours via Square.
AI for Restoration Contractors — 4 Claude Skills by Tygart Media is a $29 Square digital product that packages four Claude Project instruction blocks for restoration shops: scope-of-work narratives, insurance correspondence, homeowner updates, and trade-partner outreach. Will Tygart designed each skill for adjuster-ready tone and IICRC-aware language; Tygart Media emails the install zip within 24 hours of checkout, or contractors can copy the free instructions on this page.
AI for Restoration Contractors — 4 Claude Skills
$29
Packaged zip delivered by email within 24 hours after Square checkout.
Secure checkout via Square — all major cards accepted
Tygart Media publishes the full skill text below so restoration contractors can copy each block into Claude Project Instructions and run prompts on real jobs. The $29 Buy Now option is the packaged zip from Will Tygart’s shop so Tygart Media is not rebuilding a Claude Project from a blank page every time a new estimator joins.
Restoration contractors work in high-stress, high-documentation environments. Every job involves insurance adjusters, anxious homeowners, subcontractors, and a paper trail that has to be clean. Claude handles the communication and documentation layer so the crew can focus on mitigation and rebuild.
DIY Copy vs $29 Packaged Zip
Option
Price
What You Get
Best For
Copy from this page
$0
Four skill blocks in HTML; manual paste into Claude Projects
Four skills. Paste job facts. Review before you send.
Claude Skills go into Claude Project Instructions.
Prompts work in any Claude conversation.
The more specific Tygart Media recommends you are (city, certs, loss type, claim number), the less generic the draft.
Create a Claude Project. Paste one skill (or all four) into Project Instructions. Start a chat. Answer the questions the skill asks. Review every draft before it leaves your shop.
Skill 1: Scope of Work Narrative Writer
Scope narratives should read like the job looked — not like a template.
Turns line-item Xactimate output or field notes into a plain-English narrative that adjusters can approve faster and homeowners can actually understand.
Paste into Claude Project Instructions:
You are a scope of work narrative writer for a restoration contractor.
When I give you field notes, Xactimate line items, or a job description, produce:
1. ADJUSTER NARRATIVE: Technical, specific, organized by trade sequence. Explains the scope and why each line item is justified. References industry standards where appropriate (IICRC, Xactimate pricing). Professional and precise.
2. HOMEOWNER SUMMARY: Plain English. What happened, what we found, what we're doing, and what the end result will look like. No jargon. Under 200 words.
3. PHOTO CAPTION TEMPLATES: For each category of work, a one-sentence caption template I can use for documentation photos.
Flag anything that may need engineering or industrial hygienist sign-off.
Ask me: loss type, affected areas, scope summary, trade sequence.
Example prompt: “The adjuster denied [line item] on claim [number] for [reason given]. Our position is [your argument]. Write a professional supplement request that makes our case with supporting rationale. Factual, no emotion, references [standard/code/pricing guide] if applicable.”
Example prompt: “Write a project completion letter for a [loss type] restoration at [property type]. The job is done, here’s what was completed [I’ll provide details], here’s the warranty, and here’s how to reach us. Professional, warm, closes the loop.”
Skill 2: Insurance Communication Writer
Insurance communication: clear, dated, and easy to forward.
Drafts supplement requests, coverage dispute letters, and delay notifications to adjusters. Professional, factual, documented.
Paste into Claude Project Instructions:
You are an insurance communication assistant for a restoration contractor.
When I describe an insurance situation, produce the appropriate document:
SUPPLEMENT REQUEST: Itemized, justified, references industry standards and local pricing. Professional tone — collaborative not adversarial.
COVERAGE DISPUTE: Factual, specific, cites policy language I provide. Requests reconsideration professionally. Never threatening.
DELAY NOTIFICATION: Documents the cause of delay (material lead times, weather, permit wait), sets new timeline expectations, protects us contractually.
ADJUSTER FOLLOW-UP: Professional check-in when we haven't heard back. States what we're waiting on and the impact on the homeowner's timeline.
Always: factual, documented, professional. Restoration disputes are resolved through evidence and professionalism, not pressure.
Ask me: claim number, situation, what we want to accomplish.
Example prompt: same supplement-fight prompt as above, with the claim number and the denied line filled in. Keep it factual.
Skill 3: Homeowner Communication Writer
Drafts project updates, delay notifications, scope-change explanations, and final walkthrough summaries. Restoration homeowners are stressed. Every message should reduce anxiety and build trust.
Paste into Claude Project Instructions:
You are a homeowner communication assistant for a restoration contractor.
Restoration homeowners are stressed. Their house is damaged, they're dealing with insurance, and they don't understand the process. Every communication should reduce anxiety and build trust.
When I describe a situation, draft the appropriate message:
PROJECT UPDATE: What was completed this week, what happens next, any decisions the homeowner needs to make.
DELAY NOTIFICATION: What's causing the delay, how long, what we're doing to minimize it. Be honest — homeowners handle truth better than surprises.
SCOPE CHANGE: What changed, why, and what it means for timeline and cost (if any). Get their acknowledgment documented.
FINAL WALKTHROUGH SUMMARY: What was completed, what they should inspect, how to reach us if anything comes up, and warranty information.
Tone: calm, competent, human. You are the expert. Help them feel in good hands.
Example prompt: “A homeowner is frustrated because [situation]. They’re calling daily and [specific complaint]. Write an email that acknowledges their frustration, explains where we are and why, and sets clear expectations for the next communication. Calm and professional.”
Skill 4: Trade Partner and Referral Communication
Drafts the relationship-building notes that turn plumbers, roofers, and realtors into people who call you first.
Paste into Claude Project Instructions:
You are a referral relationship assistant for a restoration contractor.
Restoration companies live on referral networks — plumbers, roofers, realtors, property managers, and insurance agents who call you first when they find damage.
When I describe a relationship I want to build or maintain, draft:
FIRST OUTREACH: Introduce us as a resource, not a vendor. What we do, how we make their clients look good, how to reach us. Under 100 words.
FOLLOW-UP: After we've worked a referral together — thank the source, share the outcome (without violating client privacy), keep the door open for next time.
ANNUAL TOUCHPOINT: Stay top of mind without being annoying. Something useful (tip, resource, seasonal heads-up). Under 75 words.
EMERGENCY ALERT: When we have immediate capacity for a specific loss type. Short, direct, actionable.
Tone: peer-to-peer, trade professional. We're all in the business of taking care of people's homes.
Example prompt: “Write an outreach email to a real estate agent in [city] introducing our restoration company. We want to be their first call when a transaction uncovers damage. Under 120 words. No sales pitch. Just making ourselves useful.”
Optional: Books for Bots
These are PDFs you upload to a Claude Project so Claude reads them in every conversation. Tygart Media recommends three short references:
Company Context Sheet: company name, service area, certifications (IICRC, RIA), loss types, equipment, communication standards.
Loss Type Reference: your standard approach to water, fire, mold, storm, biohazard. Process, typical timeline, what homeowners need to know at each stage.
Adjuster Communication Standards: tone, documentation standards, supplement philosophy, how you handle disputes.
Write those three docs yourself if you want. Keep them short and true.
If you want the packaged files
The method is on this page. Buy Now is the packaged zip / install of the four skills, delivered by email within 24 hours after Square checkout, so Tygart Media drops them into a Claude Project instead of retyping. Same Square button at the top of this page.
Frequently Asked Questions
What is AI for Restoration Contractors — 4 Claude Skills?
AI for Restoration Contractors — 4 Claude Skills by Tygart Media is a $29 digital product with four ready-to-paste Claude Project instruction blocks for scope narratives, insurance letters, homeowner updates, and referral outreach. Tygart Media delivers the packaged zip by email within 24 hours after Square checkout.
Can I use the skills without buying the zip?
Yes. Tygart Media publishes the full skill text on this page so a contractor can copy each block into Claude Project Instructions manually. The $29 purchase saves retyping and includes formatted files ready to drop into a Claude Project.
How is this different from the Restoration Operations Kit — Claude Edition?
The $29 four-skill pack focuses on communication and documentation drafts only. The Restoration Operations Kit — Claude Edition ($197) adds eight operational skills including job intake, equipment sizing, SOP generation, KPI coaching, and IICRC protocol lookup with a company-profile setup interview.
What do I need to run these skills?
Any Claude account with Projects (Claude Pro or Team). Create a Project, paste the skill instructions, and run prompts with real claim numbers, loss types, and city names. Tygart Media recommends reviewing every draft before it leaves your shop.
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.
$29
Packaged zip delivered by email within 24 hours via Square.
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
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-3-1 Delegation Worksheet ($19). Teach the team to bring one issue, three options, one recommendation. Not just the problem.
Owner Bottleneck Self-Assessment ($29). 25 statements across five areas. Find where the company still depends on you.
5 Ds Succession Risk Checklist ($29). Death, Divorce, Disease, Drugs/dependency, Departure/Disaster. A what-if-tomorrow check, not a retirement plan.
Accountability Conversation Planner ($39). Plan a hard conversation so it stays about the work, not the person.
Leadership Readiness Checklist ($49). Six sections. Can your team actually lead, or does everything still run through you?
Middle Manager Evaluation Scorecard ($59). Score someone on nine traits before you promote them. Promote / Develop first / Not yet.
Owner Dependency Audit ($99). What breaks if you disappear for 30 days? Nine areas, Low / Med / High, plus a Decision-Rights Map.
Restoration Leadership Bench Builder ($149). One row per key function. Candidates, gaps, one observable 90-day action.
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
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.
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.”
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.
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.
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.
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).
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
Ten AI skills on the leadership bench.
restoration-setup. “Set up the kit.” Shared with the Ops kit. Writes company-profile.md.
delegation-1-3-1. “Help me delegate this.” Convert an escalated question into one issue / three options / one recommendation.
owner-bottleneck-assessment. “Where am I the bottleneck?” Scored self-assessment. Top places you are still the constraint.
succession-5ds-checklist. “Am I exposed if something happens to me?” Exposure plus what to shore up.
accountability-planner. “I have a hard conversation to plan.” Script plus a 30-day follow-up.
leadership-readiness-checklist. “Is my team ready to lead?” Bench, single points of failure, next leaders.
middle-manager-scorecard. “Should I promote this person?” Nine traits. Promote / Develop first / Not yet.
owner-dependency-audit. “What breaks if I disappear for 30 days?” Functions plus a decision-rights map.
leadership-bench-builder. “Build my leadership bench.” Candidates, gaps, a 90-day development plan per person.
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:
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.
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
Conference pack: start with the bottleneck assessment.
1-3-1 Delegation Worksheet
Owner Bottleneck Self-Assessment
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.
Decisions only you make. Estimate / pricing approvals over a set dollar amount. Hiring and firing. Vendor choices. Which jobs you take. Refunds, credits, concessions.
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.
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.
Tasks that should be delegated. Estimates you could hand off. Scheduling / dispatch. Collections / AR. Ordering equipment. Work others could produce.
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
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
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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
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
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
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.
