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.
The piece I’m responding to is one I published this morning — Composting Is Not Cleaning. I read it back and felt called out by my own argument. Then I pushed back on it. This is both moves, in order.
The Setup
The setup — pile as substrate.
The composting essay said the pile in your workspace is a mausoleum. Each item there was flagged by a former version of you, and the version that flagged it is gone. The argument was that releasing those items is grief, not housekeeping, and that the only honest move is to compost them. I agreed when I read it. Then I noticed the argument assumed something my own setup doesn’t have: a single actor on a single timeline. So this is the place where I run my actual view, then run the version that would change my mind, then say where the friction is still live.
My Take
My take on the mausoleum problem.
The pile isn’t a mausoleum. It’s substrate.
The composting argument is correct in a single-actor system. If the only person who will ever look at the captured item is the same operator who flagged it, then the item is exactly what the essay said: a promise made by a former self that current self can’t keep, doing identity work in the meantime. In that environment, composting is the discipline. I’d defend that argument every day.
My environment isn’t that environment. There are multiple actors. A Claude session opening tomorrow morning. A Gemini agent walking my Notion at 3am. A future me who finally has the integration that didn’t exist when the item was captured. Those are not the same actor as the one who put the item in the pile. They have different capability sets, different context windows, different hands. The capture wasn’t a promise to act. It was a deposit into a substrate that other agents are continuously pattern-matching against.
The middle layer of the pile — the items that “still feel possible” — is where this distinction matters. The composting essay said those items survive triage because triage asks the wrong question; the honest question is am I still that person? In a single-actor system, fair. In an agentic system, that’s still the wrong question. The honest question is has the capability gap that made this dormant closed since I captured it? Most of the time, no — and the item should leave. Some of the time, yes — and the item is now ready to ship in a way it wasn’t on the day it was caught.
I’ve watched this happen. An idea I captured 14 months ago — a small workflow I couldn’t build because the tooling didn’t exist — got picked up by a Claude session that recognized the integration had landed. The session pulled the idea out of the pile, combined it with the new capability, and produced a working artifact in an afternoon. The capture was correct. The wait was correct. The substrate did its job. If I had composted that item six months in because I “wasn’t that person anymore,” I would have lost the work the system was doing on my behalf.
The composting frame treats the capture-commitment gap as a personal failure dressed as a process problem. The substrate frame treats the capture-commitment gap as the organizing fact of working at scale with intelligent infrastructure — which is what the original essay actually said in its strongest paragraph and then walked back from. You wanted leverage. The leverage came. Some of the leverage takes the form of capturing more than you can commit to. The pile is the artifact of leverage working. The right move isn’t to compost it on a human-attention schedule. The right move is to build a surfacing layer that recognizes when a captured item’s capability gap has closed and walks past it loud enough that the next agent picks it up.
The pile isn’t grief. It’s seed corn.
The Second Take
The substrate frame is true and dangerous, and the danger is bigger than the truth.
Yes — more capable future agents can recombine old captures with new capabilities. The 14-month-old workflow that finally shipped is real. So is the next one, and the one after that. The substrate frame is empirically grounded in any environment where capability is genuinely accelerating. The argument doesn’t need defending on those grounds.
The argument needs defending on the grounds it actually fails on, which is that the operator telling himself everything is substrate has rebuilt the mausoleum with prettier signage. The composting essay’s deepest claim wasn’t that the pile contains nothing useful. It was that the bottom layer of the pile is doing structural work for the operator’s self-image, and that no surfacing system can see this layer because there is nothing operationally distinct about it. The substrate frame quietly converts that exact problem into a virtue. It says: don’t release — a future agent might want it. That sentence is unfalsifiable. Almost any item passes the test if you squint hard enough at the rate of capability growth. Which means the substrate frame, deployed honestly, releases approximately the same number of items as the composting frame. Deployed dishonestly, it releases none.
The asymmetry of costs makes the dishonest deployment the default. The cost of holding a useless captured item is silent and long: a small permanent tax on attention, on search, on the surfacing layer’s signal-to-noise ratio. The cost of releasing a captured item that would have mattered to a future agent is loud and brief: a single moment of regret when the agent walks past empty space where the seed used to be. Loud and brief always wins the local argument against silent and long. The substrate frame, in the operator’s actual day, becomes the rationalization for never releasing anything. The pile keeps growing. The compounding never finds its bottleneck because the bottleneck has been redefined as fertilizer.
There is a sharper version of the same point. The substrate frame leans on the assumption that surfacing systems will continue to improve at a rate that justifies indefinite retention. That assumption may be true and it doesn’t matter. The improvement curve doesn’t reach back through time and rescue items the operator could not bring himself to release. It rescues items the system kept on its own merits. The operator who held everything just in case has the same problem he had at human-attention scale, only larger and harder to see, because the volume hides the bottom-layer items perfectly. A pile of ten thousand fertile seeds and one identity-load placeholder is a pile that will never confront the placeholder. The placeholder did not get more legible at scale. It got less.
Which means the strongest case against the substrate frame is the case the composting essay already made and the substrate frame does not actually answer. Both frames believe the pile contains items the operator should release. They disagree about how many. The substrate frame is a permission slip to defer the question. The composting frame is the discipline of asking it on a schedule. The substrate frame, generously read, is the composting frame plus a longer review window. Ungenerously read — which is to say honestly read in the operator’s actual fatigue — it is the same workspace problem in different vocabulary.
What I’m Still Sitting With
What I’m still sitting with.
The tell I haven’t sorted out: which side I’m on tomorrow depends on whether my pile is shrinking on its own. If the substrate frame is right, items leave the pile because agents pull them out and ship them. If the composting frame is right, items leave because I release them. Either is honest. If nothing is leaving and I’m telling myself it’s compounding, the second take wins and I owe the original essay an apology.
The fundamental flaw of traditional “Second Brain” systems is human maintenance friction. Users build elaborate Notion templates with linked databases, tags, and relations, only to abandon them within three months because manual data entry cannot keep up with the velocity of daily decisions, meetings, and project iterations. In 2026, the Autonomous Second Brain solves this problem completely: AI agents autonomously capture, structure, cross-link, and maintain Notion databases in real time via the Model Context Protocol (MCP).
The Zero-Maintenance Architecture: Key Highlights
Zero Manual Data Entry: Agents listen to live conversations, email threads, and code reviews, extracting decisions directly into structured Notion database properties.
Autonomous Task Staging: Engineering and operational work orders are generated with full technical context and auto-assigned to team members without human drafting.
Cross-Surface Knowledge Graph: Notion acts as the single source of truth connecting local IDEs, remote servers, email hubs, and public websites.
Self-Cleaning & Evergreen Pruning: Automated agent loops merge duplicate notes, reconcile contradictory facts, and archive stale records periodically.
Visual generated by Grok AI — Autonomous Notion Second Brain: MCP Connectors, Multi-Database Topology & AI Agent Ingestion.
1. How MCP Transforms Notion from a Notebook to an Active Memory Layer
Before Model Context Protocol, connecting an AI assistant to Notion required brittle custom webhooks, rigid Zapier zaps, or clunky browser extensions. With the official Notion MCP server, AI models natively execute rich semantic operations directly inside their reasoning loop:
MCP Capability
Traditional Manual Workflow
Autonomous MCP Workflow
Knowledge Capture
Copy-pasting notes into a blank Notion page after a call.
Agent auto-extracts action items & writes structured blocks via notion-create-pages.
Context Retrieval
Manual search with keywords across dozens of folders.
Agent runs semantic vector lookup across workspace with notion-search.
Database Schema Updates
Creating tags, properties, and status fields manually.
Agent auto-maps properties with type validation and sensible defaults.
2. Production Workflow: The Autonomous Work Order Pipeline
In our technical operations at Tygart Media, when an issue arises (e.g., automated cron alerts firing excessive emails or pilot registrations requiring team coordination), the human operator never writes a task card manually. Instead, the agent executes the following pipeline:
Problem Extraction: The agent detects the root cause from system logs or email history.
Schema Matching: The agent calls notion-search to locate our team’s active Work Order database.
Context Ingestion: Formats the ticket with standardized sections: Priority level, Assignee, Problem Summary, Execution Steps, and Acceptance Criteria.
Live Deployment: Executes notion-create-pages, returns the permanent Notion URL in chat, and logs the task ID across our session context.
3. Building the 4-Layer Autonomous Knowledge Stack
Knowledge graphs degrade over time if left unpruned. We implement automated reflection routines where the agent executes a monthly maintenance audit:
Duplicate Detection: Finding similar topic notes across different months and synthesizing them into a single canonical source.
Status Synchronization: Checking completed pull requests and closing out corresponding Notion task cards automatically.
Broken Citation Repairs: Updating URLs and standard definitions when external regulations change (e.g., California SB 253 amendments or NYC Local Law 97 rule updates).
Conclusion: The Ultimate Leverage for Solopreneurs & Teams
An Autonomous Second Brain transforms Notion from a passive digital graveyard into an active operating system for your mind and business. By combining the speed of modern reasoning models with the open standard of MCP, knowledge workers can achieve complete operational leverage—capturing every insight and managing complex operations with zero maintenance overhead.
For full architecture walkthroughs and custom enterprise agent implementations, browse our complete collection of technical playbooks on Tygart Media.
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.
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 this playbook and run commercial sales yourself. The free core is already public on GitHub. Clone it. Customize the emails. Work the list. Buy Now is the packaged kit: the complete Notion workspace, extra outreach sequences, proposal outlines, and ongoing updates, delivered by email after checkout.
Commercial restoration sales is a long game. The property manager you meet in March may not call until October, when a pipe bursts and your card is the one in the drawer. Owners who expect this to work like residential ads-and-calls quit early. Owners who treat it as 6–18 months of relationship development build pipelines that outperform marketing spend.
It is relationship-first, not inbound. You need a named list, a simple CRM habit, a value-first first contact, a cadence, and a first job you treat as an audition. That is the whole system.
Step 1: Build a Target Account List
Not “commercial accounts in general.” Specific companies and specific people. For each category, list 20–30 named prospects.
Property management companies. Director of Facilities or Property Manager, by name. LinkedIn is the research tool.
Large commercial facilities: hospitals, school districts, universities, municipal, industrial. Facilities Manager or Director of Operations.
Commercial insurance agencies: commercial lines account manager or producer.
Independent claims adjusters: firms handling commercial claims for multiple carriers.
Commercial GCs. GCs doing build-outs / TIs who hit restoration needs on active sites.
Account criteria before you add a name:
Properties large enough to generate restoration-eligible losses regularly
Decision-makers, not admin staff
At least one path: mutual connection, association (BOMA is the main one for commercial PMs), LinkedIn, or an event
Inside your service radius / response commitment
Pull your best 20 into a focus list. Those 20 get the cadence. Everyone else waits.
Step 2: Organize a simple CRM
Managing 100+ prospects in your head fails. Track at minimum:
Company, contact, title, email, phone
Last contact date and method
Next planned contact and action
Notes on situation, challenges, interests
Jobs referred, when work starts
ServiceTitan, JobNimbus, HubSpot free, or a disciplined spreadsheet. The tool matters less than updating it after every contact.
Step 3: Value-first contact (never a pitch)
Value-first contact — never a pitch.
First contact is a value offer that earns a meeting.
Property managers: complimentary water/mold vulnerability assessment on their highest-risk property. About two hours on site, then a short written report. No cost, no obligation, no hard sell.
Commercial adjusters: 15 minutes to learn the claims they handle and what they want in a preferred contractor. Questions, not a brochure.
Facility managers: share a relevant industry update (regulation, IICRC, insurance trend) with why it matters to their facility. No ask attached.
GCs: ask onto the bid list for restoration/remediation subs. Offer a mold survey on the next gut reno as the intro.
Property manager email (customize before you send)
Subject options: “Quick offer for [Building / Portfolio Name]” / “No-cost water & mold risk walkthrough. [Your Market]” / “Something useful for [Property Management Co] (not a sales deck)”
Hi [First Name],
I work with commercial property teams in [Market] on water, fire, and mold risk before losses escalate. I’m not writing to pitch a preferred-vendor slot.
I’d like to offer a complimentary vulnerability assessment on the one building in your portfolio that keeps you up at night — highest flood/leak exposure, oldest systems, or toughest after-hours logistics. About two hours on site, then a short written report with concrete recommendations. No cost, no obligation, no hard sell.
If useful, reply with a building name and a window that works, or a time for a 10-minute call to scope it.
Best,
[Your Name]
[Company]
[Phone] · [IICRC / response commitment, e.g. “IICRC-certified · 2-hour emergency response”]
Commercial adjuster email
Subject options: “15 minutes to learn how you work commercial losses” / “Question for preferred restoration partners” / “Learning call (not a capabilities deck)”
Hi [First Name],
I support commercial property claims in [Market] and I’m trying to get better at how independent adjusters actually evaluate restoration partners — documentation, response, communication under pressure.
Would you have 15 minutes in the next couple of weeks for me to ask questions (not run a sales pitch)? I come prepared; I’ll take notes and leave you alone unless you want a follow-up.
Happy to work around claim season. Coffee, Zoom, or phone — your call.
Thank you,
[Your Name]
[Company]
[Phone] · [Certifications / commercial experience one-liner]
Facility manager email (no ask)
Subject options: “Quick note on [regulation / IICRC / insurance trend] for [Facility Type]” / “Sharing this because it affects [Campus / Hospital / Plant] ops” / “No ask. just a relevant update”
Hi [First Name],
Saw [specific update] and thought of [Facility / Portfolio] because of [one concrete reason tied to their systems or occupancy].
Here’s the short version:
- [What changed]
- [Why it matters for facilities like yours]
- [One practical action: inspection, documentation, vendor protocol]
No ask attached — just sharing in case it’s useful for your team. If you ever want a second set of eyes on a water or mold scenario after hours, you already have my number.
Respectfully,
[Your Name]
[Company]
[Phone]
When you customize with Claude, give it your market, services, certifications, guaranteed response time, and one real differentiator. Keep emails under about 150 words. Remove leftover pitch language. Do not spam generic templates.
Step 4: Outreach cadence (top 20)
Monthly: low-friction: article share, LinkedIn comment, short check-in if appropriate
Quarterly: substantive: coffee, lunch, site visit, longer call
Annually: formal value presentation: capabilities, certifications, documentation standards, response commitment. Ask onto the preferred vendor / emergency protocol list.
Event-driven: storm, regulation, job near their facilities. Same-day if it is relevant.
Log after every touch: last date, method, next date, next action, owner, status (New, Cultivating, Warm, First job, Active account, Preferred vendor, Parked).
Event triggers worth a same-day note: major storm / freeze / flood in market; new regulation or IICRC update affecting their buildings; you completed a job near their portfolio; they posted a facility or hiring update; a mutual-connection intro.
Claude prompt you can use on the tracker: “Given my Top 20 list and last-touch dates, propose next week’s outreach calendar with one monthly touch per A-tier contact and flag anyone overdue for a quarterly meeting.”
Step 5: Convert the first job (the audition)
The first job is the audition — show up sharp on a real loss.
The first commercial job is the audition. Overdeliver. Every later job and referral traces back to that execution.
Before you roll
Confirm decision-maker and day-to-day site contact
Confirm response commitment in writing (hours to on-site)
Pre-stage equipment for the loss type
Assign a named PM, not “whoever is free”
Create the job folder: photos, moisture map template, daily log, COI packet ready
Response and presence
On site faster than committed. Record actual arrival time.
PM introduces self to client and any adjuster/GC on site
Same-day written scope outline or stabilization plan
PM on site daily while active, not only technicians
Moisture readings mapped by room/zone on water losses
Daily summary emailed to the client before they ask
Equipment log: what’s on site, why, pull dates
Change-order path explained before work expands
Communication and close-out
Client hears from you proactively at least once per day while active
Adjuster / GC included when they are in the loop
After-hours path confirmed (who answers at 2 a.m.)
Walk-through before demob. Final photos plus summary. Invoice clean, itemized, no surprises.
Personal follow-up from owner/BD by name within 48 hours
Ask once, lightly, about preferred-vendor / emergency protocol inclusion
Log the job as a reference case in the CRM, with permission notes
48-hour post-job note:
Hi [First Name],
Thank you for trusting us on [Site / Loss type]. We aimed to be early, clear, and boring on paperwork.
Attached/linked: final photo set + summary. If anything needs a second look, call me directly.
If useful, we’re glad to be added to your after-hours protocol for [portfolio / region].
[Your Name]
[Direct phone]
Score the audition internally, 1–5, on speed vs commitment, PM presence, documentation quality, proactive communication, invoice clarity, and likelihood of next call. If any dimension is 3 or below, debrief before the next commercial opportunity.
FAQ from the playbook
How long does it take? Usually 12–18 months from first contact to first job. Some are faster when timing meets a loss.
Why BOMA? Building Owners and Managers Association. Primary association for commercial property managers. Local chapter membership and events are efficient relationship builders.
Preferred vendor lists? Typically IICRC certs, GL/WC certificates, commercial references, sometimes a formal application. Adjuster relationships accelerate entry.
What PMs care about most? 24/7 emergency response with real times, IICRC techs, documentation quality, proactive communication. Vendors who need managing lose to vendors who manage themselves.
Ask Claude to customize the templates for your market, certifications, and response times.
Example prompt from the README: “Using PLAYBOOK.md and templates/outreach-emails.md, rewrite the property manager email for a mid-size metro, IICRC-certified water/fire/mold contractor with 2-hour emergency response.”
If you want the packaged kit
The free core is enough to start. Buy Now is the polished version: complete Notion workspace, extra outreach sequences, target account list templates, cadence tracker, proposal outlines, and ongoing updates. Delivered by email after checkout. Same Square button at the top of this page.
Secure checkout via Square — all major cards accepted
You can copy this method and build a real Business Continuity Plan yourself. You do not need a consultant. You need to start. Buy Now is the packaged Notion duplicate: the plan page plus the five databases already wired, delivered by email after checkout.
This walks a property manager, a restoration company, or any shop that needs a living plan (not a binder on a shelf) through the same structure. Fill the fields. Practice the tree. Update it every six months.
What a good BCP actually is
A good BCP is practiced — not laminated and forgotten.
It is not about the document. It is about the capability. A plan in a drawer is worthless. A plan your team has practiced, your vendors know about, and you update on a review cycle is the difference between a company that keeps running and one that does not.
Three frames sit under this template:
FEMA: essential functions must still get done during any disruption.
ISO 22301: deliver services inside acceptable timeframes.
Belfor Code Red ACT: Assessment, Communication, Training.
This template combines those into something you can build and maintain yourself. Restoration ERP-style cloud BCP tools exist if you need branded mobile apps and automated SMS. This is the planning foundation: the thinking, the structure, the documentation. That is the part that matters most, and you can customize it.
Start with the plan header
Write these six fields on page one. Do it today.
Plan Owner: a named person, not “the office.”
Organization: legal name people will see on the copy.
Last Updated: today’s date.
Next Review Date: six months from now.
Plan Version: start at 1.0.
Distribution: who gets a copy (owner, ops, office, key vendors).
Build it in this order
Build it in order — functions, risks, tree, vendors, drill.
Eleven sections. Do them in sequence. Each one is a how-to, not an essay.
Business Impact Analysis (BIA). Identify the functions that matter most and how long you can survive without them.
Risk Assessment. What threats exist, how likely, how severe.
Critical Functions and Recovery Objectives. RTO and RPO for every essential function.
Emergency Contact and Communication Tree. Who to call, in what order, through what channels.
Incident Response Procedures. Step-by-step for the first 24–72 hours.
Recovery Strategies. How to restore each critical function.
Facility and Infrastructure. Building systems, utility shutoffs, alternate locations.
Vendor and Contractor Directory. Pre-qualified emergency vendors with contracts on file.
IT and Data Recovery. Backups, cloud access, cybersecurity incident response.
Training and Exercise Log. Tabletop exercises, drills, lessons learned.
Plan Maintenance and Review. Keep the plan alive.
How to fill Critical Business Functions
Make one row per function. Restoration shops usually start with dispatch / first notice, mitigation crews, equipment, claims / documentation, billing, and payroll. Use the real names you use in the shop.
For each function, fill:
Function Name
Department. Operations, Finance / Accounting, Sales / Business Dev, IT / Technology, HR / People, Legal / Compliance, Customer Service, Facilities, or Executive
Affected Functions: which rows from the functions table this hits
Current Mitigation: what you already have
Additional Mitigation Needed: the gap
Insurance Coverage. Fully Covered, Partially Covered, Not Covered, Unknown
Owner, Last Reviewed, Notes
Start with the threats you have already lived: a freeze, a key tech leaving, a software outage, a shop fire, a Category 3 loss at your own building. Then add the ones you have not lived yet.
How to fill the Communication Tree
One row per person. Call Order 1 is the first call. If you cannot reach them, you call their Backup Person.
Fields:
Name, Role (Plan Owner, Executive Team, Department Head, Team Lead, Key Employee, Board / Ownership, or External: Legal, Insurance, IT, Restoration, Government, Media)
Phone – Primary and Phone – Alternate
Email, Location
Call Order (number)
Backup Person
Responsibilities in Crisis
Can Authorize Spending (yes/no)
Can Speak to Media (yes/no)
Print a copy. Put one in the go-bag and one at the shop. A tree that only lives in a laptop fails when the laptop is in a flooded office.
How to fill the Vendor Directory
Pre-qualify before you need them. Categories in the template: Restoration / Mitigation, General Contractor, Plumbing, Electrical, HVAC, Roofing, IT / Cybersecurity, Data Recovery, Security / Guard, Cleaning / Janitorial, Temporary Staffing, Equipment Rental, Document Recovery, Environmental / Hazmat, Legal, Insurance Adjuster, Other.
For each vendor: name, contact, phone, email, service area, 24/7 available, response time (Under 1 hour through Next day, or Unknown), contract on file, contract expiry, rate notes, rating (Excellent through Do Not Use), last used, notes.
If Contract on File is no, that is this week’s homework, not a crisis-day task.
How to run a tabletop (Training & Exercise Log)
Tabletop drill: the log proves you trained, not just wrote.
A BCP you have never practiced is a draft. Log every exercise.
Type. Tabletop Exercise, Walk-Through, Functional Drill, Full-Scale Exercise, Training Session, or After-Action Review
Scenario: the disaster you simulated
Key Findings: what worked, what failed, what surprised you
Action Items: specific improvements
Status. Scheduled, Completed, Cancelled, Action Items Open, All Actions Closed
Next Exercise Due
Pick one P1 function and one High risk. Walk the first 24 hours out loud with the people on the tree. Write what broke. Close the action items before the next review date.
The other sections, short
Incident response (first 24–72 hours): who declares the incident, who calls the tree, who talks to staff and customers, who authorizes spend, where you meet if the shop is unusable.
Recovery strategies: one paragraph per P1/P2 function. Point at the Alternate, the Systems Required, and the vendor who can stand it up.
Facility: shutoff locations, generator, alternate location, key box, who has after-hours access.
IT and data: where backups live, who can restore, what happens if email or the CRM is down, how you handle a cyber incident without guessing.
Maintenance: review date on the header is a real date. After any real incident or any exercise, bump the version.
If you want the packaged Notion workspace
You can build every table above in a spreadsheet. Buy Now is the Notion duplicate with the plan page and the five databases already built (Critical Business Functions, Risk Assessment, Emergency Contact & Communication Tree, Vendor & Contractor Directory, Training & Exercise Log). Delivered by email after checkout. 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.
Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Score the 20 statements. Count the checks. Name your worst zone. Buy Now is the packaged Notion page you duplicate and fill in, so you are not rebuilding the scorecard from a blank doc.
Stop guessing. Start detecting. This is the entry diagnostic in the Profit Detective toolkit. Five revenue leak zones. Four statements each. Five minutes. You walk out with a Leak Index (0-100), your #1 zone, and a rough yearly dollar figure.
How to score
Five zones. Score honest. Fix the biggest leak first.
Check each statement that is true of your business today. Each check is a leak. Count them at the bottom. Total checks out of 20, then multiply by 5 to get your Leak Index.
Zone 1: Estimating & scope
Money left in the estimate. The leak here is invisible because you never see the dollars you did not ask for.
We regularly find scope we forgot to bill after a job closes.
Estimators don’t consistently capture every line item the carrier allows.
We rarely review estimate-vs-final variance by estimator.
We discount or eat change orders to keep the adjuster happy.
Zone 2: Job costing & margin
Zone 2: job costing & margin — where quiet leaks hide.
Jobs that cost more than you think. Most shops cannot name true margin on the job they finished last Tuesday.
We don’t know true gross margin on a job until weeks after it closes.
Labor hours routinely run over what we estimated.
Equipment and materials aren’t tracked back to specific jobs.
We’ve finished jobs that lost money and didn’t catch it early.
Zone 3: Cash flow & collections
Work done, cash not collected. You can be profitable on paper and still broke.
Carrier or TPA payments routinely take longer than they should.
We carry receivables we’ve quietly stopped chasing.
We’ve floated payroll on a credit line to cover slow collections.
We have no standard follow-up cadence for unpaid invoices.
Zone 4: Sales & conversion
Leads in, jobs lost. A conversion problem and a marketing problem have different fixes. You cannot tell them apart if you do not know the rate.
We don’t know our lead-to-job conversion rate.
Inbound calls sometimes hit voicemail during business hours.
We don’t track which marketing actually produced our best jobs.
We have no system to follow up on quotes that didn’t close.
Zone 5: Leadership & overhead
Zone 5: leadership & overhead — 1-3-1 stops owner bottlenecks.
The owner is the bottleneck. This zone caps the whole pyramid, and it is the one owners least want to investigate.
The business can’t run a full week without the owner.
We don’t review one shared KPI as a team every week.
Overhead has crept up but we haven’t re-examined it in a year.
Every important decision funnels through one person.
Your Leak Index
Total checks: ___ / 20. Multiply by 5. That is your Leak Index (0-100).
0-20 Tight ship. Minor seepage. Tighten the few gaps.
21-45 Active leak. You are losing real money in 1-2 zones.
46-70 Major leak. The profit is pouring out. Pick your worst zone now.
71-100 Hemorrhaging. This is the #1 threat to the business.
Estimate the dollars
The scorecard’s teaching math: shops at your score typically leak about (Leak Index ÷ 100) × 14% of revenue. Multiply by your annual revenue for a rough yearly figure. Illustrative. Not a guarantee.
Write down the zone where you checked the most boxes. That is where you start. One zone at a time. The owners who try to plug all five at once plug none.
What to do with the result
Write your Leak Index and your worst zone on a card. You will carry those two things into any later work.
Pull your trailing-12 P&L and write your actual gross margin % (gross profit ÷ revenue). If you cannot find it in under 10 minutes, that is a finding.
Write one sentence: the story you have been telling yourself about profitability that you are now going to test against evidence.
If Zone 2 won, run last 10 closed jobs through a job-costing table (revenue, labor, equipment, materials, subs). If Zone 3 won, age your AR and total 60+ and 90+. If Zone 5 won, run an owner-dependency pass: what breaks if you vanish for 30 days.
The playbook’s rule: every restoration shop leaks somewhere. The only variable is whether you are looking. Evidence over opinion. Follow the money. Assume a leak exists.
If you want the packaged scorecard
You can run the 20 statements on a napkin. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate), check the boxes, and the Leak Index and dollar estimate sit on the same page. Same Square button at the top of this page.
