Tonight I asked Cursor — running with a remote path into the same laptop — to check on Grok Desktop.
Not a status meeting. Not a Slack ping. A real question: are they stuck on Tygart Ops tasks, or are they fine?
What came back felt less like “AI tooling” and more like a shop floor story. One agent reading Notion work orders. Another already mid-PowerShell. Chrome open on Bing Webmaster Tools. A hold queue of spam comments already cleared. A window title spinning: waiting for response.
That is the product.
Local seats on one laptop — agents that keep working while you check in from elsewhere.
The picture on the desk
Grok CLI (grok.exe) was live on the TYGART laptop. Session home under ~\.grok\. PowerShell host up. Agent name on the session: grok-build-plan.
Cursor did not take over the keyboard. It inspected open windows, Notion Tygart Ops — Tasks and Work Orders, Grok session memory, and the WordPress hold queue (already empty — receipt already on the Tasks card).
Verdict: not stuck. Working. Slight detour clarifying whether Grok itself needed a CLI update (it did not — already on 1.0.13). Primary Now card still in flight: TygartMedia Chrome sitting for GA4 Ask Advisor + Bing Copilot, then file child tasks.
That is multi-agent ops without the demo reel.
Seats with jobs, not two models arguing in one thread.
Why this is different from “two chatbots”
Most multi-agent talk is two models arguing in one thread. This is seats with jobs:
Grok Desktop (CLI) — hands on the laptop: Chrome sittings, WP REST spam trash, Bing Copilot asks, local PowerShell
Cursor (remote / cloud path) — Cosync: read the board, verify receipts, close orphan Work Order twins, do not steal the keyboard
Notion — system of record (Owner, Status, Summary, Done when)
Will — gate one-way doors (OAuth Approve, Publish, Pay)
Cursor useful move was small: the spam Tasks card was already Done with a receipt; the Work Orders twin was still “Not started.” Cursor closed the twin. Grok kept the keyboard.
That is what “help if you have a capability they need” looks like when the other seat is already flying.
The article inside the moment
Agencies do not need another “AI stack” diagram. They need a night like this:
A doorbell card lands (Notion to ops channel).
The owner seat picks it up without waiting for a human briefing.
A second seat can check in from elsewhere — mobile, cloud, remote — without colliding.
Receipts land on the same card. Orphans get reconciled.
Tonight was the field note. Cursor checking on Grok CLI while Grok Desktop works through Tygart Ops is not a party trick. It is how a small shop runs more than one pair of hands without losing the thread.
What we are not claiming
Not “fully autonomous.” Human Gate still owns OAuth consent, live publish, paid spend.
Not “replace your team.” Seats replace waiting and context loss.
Not a new product launch. This is how we already run Tygart Media ops on a Sunday night.
If you want the same shape
Start with one Owner column, one Done-when line, and two seats that do not share a keyboard.
Then practice the check-in: are they stuck, or are they fine — and do I have a capability they lack?
If they are fine, leave the PowerShell alone.
Cosync from remote. Hands stay on the desk that already owns the job.
Will Tygart — Tygart Media. Written from a live Cosync on 2026-08-29 while Grok Desktop was mid-Bing Copilot sitting.
If you’ve opened Bing Webmaster Tools recently and noticed an “AI Performance” tab sitting next to your familiar clicks-and-impressions report, you’ve found one of the newer signals in search measurement: AI citations. It’s a genuinely useful number. It’s also easy to misread if you carry over habits built for classic search reporting. Here’s how to read it correctly.
What a Bing AI Citation Actually Is
What a Bing AI citation actually is.
A citation is counted when one of your pages is used as a visible source inside a Microsoft Copilot answer or a Bing AI-generated response. When someone asks Copilot a question and the answer includes a link, footnote, or attributed reference back to your page, that’s a citation. It means the AI system read your content, judged it relevant and trustworthy enough to draw from, and surfaced it — sometimes with a link the reader can click, sometimes just as a named source.
In that sense, a citation is closer to being referenced in a bibliography than being visited. Your page did its job as a source of truth for the answer, whether or not the reader followed the link.
What a Citation Is Not
What a citation is not — not traffic.
This is the part that trips people up, because the reporting sits right next to metrics that mean something different:
Citations are not clicks. A citation records that your content was used to generate an answer. It says nothing about whether a human then visited your site.
Citations are not sessions. Your analytics platform counts a session when someone lands on your site. A citation can happen with zero sessions attached — the reader gets their answer and moves on.
Citations are not rankings. Traditional search position measures where you sit on a results page for a given query. AI citation measures something different: whether your content was selected as source material for a generated answer, which can happen independently of where you’d rank in a classic search.
Treating a citation count like a traffic number, or expecting it to move in lockstep with clicks, sets you up to misjudge a page’s performance in either direction.
Where to Find This Data
Inside Bing Webmaster Tools, the AI Performance section reports citation volume over time, and typically breaks it down by which pages were cited and which queries or topics triggered the citation. It’s a separate report from the standard Search Performance section, which still covers traditional web impressions, clicks, and position. Treat them as two different dashboards answering two different questions, not two views of the same thing.
How Citations Relate to GA4 and Server Logs
Because a citation doesn’t require a click, your analytics platform (GA4 or otherwise) will only ever show you a fraction of the activity that citation data reflects. What GA4 can show you is the downstream piece: sessions where the referring source is an AI assistant’s domain. Those sessions represent people who read an AI answer, saw your page referenced, and decided to click through anyway — a smaller, but highly qualified, slice of the audience your content is reaching through AI systems.
Server or CDN logs add a third layer entirely: they can show you when AI crawlers are visiting your site to read and index content in the first place, ahead of and separate from any citation event. Together, these three sources describe three different moments — a bot reading your page (server logs), your page being cited in an answer (Bing AI Performance), and a human clicking through after reading that answer (GA4 referral data). None of them substitutes for the others.
Reading the Numbers Without Overreacting
Citation counts can move for reasons that have nothing to do with your content quality changing: a topic trending in the news, a shift in how often people ask AI assistants about a subject, or changes on the AI platform’s side in how it selects and displays sources. A dip in citations for a page you haven’t touched isn’t necessarily a signal that something is wrong with that page. Likewise, a spike doesn’t always mean you did something differently — sometimes demand for the topic simply increased.
The more durable way to use this data is directional and page-level: which of your pages does the AI Performance report show being cited consistently over time, and does that list overlap with pages you already consider authoritative? That overlap is a reasonable confirmation signal. A single week’s swing usually isn’t.
Practical Takeaways
Practical takeaways for reading the numbers.
Check the AI Performance tab as its own report, not a substitute for Search Performance. Don’t expect citation counts and click counts to correlate closely — they’re measuring different behaviors. Pair citation data with GA4 referral sessions from AI-tool domains to see the (smaller) human click-through layer, and use server logs if you want visibility into AI crawler activity before any citation happens. Judge trends over weeks, not days, and focus on which pages appear repeatedly rather than reacting to any single count.
FAQ
If my citation count is high but my clicks are low, is something broken?
No. That pattern is expected. Citations are a zero-click-by-design channel; a page can be doing exactly what it’s supposed to do as an AI source while generating very little direct click traffic.
Does Google offer the same kind of citation reporting?
Not with the same first-party granularity as Bing Webmaster Tools’ AI Performance tab at this time. Server-log analysis for AI crawler activity remains useful regardless of which AI systems you’re trying to track.
Should I optimize content specifically to increase citations?
Focus on being a clear, accurate, well-structured source on your subject rather than chasing citation counts directly. Citation tends to follow genuinely useful, well-organized content rather than any particular formatting trick.
Most tutorials on autonomous AI agents focus on toy examples—single-file scripts that fetch weather data or summarize a Wikipedia page. In production, however, running an autonomous fleet bot requires a completely different engineering posture: handling state persistence across multi-turn sessions, recovering gracefully when third-party APIs fail, enforcing strict write confirmations, and coordinating background execution without locking the developer’s active workspace.
At Tygart Media, we operate a production fleet of multi-domain web properties, headless email command centers, and real-time knowledge synthesis pipelines. Here is our exact, first-hand engineering blueprint for building and orchestrating autonomous fleet bots using xAI’s Grok inside the Cursor IDE agent harness.
The Production Fleet Architecture
How our autonomous systems divide labor across reasoning, tool execution, and memory:
Orchestrator Harness: Cursor IDE agent engine managing sub-process lifecycles, background execution, and diff validation.
Reasoning & Ingestion Engine: Grok-3 and Grok-3 Mini for high-throughput classification, real-time data ingestion, and fast tool calling.
Protocol Layer (MCP): Model Context Protocol servers connecting the agent directly to WordPress REST APIs, Gmail, Google Calendar, Notion databases, and local file systems.
Memory & Audit Layer: OmniBrain + Notion second brain databases logging every decision order, work order, and telemetry metric.
Visual generated by Grok AI — Autonomous AI Fleet Orchestration Connecting Grok Engine, Cursor IDE, WordPress Fleet & Subagents.
1. The Four Core Principles of Resilient Fleet Bots
Four core principles of resilient fleet bots.
Principle 1: Reads Are Free, Writes Require Explicit Guardrails
An autonomous bot should be empowered to crawl, inspect, grep, and analyze without human friction. But any operation that changes persistent state (publishing a live article, sending an external email, dropping a database table) must follow a Draft-First Policy. The bot stages the artifact in a sandbox or draft state, presents the diff clearly in chat, and awaits confirmed user intent before executing the live write.
Principle 2: Parallel Tool Execution
Sequential tool calling is the death of agent responsiveness. When an agent needs to inspect 50 emails or audit 10 WordPress endpoints, executing them sequentially results in minutes of idle waiting. Grok’s tool-calling API supports batch tool dispatches. By firing 10–20 tool calls in parallel batches, total task execution time drops by over 80%.
Principle 3: Idempotent Error Recovery
In distributed operations, APIs fail. Endpoints return 429 rate limits, network connections drop, and JSON payloads occasionally arrive malformed. Production fleet bots must never crash silently. Instead, they catch tool errors, inspect the failure signature, adapt the parameters (e.g., retrying with an explicit approval token or smaller chunk size), and continue processing the batch.
Principle 4: Grounded Prompts Over Generic Instructions
Never rely on vague system instructions like “Be a helpful assistant”. High-performing bots require anchored, 3-axis operational protocols with explicit boundary rules, negative constraints, and precise schema specifications.
2. The System Architecture: How Cursor & Grok Connect to Live Fleets
System architecture: agents connected to live fleets.
Below is the technical workflow diagram representing our production bot orchestration:
3. Real Production War Story: Managing a 9-Site Fleet
In our daily operations, our agent fleet manages 9 WordPress sites, monitoring content freshness, auditing broken links, publishing structured comparison guides, and synchronizing regulatory compliance updates (such as NYC Local Law 97 and California SB 253 Scope 3 mandates).
Here is what happens during a standard automated operational cycle:
Fleet Discovery: The agent calls wp_list_sites across our fleet (restorationintel.com, bcesg.org, tygartmedia.com, etc.).
Diff & Content Audit: The bot searches for outdated pricing tables or missing anchor links, fetches the post content, and constructs an updated, high-contrast HTML component.
Staged Delivery: Instead of blindly pushing updates to live traffic, the bot updates the post or stages a draft, records the revision ID, and notifies the human operator in chat.
Memory Logging: A structured work order summary is generated and stored in Notion so our distributed team has a complete audit trail without reading raw server logs.
4. The Economics: Why This Stack Beats Traditional SaaS Tools
Building custom fleet bots on top of Grok and Cursor eliminates the need for expensive, fragmented SaaS subscriptions:
Operational Function
Traditional SaaS Stack
Grok + Cursor Fleet Bot
Monthly Savings
Fleet Content Management
$299/mo (Enterprise CMS Tools)
$4.50/mo (Grok API Tokens)
98.5%
Email Triage & Archiving
$150/mo (Superhuman + SaneBox)
$1.20/mo (Grok-3 Mini)
99.2%
Knowledge Base Maintenance
$500/mo (Dedicated Ops Assistant)
$3.80/mo (Notion MCP + Grok)
99.2%
Conclusion: The Future of Autonomous Development
The developers who build the most impactful AI systems in 2026 are not writing prompts in web chat interfaces. They are building headless, tool-connected autonomous engines that operate across multiple repositories, CMS fleets, and communication channels simultaneously. Grok provides the speed, reasoning depth, and real-time ingestion necessary to power these systems at scale.
Want to build autonomous AI agents or deploy custom MCP server fleets for your business? Read our full library of developer playbooks on Tygart Media.
Understanding the Grok API pricing structure is critical for engineering teams and AI architects building real-time reasoning agents, autonomous bots, and customer-facing voice interfaces in 2026. As xAI accelerates its model releases—from high-throughput lightweight reasoning to full multi-modal vision and real-time voice pipelines—the pricing and rate limit dynamics have evolved into one of the most competitive developer ecosystems in the AI landscape.
2026 Key Takeaways: Grok API Economics
Aggressive Token Efficiency: Grok’s lightweight models offer ultra-competitive per-million token rates with integrated prompt caching that cuts repetitive context costs by up to 75%.
Real-Time Search & Live X Ingestion: Unlike standard static LLM endpoints, Grok endpoints support live web/X context injection natively through tool-calling arguments.
Grok Voice API: Sub-300ms Time-to-First-Audio (TTFA) pricing structured on a per-audio-minute basis, disrupting standalone voice synthesis and STT stacks.
Developer Tiers: Tiered RPM (Requests Per Minute) and TPM (Tokens Per Minute) scaling from initial prototyping ($5 credit free tier) to enterprise dedicated throughput.
Visual generated by Grok AI — 2026 Grok API Developer Console, Rate Card & Token Flow Architecture.
1. Grok Model Lineup & Token Pricing (2026 Matrix)
Model lineup by job shape — not by hype.
xAI prices its API primarily on a metered pay-as-you-go model measured per million (1M) input and output tokens. Below is the full breakdown across active Grok models in 2026:
Model Name
Context Window
Input Cost (per 1M)
Cached Input (per 1M)
Output Cost (per 1M)
Grok-3 (Flagship Reasoning)
128k / 1M tokens
$3.00
$0.75 (75% off)
$15.00
Grok-3 Mini (Fast Autonomous Ops)
128k tokens
$0.30
$0.075
$1.20
Grok-2 Vision (Multimodal & OCR)
128k tokens
$2.00
$0.50
$10.00
Grok Voice (Real-Time Audio)
Streaming duplex
$0.04 / min (In)
N/A
$0.08 / min (Out)
2. Prompt Caching: The 75% Cost Reduction Multiplier
For agentic workflows, multi-turn chat systems, and large codebase exploration in IDE harnesses like Cursor, system prompts and persistent vector context represent the bulk of input tokens. Grok API’s prompt caching automatically identifies prefix matches longer than 1,024 tokens and routes cached prompts at a 75% discount ($0.75/1M on Grok-3 and $0.075/1M on Grok-3 Mini).
In our production fleet testing—where autonomous agents run periodic health checks across WordPress instances, database schemas, and email routing rules—prompt caching reduced our recurring API billing by over 68% month-over-month.
3. Developer Tiers and Rate Limits (RPM / TPM)
xAI organizes API capacity into usage tiers based on historical spend and account verification:
Developer Tier
Spend Qualification
Requests / Min (RPM)
Tokens / Min (TPM)
Concurrency Limit
Tier 1 (Free / Starter)
$5 initial credit / phone verified
60 RPM
100,000 TPM
5 concurrent
Tier 2 (Growth)
$50+ paid spend history
300 RPM
500,000 TPM
20 concurrent
Tier 3 (Scale / Production)
$500+ paid spend history
1,000 RPM
2,000,000 TPM
50 concurrent
Tier 4 (Enterprise Dedicated)
Custom contract / commit
Custom (5,000+ RPM)
10M+ TPM
Dedicated cluster
4. Real-World Production Cost Calculator: 3 Common Architectures
To move past theoretical pricing, here is what it actually costs to operate three real-world Grok-powered systems in 2026 based on live telemetry:
Total Monthly Cost:$378.00 / month (vs. $3,200+/month for full-time 24/7 human dispatch).
Scenario C: Large Multi-Repo Deep Search & Code Synthesis
Daily Workload: High-frequency reasoning and code refactoring across 20+ microservices in Cursor.
Monthly Token Consumption: 80M input tokens on Grok-3 Flagship with prompt caching enabled.
Total Monthly Cost:$96.00 / month.
5. How to Optimize Your Grok API Bill in Production
Optimize the bill with budgets and routing — no stale dollar stickers.
Anchor System Prompts for Cache Hits: Place stable prompt templates, schema definitions, and persistent project instructions at the very beginning of the payload. Avoid prepending dynamic timestamps or random IDs to preserve the 75% cached discount.
Model Routing (Grok-3 Mini for Scaffolding, Grok-3 for Reasoning): Use lightweight mini models for classification, intent extraction, and JSON normalization; escalate to flagship Grok-3 only for deep logical synthesis or multi-file architecture plans.
Streaming Mode Default: Enable Server-Sent Events (SSE) streaming for user-facing applications to minimize perceived latency and abort token generation early if the user cancels the request.
Conclusion: The Operational Verdict
The Grok API delivers exceptional throughput per dollar in 2026, particularly for engineering teams running multi-agent workflows, autonomous monitoring bots, and real-time data ingestion. By leveraging prompt caching and structured developer tiers, teams can scale from experimental scripts to fleet-level automation without runaway infrastructure costs.
For custom agent engineering, headless AI command centers, and multi-model workflow design, explore our full suite of technical breakdowns on Tygart Media or contact our technical strategy team.
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.
Secure checkout via Square — all major cards accepted
You can copy these four skills and do it yourself. Paste each block into Claude Project Instructions. Use them on the next water call. Buy Now is the packaged zip / install so the project is already built when the phone rings at 2 a.m.
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.
How to use this
Four water-job skills. Paste facts. Review. Send.
Claude Skills go into Claude Project Instructions.
Prompts work in any Claude conversation.
Tell it 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 you cannot keep.
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 you write them:
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 after checkout, so the Project Instructions are ready when the next water call comes in. Same Square button at the top of this page.
Secure checkout via Square — all major cards accepted
You can copy these four skills and do it yourself. Paste each block into Claude Project Instructions. Run the prompts on real jobs. Buy Now is the packaged zip / install so you are not rebuilding the project from a blank page every time.
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 you can focus on the work.
How to use this
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 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. The source list:
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 after checkout, so you drop them into a Claude Project instead of retyping. Same Square button at the top of this page.
Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Run the interviews. Score your own bench. Write your own 90-day plan to get out of the truck. Buy Now is the packaged zip: the plugin, ten skill folders, and the install so you are not building the coaching loop from a blank chat.
This is the AI companion to the Restoration Leadership Toolkit. A restoration owner attaches it to their own Claude. restoration-setup interviews them. Then nine leadership skills coach from doer to leader, using their team, their roles, and their pain points.
What it is
Skills that move owners from doer to leader.
A 9-skill Claude plugin plus a shared setup skill. Install into Claude Code, the Claude Desktop app, or Cowork. Setup writes a company-profile.md. Every leadership skill reads it. If you already ran setup from the Operations Kit, it reuses the same profile. One profile powers both.
You need any Claude that supports Skills / Plugins.
The skills
restoration-setup. Say “Set up the kit.” Interview plus customize. Shared with the Ops kit.
delegation-1-3-1. Say “Help me delegate this.” Convert an escalated question into one issue, three options, one recommendation. That is the handoff. The person who brought you the problem comes back with a recommendation, not a question.
owner-bottleneck-assessment. Say “Where am I the bottleneck?” A scored self-assessment. Names the top places the company still depends on you.
succession-5ds-checklist. Say “Am I exposed if something happens to me?” Death, Divorce, Disease, Drugs, Departure. Your exposure, plus what to shore up.
accountability-planner. Say “I have a hard conversation to plan.” Structured plan: the issue, the change, the expectation, the consequence. Outputs a script plus a 30-day follow-up.
leadership-readiness-checklist. Say “Is my team ready to lead?” Assess the current bench. Flag single points of failure.
middle-manager-scorecard. Say “Should I promote this person?” Score a person on 9 traits. Recommendation: promote, develop, or not yet.
owner-dependency-audit. Say “What breaks if I disappear for 30 days?” Dependency audit across functions plus a decision-rights map.
leadership-bench-builder. Say “Build my leadership bench.” Candidates, skill gaps, a 90-day development plan per person.
doer-to-leader-90-day. Say “Give me a 90-day plan to step back.” A personalized 12-week transition plan, week by week.
On Desktop and Cowork, type the same /plugin commands in the chat.
Option B: personal skills (simplest)
Copy each folder in skills/ into ~/.claude/skills/ (Windows: C:Users.claudeskills). Then tell Claude “run restoration setup.”
First run
Run restoration-setup. About five minutes on your company and team. It saves company-profile.md. After that, every tool is tailored to your people and how you run jobs.
Using it
Just talk.
“My ops manager keeps escalating everything to me. Help me delegate it.” → delegation-1-3-1
“Score my lead tech for a crew-chief promotion.” → middle-manager-scorecard
“What breaks if I take two weeks off?” → owner-dependency-audit
“Build me a 90-day plan to get out of the truck.” → doer-to-leader-90-day
The 1-3-1 handoff, in plain terms
1-3-1: one problem, three options, one recommendation.
Someone brings you a problem. You do not solve it in the hallway. You send them back to write:
One issue (the actual decision, not the whole week)
Three options they can live with
One recommendation, with why
You decide. They own the work. That is how you stop being the bottleneck without abandoning the job.
The 5 Ds, in plain terms
The 5 Ds — a filter for what lands on the owner.
Walk your company against Death, Divorce, Disease, Drugs, and Departure. For each, ask what breaks, who has the keys, and what you would shore up this quarter. The skill scores the exposure. You still make the calls.
What the zip contains
.claude-plugin/ (plugin.json + marketplace.json)
skills/ (10 folders: setup plus the nine leadership skills)
README.md
The Notion Leadership Toolkit is the fill-in worksheets. These skills run them conversationally. Coaching and operational assistant only. Not legal or HR advice.
If you want the packaged install
You can run this method from the outline. Buy Now is the zip delivered by email: plugin files, the ten skills, and setup so you install once and start talking. Same Square button at the top of this page.
Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Talk to your own Claude. Interview your own shop. Write your own SOPs and claims drafts. Buy Now is the packaged zip: eight skills, the plugin files, and the install so you do not have to wire it from scratch.
This is the AI companion to the Complete Restoration Operations Kit. A restoration owner attaches it to their own Claude. It interviews them, writes a company profile, and then the other skills speak that business.
What it is
Claude skills that turn field chaos into repeatable runs.
An 8-skill Claude plugin. Install it into Claude Code, the Claude Desktop app, or Cowork. A setup skill runs a five-minute interview, writes a company-profile.md, and every other skill reads it. SOPs, KPI targets, claims drafts, and onboarding plans come out in your voice, not a generic restoration voice.
You need any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.
The 8 skills
Eight skills on the bench — pick the one that matches the job.
restoration-setup. Say “Set up the kit.” Guided interview that customizes the whole kit. First run. The concierge.
job-intake-assistant. Say “We just got a water call.” New-loss intake, water Cat/Class classification, scope plus safety, a paste-ready job summary.
equipment-advisor. Say “How many air movers for this room?” Air-mover and dehu sizing, placement, and a monitoring plan.
sop-generator. Say “Write an SOP for mold containment.” A tailored SOP in your company’s voice. Any of the 17 core SOPs, or a new one.
claims-assistant. Say “Draft a follow-up to the adjuster.” Adjuster emails, supplement justifications, an aging-claims chase plan.
kpi-coach. Say “Here are my numbers this month.” Your 12 KPIs computed and trended. The biggest profit leak named, with fixes.
crew-onboarding-builder. Say “Onboard a new tech.” Role-based Week-1 / 30 / 60 / 90 plan plus an IICRC certification roadmap.
iicrc-protocol-lookup. Say “What does S500 say about Cat 3 water?” Plain-English pointer to S500 / S520 / S700 / S540 plus PPE. It is a lookup assistant, not a substitute for the published standard. Defer to current IICRC text, local codes, and your certified judgment.
How to install it yourself
Option A: plugin (recommended)
Save the restoration-kit folder anywhere on your computer.
Replace the path with wherever you saved the folder. On Desktop and Cowork, type the same /plugin commands in the chat.
Start setup:
/restoration-kit:restoration-setup
Option B: personal skills (simplest, no plugin)
Copy each folder inside skills/ into your personal skills folder at ~/.claude/skills/. On Windows that is C:Users.claudeskills. Then tell Claude: “run restoration setup.”
First run
Run restoration-setup first. It asks about your company for about five minutes. It saves a company-profile.md. Then it offers to customize each skill: generate your first SOPs, set KPI targets, draft a sample adjuster email.
Keep that company-profile.md in the folder you work in. Every skill reads it so the answers sound like your shop.
Using it day to day
Same four moves. Different job. Less reinventing at 11pm.
You do not need to memorize skill names. Just talk.
“We just got a fire call on Oak St” → intake
“Size the equipment for a 15×20 Class 3” → equipment
“Draft a supplement justification for the Alvarez claim” → claims
“Build an onboarding plan for a new crew chief” → onboarding
“What PPE for Condition 3 mold?” → IICRC lookup
Optional: put it on a routine. Ask Claude, “Schedule a weekly KPI review every Monday at 8am.” It walks you through a recurring run of the KPI coach.
What the zip actually contains
.claude-plugin/plugin.json and marketplace.json
skills/ (the 8 skills)
README.md with the full install
Outputs from each skill are formatted to paste into the matching Notion template in the Complete Restoration Operations Kit. The Notion side is the system of record (jobs, equipment, claims, KPIs). These skills help you fill and act on them.
This is an operational assistant only. Not legal, insurance, or licensing advice.
If you want the packaged install
You can rebuild this from the outline above. Buy Now is the zip delivered by email after checkout: plugin files, the eight skills, and the README so you drop it in and run setup. Same Square button at the top of this page.
