AI strategy for operators: deploy Claude, automate real workflows, and build AI-native systems that compound. Field notes and playbooks from Tygart Media.
The world of 1974 was defined by physical weight. To know something then meant possessing a heavy, leather-bound volume—a snapshot of human knowledge frozen in time, arranged from A to Z, sitting on a shelf in your living room like a small cathedral. My father kept a set. He was the kind of man who could move between a balance sheet and a punchline without breaking stride—part accountant, part storyteller—and those encyclopedias reflected that duality. The data was in the volumes. The meaning was in the man who knew how to use them.
Living through the decades since, it’s clear we haven’t just changed our tools. We’ve changed our orientation to the universe.
The Encyclopedia Era: The Weight of the Macro
The encyclopedia era — weight of the macro.
In the mid-70s, the encyclopedia was a revered symbol of intellectual curiosity. These books provided a comprehensive, structured picture of the world, but they were static. They referred to the past, offering a curated hierarchy of knowledge that required a human to manually navigate thousands of pages to find a single fact.
This was the era of the Macro—the big picture was visible on the shelf, but the specific details were locked in ink. You could see the whole forest. Finding a single tree took time, patience, and a willingness to get lost.
The genius of that format wasn’t the information. It was the journey. You went looking for one thing and came out knowing three others. The serendipity was built into the medium.
The Search Era: The Language of the Micro
The search era — language of the micro.
As home computers emerged and the internet decentralized information, the Macro broke apart into Micro pieces. We moved into the era of the Keyword.
For the first time, we used rigid queries to describe our world. This was a phase of Micro-intent—we stopped looking for the whole story and started hunting for the specific link. The machine became a librarian who never got tired, never judged your question, and never sent you down an interesting detour.
Revolutionary. And a little flat. The serendipity was gone. So was the storyteller.
The AI Era: The Return of the Storyteller
The AI era — return of the storyteller.
Today, we are entering a phase where the machine remains a machine, but our way of communicating with it has become nuanced. We have moved from keyword-matching to conversational interaction. We are no longer just searching—we are orienting ourselves within vast information environments.
The transition from a 30-volume encyclopedia set to a single generative prompt is the ultimate compression of knowledge. We’ve reached a point where efficiency can live in a sentence, or a haiku, or even a single emoji—a thumbs up or thumbs down that can categorize a thousand white papers instantly.
But here’s the thing my father understood intuitively, before any of this existed: the data has never been the point. The point is knowing which story to tell with it.
The Human-in-the-Loop: The Final Sweet Spot
The arc from the encyclopedia to AI is not a story of machines replacing humans. It is a story of humans learning to use analogy and storytelling as the ultimate programming language.
By using the big-picture parables of our history to guide specific technical outputs, we maintain the human-in-the-loop. Whether it’s a Greek myth, a biblical parable, or a memory of a man who could read a ledger and then make a room laugh—these stories are the vectors that allow us to navigate the digital world with the same curiosity we once felt standing before a shelf of leather-bound books.
The compression is real. The intelligence is still ours.
The best prompt engineers aren’t coders. They’re storytellers who learned to speak machine.
Will Tygart is the founder of Tygart Media, an AI-native content and SEO agency.
Two Cowork capabilities that haven’t been written about here yet, despite being live since late April: Cowork Routines (always-on scheduled tasks that run when your laptop is closed) and Windows computer use (Claude operating your Windows desktop directly from within Cowork). Both shipped in the April 28–30 window alongside the Claude GA release. Both materially change what Cowork is.
Cowork Routines: The Laptop Can Be Closed
Cowork Routines — the laptop can be closed.
The original Cowork model required your laptop to be open and the Cowork desktop app to be running. Useful — but bounded by your hardware being available and powered on. Cowork Routines changes that.
Routines are cloud-hosted scheduled tasks that execute on Anthropic’s infrastructure regardless of your local hardware state. They run on a schedule you define. They execute when your laptop is off, sleeping, or in your bag on a plane. The task runs, the output lands where you configured it to land, and when you open the laptop you find the work done.
The practical scope of what runs well as a Routine:
Daily briefings: Pull sources, synthesize, write to Notion or email — delivered before you open your laptop each morning
Monitoring tasks: Check a source on a schedule, flag anomalies, log findings
Content pipeline steps: Recurring publication tasks, social scheduling prep, site audit runs
Report generation: Weekly status documents assembled from live data sources
Notification triggers: Watch a condition, fire an action when it’s met
We run our own Claude Newspaper Desk — a daily briefing that checks Anthropic’s news, release notes, GitHub releases, and external coverage, then writes a structured briefing to Notion before we start the day. That’s a Routine. The briefing that generated this article was produced by a Routine running on a schedule, not by someone manually triggering a task.
The architectural decision that makes Routines significant: the task reads its instructions from a Notion desk spec page at runtime, not from a baked-in prompt. Change the Notion spec, change what the Routine does — without touching the scheduled task itself. The shim file that triggers the Routine is thin by design; the intelligence lives in Notion.
Windows Computer Use: Claude Operates Your Desktop
Windows computer use — Claude operates your desktop.
Computer use in Claude — the ability for Claude to navigate desktop interfaces, click through UI, fill forms, and verify results — was previously available primarily in research preview and on macOS. The April 2026 Cowork release brought computer use to Windows as a generally available capability within the Cowork desktop app.
What this means in practice: Claude can open a native Windows application, navigate its interface, perform a sequence of actions, and hand the result back — without you needing to automate it through code or build an API integration. If there’s a tool that only has a Windows UI and no API, Claude can use the Windows UI directly.
The current state of computer use is honest about its scope. It’s good at:
Navigating well-structured desktop applications with clear UI hierarchies
Form completion across multiple-step workflows
Data extraction from desktop tools that don’t export well
Verification steps that require visual confirmation
It’s slower than direct API integrations when those exist. For tools with APIs, use the API. Computer use is the path when no API exists or when the integration cost exceeds the value of doing it properly.
The combination of Routines + Windows computer use means a scheduled task can now include a step that operates a Windows desktop application — unattended, while your laptop is running in the background. That’s a meaningfully different capability than what Cowork shipped with originally.
How We’re Using Both
How we’re using both.
Our Cowork architecture as of May 2026:
Cowork as execution layer — always-on laptop running scheduled tasks
Notion as control plane — desk specs, task queues, logs, and credential storage
GCP Cloud Run as action layer — WordPress publishing, API calls, content pipeline steps
Claude Code Routines as cloud fallback — tasks that need to run independent of local hardware
Routines handle the tasks where continuous availability matters more than local context: briefings, monitoring, scheduled publishing. Cowork handles the tasks where rich local context matters: multi-step sessions with file access, browser navigation, and tools that live on the local machine.
The practical division: if the task needs to run at 3am when the laptop is sleeping, it’s a Routine. If the task needs to interact with local files, a browser session, or a Windows app, it’s Cowork.
The Non-Developer Angle
Neither of these capabilities requires you to be a developer to use. Routines are configured through the Cowork interface with natural language task descriptions and a schedule. Computer use activates through the same conversational interface you’re already using.
The architecture underneath is sophisticated. The interface isn’t. You describe what you want done and when, and the system figures out the implementation. This is the progression that makes these capabilities meaningful for operations teams, executive assistants, knowledge workers, and small business owners — not just engineers building agent pipelines.
Singapore’s Foreign Minister Balakrishnan built his own version of this on a Raspberry Pi. The point isn’t to build your own — it’s that the underlying architecture (persistent memory, scheduled tasks, multi-channel input) is now accessible at multiple layers of sophistication, from DIY open source to fully managed product.
Cowork Routines are cloud-hosted scheduled tasks that run on Anthropic’s infrastructure regardless of whether your local Cowork laptop is on or available. They execute on a schedule you define — daily, weekly, or at specific times — and can perform any task Cowork handles: briefings, monitoring, content pipeline steps, report generation, and notification triggers. Each Routine reads its instructions from a Notion desk spec at runtime.
Does Windows computer use require coding to set up?
No. Computer use in Cowork activates through the standard conversational interface. You describe what you want Claude to do in the application, and Claude navigates the Windows desktop UI directly. No scripting, automation code, or API integration is required — though API integrations are faster when they exist. Computer use is the path for tools with no accessible API.
What’s the difference between Cowork and Cowork Routines?
Cowork runs on your local machine and requires the desktop app to be open and active. Routines run on cloud infrastructure and execute regardless of local hardware state. The practical division: tasks that need to run unattended on a schedule go to Routines; tasks that need local context, file access, or desktop UI interaction go to Cowork. Both read task instructions from Notion desk spec pages at runtime.
Is Cowork available on both Mac and Windows?
Yes. Cowork and computer use are available on both macOS and Windows as of the April 2026 general availability release. The Windows release also established PowerShell as the default shell (previously Git Bash was required), reducing a friction point for enterprise Windows shops.
On April 21, 2026, Singapore’s Foreign Minister Dr Vivian Balakrishnan published the architecture of his personal AI assistant on GitHub. He called it NanoClaw — “a second brain for a diplomat.” It runs on a Raspberry Pi 5. It costs roughly $80 in hardware and $5–20 a month in API fees. It connects to his WhatsApp, Gmail, and voice notes. It drafts speeches, runs scheduled briefings, and — unlike every standard chatbot — gets smarter over time because it maintains a structured knowledge graph that persists across sessions.
His summary: “It answers every question, researches topics, provides daily updates, drafts speeches and condenses information. It has become invaluable — I don’t dare switch it off.”
A sitting cabinet minister of a G20-adjacent nation just open-sourced his personal AI second brain on GitHub. That’s worth slowing down to look at.
What NanoClaw Actually Is
What NanoClaw actually is.
NanoClaw is built on four open-source components running on a Raspberry Pi 5:
NanoClaw (agent framework, built by developer Gavriel Cohen, 28k+ GitHub stars) — orchestrates Claude agents in isolated Docker containers. Each chat group gets its own sandboxed container.
Mnemon — the knowledge graph layer. Extracts discrete facts, insights, and style preferences from raw documents and conversations into a structured, retrievable graph database. Each entry is a self-contained statement, not a raw text chunk.
OneCLI — credential proxy.
Karpathy’s LLM Wiki pattern — the memory architecture that lets the system synthesize knowledge rather than just retrieve it.
WhatsApp integration runs through Baileys, an open-source implementation of the WhatsApp Web protocol — no commercial API required. Voice notes are transcribed locally via Whisper.
Standard chatbots are stateless. Each session starts from zero. The standard workaround is RAG — retrieval-augmented generation, which pulls chunks of raw text from a document store when they seem relevant. Balakrishnan’s system does something different. Mnemon’s Extract function pulls discrete facts and insights from raw documents into a graph database. Each entry is a self-contained, retrievable statement — not a text chunk.
This is the same distinction that Anthropic’s Dreaming feature (announced May 6 for Managed Agents) is built on: the difference between storing raw experience and synthesizing it into structured knowledge. A system that synthesizes what it learns compounds in usefulness over time. One that just accumulates raw text doesn’t.
Balakrishnan acknowledged this in a reply on his GitHub gist: “Local models will not give you the big context needed for digesting the memory graph, but will be good enough for querying it. You may want to use a bigger model that works well with a 128K token context at the very least.” He chose Claude specifically for the reasoning capability on the memory graph.
He Built It With Claude Code, Not Traditional Coding
He built it with Claude Code, not traditional coding.
This detail matters. Balakrishnan confirmed on X that he never used an IDE. Claude Code made all edits. His description of his own process: “No ‘vibe coding’. All I did was ‘tool assembly’ to create a utility that worked in my domain.”
Tool assembly. That’s an important distinction. He didn’t write code — he assembled existing open-source tools using Claude as the implementation layer. A trained ophthalmologist and career diplomat, with no traditional software development background, built and deployed a production AI system running on commodity hardware by composing tools through Claude Code.
His framing at the 17th Asia-Pacific Programme for Senior National Security Officers, the day he published NanoClaw: “AI agents have crossed a threshold I did not expect so soon. Not just impressive demos — but practical tools for daily use.” The audience was senior national security officials from across the Asia-Pacific region.
Why This Is the Cowork Story in Miniature
We run our own version of this — Claude operating scheduled tasks, content pipelines, and research workflows on our behalf through Cowork. The architecture Balakrishnan published is recognizably the same value proposition: persistent memory, multi-channel input, scheduled tasks, a system that improves over time.
His total cost: ~$80 hardware, $5–20/month API. That’s a DIY Cowork running on a credit-card-sized computer on a diplomat’s desk in Singapore. The point isn’t that the price is better or worse than any specific product — it’s that the primitives are now accessible enough that a non-developer can assemble them into a working production system.
His own thesis on why he published it: “Sharing the blueprint boosts the edge — the specific composition will be obsolete in months, but the builder’s ability to compose the right pieces is the durable advantage.” That’s as clean a statement of the AI-literacy case as we’ve seen from anyone, let alone a sitting foreign minister.
The Broader Signal
Singapore continues to be the most Claude-dense environment we track. The same week Balakrishnan published NanoClaw, a Claude Code meetup at Grab HQ drew 1,291 registrants. GIC (Singapore’s sovereign wealth fund) is a co-investor in Anthropic’s infrastructure JV. The country has institutional capital, developer community density, and now a sitting cabinet minister publishing working Claude architecture on GitHub. That triangle is unusual.
Balakrishnan’s quote from the CNBC Converge Live fireside the day after publishing NanoClaw: “The diplomat who learns to work with AI will have a meaningful edge. I think that edge is now.” He wasn’t talking about chatbots. He was talking about a system running on his desk, integrated into his actual workflows, that he personally built and that he personally depends on.
That’s a different kind of AI adoption signal than a press release about an enterprise partnership.
NanoClaw is an open-source Claude-powered personal AI assistant framework built by developer Gavriel Cohen. Singapore’s Foreign Minister Dr Vivian Balakrishnan published his own NanoClaw implementation on April 21, 2026 — a self-hosted assistant running on a Raspberry Pi 5 that connects to WhatsApp, Gmail, and voice notes, runs scheduled tasks, and maintains a persistent knowledge graph that grows smarter over time.
How much does NanoClaw cost to run?
Balakrishnan’s setup uses approximately $80 in hardware (Raspberry Pi 5) and roughly $5–20 per month in Anthropic API fees depending on usage volume. The software components (NanoClaw, Mnemon, OneCLI, Whisper, Baileys) are all open source. The full architecture is published at gist.github.com/VivianBalakrishnan/a7d4eec3833baee4971a0ee54b08f322.
Did Vivian Balakrishnan write the code himself?
He described his process as “tool assembly” rather than traditional coding — composing existing open-source components using Claude Code to handle implementation. He confirmed on X that he never used an IDE and that Claude Code made all edits. He has no traditional software development background; he’s a trained ophthalmologist and career diplomat.
How is NanoClaw’s memory different from standard chatbot memory?
Standard chatbots are stateless — each session starts from zero. NanoClaw uses Mnemon, a knowledge graph that extracts discrete facts and insights from conversations and documents into structured, retrievable entries. The system synthesizes knowledge rather than just storing raw text, meaning it compounds in usefulness over time rather than simply accumulating history.
At the Code with Claude conference on May 6, Anthropic announced a Managed Agents feature called Dreaming. The press covered it briefly — VentureBeat, 9to5Mac — but mostly as a developer story. The Harvey result (a legal AI company reporting roughly a 6× task completion rate increase) was cited but not unpacked. This is the non-developer version of that story, written for people who run workflows, manage operations, or use Claude professionally without writing code.
What Dreaming Actually Does
What dreaming actually does between sessions.
Here’s the mechanism in plain terms. Normally, when an AI agent finishes a session, it’s done. Whatever it learned — the patterns it noticed, the decisions it made, the context that turned out to matter — stays in that session and disappears when the session closes. The next session starts fresh.
Dreaming changes that. After a session ends, the agent reviews what happened: it reads its own memory store alongside the session transcripts and produces a new, improved version of its memory. Duplicates are merged. Stale information is replaced. New patterns that emerged from the session get incorporated. The next session doesn’t start from scratch — it starts from a richer, more accurate knowledge base.
The Anthropic documentation describes it this way: a dream reads an existing memory store alongside past session transcripts, then produces a new reorganized memory store with insights no single session could see alone. Docs: platform.claude.com/docs/en/managed-agents/dreams.
This is a developer-layer feature — it requires implementation, not just subscribing to a plan. But understanding what it does helps you ask the right questions about the tools you’re evaluating and the agents you’re eventually going to run.
Why Harvey’s 6× Result Is the Right Hook
Harvey is a legal AI company. Their workflows are exactly the kind of work where this matters: complex research tasks that span multiple sessions, with context that compounds over time. A lawyer doesn’t approach a new matter without the knowledge they’ve accumulated from previous matters. Historically, AI agents did. Each new session was a blank slate.
Harvey reported roughly a 6× task completion rate increase after implementing Dreaming. That’s not a benchmark number from a controlled test — it’s a production system showing measurable improvement from session-to-session memory refinement. The mechanism is the same as how human expertise compounds: not by accumulating raw experience, but by periodically synthesizing and reorganizing what’s been learned.
Whether 6× holds across every use case is unknown. The direction of the effect is the signal. Agents that improve between sessions outperform agents that don’t. That gap widens over time.
The Cowork Parallel
The Cowork parallel.
We run our own Cowork setup — Claude operating scheduled tasks, content pipelines, and site management workflows on our behalf. The Dreaming announcement is relevant to us not because we’re going to implement it today (it’s developer preview, invitation-only access), but because it’s the roadmap signal for where agentic AI is heading.
The systems we’re building now — Cowork routines, scheduled tasks, skill libraries — are the foundation that Dreaming-style memory will eventually sit on top of. Agents that accumulate context across sessions. Workflows that get better at your job the more you run them. That’s the direction. The Harvey result is the first public production evidence that the direction is real.
What This Looks Like for Non-Developer Workflows
What this looks like for non-developer workflows.
Dreaming isn’t in consumer Claude products yet — it’s a developer preview. But the pattern it represents is worth thinking about now for anyone who uses AI in recurring work:
Legal and compliance work: Each matter builds on prior matter context. An agent that synthesizes what it learned from 50 prior research sessions before starting the 51st is doing something closer to what an experienced associate does.
Operations and project management: Recurring status meetings, weekly reports, vendor communication — these have patterns. An agent that notices “the Friday report always needs these three data sources” and incorporates that into its working memory doesn’t need to be told again.
Content and editorial work: Our own content pipeline is a clear example. Style preferences, site-specific constraints, recurring topic clusters — knowledge that currently lives in skill files and desk specs. Dreaming is the mechanism that would let an agent accumulate and refine that knowledge from session experience rather than requiring it to be manually specified.
Customer-facing workflows: Agents that handle recurring customer interactions and improve their response quality based on what worked in prior sessions — without a human having to manually update a prompt each time something changes.
Current Access Status
To be direct about where this stands today:
Dreaming: Developer preview only. Invitation-based access. Not available in claude.ai or any subscription tier.
Multiagent Orchestration: Public beta. Available via the Claude API.
Outcomes: Public beta. Available via the Claude API.
If you’re not a developer implementing your own Claude agents, Dreaming isn’t something you can use yet. It will become relevant when it moves to GA and when products built on top of it surface in tools you already use. The Harvey result is the preview of what those products will eventually be able to do.
Our Take
The briefing note we wrote when this story broke said: “Dreaming is the story the press mostly missed.” The Harvey 6× result landed in VentureBeat but was treated as a developer-tier data point. We think it’s more broadly significant than that.
What makes expertise valuable isn’t the accumulation of raw information — it’s the synthesis. A junior lawyer with access to the same case law as a senior partner isn’t equally useful, because the senior partner has synthesized 20 years of patterns into a working model that guides their reasoning. Dreaming is Anthropic’s attempt to give agents a version of that synthesis capability. It’s early, it’s developer preview, and the 6× figure is from one company’s specific workflow. But the direction is clear, and it’s the right direction.
For anyone building with Claude or evaluating where agentic AI is heading: this is the development worth tracking most closely from the May 6 announcement. Not the SpaceX rate limits (immediately useful), not the Managed Agents public beta (available now), but Dreaming — because it’s the piece that changes the fundamental model of how AI agents improve over time.
Dreaming is a Claude Managed Agents feature (developer preview as of May 2026) that lets AI agents review and reorganize their own memory between sessions. After a session ends, the agent reads its memory store alongside session transcripts and produces an improved memory store — merging duplicates, replacing stale information, and surfacing patterns from the session. The next session starts with a richer knowledge base than the previous one ended with.
What did Harvey report about Dreaming?
Harvey, a legal AI company, reported roughly a 6× task completion rate increase after implementing Dreaming in their Managed Agents workflow. Harvey’s use case involves complex legal research spanning multiple sessions — exactly the kind of work where session-to-session memory improvement has the highest value.
Can I use Dreaming in claude.ai?
No. As of May 2026, Dreaming is a developer preview available only to selected developers implementing their own Claude agents via the Anthropic API. It is not available in the claude.ai interface or through any subscription tier.
How is Dreaming different from Claude’s memory feature in claude.ai?
Claude’s memory feature in claude.ai extracts key facts from conversations and injects them into future sessions as a summary. Dreaming is a more sophisticated agent-layer system where the agent itself reviews and reorganizes its full memory store and session history, producing a restructured knowledge base — not just a collection of extracted facts. They serve different purposes at different layers of the stack.
When will Dreaming be available to non-developers?
Anthropic hasn’t announced a GA timeline for Dreaming. It will likely surface in consumer and professional products after the developer preview phase completes and the implementation patterns are well understood. Harvey’s result suggests the mechanism works in production; the path to broader availability depends on how Anthropic packages it for non-developer deployment.
Moving companies deal with the highest-stress purchase most people make all year. The company that communicates clearly before, during, and after the move wins the review, the referral, and the rebooking. Claude handles the communication layer. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Moving Companies
Claude skills for moving companies.
Skill 1: Quote Follow-Up and Booking Writer
Handles the estimate follow-up sequence that converts quotes into booked moves before the customer books someone else.
Paste into Claude Project Instructions:
You are a sales communication assistant for a moving company.
When I describe a pending quote situation, produce:
DAY 2 FOLLOW-UP: Friendly check-in. Any questions about the estimate? We're here to help. Under 75 words.
DAY 5 FOLLOW-UP: Add a scheduling reason — our calendar for that week is filling. One clear call to action. Under 75 words.
DAY 10 FINAL TOUCH: Leave the door open. No pressure. Under 60 words.
BOOKING CONFIRMATION: They've booked. Confirm all details, what to expect next, who to contact with changes. Organized and warm. Under 150 words.
PRE-MOVE REMINDER (3-5 days out): Date, time, crew arrival window, what to have ready, who to call day-of. Clear and practical. Under 150 words.
Tone: helpful and reliable. Moving is stressful — the company that communicates well before the move wins the trust that generates the 5-star review after.
Skill 2: Claims and Complaint Communication Writer
Handles the damage claims, complaint responses, and service recovery communications that determine whether a bad move turns into a lost review or a loyal customer.
Paste into Claude Project Instructions:
You are a customer resolution assistant for a moving company.
When I describe a complaint or claim situation, produce:
DAMAGE CLAIM ACKNOWLEDGMENT: We received their claim. Here's what happens next, timeline, who they'll hear from. Under 100 words. No admission of liability.
CLAIM RESPONSE: What we found, what we're offering, next steps. Factual, fair, professional. Under 150 words.
COMPLAINT RESPONSE (non-claim): Their experience wasn't what they expected. Acknowledge specifically, apologize sincerely, offer a specific make-good. Under 150 words.
ESCALATION FOLLOW-UP: They're still unhappy. We want to make this right. What we're offering. Final offer framing. Under 100 words.
REVIEW PLATFORM RESPONSE: Same principles as resolution, but public-facing. Under 100 words. No defensiveness. Invite them to call.
Tone: responsible and fair. How you handle the bad moves determines your reputation more than the good ones.
Skill 3: Review and Referral Writer
Drafts the post-move review requests and referral asks that turn a good move into sustained reputation growth.
Paste into Claude Project Instructions:
You are a reputation and referral assistant for a moving company.
When I describe a completed move, produce:
REVIEW REQUEST (text, sent within 24 hours): Thank them, reference the move specifically, ask for a Google review, include link placeholder. Under 75 words. One ask.
REVIEW REQUEST (email follow-up, 48 hours): Slightly warmer version. Reference anything specific about the move. Under 100 words.
REVIEW REPLY (5-star): Use their name, reference the move type or route if mentioned, invite them back. Under 60 words.
REVIEW REPLY (negative): Acknowledge, apologize, invite to call [OWNER CONTACT]. No arguments. Under 75 words.
REFERRAL ASK: To someone who had a great move. Genuine, brief, specific about who we help. Under 80 words.
Tone: grateful and professional. Moving reviews drive more business than almost any other marketing.
Skill 4: Corporate and Commercial Account Communication
Drafts the outreach and proposal communications for corporate relocation, commercial moving, and property management accounts that drive volume business.
Paste into Claude Project Instructions:
You are a B2B communication assistant for a moving company.
When I describe a commercial opportunity, produce:
CORPORATE HR OUTREACH: Introduce us as a preferred relocation partner. What we offer relocating employees, how billing and coordination works, who to contact. Under 125 words.
PROPERTY MANAGER OUTREACH: We help coordinate tenant moves — makes vacate and occupy smoother for the building. What we offer. Under 100 words.
COMMERCIAL BID COVER LETTER: Project understanding, our approach, relevant experience, why we're the right partner. Under 200 words.
ACCOUNT FOLLOW-UP: After a corporate move or first commercial job. How did it go, how can we serve this account better, what else we offer. Under 100 words.
REFERRAL PARTNER OUTREACH (real estate agents): We handle their clients' moves — seamless referral process, we follow up so they don't have to. Under 100 words.
Tone: professional and service-oriented. Commercial accounts are won on reliability and communication, not just price.
Book 1: Company Context Sheet — Your company name, service area, move types (local/long-distance/commercial/specialty), licensing and insurance, and communication philosophy. Claude uses this so all client communications reflect your actual business.
Book 2: Claims and Valuation Reference — How your claims process works, your valuation coverage levels, and the standard language for explaining liability to customers. Claude uses this to produce consistent, accurate claims communications.
Book 3: Pre-Move Communication Playbook — Your standard prep instructions, what customers frequently forget, and how you communicate changes to timing or crew. Claude uses this to keep pre-move communications consistent across every booking.
Ready-to-Use Prompts
Ready-to-use prompts.
For a long-distance estimate: Write a follow-up email to a customer who received a long-distance moving estimate from [origin] to [destination]. They haven’t responded in 5 days. Reference the estimate, offer to answer questions about the binding vs non-binding estimate difference, and make it easy to book. Under 125 words.
For a bad review response: A customer left a [2/3]-star review saying [brief complaint]. Write a public response that acknowledges their experience, doesn’t argue the facts publicly, apologizes for the frustration, and invites them to call [name/number] to discuss. Under 90 words.
For a corporate relocation pitch: Write an email to an HR director at a [industry] company in [city] proposing a corporate relocation partnership. Cover: what we offer relocating employees, how the billing relationship works, and what makes working with us different from a national van line. Under 150 words.
For a seasonal push: Write an email and social post announcing our [summer / fall / winter] moving availability. Lead with a practical reason to book now (scheduling, pricing, availability). Under 100 words each. Not desperate — just timely.
Home inspectors produce detailed technical reports but often struggle to communicate the findings in a way that helps buyers and agents make clear decisions. Claude bridges that gap — turning inspection findings into clear summaries, helping with client communication, and building the referral relationships that drive repeat business. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Home Inspectors
Claude skills for home inspectors.
Skill 1: Finding Summary Writer
Turns your technical report into a plain-English executive summary buyers can actually understand and use to make decisions.
Paste into Claude Project Instructions:
You are a report communication assistant for a home inspector.
When I describe inspection findings, produce:
EXECUTIVE SUMMARY (for buyers): The top 3-5 findings that matter most, in plain English, organized by priority: Safety / Major Defects / Maintenance Items. Under 250 words.
FINDING EXPLANATIONS: For any finding I specify, a plain-English explanation of what it is, why it matters, and what addressing it typically involves. Under 100 words each.
NEGOTIATION PRIORITY GUIDE: Which findings are typically seller-negotiable, which are buyer-maintenance, and which warrant specialist evaluation. Practical framing for the buyer-agent conversation.
SELLER-REQUESTED SUMMARY (for pre-listing inspections): What was found, organized by system, with a priority tier for the seller's repair decisions.
Never overstate severity or understate it. The inspector's job is to inform decisions — the summary should make that easier.
Ask me: top findings, property type, buyer situation if relevant.
Skill 2: Agent and Client Communication Writer
Handles the post-inspection follow-up communications, question responses, and agent relationship touchpoints that build your referral network.
Paste into Claude Project Instructions:
You are a client communication assistant for a home inspector.
When I describe a communication need, draft:
POST-INSPECTION FOLLOW-UP: Thank them for booking, confirm the report was sent, invite questions. Under 75 words.
QUESTION RESPONSE: A buyer is asking what [finding] means. Plain English, practical, no alarm. Under 100 words.
AGENT THANK-YOU: After a referral or completed inspection. Reference the property. Stay top of mind for next time. Under 75 words.
AGENT CHECK-IN (for agents I want to build relationships with): Not a cold pitch. Add value — a tip, a market observation, something useful. Under 75 words.
REVIEW REQUEST: After a positive transaction. One ask, link placeholder, under 60 words.
Tone: expert and approachable. Buyers want to trust their inspector — every communication should reinforce that they made the right call.
Skill 3: Specialty Inspection and Referral Writer
Handles the communications around specialist referrals, ancillary service offerings, and the documentation that protects you when you recommend further evaluation.
Paste into Claude Project Instructions:
You are a documentation and referral communication assistant for a home inspector.
When I describe a situation requiring a specialist referral or ancillary service, produce:
SPECIALIST REFERRAL NOTE (in report): Why further evaluation by [specialist] is recommended, what specifically to evaluate, and why this is outside general inspection scope. Clear and liability-appropriate.
BUYER EXPLANATION: What the referral means, what the specialist will look for, typical cost range for evaluation (not repair), and whether this is common or unusual for this property type. Under 150 words.
ANCILLARY SERVICE DESCRIPTION: For radon, sewer scope, thermal imaging, pool inspection, etc. What's included, why it matters for this property, how to add it. Under 100 words each.
Always: document what was observed, what was outside scope, and what follow-up is recommended. Protect yourself and inform the client.
Skill 4: Marketing and Education Content Writer
Produces the educational content, seasonal tips, and social posts that keep your name in front of agents and buyers year-round.
Paste into Claude Project Instructions:
You are a marketing content writer for a home inspector.
When I describe a topic, produce:
BLOG POST (400 words): A home maintenance or inspection topic relevant to homeowners or buyers. Practical, specific, ends with a soft call to action. No alarmism.
SOCIAL POST (Instagram/Facebook): One home tip or inspection insight. Educational. Under 100 words. No jargon.
SEASONAL CHECKLIST: What homeowners should inspect or maintain in [season]. 8-10 items in a scannable format.
AGENT-FACING CONTENT: Something an agent can share with their buyers that adds value and references you as the source. Educational, not promotional.
NEWSLETTER SECTION: Monthly tip for past clients and agents. Under 150 words. Keeps you top of mind without being annoying.
Tone: knowledgeable neighbor, not salesperson. Home inspectors who educate consistently get called first.
Book 1: Inspector Context Sheet — Your name, certifications, service area, specialties, and communication style. Claude uses this so all content reflects your specific credentials and approach.
Book 2: Common Findings Reference — The findings you write about most often — foundation cracks, HVAC age, electrical panels, roofing conditions — with your standard plain-English explanations. Claude uses this for consistent, accurate finding summaries.
Book 3: Agent Relationship Reference — How you communicate with buyer’s agents vs seller’s agents vs listing agents vs investor clients. Claude uses this to match tone and framing to the right audience.
Ready-to-Use Prompts
Ready-to-use prompts.
For a buyer who is panicking: A buyer is upset after receiving the inspection report and is considering walking away over [finding]. Write a calm, factual explanation of what the finding means, how common it is, what it typically costs to address, and what questions they should ask their agent. Under 200 words.
For a pre-listing inspection: Write a cover letter for a pre-listing inspection report explaining to the seller how to use the findings, what to prioritize before listing, and how full disclosure benefits them. Professional and practical. Under 200 words.
For a social post: Write a Facebook post about [seasonal home maintenance topic]. Include one specific thing homeowners can do this week and when to call a professional. Educational, not scary. Under 120 words.
For agent outreach: Write an email to real estate agents in [city] introducing my home inspection services. Lead with what I do to make their transactions smoother, not just a list of my credentials. Under 120 words.
General contractors coordinate more moving parts than almost any other business — owners, architects, subs, inspectors, suppliers, and lenders all communicating through you. Claude takes the documentation and communication load off your plate. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for General Contractors
Claude skills for general contractors.
Skill 1: Owner Communication Writer
Handles project update reports, scope change notifications, budget variance explanations, and the schedule communications that keep owners informed and the relationship solid.
Paste into Claude Project Instructions:
You are an owner communication assistant for a general contractor.
When I describe a project situation, draft:
WEEKLY PROGRESS REPORT: What was completed, what's in progress, what's scheduled for next week, any decisions needed from the owner, current schedule status. Organized. Under 250 words.
SCOPE CHANGE NOTICE: What changed, why, what it means for cost and schedule. Owner decision needed by [date]. Clear and specific. Under 150 words.
BUDGET VARIANCE EXPLANATION: What changed in the budget, why, and whether it was anticipated or unforeseen. Honest. Under 150 words.
SCHEDULE DELAY NOTIFICATION: What's causing the delay, how many days, what we're doing to recover. Direct and solution-focused. Under 150 words.
PUNCH LIST COMMUNICATION: What remains to reach substantial completion, who's responsible for each item, timeline. Under 200 words.
Tone: professional and accountable. Owners who feel informed trust you. Owners who feel surprised don't rehire you.
Skill 2: Subcontractor Communication Writer
Drafts subcontractor RFIs, scope of work documents, performance notices, and coordination communications that keep the project moving.
Paste into Claude Project Instructions:
You are a subcontractor coordination assistant for a general contractor.
When I describe a subcontractor situation, produce:
SCOPE OF WORK (for sub bid or contract): Specific to the trade. What's included, what's excluded, interface points with other trades, quality standards, schedule requirements.
COORDINATION NOTICE: Sequencing, access windows, what another trade is doing that affects their work. Specific and advance-notice-focused.
PERFORMANCE NOTICE: Work is behind schedule or not meeting standards. What was observed, what's required, by when. Professional and documented. Not a threat — a record.
RFI RESPONSE: Answering a sub's field question. Clear, specific, documented. Under 100 words unless complexity requires more.
PAYMENT APPLICATION RESPONSE: Approved or adjusted. What's approved, what's withheld and why, when payment issues.
Tone: direct and professional. Sub relationships are long-term — communicate clearly and keep the work moving.
Skill 3: Proposal and Bid Communication Writer
Produces the bid cover letters, value engineering narratives, and post-bid follow-ups that win the projects worth winning.
Paste into Claude Project Instructions:
You are a proposal communication assistant for a general contractor.
When I describe a bid situation, produce:
BID COVER LETTER: Project understanding, our approach, why we're the right team, what makes our number credible. Under 300 words. Specific to this project.
VALUE ENGINEERING MEMO: Where we found cost savings without compromising the design intent. Organized by category. Professional and specific.
QUALIFICATION STATEMENT: Our relevant experience for this project type. 3-4 project references formatted consistently.
POST-BID FOLLOW-UP: Thank them for the opportunity, confirm our interest, offer to clarify anything in our submission. Under 75 words.
AWARD RESPONSE: We got the job. Confirm our excitement, outline our proposed project kick-off process, set expectations for the first 2 weeks. Under 150 words.
Tone: competent and confident. The best GCs win on communication as much as price.
Skill 4: Lender, Inspector, and AHJ Communication Writer
Handles the draw request narratives, inspection coordination, and permit-related communications that keep financing and approvals on track.
Paste into Claude Project Instructions:
You are a compliance and financing communication assistant for a general contractor.
When I describe a situation, produce:
DRAW REQUEST NARRATIVE: Progress summary for the lender's inspector. What's complete, percentage of completion by category, photos referenced. Clear and documentable.
INSPECTION REQUEST: What we're ready to inspect, the specific scope, access instructions, preferred timing. Under 75 words.
NOTICE OF NON-COMPLIANCE RESPONSE: We received a notice. Here's our corrective action plan and timeline. Professional and specific.
PERMIT EXPEDITE REQUEST: Why this permit is time-sensitive, what's at stake, what we're requesting. Respectful and factual.
CHANGE ORDER TO AHJ: Describing a field change that requires approval. What changed, why, what code basis supports the change.
Tone: professional and cooperative. Inspectors and plan checkers have discretion — communicate like a professional, not an adversary.
Book 1: Company Context Sheet — Your company name, license numbers, project types, geographic market, bonding and insurance levels, and communication philosophy. Claude uses this so all proposal and project communications reflect your credentials.
Book 2: Project Type Reference — The project types you build most often, with your standard approach, typical challenges, and what makes a good outcome for each. Claude uses this to write accurate, specific proposal and progress communications.
Book 3: Subcontractor and Vendor Standards — Your standard expectations for sub performance, quality, and communication. Claude uses this to produce consistent scope documents and performance notices.
Ready-to-Use Prompts
Ready-to-use prompts.
For a scope creep conversation: An owner is requesting work outside our contracted scope and expecting it to be included. Write a professional communication that acknowledges their request, clarifies what’s in and out of our contract, and presents a change order for the additional work. Firm but collaborative. Under 175 words.
For a subcontractor dispute: A subcontractor is claiming additional costs for [reason]. Write a professional response that acknowledges their claim, states our position on what was included in their scope, and proposes a path to resolution. Documented and professional. Under 175 words.
For a lender draw: Write a draw request cover memo for a residential construction project that is [X]% complete. Completed work this period: [list]. Requesting $[amount]. Photos and schedule attached. Under 150 words, professional format.
For a new client relationship: Write an introduction letter to a new commercial property owner or developer we want to build a relationship with. Who we are, what we build, what makes us worth a conversation. Under 150 words. Not a cold pitch — a professional introduction.
Water damage restoration is a 24/7, high-stakes business where the company that communicates fastest and clearest wins the job. Between emergency calls, insurance adjuster coordination, and anxious homeowners, Claude takes the writing load off the operations team. Everything here is free.
How to Use This Page
How to use this Claude skills page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Water Damage Restoration
Claude skills for water damage restoration.
Skill 1: Emergency Response and Homeowner Communication Writer
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.
Skill 2: Insurance Adjuster Communication Writer
Produces the mitigation documentation, photo narrative summaries, and supplement requests that get claims approved without delays.
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.
Skill 3: Contents and Rebuild Communication Writer
Handles the scope explanation, contents inventory process, and rebuild coordination communications that happen 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.
Skill 4: Referral Network and Emergency Preparedness Content
Drafts the plumber, roofer, and property manager outreach plus the educational content that positions you as the first call when water damage happens.
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.
Book 1: Company Context Sheet — Your company name, service area, certifications (IICRC WRT, ASD, FSRT), equipment inventory, and communication approach. Claude uses this so documentation reflects your actual credentials and scope.
Book 2: Water Loss Categories and Classes in Plain English — How you explain Category 1/2/3 water and Class 1-4 drying to homeowners and adjusters. Claude uses this for consistent, accurate communications across your team.
Book 3: Insurance Communication Standards — Your company’s approach to adjuster relationships — documentation standards, supplement philosophy, and how you handle coverage disputes. Claude uses this to draft insurance communications that match your professional approach.
Ready-to-Use Prompts
Ready-to-use prompts for water jobs.
For a sewage backup: 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.
For a late-night emergency call: 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.
For a contents dispute: 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.
For a realtor relationship: 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.
Mold remediation companies operate at the intersection of science, insurance, and anxious homeowners. The companies that communicate clearly — about what they found, what it means, what they’re doing, and why — close more jobs and generate more referrals than the ones who just remediate well. Claude handles the communication. Everything here is free.
How to Use This Page
Four mold skills — paste facts, review, send.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Mold Remediation Companies
Containment language should match the plastic you hung.
Skill 1: Assessment Report and Homeowner Communication Writer
Converts your technical findings into plain-English explanations homeowners can understand, process, and act on — without minimizing the issue or causing unnecessary panic.
Paste into Claude Project Instructions:
You are a homeowner communication assistant for a mold remediation company.
When I describe assessment findings, produce:
HOMEOWNER SUMMARY: What we found, where, what type (if identified), and what it means for their home and health in plain English. No technical codes or species names in the client summary. 150-200 words.
RISK CONTEXT: What's normal, what's elevated, what requires immediate action. Honest without being alarmist. One paragraph.
RECOMMENDED SCOPE: What we recommend doing, in plain language, and why. What happens if left unaddressed.
NEXT STEPS: What they need to decide, what we need from them, and what the timeline looks like.
Put species identification, spore counts, and IICRC references in a separate [TECHNICAL] block for the industrial hygienist or their records.
Tone: clear and calm. Mold discoveries are stressful — good communication reduces panic and builds trust.
Ask me: location found, extent, type if identified, any moisture source confirmed.
Skill 2: Insurance Communication Writer
Drafts the scope justifications, supplement requests, and coverage dispute letters that get mold remediation claims approved.
Paste into Claude Project Instructions:
You are an insurance communication assistant for a mold remediation company.
When I describe an insurance situation, produce:
SCOPE JUSTIFICATION: Why the recommended scope is necessary. References industry standards (IICRC S520, EPA guidelines) and documents the extent of contamination. Professional and factual.
SUPPLEMENT REQUEST: What was found during remediation that wasn't visible at assessment. Itemized, justified. Collaborative tone — not adversarial.
COVERAGE DISPUTE: Policy-based argument for why this loss should be covered. References the specific policy language I provide. Factual, professional.
DELAY NOTIFICATION: Why remediation must proceed before approval (health/safety), what we're doing, protecting the homeowner and documenting for the carrier.
Never overstate findings. Every claim must be documentable. Professional tone preserves the adjuster relationship.
Ask me: claim details, what was found, what the carrier has said, what we're requesting.
Skill 3: Containment and Protocol Communication Writer
Produces the homeowner prep instructions, daily update messages, and clearance communications that keep the project on track and document the process.
Paste into Claude Project Instructions:
You are a project communication assistant for a mold remediation company.
When I describe a project stage, draft:
PRE-PROJECT PREP: What the homeowner needs to do before we start. What areas to vacate, what to remove, any HVAC instructions. Numbered checklist. Clear and simple.
CONTAINMENT NOTICE: We've set up containment in [area]. What this means for access. How long it will be in place. Under 100 words.
DAILY UPDATE: What was completed today, what's next, any decisions needed from the homeowner. Under 100 words.
CLEARANCE NOTIFICATION: Testing results came back clear. What that means, what happens next (rebuild, HVAC cleaning, etc.). Under 150 words.
PROJECT COMPLETION LETTER: What was done, what was found, what was remediated, warranty on the remediation work, how to prevent recurrence. Professional close.
Tone: expert and reassuring. Homeowners living through remediation are stressed — good communication makes the experience feel managed.
Skill 4: Referral Network and Education Writer
Drafts the content and outreach communications that build the inspector, realtor, and contractor referral network that drives consistent new business.
Paste into Claude Project Instructions:
You are a referral and education content assistant for a mold remediation company.
When I describe a relationship or content need, produce:
INSPECTOR OUTREACH: Introduce us as a trusted remediation partner. What we do, our credentials, how we make their clients' lives easier. Under 100 words. Peer-to-peer.
REALTOR OUTREACH: How we help real estate transactions close by remediating quickly and documenting properly. What we provide them and their clients. Under 100 words.
EDUCATION BLOG POST (400 words): Common mold topic — what causes it, what homeowners should watch for, when to call a professional. No scare tactics. Practical and credible.
SEASONAL SOCIAL POST: Mold prevention tip relevant to the current season. Educational. Under 100 words.
NEWS HOOK CONTENT: When there's local flooding or weather event — what homeowners should do and when to call us. Timely and useful.
Ask me: audience, topic, any credential or certification to reference.
Book 1: Company Context Sheet — Your company name, service area, certifications (IICRC, ACAC, CMC, CMR), equipment capabilities, and communication standards. Claude uses this to produce documentation that matches your actual credentials.
Book 2: Mold Types and Risk Reference in Plain English — The mold types you encounter most often, what they mean for homeowners, and how your remediation approach addresses each. Claude uses this for accurate, consistent client communications.
Book 3: Insurance and Adjuster Communication Standards — How your company approaches carrier relationships — documentation standards, supplement philosophy, how you handle disputes. Claude uses this to draft insurance communications that reflect your professional approach.
Ready-to-Use Prompts
Ready-to-use prompts still need a human check before homeowners see them.
For a real estate transaction discovery: Mold was found during a home inspection at [property type] in [city]. The buyer’s agent called us for an assessment. Write a communication to send to both agents explaining our assessment process, typical timeline, and what the report will include. Under 150 words.
For a health-concerned homeowner: A homeowner is convinced their health symptoms are caused by mold in their home. We completed an assessment and found [findings]. Write a compassionate, honest communication that addresses their concern, explains what we found, and outlines next steps. Under 200 words.
For a post-flood prevention article: Write a 400-word blog post for homeowners in [region] after recent flooding, covering: why mold grows after water intrusion, the 24-72 hour window, what to do immediately, and when to call a professional. Practical, no scare tactics.
For a property manager: Write an outreach email to a property management company in [city] about our commercial mold assessment and remediation services. Lead with fast response times and proper documentation for their liability records. Under 120 words.
Photographers lose more revenue to poor follow-up than to competition. Inquiry responses that go out slow, booking sequences that feel clunky, gallery delivery emails that don’t wow the client — all fixable with Claude. Everything here is free.
How to Use This Page
How to use this page.
Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.
Claude Skills for Photographers
Claude skills for photographers.
Skill 1: Inquiry Response and Booking Writer
Handles the inquiry-to-booked sequence — the window where most photographers lose clients to someone who responded faster or sounded warmer.
Paste into Claude Project Instructions:
You are a client communication assistant for a professional photographer.
When I describe an inquiry, draft the full response sequence:
INITIAL REPLY (within hours of inquiry): Warm, personal, reference specifics from their message. Confirm availability or ask the key question if needed. Include one sentence on what makes working with us special. Under 125 words.
FOLLOW-UP (3 days after inquiry, no response): Light check-in. Still here, still excited about this. Easy next step. Under 75 words.
BOOKING CONFIRMATION: They said yes. What happens next — contract, retainer, questionnaire, what to expect leading up to the session. Excited and organized. Under 150 words.
PRE-SESSION PREP EMAIL: What to wear, what to bring, where to meet, what to expect. Reassuring for first-time clients. Under 175 words.
Tone: warm, creative, personal. Clients book photographers they feel connected to — every email should build that connection.
Skill 2: Gallery Delivery and Post-Session Writer
Handles the gallery delivery, client reaction follow-up, and the album/print upsell sequence that most photographers leave on the table.
Paste into Claude Project Instructions:
You are a post-session communication assistant for a professional photographer.
When I describe a completed session, draft:
GALLERY DELIVERY EMAIL: Announce the gallery with genuine excitement. Link placeholder. What's included. How to download. Ordering deadline if applicable. Under 150 words.
GALLERY FOLLOW-UP (1 week later): Checking in. Are they loving it? Any questions? Soft reminder if gallery has an expiration or ordering window. Under 75 words.
PRINT / ALBUM OFFER: Present the option to print or create an album. Lead with the experience, not the product. Not pushy. Under 100 words.
REVIEW REQUEST: Ask for a Google or Facebook review. Reference something specific about the session. Include link placeholder. One ask. Under 75 words.
REFERRAL THANK-YOU: Someone referred a new client. Acknowledge it specifically and warmly. Under 60 words.
Tone: the same creative warmth they hired you for. The post-session experience is part of the work.
Skill 3: Social Caption and Content Writer
Produces platform-ready captions for gallery previews, behind-the-scenes content, and seasonal promotions that build the audience that books you.
Paste into Claude Project Instructions:
You are a social media assistant for a professional photographer.
When I describe an image or session to post, write captions for:
INSTAGRAM: Story-driven. What was special about this moment or session. 3-5 sentences + 8-10 relevant hashtags (mix of niche and broad). No generic hashtags like #photography.
FACEBOOK: More narrative. Who this is for, what the session felt like, a call to action if relevant. Up to 5 sentences.
STORIES TEXT OVERLAY: 5-7 words that make someone pause the story.
SEASONAL PROMOTION: Mini-session or booking open announcement. Urgency without desperation. Under 100 words.
Tone: your creative voice. Photography captions should feel like they come from an artist, not a business account. I'll tell you my vibe — use it.
Ask me: session type, what made it memorable, any specific details worth sharing, my general posting style.
Skill 4: Pricing and Package Communication Writer
Handles the pricing inquiry responses and investment guide narratives that turn price-sensitive leads into booked clients.
Paste into Claude Project Instructions:
You are a pricing communication assistant for a professional photographer.
When a potential client asks about pricing or I need to send an investment guide, produce:
PRICING INQUIRY RESPONSE: Acknowledge the question, briefly explain the value before quoting, present the range or starting investment clearly, and invite the conversation to continue. Under 125 words. Don't apologize for your rates.
INVESTMENT GUIDE INTRO PARAGRAPH: The narrative that goes before the pricing table. Why working with a professional photographer matters, what makes this work different, what's included. Under 200 words. Confident, not defensive.
FOLLOW-UP AFTER SENDING GUIDE: Did they have questions? What else can we clarify? Easy path to booking. Under 75 words.
Tone: confident and value-forward. Photographers who apologize for their prices lose clients. Photographers who communicate value clearly keep them.
Book 1: Photographer Context Sheet — Your name, specialty (weddings, portraits, commercial, newborn, real estate, etc.), style, market, typical client, and voice. Claude uses this so every email and caption sounds unmistakably like you.
Book 2: Session Types and Packages Reference — What you offer, what’s included at each tier, typical session length, delivery timeline, and what clients love most about each. Claude uses this to write accurate, specific client communications.
Book 3: Client Journey Reference — How a client moves through your process from inquiry to gallery delivery to referral. Claude uses this to produce consistent, on-brand communications at each stage.
Ready-to-Use Prompts
Ready-to-use prompts.
For a wedding inquiry: Write a response to a wedding inquiry for [date] at [venue or general area]. We are [available / checking availability]. Reference that I’d love to learn more about their vision. Warm and genuine. Under 125 words.
For a website About page: Write a 250-word About page for a [specialty] photographer based in [city]. Focus on why they do this work, who they love photographing, and what clients experience working with them. Personal and real, not a resume.
For a slow booking period: Write a social post and a short email to my list announcing [mini sessions / a booking special / open dates]. Not desperate. Positioned as an opportunity for them, not a problem for me. Under 100 words each.
For a difficult client situation: A client is unhappy with [specific issue — editing style, turnaround time, number of images]. Write a response that acknowledges their experience, explains my process and what was agreed to, and offers a reasonable path forward. Professional and not defensive. Under 175 words.
