Restoration Intelligence - Tygart Media

Tygart Media

Category: Restoration Intelligence

The definitive resource for restoration company operators — business operations, marketing, estimating, AI, and growth strategy.

  • How Commercial Property Managers Are Counting Your Emissions (Whether You Know It or Not)

    How Commercial Property Managers Are Counting Your Emissions (Whether You Know It or Not)

    The Agency Playbook
    TYGART MEDIA · PRACTITIONER SERIES
    Will Tygart
    · Senior Advisory
    · Operator-grade intelligence

    When a commercial property manager reports their Scope 3 emissions to GRESB, CDP, or their California SB 253 auditor, they need to account for the emissions from every significant supplier and contractor in their value chain. That includes their restoration contractors.

    The problem: most restoration contractors don’t track or report their emissions. So property managers are using a fallback method that produces high-uncertainty estimates — and that method systematically misrepresents what restoration work actually emits.

    The Spend-Based Estimation Method

    When primary data — actual measured emissions from a specific supplier — isn’t available, the GHG Protocol allows companies to use a spend-based estimation method. The formula is simple: multiply what you paid a supplier by an industry-average emissions intensity factor (measured in kilograms of CO2 equivalent per dollar spent in that industry), and that becomes your estimate of that supplier’s contribution to your Scope 3.

    For example: a property manager paid a restoration contractor $85,000 for a water damage remediation. Using the EPA’s industry-average emissions factor for “services to buildings and dwellings,” they estimate the Scope 3 emissions from that engagement as approximately 8.5 metric tons of CO2 equivalent.

    That number may be wildly inaccurate. It might be double the actual emissions. It might be half. The spend-based method doesn’t account for job type, geographic location, crew size, equipment used, materials consumed, or waste generated. It treats a $85,000 carpet cleaning the same as an $85,000 Category 3 sewage backup remediation with hazmat disposal — because both cost $85,000.

    Why Property Managers Are Stuck With This Method

    The GHG Protocol is explicit that primary data — actual emissions data provided by the supplier — is preferred over spend-based estimates. Primary data produces more accurate disclosures, reduces auditor scrutiny, and demonstrates genuine supply chain engagement to investors and regulators.

    But primary data requires the contractor to track and report their emissions per job. Almost no restoration contractors do this. So property managers default to spend-based estimates not because they prefer them, but because they have no alternative.

    This creates a specific problem for restoration contractors who want to compete for commercial work: the property manager’s ESG team sees your company as an uncontrolled data gap in their Scope 3 inventory. That’s not a comfortable position to occupy when they’re selecting preferred vendors for their next contract cycle.

    What Happens When You Provide Primary Data

    When a restoration contractor provides actual emissions data per job — even a simple calculation using documented emission factors for their equipment, vehicles, and materials — several things change for the property manager:

    Their Scope 3 disclosure becomes more accurate and more defensible to auditors. Their ESG report can distinguish between a high-emissions fire restoration project and a low-emissions water extraction job, rather than treating them identically based on invoice amount. They can demonstrate to investors and regulators that they have active supply chain engagement on emissions — one of the specific data quality improvements that frameworks like GRESB reward.

    From the contractor’s perspective, providing primary data changes the relationship. You’re no longer a vendor they’re estimating around — you’re a supply chain partner who is actively contributing to the accuracy of their ESG disclosure. That’s a different conversation in a contract renewal discussion.

    The Standard That Doesn’t Exist Yet

    The missing piece is a standardized methodology for calculating restoration-specific emissions per job — one that is rigorous enough for ESG auditors to accept, simple enough for restoration contractors to actually use, and consistent enough that a property manager with multiple restoration vendors can aggregate data from all of them in a compatible format.

    The Restoration Carbon Protocol is being built to be that standard. The goal is a per-job carbon report that any restoration contractor can complete using data they already capture in their job management systems — and that any commercial property manager can plug directly into their GRESB or CDP disclosure without additional processing.

    How do commercial property managers currently estimate restoration contractor emissions?

    Most use a spend-based estimation method — multiplying contractor invoices by industry-average emissions intensity factors from sources like the EPA or EXIOBASE. This produces high-uncertainty estimates that don’t account for job type, equipment, materials, or waste streams specific to restoration work.

    Is spend-based estimation accurate for restoration work?

    No. It treats all restoration spending as equivalent regardless of job type, scope, or actual emissions profile. A $50,000 water extraction and a $50,000 fire debris removal generate very different emissions, but spend-based estimation produces the same number for both.

    Why can’t property managers just ask their restoration contractors for emissions data?

    Most restoration contractors don’t track per-job emissions data and there is no industry standard for what that data should include or how it should be calculated. The Restoration Carbon Protocol is being developed to create that standard.

    What is primary data in Scope 3 reporting?

    Primary data is actual emissions data provided by a supplier, based on measured or calculated emissions from their specific activities. The GHG Protocol prefers primary data over spend-based estimates because it produces more accurate disclosures and is more defensible in audits.

  • What Is Scope 3 and Why Restoration Contractors Need to Care

    What Is Scope 3 and Why Restoration Contractors Need to Care

    The Agency Playbook
    TYGART MEDIA · PRACTITIONER SERIES
    Will Tygart
    · Senior Advisory
    · Operator-grade intelligence

    If you run a restoration company and nobody has mentioned Scope 3 emissions to you yet, that’s about to change. Commercial property managers, REITs, hospital systems, and institutional facility directors are all facing mandatory ESG reporting deadlines — and the emissions from the contractors they hire count toward their numbers.

    Your restoration work is in their Scope 3. Whether you know it or not, whether you track it or not, your clients are being asked to account for it.

    The Three Scopes of Greenhouse Gas Emissions

    The Greenhouse Gas Protocol — the internationally accepted standard for carbon accounting — divides emissions into three categories based on where they originate in relation to the reporting organization.

    Scope 1 covers direct emissions from sources the company owns or controls. A property management company’s Scope 1 would include fuel burned in company-owned boilers, generators, and vehicles.

    Scope 2 covers indirect emissions from purchased energy — electricity, steam, heat, and cooling consumed by the organization’s buildings and operations.

    Scope 3 covers everything else: all the indirect emissions that occur in the organization’s value chain, both upstream and downstream. For a commercial real estate company, Scope 3 includes the emissions from construction and renovation work, from tenant operations in leased space, from the materials used in building maintenance — and from the restoration contractors called in when water, fire, or mold damage occurs.

    Scope 3 is where the numbers get large. For commercial real estate, Scope 3 emissions typically account for 85 to 95 percent of total reported emissions. It’s also where the data is hardest to collect — because it requires getting information from dozens or hundreds of vendors, suppliers, and contractors who may not track their own emissions at all.

    Where Restoration Contractors Appear in Scope 3

    The GHG Protocol defines 15 categories of Scope 3 emissions. Restoration work touches several of them simultaneously:

    • Category 1 — Purchased goods and services: The materials your crews use on a job — drying equipment consumables, remediation chemicals, replacement materials — generate upstream emissions that get counted in your client’s Category 1.
    • Category 4 — Upstream transportation and distribution: The emissions from driving your trucks to the job site, hauling equipment, and transporting waste to disposal facilities.
    • Category 5 — Waste generated in operations: The debris, contaminated materials, and hazardous waste generated during restoration work that gets disposed of on behalf of the property owner.
    • Category 12 — End-of-life treatment of sold products: Applies when restoration involves removing and disposing of building materials — flooring, drywall, insulation — on behalf of the property.

    A single significant water loss job touches all four of these categories. A large fire restoration project may touch additional categories depending on the scope of reconstruction work involved.

    Why This Is a 2027 Problem for Your Business

    California Senate Bill 253 — the Climate Corporate Data Accountability Act — requires companies with more than $1 billion in annual revenue doing business in California to report Scope 1 and 2 emissions starting in 2026 and Scope 3 emissions starting in 2027. More than 5,000 companies are within scope of this law.

    The EU Corporate Sustainability Reporting Directive (CSRD) is already in effect, with Scope 3 reporting requirements phasing in through 2027 for large European companies — many of which own commercial real estate and operate facilities in the United States.

    What this means practically: the commercial property managers, REITs, hospital systems, and institutional facility directors who hire restoration contractors are right now trying to figure out how to collect Scope 3 emissions data from their vendor base. They need that data to file required disclosures. If you can provide it — in a structured, consistent, usable format — you become a preferred vendor. If you can’t provide it, you become a data gap they need to work around.

    The Gap the Restoration Industry Has Not Addressed

    No major restoration trade association — not IICRC, not RIA, not RCAT — has published a Scope 3 reporting standard for restoration contractors. There is no industry-agreed methodology for calculating the emissions contribution of a water damage job, a fire restoration project, or a mold remediation. There is no standard job carbon report format that a contractor can provide to a property manager for their ESG disclosure.

    This is the void the Restoration Carbon Protocol is designed to fill. In the absence of an industry standard, each commercial property manager is either making up their own methodology, using generic spend-based estimates with high uncertainty, or simply leaving restoration contractor emissions out of their disclosure and hoping their auditors accept it.

    None of those options serve the property manager. None of them serve the contractor. And none of them serve the goal of accurate climate disclosure.

    The restoration industry has an opportunity to lead here — to define the standard before regulators or clients define it for them, and to make that standard one that is actually workable for contractors who are focused on doing restoration work, not filing emissions reports.

    What are Scope 3 emissions?

    Scope 3 emissions are indirect greenhouse gas emissions that occur in an organization’s value chain — from the goods and services they purchase, the transportation of those goods, the waste generated in their operations, and the activities of their contractors and suppliers. For commercial real estate, Scope 3 typically accounts for 85–95% of total reported emissions.

    Do restoration contractors’ emissions count in their clients’ Scope 3?

    Yes. Restoration work generates emissions from vehicle transportation, equipment fuel use, materials consumption, and waste disposal — all of which fall under specific GHG Protocol Scope 3 categories that commercial property managers are required to report.

    When do commercial property managers need to report Scope 3 emissions?

    California SB 253 requires Scope 3 reporting starting in 2027 for companies with over $1 billion in revenue doing business in California. EU CSRD is already phasing in Scope 3 requirements. Many institutional investors and ESG frameworks (GRESB, CDP) already request Scope 3 data from their portfolio companies.

    Is there currently a Scope 3 reporting standard for restoration contractors?

    No. No major restoration trade association has published a Scope 3 calculation methodology or reporting standard for restoration work. The Restoration Carbon Protocol (RCP) is being developed to fill this gap.


  • Build Your Own KnowHow — And Then Go Further

    Build Your Own KnowHow — And Then Go Further

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart • Long-form Position • Practitioner-grade

    KnowHow is one of the most important things happening in the restoration industry right now. If you’re not familiar with it: it’s an AI-powered platform that takes your company’s operational knowledge — your SOPs, your onboarding materials, your hard-won process documentation — and turns it into an on-demand resource every team member can access from their phone. Your best technician’s knowledge stops walking out the door when they leave. Your new hire in Iowa follows the same protocol as your veteran in Texas. Your managers stop being human FAQ machines.

    It solves a real problem that has cost restoration companies enormous amounts of money in inconsistent work, slow onboarding, and institutional knowledge that evaporates with turnover.

    But KnowHow solves the internal problem. The knowledge stays inside your organization. And there is a second problem — the external one — that nobody has solved yet.

    The Internal Problem vs. The External Problem

    The internal problem is: your people don’t have access to what your company knows when they need it. KnowHow fixes that. The knowledge becomes accessible, searchable, consistent, and deliverable at scale across every location and every shift.

    The external problem is different: your clients, prospects, and contracting authorities have no way to verify that your company knows what it claims to know. They can read your capabilities statement. They can check your certifications. They can call references. But they can’t look inside your organization and confirm that your documented protocols are current, specific, and actually practiced — not just written down for the sake of winning a bid.

    In commercial restoration, that verification gap is expensive. Facility managers, FEMA contracting officers, insurance carriers, and national property management companies are making vendor decisions based on trust signals that are largely unverifiable. The company with the best pitch often wins over the company with the best protocols.

    An external knowledge API changes that dynamic completely.

    What an External Knowledge API Actually Is

    An external knowledge API is a structured, authenticated, publicly accessible feed of your operational knowledge — not your trade secrets, not your pricing, not your internal communications, but your documented protocols, your methodology, your standards, and your verified expertise. Published. Structured. Machine-readable. Available to anyone who needs to evaluate whether your company is the right partner for a complex job.

    Think of it as the difference between telling a client “we follow IICRC S500 water damage protocols” and showing them a live, structured endpoint where they can pull your actual documented water mitigation process — with timestamps that confirm it was updated last month, not in 2019.

    The internal KnowHow platform is the source. The external API is the window — carefully curated, access-controlled, and designed to answer the questions that matter to the people evaluating you.

    Who Cares About Your External Knowledge

    The list is longer than most restoration contractors realize.

    Commercial property managers and facility directors. A national hotel chain or healthcare system evaluating restoration vendors for their approved vendor program needs more than a certificate of insurance and a reference list. They want to know that your protocols are consistent across every job, that your team follows the same process whether the project manager is on-site or not, and that your documentation standards will hold up in a claim. An external knowledge feed — showing your water damage, fire damage, and mold remediation protocols in structured, current form — answers those questions before the conversation even starts.

    FEMA and government contracting. Federal disaster response contracts are awarded to companies that can demonstrate organizational capability at scale. The RFP process rewards documentation. A company that can point to an externally published, structured knowledge base as evidence of their operational maturity is presenting something most competitors don’t have. It’s not just a differentiator — it’s proof of the kind of institutional infrastructure that large government contracts require.

    Insurance carriers and TPAs. Third-party administrators and carrier programs are increasingly using AI tools to evaluate and route claims to preferred vendors. A restoration company whose documented protocols are structured and machine-readable — available for an AI system to pull and verify against claim requirements — is positioned for the way preferred vendor selection is heading, not the way it used to work.

    Commercial real estate and institutional property owners. REITs, hospital systems, university facilities departments, and large corporate real estate portfolios are all moving toward vendor relationships that have verifiable documentation standards. An external knowledge API gives them something they can actually audit — not just a sales presentation.

    How to Build It: The Two-Layer Stack

    The stack that makes this work has two layers, and KnowHow already gives you the first one.

    Layer one — internal capture and organization (KnowHow’s job). Use KnowHow, or an equivalent internal knowledge platform, to capture and organize your operational knowledge. Document your protocols rigorously. Keep them current. Assign ownership so they don’t go stale. The discipline required here is real, but it’s also the discipline that makes your company better operationally regardless of what you do with the knowledge externally. This layer is the foundation.

    Layer two — external publication and API distribution (the next layer). Select the knowledge that is appropriate to share externally — your methodology, your standards, your certifications, your documented approach to specific job types — and publish it in a structured, consistently maintained form. This can be as simple as a well-organized section of your company website with current protocol documentation, or as sophisticated as a full REST API endpoint that clients and AI systems can query directly. The key requirements are structure (consistent format, clear categorization), currency (updated when protocols change, timestamped), and accessibility (easy for a prospect or evaluator to find and verify).

    The gap between layer one and layer two is smaller than it sounds. If you’ve already done the internal documentation work in KnowHow, the editorial work of curating an external-facing version of that knowledge is incremental. You’re not building from scratch — you’re deciding what to show and building the window to show it through.

    The Credential That No Certificate Can Replace

    Certifications are static. An IICRC certification tells a client you passed a test. It doesn’t tell them what your company actually does when a technician encounters a Category 3 water loss in a 1960s commercial building with asbestos-containing materials in the subfloor.

    External knowledge does. It shows the specific, documented, currently-maintained thinking your company applies to that situation. It’s living proof of operational maturity, not a snapshot from the last time someone studied for an exam.

    In the commercial restoration market, where the jobs are large, the documentation requirements are significant, and the clients are sophisticated, that distinction is worth money. The companies that build this layer now — while most competitors are still treating knowledge as purely internal — will have a credential that can’t be quickly replicated.

    The Practical Starting Point

    You don’t need a full API to start. The minimum viable version of an external knowledge layer is a structured, well-maintained “Our Methodology” section on your website — not a generic “our process” marketing page, but actual documented protocols organized by job type, with clear version dates and enough specificity that an evaluator can see you’ve actually done the work.

    From there, the path to a structured API is incremental: add consistent categorization, ensure each protocol document has a permanent URL, and eventually expose that structure through a queryable endpoint. Each step makes the credential more verifiable and more valuable.

    KnowHow got the industry to take internal knowledge seriously. The companies that figure out how to take the next step — making that knowledge externally verifiable and machine-readable — will have something the market has never seen before in restoration.

    What is the difference between internal and external knowledge in restoration?

    Internal knowledge (what KnowHow manages) is operational documentation accessible to your own team — SOPs, onboarding materials, process guides. External knowledge is a curated version of that same expertise published in a structured, verifiable form for clients, contracting authorities, and AI systems to access and evaluate.

    Why would a restoration company publish its knowledge externally?

    Because commercial clients, FEMA, insurance carriers, and institutional property managers need to verify operational maturity before awarding contracts. A structured, current, machine-readable knowledge base is a stronger credential than certifications or capabilities statements — it shows documented, maintained expertise rather than a static snapshot.

    What is an external knowledge API for a restoration company?

    A structured, authenticated feed of your documented protocols, methodology, and standards — published in a format that clients, evaluators, and AI systems can query directly. It turns your operational knowledge into a verifiable, market-facing credential rather than keeping it purely internal.

    Who specifically benefits from a restoration company’s external knowledge API?

    Commercial facility managers building approved vendor programs, FEMA and government contracting officers evaluating organizational capability, insurance carriers and TPAs using AI tools to route claims to preferred vendors, and institutional property owners who need auditable vendor documentation standards.

    Does a restoration company need KnowHow to build an external knowledge API?

    No — any internal knowledge platform or even rigorous in-house documentation works as the foundation. KnowHow accelerates the internal capture work, which makes the external publication step more realistic. But the two-layer stack works with any internal knowledge infrastructure that produces well-documented, current, organized protocols.

  • Claude Managed Agents Pricing: $0.25/Session-Hour — Full 2026 Cost Breakdown

    Claude Managed Agents Pricing: $0.25/Session-Hour — Full 2026 Cost Breakdown

    Updated May 2026

    Pricing updated to reflect current Opus 4.7 launch ($5/$25 per MTok) and the retirement of Claude Sonnet 4 and Opus 4 on April 20, 2026. Managed Agents moved to public beta — see the complete pricing guide for current rate details.

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    $0.08 Per Session Hour: Is Claude Managed Agents Actually Cheap?

    Claude Managed Agents Pricing: $0.08 per session-hour of active runtime (measured in milliseconds, billed only while the agent is actively running) plus standard Anthropic API token costs. Idle time — while waiting for input or tool confirmations — does not count toward runtime billing.

    When Anthropic launched Claude Managed Agents on April 9, 2026, the pricing structure was clean and simple: standard token costs plus $0.08 per session-hour. That’s the entire formula.

    Whether $0.08/session-hour is cheap, expensive, or irrelevant depends entirely on what you’re comparing it to and how you model your workloads. Let’s work through the actual math.

    What You’re Paying For

    The session-hour charge covers the managed infrastructure — the sandboxed execution environment, state management, checkpointing, tool orchestration, and error recovery that Anthropic provides. You’re not paying for a virtual machine that sits running whether or not your agent is active. Runtime is measured to the millisecond and accrues only while the session’s status is running.

    This is a meaningful distinction. An agent that’s waiting for a user to respond, waiting for a tool confirmation, or sitting idle between tasks does not accumulate runtime charges during those gaps. You pay for active execution time, not wall-clock time.

    The token costs — what you pay for the model’s input and output — are separate and follow Anthropic’s standard API pricing. For most Claude models, input tokens run roughly $3 per million and output tokens roughly $15 per million, though current pricing is available at platform.claude.com/docs/en/about-claude/pricing.

    Modeling Real Workloads

    The clearest way to evaluate the $0.08/session-hour cost is to model specific workloads.

    A research and summary agent that runs once per day, takes 30 minutes of active execution, and processes moderate token volumes: runtime cost is roughly $0.04/day ($1.20/month). Token costs depend on document size and frequency — likely $5-20/month for typical knowledge work. Total cost is in the range of $6-21/month.

    A batch content pipeline running several times weekly, with 2-hour active sessions processing multiple documents: runtime is $0.16/session, roughly $2-3/month. Token costs for content generation are more substantial — a 15-article batch with research could run $15-40 in tokens. Total: $17-43/month per pipeline run frequency.

    A continuous monitoring agent checking systems and data sources throughout the business day: if the agent is actively running 4 hours/day, that’s $0.32/day, $9.60/month in runtime alone. Token costs for monitoring-style queries are typically low. Total: $15-25/month.

    An agent running 24/7 — continuously active — costs $0.08 × 24 = $1.92/day, or roughly $58/month in runtime. That number sounds significant until you compare it to what 24/7 human monitoring or processing would cost.

    The Comparison That Actually Matters

    The runtime cost is almost never the relevant comparison. The relevant comparison is: what does the agent replace, and what does that replacement cost?

    If an agent handles work that would otherwise require two hours of an employee’s time per day — research compilation, report drafting, data processing, monitoring and alerting — the calculation isn’t “$58/month runtime versus zero.” It’s “$58/month runtime plus token costs versus the fully-loaded cost of two hours of labor daily.”

    At a fully-loaded cost of $30/hour for an entry-level knowledge worker, two hours/day is $1,500/month. An agent handling the same work at $50-100/month in total AI costs is a 15-30x cost difference before accounting for the agent’s availability advantages (24/7, no PTO, instant scale).

    The math inverts entirely for edge cases where agents are less efficient than humans — tasks requiring judgment, relationship context, or creative direction. Those aren’t good agent candidates regardless of cost.

    Where the Pricing Gets Complicated

    Token costs dominate runtime costs for most workloads. A two-hour agent session running intensive language tasks could easily generate $20-50 in token costs while only generating $0.16 in runtime charges. Teams optimizing AI agent costs should spend most of their attention on token efficiency — prompt engineering, context window management, model selection — rather than on the session-hour rate.

    For very high-volume, long-running workloads — continuous agents processing large document sets at scale — the economics may eventually favor building custom infrastructure over managed hosting. But that threshold is well above what most teams will encounter until they’re running AI agents as a core part of their production infrastructure at significant scale.

    The honest summary: $0.08/session-hour is not a meaningful cost for most workloads. It becomes material only when you’re running many parallel, long-duration sessions continuously. For the overwhelming majority of business use cases, token efficiency is the variable that matters, and the infrastructure cost is noise.

    How This Compares to Building Your Own

    The alternative to paying $0.08/session-hour is building and operating your own agent infrastructure. That means engineering time (months, initially), ongoing maintenance, cloud compute costs for your own execution environment, and the operational overhead of managing the system.

    For teams that haven’t built this yet, the managed pricing is almost certainly cheaper than the build cost for the first year — even accounting for the runtime premium. The crossover point where self-managed becomes cheaper depends on engineering cost assumptions and workload volume, but for most teams it’s well beyond where they’re operating today.

    Frequently Asked Questions

    Is idle time charged in Claude Managed Agents?

    No. Runtime billing only accrues when the session status is actively running. Time spent waiting for user input, tool confirmations, or between tasks does not count toward the $0.08/session-hour charge.

    What is the total cost of running a Claude Managed Agent for a typical business task?

    For moderate workloads — research agents, content pipelines, daily summary tasks — total costs typically range from $10-50/month combining runtime and token costs. Heavy, continuous agents could run $50-150/month depending on token volume.

    Are token costs or runtime costs more important to optimize for Claude Managed Agents?

    Token costs dominate for most workloads. A two-hour active session generates $0.16 in runtime charges but potentially $20-50 in token costs depending on workload intensity. Token efficiency is where most cost optimization effort should focus.

    At what point does building your own agent infrastructure become cheaper than Claude Managed Agents?

    The crossover depends on engineering cost assumptions and workload volume. For most teams, managed is cheaper than self-built through the first year. Very high-volume, continuously-running workloads at scale may eventually favor custom infrastructure.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

    What to do next

    Now that you have the cost — here’s how to choose and implement

    You know the session-hour rate. The harder decision is whether Managed Agents is the right architecture vs. building on the raw API — or vs. OpenAI’s equivalent.

  • AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    AI Agents Explained: What They Are, Who’s Using Them, and Why Your Business Will Need One

    What Is an AI Agent? An AI agent is a software program powered by a large language model that can take actions — not just answer questions. It reads files, sends messages, runs code, browses the web, and completes multi-step tasks on its own, without a human directing every move.

    Most people’s mental model of AI is a chat interface. You type a question, you get an answer. That’s useful, but it’s also the least powerful version of what AI can do in a business context.

    The version that’s reshaping how companies operate isn’t a chatbot. It’s an agent — a system that can actually do things. And with Anthropic’s April 2026 launch of Claude Managed Agents, the barrier to deploying those systems for real business work dropped significantly.

    What Makes an Agent Different From a Chatbot

    A chatbot responds. An agent acts.

    When you ask a chatbot to summarize last quarter’s sales report, it tells you how to do it, or summarizes text you paste in. When you give the same task to an agent, it goes and gets the report, reads it, identifies the key numbers, formats a summary, and sends it to whoever asked — all without you supervising each step.

    The difference sounds subtle but has large practical implications. An agent can be assigned work the same way you’d assign work to a person. It can work on tasks in the background while you do other things. It can handle repetitive processes that would otherwise require sustained human attention.

    The examples from the Claude Managed Agents launch make this concrete:

    Asana built AI Teammates — agents that participate in project management workflows the same way a human team member would. They pick up tasks. They draft deliverables. They work within the project structure that already exists.

    Rakuten deployed agents across sales, marketing, HR, and finance that accept assignments through Slack and return completed work — spreadsheets, slide decks, reports — directly to the person who asked.

    Notion’s implementation lets knowledge workers generate presentations and build internal websites while engineers ship code, all with agents handling parallel tasks in the background.

    None of those are hypothetical. They’re production deployments that went live within a week of the platform becoming available.

    What Business Processes Are Actually Good Candidates for Agents

    Not every business task is suited for an AI agent. The best candidates share a few characteristics: they’re repetitive, they involve working with information across multiple sources, and they don’t require judgment calls that need human accountability.

    Strong candidates include research and summarization tasks that currently require someone to pull data from multiple places and compile it. Drafting and formatting work — proposals, reports, presentations — that follows a consistent structure. Monitoring tasks that require checking systems or data sources on a schedule and flagging anomalies. Customer-facing support workflows for common, well-defined questions. Data processing pipelines that transform information from one format to another on a recurring basis.

    Weak candidates include tasks that require relationship context, ethical judgment, or creative direction that isn’t already well-defined. Agents execute well-specified work; they don’t substitute for strategic thinking.

    Why the Timing of This Launch Matters for Small and Mid-Size Businesses

    Until recently, deploying a production AI agent required either a technical team capable of building significant custom infrastructure, or an enterprise software contract with a vendor that had built it for you. That meant AI agents were effectively inaccessible to businesses without large technology budgets or dedicated engineering resources.

    Anthropic’s managed platform changes that equation. The infrastructure layer — the part that required months of engineering work — is now provided. A small business or a non-technical operations team can define what they need an agent to do and deploy it without building a custom backend.

    The pricing reflects this broader accessibility: $0.08 per session-hour of active runtime, plus standard token costs. For agents handling moderate workloads — a few hours of active operation per day — the runtime cost is a small fraction of what equivalent human time would cost for the same work.

    What to Actually Do With This Information

    The most useful framing for any business owner or operations leader isn’t “what is an AI agent?” It’s “what work am I currently paying humans to do that is well-specified enough for an agent to handle?”

    Start with processes that meet these criteria: they happen on a regular schedule, they involve pulling information from defined sources, they produce a consistent output format, and they don’t require judgment calls that have significant consequences if wrong. Those are your first agent candidates.

    The companies that will have a structural advantage in two to three years aren’t the ones that understood AI earliest. They’re the ones that systematically identified which parts of their operations could be handled by agents — and deployed them while competitors were still treating AI as a productivity experiment.

    Frequently Asked Questions

    What is an AI agent in simple terms?

    An AI agent is a program that can take actions — not just answer questions. It can read files, send messages, browse the web, and complete multi-step tasks on its own, working in the background the same way you’d assign work to an employee.

    What’s the difference between an AI chatbot and an AI agent?

    A chatbot responds to questions. An agent executes tasks. A chatbot tells you how to summarize a report; an agent retrieves the report, summarizes it, and sends it to whoever needs it — without you directing each step.

    What kinds of business tasks are best suited for AI agents?

    Repetitive, well-defined tasks that involve pulling information from multiple sources and producing consistent outputs: research summaries, report drafting, data processing, support workflows, and monitoring tasks are strong candidates. Tasks requiring significant judgment, relationship context, or creative direction are weaker candidates.

    How much does it cost to deploy an AI agent for a small business?

    Using Claude Managed Agents, costs are standard Anthropic API token rates plus $0.08 per session-hour of active runtime. An agent running a few hours per day for routine tasks might cost a few dollars per month in runtime — a fraction of the equivalent human labor cost.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

  • Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    Claude Managed Agents vs. Rolling Your Own: The Real Infrastructure Build Cost

    The Build-vs-Buy Question: Claude Managed Agents offers hosted AI agent infrastructure at $0.08/session-hour plus token costs. Rolling your own means engineering sandboxed execution, state management, checkpointing, credential handling, and error recovery yourself — typically months of work before a single production agent runs.

    Every developer team that wants to ship a production AI agent faces the same decision point: build your own infrastructure or use a managed platform. Anthropic’s April 2026 launch of Claude Managed Agents made that decision significantly harder to default your way through.

    This isn’t a “managed is always better” argument. There are legitimate reasons to build your own. But the build cost needs to be reckoned with honestly — and most teams underestimate it substantially.

    What You Actually Have to Build From Scratch

    The minimum viable production agent infrastructure requires solving several distinct problems, none of which are trivial.

    Sandboxed execution: Your agent needs to run code in an isolated environment that can’t access systems it isn’t supposed to touch. Building this correctly — with proper isolation, resource limits, and cleanup — is a non-trivial systems engineering problem. Cloud providers offer primitives (Cloud Run, Lambda, ECS), but wiring them into an agent execution model takes real work.

    Session state and context management: An agent working on a multi-step task needs to maintain context across tool calls, handle context window limits gracefully, and not drop state when something goes wrong. Building reliable state management that works at production scale typically takes several engineering iterations to get right.

    Checkpointing: If your agent crashes at step 11 of a 15-step job, what happens? Without checkpointing, the answer is “start over.” Building checkpointing means serializing agent state at meaningful intervals, storing it durably, and writing recovery logic that knows how to resume cleanly. This is one of the harder infrastructure problems in agent systems, and most teams don’t build it until they’ve lost work in production.

    Credential management: Your agent will need to authenticate with external services — APIs, databases, internal tools. Managing those credentials securely, rotating them, and scoping them properly to each agent’s permissions surface is an ongoing operational concern, not a one-time setup.

    Tool orchestration: When Claude calls a tool, something has to handle the routing, execute the tool, handle errors, and return results in the right format. This orchestration layer seems simple until you’re debugging why tool call 7 of 12 is failing silently on certain inputs.

    Observability: In production, you need to know what your agents are doing, why they’re doing it, and when they fail. Building logging, tracing, and alerting for an agent system from scratch is a non-trivial DevOps investment.

    Anthropic’s stated estimate is that shipping production agent infrastructure takes months. That tracks with what we’ve seen in practice. It’s not months of full-time work for a large team — but it’s months of the kind of careful, iterative infrastructure engineering that blocks product work while it’s happening.

    What Claude Managed Agents Provides

    Claude Managed Agents handles all of the above at the platform level. Developers define the agent’s task, tools, and guardrails. The platform handles sandboxed execution, state management, checkpointing, credential scoping, tool orchestration, and error recovery.

    The official API documentation lives at platform.claude.com/docs/en/managed-agents/overview. Agents can be deployed via the Claude console, Claude Code CLI, or the new agents CLI. The platform supports file reading, command execution, web browsing, and code execution as built-in tool capabilities.

    Anthropic describes the speed advantage as 10x — from months to weeks. Based on the infrastructure checklist above, that’s believable for teams starting from zero.

    The Honest Case for Rolling Your Own

    There are real reasons to build your own agent infrastructure, and they shouldn’t be dismissed.

    Deep customization: If your agent architecture has requirements that don’t fit the Managed Agents execution model — unusual tool types, proprietary orchestration patterns, specific latency constraints — you may need to own the infrastructure to get the behavior you need.

    Cost at scale: The $0.08/session-hour pricing is reasonable for moderate workloads. At very high scale — thousands of concurrent sessions running for hours — the runtime cost becomes a significant line item. Teams with high-volume workloads may find that the infrastructure engineering investment pays back faster than they expect.

    Vendor dependency: Running your agents on Anthropic’s managed platform means your production infrastructure depends on Anthropic’s uptime, their pricing decisions, and their roadmap. Teams with strict availability requirements or long-term cost predictability needs have legitimate reasons to prefer owning the stack.

    Compliance and data residency: Some regulated industries require that agent execution happen within specific geographic regions or within infrastructure that the company directly controls. Managed cloud platforms may not satisfy those requirements.

    Existing investment: If your team has already built production agent infrastructure — as many teams have over the past two years — migrating to Managed Agents requires re-architecting working systems. The migration overhead is real, and “it works” is a strong argument for staying put.

    The Decision Framework

    The practical question isn’t “is managed better than custom?” It’s “what does my team’s specific situation call for?”

    Teams that haven’t shipped a production agent yet and don’t have unusual requirements should strongly consider starting with Managed Agents. The infrastructure problems it solves are real, the time savings are significant, and the $0.08/hour cost is unlikely to be the deciding factor at early scale.

    Teams with existing agent infrastructure, high-volume workloads, or specific compliance requirements should evaluate carefully rather than defaulting to migration. The right answer depends heavily on what “working” looks like for your specific system.

    Teams building on Claude Code specifically should note that Managed Agents integrates directly with the Claude Code CLI and supports custom subagent definitions — which means the tooling is designed to fit developer workflows rather than requiring a separate management interface.

    Frequently Asked Questions

    How long does it take to build production AI agent infrastructure from scratch?

    Anthropic estimates months for a full production-grade implementation covering sandboxed execution, checkpointing, state management, credential handling, and observability. The actual time depends heavily on team experience and specific requirements.

    What does Claude Managed Agents handle that developers would otherwise build themselves?

    Sandboxed code execution, persistent session state, checkpointing, scoped permissions, tool orchestration, context management, and error recovery — the full infrastructure layer underneath agent logic.

    At what scale does it make sense to build your own agent infrastructure vs. using Claude Managed Agents?

    There’s no universal threshold, but the $0.08/session-hour pricing becomes a significant cost factor at thousands of concurrent long-running sessions. Teams should model their expected workload volume before assuming managed is cheaper than custom at scale.

    Can Claude Managed Agents work with Claude Code?

    Yes. Managed Agents integrates with the Claude Code CLI and supports custom subagent definitions, making it compatible with developer-native workflows.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

  • Claude Managed Agents Enterprise Deployment: What Rakuten’s 5-Department Rollout Actually Cost

    Claude Managed Agents Enterprise Deployment: What Rakuten’s 5-Department Rollout Actually Cost

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    Rakuten Stood Up 5 Enterprise Agents in a Week. Here’s What Claude Managed Agents Actually Does

    Claude Managed Agents for Enterprise: A cloud-hosted platform from Anthropic that lets enterprise teams deploy AI agents across departments — product, sales, HR, finance, marketing — without building backend infrastructure. Agents plug directly into Slack, Teams, and existing workflow tools.

    When Rakuten announced it had deployed enterprise AI agents across five departments in a single week using Anthropic’s newly launched Claude Managed Agents, it wasn’t a headline about AI being impressive. It was a headline about deployment speed becoming a competitive variable.

    A week. Five departments. Agents that plug into Slack and Teams, accept task assignments, and return deliverables — spreadsheets, slide decks, reports — to the people who asked for them.

    That timeline matters. It used to take enterprise teams months to do what Rakuten did in days. Understanding what changed is the whole story.

    What Enterprise AI Deployment Used to Look Like

    Before managed infrastructure existed, deploying an AI agent in an enterprise environment meant building a significant amount of custom scaffolding. Teams needed secure sandboxed execution environments so agents could run code without accessing sensitive systems. They needed state management so a multi-step task didn’t lose its progress if something failed. They needed credential management, scoped permissions, and logging for compliance. They needed error recovery logic so one bad API call didn’t collapse the whole job.

    Each of those is a real engineering problem. Combined, they typically represented months of infrastructure work before a single agent could touch a production workflow. Most enterprise IT teams either delayed AI agent adoption or deprioritized it entirely because the upfront investment was too high relative to uncertain ROI.

    What Claude Managed Agents Changes for Enterprise Teams

    Anthropic’s Claude Managed Agents, launched in public beta on April 9, 2026, moves that entire infrastructure layer to Anthropic’s platform. Enterprise teams now define what the agent should do — its task, its tools, its guardrails — and the platform handles everything underneath: tool orchestration, context management, session persistence, checkpointing, and error recovery.

    The result is what Rakuten demonstrated: rapid, parallel deployment across departments with no custom infrastructure investment per team.

    According to Anthropic, the platform reduces time from concept to production by up to 10x. That claim is supported by the adoption pattern: companies are not running pilots, they’re shipping production workflows.

    How Enterprise Teams Are Using It Right Now

    The enterprise use cases emerging from the April 2026 launch tell a consistent story — agents integrated directly into the communication and workflow tools employees already use.

    Rakuten deployed agents across product, sales, marketing, finance, and HR. Employees assign tasks through Slack and Teams. Agents return completed deliverables. The interaction model is close to what a team member experiences delegating work to a junior analyst — except the agent is available 24 hours a day and doesn’t require onboarding.

    Asana built what they call AI Teammates — agents that operate inside project management workflows, picking up assigned tasks and drafting deliverables alongside human team members. The distinction here is that agents aren’t running separately from the work — they’re participants in the same project structure humans use.

    Notion deployed Claude directly into workspaces through Custom Agents. Engineers use it to ship code. Knowledge workers use it to generate presentations and build internal websites. Multiple agents can run in parallel on different tasks while team members collaborate on the outputs in real time.

    Sentry took a developer-specific angle — pairing their existing Seer debugging agent with a Claude-powered counterpart that writes patches and opens pull requests automatically when bugs are identified.

    What Enterprise IT Teams Are Actually Evaluating

    The questions enterprise IT and operations leaders should be asking about Claude Managed Agents are different from what a developer evaluating the API would ask. For enterprise teams, the key considerations are:

    Governance and permissions: Claude Managed Agents includes scoped permissions, meaning each agent can be configured to access only the systems it needs. This is table stakes for enterprise deployment, and Anthropic built it into the platform rather than leaving it to each team to implement.

    Compliance and logging: Enterprises in regulated industries need audit trails. The managed platform provides observability into agent actions, which is significantly harder to implement from scratch.

    Integration with existing tools: The Rakuten and Asana deployments demonstrate that agents can integrate with Slack, Teams, and project management tools. This matters because enterprise AI adoption fails when it requires employees to change their workflow. Agents that meet employees where they already work have a fundamentally higher adoption ceiling.

    Failure recovery: Checkpointing means a long-running enterprise workflow — a quarterly report compilation, a multi-system data aggregation — can resume from its last saved state rather than restarting entirely if something goes wrong. For enterprise-scale jobs, this is the difference between a recoverable error and a business disruption.

    The Honest Trade-Off

    Moving to managed infrastructure means accepting certain constraints. Your agents run on Anthropic’s platform, which means you’re dependent on their uptime, their pricing changes, and their roadmap decisions. Teams that have invested in proprietary agent architectures — or who have compliance requirements that preclude third-party cloud execution — may find Managed Agents unsuitable regardless of its technical merits.

    The $0.08 per session-hour pricing, on top of standard token costs, also requires careful modeling for enterprise workloads. A suite of agents running continuously across five departments could accumulate meaningful runtime costs that need to be accounted for in technology budgets.

    That said, for enterprise teams that haven’t yet deployed AI agents — or who have been blocked by infrastructure cost and complexity — the calculus has changed. The question is no longer “can we afford to build this?” It’s “can we afford not to deploy this?”

    Frequently Asked Questions

    How quickly can an enterprise team deploy agents with Claude Managed Agents?

    Rakuten deployed agents across five departments — product, sales, marketing, finance, and HR — in under a week. Anthropic claims a 10x reduction in time-to-production compared to building custom agent infrastructure.

    What enterprise tools do Claude Managed Agents integrate with?

    Deployed agents can integrate with Slack, Microsoft Teams, Asana, Notion, and other workflow tools. Agents accept task assignments through these platforms and return completed deliverables directly in the same environment.

    How does Claude Managed Agents handle enterprise security requirements?

    The platform includes scoped permissions (limiting each agent’s system access), observability and logging for audit trails, and sandboxed execution environments that isolate agent operations from sensitive systems.

    What does Claude Managed Agents cost for enterprise use?

    Pricing is standard Anthropic API token rates plus $0.08 per session-hour of active runtime. Enterprise teams with multiple agents running across departments should model their expected monthly runtime to forecast costs accurately.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

  • Anthropic Launched Managed Agents. Here’s How We Looked at It — and Why We’re Staying Our Course.

    Anthropic Launched Managed Agents. Here’s How We Looked at It — and Why We’re Staying Our Course.

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    Anthropic Launched Managed Agents. Here’s How We Looked at It — and Why We’re Staying Our Course.

    What Are Claude Managed Agents? Anthropic’s Claude Managed Agents is a cloud-hosted infrastructure service launched April 9, 2026, that lets developers and businesses deploy AI agents without building their own execution environments, state management, or orchestration systems. You define the task and tools; Anthropic runs the infrastructure.

    On April 9, 2026, Anthropic announced the public beta of Claude Managed Agents — a new infrastructure layer on the Claude Platform designed to make AI agent deployment dramatically faster and more stable. According to Anthropic, it reduces build and deployment time by up to 10x. Early adopters include Notion, Asana, Rakuten, and Sentry.

    We looked at it. Here’s what it is, how it compares to what we’ve built, and why we’re continuing on our own path — at least for now.

    What Is Anthropic Managed Agents?

    Claude Managed Agents is a suite of APIs that gives development teams fully managed, cloud-hosted infrastructure for running AI agents at scale. Instead of building secure sandboxes, managing session state, writing custom orchestration logic, and handling tool execution errors yourself, Anthropic’s platform does it for you.

    The key capabilities announced at launch include:

    • Sandboxed code execution — agents run in isolated, secure environments
    • Persistent long-running sessions — agents stay alive across multi-step tasks without losing context
    • Checkpointing — if an agent job fails mid-run, it can resume from where it stopped rather than restarting
    • Scoped permissions — fine-grained control over what each agent can access
    • Built-in authentication and tool orchestration — the platform handles the plumbing between Claude and the tools it uses

    Pricing is straightforward: you pay standard Anthropic API token rates plus $0.08 per session-hour of active runtime, measured in milliseconds.

    Why It’s a Legitimate Signal

    The companies Anthropic named as early adopters aren’t small experiments. Notion, Asana, Rakuten, and Sentry are running production workflows at scale — code automation, HR processes, productivity tooling, and finance operations. When teams at that level migrate to managed infrastructure instead of building their own, it suggests the platform has real stability behind it.

    The checkpointing feature in particular stands out. One of the most painful failure modes in long-running AI pipelines is a crash at step 14 of a 15-step job. You lose everything and start over. Checkpointing solves that problem at the infrastructure level, which is the right place to solve it.

    Anthropic’s framing is also pointed directly at enterprise friction: the reason companies don’t deploy agents faster isn’t Claude’s capabilities — it’s the scaffolding cost. Managed Agents is an explicit attempt to remove that friction.

    What We’ve Built — and Why It Works for Us

    At Tygart Media, we’ve been running our own agent stack for over a year. What started as a set of Claude prompts has evolved into a full content and operations infrastructure built on top of the Claude API, Google Cloud Platform, and WordPress REST APIs.

    Here’s what our stack actually does:

    • Content pipelines — We run full article production pipelines that write, SEO-optimize, AEO-optimize, GEO-optimize, inject schema markup, assign taxonomy, add internal links, run quality gates, and publish — all in a single session across 20+ WordPress sites.
    • Batch draft creation — We generate 15-article batches with persona-targeting and variant logic without manual intervention.
    • Cross-site content strategy — Agents scan multiple sites for authority pages, identify linking opportunities, write locally-relevant variants, and publish them with proper interlinking.
    • Image pipelines — End-to-end image processing: generation via Vertex AI/Imagen, IPTC/XMP metadata injection, WebP conversion, and upload to WordPress media libraries.
    • Social media publishing — Content flows from WordPress to Metricool for LinkedIn, Facebook, and Google Business Profile scheduling.
    • GCP proxy routing — A Cloud Run proxy handles WordPress REST API calls to avoid IP blocking across different hosting environments (SiteGround, WP Engine, Flywheel, Apache/ModSecurity).

    This infrastructure took time to build. But it’s purpose-built for our specific workflows, our sites, and our clients. It knows which sites route through the GCP proxy, which need a browser User-Agent header to pass ModSecurity, and which require a dedicated Cloud Run publisher. That specificity has real value.

    Where Managed Agents Is Compelling — and Where It Isn’t (Yet)

    If we were starting from zero today, Managed Agents would be worth serious evaluation. The session persistence and checkpointing would immediately solve the two biggest failure modes we’ve had to engineer around manually.

    But migrating an existing stack to Managed Agents isn’t a lift-and-shift. Our pipelines are tightly integrated with GCP infrastructure, custom proxy routing, WordPress credential management, and Notion logging. Re-architecting that to run inside Anthropic’s managed environment would be a significant project — with no clear gain over what’s already working.

    The $0.08/session-hour pricing also adds up quickly on batch operations. A 15-article pipeline running across multiple sites for two to three hours could add meaningful cost on top of already-substantial token usage.

    For teams that haven’t built their own agent infrastructure yet — especially enterprise teams evaluating AI for the first time — Managed Agents is probably the right starting point. For teams that already have a working stack, the calculus is different.

    What We’re Watching

    We’re treating this as a signal, not an action item. A few things would change that:

    • Native integrations — If Managed Agents adds direct integrations with WordPress, Metricool, or GCP services, the migration case gets stronger.
    • Checkpointing accessibility — If we can use checkpointing on top of our existing API calls without fully migrating, that’s an immediate win worth pursuing.
    • Pricing at scale — Volume discounts or enterprise pricing would change the batch job math significantly.
    • MCP interoperability — Managed Agents running with Model Context Protocol support would let us plug our existing skill and tool ecosystem in without a full rebuild.

    The Bigger Picture

    Anthropic launching managed infrastructure is the clearest sign yet that the AI industry has moved past the “what can models do” question and into the “how do you run this reliably at scale” question. That’s a maturity marker.

    The same shift happened with cloud computing. For a while, every serious technology team ran its own servers. Then AWS made the infrastructure layer cheap enough and reliable enough that it only made sense to build it yourself if you had very specific requirements. We’re not there yet with AI agents — but Anthropic is clearly pushing in that direction.

    For now, we’re watching, benchmarking, and continuing to run our own stack. When the managed layer offers something we can’t build faster ourselves, we’ll move. That’s the right framework for evaluating any infrastructure decision.

    Frequently Asked Questions

    What is Anthropic Managed Agents?

    Claude Managed Agents is a cloud-hosted AI agent infrastructure service from Anthropic, launched in public beta on April 9, 2026. It provides persistent sessions, sandboxed execution, checkpointing, and tool orchestration so teams can deploy AI agents without building their own backend infrastructure.

    How much does Claude Managed Agents cost?

    Pricing is based on standard Anthropic API token costs plus $0.08 per session-hour of active runtime, measured in milliseconds.

    Who are the early adopters of Claude Managed Agents?

    Anthropic named Notion, Asana, Rakuten, Sentry, and Vibecode as early users, deploying the service for code automation, productivity workflows, HR processes, and finance operations.

    Is Anthropic Managed Agents worth switching to if you already have an agent stack?

    It depends on your existing infrastructure. For teams starting fresh, it removes significant scaffolding cost. For teams with mature, purpose-built pipelines already running on GCP or other cloud infrastructure, the migration overhead may outweigh the benefits in the short term.

    What is checkpointing in Managed Agents?

    Checkpointing allows a long-running agent job to resume from its last saved state if it encounters an error, rather than restarting the entire task from the beginning. This is particularly valuable for multi-step batch operations.

    Related: Complete Pricing Reference — every variable in one place. Complete FAQ Hub — every question answered.

  • Your Jobs Are a Knowledge Base. You’re Just Not Using Them That Way.

    Your Jobs Are a Knowledge Base. You’re Just Not Using Them That Way.

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

    Every restoration job teaches something. Almost none of it ever gets written down.

    A crew shows up to a flooded basement at 2am. They make decisions — where to set the equipment, how to read the moisture map, which walls are worth opening and which aren’t, how to sequence the dry-down so the structure doesn’t get worse before it gets better. They’ve made these calls before. They know things that took years to learn. They finish the job, submit a field report, and move on.

    Then the experienced tech takes another job across town. Or retires. Or just gets too busy to train anyone. And that knowledge disappears.

    I want to talk about a different approach. One that captures that knowledge systematically — and turns it into something that works in two directions at once.

    The Double-Purpose Content System

    The idea is straightforward: document your jobs as content. Scrub the client-specific details — no names, no addresses, no identifying information. But tell the real story. What was the scope? What made this job complicated? What decisions were made and why? What was the outcome?

    Published on your website, this does something conventional marketing content can’t: it demonstrates expertise through specificity. Not “we handle all types of water damage” — but a documented account of how your team handled a Category 3 intrusion in a commercial kitchen with active mold growth and a compressed timeline. That’s a different signal entirely.

    The reader — whether that’s a property manager searching for a qualified contractor or an insurance adjuster evaluating whether to refer you — isn’t reading a brochure. They’re reading a case record. They can see how your team thinks.

    But here’s the second direction, and it’s the one I find more interesting: that same documentation feeds back into the company as a knowledge base.

    The Internal Payoff

    Restoration companies have a training problem that nobody talks about directly. The knowledge of how to do the job well is distributed unevenly across the team. The senior technicians have it. The new hires don’t. And the transfer mechanism is usually informal — ride-alongs, tribal knowledge, institutional memory held by people who may not stay forever.

    When you document jobs as structured content, you start to build something that actually scales. A new technician can search the knowledge base for jobs similar to what they’re walking into. They can see how a comparable loss was scoped, how the equipment was deployed, what complications arose and how they were handled. Before they’ve seen thirty jobs themselves, they can read about thirty jobs your company has already worked.

    An operations manager making a scheduling or resource decision can pull up historical jobs of a similar size and see what the typical crew requirements were. A project manager prepping a scope of work can see how similar scopes were structured and what line items were typically included.

    And when AI tools enter the workflow — which they will, if they haven’t already — that documented job history becomes training data your AI actually understands. Not generic restoration industry knowledge pulled from the web. Your company’s specific approach, your specific decisions, your specific standards. An AI assistant working from that foundation gives answers that sound like your company, because they’re drawn from your company’s real work.

    What Makes This Different From a Blog

    Most restoration company blogs are essentially SEO performance. Keywords stuffed into generic articles about what causes mold or how long drying takes. Useful, maybe. Differentiating, no.

    What I’m describing is a content system built on documented operational reality. The subject matter isn’t manufactured — it’s the actual work. Which means it has a quality that manufactured content can never replicate: it happened. The specificity is real because the job was real. The decisions were real. The outcome was real.

    Readers feel this, even when they can’t articulate why. They’re not evaluating whether your content sounds authoritative. They’re reading something that is authoritative, because it comes from direct experience rather than borrowed knowledge.

    And unlike a blog that requires a content team to invent topics every week, this system has an inventory problem that only gets easier over time. Every job adds to it. The longer you run the system, the richer the knowledge base becomes — for your website visitors and for your own team.

    The Setup

    The practical structure is simpler than it sounds. Each job entry captures a handful of consistent fields: loss type, scope classification, environmental conditions, key decision points, equipment deployed, timeline, outcome. The sensitive details — client, location, anything identifying — never make it into the published version.

    What gets published is the pattern. The structure of the problem and the response. Categorized, searchable, and useful to anyone trying to understand how your company operates — including your own people.

    This isn’t a new concept in medicine or law, where case documentation has always served both public communication and internal learning simultaneously. It’s just new in restoration, where the work is equally complex and the knowledge equally worth preserving.

    The companies that start building this now will have a meaningful advantage in three years. Not because their marketing was cleverer — because their institutional knowledge actually compounded instead of walking out the door every time someone left.

    Tygart Media builds content and knowledge systems for property damage restoration companies. If you’re interested in implementing a job documentation system for your operation, start here.

  • Agentic Commerce: The Protocol Stack That Replaces the Human Buyer

    Agentic Commerce: The Protocol Stack That Replaces the Human Buyer

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    For most of the history of the internet, commerce had a fixed shape: a human found a product, a human put it in a cart, a human entered payment details, a human clicked buy. The entire infrastructure of digital commerce — payment processors, shopping carts, merchant platforms, ad networks, fraud detection — was built around that human in the loop.

    Agentic commerce removes the human from most of those steps. An AI agent acting on your behalf finds the product, evaluates it against your criteria, initiates checkout, authorizes payment, and completes the transaction. The human sets the intent and the constraints. The agent executes. And the protocols being built right now are what make that execution possible at scale across the open web.

    This isn’t a future prediction. It’s the infrastructure layer being built in production today, with real merchants, real transactions, and real competitive stakes for every business that sells anything online.

    The Protocol Stack: Four Layers, Multiple Players

    Agentic commerce isn’t one protocol — it’s a stack of protocols, each handling a specific layer of the transaction. Understanding the stack is the prerequisite for understanding what any business actually needs to do about it.

    The commerce layer handles the shopping journey itself: how an agent discovers products, queries catalogs, compares options, and initiates checkout. Two protocols are competing here. OpenAI’s Agentic Commerce Protocol (ACP), co-developed with Stripe and open-sourced under Apache 2.0, powers checkout inside ChatGPT and connects to merchants through Stripe’s payment infrastructure. Google’s Universal Commerce Protocol (UCP), launched at NRF in January 2026 with Shopify, Walmart, Target, and more than twenty partners, handles the full commerce lifecycle from discovery through post-purchase across any AI surface, not just Google’s own.

    The payments layer handles authorization, trust, and money movement — the part of the transaction where something actually changes hands. Google’s Agent Payments Protocol (AP2) is the most prominent here, introducing “mandates” — digitally signed statements that define exactly what an agent is authorized to do and spend. Visa has its Trusted Agent Protocol. Mastercard has Agent Pay. Coinbase introduced x402, which revives the long-dormant HTTP 402 “Payment Required” status code to enable microtransactions between machines without accounts or API keys.

    The infrastructure layer is the operating system underneath everything else: Anthropic’s Model Context Protocol (MCP) for connecting AI models to external tools and data sources, and Google’s Agent2Agent (A2A) protocol for coordination between agents. These are less visible to merchants but essential for making the commerce and payments layers work together.

    The trust layer sits across all of it: fraud detection, consent management, identity verification for non-human actors. This is the least standardized layer and the one where the most work remains.

    ACP vs. UCP: Different Bets on the Same Shift

    The practical choice most merchants face isn’t which single protocol to adopt — it’s understanding what each one connects to and what supporting both costs.

    ACP is optimized for merchant integrations with ChatGPT, while UCP takes a more surface-agnostic approach, aiming to standardize how platforms, agents, and merchants execute commerce flows across the ecosystem. The scope difference is meaningful: ACP standardizes the checkout conversation. UCP standardizes the entire shopping journey.

    The tradeoff each represents is also different. ACP trades openness for control, while UCP trades control for index breadth and protocol-level standardization. ACP gives merchants a more curated, high-touch integration with a specific AI surface. UCP gives merchants broader reach at the cost of less hand-holding through the integration.

    For most merchants, the realistic answer is both — because each connects to a different AI shopping surface where different buyers will transact. Most retailers will need to support at least two of these protocols, since each connects to different AI shopping surfaces. ChatGPT uses ACP for transactions. Google AI Mode and Gemini use UCP. The protocols aren’t competing for the same merchants so much as competing to be the standard their respective AI ecosystems use.

    The Amazon Anomaly

    Every major retailer in the agentic commerce ecosystem is moving toward open protocols — except the largest one. Amazon has taken the opposite position: updating its robots.txt to block AI agent crawlers, tightening its legal terms against agent-initiated purchasing, and pursuing litigation against unauthorized agent interactions with its platform.

    The strategic logic is straightforward. Amazon’s competitive advantage is built on controlling the discovery moment — the point at which a buyer decides what to consider buying. Open protocols where AI agents compare products across every online store turn Amazon into just another merchant behind an API, stripping away the algorithmic leverage that makes its platform valuable to both buyers and sellers. The walled garden is a defensive move, not a philosophical one.

    For merchants who are primarily Amazon-dependent, the agentic commerce transition is less immediately relevant — Amazon’s own AI shopping assistant, Rufus, operates inside the walled garden and isn’t subject to open protocol dynamics. For merchants who sell direct or through multi-channel platforms, the protocols represent a potential path to discovery that doesn’t flow through Amazon’s toll booth.

    The Payment Authorization Problem

    The hardest unsolved problem in agentic commerce isn’t discovery or checkout — it’s authorization. How does a merchant know that an AI agent actually has permission to spend the buyer’s money? How does a buyer trust that an agent won’t exceed its authorized scope? How does a payment processor handle chargebacks when the “buyer” is software?

    AP2’s mandate system is the most developed answer to this. AP2 introduces the concept of mandates, digitally signed statements that define what an agent is allowed to do, such as create a cart, complete a purchase, or manage a subscription. These mandates are portable, verifiable, and revocable, allowing multiple stakeholders to coordinate safely. A mandate is essentially a scoped permission — the agent can spend up to this amount, in this category, on behalf of this identity, and here’s the cryptographic proof.

    This matters for the full agent-to-agent commerce scenario — where both buyer and seller are autonomous agents, no human is involved in real time, and traditional consumer protection frameworks don’t map cleanly to the transaction. That’s the frontier where the standards work is most active and the solutions are least settled.

    What This Means for Content and SEO Strategy

    The shift to agentic commerce doesn’t just change how transactions happen. It changes how discovery happens — which changes what content and SEO strategy is actually for.

    In the search engine model, a buyer types a query, gets a ranked list of results, clicks through, and eventually converts. The optimization target is rank position. In the agentic commerce model, a buyer tells an agent what they want, the agent queries structured data sources and evaluates options programmatically, and surfaces a recommendation. The optimization target shifts from rank position to selection rate — how often an agent chooses your product when it’s evaluating options that include yours.

    Selection rate is determined by data quality (how completely and accurately your product catalog is exposed through the protocol), trust signals (reviews, ratings, return policies — the inputs agents use to evaluate reliability), and price competitiveness at the moment of agent evaluation. AEO and GEO optimization — structuring content so AI systems can extract and cite it accurately — becomes more important, not less, in an agentic commerce environment. The agent needs to understand your product in enough depth to recommend it with confidence.

    For service businesses and content publishers who aren’t selling physical goods, the implications are different but parallel. When AI agents are answering questions and making recommendations on behalf of users, the question of which businesses and sources get cited is the agentic equivalent of search rank. The content infrastructure that makes you citable — entity clarity, structured data, authoritative sourcing — is the same infrastructure that makes you recommendable in an agent-mediated discovery environment.

    The Readiness Ladder

    Agentic commerce readiness isn’t binary — it’s a ladder, and most businesses are somewhere in the middle rather than at the top or bottom.

    The first rung is structured data hygiene: product catalogs that are complete, accurate, and machine-readable. If your product data is messy, inconsistent, or locked behind interfaces that agents can’t parse, no protocol integration will help. Clean structured data is the prerequisite for everything else.

    The second rung is protocol awareness: understanding which protocols matter for your specific channels and customer base. A Shopify merchant gets ACP integration automatically through the platform. A business selling through Google Shopping needs UCP readiness. A B2B operation should be watching AP2 and mandate-based authorization more closely than consumer checkout protocols.

    The third rung is active integration: implementing the relevant protocol specs, publishing the required endpoints, and testing agent interactions in a controlled environment before they happen in production. This is where most businesses aren’t yet — not because the protocols are inaccessible, but because the urgency hasn’t been felt directly.

    The fourth rung is optimization: monitoring selection rate and proxy conversion metrics, iterating on catalog data quality and trust signals, and adapting content strategy for agent-mediated discovery rather than human-mediated search. This is where competitive differentiation will be built once the infrastructure layer matures.

    The window for first-mover advantage in protocol adoption is open now, and it won’t stay open indefinitely. The businesses that establish protocol presence before agentic commerce becomes the default mode of online discovery will have an advantage that compounds as agent behavior increasingly determines where transactions happen.

    Frequently Asked Questions About Agentic Commerce

    Do small businesses need to worry about agentic commerce protocols now?

    If you’re on Shopify, you may already be enrolled — Shopify has handled ACP integration at the platform level for eligible merchants. If you’re not on a platform that’s done it for you, the honest answer is: start with structured data hygiene now, monitor protocol adoption over the next six months, and plan for integration in the second half of 2026. The urgency is real but the timeline isn’t emergency-level for most small businesses yet.

    What’s the difference between ACP, UCP, and MCP?

    ACP and UCP are commerce protocols — they define how agents shop and transact on behalf of buyers. MCP is an infrastructure protocol — it defines how AI models connect to external tools and data sources, including commerce APIs. MCP is the plumbing; ACP and UCP are the applications running on the plumbing. Most merchants will interact primarily with ACP and UCP. Developers building agent applications interact more directly with MCP.

    Will there be one winning protocol or multiple?

    Multiple, almost certainly. The historical pattern of internet standards is that protocols fragment by ecosystem and then slowly consolidate as interoperability pressure mounts. ACP and UCP serve different AI surfaces and are backed by different platform ecosystems. Both will persist as long as ChatGPT and Google AI Mode both matter, which is likely to be a long time. The consolidation pressure comes from merchants who don’t want to maintain five separate integrations — that merchant pressure will drive interoperability work, not the platforms voluntarily ceding ground.

    How does this affect businesses that don’t sell products online?

    Service businesses and content publishers are affected through the discovery layer, not the transaction layer. When AI agents answer questions and make recommendations, the businesses and sources that get surfaced are determined by the same kind of structured data and entity clarity that determines protocol-level discoverability for product merchants. The content infrastructure that makes you citable by AI systems is the service-business equivalent of protocol integration for product merchants.

    What should I actually do this week?

    Audit your structured product or service data for completeness and machine readability. Check whether your commerce platform has already integrated any of the major protocols on your behalf. Read the ACP and UCP documentation to understand what implementation requires. And look at your current AEO and GEO optimization — the content signals that determine AI citability are the same signals that will determine agent recommendability as agentic commerce matures.