Tygart Media

Tag: AI for Business

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

    Last refreshed: May 15, 2026

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

    How to Use This Page

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

    Claude Skills for Restaurants

    Skill 1: Google Review Reply Engine

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

    Paste into Claude Project Instructions:

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

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

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

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

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

    Skill 2: Menu Description Writer

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

    Paste into Claude Project Instructions:

    You are a menu copywriter for a restaurant.

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

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

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

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

    Skill 3: Staff Communication Writer

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

    Paste into Claude Project Instructions:

    You are an internal communications assistant for a restaurant.

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

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

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

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

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

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

    Skill 4: Social Media Caption Writer

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

    Paste into Claude Project Instructions:

    You are a social media assistant for a local restaurant.

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

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

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

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

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

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

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

    Books for Bots

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

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

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

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

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

    Ready-to-Use Prompts

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

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

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

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

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

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

    Last refreshed: May 15, 2026

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

    How to Use This Page

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

    Claude Skills for Lawyers

    Skill 1: Client Status Update Writer

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

    Paste into Claude Project Instructions:

    You are a client communication assistant for a law firm.

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

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

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

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

    Skill 2: Legal Concept Explainer

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

    Paste into Claude Project Instructions:

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

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

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

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

    Skill 3: Intake and Onboarding Email Writer

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

    Paste into Claude Project Instructions:

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

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

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

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

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

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

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

    Skill 4: Non-Billable Email Handler

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

    Paste into Claude Project Instructions:

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

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

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

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

    Books for Bots

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

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

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

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

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

    Ready-to-Use Prompts

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

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

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

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

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

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

    Last refreshed: May 15, 2026

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

    How to Use This Page

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

    Claude Skills for Accountants

    Skill 1: Client Email Writer

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

    Paste into Claude Project Instructions:

    You are a professional email assistant for a CPA firm.

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

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

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

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

    Skill 2: Tax Concept Explainer

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

    Paste into Claude Project Instructions:

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

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

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

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

    Skill 3: Engagement Letter Drafter

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

    Paste into Claude Project Instructions:

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

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

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

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

    Skill 4: IRS Notice Triage

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

    Paste into Claude Project Instructions:

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

When I describe an IRS notice, produce:

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

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

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

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

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

    Books for Bots

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

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

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

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

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

    Ready-to-Use Prompts

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

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

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

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

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

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

  • Jared Kaplan: The Physicist Who Discovered AI Scaling Laws

    Jared Kaplan: The Physicist Who Discovered AI Scaling Laws

    Last refreshed: May 15, 2026

    Claude AI · Fitted Claude

    Jared Kaplan is the Chief Science Officer of Anthropic and one of the most consequential AI researchers alive. His 2020 paper on neural scaling laws — co-authored with Sam McCandlish and others — changed how every major AI lab thinks about model development. He is a TIME100 AI honoree, has testified before the U.S. Senate, and Forbes estimates his net worth at $3.7 billion. Yet outside of AI research circles, his name remains largely unknown to the general public.

    Academic Background

    Kaplan holds a PhD in physics, having trained as a theoretical physicist before pivoting to AI. Like several Anthropic co-founders, his physics background proved directly applicable to machine learning — particularly in developing the mathematical frameworks for understanding how AI systems scale. Physics training emphasizes finding simple underlying laws that explain complex phenomena, which is exactly what scaling law research does.

    The Discovery That Changed AI: Scaling Laws

    In January 2020, Kaplan and colleagues at OpenAI published “Scaling Laws for Neural Language Models” — a paper that demonstrated something remarkable: AI model performance improves in a smooth, predictable way as you increase model size, training data, and compute budget. The relationship follows a power law, meaning you can forecast how capable a model will be before training it, simply by knowing how much compute you’re using.

    This was not merely an academic finding. It gave AI labs a roadmap: if you want a more capable model, you know roughly how much more investment is required. It directly enabled the aggressive scaling strategies that produced GPT-4, Claude 3, and every frontier model since. The paper has been cited tens of thousands of times and is considered foundational to the modern AI race.

    Co-Founding Anthropic

    Kaplan was among the seven OpenAI researchers who left in 2021 to found Anthropic. His technical authority — particularly in understanding what training configurations produce which capabilities — made him a natural fit as Chief Science Officer, the role he holds today.

    Recognition and Public Profile

    Kaplan was named to TIME’s 100 Most Influential People in AI, one of a handful of researchers recognized for foundational contributions rather than executive roles. He has testified before the U.S. Senate on AI safety and capabilities — bringing the technical perspective of a researcher who understands, at a mathematical level, how AI systems grow in power.

    Net Worth

    Forbes estimated Kaplan’s net worth at approximately $3.7 billion as of early 2026, reflecting his co-founder equity in Anthropic at the company’s current valuation. If Anthropic proceeds with its targeted IPO in late 2026, this figure could change substantially.

    Frequently Asked Questions

    What is Jared Kaplan known for?

    Jared Kaplan is best known for co-discovering AI scaling laws — the mathematical relationships that predict how AI model performance improves with more compute, data, and parameters. His 2020 paper “Scaling Laws for Neural Language Models” is foundational to modern AI development.

    What is Jared Kaplan’s role at Anthropic?

    Kaplan is the Chief Science Officer of Anthropic, responsible for the company’s scientific research direction and the technical foundations of Claude’s development.

    What is Jared Kaplan’s net worth?

    Forbes estimated Jared Kaplan’s net worth at approximately $3.7 billion as of early 2026, based on his co-founder equity stake in Anthropic.


    Need this set up for your team?
    Talk to Will →

  • Why AI Agents Are Different From Chatbots, Automations, and APIs

    Why AI Agents Are Different From Chatbots, Automations, and APIs

    These terms get used interchangeably. They’re not the same thing. Here’s the actual distinction between each one, where the lines get genuinely blurry, and which category fits what you’re actually trying to build.

    Chatbots

    A chatbot is a software interface designed to simulate conversation. The defining characteristic: it’s stateless and reactive. You send a message; it responds; the exchange is complete. Each interaction is largely independent.

    Traditional chatbots (pre-LLM) operated on decision trees — “if the user says X, respond with Y.” Modern LLM-powered chatbots use language models to generate responses, which makes them dramatically more capable and flexible — but the fundamental architecture is the same: you ask, it answers, you ask again.

    What chatbots are good at: answering questions, providing information, routing conversations, handling defined service scenarios with natural language flexibility. What they’re not: action-takers. A chatbot can tell you how to cancel your subscription. An agent can cancel it.

    Automations

    Automations are rule-based workflows that execute when triggered. Zapier, Make, and similar tools are the canonical examples. When event A happens, do B, then C, then D.

    The key characteristic: the path is predefined. Every step is specified by the person who built the automation. If an unexpected situation arises that the automation wasn’t built for, it either fails or skips the step. There’s no reasoning about what to do — there’s only executing the specified path or not.

    Automations are highly reliable for well-defined, stable processes. They break when edge cases arise that weren’t anticipated. They scale perfectly for the exact task they were built for; they don’t generalize.

    APIs

    An API (Application Programming Interface) is a communication contract — a defined way for software systems to talk to each other. APIs are infrastructure, not agents or automations. They’re the mechanism through which agents and automations take action in external systems.

    When an AI agent “uses Slack,” it’s calling Slack’s API. When an automation “posts to Twitter,” it’s calling Twitter’s API. The API is the door; agents and automations are the things that open it.

    Conflating APIs with agents is a category error. An API is a tool, not a behavior pattern.

    AI Agents

    An AI agent takes a goal and figures out how to accomplish it, using tools available to it, handling unexpected situations along the way, without a human specifying each step.

    The distinguishing characteristics versus the above:

    • vs. Chatbots: Agents take action in the world; chatbots respond to messages. An agent can book the flight, not just tell you how to book it.
    • vs. Automations: Agents reason about what to do next; automations execute predefined paths. When an unexpected situation arises, an agent adapts; an automation fails or skips.
    • vs. APIs: APIs are tools an agent uses; they’re not the agent itself. The agent is the reasoning layer that decides which API to call and what to do with the result.

    Where the Lines Actually Blur

    In practice, real systems often combine these categories:

    LLM-powered chatbots with tool access: A customer service chatbot that can look up your order status, initiate a return, and send a confirmation email is starting to look like an agent — it’s taking actions, not just responding. The boundary between “advanced chatbot” and “limited agent” is genuinely fuzzy.

    Automations with AI decision steps: A Zapier workflow with an OpenAI or Claude step in the middle isn’t purely rule-based anymore — the AI step can produce variable outputs that affect what the automation does next. This is a hybrid: mostly automation, partly agentic.

    Agents with constrained scopes: An agent restricted to a single tool and a narrow task class starts to look like a sophisticated automation. The more constrained the scope, the more the distinction collapses in practice.

    The useful question isn’t “what category is this?” but “is this system reasoning about what to do, or executing a predefined path?” That’s the actual distinction that matters for how you build, monitor, and trust it.

    Why the Distinction Matters Operationally

    Reliability profile: Automations fail predictably — when an edge case hits a path that wasn’t built. Agents fail unpredictably — when their reasoning goes wrong in a way you didn’t anticipate. Different failure modes require different monitoring approaches.

    Maintenance overhead: Automations require explicit updates when processes change. Agents adapt to process changes automatically — but may adapt in unexpected ways that need to be caught and corrected.

    Auditability: Automations are fully auditable — you can read the workflow and know exactly what it does. Agents are less auditable — you can inspect their actions, but not fully predict them in advance. For compliance-sensitive contexts, this matters significantly.

    Build cost: Automations are faster to build for well-defined, stable processes. Agents are faster to deploy when the process is complex, variable, or not fully specified — because you’re specifying a goal rather than a procedure.

    For what agents can actually do in production: What AI Agents Actually Do. For a business owner’s introduction: AI Agents Explained for Business Owners. For hosted agent infrastructure: Claude Managed Agents FAQ.


    Hosted agent infrastructure pricing: Claude Managed Agents Pricing Reference.

  • What AI Agents Actually Do (Not the Hype Version)

    What AI Agents Actually Do (Not the Hype Version)

    Not the version where AI agents are going to replace all human jobs by 2030. The actual version, right now, based on what’s deployed in production.

    The Actual Definition

    What an AI agent is

    Software that takes a goal, breaks it into steps, uses tools to execute those steps, handles errors along the way, and keeps working without you directing every action. The distinguishing characteristic is autonomous multi-step execution — not just answering a question, but completing a task.

    The Key Distinction: One-Shot vs. Agentic

    Most people’s experience with AI is one-shot: you type something, the AI responds, the exchange is complete. That’s a language model doing inference. An AI agent is different in one specific way: it takes actions, checks results, and takes more actions based on what it found — often dozens of steps — without you approving each one.

    Example of one-shot AI: “Summarize this document.” You paste the document, the AI returns a summary. Done.

    Example of an AI agent doing the same task: “Research this topic and produce a summary with verified sources.” The agent searches the web, reads multiple pages, identifies conflicts between sources, runs additional searches to resolve them, synthesizes findings, and returns a summary with citations — without you specifying each search query or each page to read. You gave it a goal; it handled the steps.

    What Agents Can Actually Do

    The tools an agent can use define its capability surface. Common tool categories in production agents:

    • Web search: Query search engines and retrieve current information
    • Code execution: Write and run code in a sandboxed environment, use results to inform next steps
    • File operations: Read, write, and modify files — documents, spreadsheets, data files
    • API calls: Interact with external services — CRMs, databases, project management tools, communication platforms
    • Browser control: Navigate web pages, fill forms, extract information
    • Memory: Store and retrieve information across steps within a session, sometimes across sessions

    The combination of these tools is what makes agents capable of genuinely autonomous work. An agent that can search, write code, execute it, check the results, and write findings to a document can complete a research and analysis task that would otherwise require hours of human work — without you steering each step.

    What “Autonomous” Actually Means in Practice

    Autonomous doesn’t mean unsupervised indefinitely. Production agents are typically configured with:

    • Defined scope: The tools the agent can use, the systems it can access, the actions it’s allowed to take
    • Guardrails: Actions that require human confirmation before proceeding — making a payment, sending an email externally, modifying a production database
    • Reporting: Checkpoints where the agent surfaces what it’s done and asks whether to continue

    Autonomy is a dial, not a switch. You set how much the agent handles independently versus checks in. Most production deployments start more supervised and reduce oversight as trust in the agent’s behavior is established.

    Real Production Examples (Not Hypotheticals)

    Concrete examples from confirmed public deployments as of April 2026:

    • Rakuten: Deployed five enterprise Claude agents in one week on Anthropic’s Managed Agents platform — handling tasks across their e-commerce operations including data processing, content tasks, and operational workflows
    • Notion: Background agents that autonomously update workspace pages, synthesize database content, and process meeting notes into structured summaries without manual triggers
    • Sentry: Agents integrated into developer workflows — monitoring error streams, triaging issues, and surfacing relevant context to engineers
    • Asana: Project management agents that update task statuses, synthesize project health, and move work items based on defined triggers

    These are not pilots. These are production systems handling real operational load.

    How They’re Built

    An agent is built from three components:

    1. A language model: The reasoning layer — the part that decides what to do next, interprets tool results, and determines when the task is complete
    2. Tools: The action layer — APIs, code execution environments, file systems, or anything else the model can call to take action in the world
    3. Orchestration: The loop that connects them — manages the sequence of model calls and tool executions, maintains state between steps, handles errors

    Historically, builders had to construct the orchestration layer themselves — a significant engineering investment. Hosted platforms like Claude Managed Agents handle the orchestration layer, letting builders focus on defining the agent’s goals, tools, and guardrails rather than the mechanics of running the loop.

    What Agents Are Not Good At (Yet)

    Honest calibration on current limitations:

    • Long-horizon planning with many unknowns: Agents perform best on tasks with relatively defined scope. Open-ended exploratory work over many days with fundamentally uncertain requirements is still better handled by humans in the loop at each major decision point.
    • Tasks requiring physical world interaction: No production general-purpose physical agent exists. Software agents operating through APIs and interfaces are the current state.
    • Tasks where errors are catastrophic: Agents make mistakes. For any irreversible, high-stakes action — financial transactions, production data modifications, external communications to important relationships — human confirmation steps should remain in the loop.

    For how hosted agent infrastructure works: Claude Managed Agents FAQ. For the difference between agents and chatbots: AI Agents vs. Chatbots, Automations, and APIs. For an SMB-focused explanation: AI Agents Explained for Business Owners.


    For pricing specifics on hosted agent infrastructure: Claude Managed Agents Complete Pricing Reference.

  • How to Write Content That AI Systems Actually Cite

    How to Write Content That AI Systems Actually Cite

    Tygart Media / Content Strategy
    The Practitioner JournalField Notes
    By Will Tygart
    · Practitioner-grade
    · From the workbench

    Being cited by AI systems is not luck and it’s not purely a domain authority game. There are structural characteristics of content that make AI systems more or less likely to pull from it. Here’s what those characteristics are and how to build them in deliberately.

    Why Content Structure Determines Citation Likelihood

    AI systems — whether Perplexity, ChatGPT with web search, or Google AI Overviews — are trying to answer a question. When they search the web and retrieve candidate content, they’re looking for the passage or page that most directly and reliably answers the query. The content that wins is the content that makes the answer easiest to extract.

    This has direct structural implications. A 3,000-word narrative essay that eventually answers a question on page 2 loses to a 600-word page that answers the question in the first paragraph, provides supporting evidence, and includes a definition. Not because shorter is better, but because clarity of answer placement is better.

    The Structural Characteristics That Drive Citation

    1. Direct Answer in the First 100 Words

    Every piece of content you want AI systems to cite should answer the primary question it’s targeting before the first scroll. AI retrieval systems don’t read like humans — they identify the most relevant passage, and that passage needs to contain the answer, not just lead toward it.

    Test: take your target query and your first 100 words. Does the answer exist in those 100 words? If not, restructure until it does. The rest of the piece can develop nuance, context, and supporting evidence — but the answer must be front-loaded.

    2. Explicit Q&A Formatting

    Question-and-answer structure signals to AI systems that the content is explicitly organized around answering queries. H3 headers phrased as questions, followed by direct answers, are one of the most reliable patterns for citation capture.

    This is why FAQ sections work — not because of FAQPage schema specifically, but because the underlying structure gives AI systems a clean extraction target. Schema reinforces it; the structure is the foundation.

    3. Defined Terms and Named Concepts

    Content that defines terms clearly — “X is Y” statements — becomes citable for queries looking for definitions. AI systems frequently answer “what is X” queries by pulling the clearest definition they can find. If your content doesn’t include a crisp definitional sentence, it’s not competing for definition queries even if you’ve written a thorough treatment of the topic.

    Add definition boxes. State “AI citation rate is the percentage of sampled AI queries where your domain appears as a cited source.” Don’t bury the definition in the third paragraph of an explanation.

    4. Specific, Verifiable Facts

    AI systems weight specificity. “$0.08 per session-hour” gets cited. “A relatively modest fee” does not. “60 requests per minute for create endpoints” gets cited. “Limited rate limits apply” does not.

    Replace hedged language with concrete numbers and specific claims wherever your content supports it. Don’t fabricate specificity — wrong specific numbers are worse than honest hedging. But wherever you have real, verifiable data, make it explicit and prominent.

    5. Entity Clarity

    Content that makes clear who is speaking, what organization they represent, and what their basis for authority is gets cited more reliably. This is the E-E-A-T signal applied to AI citation: the system needs to assess whether this source is credible enough to cite.

    Name the author. State the organization. Link to primary sources. Include dates on time-sensitive claims (“as of April 2026”). These signals tell the AI system this content has an accountable source, not anonymous text.

    6. Freshness on Time-Sensitive Topics

    For any topic where recency matters — product pricing, regulatory status, current events — AI systems heavily weight recently indexed, recently updated content. A page published April 2026 beats a page published January 2025 for queries about current status, even if the older page has higher domain authority.

    Update time-sensitive content. Add “last updated” dates. Re-publish with fresh timestamps when the underlying facts change. Freshness signals are real citation drivers for volatile topic areas.

    7. Speakable and Structured Data Markup

    Speakable schema explicitly marks the passages in your content best suited for AI extraction. It’s a direct signal to AI retrieval systems: “this paragraph is the answer.” Combined with FAQPage schema, Article schema, and HowTo schema where relevant, structured markup makes your content more parseable.

    Schema doesn’t replace the underlying structure — it reinforces it. A well-structured page with schema beats a poorly structured page with schema. But a well-structured page with schema beats a well-structured page without it.

    8. Internal Link Architecture

    AI systems that crawl the web assess topical depth partly through link structure. A page that sits within a tight cluster of related pages — all cross-linking around a topic — signals topical authority more strongly than an isolated page, even if the isolated page’s content is comparable.

    Build the cluster. The hub-and-spoke architecture is as relevant for AI citation as it is for traditional SEO. Every spoke article should link to the hub; the hub should link to every spoke.

    What Doesn’t Work

    A few patterns that are intuitively appealing but don’t translate to citation lift:

    • More content for its own sake: 5,000 words of padded content is not more citable than 900 words of dense, accurate content. AI retrieval is looking for passage quality, not page length.
    • Keyword density: Traditional keyword repetition strategies don’t make content more citable. The query match is handled at retrieval; the citation decision is about answer quality, not keyword frequency.
    • Generic authority claims: “We’re the leading experts in X” is not citable. A specific data point that demonstrates expertise is.

    The Compound Effect

    These characteristics compound. A page with a direct front-loaded answer, Q&A structure, defined terms, specific facts, clear entity signals, fresh timestamps, and schema markup sitting within a well-linked cluster is materially more citable than a page with only two or three of these characteristics. The full stack produces disproportionate results.

    For the monitoring layer: How to Track When AI Systems Cite You. For the metrics: What Is AI Citation Rate?. For the full citation monitoring guide: AI Citation Monitoring Guide.


    For the infrastructure layer: Claude Managed Agents Pricing Reference | Complete FAQ Hub.

  • AI Citation Monitoring Tools — What Exists, What Doesn’t, What We Built

    AI Citation Monitoring Tools — What Exists, What Doesn’t, What We Built

    The Lab · Tygart Media
    Experiment Nº 570 · Methodology Notes
    METHODS · OBSERVATIONS · RESULTS

    You want to monitor whether AI systems are citing your content. What tools actually exist for this, what they do, what they don’t do, and what we’ve built ourselves when nothing on the market fit.

    The Market as of April 2026

    The AI citation monitoring category is real but nascent. Here’s an honest inventory:

    Established SEO Platforms Adding AI Visibility Metrics

    Several major SEO platforms have added “AI visibility” or “AI search” modules in the past 6–12 months. These generally track:

    • Whether your domain appears in AI Overviews for tracked keywords (via SERP scraping)
    • Brand mentions in AI-generated snippets
    • Comparative visibility versus competitors in AI search results

    Ahrefs, Semrush, and Moz have all moved in this direction to varying degrees. Verify current feature availability — this has been an active development area and capabilities have changed rapidly.

    Mention Monitoring Tools Expanding to AI

    Brand mention tools like Brand24 and Mention have begun tracking AI-generated content that includes brand references. The challenge: they’re tracking brand name occurrences in crawled content, not necessarily AI citation events. Useful for brand visibility in AI-generated content that gets published, less useful for tracking in-session citations.

    Purpose-Built AI Citation Tools (Emerging)

    Several purpose-built tools targeting AI citation tracking specifically have launched or raised funding in early 2026. This category is moving fast. As of our last check:

    • Tools focused on tracking specific brand or entity mentions across AI platforms
    • API-first tools targeting developers who want to build citation monitoring into their own workflows
    • Dashboard tools with pre-built query sets for common industry categories

    Treat any specific product recommendation here as a starting point for your own research — the category will look different in 6 months.

    Google Search Console

    The strongest existing tool, and it’s free. AI Overviews that cite your pages register as impressions and clicks in GSC under the relevant queries. This is first-party data from Google itself. Limitation: covers only Google AI Overviews, not Perplexity, ChatGPT, or other platforms.

    What We Built

    When no existing tool covered the specific workflows we needed, we built our own. The stack:

    Perplexity API Query Runner

    A Cloud Run service that runs a predefined query set against Perplexity’s API on a weekly schedule. It parses the citations field from each response, checks for domain appearances, and writes results to a BigQuery table. Total engineering time: roughly one day. Ongoing cost: minimal (Cloud Run idle cost + Perplexity API usage).

    The output: a weekly BigQuery record per query showing which domains Perplexity cited, with timestamps. Trend queries show citation rate over time by query cluster.

    GSC AI Overview Monitor

    Not a custom build — just systematic review of GSC data. We check weekly which queries are generating AI Overview impressions for our tracked sites. The signal: if a page is generating AI Overview impressions on new queries, that’s a citation event.

    Manual ChatGPT Sampling

    For highest-priority queries, manual weekly sampling of ChatGPT with web search enabled. We log results to a shared spreadsheet. Less scalable than the API approach, but ChatGPT’s web search activation is inconsistent enough that API automation adds complexity without proportional reliability gain.

    What Doesn’t Exist (That Would Be Useful)

    The tool gaps that we still feel:

    • Cross-platform citation dashboard: A single view showing citation rate across Perplexity, ChatGPT, Gemini, and AI Overviews for the same query set. Nobody has built this cleanly yet.
    • Historical citation rate database: Knowing your citation rate is useful. Knowing whether it improved after you published a new piece of content is more useful. The temporal correlation is hard to establish with spot-check sampling.
    • Competitor citation tracking at scale: Easy to check manually for specific queries; hard to monitor systematically across a large competitor set and query space.

    These gaps exist because the category is new, not because the problems are technically hard. Expect the tool landscape to fill in significantly over the next 12 months.

    How to calculate citation rate: What Is AI Citation Rate?. How to set up tracking: How to Track When ChatGPT or Perplexity Cites Your Content. How to optimize for citations: How to Write Content That AI Systems Cite.


    The Perplexity API monitoring stack we built runs on Claude. For the hosted infrastructure context: Claude Managed Agents Pricing Reference | Complete FAQ.

  • What Is AI Citation Rate? (And How to Calculate Yours)

    What Is AI Citation Rate? (And How to Calculate Yours)

    AI citation rate is a metric that doesn’t have a standard definition yet, which means everyone using the term might mean something slightly different. Here’s what it is, how to calculate it, and what it actually measures — and doesn’t.

    Definition

    AI Citation Rate

    The percentage of sampled AI queries where a specific domain or URL appears as a cited source in the AI system’s response.

    Formula: (Queries where your domain appeared as a source) ÷ (Total queries sampled) × 100

    A Concrete Example

    You run 50 queries in Perplexity across your core topic cluster. Your domain appears as a cited source in 12 of those responses. Your AI citation rate for that query set on that platform: 12/50 = 24%.

    That’s the basic calculation. The complexity is in what you define as your query set, which platforms you sample, and what counts as a “citation.”

    What Counts as a Citation

    Not all AI source mentions are equal. Some distinctions worth tracking separately:

    • Direct URL citation: The AI explicitly lists your URL as a source. Highest confidence — trackable programmatically via API.
    • Domain mention: Your domain name appears in the response text but not necessarily as a formal source citation.
    • Brand mention: Your brand name appears in the response. May or may not correlate with your web content being the source.
    • Implied citation: Content clearly derived from your page but no explicit attribution. Only detectable through content fingerprinting — difficult at scale.

    For tracking purposes, direct URL citation is the most reliable signal. Brand mentions are noisier but still worth tracking for brand visibility purposes.

    How to Calculate It

    Step 1: Define Your Query Set

    Select 20–100 queries where you want to appear. Good sources for your query set:

    • Your highest-impression GSC queries (you rank for these — do AI systems cite you?)
    • Queries where you’ve published dedicated content
    • Queries from your keyword research that match your expertise
    • Questions your clients or prospects actually ask

    Step 2: Sample Across Platforms

    Run each query in Perplexity (most trackable — consistent citation format), ChatGPT with web search enabled, and Google AI Overviews (via organic search). Track results separately by platform — citation rates vary significantly between platforms for the same query set.

    Step 3: Log Results

    For each query on each platform, record:

    • Whether your domain appeared as a citation (binary: yes/no)
    • Position if ranked (first citation, third citation, etc.)
    • Date of query

    Step 4: Calculate Rate

    Aggregate by time period (weekly or monthly). Calculate separately by platform and by topic cluster — aggregate rate across all platforms and queries hides the variation that’s actually useful.

    Step 5: Establish Baseline, Then Track Change

    Your first 4–6 weeks of data sets your baseline. After that, track directional change — is the rate improving, declining, or stable? Correlate changes with content updates, new publications, and competitor activity.

    What Citation Rate Actually Measures (And Doesn’t)

    AI citation rate is a proxy for content authority signal in AI systems — not a direct ranking factor you can optimize mechanically. It reflects:

    • Whether your content is being indexed and surfaced by AI systems for your target queries
    • Whether your content structure and freshness match what AI systems prefer to cite
    • Relative authority versus competitors for the same query space

    It doesn’t measure:

    • Whether AI systems are using your content without citation (training data influence)
    • User behavior after AI responses (do they click through to your site?)
    • Revenue impact of being cited (cited ≠ converting)

    Benchmarks and Context

    Because this metric is new, industry benchmarks don’t exist yet. What matters is your own trend line, not comparison to a published standard. A 20% citation rate in a highly competitive topic cluster might represent strong performance; 20% in a niche you should dominate might indicate underperformance. Context is everything.

    For the full monitoring setup: How to Track When ChatGPT or Perplexity Cites Your Content. For tools available: AI Citation Monitoring Tools Comparison. For content optimization: How to Write Content That AI Systems Actually Cite.


    For the agent infrastructure behind automated citation tracking: Claude Managed Agents Pricing and FAQ Hub.