Last verified: September 5, 2026 (Pacific). Source: Thanks.io product email from Ryan Hartman. Product docs: How To Create A Dynamic Postcard Template and thanks.io. This is an operator read of a vendor update, not a paid placement.
Direct answer: Thanks.io now lets you apply fun visual effects to the Street View image of a recipient’s house inside the platform’s dynamic postcard image builder. The house photo was already a merge field. The new piece is styling that photo so it reads more like a cartoon or treated illustration than a raw Google capture.
That is the whole announcement. The rest of this page is how to treat it as a control, not a novelty.
Vendor example from Thanks.io's September 5, 2026 product update. Editorial use.
What actually shipped
Thanks.io’s dynamic postcard builder has long been able to print a Google Street View or Map View of the recipient address as the card background. Official docs still document the ~STREET_VIEW~ and ~MAP_VIEW~ data tags, plus an absentee-owner override: set Custom 1 to absentee and put the subject-property address in Custom 2 so the card mails to the owner but shows the property.
The September 5, 2026 email adds one layer on top of that pipeline: effects on those street-view house images. The subject line called them “cartoonified houses.” The body called them “fun effects.” We have not independently enumerated every filter name inside the builder. Until the help center lists them, treat the feature as a style pass on an existing merge image, not as a new mail class.
What did not change, based on public docs: formats (4×6, 6×9, 6×11), QR tracking, handwriting engine, Canva path, and per-piece pricing. Do not rewrite a media plan because the house now looks drawn.
Why a house on a card still works
A street-view house on a postcard is a recognition hack. The recipient does not have to decode a brand. They decode their own porch. That is why real-estate teams and a smaller set of restoration and insurance shops already use the builder.
A cartoon or stylized treatment changes the emotional register. A raw Street View can feel like surveillance. A treated image can feel like a sketch of the place. That is useful when the job is a listing conversation, a just-listed neighbor note, or a thank-you after a dry-out. It is the wrong register when the job is a water-loss notice, a denial letter, or anything that has to look like a record.
Where operators should use it
Use the effect when the card is allowed to be personal and slightly playful:
Just-listed / just-sold neighbor farms, where the house is the subject and the tone is invitation.
Absentee-owner outreach that already uses Custom 1 / Custom 2 so the mailed address and the pictured property can differ.
Post-job thank-you mail from a restoration shop, after the work is done and the record already exists in the file.
Seasonal or sphere mail where the house is a landmark, not evidence.
Do not use the effect when the image has to stand as a document. Street View is already a dated, third-party capture. Cartoonizing it does not make it more accurate. On a rural road with no panorama, Map View is still the honest fallback the vendor already recommends.
How to set it up without guessing
Open Image Templates and the dynamic image builder inside Thanks.io.
Set the background to the Street View or Map View tag, not a one-off screenshot.
Apply the new effect on that street-view layer. Preview more than one address before you lock a campaign. Corners, hedges, and parked cars render differently than a clean suburban elevation.
Keep headline, QR, and handwriting as separate layers. The effect is decoration on the house, not a reason to hide the offer.
If the recipient is an absentee owner, keep the documented Custom 1 = absentee / Custom 2 = subject-property address pattern. The effect does not replace that mapping.
Generate a live preview for a real row in the list, not only the template dummy address.
This feature is not an SEO tactic. It is a physical-mail personalization tactic. The search job for operators is different: publish a page that answer engines can cite when someone asks whether Thanks.io can stylize a house photo on a postcard.
AEO. Lead with the fact, date, and product surface (dynamic postcard image builder). Put the same answer in the FAQ so extractors do not have to invent one.
SEO. Rank for the query family around Thanks.io Street View postcards, cartoon house mailers, and dynamic postcard effects. Those phrases now have a dated source page.
GEO. Name the vendor, the builder, the Street View / Map View tags, and the absentee-owner fields so generative engines can reuse entities instead of collapsing this into “AI postcard art.”
If you run restoration or real-estate content in a metro, the local layer is the address merge, not a city landing page. The card is already geo-personal. Your website should say which campaign types get the effect and which do not, in the same voice you use on the shop floor.
Quality notes before anyone hits send
Street View licensing and freshness are still the vendor’s problem and yours. Preview ugly captures. Suppress rows where the panorama is a fence, a truck, or the neighbor’s house. Do not imply the cartoon is a current photo of completed work. Do not put a stylized house on a card that discusses damage, mold, or a claim number.
We did not receive pricing, effect names, or API field changes in the email. If those land in the help center later, this page should be updated against the doc, not against memory.
FAQ
Can Thanks.io put a cartoon version of a house on a postcard?
Yes, as of September 5, 2026. Thanks.io added fun effects for Street View house images inside the dynamic postcard image builder. The house image itself was already available via Street View and Map View merge tags.
Is this a new postcard size?
No. It is a style option on the existing dynamic image builder. Public pricing pages still list 4×6, 6×9, and 6×11 postcards.
Can the pictured house be different from the mailing address?
Yes. Thanks.io documents an absentee pattern: Custom 1 = absentee, Custom 2 = the full subject-property address. Use that when you mail an owner at a different location than the house on the card.
Should a restoration company cartoonify every job-site house?
No. Keep raw or unused imagery for anything that has to look like a file. Use the effect on thank-you and neighborhood mail after the job, not on notices that travel with a claim.
Where is the official documentation?
Start with How To Create A Dynamic Postcard Template. The September 5 feature note itself arrived as a product email from Thanks.io, not as a new help-center article at the time this page was written.
The magazine piece tells the facility manager why the gap exists. This is the shop version. Same week. Different door.
A water job ends when the last air mover comes off the truck, not when the invoice hits QuickBooks. After that, the only carbon record most shops have is a line item and a memory. The FM who hired you will get asked for Category 1 and Category 5 numbers. They will call you. You will not have them.
What actually has to leave with the crew
Not a sustainability essay. A dozen fields, written while the floor is still wet:
If a tech cannot fill it in five minutes, the form is wrong. If it waits for the office on Monday, it will be invented.
Put it on the invoice trigger
Nobody fills a questionnaire after the trucks have gone. They fill what stands between them and getting paid.
One clause in the work auth or the master: the per-job record is a condition of final invoice. Same shape as a moisture log. Same habit as photos. The Restoration Carbon Protocol is the open mapping if you do not want to invent the buckets. Use it, rename it, or steal the twelve fields. The standard is not the point. The timestamp is.
Who this is for
Commercial water, fire, mold, and the one-off mechanical swap. The FM inside the building is the only person who can demand the data at the door. You are the only person who can produce it at the job.
IFMA just ran the occupier-side argument. Closing the Scope 3 Data Gap is theirs. This is the field note that makes that article usable when the next pipe opens.
The sentence that pays
“We capture the job record before we leave. You can hand it to whoever asks.”
Open field playbook. No patent. Copy it, rename it, change the nouns to fire / mold / rebuild. If it makes you money, good. If it puts another dish on a wet roof, also good.
License: do what you want. Attribution nice, not required. Tygart Media is not a Starlink, SpaceX, Tesla, or xAI partner. Links below go straight to them. No tracking parameters. No referral codes.
Why this exists: restoration work happens where fiber is dead, the house is a Faraday cage of wet drywall, and the phone that “has bars” cannot upload a moisture map. Starlink is a sky-view pipe. More honest job-site pipes → more honest traffic on the constellation → more reason to fly birds. The selfish clause is allowed: a 4G phone in the sticks should still talk to a voice agent when the street is dark.
Bars on the phone. Upload still dead. That is the job the dish is for.
Buy and read from the source. Prices move. The impedance rule does not.
The structure or the street has no working cable/fiber (storm, rural, construction, “the pole is in the river”).
You need to upload, not just talk: photos, video walkthrough, Xactimate sketch, moisture log, signed work auth.
You will be on site more than an hour and cell is congested or roaming into a dead pocket.
The office needs a second path so after-hours voice and dispatch do not die with the cable modem.
Do not use it as:
A replacement for a good office fiber drop.
A phone. Voice agents still ride the pipe; the dish is not Jarvis.
A “we have Starlink” line on the website. Homeowners hire the truck that showed up.
Cell first if it works. Starlink is the sink when cell is the bottleneck.
2. Two kits (steal one)
Kit A — truck / first-on-site (most shops)
Starlink Mini on a Roam plan or, if this is actually a business WAN, start at Business and read the current hardware list. Mini is the backpack dish. In-motion rules live here. The home V5 kit is not the roam toy.
Power: Mini wants a USB-PD source rated 65–100 W even though it only drinks ~25–40 W. A 45 W phone brick will lie to you. Truck: 12 V → 30 V / Anderson, or a 500 Wh class station.
Plan: numbers on starlink.com move. Roam is written for travel. If the kit is production, read Business vs Enterprise. Mini often does not sit on the Priority SLA. Do not tell a carrier you have enterprise uptime because you paid a business invoice for a Mini.
One cheap travel router if Mini Wi-Fi dies inside a metal trailer.
Power before the meter. 65–100 W brick. Phone chargers lie.
Standby the truck kit when it is not a weather week. Idle is cheaper than a second hardware buy because someone borrowed it.
6. Dispatch and voice
Dispatch and voice when the site is remote.
The dish is layer 0. The voice agent is layer 1.
On a dead-fiber job: photos go up the pipe; the after-hours line stays reachable; the agent writes a new row (address, standing water y/n, next action). It does not edit your website.
If you already have a process, add one rule: when cell upload fails, kit A comes off the hook.
7. Failure modes
Trees and eaves. Rain. 45 W bricks. Consumer Roam sold as production WAN. Twelve intake fields before anyone asks “can we come now?”
8. The sentence that pays the shop
“If the street internet is out we still upload your photos and get the adjuster pack off the truck tonight.”
Only say it if the kit is in the truck.
This document stays free. Charge for the hour you spend teaching another shop the first 30 minutes if you want. Do not charge Starlink. They already sold you the dish.
9. What this is not asking
No meeting. No partnership badge. No official anything.
Redmond already knows how to stamp birds. The ground should not be a graveyard of unused kits. Order here. Then put the dish where the sky is.
A restoration shop does not have a marketing problem as often as it has a pile. Quotes written and not booked. Supplements submitted and not approved. Calls that rang and became someone else’s water job.
That pile has an equation. It did not come from a CRM vendor. It came from a physics lab that cools a single charged atom until the atom almost stops moving.
How we got here
Red-detuned laser on a trapped ion — cooling kicks, noise puts a little heat back.
Saturday night started in curiosity, not a content calendar. Trapped calcium ion. Paul trap as a tiny harmonic box. Red-detuned laser hits harder when the ion runs toward the beam. Random fluorescence puts a little heat back. Floor is the Doppler limit — not zero.
Question: swap the ion for something else, does the math still answer?
Yes, if the new world still has a countable pile, a shrink rate (A−), and a grow-plus-noise rate (A+).
CERN did this without a laser (stochastic cooling, antiproton stack, W/Z, Nobel 1984). A shop does it every week and almost never writes the rates down.
The kit
The kit — what ships with the leftover pile.
Ladder: n = 0, 1, 2, …
Leftover:
n̄ = A+ / (A− − A+)
Equal rates → pile stays. A+ wins → pile runs. Pretend A+ is zero → you predicted a miracle.
Classically: leftover = noise / net cooling. Photons were a costume.
More map-pack clicks + voicemail after hours = blue-detune. That is “more leads, same jobs.”
Priors (measure the shop anyway)
Priors — measure the shop anyway.
Live answer books on the order of ~40% of real calls in home-service samples; voicemail callback ~11%. Miss rate often 25–50%. Almost nobody voicemails. Invoca 2026: ~52% reach a person; ~55% of shops never ask for the book. ~Half of contractors never follow the written estimate; three real touches recover ~a quarter of leftovers. Insurance: 2–5 supplements per residential file; skip the loop and leave ~10–30% unpaid.
Industry % are priors. The shop must count its own four columns.
The four-week test
Mondays: open quotes, new noise, honest closes — plot the leftover.
Mondays, one sheet:
n = open quotes
A+ = new quotes + missed calls that never became a row
A− = booked or killed on purpose
Plot n̄
Cadence: day-1 text, day-3 call, day-7 close-or-kill. If n̄ does not fall, follow-up is theater or miss rate is the heat.
Voice that texts back in a minute = kick. Voice that only writes a pretty card = thermometer.
Not this
Will not cool a brand. Will not set ad spend from a calcium line. Use on piles that shrink when kicked. Preferential attachment is a fire, not a trap.
You do not need another binder in the truck. You need the protocol answer while the carpet is still wet.
IICRC S500 is not mysterious. The failure mode is that the PM is standing in a basement and the binder is in the office. That is how a supplement dies in email.
Office owns jobs, fleet, claims, and certs. Van gets a work order. When the question is S500-shaped, ask Claude with a protocol-grounded skill — not a Facebook group.
That stack is the Complete Restoration Operations Kit — seven Notion templates plus the IICRC lookup skill. $97 on Square. No email to purchase.
Need only the lookup? Buy the skill. Need more than two pieces? The kit is cheaper.
Claude Managed Agents is the product. Slack, Notion, Jira, and Asana are just the interface. Anthropic is building the invisible execution layer that powers the next generation of enterprise software.
There is a pattern emerging in enterprise AI that most people are reading wrong. They see Anthropic launch Claude Tag in Slack and think “chatbot upgrade.” They see Claude show up inside Notion and think “productivity feature.” They see AI agents appear in Jira and Asana and think “automation plugin.”
They are missing the architecture underneath all of it.
Anthropic is not building a better chatbot. It is building the invisible agent runtime that sits beneath every collaboration tool your team already uses. The company’s Claude Managed Agents (CMA) platform — launched in public beta on April 8, 2026 — is the infrastructure layer that makes this possible. And the speed at which partners are embedding it tells you everything about where enterprise software is heading.
What Claude Managed Agents Actually Is
What Claude Managed Agents actually is — the runtime layer.
Claude Managed Agents is a set of composable APIs for building and deploying production AI agents on Anthropic’s cloud infrastructure. The service handles sandboxed code execution, session persistence, credential management, scoped permissions, and end-to-end tracing — all the operational complexity that previously kept agents stuck in proof-of-concept limbo.
The architecture rests on three primitives: the Agent (configuration and behavior), the Environment (sandboxed execution), and the Session (the event log that tracks everything the agent does). What makes this interesting architecturally is how Anthropic decoupled the “brain” from the “hands.” Claude’s reasoning runs on Anthropic’s own infrastructure while the code execution sandbox spins up independently — and in parallel. The brain starts reasoning immediately while the sandbox provisions, delivering roughly 60% faster time-to-first-token at the p50 level and over 90% faster at p95, according to Anthropic’s engineering team.
Pricing follows a transparent model: standard Claude API token rates plus $0.08 per session-hour of active runtime during the current beta period. Runtime is measured to the millisecond and only accrues while the agent is actively executing — idle time waiting for input or tool confirmations does not count.
For teams that need to keep execution inside their own perimeter, CMA supports self-hosted sandboxes through partners including Cloudflare, Daytona, Modal, and Vercel, or custom VPC deployments. MCP tunnels allow agents to connect to private Model Context Protocol servers inside your network without exposing them to the public internet. A Vaults system keeps credentials out of the sandbox entirely using envelope encryption. And a feature called Dreaming runs scheduled reviews of past sessions to curate agent memory — essentially letting agents learn from their own operational history.
The Embedded Layer: Where CMA Actually Lives
Embedded layer: where CMA actually lives in the stack.
The real story is not the infrastructure. It is where that infrastructure shows up. In the ten weeks since CMA launched, Anthropic has embedded its agent runtime inside the collaboration tools that enterprises already depend on. This is not a roadmap — these integrations are live or in active beta.
Slack: Claude Tag as Persistent Team Member
Claude Tag, launched June 23, 2026, replaces Anthropic’s original Claude in Slack integration with something fundamentally different. This is not a chatbot you summon with a slash command. It is a persistent AI team member that lives in your channels, builds memory across conversations, and can take initiative through what Anthropic calls “ambient mode” — proactively surfacing information, following up on forgotten threads, and keeping teams updated across the organization.
Claude Tag is multiplayer by design: one Claude identity per channel, accessible to everyone, with the ability to hand off half-finished tasks between team members. It runs on Claude Opus 4.8, Anthropic’s most capable model released May 28, 2026. And internally, Anthropic reports that Claude Tag is already approving and incorporating 65% of the code changes their product team submits. The existing Claude in Slack app will be retired on August 3, 2026. Claude Tag is available on Enterprise and Team plans.
Notion: Claude as External Agent
On May 13, 2026, Notion launched its Developer Platform version 3.5, which introduced the External Agents API. This API lets AI agents — including Claude — operate inside your Notion workspace as first-class participants. They can read pages, write to databases, create tasks, trigger automations, and be @-mentioned directly in documents. Claude operating through this API can chain actions together: read a project brief, check the task database for related work, draft a new document, and create a linked task entry — all in a single session, running on CMA infrastructure with full sandboxing.
Asana: AI Teammates
Asana built AI Teammates on CMA — agents that pick up assigned tasks inside projects, draft deliverables, and hand back outputs for human review. Specialist agents handle specific workflows: the Campaign Brief Writer turns scattered notes into structured briefs, the Workflow Optimizer identifies process gaps and builds automations, and the Compliance Specialist checks work against regulatory standards. Asana’s CTO said CMA let them ship these features “dramatically faster” than any prior approach to agent development.
Atlassian: Claude Agent for Jira
Atlassian released Claude Agent for Jira, built on CMA infrastructure, which lets teams assign work items directly to Claude from the Jira UI. The agent clones the repository, analyzes the codebase, implements changes on an independent branch, pushes the code, and opens a draft pull request — streaming real-time status updates back to the Jira work item throughout the process.
Sentry: From Bug Detection to Merge-Ready PR
Sentry’s existing AI debugging agent, Seer, already used Claude for root cause analysis. With CMA, Sentry extended the workflow from diagnosis to automated fixing — the agent takes Seer’s root cause output, generates a fix, opens a branch with the changes, and creates a pull request for developer review. Sentry processes over one million root cause analyses per year and provides near-immediate reviews on over 600,000 pull requests per month. The CMA integration was built by a single engineer in weeks, eliminating months of custom agent runtime development.
Rakuten: Specialist Agents Across the Enterprise
Rakuten deployed specialist agents across product, sales, marketing, and finance using CMA, with each agent deployed in approximately one week. Agents plug into Slack and Teams, letting employees assign tasks and receive deliverables including spreadsheets, slides, and applications. In the pilot, Rakuten reported a 97% drop in critical first-pass errors, with cost down more than 30% and latency reduced by 34%, without any loss in output quality.
KPMG: Global Professional Services Alliance
On May 19, 2026, KPMG and Anthropic announced a global alliance and launched “Digital Gateway Powered by Claude.” The partnership embeds Claude, Cowork, and CMA directly into KPMG’s client delivery platform, with an initial focus on tax and private equity clients. Building an AI agent for tax regulation workflows previously took weeks and required switching between multiple tools. With CMA integrated into Digital Gateway, KPMG says the same capability takes minutes. The alliance extends to KPMG’s 276,000-person global workforce.
The Strategic Pattern: Agent Runtime as a Service
Step back from the individual integrations and the strategic pattern becomes clear. Anthropic is not trying to own the interface. It is deliberately positioning CMA as the execution layer underneath interfaces that other companies own. Slack owns the messaging UI. Notion owns the workspace UI. Jira owns the project tracking UI. Anthropic owns the agent brain that powers all of them.
This is a fundamentally different strategy from its two largest competitors.
OpenAI chose vertical integration. When OpenAI launched Workspace Agents on April 22, 2026, it positioned ChatGPT itself as the central hub — a no-code successor to custom GPTs that connects to Slack, Salesforce, Google Drive, and Notion through plugins. Agents are created inside ChatGPT, accessed from ChatGPT, and managed through ChatGPT. OpenAI wants to own the surface area.
Google chose platform depth. At Google Cloud Next on April 22, 2026, Google unveiled the Gemini Enterprise Agent Platform — a reimagined evolution of Vertex AI — alongside Workspace Intelligence, a semantic unifying layer that connects data across Docs, Slides, Gmail, and the broader Google Cloud ecosystem. Google’s agent platform supports 200+ models including Claude, and the Agent2Agent (A2A) protocol enables distributed peer-to-peer agent communication. Google is leveraging its data moat and distribution at the platform level.
Anthropic chose tool-centric orchestration. Rather than owning the UI (OpenAI) or the platform (Google), Anthropic is embedding its agent runtime into every tool through composable APIs and the Model Context Protocol. The platform you use becomes irrelevant — whether it is Slack, Notion, Jira, Asana, or Sentry — because the agent brain running underneath is Claude on CMA.
This is the agent-as-a-service model. And it may be the most defensible position of the three, because it does not require users to change their behavior or migrate to a new platform. The agent shows up where they already work.
What the Numbers Say About Enterprise Agent Adoption
The macro context supports Anthropic’s timing. Gartner predicts that 40% of enterprise applications will include embedded task-specific agents by the end of 2026, up from less than 5% in 2025. McKinsey’s April 2026 analysis found that agentic AI can enable automation of 60 to 80 percent of routine infrastructure work over time, translating to a 20 to 40 percent run-rate cost reduction in initial deployments.
The gap between experimentation and production remains the defining challenge. Industry research compiled from major firms shows that nearly four in five enterprises have experimented with or deployed agents in some form, but fewer than one in nine are running them in production at a scale that generates measurable business value. For the agents that do reach production, the average return on investment is 171% — though 19% of deployments never reach payback at all.
That production gap is exactly what CMA is designed to close. The infrastructure burden — sandboxing, session persistence, credential isolation, error recovery, observability — is the bottleneck. Engineering teams routinely dedicated significant senior engineering resources for months before a single agent reached production. CMA eliminates that layer entirely, which is why partners like Asana, Sentry, and Rakuten report shipping production agents in days or weeks rather than quarters.
What This Means for Businesses Already Using These Tools
If your organization uses Slack, Notion, Jira, or Asana — and statistically, you use at least two of them — you are about to encounter Claude whether you planned to adopt it or not. This is not a technology decision your IT team is making. It is a feature that your existing vendors are shipping.
The practical implications are significant. Claude Tag in Slack means your team channels will have an AI participant that remembers past conversations, can be handed tasks asynchronously, and may proactively surface information. Claude in Notion means your project documentation, databases, and task boards can be read, analyzed, and acted upon by an agent that chains actions together. Claude Agent for Jira means development tickets can be assigned to an AI that clones your repo, writes code, and opens pull requests.
For agencies and service providers managing client work across multiple tools, the embedded agent layer changes the economics fundamentally. Work that previously required a human to context-switch between Slack, Notion, and a project management tool — reading a brief here, updating a task there, drafting a document somewhere else — can be handled by an agent that operates across all of them simultaneously. The coordination tax that consumes a substantial share of knowledge work time is the exact problem embedded agents are built to solve.
The companies that benefit most will be the ones that have clean operational systems — structured task boards, documented processes, well-organized project databases — because agents can only act on information they can read. Messy Notion workspaces and disorganized Jira boards will limit what agents can accomplish. Operational hygiene just became a competitive advantage.
What This Means for Solo Operators Already Running Agent Infrastructure
There is a specific audience that should be paying very close attention to CMA: the solo operators and small agency owners who have already built their own agent stacks from scratch. If you are running scheduled Claude tasks on a GCP Compute Engine VM, connecting to WordPress via REST API proxies, piping work orders through Notion, monitoring Gmail for client replies, and publishing content through MCP-connected pipelines — you have already built a version of what CMA is productizing.
The economics question is worth doing the math on. A lightweight GCP VM running 24/7 to host recurring agent tasks — news desk monitors, outreach reply checks, newsletter extraction, scheduled content audits — costs a fixed monthly rate whether the agents are actively working or sitting idle. CMA at $0.08 per session-hour of active runtime only charges when agents are executing. For tasks that run for a few minutes every few hours, the per-session billing model could be substantially cheaper than keeping a VM warm around the clock. A task that runs for ten minutes six times a day would cost roughly $0.08 per day on CMA, versus the cost of a VM instance that never sleeps.
But the migration path is not ready yet, and solo operators should understand exactly where the gaps are before making any infrastructure decisions.
The biggest gap is MCP tunnels. CMA’s ability to connect agents to private MCP servers inside your network is still in research preview — not production-ready. If your agent stack depends on a private WordPress REST API proxy, a Notion workspace connected via MCP, or any internal tool that is not exposed to the public internet, CMA cannot reach it today. The Vaults system for credential management is promising, but it does not solve the network connectivity problem for self-hosted infrastructure.
The second gap is orchestration control. Solo operators who have built their own agent infrastructure typically have precise control over scheduling, retry logic, error handling, and the exact sequence of tool calls. CMA’s Dreaming feature — which reviews past sessions to curate agent memory — is an interesting approach to agent learning, but it is not the same as having direct control over a cron job that fires at 6:00 AM, checks three data sources in a specific order, and writes results to a specific Notion database with a specific schema.
The thesis for solo operators is straightforward: CMA is almost certainly the future migration path for self-hosted agent infrastructure. The economics favor it for intermittent workloads, the managed security and sandboxing eliminate operational risk you are currently carrying yourself, and the session persistence model solves problems that custom agent runtimes handle poorly. But the plumbing — particularly MCP tunnels to private infrastructure — is not production-ready. Track it closely. Do not migrate yet. When MCP tunnels graduate from research preview to general availability, revisit the math and the connectivity story. That is the trigger point.
The Risk Nobody Is Talking About
The risk nobody talks about — agents that act with memory.
There is a tension in this model that deserves attention. When Claude operates as an invisible layer inside tools you already trust, the boundary between the tool’s native capabilities and the AI agent’s actions blurs. A Jira ticket that was “completed” might have been implemented by Claude, reviewed by a human for thirty seconds, and merged. A Notion project plan that looks thorough might have been generated by an agent that filled in the sections with plausible-sounding content.
The embedded model works precisely because it reduces friction — but reduced friction also means reduced scrutiny. Organizations adopting embedded agents need to build review processes that match the speed at which agents can produce output. The 171% average ROI from agent deployments accounts for the value created, but it does not account for the subtle quality risks of production work generated by systems that are confident, fluent, and occasionally wrong.
Anthropic has built guardrails into CMA — sandboxed execution, credential isolation, session logging — but the governance layer for reviewing agent output at enterprise scale is still largely unsolved. This is a space where internal operational discipline matters more than the technology itself.
Where This Goes Next
Claude Tag launched on Slack first. Anthropic has indicated plans for wider rollout beyond Slack. If the pattern holds, expect Claude Tag’s persistent team member model to appear in Microsoft Teams, Discord, and any other collaboration surface where teams coordinate work.
The CMA primitives are designed to be composable, which means the partner integration list will grow rapidly. Any SaaS company with an API and a workflow that involves reading context, making decisions, and taking actions is a candidate for CMA integration. Customer support platforms, CRM systems, design tools, analytics dashboards, HR systems — the addressable surface is essentially every tool that knowledge workers touch.
Gartner’s long-term projection estimates that agentic AI could drive approximately 30% of enterprise application software revenue by 2035, surpassing $450 billion. If Anthropic’s embedded strategy succeeds, a meaningful slice of that revenue flows through CMA as the underlying runtime — regardless of whose logo is on the interface.
The chatbot era is ending. The embedded agent era is starting. And Anthropic is betting that the company that owns the invisible execution layer wins the market, even if no end user ever sees its name.
Claude Managed Agents is a set of composable APIs launched by Anthropic on April 8, 2026 in public beta. CMA lets developers build and deploy production AI agents on Anthropic’s cloud infrastructure, handling sandboxed code execution, session persistence, credential management, and end-to-end tracing. The architecture separates the “brain” (Claude reasoning) from the “hands” (code execution sandbox), enabling parallel processing and faster agent responses.
How much do Claude Managed Agents cost?
During the current public beta, CMA pricing is standard Claude API token rates plus $0.08 per session-hour of active runtime. Runtime is measured to the millisecond and only accrues while the agent is actively executing — idle time does not count. GA pricing has not been finalized and may differ from the beta rate.
What is Claude Tag in Slack?
Claude Tag is Anthropic’s persistent AI team member for Slack, launched June 23, 2026. Unlike a traditional chatbot, Claude Tag lives in channels, builds memory across conversations, takes initiative through ambient mode, and works asynchronously. It is multiplayer — one Claude identity per channel that all team members interact with. Claude Tag runs on Claude Opus 4.8 and is available on Enterprise and Team plans. It replaces the original Claude in Slack app, which retires August 3, 2026.
Which tools have Claude Managed Agents embedded?
As of June 2026, CMA is embedded in Slack (via Claude Tag), Notion (via the External Agents API), Asana (AI Teammates), Atlassian Jira (Claude Agent for Jira), and Sentry (extending the Seer debugging agent). Enterprise deployments include Rakuten (specialist agents across product, sales, marketing, and finance) and KPMG (Digital Gateway Powered by Claude for tax and private equity clients).
How does Anthropic’s agent strategy differ from OpenAI and Google?
Anthropic uses a tool-centric orchestration approach, embedding its agent runtime inside existing tools via composable APIs and the Model Context Protocol (MCP). OpenAI chose vertical integration with Workspace Agents, positioning ChatGPT as the central hub. Google chose platform depth with the Gemini Enterprise Agent Platform and Workspace Intelligence semantic layer. Anthropic’s approach does not require users to change platforms — the agent shows up where they already work.
What percentage of enterprise apps will have embedded AI agents by end of 2026?
Gartner predicts that 40% of enterprise applications will include embedded task-specific agents by the end of 2026, up from less than 5% in 2025. However, fewer than one in nine enterprises currently run agents in production at scale, suggesting significant growth ahead.
Can Claude Managed Agents run inside a private network?
Yes. CMA supports self-hosted sandboxes through partners including Cloudflare, Daytona, Modal, and Vercel, or custom VPC deployments. MCP tunnels allow agents to connect to private Model Context Protocol servers inside your network without public exposure. A Vaults system keeps credentials out of the sandbox using envelope encryption.
The hardest org-chart decision in restoration is not who to hire. It is what order to hire them in. Get the sequence wrong and you spend money on a seat that doesn’t relieve the bottleneck — while the real constraint, almost always you, keeps strangling growth.
Most owners build their team reactively. A big loss comes in, they’re underwater, so they grab whoever is available — usually another tech. Six months later they have more trucks and the same problem: every job, every estimate, and every collections call still routes through the owner. They added capacity to the field and zero capacity to the bottleneck.
Here is the honest sequence — the one that actually pulls the owner out of the truck — mapped to the revenue milestones where each hire pays for itself.
First, Find Your Real Bottleneck (It’s Probably You)
Find the real bottleneck before you hire more techs.
Before you hire anyone, do the boring exercise. List every function the company performs — answer the phone, dispatch, scope the loss, write the estimate, run the crew, order equipment, invoice the TPA, chase payment, do payroll. Next to each one, write the name of who actually does it. Count how many times your own name appears. That number is your bottleneck, and the first hire should remove the most expensive, most repeatable item from your list — not the one you enjoy least.
The trap is hiring for relief instead of leverage. Hiring a third tech feels good because the trucks are full. But if you are still the only person who can scope a loss and write a winning estimate, those trucks just create more work that funnels back to you.
$0–$1M: You and a Lead Tech
At startup scale, the org chart is two boxes: you and a strong lead technician. You are the estimator, the PM, the dispatcher, and the collections department. That’s fine — and unavoidable — at this stage. The rule of thumb most operators use is roughly $150,000–$200,000 in annual revenue per field technician before adding the next one, because that’s the point where there is genuinely enough work to keep another body busy and billable.
The mistake here is hiring a second tech too early to look bigger than you are. Idle techs are the fastest way to torch a thin startup margin.
$1M–$2M: The First Office Hire — Not Another Tech
First office hire — not another tech — unlocks the owner.
This is the milestone where most owners hire wrong. They add a second or third tech when the seat that actually frees them is administrative. An office coordinator or office manager who owns scheduling, job-file documentation, TPA paperwork, and the collections follow-up is the single highest-leverage hire at this stage. Restoration office and administrative coordinator roles commonly run in the $45,000–$60,000 range depending on market, and that one seat can claw back ten to fifteen owner-hours a week — hours you can redirect into estimating and sales, which are the only two activities that grow revenue.
The math is simple. If you are personally billing $150-plus per estimating hour and you hand off twelve hours of admin a week to a $55,000 coordinator, the hire pays for itself almost immediately and converts owner time into top-line growth.
$2M–$3.5M: A Dedicated Estimator / Project Manager
Once admin is covered, the next thing chained to the owner is almost always scoping and estimating. This is the hardest seat to give up because it feels like the part only you can do — and at first, it is. But a $2M shop cannot scale on a single estimator who is also the CEO.
Hire a restoration estimator/PM who can scope a loss, write the Xactimate estimate, and manage the job to completion. Expect this to be one of your more expensive seats: restoration project manager and estimator compensation broadly lands in the $60,000–$90,000 range nationally, with experienced, supplement-savvy PMs commanding more in tight labor markets. Plan for a ramp — a new PM rarely writes estimates as tight as an experienced owner on day one, and supplement recovery may dip during the handoff before it recovers.
This is also where your tech stack starts to matter. If your estimating, job management, and TPA reporting all live in the owner’s head or a spreadsheet, the new PM can’t be effective. The hire and the system have to land together.
$3.5M–$5M: An Operations Manager and the Owner Comes Off the Truck
Ops manager stage: owner comes off the truck on purpose.
By this stage you should have a small bench: lead techs, an office manager, and at least one PM/estimator. The seat that defines a $5M shop is an operations manager — someone who is not you and, ideally, not a relative — who owns daily execution: dispatch, crew utilization, equipment, and job throughput. Restoration operations manager pay broadly runs from roughly $63,000 on the lower end to around $89,000-plus for experienced managers, depending heavily on market and revenue scale.
This is the hire that lets the business survive without the owner physically present. It is also the one that most directly changes what the company is worth. Restoration shops under about $2M tend to trade at roughly 2.8x–3.0x SDE, while companies that cross $5M with a diversified service mix and a real second layer of leadership command 4x–7x EBITDA. Buyers aren’t paying that premium for revenue — they’re paying for an operation that runs without the founder in the dispatch seat. The operations manager is what makes that true.
A Sanity Check on Labor Cost
As you build the team, keep the whole picture in view. Healthy restoration shops generally run blended gross margins in the 50–75% range depending on mix — water mitigation sits at the high end (roughly 70–80%) because equipment does much of the work, while reconstruction and fire work run leaner. Well-run operations keep total operating expense, excluding direct job cost, in the rough range of 40–55% of revenue. If a new hire pushes overhead past that band without a clear path to more billable throughput, you’ve hired ahead of your revenue — slow down and fill the pipeline before you fill the seat.
The Bottom Line
The order is admin, then estimator/PM, then operations manager — and only more techs as billable volume genuinely demands them. Hire to remove yourself from the bottleneck, not to make the trucks look full. The owners who hit $5M and sell at a 4x-plus multiple are not the ones who hired the most people fastest. They’re the ones who hired the right seat next, every time, until the day the business no longer needed them in the truck.
If you’re still running the whole company from the van, the Complete Restoration Operations Kit gives you the connected job tracker, equipment, claims, SOPs, KPIs, and crew tools that make those hires actually stick. Pair it with the Restoration Leadership Toolkit — Claude Edition when you’re ready to build the bench that lets you step out of the truck.
Water damage restoration keywords hit $250 per click in competitive markets. Fire restoration, mold remediation, biohazard cleanup – they’re not far behind. If you’re running Google Ads with a dumped-together campaign and hoping the phone rings, you are subsidizing your competitors’ retirement.
The restoration owners who actually make PPC work aren’t necessarily spending more. They’re spending smarter. This is what their campaigns look like – and where the common setups fall apart.
The Single-Campaign Trap
The single-campaign trap is where the bleed usually starts.
The most common setup I see: one campaign, one ad group, a mix of water damage, mold removal, fire restoration, and flood cleanup keywords all fighting each other. Every click gets the same generic ad. Every ad points to the homepage.
Here’s why that’s expensive. Google’s Quality Score – which directly sets your cost per click – is built on three signals: expected click-through rate, ad relevance, and landing page experience. When you stuff water damage and fire restoration into the same ad group, your ad relevance tanks for both. A restoration company with a Quality Score of 9 can outrank a competitor bidding twice as much with a Quality Score of 5. Poor structure can inflate your CPC by 30% or more while delivering fewer qualified leads.
The fix is not complicated, but it requires discipline:
Campaign 1 – Emergency Water Damage: Ad groups for emergency water extraction, burst pipe, basement flooding, sewage backup. Separate ad copy for each. Landing page that opens with emergency water damage, not your homepage.
Campaign 2 – Fire and Smoke Restoration: Fire damage, smoke damage, soot removal. Different calls-to-action – fire jobs are longer projects, different sales conversation.
Campaign 3 – Mold Remediation: Mold testing, black mold removal, mold inspection. This is often a separate buyer with a different timeline.
Each ad group should have 10-20 tightly related keywords. Every keyword in the group needs to logically fit the same ad and the same landing page. If they don’t, split them.
What CPCs Actually Look Like in 2025-2026
Emergency restoration keywords in competitive metros – Atlanta, Dallas, Phoenix, Miami – routinely hit $80-$150 per click. Premium terms like “emergency water damage restoration” have been reported as high as $250 per click in certain markets.
At those CPCs, your cost per lead depends almost entirely on your landing page conversion rate. A page converting at 8% on a $100 CPC keyword produces a $1,250 cost per lead. Tighten that to 15% conversion and you’re at $667 per lead. On a $15,000 water damage job, either number can work – if you close it. On a $3,500 mold job, you need to be much more careful about which keywords you’re running.
Average lead costs by channel, for context:
Google LSA (Local Services Ads): $100-$200 per verified lead in most markets
Google PPC (traditional Search Ads): $200-$400 per qualified lead when structured properly; $400-$700+ when not
Organic SEO (year 3+): Under $25 per lead once content and authority are built
This is not a case against PPC. It’s a case for understanding what you’re buying. LSA leads are cheaper but lower volume and dependent on Google’s automated credit system. PPC gives you scale and control – but the control only works if your campaigns are set up to exercise it.
Negative Keywords: The Bill You’re Not Seeing
Negatives are the bill you are not seeing.
Most restoration PPC campaigns have weak or nonexistent negative keyword lists. Every day your campaign runs without them, you’re paying for clicks from job seekers searching “water damage restoration jobs near me,” DIY researchers searching “how to do water damage restoration yourself,” students searching for training programs, and equipment renters who aren’t calling you for service.
Campaigns that actively manage their negative keyword list see 10-20% lower wasted spend and 5-15% improvement in conversion rate. On a $10,000/month ad budget, that’s $1,000-$2,000 per month currently going to irrelevant clicks.
Build your seed negative list before the campaign launches. Pull your Search Terms Report weekly for the first 60 days. Add exact match negatives first; only go broader if the data supports it. Over-blocking with broad match negatives will starve your campaign of volume you actually want.
Bidding Strategy: Stop Fighting the Machine
78% of Google Ads spend now runs through Smart Bidding – Target CPA, Target ROAS, Maximize Conversions. Advertisers using AI bidding report roughly 22% lower cost per conversion compared to manual CPC on average.
For restoration companies, the right bidding strategy depends on your data:
Under 30 conversions per month in a campaign: Use Maximize Clicks with a CPC cap while you accumulate data. Smart Bidding needs signal to work; starving it on a new campaign produces garbage results.
30+ conversions per month: Move to Target CPA. Set your target based on actual job margins, not aspirational ones. If a water damage job averages $12,000 and you close 25% of qualified leads, you can afford a $300 CPL target and still profit. If you’re closing less than 15%, fix your sales process before you fix your bidding.
Large campaigns with consistent job data: Target ROAS becomes viable, but you need accurate revenue tracking wired into Google Ads – something most restoration companies don’t have configured properly.
A qualified water damage lead that converts to a full job is a 14x-100x return on ad spend. The problem is rarely the channel – it’s losing track of where the leads went after the phone call.
The Landing Page Problem Nobody Talks About
Landing mismatch kills intent you already paid for.
You’ve fixed the campaign structure, added negatives, set a Target CPA. Your CPC is still $90. You’re still not closing leads.
Check your landing page. If your ad says “Emergency Basement Flooding – 24/7 Response” and your landing page is your homepage with a hero image of a happy family and a form below the fold, you’re burning the top-of-funnel work you just paid for.
A restoration PPC landing page needs: the emergency service name in the H1 above the fold, a click-to-call phone number prominent on mobile, a response time claim if you can back it up, one short form (name, phone, zip, issue), and proof elements – reviews, IICRC certification, insurance logos.
Do not send PPC traffic to your homepage. Do not build one landing page for all services. Match the ad to the page, the page to the ad group, the ad group to the keyword cluster. That chain is where Quality Score lives.
Budget Sizing for Competitive Markets
Ballpark monthly budgets to be competitive on emergency restoration keywords:
Mid-size market (pop. 200K-500K): $3,000-$6,000/month to generate 15-30 leads
Major metro (pop. 1M+): $8,000-$15,000/month to maintain consistent visibility
Specific suburb or tight service area: $1,500-$3,000/month if geo-targeting is tight and Quality Score is managed
These are Search campaign figures only. If you’re also running Performance Max, give it a separate campaign and separate budget so you can see what your Search investment is actually doing. PMax’s black-box reporting will otherwise obscure whether Search is working.
Bottom Line
Google Ads works for restoration companies that treat it as an engineering problem, not a set-it-and-forget-it expense. The contractors winning on PPC have siloed campaigns by service, loaded negatives before launch, let Smart Bidding mature on real conversion data, and matched every landing page to its ad group.
The ones losing money are running one campaign, one ad group, a hundred keywords, and pointing everything at a homepage built by someone who has never answered a restoration emergency call.
If your current PPC agency can’t show you separate service campaigns, a negative keyword list with at least 50 entries, and a dedicated landing page for each major service – find one that can. At $100+ per click, the cost of a weak setup compounds fast.
If you work insurance program work, this is the one report you should actually read. Every year, the Restoration Industry Association’s Advocacy and Governmental Affairs committee surveys contractors who have worked with TPAs in the past 12 months. No vendor marketing. No TPA spin. Just anonymous contractor ratings across 8 categories that actually matter: value, claims process, contractor support, scoring clarity, guidelines, credentialing, claim volume, and geographic coverage.
The 2025 results are in. 379 contractors rated 13 TPAs. The industry average sits at 2.7 out of 5 — a 54% satisfaction rate. That’s not a ringing endorsement of the TPA model, but it tells you something more useful: the spread between programs is significant, and knowing who’s at the top and who’s at the bottom changes your program strategy.
Here’s the breakdown, with the data that matters.
The Leaderboard: Who Contractors Actually Trust
Score TPAs on what contractors feel — not the brochure.
ONCORE Claims Network: 3.1 stars — #1 for the third consecutive year. This is the benchmark. ONCORE (formerly CORE) outperforms everyone across nearly every category: 3.4 on credentialing (the highest of any TPA), 3.3 on guidelines, 3.2 on value, and 3.0 on contractor support — the only TPA to crack 3.0 in that category. Claim volume is their soft spot at 2.7, which contractors consistently flag: the program is good, but there aren’t enough jobs to go around. If you can get in and get volume, this is the cleanest program to run.
Lionsbridge: 3.0 stars. Tied with Sedgwick for second and rising. Lionsbridge improved 3% since 2022 and scores well on guidelines (3.1) and claims process (3.1). It operates as a CCA Global Partners cooperative — meaning members get access to significant group buying power on equipment, credit card processing, and supplies in addition to leads. The program is selective and built for established contractors. Their claim volume score of 2.4 is the weak link, but the jobs they do send tend to be cleaner to close.
Sedgwick: 3.0 stars. The highest geographic coverage of any TPA at 3.2, tied with Alacrity and Contractor Connection. Sedgwick is a large TPA that manages claims for major commercial carriers. Their value score improved from 2022 and holds at 3.2. Contractor support fell slightly to 2.8, which is still above average. Sedgwick’s biggest contractor complaint: they want better advocacy with carriers when scope disputes arise (34% of contractors flagged this as their top improvement priority).
The Middle of the Pack
Westhill Global: 2.9 stars (+27% from 2022). The biggest mover in the 2025 report. Westhill climbed from 2.3 to 2.9, the largest percentage gain of any TPA. They earned the highest credentialing score in that category at 3.2, and their value rating jumped from 2.0 to 3.0. What drove it? Contractors report that Westhill made meaningful process improvements and the program became easier to actually manage. Watch this one — if the trajectory continues, they’ll be in the top tier in 2027.
Preferred Repair Network (PRN) / Hancock Group: 2.9 stars (down from 3.5 in 2022). The biggest drop in the report. PRN was the top-rated TPA in 2022. Two years later they’ve fallen 17% across all categories — contractor support cratered from 3.5 to 2.7. The program score fell sharply (from 3.5 to 3.0), guidelines dropped, and claim volume expectations are down 23%. Contractors aren’t abandoning the program — the claim volume and geographic scores are still reasonable — but something changed in how the program is managed. If you’re heavily weighted in PRN, the trend line warrants attention.
Direct Claims Management Group (DCMG): 2.8 stars (+12% from 2022). DCMG improved across the board and earned the highest scoring clarity rating (3.1) and tied for the top value rating. Their communication scores are better than average, and they’re rated best-in-class for not requiring contractors to take estimate-only projects. Smaller program footprint, but if you’re in their coverage area, worth evaluating.
Alacrity Solutions/Alacrity Nexxus: 2.7 stars (down 4%). The largest program by claim volume alongside Contractor Connection — and that volume score (2.7) is their strongest asset. Contractors use Alacrity for the jobs, not the relationship. The program scored 2.3 on contractor support, the second lowest of any TPA. Key contractor complaints: 38% want better advocacy with carriers, 34% want overhead and profit addressed, 33% want more flexibility in guidelines. Alacrity knows this and has invested in contractor relations improvements (rebranding from the original Altimeter structure), but the needle hasn’t moved enough to show in the scores yet.
The Programs That Are Losing Contractor Confidence
Programs losing confidence usually lose it in the scope fight.
Brightserv: 2.6 stars (flat). No change from 2022. Contractors score timely payment as a weak point (29% flag it), and contractor support (2.3) needs work. The program hasn’t gotten worse, but in a field where others are improving, flat is a problem.
HOMEE: 2.6 stars (new to 2025 survey). Debuted slightly below average with a concerning claim volume score of 1.8 — the lowest of any TPA. Contractor support is at 2.6, and 46% of contractors rate “improve partnership with TPA” as their top request. As a tech-forward TPA operating in the gig-economy model, HOMEE is a different kind of program — useful for certain contractors but not a primary revenue source for established restoration companies.
Contractor Connection (Crawford): 2.6 stars. The most widely used TPA in the restoration industry — 289 contractor responses, the largest sample in the survey. Geographic coverage ties for highest (3.2), claim volume ties for highest (2.7), and they’re among the best for timely payment (only 8% of contractors flag slow payment, one of the lowest rates). The problem is everything else. Contractor support sits at 2.2 — second lowest. Contractor advocacy with carriers is the top complaint at 42%. Guidelines flexibility is flagged by 39% of contractors. They send the most work. They’re also the most frustrating to work with. The calculation you have to make: is the volume worth the margin compression and administrative friction?
Accuserve (formerly CodeBlue): 2.1 stars — last place. The lowest-rated TPA in the 2025 report, and it’s not close. Accuserve scores below 2.0 on value (1.9), scoring clarity (1.9), claims process (1.9), and contractor support (1.9). The only category where they score above 2.5 is credentialing (2.6). Fifty percent of contractors working with Accuserve say providing pricing consistent with market value is their top requested improvement — double the industry average. This program has structural problems that go beyond management tweaks.
What the Numbers Actually Tell You
The overall industry average of 2.7 out of 5 means most contractors are running TPA work that’s tolerated, not preferred. The five most important things contractors want from TPAs — in order of importance they rated themselves: claims process efficiency (4.4/5 importance), contractor support/advocacy (4.2), claim volume (4.2), value/ROI (4.2), and guidelines flexibility (4.1). On every single one of those, TPAs are delivering somewhere between 2.3 and 2.9. There’s a consistent gap between what contractors need and what they’re getting.
The other number worth noting: 53% of restoration firms now report zero TPA revenue, up from 45% the prior year. That’s not a blip — it’s a structural shift. Contractors who built their own lead channels through Google LSA, direct plumber and agent referrals, and organic SEO are generating work at better margins without the administrative overhead. The TPA model still works, but fewer operators are treating it as their primary revenue strategy.
How to Build Your TPA Program Intelligently
Build your TPA mix like a checklist — not a hope.
The operators who do TPA work profitably aren’t in every program — they’re in two or three that fit their capacity, their geographic footprint, and their operational model. Here’s the framework:
Use the RIA scorecard as a filter, not a verdict. A 3.1 from ONCORE doesn’t mean the program works in your market — claim volume (2.7) is the constraint. A 2.6 from Contractor Connection doesn’t mean you walk away from the largest volume source in the country. But it does mean you know where the friction is going to come from before you budget for it.
Cap TPA revenue at 40-50% of total revenue. The moment more than half your revenue runs through a program, the TPA controls your business. They can change pricing, add administrative requirements, or reduce your zip code coverage — and you have no leverage. Keep direct work as your floor, TPA work as your upside.
Track margin per TPA, not aggregate TPA margin. The programs that send the most work aren’t always the ones generating the most gross profit. A company doing $800K in Contractor Connection work at 28% gross margin is generating less than a company doing $300K in ONCORE work at 44% gross margin. Build a simple spreadsheet that tracks average gross margin per job by program. You’ll know within 90 days which programs deserve more of your capacity.
Document your TPA scorecard complaints. The RIA survey directly affects how TPA programs are managed — TPA executives receive this data and respond to it. If you’re running program work and experiencing consistent friction with a specific TPA, log it and participate in the next RIA survey. That’s not altruism. That’s how contractors collectively move the needle on program terms.
The Bottom Line
If you’re choosing between TPA programs in 2025, the data is clear: ONCORE leads, Lionsbridge and Sedgwick are solid programs for contractors who qualify, and Westhill Global is the most improved. Contractor Connection sends the most work but has the worst contractor support score. Accuserve has structural problems that pricing alone won’t fix.
Don’t build your business on programs. Build your business on direct marketing, strong referral relationships, and operational capability — then let TPA work be the fill you take when capacity allows. The contractors who get that order right keep their margins. The ones who get it backwards spend their careers negotiating scope with adjusters they’ll never win against.
Source: RIA 2025 TPA Scorecard Report, Restoration Industry Association Advocacy and Government Affairs Committee. Survey conducted anonymously among 379 restoration contractors.
Most restoration owners get the second-location itch around $3M. The honest answer is they shouldn’t scratch it until $5M — and even then, only if a specific list of things is already true inside the first shop.
Opening a branch is one of those decisions that looks like growth on the surface and turns into the slow bleed underneath. The mistake is almost never the second location itself. The mistake is the first location wasn’t ready to be left alone yet, and the owner went from running one healthy business to running two broken ones.
Here’s the honest framework. Not the cheerleader version.
Why $5M Is the Real Threshold (Not $3M)
Industry valuation data makes this concrete: restoration shops under $2M trade at roughly 2.8x–3.0x SDE. Once you cross $5M with a diversified service mix, multiples jump to 4x–7x EBITDA. That gap is not just about revenue — it reflects what buyers see in the operation. A $5M shop has a real second layer of leadership. A $3M shop almost always doesn’t.
When you open a second location from a $3M base, you are usually taking the only person who knows how to run the business — you — and splitting yourself in half. The first location’s gross margin starts compressing within ninety days. The new location burns cash for twelve to eighteen months before it stabilizes. Now you have two locations that both need you and neither one is the business it used to be.
At $5M, you typically have an operations manager, a production manager, a dedicated estimator or project manager bench, and recurring TPA volume that doesn’t depend on the owner answering the phone. That is the difference. The threshold isn’t a dollar figure — it’s whether the first location can run a full week without you in the building.
The Five Things That Have to Be True Before You Open
Five things have to be true before you open.
1. The first location can survive 30 days without you. Not “the work gets done.” That you can be unreachable for a month and the financials, the TPA scorecards, and the production schedule all stay inside normal range. If you can’t do that, you don’t have a second-location problem. You have a delegation problem at the first one, and adding geography won’t fix it.
2. You have an operations manager who is not you and is not a relative. Family members can run a second location, but only if they were already running a P&L inside the first one. The second-location playbook is the operations manager playbook. If you don’t have someone who can hold gross margin, manage WIP, and run a weekly production meeting without you in the room, the branch will not work.
3. The new market has documented demand, not a feeling. Pull the data before you sign a lease. Carrier referrals you’re already turning down in the target market. TPA territory gaps your existing programs have flagged. Search volume for “water damage restoration [city]” and the CPC on it. If the only reason you’re picking the market is that your cousin lives there or you saw a competitor’s truck, you don’t have a market — you have a hunch.
4. The first location is throwing off enough cash to fund 18 months of branch burn. A new restoration location typically loses money for twelve to eighteen months. Plan for the long end. SBA expansion loans usually want a 1.25 DSCR before they’ll touch it, which means your existing operation has to be healthy enough to service the new debt while the branch is still in the red. If the math doesn’t work without the new location immediately producing, the math doesn’t work.
5. Your tech stack scales without bolt-ons. If your job management software, Xactimate workflow, and TPA portal logins are all stitched together by tribal knowledge inside the first office, the second location will not run the same playbook. It will run a worse one. The system has to be portable before the branch opens, not after.
What Most Owners Get Wrong
Most owners get people depth wrong — not the lease math.
The most common second-location failure pattern goes like this. Owner hits $3.5M. Owner is tired, ambitious, and has an opportunity — a competitor closing down, a key employee asking for an ownership path, a city forty-five minutes away that “doesn’t have anyone good.” Owner signs a lease, hires a production lead, and tells himself the branch will be self-sufficient by month six.
Month six arrives. The branch is at 40% of projected revenue. The original location’s gross margin has slipped four points because the best production manager got moved to the new branch and the bench underneath wasn’t ready. The owner is driving between two offices three days a week. Cash is tight. The owner doubles down — hires another person, runs a Google Ads campaign in the new market, increases the burn — and by month eighteen the branch is either limping or being quietly wound down.
This isn’t a hypothetical. It is the most common growth-stage failure in the industry, and it happens because the second location was opened as a revenue bet when it should have been opened as an operational bet.
The owners who successfully open second locations almost always share three traits. First, they spent eighteen to twenty-four months building the leadership bench inside the first location before they ever talked about a branch. Second, they entered the new market with a known revenue floor — either a TPA program that committed volume, a large commercial client base in the geography, or a key person from the new market with their own book. Third, they treated the first six months of the branch as an investment, not a revenue line. They didn’t expect the branch to carry itself. They expected to lose money buying market presence and learning the territory.
The phrase that separates the two camps is simple. Failed openings start with “we need to grow.” Successful openings start with “we have the team and the demand to grow.”
The Bottom Line
If you’re under $5M and you don’t have a real operations bench, do not open a second location. Spend the next twelve months building the bench, hardening the tech stack, and proving the first location can run without you. The valuation gap between a clean $5M single location and a $7M two-location operation where both are slightly broken is enormous — and it almost always favors the clean single.
The second location is a multiplier. It multiplies whatever is true about the first one. If the first one is humming, you’ll build something worth selling for 5x EBITDA. If the first one is fragile, you’ll build two fragile ones and discover that the buyers paying premium multiples will pass on both.
Build the bench. Document the playbook. Hit $5M with the owner out of the truck. Then open the second.
