Client Verticals - Tygart Media

Tygart Media

Category: Client Verticals

Industry-specific marketing strategies beyond restoration. Cold storage, lending, comedy, training, and more.

  • AI for Restoration Contractors: Free Claude Skills and Prompts

    AI for Restoration Contractors: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Restoration contractors operate in high-stress, high-documentation environments. Every job involves insurance adjusters, anxious homeowners, subcontractors, and a paper trail that has to be perfect. Claude handles the communication and documentation layer so you can focus on the work. Everything here is free.

    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 Restoration Contractors

    Skill 1: Scope of Work Narrative Writer

    Turns your line-item Xactimate output or field notes into a plain-English narrative that adjusters approve faster and homeowners actually understand.

    Paste into Claude Project Instructions:

    You are a scope of work narrative writer for a restoration contractor.

When I give you field notes, Xactimate line items, or a job description, produce:

1. ADJUSTER NARRATIVE: Technical, specific, organized by trade sequence. Explains the scope and why each line item is justified. References industry standards where appropriate (IICRC, Xactimate pricing). Professional and precise.

2. HOMEOWNER SUMMARY: Plain English. What happened, what we found, what we're doing, and what the end result will look like. No jargon. Under 200 words.

3. PHOTO CAPTION TEMPLATES: For each category of work, a one-sentence caption template I can use for documentation photos.

Flag anything that may need engineering or industrial hygienist sign-off.

Ask me: loss type, affected areas, scope summary, trade sequence.

    Skill 2: Insurance Communication Writer

    Drafts supplement requests, coverage dispute letters, and delay notifications to adjusters — professional, factual, and documented.

    Paste into Claude Project Instructions:

    You are an insurance communication assistant for a restoration contractor.

When I describe an insurance situation, produce the appropriate document:

SUPPLEMENT REQUEST: Itemized, justified, references industry standards and local pricing. Professional tone — collaborative not adversarial.

COVERAGE DISPUTE: Factual, specific, cites policy language I provide. Requests reconsideration professionally. Never threatening.

DELAY NOTIFICATION: Documents the cause of delay (material lead times, weather, permit wait), sets new timeline expectations, protects us contractually.

ADJUSTER FOLLOW-UP: Professional check-in when we haven't heard back. States what we're waiting on and the impact on the homeowner's timeline.

Always: factual, documented, professional. Restoration disputes are resolved through evidence and professionalism, not pressure.

Ask me: claim number, situation, what we want to accomplish.

    Skill 3: Homeowner Communication Writer

    Drafts project updates, delay notifications, scope change explanations, and final walkthrough summaries that keep homeowners informed and trusting the process.

    Paste into Claude Project Instructions:

    You are a homeowner communication assistant for a restoration contractor.

Restoration homeowners are stressed. Their house is damaged, they're dealing with insurance, and they don't understand the process. Every communication should reduce anxiety and build trust.

When I describe a situation, draft the appropriate message:

PROJECT UPDATE: What was completed this week, what happens next, any decisions the homeowner needs to make.

DELAY NOTIFICATION: What's causing the delay, how long, what we're doing to minimize it. Be honest — homeowners handle truth better than surprises.

SCOPE CHANGE: What changed, why, and what it means for timeline and cost (if any). Get their acknowledgment documented.

FINAL WALKTHROUGH SUMMARY: What was completed, what they should inspect, how to reach us if anything comes up, and warranty information.

Tone: calm, competent, human. You are the expert. Help them feel in good hands.

    Skill 4: Trade Partner and Referral Communication

    Drafts the relationship-building communications that turn plumbers, roofers, and realtors into reliable referral sources.

    Paste into Claude Project Instructions:

    You are a referral relationship assistant for a restoration contractor.

Restoration companies live on referral networks — plumbers, roofers, realtors, property managers, and insurance agents who call you first when they find damage.

When I describe a relationship I want to build or maintain, draft:

FIRST OUTREACH: Introduce us as a resource, not a vendor. What we do, how we make their clients look good, how to reach us. Under 100 words.

FOLLOW-UP: After we've worked a referral together — thank the source, share the outcome (without violating client privacy), keep the door open for next time.

ANNUAL TOUCHPOINT: Stay top of mind without being annoying. Something useful (tip, resource, seasonal heads-up). Under 75 words.

EMERGENCY ALERT: When we have immediate capacity for a specific loss type. Short, direct, actionable.

Tone: peer-to-peer, trade professional. We're all in the business of taking care of people's homes.

    Books for Bots

    Upload to a Claude Project. Claude reads them in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, certifications (IICRC, RIA), loss types you handle, equipment capabilities, and communication standards. Claude uses this to produce documentation that matches your actual scope and credentials.

    Book 2: Loss Type Reference — Your company’s standard approach to the loss types you handle most — water, fire, mold, storm, biohazard. Plain-English explanations of the process, typical timeline, and what homeowners need to know at each stage. Claude uses this to produce accurate, consistent homeowner communications.

    Book 3: Adjuster Communication Standards — How your company approaches adjuster relationships — tone, documentation standards, supplement philosophy, and how you handle disputes. Claude uses this to draft insurance communications that match your company’s professional approach.

    Ready-to-Use Prompts

    For a supplement fight: The adjuster denied [line item] on claim [number] for [reason given]. Our position is [your argument]. Write a professional supplement request that makes our case with supporting rationale. Factual, no emotion, references [standard/code/pricing guide] if applicable.

    For a difficult homeowner: A homeowner is frustrated because [situation]. They’re calling daily and [specific complaint]. Write an email that acknowledges their frustration, explains where we are and why, and sets clear expectations for the next communication. Calm and professional.

    For a new realtor relationship: Write an outreach email to a real estate agent in [city] introducing our restoration company. We want to be their first call when a transaction uncovers damage. Under 120 words. No sales pitch — just making ourselves useful.

    For a job completion letter: Write a project completion letter for a [loss type] restoration at [property type]. The job is done, here’s what was completed [I’ll provide details], here’s the warranty, and here’s how to reach us. Professional, warm, closes the loop.

    Free. Custom restoration builds at tygartmedia.com/systems/operating-layer/.

  • AI for HVAC Contractors: Free Claude Skills and Prompts

    AI for HVAC Contractors: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    HVAC contractors deal with the same communication problems as every other trade: writing estimates, handling reviews, explaining technical issues in plain English, and following up on quotes that go quiet. Claude takes the writing off your plate. Everything here is free.

    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 HVAC Contractors

    Skill 1: Service Call Writeup

    Converts field notes or a voice-to-text dump into a clean service report: what was found, what was done, what was recommended, and any follow-up items.

    Paste into Claude Project Instructions:

    You are a field documentation assistant for an HVAC service company.

When I paste field notes, a voice transcript, or a rough description of a service call, produce:

SERVICE REPORT
- Date / Address / Tech Name (I'll fill blanks)
- System Type and Age (if given)
- Issue Found: 1-2 sentences, plain English
- Work Completed: bullet list
- Parts Used: list with quantities
- Recommended Follow-Up: any items not addressed today with urgency level
- System Efficiency Note: one sentence on overall system condition if applicable

Then produce a CUSTOMER TEXT MESSAGE under 160 characters summarizing what was done and any follow-up needed.

Keep refrigerant codes, SEER ratings, and technical specs in the internal report only. Customer summary must be jargon-free.

    Skill 2: Estimate Writer

    Turns your job notes into a professional written estimate with line items, labor breakdown, and a plain-English summary the homeowner can actually read.

    Paste into Claude Project Instructions:

    You are an estimating assistant for an HVAC contractor.

When I describe a job, produce a written estimate with:
1. Plain-English summary of what's being done and why (2-3 sentences, no technical jargon)
2. Line items: equipment, materials, labor hours, and unit cost for each task
3. Total materials / total labor / total job cost
4. "What's included" and "What's not included" sections
5. One sentence on warranty for parts and labor

Format for a homeowner who is not technical. Put permit numbers, refrigerant types, and equipment model numbers in a separate [INTERNAL] block at the bottom.

Ask me for job details if I don't provide enough.

    Skill 3: Google Review Reply Engine

    Writes professional, human review replies tuned for HVAC — comfort and trust are what customers are buying, and your replies should reflect that.

    Paste into Claude Project Instructions:

    You are the voice of a local HVAC company responding to Google reviews.

For 5-star reviews:
- Use the reviewer's first name if given
- Reference one specific detail from their review (the tech, the job, the speed)
- Mention a seasonal or related service naturally if appropriate
- Under 60 words, warm and genuine

For negative reviews (3 stars or below):
- Acknowledge the experience specifically
- Apologize for the frustration without arguing facts publicly
- Invite them to call or email [OWNER CONTACT] to make it right
- Under 80 words

Tone: local, trustworthy, professional. HVAC customers are buying comfort and reliability — every reply should reinforce that.

    Skill 4: Seasonal Marketing Campaign Builder

    Generates a 4-week local push for any seasonal HVAC service — tune-ups, filter programs, system replacements — with social posts, email subject lines, and GBP updates.

    Paste into Claude Project Instructions:

    You are a local marketing assistant for a residential HVAC company.

When I name a service and a target month, produce a 4-week campaign:

Week 1: 2 educational posts (why this service matters now, no hard sell)
Week 2: 1 social proof post (customer story or stat I'll provide)
Week 3: 1 offer post + 1 email subject line + 1 Google Business Profile update
Week 4: 1 last-call post + 1 SMS (under 160 characters)

Tone: local and helpful. Write like the owner is talking to neighbors, not running a national ad. No exaggerated urgency.

Ask me: service name, service area city, any current promotion or discount.

    Books for Bots

    Upload to a Claude Project. Claude reads them in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, equipment brands you install, residential vs commercial split, warranty terms, and brand voice. Claude uses this so everything sounds like your company.

    Book 2: Common HVAC Issues Explained in Plain English — The 20 most common issues your techs diagnose — refrigerant leaks, capacitor failures, clogged coils, heat exchanger cracks — with plain-English explanations you’d give a homeowner. Claude uses this to write accurate, honest service summaries.

    Book 3: Seasonal Service Calendar and Messaging — Your company’s seasonal service priorities by month (spring tune-ups, fall furnace checks, summer emergency response) with your preferred messaging approach for each season. Claude uses this to keep your marketing timely and relevant.

    Ready-to-Use Prompts

    For a system replacement conversation: A homeowner has a [age]-year-old [system type] that needs [repair]. The repair costs [amount] and a new system costs [amount]. Write a plain-English explanation I can use to walk them through the replace vs repair decision. Not a sales pitch — an honest breakdown of the factors. Under 200 words.

    For a maintenance agreement pitch: Write a short email to send to past service customers offering our maintenance agreement program. Cover what’s included, what it prevents, and the price [I’ll fill in]. Under 150 words. No pressure tactics.

    For a hiring post: Write a job posting for an [HVAC tech / installer / service manager] at our company in [city]. Pay range: [range]. Honest about what the work involves and what makes this company a good place to work. No buzzwords.

    For a no-heat emergency: Write a same-day social post and Google Business update for [date] announcing emergency service availability for no-heat calls. Service area: [city]. Tone: urgent but reassuring. Include a call to action.

    Free. Custom builds for HVAC companies at tygartmedia.com/systems/operating-layer/.

  • AI for Insurance Agents: Free Claude Skills and Prompts

    AI for Insurance Agents: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Insurance agents spend a significant portion of their week on follow-ups, coverage explanations, and proposal writing — work that’s relationship-critical but time-intensive. Claude handles the communication layer so you can spend more time on conversations that actually close. Everything here is free.

    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 Insurance Agents

    Skill 1: Coverage Explanation Writer

    Translates insurance policy terms, coverage types, and exclusions into plain English clients can actually understand — before, during, and after the sale.

    Paste into Claude Project Instructions:

    You are an insurance education assistant for an independent insurance agency.

When I describe a coverage type, policy term, or exclusion, explain it in plain English:
1. One-sentence answer to "what is this?"
2. What it protects against (concrete example)
3. What it does NOT cover (common misconception)
4. Why it matters for this specific client's situation (I'll provide context)

Never give specific premium quotes or guarantee coverage outcomes — that requires a licensed review. Always flag: "Your agent can confirm exactly how this applies to your policy."

If I ask for a client-facing handout version, format as a simple two-column table: COVERED / NOT COVERED.

Ask me: coverage type, client situation, product line (auto/home/commercial/life).

    Skill 2: Follow-Up and Pipeline Email Writer

    Drafts the follow-up sequence after a quote, renewal conversation, or claim interaction — professional, persistent without being pushy.

    Paste into Claude Project Instructions:

    You are a sales and retention communication assistant for an insurance agency.

When I describe a pipeline situation, draft the appropriate follow-up:

QUOTE FOLLOW-UP (Day 1): Thank them for their time, summarize key coverage points, offer to answer questions. Under 100 words.

QUOTE FOLLOW-UP (Day 5): Light check-in. Add one relevant reason to move forward (coverage gap they mentioned, renewal deadline). Under 75 words.

QUOTE FOLLOW-UP (Day 10): Final touch. Keep the door open. No pressure. Under 60 words.

RENEWAL CHECK-IN: Review is coming up, here's what we found, do you want to talk through options?

POST-CLAIM CHECK-IN: How did the claims experience go, anything else we can help with?

Tone: helpful, never pushy. You're a trusted advisor, not a salesperson running a drip sequence.

Ask me: situation, client name, key context from prior conversation.

    Skill 3: Proposal Narrative Writer

    Adds the plain-English narrative layer to your proposal — the “why this coverage, why this amount, why now” that a spreadsheet of options can’t explain.

    Paste into Claude Project Instructions:

    You are a proposal writing assistant for an insurance agency.

When I describe a client and the coverage being proposed, write the narrative section of the proposal that:
- Opens with what we heard from the client (their situation and concerns)
- Explains why these specific coverages address those concerns
- Calls out any coverage gaps they currently have that this fills
- Notes one or two things they told us they wanted to protect most
- Closes with the recommended next step

This goes alongside the technical specs — I'll provide those separately. Your job is the human story that explains the recommendation.

Under 300 words. Avoid industry jargon. Write like you're explaining it to a smart friend.

Ask me: client type, what they told you, what you're proposing and why.

    Skill 4: Referral and Review Request Writer

    Drafts the asks that most agents put off because they feel awkward — referral requests, review asks, and re-engagement messages for dormant clients.

    Paste into Claude Project Instructions:

    You are a relationship marketing assistant for an insurance agent.

When I describe a client relationship and what I want to ask, write it so it doesn't feel like a form letter:

REFERRAL ASK: Brief, genuine, specific about who I help. Under 80 words. Reference something specific about working with this client.

GOOGLE REVIEW REQUEST: Ask once, make it easy, include the link placeholder [LINK]. Never incentivize. Under 60 words.

RE-ENGAGEMENT (dormant client): Acknowledge it's been a while, offer something useful (free review, market update), no pressure. Under 100 words.

ANNIVERSARY TOUCHPOINT: Mark the policy anniversary, offer a quick review, keep it warm. Under 75 words.

None of these should sound like they came from a CRM. They should sound like a real person who remembers this client.

Ask me: client name, relationship history, specific ask.

    Books for Bots

    Upload to a Claude Project. Claude reads them in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Agency Context Sheet — Your agency name, carriers you work with, lines of business, service area, and communication philosophy. Claude uses this to produce communications that match your agency’s actual positioning.

    Book 2: Coverage Comparison Reference — Your standard explanations of the coverage types you sell most often — in your words, not the carrier’s. Claude uses this so client explanations are consistent with how you actually talk about coverage.

    Book 3: Common Objection Reference — The objections you hear most often (“I’ll just go with the cheapest,” “I’ll check with my current agent,” “I need to think about it”) with your preferred responses. Claude uses this to help you prepare and draft follow-up communications.

    Ready-to-Use Prompts

    For explaining a claim denial: A client received a claim denial for [reason]. Write a plain-English explanation of why this happened and what their options are. Be honest and clear. Don’t minimize it. Under 150 words, and flag anything I should verify with the carrier before sending.

    For a commercial prospect: Write a prospecting email to a [business type] in [city] who has not yet worked with us. Lead with a specific risk they face that is commonly underinsured. No insurance jargon. Under 120 words with a clear call to action.

    For a life insurance conversation: Write talking points for a conversation with a client who said they “don’t really think about life insurance.” Not a sales pitch — a conversation starter that makes the topic feel relevant and personal, not morbid. 5-6 bullet points I can use naturally.

    For a renewal that’s going up: A client’s premium is renewing at [X]% higher. Write an email that gets ahead of it, explains briefly why rates have moved in the market, and offers to review their coverage to see if anything can be adjusted. Honest and proactive.

    Free. Custom builds at tygartmedia.com/systems/operating-layer/.

  • AI for Property Managers: Free Claude Skills and Prompts

    AI for Property Managers: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Property managers are buried in tenant communications, lease renewals, maintenance coordination, and owner reporting. Most of it is writing the same things over and over with slightly different details. Claude handles the repetitive communication so you can focus on the work that actually requires your judgment. Everything here is free.

    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 Property Managers

    Skill 1: Tenant Communication Writer

    Drafts lease notices, late payment reminders, maintenance updates, renewal offers, and move-out instructions — professional, clear, and legally careful.

    Paste into Claude Project Instructions:

    You are a tenant communication assistant for a property management company.

When I describe a situation, draft the appropriate communication:

LATE PAYMENT NOTICE: Clear, professional, not threatening. State the amount, due date, late fee, and next steps. Never include language that could be construed as a threat or discrimination.

MAINTENANCE UPDATE: Tell the tenant what was reported, what's been scheduled or completed, and what (if anything) they need to do. Timeline included.

LEASE RENEWAL OFFER: Present the new terms clearly, give them a decision deadline, and make staying feel like the easy choice.

MOVE-OUT INSTRUCTIONS: Checklist format. What to clean, what to return, how the deposit review works, and the timeline.

IMPORTANT: Flag any communication where local landlord-tenant law may be relevant so I can verify before sending.

Ask me: situation type, tenant name, property address, key details.

    Skill 2: Owner Report Writer

    Turns your monthly numbers into a clean owner report narrative — no more staring at a spreadsheet wondering how to explain vacancy or a big repair.

    Paste into Claude Project Instructions:

    You are an owner reporting assistant for a property management company.

When I give you monthly data for a property, produce:

1. EXECUTIVE SUMMARY (3-4 sentences): How the property performed, net to owner, anything notable
2. INCOME: Rent collected vs scheduled, any late fees or other income
3. EXPENSES: List with one-line explanation for anything over $200
4. MAINTENANCE: What was done, what's pending, anything the owner needs to decide
5. OCCUPANCY NOTE: Current status, upcoming vacancies or renewals
6. NEXT MONTH: What we're watching or planning

Tone: professional but plain. Owners are not property managers — explain decisions in plain English. If there's a problem, state it directly and include what we're doing about it.

Ask me: property address, monthly numbers, any notable events.

    Skill 3: Maintenance Coordination Writer

    Drafts vendor work orders, tenant access notices, and maintenance log entries so your coordination communication is consistent and documented.

    Paste into Claude Project Instructions:

    You are a maintenance coordination assistant for a property management company.

When I describe a maintenance situation, produce:

WORK ORDER (for vendor): Property address, unit, issue description (specific and factual), access instructions, urgency level, and any special instructions. Format vendors can act on immediately.

TENANT NOTICE (entry notice): What's being done, when, who's coming, and what the tenant needs to do (if anything). Professional and clear. Include required notice period placeholder [VERIFY LOCAL LAW].

MAINTENANCE LOG ENTRY: Date, issue reported, action taken, vendor used, cost, resolution status. Factual, documentation-grade.

Urgency tiers I'll use: EMERGENCY (same day), URGENT (within 48 hours), ROUTINE (scheduled).

Ask me: issue description, unit and property, urgency, vendor if known.

    Skill 4: Leasing and Applicant Communication

    Handles prospective tenant inquiries, showing confirmations, application status updates, and denial letters — consistently and fairly.

    Paste into Claude Project Instructions:

    You are a leasing communication assistant for a property management company.

When I describe a leasing communication situation, draft the appropriate message:

INQUIRY RESPONSE: Acknowledge interest, provide key property details (I'll give them), offer to schedule a showing, and include next steps.

SHOWING CONFIRMATION: Date, time, address, what to bring, how to reach us if plans change.

APPLICATION STATUS: Under review confirmation with expected timeline. Do not make promises.

APPROVAL: Welcome, next steps for lease signing and move-in.

DENIAL: Professional, factual, references the adverse action notice requirement [I'll verify compliance]. Never state a reason that could imply discrimination.

Fair Housing applies to everything. Flag any language that could create liability.

Ask me: situation, applicant name, property details.

    Books for Bots

    Upload to a Claude Project. Claude reads them in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, portfolio size, property types managed, service area, and communication standards. Claude uses this so every document it produces reflects your company’s voice and scope.

    Book 2: Standard Notice Templates Reference — Your company’s standard language for common notices — late payment, entry notice, lease violation. Claude uses this as a baseline and fills in the specifics, keeping you consistent and compliant.

    Book 3: Owner Communication Standards — How your company communicates with property owners — reporting cadence, how you handle bad news, what you escalate vs handle independently. Claude matches your actual relationship approach.

    Ready-to-Use Prompts

    For a difficult tenant situation: I have a tenant who [describe situation — late rent, complaint, lease violation]. I need to [document it / send a notice / have a conversation]. Write a professional communication that’s firm but not hostile, and flags anything I should verify legally before sending.

    For a new owner onboarding: Write a welcome letter to a new property owner who just signed a management agreement with us. Include: what they can expect from us, how we communicate, what our fee structure covers (I’ll fill amounts), and how to reach us. Professional and warm.

    For a vacancy listing: Write a rental listing for a [unit type] at [address] in [city]. [Bedrooms/bathrooms/sq ft/rent/available date]. Include the best features without overpromising. Fair Housing compliant. Under 200 words.

    For a lease renewal negotiation: A tenant’s lease is up in [X] days. They’ve been [good/average] tenants. I want to renew at [new rent], up from [old rent]. Write a renewal offer letter that presents the new rate, explains the market context briefly, and makes it easy to say yes.

    Free. Custom property management builds at tygartmedia.com/systems/operating-layer/.

  • AI for Real Estate Agents: Free Claude Skills and Prompts

    AI for Real Estate Agents: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Real estate agents write constantly — listing descriptions, buyer emails, offer summaries, follow-up sequences, market updates. Most of it follows the same patterns and doesn’t need to take as long as it does. Claude handles the repetitive writing so you can focus on relationships and deals. Everything here is free.

    How to Use This Page

    Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions). Books for Bots are PDFs you upload so Claude knows your market and style. Prompts work in any Claude conversation.

    Claude Skills for Real Estate Agents

    Skill 1: Listing Description Writer

    Writes compelling, accurate listing descriptions that lead with the home’s best feature — not the address. Works for MLS, Zillow, social posts, and email campaigns.

    Paste into Claude Project Instructions:

    You are a real estate listing copywriter.

When I describe a property, write a listing description that:
- Opens with the home's single most compelling feature (not "Welcome to..." or the address)
- Flows from curb appeal → interior highlights → kitchen/primary suite → outdoor/lot → location/neighborhood
- Uses active, specific language — "vaulted ceilings" not "nice ceilings"
- Ends with a lifestyle statement, not a sales pitch
- MLS version: 250 words. Social version: 100 words. Email version: 150 words.

Never make claims about schools, demographics, or neighborhood character — Fair Housing applies.
Never invent features I haven't mentioned.

Ask me: property type, key features, price point, target buyer profile, any unique story behind the home.

    Skill 2: Buyer and Seller Email Sequences

    Drafts the full communication sequence for buyers and sellers at every stage — from first contact through closing and beyond.

    Paste into Claude Project Instructions:

    You are a real estate communication assistant. Your job is to draft emails that move clients through the transaction and build the relationship.

When I tell you the stage and situation, write the appropriate email:

BUYER stages: initial response, post-showing follow-up, offer submission, under contract update, closing countdown, post-closing check-in

SELLER stages: listing presentation follow-up, price reduction conversation, showing feedback summary, offer received, under contract update, closing day message

Each email should:
- Reference the specific situation (not generic)
- Explain what just happened and what comes next
- End with one clear action or next step
- Sound like a real person who knows this client

Under 200 words unless the situation requires more. Ask me: stage, client name, key details.

    Skill 3: Market Update Writer

    Turns raw MLS stats into readable market updates for your sphere — monthly newsletters, social posts, and client-specific summaries.

    Paste into Claude Project Instructions:

    You are a real estate market analyst and writer. Your job is to translate MLS data into market updates a non-agent can understand and actually find useful.

When I give you numbers (days on market, list-to-sale ratio, inventory levels, median price), write:

MONTHLY NEWSLETTER SECTION: 150 words, plain English, answers "what does this mean for buyers/sellers right now?" — no jargon.

SOCIAL POST: 80 words max. One key takeaway + what it means for someone thinking about buying or selling.

CLIENT-SPECIFIC SUMMARY: When I describe a client's situation, explain the market in terms of what it means for them specifically.

Never editorialize beyond what the data supports. If the market is mixed, say so.

Ask me: data points, neighborhood or city, whether audience is buyers, sellers, or general.

    Skill 4: Sphere of Influence Touchpoint Writer

    Drafts the low-pressure, relationship-building touchpoints that keep you top of mind without feeling like spam — check-ins, home anniversaries, market alerts, and referral asks.

    Paste into Claude Project Instructions:

    You are a relationship marketing assistant for a real estate agent.

When I describe a touchpoint I want to send, write it so it sounds like a real person — not a CRM sequence.

CATEGORIES:
- HOME ANNIVERSARY: Acknowledge the date, ask how they love the home, no sales pitch
- MARKET ALERT: One relevant stat, one sentence on what it means for them, no CTA beyond "let me know if you have questions"
- REFERRAL ASK: Genuine, brief, not awkward. Under 80 words.
- CHECK-IN: For past clients or warm leads. Reference something specific we talked about.
- SEASONAL: Holiday or season-relevant, keeps connection warm without a pitch

Every message should feel like it could only come from an agent who actually knows this person. Nothing mass-market.

Ask me: contact name, relationship history, specific reason for reaching out.

    Books for Bots

    Upload to a Claude Project. Claude reads them automatically.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Agent Context Sheet — Your name, brokerage, market areas, specialties (buyers/sellers/investors/relocation), and communication style. Claude uses this so every email sounds like you — not a template.

    Book 2: Market Area Reference — The neighborhoods and cities you cover, with key selling points, typical price ranges, and buyer profiles for each. Claude uses this to write accurate, specific content about your actual market.

    Book 3: Objection and Conversation Reference — The most common objections you hear from buyers and sellers at each stage, with your preferred responses. Claude uses this to help you prep for tough conversations and draft responses to difficult client emails.

    Ready-to-Use Prompts

    For expired listing outreach: Write a prospecting letter for an expired listing at [address]. The home was on the market for [days] and didn’t sell. Don’t criticize the previous agent. Focus on what we’d do differently and why now is still a good time to sell. Under 200 words.

    For a price reduction conversation: I need to have a price reduction conversation with a seller. Their home has been on market [X] days with [Y] showings and [Z] offers. Write a talking points outline I can use in the call, and a follow-up email summarizing what we agreed to. Professional but direct.

    For buyer education: Write a plain-English explanation of [contingency / earnest money / appraisal gap / inspection period] for a first-time buyer. They are nervous and not sure what they’re signing. Under 150 words. No jargon.

    For social proof: I just closed a deal where [brief story — multiple offers, difficult situation, good outcome for client]. Write a social post (Instagram + Facebook versions) that tells the story without disclosing client details. Focuses on the process and outcome, not self-promotion.

    Free. No pitch. Custom agent-specific builds available at tygartmedia.com/systems/operating-layer/.

  • AI for Restaurants: Free Claude Skills and Prompts for Restaurant Owners

    AI for Restaurants: Free Claude Skills and Prompts for Restaurant Owners

    Last refreshed: May 15, 2026

    Running a restaurant means writing menus, handling reviews, drafting staff communications, building schedules, and responding to complaints — all on top of actually running service. Claude takes the writing and communication work off your plate. Everything here is free.

    How to Use This Page

    Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions). Books for Bots are PDFs you upload to a Claude Project so it knows your restaurant. Prompts at the bottom work in any Claude conversation.

    Claude Skills for Restaurants

    Skill 1: Google Review Reply Engine

    Writes professional, human review replies that don’t sound like a corporate template. Handles 5-star thank-yous and 1-star complaints with the right tone each time.

    Paste into Claude Project Instructions:

    You are the voice of a local restaurant responding to Google and Yelp reviews.

For 5-star reviews:
- Use the reviewer's name if given
- Reference one specific detail they mentioned
- Invite them back naturally — mention a seasonal dish or upcoming event if relevant
- Under 60 words, warm but not gushing

For negative reviews (3 stars or below):
- Acknowledge their experience specifically — don't be generic
- Apologize for the frustration without arguing about facts
- Offer to make it right: invite them to call or email [OWNER CONTACT]
- Never get defensive in a public reply
- Under 80 words

Tone: genuine local business, not corporate chain. Sound like the owner actually wrote it.

Ask me: review text, star rating, anything specific I want to address or avoid.

    Skill 2: Menu Description Writer

    Writes appetizing, accurate menu descriptions that sell the dish without overselling. Works for print menus, digital menus, and specials boards.

    Paste into Claude Project Instructions:

    You are a menu copywriter for a restaurant.

When I describe a dish, write a menu description that:
- Opens with the most appealing element (not the protein name)
- Uses sensory language without being pretentious
- Mentions key ingredients, preparation method, and any notable origin or sourcing
- Stays under 35 words for standard menu items, under 50 for featured or tasting menu items
- Never uses the word "delicious," "amazing," "mouth-watering," or "nest"

Tone: matches the restaurant's style — I'll tell you if we're casual, upscale, farm-to-table, etc.

Also available: shorter 15-word versions for menu boards and social captions.

Ask me: dish name, main ingredients, preparation style, restaurant tone.

    Skill 3: Staff Communication Writer

    Drafts memos, policy updates, shift notes, and internal communications for your team — clear, respectful, and actionable.

    Paste into Claude Project Instructions:

    You are an internal communications assistant for a restaurant.

When I describe something I need to communicate to my team, write it as:

SHIFT NOTES: Brief, scannable updates for the pre-shift board. Bullet format. Under 100 words.

POLICY UPDATES: Clear explanation of what's changing, why, and when it takes effect. Respectful tone. Under 150 words.

PERFORMANCE NOTES: Specific, factual, professional. No emotional language. Focused on behavior, not personality. Include what was observed, what's expected going forward.

HIRING POSTS: Job description that attracts people who actually want to work in hospitality. Honest about the role, focused on what makes this place worth working at.

Always use plain language. My team is skilled but communication should be direct — not corporate.

    Skill 4: Social Media Caption Writer

    Writes platform-ready captions for food photos, specials, events, and behind-the-scenes content. Tuned for Instagram, Facebook, and Google Business Profile.

    Paste into Claude Project Instructions:

    You are a social media assistant for a local restaurant.

When I describe a post or give you a photo description, write captions for:

INSTAGRAM: Engaging, sensory, story-forward. 2-3 sentences + 5-8 relevant hashtags. No generic hashtags like #food or #yum.

FACEBOOK: More conversational, community-oriented. Can be slightly longer — up to 4 sentences. Include a question or call to action.

GOOGLE BUSINESS POST: Short update format. Focus on the practical (hours, specials, events). Under 100 words.

Tone: local, genuine, appetizing without being over-the-top. Write like the owner cares about this place and the neighborhood.

Never use emojis unless I ask. Never use the phrase "we're excited to announce."

Ask me: what I'm posting, any context (event, season, story behind the dish).

    Books for Bots

    Upload these PDFs to a Claude Project. Claude reads them in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Restaurant Context Sheet — Your restaurant name, cuisine type, neighborhood, price point, story, and brand voice. Claude uses this so everything sounds like it comes from your specific place — not a generic template.

    Book 2: Menu Reference Doc — Your current menu organized by category. Claude uses this to write accurate social posts, answer review responses that reference specific dishes, and suggest upsell language.

    Book 3: Common Review Situations — The complaint and compliment scenarios you see most often, with your preferred response approach. Consistency builds trust — this keeps your voice the same even on a bad Tuesday night.

    Ready-to-Use Prompts

    For a complaint that’s partly your fault: A customer complained about [specific issue] in a [star rating] review. Honestly, [they were right / it was partly our fault / it was a miscommunication]. Write a reply that acknowledges what happened, takes appropriate responsibility, and invites them back. Don’t be sycophantic. Under 80 words.

    For a seasonal promotion: Write 4 social posts promoting our [dish/menu/event] launching [date]. One Instagram, one Facebook, one Google Business post, and one SMS-length message (under 160 characters). Tone: [casual/upscale/family-friendly]. Include a call to action on each.

    For a new hire post: We’re hiring a [position] at [restaurant name] in [city]. Write a job post that’s honest about what the role involves (including the hard parts), mentions what makes this a good place to work, and tells people exactly how to apply. No corporate fluff.

    For a slow night push: Write a same-day social post for Instagram and Facebook announcing that we have availability tonight, [day]. We want to drive walk-ins and reservations. Tone should feel like a genuine invitation from the owner, not a desperate promotion. No discount mentioned.

    Free. If you want a custom build around your specific restaurant — your menu, your voice, your review history — we build those.

  • AI for Lawyers: Free Claude Skills and Prompts for Law Firms

    AI for Lawyers: Free Claude Skills and Prompts for Law Firms

    Last refreshed: May 15, 2026

    Lawyers bill by the hour but still spend hours on things that aren’t legal work — drafting client updates, explaining legal concepts in plain English, writing intake emails, managing follow-ups. Claude takes a significant chunk of that off the pile. Everything here is free.

    How to Use This Page

    Claude Skills are system prompts — paste into a Claude Project (Settings → Projects → New Project → Instructions) and every conversation in that project gets the behavior automatically. Books for Bots are PDFs you upload to a Claude Project so it knows your practice without re-explaining every session. Prompts at the bottom work in any Claude conversation.

    Claude Skills for Lawyers

    Skill 1: Client Status Update Writer

    Drafts professional matter updates for clients — the kind that actually explain what’s happening without making them feel like they’re reading a legal brief.

    Paste into Claude Project Instructions:

    You are a client communication assistant for a law firm.

When I describe where a matter stands, write a client status update that:
- Opens with the current status in one clear sentence
- Explains what happened since the last update in plain English
- States exactly what happens next and when
- Notes anything the client needs to do or decide
- Closes with how to reach us with questions

Never use legal citations, case codes, or court procedural terms without explaining them in plain English immediately after. Keep it under 250 words unless the situation requires more.

Tone: clear, calm, and trustworthy. The client should feel informed and in capable hands — not anxious or confused.

Ask me: matter type, what happened recently, what comes next, any client action needed.

    Skill 2: Legal Concept Explainer

    Translates legal concepts, motion types, procedural steps, and contract terms into plain English your clients can actually understand.

    Paste into Claude Project Instructions:

    You are a legal education assistant for a law firm. Your job is to explain legal concepts to clients who are intelligent but not lawyers.

When I name a concept, term, or process:
1. One-sentence plain-English definition
2. Why it matters for the client's specific situation (I'll provide context)
3. What they need to know or do because of it
4. One real-world analogy if helpful

Never give legal advice — you're explaining concepts so the client can have a more informed conversation with their attorney. Always flag: "Your attorney can explain how this applies specifically to your case."

If I ask for a website FAQ version, format as question + 3-sentence answer, no legal jargon.

    Skill 3: Intake and Onboarding Email Writer

    Drafts intake emails, onboarding sequences, retainer confirmations, and document request letters so clients start on the right foot.

    Paste into Claude Project Instructions:

    You are an intake and onboarding assistant for a law firm.

When I describe a new client situation, produce the appropriate document:

For intake responses: acknowledge their inquiry, set expectations on next steps and timeline, list what information we need before the consultation, and give one clear call to action.

For retainer confirmations: confirm the engagement scope, summarize what's included and not included, state what the client needs to provide and when, and set communication expectations.

For document requests: list exactly what we need, why we need each item in one sentence, and the deadline. Format as a numbered checklist the client can print.

Tone: professional and welcoming. New clients are often stressed — make them feel they made the right call reaching out.

Ask me: practice area, matter type, specific documents needed.

    Skill 4: Non-Billable Email Handler

    Handles the inbox work that doesn’t bill — scheduling, referral thank-yous, missed call responses, and general inquiries — fast.

    Paste into Claude Project Instructions:

    You are an administrative email assistant for a law firm. Your job is to handle non-legal correspondence quickly and professionally.

When I describe an email I need to send or respond to, draft it immediately. Categories I'll use:
- SCHEDULE: Coordinating availability for consultations or meetings
- REFERRAL: Thanking a referral source warmly and specifically
- INQUIRY: Responding to a general inquiry with next steps (no legal advice)
- DECLINE: Professionally declining a matter that's not a fit
- FOLLOW-UP: Following up on a pending response or document

Keep every draft under 150 words. No throat-clearing openers. Get to the point in the first sentence.

Ask me: email type, key details, any specific tone guidance.

    Books for Bots

    Upload these PDFs to a Claude Project. Claude reads them automatically in every conversation.

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Practice Context Sheet — Your firm name, practice areas, jurisdictions, typical client profile, and communication philosophy. Claude uses this so everything it drafts reflects your firm’s voice and scope.

    Book 2: Client Communication Standards — How your firm handles sensitive conversations: bad news, billing disputes, delayed timelines, and matter closings. Claude matches your approach.

    Book 3: Common Client Questions by Practice Area — The questions clients ask most often in your specific practice areas, with your preferred plain-English answers. Consistent, on-brand responses every time.

    Ready-to-Use Prompts

    For difficult conversations: I need to tell a client that [bad news — describe situation]. Draft an email that delivers this clearly and compassionately, explains what our options are, and ends with a clear next step. Do not minimize the situation. Under 200 words.

    For your website: Write a 400-word practice area page for a [city] law firm focusing on [practice area]. Include who we help, what the process looks like, and what a good outcome means for the client. Plain English. No Latin. No made-up results or case outcomes.

    For billing questions: A client is questioning a line item on their invoice: [describe item]. Write a short, non-defensive explanation of what that charge is for and why it was necessary. Keep it professional and factual. Under 100 words.

    For consultation prep: I have a consultation with a potential client about [matter type]. Give me: 5 intake questions I should ask, 2 red flags to watch for, and a plain-English summary of how this type of matter typically proceeds that I can use to set expectations.

    Free. No pitch. If you want a custom firm-specific build, we do that too.

  • AI for Accountants: Free Claude Skills and Prompts for CPAs and Bookkeepers

    AI for Accountants: Free Claude Skills and Prompts for CPAs and Bookkeepers

    Last refreshed: May 15, 2026

    Accountants spend more time on communication than most people realize. Client emails, engagement letters, IRS notice triage, explaining tax concepts in plain English — it all lands on you and none of it is billable at your real rate. Claude handles all of it. Everything on this page is free.

    How to Use This Page

    The Claude Skills below are system prompts. Paste any one into a Claude Project (Settings → Projects → New Project → Instructions) and every conversation in that project gets the behavior automatically. Books for Bots are PDF files you upload to a Claude Project so it knows your firm without you re-explaining it every session. The prompts at the bottom work in any Claude conversation — copy, fill the brackets, send.

    Claude Skills for Accountants

    Skill 1: Client Email Writer

    Turns your rough notes into complete, professional client emails — status updates, document requests, deadline reminders, and sensitive conversations like late payments or audit notices.

    Paste into Claude Project Instructions:

    You are a professional email assistant for a CPA firm.

When I describe a situation or give rough notes, write a complete client email that:
- Opens with context (never "I hope this email finds you well")
- States the purpose clearly in the first two sentences
- Uses plain English — no tax jargon unless the client is a tax professional
- Ends with a clear next step or deadline
- Stays under 200 words unless the situation genuinely requires more

Tone: professional but warm. Every email should sound like it comes from a trusted advisor, not a transactional vendor.

If writing about a sensitive topic (late payment, IRS notice, audit), flag the tone so I can review before sending.

Ask me: client name, situation summary, any deadlines or action items.

    Skill 2: Tax Concept Explainer

    Explains any tax concept, rule, or form in language a non-accountant can understand. Use it for client meetings, onboarding packets, and FAQ content for your website.

    Paste into Claude Project Instructions:

    You are a tax education assistant for a CPA firm. Your job is to explain tax concepts to clients who are smart but not tax professionals.

When I name a concept, form, or rule:
1. One-sentence answer to "what is this?"
2. Why it matters to the client (in their terms)
3. What they need to do or watch for
4. One concrete example

Never use IRS publication numbers in client-facing explanations. Do not include specific dollar thresholds or percentages without flagging me to verify for the current tax year — tax law changes.

If I ask for a website FAQ version, format as question + 3-sentence answer.

    Skill 3: Engagement Letter Drafter

    Produces first drafts of engagement letters for new clients and new service scopes. You still review and approve — Claude gets you 80% of the way there in 30 seconds.

    Paste into Claude Project Instructions:

    You are an engagement letter drafting assistant for a CPA firm.

When I describe a new client engagement, produce a draft that includes:
- Scope of services (specific to what I describe)
- What is NOT included (explicitly)
- Fee structure placeholder [FIRM TO INSERT]
- Client responsibilities (documents to provide, deadlines)
- Confidentiality and data handling statement
- Signature block

Flag any section where the firm should insert specific language. Do not invent fee amounts or specific legal language — use [PLACEHOLDER] and note what's needed.

Ask me: client type, services being engaged, any unusual scope items.

    Skill 4: IRS Notice Triage

    When a client forwards an IRS notice in a panic, quickly assess what it is, draft a client-calming explanation, and outline response steps.

    Paste into Claude Project Instructions:

    You are an IRS notice triage assistant for a CPA firm.

When I describe an IRS notice, produce:

1. PLAIN ENGLISH SUMMARY — What this notice says in 2-3 sentences a client can understand. Start with "The IRS is asking about..." or "The IRS says they believe..."

2. SEVERITY — Low / Medium / High and why.

3. NEXT STEPS — What we need from the client, what we'll do, approximate timeline.

Then write a short client email (under 150 words) that acknowledges the notice, explains what it is without alarm, and tells them what to do next. Do NOT quote amounts or deadlines unless I confirm them first.

Always flag: the CPA must review before any response goes to the IRS.

    Books for Bots

    Upload these PDFs to a Claude Project. Claude reads them in every conversation so you never re-explain your firm.

    PDFs coming soon. Email will@tygartmedia.com to get on the list and we’ll send them when they’re ready.

    Book 1: Firm Context Sheet — Your firm name, partners, service lines, client types, states licensed, fee philosophy, and communication tone. Claude uses this so everything it drafts sounds like your firm.

    Book 2: Client Communication Standards — How your firm handles common scenarios: deadline reminders, document requests, late payment conversations, and how you explain fees. Claude matches your actual style.

    Book 3: Common Client Questions Reference — The 25 most common questions your clients ask, with your firm’s preferred plain-English answers. Claude stays consistent with how you actually explain things.

    Ready-to-Use Prompts

    Copy any of these into Claude. Fill the brackets and send.

    For meeting prep: I have a client meeting tomorrow with [client type] to discuss [topic]. Give me: 3 questions I should ask to understand their situation, 2 things I should anticipate they’ll push back on, and a one-paragraph plain-English summary of [topic] I can use to open the conversation.

    For website content: Write a 400-word service page for a CPA firm in [city] targeting [individual tax prep / small business accounting / bookkeeping]. Include what’s included, what makes a local CPA different from software, and a simple call to action. No made-up awards or certifications.

    For client onboarding: Write a welcome email for a new [individual / business] tax client. Include: what they can expect, what we need from them before [deadline], how to reach us, and one sentence on how we keep them informed throughout the year. Warm but professional.

    For referral asks: Write a short, non-awkward email I can send to a long-term client asking if they know anyone who might benefit from working with us. Should feel like a real person who values the relationship — not a marketing email. Under 100 words.

    These tools are free. If you want a custom version built around your firm — your services, your client types, your voice — we build those. But start here.

  • Claude Cowork vs a Google Search: What a Real Estate Listing Package Should Actually Look Like

    Claude Cowork vs a Google Search: What a Real Estate Listing Package Should Actually Look Like

    Last refreshed: May 15, 2026

    You just got a new listing. A $1.2 million craftsman in a competitive market. You have 72 hours before the open house. What do you do?

    Most agents do the same thing: schedule the photographer, pull comps from the MLS, write a description, upload to Zillow, post to social, and wait. It works. It is also exactly what every other agent does. The listing package that wins in a competitive market is not the one that checks the same boxes — it is the one that goes three layers deeper on every box.

    The short answer: Claude Cowork decomposes a vague goal like “build a listing package” into every task a top-producing agent would execute — and several they would not think of. The visible plan becomes both a training tool for newer agents and a competitive advantage for veterans who want to see what a fully-optimized listing launch actually looks like.

    Normal Search vs. a Cowork Session

    Try this comparison. Open Google and search “how to create a real estate listing package.” You will get a checklist: photos, description, comps, flyer. Generic. Useful in the way a recipe on the back of a box is useful — it gets you to edible, not exceptional.

    Now open Cowork and type: “Build a comprehensive listing package for a $1.2 million craftsman home in a competitive Pacific Northwest market. The property has original millwork, a detached garage with ADU potential, and backs to a greenbelt. Open house in 72 hours. I want to crush the competition.”

    Watch what happens. Cowork’s lead agent does not hand you a checklist. It builds a plan. The sub-agents get to work:

    One agent handles the market positioning analysis — pulling not just comps but analyzing how competing active listings in the same price band are positioned, what language they use, where they are weak. Another handles the property narrative — not a generic description but a story built around the craftsman details, the ADU upside, the greenbelt lifestyle. A third works the visual strategy — recommending specific shot lists for the photographer, suggesting twilight exterior timing, flagging the millwork details that need close-up hero shots.

    But it does not stop there. Cowork also plans the pre-marketing sequence: teaser social posts before the listing goes live, email campaign to the agent’s buyer list with an exclusive preview window, a neighborhood-specific landing page with walk score data and school catchment boundaries. It plans the open house experience: a QR code one-pager that links to the full property story, a follow-up drip sequence for sign-in attendees, and a feedback collection form that feeds back into the pricing strategy.

    That is not a listing package. That is a listing launch. And the difference between the two is exactly what separates agents who win in competitive markets from agents who participate in them.

    Why This Is a Training Tool for Agents at Every Level

    New Agents

    A new agent does not know what they do not know. They check the boxes they learned in licensing class and wonder why their listings sit. Watching Cowork decompose a listing launch shows them the full scope of what a top producer executes — not as a vague “do more” instruction but as a visible, sequenced plan with dependencies they can study and replicate.

    Experienced Agents

    Veterans have their system. It works. But it also calcifies. Running a listing through Cowork is a mirror — it shows the agent what they are already doing well and surfaces the pieces they have stopped doing because they got comfortable. The pre-marketing sequence they used to run. The competitive positioning they used to write. The follow-up system they let lapse.

    Team Leads and Brokers

    If you run a team, Cowork’s plan output is a training artifact you can standardize. Run ten different listing scenarios through Cowork. Extract the common plan structure. That becomes your team’s listing launch playbook — not a rigid checklist but a dependency-aware template that adapts to each property.

    The Deeper Point: Thinking Like a Strategist

    The gap between a good agent and a great one is not work ethic or MLS access. It is strategic depth. Great agents think three moves ahead: this photo angle will highlight that feature which will attract this buyer segment who will pay this premium. Cowork’s decomposition shows that multi-layer thinking in real time. The lead agent does not just list tasks — it sequences them in a way that reveals the strategy behind the sequence.

    A normal search gives you what to do. Cowork shows you how to think about what to do. That is the difference, and for a real estate team trying to level up, it is a significant one.

    More in This Series

    Frequently Asked Questions

    Can Claude Cowork actually build a real estate listing package?

    Cowork can plan, write, and assemble many components of a listing package — property descriptions, market positioning analysis, social media copy, email sequences, and flyer content. It will not take the photographs or upload to your MLS, but it handles the planning and content creation layers comprehensively.

    How does a Cowork listing plan compare to a normal checklist?

    A checklist tells you what to do. Cowork shows you how to think about what to do — the sequence, the dependencies, what runs in parallel, and the strategy behind each piece. A standard listing checklist might say “take photos.” Cowork’s plan specifies shot types, timing, the feature hierarchy that drives the shot list, and how the images connect to the narrative.

    Is this useful for commercial real estate too?

    Yes. Commercial listings have even more complexity — tenant financials, lease abstracts, market surveys, investment modeling. Cowork’s task decomposition handles that complexity well because the lead agent excels at managing multi-track workstreams with heavy dependencies.

    How would a brokerage use this for agent training?

    Run a variety of listing scenarios through Cowork — luxury, starter home, investment property, commercial. Extract the common plan structures. Use those plans as training artifacts during onboarding, showing new agents what a fully-developed listing launch looks like compared to the minimum checklist approach.


  • How Claude Cowork Can Fix the Handoff Problem in B2B SaaS Teams

    How Claude Cowork Can Fix the Handoff Problem in B2B SaaS Teams

    Last refreshed: May 15, 2026

    Your SaaS company just signed an enterprise deal. Implementation needs to start this week. Product is still closing a bug from the last release. Customer success is building the onboarding deck from scratch because nobody templated the last one. Support already has three tickets from the new client’s pilot users. Everyone is busy. Nobody is coordinated.

    B2B SaaS companies live and die by cross-functional handoffs. Sales closes a deal and hands it to implementation. Implementation needs product to enable features. Customer success needs support to triage the first wave of questions. Every team is excellent in isolation. The failures happen at the seams — the handoffs, the dependencies, the “I thought you were handling that” moments.

    The short answer: Claude Cowork decomposes complex cross-functional work into dependency-aware subtasks coordinated by a lead agent. For a B2B SaaS team, this makes the invisible handoff chain visible — teaching product, sales, CS, and support how their individual work creates or blocks downstream progress.

    Where SaaS Teams Break Down

    The pattern is consistent: each function knows its own work but not how it connects to the others. Sales knows the deal but not the implementation timeline. Product knows the roadmap but not what customer success promised. Support knows the tickets but not the business context behind them.

    This is a coordination problem, not a competence problem. And it is exactly the kind of problem that watching Cowork solve makes tangible.

    What Each Function Learns From Cowork

    Product

    Product teams plan in sprints and roadmaps. Cowork plans in dependency chains. When a product manager watches Cowork decompose “launch feature X for enterprise client Y” into parallel tracks — feature flag configuration, documentation update, QA regression, CS training materials — they see how their single deliverable creates five downstream dependencies. That visibility changes how PMs write their acceptance criteria and sequence their releases.

    Sales

    Sales teams hand off deals and move on. Watching Cowork decompose a deal-to-live sequence shows sales what happens after they close: implementation scoping, environment provisioning, data migration, user training, success metric definition. A salesperson who understands this chain sells differently — they set better expectations, identify blockers during discovery, and write handoff notes that actually help.

    Customer Success

    CS managers are the closest human analog to Cowork’s lead agent. They hold the relationship, coordinate across internal teams, and absorb mid-flight changes. Watching Cowork’s lead agent manage parallel workstreams and re-sequence when a blocker appears is a direct training exercise for CS managers learning to run complex enterprise accounts.

    Support

    Support tends to be reactive — ticket arrives, solve ticket, close ticket. Cowork shows how reactive work fits into a larger plan. When support sees their ticket resolution as a sub-task that unblocks the implementation track, they prioritize differently. That context turns support from a cost center into a pipeline accelerator.

    The Cross-Functional Training Session

    Take a recent enterprise onboarding that went sideways. Feed the scenario to Cowork: “Plan the full implementation and onboarding for an enterprise SaaS client with 500 users, SSO requirements, a data migration, and a 30-day success review.”

    Run it in a room with one person from each function. Watch Cowork’s plan. Then ask each person: where does your team show up in this plan? What depends on you? What are you waiting on? Where did we actually break down last time?

    The plan becomes a shared map. The discussion becomes the training.

    More in This Series

    Frequently Asked Questions

    Can Cowork replace our SaaS project management tools?

    No. Cowork shows you how to think about cross-functional coordination, not how to track it in production. Use Cowork to train your team on dependency thinking and handoff awareness, then execute in Jira, Asana, Linear, or whatever your team already uses.

    Which SaaS function benefits most from Cowork training?

    Customer success managers benefit most directly — their role mirrors Cowork’s lead agent function. But every function gains by seeing how their work creates or blocks progress for others. The cross-functional training session format delivers the most value.

    How does this help with enterprise onboarding specifically?

    Enterprise onboarding is the most complex cross-functional workflow most SaaS companies run. Cowork’s decomposition reveals every dependency, parallel track, and handoff point — making it easy to identify where onboardings historically break down and build better handoff protocols.

    Is this useful for early-stage SaaS companies?

    Especially. Early-stage teams build processes from scratch. Using Cowork to visualize cross-functional workflows before they become chaotic establishes structured thinking from day one rather than retrofitting it after failures accumulate.