Intersection Strategies LLC operates at the crossing point of three domains that rarely share the same person, let alone the same firm. Collision industry knowledge — learned directly inside CCC Intelligent Solutions and forged at the service drive of the family's Mercedes-Benz dealerships. Enterprise go-to-market experience — how large consulting engagements actually get scoped, sold, and delivered to sophisticated buyers. Frontier AI orchestration — a self-taught mastery of Claude, Claude Code, Routines, and the thirty-plus MCP servers that now constitute the actual infrastructure of intelligent automation. The intersection of those three is where trigger-based collision agents become buildable. Everyone else sees a pain point. Intersection Strategies sees the exact API endpoint, the exact trigger condition, the exact regulatory frame, and the exact dollar the shop is currently leaving on the adjuster's desk.
One operator. Full accountability. No agency overhead, no white-label reseller, no distant product team. The person who configures your Routines is the same person who sells the contract, monitors the outputs, and writes the monthly ROI report.
James spent his formative professional years inside CCC Intelligent Solutions — the company whose ONE platform serves 28,000+ collision shops and sits at the center of every pain point documented in this briefing. Working on go-to-market strategy and internal solutions consulting meant living inside the adjuster-shop-estimating triangle from the vendor side. The insurer bias of the platform, the gaps in the MOTOR P-Page data, the supplement friction between carriers and shops — none of it is academic. It was the daily subject matter.
Growing up inside family-owned Mercedes-Benz dealership operations added the service-department counterbalance: how the technician actually works, what a legitimate teardown looks like, what it costs to sit on a compromised EV battery in a quarantine bay, and what a missed calibration does to a customer's drive home. The combination of dealer-service perspective and CCC-vendor perspective is uncommon. It means every agent in this stack was designed from both sides of the estimate at once.
SullivanCotter's compensation and workforce consulting practice is a serious training ground for how complex engagements get structured. The discovery call, the data-sharing agreement, the monthly ROI report format, the scope-control conversation — these are not startup improvisations. They are consulting primitives adapted to the collision repair vertical. A finance degree from Miami University (Ohio) put the unit economics discipline underneath.
The last two years have been a zero-to-orchestrator sprint. A non-technical professional, working almost exclusively via voice and plain English, learning Claude, Claude Code, Codex, NotebookLM, and the frontier of MCP tooling. Thirty-plus MCP servers live and integrated. Multi-agent workflows shipped. Real deliverables in clients' hands. The transformation is the product — James is the proof of exactly the capability shift he is now productizing for collision operators.
A professional hockey background sits underneath all of it. Not as résumé decoration — as operating cadence. Competitive discipline. Early mornings. The bias toward doing the work over explaining the work. When a shop signs the MSA, the person on the other end treats the engagement like a season, not a contract.
Trigger-based collision agents could not have been built eighteen months ago. The infrastructure did not exist at the right level of the stack. In 2026, every precondition is now in place — and the window to be the default shop-side layer on top of CCC is open but not permanent.
The AI model is the commodity. The trigger is the product. Whoever owns the trigger layer closest to the collision shop's daily pain owns the next decade of operating leverage in collision repair.— Intersection Strategies, April 2026
Anthropic's Claude Code Routines capability — productionized in 2026 — is the piece that was missing. Durable, long-running, cloud-hosted triggers that can authenticate, reason, take action, and hand back to a human without a local server or a custom platform. Before Routines, every one of these agents required a bespoke SaaS wrapper. Now, they are configuration.
CCC Secure Share publishes CIECA BMS JSON/XML endpoints. Mitchell RepairCenter exposes OData REST APIs. Audatex Qapter ships a full OAS3 Swagger surface. Enterprise ARMS and Hertz HIRS operate mature web portals with predictable DOM structures. The integration substrate is mature — what has been missing is a trigger-based orchestrator sitting above it with industry-native intelligence.
CCC ONE is indispensable to 28,000+ shops. It is also fundamentally insurer-biased — its scorecards, its labor times, its MOTOR exclusions all serve the carrier's severity management. Shops are frustrated, not rebellious. A shop-friendly agent layer that sits on top of CCC — enhancing rather than replacing it — is the cleanest possible wedge. It does not require the shop to switch anything. It just makes their existing CCC workflow win more arguments.
Every collision operator who considers this engagement will ask the same reasonable question: can this person actually produce the deliverables? The answer lives in public. Intersection Strategies ships briefing hubs like this one for vertical after vertical — each one a deployable reference document, each one a demonstration of the same capability stack.
A full briefing hub for commercial insurance brokers: market analysis, tool catalog, workflow automations, ROI framework, and engagement roadmap. Same architecture. Same editorial standard. Different vertical. Published publicly as a demonstration of the Intersection Strategies delivery pattern.
The Broker hub is one of several vertical deliverables in production. Each validates the same pattern: deep research, specific pain-point mapping, buildable agent catalog, transparent pricing, and publication-grade presentation. The collision version you are reading now is engineered to the same standard.
Principles are usually filler. These are not — they are the actual rules that govern how Intersection Strategies decides what to build, what to ship, what to charge, and what to refuse. Every deliverable passes through them.
Every initiative is tested against a single question: does this help close a beta, sharpen proof, or improve cash trajectory? Work that cannot answer yes is deferred, not pursued.
Working and sent beats elegant and internal. The first ROI report out of Agent 04 is more valuable than an unreleased version with a prettier chart. Polish is layered on after the capture is real.
Fewest moving parts that do the job. Every trigger, every integration, every handoff is engineered for the smallest possible surface area. Complexity is a liability priced in downtime.
The value of a Routine is not in the cleverness of the prompt — it is in the quality of the context loaded into the trigger. P-Pages, DEG rulings, OEM procedures, DRP contract terms, state appraisal statutes. Context is the moat.
Briefing hubs, deployable agents, working integrations — the artifact carries the argument. Intersection Strategies does not sell with pitch decks; it sells with the thing itself.
The final filter on every deliverable. Would I put this in front of a veteran shop operator, a CCC product lead, or an MSO acquirer without flinching? If no, it is not done.
Direct line to the builder. No intake form, no BDR queue, no round-robin routing. One person answers, and the same person runs the engagement.
Thirty minutes to confirm the shop's SMS, DRP mix, and biggest daily friction. No pitch deck. At the end of the call, the flagship agent is selected and the pilot path is defined — or we discover it is not a fit, and we both save an afternoon.