Tag: Automation

  • AI for Property Managers: Free Claude Skills and Prompts

    AI for Property Managers: Free Claude Skills and Prompts

    Last refreshed: October 20, 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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    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

    Four comparison cards for Claude skills, MCP, connectors, and plugins
    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

    Four cards for content, ops, build, and knowledge work with Claude
    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/.

    Related on Tygart Media: AI for real estate · AI for insurance agents · AI for home inspectors.

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

    AI for Real Estate Agents: Free Claude Skills and Prompts

    Last refreshed: October 20, 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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    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

    Four comparison cards for Claude skills, MCP, connectors, and plugins
    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

    Four cards for content, ops, build, and knowledge work with Claude
    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/.

    Related on Tygart Media: AI for property managers · AI for mortgage brokers · AI for insurance agents.

  • AI for Restaurants: Free Claude Prompts for Owners

    AI for Restaurants: Free Claude Prompts for Owners

    Last refreshed: October 20, 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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    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

    Four comparison cards for Claude skills, MCP, connectors, and plugins
    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

    Four cards for content, ops, build, and knowledge work with Claude
    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.

    Related on Tygart Media: AI for event planners · AI for cleaning · how to use Claude.

  • Claude for Lawyers: Free Prompts & Skills for Law Firms

    Claude for Lawyers: Free Prompts & Skills for Law Firms

    Last refreshed: October 20, 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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    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

    Four comparison cards for Claude skills, MCP, connectors, and plugins
    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

    Four cards for content, ops, build, and knowledge work with Claude
    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.

    Related on Tygart Media: Claude for accountants · AI for financial advisors · how to use Claude.

  • Claude Prompts for Accountants: Free AI Skills for CPAs

    Claude Prompts for Accountants: Free AI Skills for CPAs

    Updated September 30, 2026.

    Claude Skills are folders with a SKILL.md file that Claude loads when your task fits the skill description; pair them with a Project that stores firm PDFs and custom instructions. This page gives CPAs four skills (client email, tax explanations, engagement letters, IRS notice triage), three “books” to upload, copy-paste prompts, and an FAQ. Free on claude.ai after you enable code execution and Skills.

    Client emails, engagement letters, IRS notice triage, and plain-English tax explanations eat hours you cannot bill at your real rate. Claude drafts; you review, sign, and send.

    How to Use This Page

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Set up Skills and a Project once, then reuse them across tax season.

    Setup: Enable Code execution and file creation (Settings → Capabilities; Team admins use Organization settings → Plugins & skills → Policy). Turn Skills on under Customize → Skills. Details: Use skills in Claude.

    Option A — Upload a Skill: Save each block below as SKILL.md, zip the folder, Customize → Skills → Upload a skill.

    Option B — Project instructions: At claude.ai/projects, paste the text below the YAML frontmatter into Custom instructions and upload firm PDFs to the knowledge base.

    Books for Bots are PDFs in that Project (outlines below). Prompts at the bottom work in any chat. Default to Claude Sonnet 5.5 for daily drafts; use Opus 5.5 for heavy document review.


    Claude Skills for Accountants

    Four comparison cards for Claude skills, MCP, connectors, and plugins
    Skills teach procedure; Projects hold firm context. Use both.

    Projects hold static firm context; Skills hold repeatable steps. See Skills explained.

    Skill 1: Client Email Writer

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

    Save as SKILL.md (or paste the body into Project custom instructions):

    ---
    name: cpa-client-email-writer
    description: Write professional client emails for a CPA firm. Use when the user needs status updates, document requests, deadline reminders, or sensitive emails about late payments, audits, or IRS notices.
    ---
    
    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 for client meetings, onboarding packets, and FAQ content for your website.

    Save as SKILL.md (or paste the body into Project custom instructions):

    ---
    name: cpa-tax-concept-explainer
    description: Explain tax concepts, forms, and rules in plain English for CPA firm clients. Use for client education, meeting prep, onboarding, or website FAQ drafts.
    ---
    
    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 most of the way there in one pass.

    Save as SKILL.md (or paste the body into Project custom instructions):

    ---
    name: cpa-engagement-letter-drafter
    description: Draft CPA engagement letters with scope, exclusions, and client responsibilities. Use when the user describes a new client or new service scope.
    ---
    
    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, assess what it is, draft a client-calming explanation, and outline response steps. Nothing goes to the IRS from Claude without your review.

    Save as SKILL.md (or paste the body into Project custom instructions):

    ---
    name: cpa-irs-notice-triage
    description: Triage IRS notices for CPA firms: plain-English summary, severity, next steps, and a short client email. Use when the user describes or pastes notice details.
    ---
    
    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

    Export each outline as a PDF and add it to your Project knowledge base. Refresh when policies change.

    Book 1: Firm Context Sheet — Name, partners, locations, service lines, client types, states licensed, billing model, portal, tone paragraph.

    Book 2: Client Communication Standards — Redacted examples: missing docs, extension reminders, late fees, bookkeeping clean-up quotes.

    Book 3: Common Client Questions Reference — Twenty-five FAQs with firm-approved answers. Publish the same language on your site and run AI citation monitoring to see what answer engines quote.


    Ready-to-Use Prompts

    Four cards for content, ops, build, and knowledge work with Claude
    Prompts for meetings, site copy, onboarding, and referrals.

    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. After publishing, track whether AI assistants surface the page using a baseline from LLM visibility measurement.

    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. For a firm-specific stack — services, voice, and pages that answer AI search — we build operating layers. See GEO case studies from 2026 before cloning generic FAQ copy.

    Related on Tygart Media: Claude for lawyers · AI for financial advisors · how to use Claude.

    FAQ

    What is the difference between a Claude Skill and Project custom instructions?

    A Skill is a packaged SKILL.md file you upload under Customize → Skills; Claude loads it when your task matches the skill description. Project custom instructions apply to every chat inside that Project and work well with uploaded firm PDFs. Most firms use a Project for context and one or more Skills for repeatable drafting workflows.

    Do I need a paid Claude plan to use Skills?

    Anthropic lists Skills on Free, Pro, Max, Team, and Enterprise plans, with code execution enabled. Your firm’s admin may restrict file creation or Skills on Team and Enterprise — check Organization settings if toggles are greyed out.

    Can Claude send IRS responses or legal advice for me?

    No. Use the IRS notice skill for triage and client communication drafts only. A licensed CPA must verify facts, amounts, and deadlines before anything goes to the IRS or into a signed return.

    Which Claude model should accountants use?

    For routine email, FAQs, and engagement letter drafts, Claude Sonnet 5.5 is the practical default as of late September 2026. Use Claude Opus 5.5 when you need heavier reasoning across long documents and you have time to review the output carefully.

    Is it safe to paste client data into Claude?

    Treat Claude like any cloud tool: follow your firm’s confidentiality policy, use redacted or synthetic examples when training skills, and prefer Projects with the minimum necessary client detail. When in doubt, remove identifiers and ask for structure only — you add account numbers and EINs locally.

  • Anthropic Cowork GA: Desktop Automation for Non-Developers

    Anthropic Cowork GA: Desktop Automation for Non-Developers

    Last refreshed: October 20, 2026

    Anthropic’s Cowork feature — the desktop automation tool aimed squarely at non-developers — moved out of research preview on April 29, 2026, and is now generally available on both macOS and Windows. It ships with a feature set that represents a meaningful step forward for anyone who has been running scheduled tasks, file workflows, and multi-step automations through Claude without writing a line of code.

    What’s New in the GA Release

    Three stacked layers: chat UI, tools, agent runtime
    What’s new in the Cowork GA release.

    The GA release lands on Pro, Max, Team, and Enterprise plans. The headline additions are expanded analytics, OpenTelemetry support for enterprise observability, and role-based access controls — the last of these being the signal that Cowork is now ready for team deployments, not just individual power users.

    Persistent agent threads are now live across both mobile (iOS and Android) and desktop, which means you can start a Cowork task on your laptop and monitor or manage it from your phone. The new Customize section consolidates skills, plugins, and connectors into a single panel, replacing what was previously a scattered setup experience across multiple menus.

    Recurring and on-demand task scheduling is also included, enabling the kind of “set it and check it” automation workflows that Cowork was always promising but only partially delivering during the preview period.

    Why This Matters for Non-Developers

    Four cards for content, ops, build, and knowledge work with Claude
    Why this matters for non-developers.

    Cowork’s core bet has always been that the most valuable use cases for AI automation don’t belong to engineers — they belong to operators, marketers, content teams, and business owners who know exactly what they want done but have no interest in writing Python scripts or JSON configs to get there. The GA release validates that bet with a production-grade infrastructure story: OpenTelemetry means IT and enterprise security teams can audit what the agents are doing; role-based access controls mean managers can delegate without handing over full system access.

    For the non-developer using Cowork day-to-day, the practical change is reliability. Research previews carry an implicit asterisk — “this works, mostly, until it doesn’t.” GA means the feature is supported, documented, and subject to real SLAs. Scheduled tasks that have been running through the preview period should now be more stable, and new automations can be built with the expectation that they’ll still work next month.

    The Enterprise Observability Story

    Five security domains: identity, data, code governance, audit, agents
    The enterprise observability story.

    The addition of Cowork data into the Analytics API and OpenTelemetry support is worth noting separately. This is the detail that unlocks enterprise adoption at scale. Procurement and security teams at larger organizations have consistently asked for auditability before green-lighting AI automation tools. Cowork now has an answer: every agent action can be traced, logged, and routed into whatever observability stack the enterprise already runs.

    For Team and Enterprise plan subscribers, this should accelerate internal approval processes for Cowork deployments that may have stalled during the preview period.

    What Stays the Same

    The fundamental Cowork model — Claude running autonomous tasks on behalf of the user, triggered by schedule or on-demand, guided by skills and connectors — is unchanged. If you’ve been running workflows in the preview, the transition to GA should be seamless. The Customize section reorganizes the setup experience but doesn’t require rebuilding existing configurations.

    Plans and pricing remain unchanged from the research preview tier placement — Cowork is included in Pro, Max, Team, and Enterprise, with no new add-on cost announced alongside the GA release.

    The Bottom Line

    Cowork GA is the milestone that turns a promising experiment into a product you can build operational workflows around. The combination of persistent threads, role-based access, and OpenTelemetry support brings Cowork into alignment with what enterprise buyers require from any automation tool they’re willing to run at scale. For individual users, the reliability improvement and the cleaner Customize panel are the day-one wins. For teams, the observability story is the green light many have been waiting for.

    Source: Anthropic Cowork Release Notes

    Related on Tygart Media: Claude Cowork · Cowork Routines.

  • Notion AI vs Zapier AI: Which Automation Layer Wins For Your Use Case

    Notion AI vs Zapier AI: Which Automation Layer Wins For Your Use Case

    Related on Tygart Media: vs n8n · vs ChatGPT.

    The 60-second version

    Zapier and Notion AI overlap in concept (automate routine work) but optimize for different operators. Zapier: massive integration catalog, no-code, simple triggers and actions, optimized for “if this, then that” patterns. Notion AI: AI reasoning native, deep workspace context, optimized for “decide what to do given context, then act.” Use Zapier for breadth of simple automations. Use Notion Agents for depth of reasoning. The two are complementary.

    When Zapier wins

    Side-by-side when to use a script versus an agent
    When Zapier wins the automation layer.
    • You need many simple automations across many apps
    • Non-technical operators need to build automations themselves
    • The trigger logic is straightforward (if X, do Y)
    • You don’t have or want AI reasoning in the loop
    • You’re not heavily invested in Notion as a platform

    When Notion Agents win

    Three stacked layers: chat UI, tools, agent runtime
    When Notion Agents win.
    • The workflow requires understanding Notion workspace content
    • AI reasoning about whether and how to act matters
    • Schedule-driven autonomous work is the goal
    • The workflow output is in Notion or affects Notion data
    • You want agents that can compose multi-step reasoning

    What Zapier does that Notion Agents don’t

    • Thousands of app integrations out of the box
    • Visual no-code building accessible to non-developers
    • Flat-rate pricing easier to budget
    • Established for years; lots of recipes and patterns

    What Notion Agents do that Zapier doesn’t

    • AI reasoning native to the workflow
    • Workspace context understanding
    • Skills (natural-language workflow definitions)
    • Workers for custom code
    • Database fluency at the platform level

    The combined pattern

    Three panels showing one problem, three options, one recommendation
    The combined pattern.

    Many operators use both:
    – Zapier for cross-app plumbing (lead from form → CRM → Slack → email)
    – Notion Agents for workspace reasoning (synthesize lead context, decide priority, draft response)
    – Sometimes Zapier triggers a Notion agent run
    Treat them as layers: Zapier moves data; Notion Agents make decisions about that data.

    Where this goes wrong

    1. Trying to use Zapier for AI reasoning. Zapier has AI features but they’re shallow compared to Notion Agents.
    2. Trying to use Notion Agents for cross-app plumbing. Possible via Workers/MCP, but Zapier’s integration catalog is broader.
    3. Picking based on price alone. The right tool for the job costs less than the wrong tool, even at higher per-task pricing.

    What to read next

    Notion Agents vs n8n Alone, n8n MCP Bridge, Workers + External APIs, AI-Native Company Patterns.

  • Claude Cowork Marketing Training: Break Department Silos

    Claude Cowork Marketing Training: Break Department Silos

    Last refreshed: October 20, 2026

    Your marketing department has a product launch in three weeks. Paid ads need creative. Email needs a nurture sequence. Social needs a content calendar. The blog needs a feature article. The PR person needs talking points. The landing page needs copy. Everyone is waiting on everyone else, and nobody owns the timeline.

    Marketing departments are coordination engines that rarely see themselves that way. Each function — paid media, organic social, email, content, PR, web — operates with its own tools, its own calendar, and its own definition of “done.” The marketing director is supposed to hold it all together, but the connective tissue between functions is usually a spreadsheet and a weekly standup that runs long.

    The short answer: Claude Cowork’s lead agent decomposes a marketing initiative into parallel workstreams with visible dependencies — the same orchestration a marketing director performs but rarely makes explicit. Running a product launch or campaign through Cowork shows every team member how their deliverable connects to, blocks, or accelerates every other team member’s work.

    The Campaign as a Project (Not a Collection of Tasks)

    Side-by-side cards defining what Claude Code is and is not
    The campaign as a project — not a collection of tasks.

    Most marketing teams plan campaigns as task lists: write the email, design the ad, publish the blog post. What they miss is the dependency chain. The ad creative depends on the messaging framework. The email sequence depends on the landing page being live. The social calendar depends on having the blog content to link to. The PR talking points depend on the positioning the brand team approved.

    These dependencies exist whether you map them or not. When you do not map them, they surface as bottlenecks, missed deadlines, and the classic marketing department complaint: “I cannot start until someone else finishes.”

    Cowork maps them. Visibly. In real time. Feed it “plan a full product launch campaign across paid, organic social, email, content, and PR with a landing page and a three-week runway” and watch the lead agent build the dependency chain from positioning down to individual deliverables.

    What Each Marketing Function Learns

    Three stacked layers: chat UI, tools, agent runtime
    What each marketing function learns.

    Paid Media

    Paid media specialists often start from creative and work backward. Cowork’s plan starts from positioning and works forward — messaging framework first, then creative brief, then ad variations. Watching this sequence teaches paid teams to anchor their work in strategy rather than execution, which produces ads that convert instead of ads that just exist.

    Email Marketing

    Email marketers learn sequencing from Cowork’s plan: welcome email depends on landing page, nurture sequence depends on content calendar being set, re-engagement triggers depend on analytics instrumentation. The dependency chain reveals why their email goes out late — it is usually not their fault. Something upstream was not finished.

    Social Media

    Social teams work on the fastest cycle in marketing — daily or even hourly. Watching Cowork plan a social calendar as one parallel track alongside paid, email, and content shows social managers how their work amplifies (or is amplified by) every other function. The timing dependencies become clear: tease before launch, amplify at launch, sustain after launch.

    Content

    Content teams are usually the bottleneck because everyone needs content but nobody accounts for the production timeline. Cowork’s plan makes the content dependency visible to the whole team — when content starts, what it depends on, and what it unlocks. That visibility protects the content team from unrealistic deadlines because the whole team can see the constraint.

    PR and Communications

    PR operates on a longer lead time than most marketing functions. Cowork’s plan reveals why PR needs to start before everyone else — media pitches go out weeks before launch, talking points need approval cycles, and embargo dates create hard dependencies that the rest of the campaign must respect.

    The Marketing Department Training Session

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    The marketing department training session.

    Take your next product launch or major campaign. Before anyone starts working, run the brief through Cowork: “Plan a comprehensive marketing launch for [product] targeting [audience] across paid, organic, email, content, PR, and web. Three-week timeline. Budget-conscious.”

    Project the plan. Walk through it with the full team. Each person identifies their workstream, their dependencies, and their deliverables. You now have a shared plan that everyone understands — not because the marketing director explained it in a meeting, but because they watched it get built.

    Do this once and your campaign coordination will improve. Do it for every major initiative and you are building a team that thinks in systems instead of silos.

    More in This Series

    Frequently Asked Questions

    Can Cowork actually execute marketing campaigns?

    Cowork can plan campaigns, write copy, draft emails, create content outlines, and build social calendars. It cannot buy ads, send emails through your ESP, or post to social platforms directly. Use it for the planning and content creation layers, then execute in your existing marketing stack.

    How does this differ from using a marketing project management tool?

    Tools like Asana, Monday, or Wrike help you track tasks. Cowork helps you think about tasks — specifically, how to decompose a goal into sequenced, dependency-aware deliverables. Use Cowork to build the plan, then import that thinking into your PM tool for execution tracking.

    Which marketing function benefits most?

    Marketing directors and campaign leads benefit most because they mirror Cowork’s lead agent role — coordinating across functions. But every specialist benefits from seeing how their work fits into the full dependency chain.

    Is this useful for one-person marketing departments?

    Especially useful. A solo marketer is all the functions at once. Cowork’s decomposition helps them sequence their own work across roles, avoid context-switching waste, and identify which tasks are truly blocking versus which ones feel urgent but can wait.

  • Claude Cowork Staff Training: Teach Better Project Planning

    Claude Cowork Staff Training: Teach Better Project Planning

    Last refreshed: October 20, 2026

    What if the most powerful staff training tool you’ll touch this year is hiding inside an AI app you already pay for?

    There is a quiet productivity feature inside Claude Cowork that almost nobody is talking about. It is accidentally one of the best project management training tools I have ever seen — and once you notice it, you cannot unsee it.

    The short answer: Claude Cowork shows you its plan and progress in real time as it decomposes a task into sub-tasks and delegates them to a team of sub-agents. That visible decomposition — the same skill a great project manager uses every day — turns Cowork into a live training tool for any staff member learning to break down ambiguous work into executable pieces.

    The Difference Between Chat and Cowork

    Side-by-side cards defining what Claude Code is and is not
    The difference between Chat and Cowork.

    When you work with Claude in chat, you hand it a prompt and you get an answer. It is fast, it is useful, and most of the work happens invisibly — somewhere between your question and the response. You do not see the thinking. You do not see the breakdown. You just see the output.

    Cowork is different. When you give Cowork a task, you watch it work. Anthropic’s own documentation confirms this: Cowork shows progress indicators at each step, surfaces its reasoning, and lets you steer mid-task to course-correct or add direction. For complex work, it coordinates multiple sub-agents running in parallel.

    That transparency is the feature. And it is the feature that makes it a training tool.

    The Conductor and the Section Players

    Three stacked layers: chat UI, tools, agent runtime
    The conductor and the section players.

    Here is what is actually happening under the hood — and this is the part I had to confirm because I had been assuming it.

    Cowork uses the same agentic architecture as Claude Code. A lead agent (the orchestrator) takes the overall task, decomposes it into subtasks, and delegates those subtasks to specialized sub-agents. The lead maintains oversight, handles dependencies, sequences work when one piece depends on another, and synthesizes the final result. Sub-agents work independently in their own context windows and can flag dependencies back to the lead.

    It is a conductor with a section of players. The conductor does not play the violin. The conductor decides when the violins come in, how loud, and for how long.

    This is exactly how a competent project manager operates.

    Why This Matters for Training Your Staff

    Most people — including most project managers I have worked with — struggle with one specific skill: taking a messy, ambiguous goal and breaking it into a sequence of manageable, dependency-aware tasks. It is the difference between “we need to launch the new site” and a project plan with seventeen sequenced items, three parallel workstreams, and clear handoff points.

    Cowork does this decomposition in front of you, in plain English, every time you give it a task. You can literally watch a lead agent think through: what does this goal actually require, what order do the pieces need to go in, what can happen in parallel, what is the dependency chain, and how do I know when we are done?

    For a PM in training, that is a live demonstration of planning. For a staff member who has never had to structure work before, it is a mental model they can borrow.

    The “Oh Yeah, I Forgot About This” Superpower

    The part I love most: you can interrupt Cowork while it is running. You can ask a question. You can add a requirement. You can redirect a visual task. And because there is a lead agent holding the plan, it does not panic — it queues your input and addresses it when appropriate.

    That is exactly how you should be working with human teams. You should not be afraid to say “oh wait, I forgot we also need X” to a project manager. A good PM takes the new input, figures out where it fits in the plan, and slots it in without derailing everything else.

    Watching Cowork do this gracefully is a training moment. It shows people that mid-flight course corrections are normal, that good planning systems absorb new information rather than break from it, and that the conductor’s job is to keep the music going even when the score changes.

    How to Actually Use Cowork to Train a Team

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    How to actually use Cowork to train a team.

    A few things I would try with a team:

    Run a Cowork narration session. Have a new project manager watch Cowork tackle a real task end-to-end and narrate what it is doing and why. Then ask them to plan a real project the same way — out loud, decomposed, with dependencies called out.

    Use Cowork as a planning artifact generator. When someone on your staff hands you a vague goal, run it through Cowork first. Not because Cowork will do the work, but because the plan Cowork produces is a teaching artifact. You can review it together: here is how the task should be broken down, here is the order, here is what runs in parallel.

    Teach delegation by example. When you are training someone to delegate, have them watch how the lead agent assigns work to sub-agents. Narrow scope, clear instructions, defined handoff. That is delegation 101, executed live.

    The Bigger Point

    Tools that hide their thinking make you dependent on them. Tools that show their thinking make you better.

    Chat hides the thinking. Cowork shows the thinking. And the thinking it shows happens to be the exact cognitive skill — structured task decomposition — that separates people who manage projects well from people who drown in them.

    If you are running an agency, a team, or any operation that depends on people learning to break down ambiguous work into executable pieces, Cowork is not just a productivity tool. It is a classroom.

    Frequently Asked Questions

    What is Claude Cowork?

    Claude Cowork is Anthropic’s agentic desktop application that takes on multi-step knowledge work tasks autonomously. Unlike chat, where you exchange single messages, Cowork accepts a goal, builds a plan, and executes it across files and applications on your computer using the same agentic architecture as Claude Code.

    How is Cowork different from Claude chat?

    Chat responds to one prompt at a time and hides its reasoning between your message and its reply. Cowork takes on full tasks, shows you its plan and progress in real time, and lets you steer mid-task. It also coordinates multiple sub-agents in parallel for complex work.

    Does Claude Cowork actually use multiple agents?

    Yes. For complex tasks, Cowork uses a lead/orchestrator agent that decomposes the work and delegates sub-tasks to specialized sub-agents that run in parallel. The lead handles dependency ordering and synthesizes results when work is complete. This is the same supervisor pattern used in Claude Code’s agent teams feature.

    Can I interrupt Cowork while it is running?

    Yes. You can jump in mid-task to ask questions, add requirements, redirect work, or course-correct. The lead agent queues your input and addresses it at the appropriate point in the plan rather than abandoning what is already in motion.

    How can a manager use Cowork to train staff?

    Use Cowork as a live demonstration of structured task decomposition. Have new project managers narrate what Cowork is doing and why, then plan their own projects the same way. Use the plans Cowork generates as teaching artifacts to discuss task breakdown, dependency mapping, and parallel workstreams. Watch the lead agent’s delegation patterns — narrow scope, clear instructions, defined handoffs — as a model for how humans should delegate.

    Who is Claude Cowork designed for?

    Cowork was built for non-technical knowledge workers — researchers, analysts, operations teams, legal and finance professionals — who work with documents, data, and files daily and want to spend more time on judgment calls and less time on assembly. It is available on Pro, Max, Team, and Enterprise plans through the Claude desktop app.

    Does Cowork work alongside Claude in chat?

    Yes. Chat remains useful for quick questions, single-step tasks, and conversational work. Cowork takes over when the work requires planning, multi-step execution, or coordination across files and applications. The same Claude account uses both modes.

    The Full Series: Cowork as a Training Tool by Industry

    More on Claude Cowork



  • Claude Cowork Marketing Training: Break Channel Silos

    Claude Cowork Marketing Training: Break Channel Silos

    Last refreshed: October 20, 2026

    A marketing department runs ads, manages social media, sends email campaigns, produces content, tracks analytics, and coordinates with sales — and the person running it is usually the only one who sees how all those pieces connect.

    That is the bottleneck nobody names: the marketing director is the orchestration layer. When they leave, get sick, or go on vacation, the department does not stop working — but it stops being coordinated. The social person keeps posting. The email person keeps sending. The ad person keeps spending. But nobody is conducting the orchestra.

    Claude Cowork makes the orchestration visible. And when the orchestration is visible, anyone on the team can learn it.

    The short answer: Claude Cowork decomposes marketing campaigns into coordinated workstreams — ads, social, email, content, analytics — and shows how they depend on each other. That visible coordination teaches every marketing team member how their channel connects to the larger campaign, turning channel specialists into campaign thinkers.

    The Channel Silo Problem

    Comparison of Claude how-to fit versus local service page fit for assistants
    The channel silo problem.

    Most marketing teams are organized by channel: one person does social, one does email, one manages ads, one writes content. Each person becomes excellent at their channel. But they rarely understand how their channel’s timing, messaging, and audience targeting should coordinate with the other channels on the same campaign.

    The result is campaigns that look coordinated on the surface — same brand, same general message — but are not actually orchestrated. The email goes out before the landing page is ready. The social posts promote a feature the ad copy does not mention. The content piece that should be driving traffic gets published two days after the ad campaign ended.

    How Cowork Trains Each Marketing Role

    Side-by-side cards defining what Claude Code is and is not
    How Cowork trains each marketing role.

    The Social Media Manager

    Give Cowork a campaign task: “We are launching a product update in two weeks. Build me the complete social media plan that coordinates with our email announcement, landing page update, paid ad campaign, and blog post.”

    Cowork does not build a social calendar in isolation. It builds a social plan that references the other channels: pre-launch teaser posts that build anticipation before the email goes out, launch-day posts timed to fire after the email sends (so early adopters amplify the message), post-launch engagement posts that reference the blog content, and paid social ads that retarget people who visited the landing page but did not convert. The social manager sees their channel as part of a system — not a standalone publishing schedule.

    The Email Marketer

    Give Cowork: “Build me the email sequence for this product launch. We have a general subscriber list, a segment of active users, and a segment of churned users. Each segment needs different messaging. Coordinate the send times with our social and ad schedules.”

    Cowork breaks the email plan into segment-specific tracks with timing that accounts for the other channels. The general list gets the announcement after social has been teasing it. Active users get early access before the public launch. Churned users get a re-engagement angle timed after the launch buzz has created social proof. The email marketer sees that send timing is a strategic decision connected to the whole campaign — not just “Tuesday morning works best.”

    The Paid Media Specialist

    Give Cowork: “Build me the paid advertising plan for this launch across Google Ads and social platforms. Budget is limited so every dollar needs to coordinate with organic efforts.”

    Cowork plans ad spend around organic momentum: heavy spend when organic buzz is generating search interest, retargeting campaigns that capture visitors driven by email and social, and budget reallocation triggers based on what channels are performing. The paid specialist sees that ad strategy is not just bidding and targeting — it is timing spend to amplify what the rest of the marketing machine is already doing.

    The Content Marketer

    Give Cowork: “Build me the content plan that supports this launch. We need a blog post, a case study update, and landing page copy. Each piece needs to serve a different stage of the buyer journey and coordinate with the distribution channels.”

    Cowork maps each content piece to a funnel stage and a distribution channel: the blog post drives top-of-funnel awareness and gets distributed via social and email, the case study serves mid-funnel consideration and gets linked from the landing page and ad copy, and the landing page serves bottom-funnel conversion and receives traffic from all other channels. The content marketer sees that content creation is half the job — distribution strategy is the other half.

    Why This Matters for Marketing Leaders

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Why this matters for marketing leaders.

    The most expensive problem in marketing is not bad creative or wrong targeting. It is lack of coordination. Campaigns underperform not because the individual pieces are weak but because the pieces do not reinforce each other.

    Cowork makes coordination teachable. When every team member watches a campaign get decomposed into interdependent workstreams, they absorb the orchestration logic that usually lives only in the marketing director’s head. That does not just improve the current campaign. It makes the team capable of running coordinated campaigns even when the director is not in the room — which is the definition of a scalable marketing operation.

    Related on Tygart Media: staff training · Cowork for agencies · LinkedIn content strategy.

    Frequently Asked Questions

    How does Claude Cowork help marketing teams specifically?

    Cowork decomposes marketing campaigns into coordinated workstreams — ads, social, email, content, analytics — and shows how they depend on each other. That visible coordination teaches every team member how their channel connects to the larger campaign.

    Can Cowork plan a full marketing campaign?

    Cowork can decompose a campaign into detailed workstreams with timing, dependencies, and channel coordination. The plans it generates serve as teaching artifacts and coordination frameworks. Execution still happens in your existing marketing tools.

    Does this replace a marketing director?

    No. A marketing director brings strategic judgment, brand understanding, and relationship context that Cowork does not have. What Cowork does is make the orchestration skill visible so other team members can learn it — reducing the bottleneck on one person being the only one who sees the whole picture.

    Which marketing role benefits most?

    Channel specialists benefit most — social media managers, email marketers, ad specialists, and content marketers. These roles are typically trained on their channel in isolation. Watching Cowork plan a coordinated campaign teaches them how their channel fits into the system.