Tag: AI for Business

  • 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.

  • Claude for Law Firms: AI Legal Research and Drafting

    Claude for Law Firms: AI Legal Research and Drafting

    Last refreshed: October 20, 2026

    Law firms have always been early adopters of tools that compress billable time. Document review software. Legal research databases. E-discovery platforms. The pattern is consistent: the firms that adopt early capture the margin advantage, and the rest catch up at cost.

    Claude is following that pattern. And the window where using it is a competitive advantage rather than table stakes is closing faster than most legal professionals realize.

    This is a practical guide to where Claude actually delivers in legal work — not theoretical use cases, but the specific tasks where it earns its keep — and where you still need a human in the loop.

    Where Claude Delivers the Most Value in Legal Practice

    Four cards for content, ops, build, and knowledge work with Claude
    Where Claude delivers the most value in legal practice.

    Legal Research and Case Law Summarization

    The highest-leverage use case for most attorneys is research compression. Claude can take a 40-page appellate decision and return a structured summary — holding, reasoning, key facts, dissent — in under 60 seconds. It can synthesize across multiple cases to identify how a circuit has treated a specific doctrine over time.

    What it cannot do: verify citations autonomously or guarantee it has not hallucinated a case name. Every citation must be independently verified in Westlaw or Lexis before it goes into a brief. Claude is the first pass, not the final check.

    Practical workflow: paste the full text of the opinion (Claude’s 200K context window handles most decisions comfortably), ask for a structured summary with specific fields — holding, key facts, procedural posture, distinguishing factors — and use that as the basis for your own analysis rather than the analysis itself.

    Contract Drafting and Redlining

    Claude handles first-draft contract language well, particularly for standard commercial agreements where the structure is predictable: NDAs, MSAs, employment agreements, vendor contracts. Give it the deal terms and the governing law, and it produces a serviceable first draft that your attorney then marks up rather than writing from scratch.

    For redlining, paste the counterparty’s draft and ask Claude to identify provisions that deviate from market standard, flag missing protections, or summarize the risk profile of specific clauses. It catches things that get missed at 11pm on a deal close.

    The limitation: Claude does not know your client’s specific risk tolerance, industry norms for your particular market, or the negotiating history with this counterparty. Those judgment calls remain human work.

    Deposition and Discovery Preparation

    One of the most underused legal applications is using Claude to prepare for depositions. Feed it the deponent’s prior testimony, relevant documents, and the key issues in the case. Ask it to generate a question outline organized by theme, flag inconsistencies in prior statements, and identify documents to confront the witness with.

    It can also process large document productions and summarize by custodian, date range, or topic — substantially reducing the time a paralegal or junior associate spends on initial review.

    Client Communication and Memo Drafting

    Client-facing memos — explaining a legal issue in plain language, summarizing a court ruling’s implications, drafting a status update — are exactly the kind of writing where Claude performs well and where attorneys often underinvest time. The work is important but not intellectually complex. Claude produces a solid draft; the attorney reviews, adjusts for client relationship context, and sends.

    What Claude Cannot Do in Legal Work

    Seven cards naming common AI chatbot failure modes
    What Claude cannot do in legal work.
    • It cannot verify citations. It will hallucinate case names and citations with confidence. Every citation must be checked against an authoritative legal database.
    • It cannot provide legal advice. It produces language and analysis, not professional judgment. The attorney exercises judgment; Claude compresses the work that precedes it.
    • It does not know current law. For recent statutory changes, new regulations, or fresh precedent, you need current research tools.
    • It lacks client context. Claude does not know your client’s history, risk appetite, or the relationship dynamics that shape legal strategy.
    • Confidentiality considerations apply. Before pasting client documents into any AI tool, your firm needs a clear policy on what data is permissible to process externally and under what terms.

    Getting Claude Set Up for Legal Work

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    Getting Claude set up for legal work.

    The most effective legal deployment of Claude is not the chat interface — it is Claude with a strong system prompt that establishes context, format expectations, and guardrails. A system prompt for a litigation practice might specify the governing jurisdiction, output format requirements, what it should flag for attorney review, and firm-specific terminology.

    For firms with technical capacity, Claude’s API allows integration directly into document management systems, allowing attorneys to invoke Claude without leaving the tools they already use.

    The Billing Question

    The elephant in the room for law firms considering AI adoption is the billing model. If Claude compresses a five-hour research task to one hour, do you bill five hours or one?

    The firms navigating this well are shifting toward value billing and fixed-fee arrangements where efficiency is profit rather than a billing problem. The ABA and state bars are actively developing guidance on AI use and disclosure. Following your jurisdiction’s bar guidance and staying current on disclosure requirements is non-negotiable.

    Bottom Line

    Claude does not replace legal judgment. It compresses the work that precedes judgment — research, drafting, review, summarization — at a quality level that makes it worth building into the workflow of any firm serious about efficiency. Pick one task category, run Claude against your next ten instances of that task, and measure the time delta. The ROI case makes itself.

    Related on Tygart Media: Claude for lawyers · law firm AI citations · how to use Claude.

  • Anthropic Revenue 2026: $30B Run Rate & Amazon Compute

    Anthropic Revenue 2026: $30B Run Rate & Amazon Compute

    Last refreshed: October 20, 2026

    Three data points published in the last two weeks of April 2026 define the scale at which Anthropic is now operating: a 5-gigawatt compute capacity commitment from Amazon announced April 20, a disclosed $30 billion annual revenue run rate (up from $9 billion at the end of 2025), and a customer base of more than 1,000 enterprises spending over $1 million per year. Taken together, they describe a company that has crossed the threshold from frontier AI lab to large-scale enterprise infrastructure provider.

    The Amazon Compute Commitment

    Five-step path: account, API keys, billing, usage, workspaces
    The Amazon compute commitment.

    Five gigawatts of committed compute capacity is a number that requires context to land properly. For reference, a large data center campus typically consumes 100–500 megawatts. Five gigawatts is the equivalent of 10–50 large data center campuses worth of compute, committed to a single AI company. This is infrastructure at a scale that was historically reserved for hyperscalers building general-purpose cloud platforms — not AI model providers.

    The Amazon partnership is part of a broader compute story that also includes Google and Broadcom’s multi-gigawatt TPU partnership (announced April 6, with capacity launching in 2027). Anthropic is not building this infrastructure itself — it’s securing committed capacity from the two largest cloud providers simultaneously, which is a different and arguably more capital-efficient strategy than building proprietary data centers.

    Revenue: $9B to $30B in One Quarter

    The jump from $9 billion to $30 billion annualized run rate between end of 2025 and April 2026 is the most striking number in the disclosure. That’s not organic growth — that’s a step change that implies either a major enterprise contract cohort closing in Q1 2026, the Cowork and Claude Code adoption curves hitting inflection simultaneously, or both. The 1,000+ customers at $1 million+/year figure is consistent with enterprise adoption at scale: at $1 million average, 1,000 customers represents $1 billion in ARR from that cohort alone.

    For context on what $30 billion run rate means competitively: OpenAI disclosed approximately $3.7 billion in annualized revenue in mid-2024. If Anthropic’s figure is accurate and current, it suggests the competitive landscape has shifted more dramatically than most public coverage has reflected.

    What This Means for Enterprise Buyers

    Floor versus ceiling cards for commoditized work and human-network premium
    What this means for enterprise buyers.

    Enterprise procurement teams evaluating AI vendors weigh financial stability heavily. A vendor that might not exist in 18 months is a vendor you don’t build critical workflows on. The combination of $30 billion run rate, 5 gigawatts of committed compute, and 1,000+ million-dollar customers removes the financial stability objection from the Anthropic procurement conversation in a way that a year ago it couldn’t.

    The Raj Narasimhan board appointment (April 14) is a governance signal in the same direction. Board composition at this revenue scale shapes how enterprise legal and compliance teams assess vendor risk. A mature board with enterprise-credible governance is a procurement unlock, not just a PR announcement.

    The Capacity Question

    Three panels showing one problem, three options, one recommendation
    The capacity question.

    The Google/Broadcom TPU capacity doesn’t launch until 2027. The Amazon commitment is a forward contract, not immediately available infrastructure. This means Anthropic is building compute capacity commitments ahead of demand — the right bet if the revenue trajectory continues, a costly overcommit if it doesn’t. The 2027 capacity launch timing will be worth watching against the actual demand curve that develops over the next 12 months.

    Source: Anthropic News

    Related on Tygart Media: Anthropic IPO · history of Anthropic · Claude pricing.

  • AI-Native Company Patterns: How Notion Agents Reshape the Org Chart

    AI-Native Company Patterns: How Notion Agents Reshape the Org Chart

    Related on Tygart Media: second-brain architecture · Notion second brain setup · Notion Command Center.

    The 60-second version

    The honest framing is uncomfortable: Custom Agents handle the work that historically required junior operational staff. Status reports, intake processing, lead enrichment, weekly digests, calendar prep, recurring deliverables. AI-native companies don’t add agents alongside that work — they replace that work with agents and reassign the humans to what humans actually do better. Editorial judgment. Client relationships. Strategic decisions. Handling exceptions. The org chart shifts. Pretending it doesn’t is denial.

    What roles change first

    Floor versus ceiling cards for commoditized work and human-network premium
    What roles change first.

    Five roles where the work compresses fastest:
    – Coordinator/admin work — meeting scheduling, calendar prep, follow-up tracking. Largely automatable.
    – Junior analyst work — data pulls, report generation, basic synthesis. Largely automatable.
    – First-tier intake — categorizing inbound leads, support tickets, content submissions. Largely automatable.
    – Status communication — weekly updates, project digests, standup notes. Largely automatable.
    – Documentation upkeep — keeping wikis, runbooks, and SOPs current. Largely automatable with Autofill + agents.
    This isn’t a prediction; it’s already happening in operator-led companies that have built Custom Agents for these workflows.

    What roles get more important

    The same shift makes other roles more valuable:
    – Editorial leadership — defining voice, judgment, standards. Agents follow standards; they don’t write them.
    – Relationship work — sales relationships, client management, partnerships. Humans signal humanity.
    – Exception handling — the 5% of cases that don’t fit the agent’s pattern. This becomes the human’s whole job.
    – System design — building the agents, prompts, skills, and workflows themselves. The new ops role.
    – Strategic work — deciding what the company should do, not how to do it.

    The new org shape

    Three stacked layers: chat UI, tools, agent runtime
    The new org shape.

    A simple four-layer pattern:
    1. Agent operators — humans who design, monitor, and improve agent workflows
    2. Exception handlers — humans who catch what agents can’t handle
    3. Relationship leads — humans who own external-facing work that requires being human
    4. Strategists — humans who decide what to do
    Notice what’s missing: layers of middle management whose primary job was coordinating between doers. Agents reduce coordination overhead because they don’t need it.

    How to transition

    Three panels showing one problem, three options, one recommendation
    How to transition.

    For most operators, the shift looks like:
    – Stop hiring for roles where agents could do 70% of the work. Build the agent instead.
    – Reassign current staff toward exception handling, relationship work, and editorial judgment.
    – Invest in agent operator skills — prompt design, workflow design, rubric design.
    – Compress the org chart. Fewer layers, broader roles, sharper accountability.
    This is a multi-year shift, not a quarter. But the operators who start now have years of compounding advantage over those who delay.

    The risk

    The risk is reorganizing too fast and losing institutional knowledge that lived in the eliminated roles. Agents don’t pick up tribal knowledge automatically. The transition needs to capture what departing staff knew and encode it in the second brain so the agents can use it.

    What to read next

    Editorial Surface Area, Second-Brain Architecture, ROI Math, When Not to Use a Notion Agent.

  • Notion AI vs Microsoft Copilot: Two Philosophies of Embedded AI

    Notion AI vs Microsoft Copilot: Two Philosophies of Embedded AI

    Related on Tygart Media: vs ChatGPT · Copilot productivity.

    The 60-second version

    The choice is philosophical, not feature-by-feature. Notion AI says: “build your work in one structured workspace and let AI flow through everything.” Microsoft Copilot says: “use the tools you already use and let AI sit inside each one.” Both are valid. Both work. Which fits depends on whether your team’s pattern is consolidated workspace or distributed productivity suite.

    When Notion AI wins

    • You want one unified workspace
    • Custom Agents and scheduled autonomous work matter
    • Database-driven workflows and Autofill are core
    • Smaller teams (under ~200) where Notion’s collaboration model fits
    • Teams that haven’t deeply invested in Microsoft 365

    When Microsoft Copilot wins

    • You’re already deep in Microsoft 365
    • Excel-heavy analysis is core to your workflow
    • Outlook + Teams is your primary collaboration surface
    • Enterprise IT requirements favor Microsoft (compliance, identity, security)
    • Larger orgs where Microsoft’s enterprise plumbing matters

    What Copilot does that Notion AI doesn’t

    • Native deep integration into Excel, Word, PowerPoint, Outlook, Teams
    • Enterprise identity and compliance posture (Azure AD, Purview)
    • Strong Excel-native data analysis with formula generation
    • Teams meeting transcription and recap as a primary surface

    What Notion AI does that Copilot doesn’t

    • Custom Agents running on schedules
    • Workers for code execution
    • The Notion-style structured knowledge graph
    • MCP and n8n integrations
    • More flexible workspace shape

    The IT-procurement layer

    Larger organizations often have IT and procurement preferences that drive this decision more than feature comparison. Microsoft enterprise contracts, identity integration, and compliance posture are real factors. Notion’s enterprise story is improving but Microsoft has decades of head start in that lane.

    Where comparisons go wrong

    1. Comparing feature lists in isolation. Real value is integration depth into the platform you actually use.
    2. Underestimating Microsoft’s enterprise plumbing. For large orgs, identity and compliance are not afterthoughts.
    3. Underestimating Notion’s flexibility. For smaller teams, Notion’s malleability beats Microsoft’s rigidity.

    What to read next

    Notion AI vs Gemini, Notion AI vs ChatGPT, Editorial Surface Area, AI-Native Company Patterns.

  • Notion AI vs Gemini for Workspaces: The Document AI Showdown

    Notion AI vs Gemini for Workspaces: The Document AI Showdown

    Related on Tygart Media: vs ChatGPT · Google Everything App.

    The 60-second version

    Most “Notion AI vs Gemini” comparisons miss the actual decision: which platform does your work live in? If you’re a Notion-first team, Notion AI is the integrated answer. If you’re a Google Workspace team, Gemini integrates more deeply into Docs, Sheets, Slides, and Gmail than any third-party AI will. Trying to use both heavily creates context-splitting problems. Pick the platform first. The AI follows.

    When Notion AI wins

    Six evaluation cards for choosing an AI assistant platform
    When Notion AI wins.
    • Your work lives in Notion (databases, pages, agents)
    • You use Custom Agents on schedules
    • Cross-source synthesis across Notion + connected sources matters
    • Database manipulation and Autofill is core to your workflow
    • Multi-app integration via MCP and Workers

    When Gemini for Workspace wins

    Four cards comparing ChatGPT, Gemini, Perplexity, and Copilot by job
    When Gemini for Workspace wins.
    • Your work lives in Google Docs, Sheets, Slides
    • Real-time multi-user document collaboration is dominant
    • Email and calendar are the primary surfaces (Gemini’s Gmail integration is strong)
    • Sheets-heavy analysis benefits from Gemini’s native data understanding
    • You’re already paying for Google Workspace

    The stacking question

    Four cards for content, ops, build, and knowledge work with Claude
    The stacking question.

    Some teams run both. Three patterns that work:
    1. Notion as second brain, Google as collaboration layer. Notion holds structured knowledge; Google holds in-flight collaborative docs.
    2. Notion as agent layer, Google as document factory. Notion runs the agents and synthesis; Google produces the actual docs that get sent.
    3. Drive integration as the bridge. Notion AI reads Google Drive content via integration so the agent can synthesize across both surfaces.

    What Gemini does that Notion AI doesn’t

    • Real-time multi-user editing with AI assistance
    • Sheets-native analysis and chart generation
    • Deep Gmail integration
    • Slides-native design and image generation

    What Notion AI does that Gemini doesn’t

    • Scheduled autonomous agents (Custom Agents)
    • Database property Autofill at the workspace level
    • Workers for code execution
    • The Notion-style structured knowledge graph
    • MCP-based tool integration

    Where comparisons go wrong

    1. Treating raw model quality as the deciding factor. Both use strong models. Integration depth matters more.
    2. Underestimating switching costs. Moving an org for AI reasons is rarely worth it.
    3. Trying to use both heavily. Context splits. Synthesis suffers.

    What to read next

    Notion AI vs ChatGPT, Notion AI vs Microsoft Copilot, Editorial Surface Area, Google Drive Integration.

  • Notion AI vs ChatGPT for Daily Knowledge Work

    Notion AI vs ChatGPT for Daily Knowledge Work

    Related on Tygart Media: Notion AI review · Claude vs Notion AI.

    The 60-second version

    This isn’t a winner-take-all comparison. Notion AI and ChatGPT are different categories of tool that get incorrectly compared because they both use the word “AI.” Notion AI knows your workspace. ChatGPT knows the open web. The right operator stack uses both. The question isn’t which to pick; it’s how to route work between them.

    When Notion AI wins

    Six evaluation cards for choosing an AI assistant platform
    When Notion AI wins.
    • Anything that requires knowing your specific content
    • Synthesis across your databases, pages, and connected sources
    • Document work where the doc lives in your workspace
    • Recurring tasks that benefit from agent automation
    • Mobile use where seamless integration matters

    When ChatGPT wins

    Four cards comparing ChatGPT, Gemini, Perplexity, and Copilot by job
    When ChatGPT wins.
    • Open-web research
    • Brainstorming on topics outside your workspace
    • Code generation (currently ChatGPT and Claude lead here)
    • General-purpose Q&A
    • Conversational exploration of ideas

    How they stack

    Four cards for content, ops, build, and knowledge work with Claude
    How they stack for daily knowledge work.

    The pattern that works for most operators: ChatGPT for “thinking out loud” and external research; Notion AI for everything that touches your actual work. Use ChatGPT to draft an idea, then move the polished version into Notion where it joins your actual workspace and Notion AI takes over.

    What ChatGPT does that Notion doesn’t (yet)

    • Image generation
    • Voice conversations as a primary mode
    • Custom GPT marketplace
    • Data analysis on uploaded files at scale

    What Notion AI does that ChatGPT doesn’t

    • Persistent context across your workspace
    • Database manipulation and Autofill
    • Custom Agents running on schedules
    • Workers for code execution
    • Native integration with Slack, Mail, Calendar at the workspace level

    The pricing reality

    ChatGPT Plus is $20/month per user. Notion Business is $20/user/month annually with separate Custom Agent credits ($10/1000) starting May 4. For a team using both heavily, the combined cost is meaningful.

    Where comparisons go wrong

    1. Asking “which is smarter.” They use overlapping models. Raw model intelligence is similar; what differs is integration depth.
    2. Trying to pick one. The right answer is usually both, with clear use-case routing.
    3. Treating ChatGPT memory as equivalent to Notion’s workspace context. ChatGPT memory is conversational. Notion’s context is structured workspace data. Different categories.

    What to read next

    Notion AI vs Claude Projects, Notion AI vs Gemini, Editorial Surface Area, Auto Model Selection.

  • Mail Integration: Drafting and Triaging Email From Inside Notion AI

    Mail Integration: Drafting and Triaging Email From Inside Notion AI

    Related on Tygart Media: Calendar + Notion AI · Slack + Notion agent · email as API.

    The 60-second version

    Inbox triage is the highest-frequency, lowest-strategic-value work most knowledge workers do daily. Notion AI’s mail integration takes the operational layer off your plate. Agent reads inbox, categorizes incoming messages, drafts replies for routine items, and surfaces what actually needs your judgment. You review the drafts and send the ones that work. The inbox-zero ritual goes from 90 minutes to 15.

    Three mail integration patterns

    Four cards for content, ops, build, and knowledge work with Claude
    Three mail integration patterns.

    1. The triage and draft agent. Runs morning and afternoon. Categorizes inbox: requires response, FYI, junk, action item. For “requires response” items where context exists in Notion, drafts the reply. You review drafts and approve sends.
    2. The follow-up watcher. Watches sent messages. Flags conversations where you sent something and haven’t heard back in 5+ days. Drafts a follow-up. You review and decide whether to send.
    3. The inbox-to-database agent. When inbox content matches database criteria (new lead → CRM, support request → tickets, content pitch → editorial queue), agent extracts structured data and creates the database entry. Reduces manual entry.

    What stays human

    • Sending. Always.
    • Sensitive replies (HR, legal, conflict, confidential)
    • Initial emails to new contacts
    • Anything where voice matters more than content

    The send button stays human

    Floor versus ceiling cards for commoditized work and human-network premium
    The send button stays human.

    This is the rule. Agent integrations with mail should be read-and-draft, never autonomous send. The relationship cost of one wrong sent email exceeds the time savings of automating sends across hundreds of right ones. Don’t.

    Where this goes wrong

    1. Trusting drafts on relationship emails. Drafts to existing contacts you have history with risk missing nuance. Read these especially carefully before sending.
    2. Auto-categorizing too aggressively. “FYI” categorization can hide actual urgency. Sample-check the FYI bucket weekly.
    3. Letting follow-ups become spam. A follow-up after 5 days is reasonable. Three follow-ups in 10 days is harassment. Configure follow-up agents conservatively.

    Privacy posture

    Five security domains: identity, data, code governance, audit, agents
    Privacy posture for mail agents.

    Mail integration gives the agent significant access. Two practices:
    – Connect a personal mail account, not a shared inbox
    – Audit what the agent has read monthly via the Notion access logs

    What to read next

    Slack Integration, Calendar + Notion AI, AI-Native Company Patterns.