Robert Stanley spent 12 years running a digital marketing firm for lawyers. Then he watched AI eat the work. Instead of competing, he pivoted with his business partner Darin Swayne. Iron Noodle is a tech consultancy that embeds inside law firms for 9-day engagements, finds the broken processes, and builds the automation to fix them.
What the engagements look like
Robert, Darin, and their team fly in and live inside a firm for 9 days. They eat lunch with the managing partners. They sit with the paralegals. The problems that surface in person don’t match what shows up on a discovery call: a receptionist toggling between four tabs to check a client’s billing status, an associate re-keying case data from Clio into a spreadsheet that feeds a report nobody reads.
The typical law firm sweet spot for Iron Noodle is one under $15–20M in revenue that runs on multiple systems: Clio for case management, separate billing software, Google Workspace or Microsoft 365, intake forms, marketing tools, and spreadsheets that stitch it all together. Most of these systems don’t talk to each other. When they do, the connection is a person copying and pasting.
Where Zapier fits
Before Zapier MCP, connecting multiple systems meant building custom integrations or waiting for a pre-built trigger that matched the exact workflow. For a 9-day engagement, that timeline doesn’t work.
With Zapier MCP, the team sets up a separate MCP server for each client within a Zapier team account. Each server gets scoped access to that firm’s tools: Clio, their billing platform, and their email. The AI layer can query all of them without anyone handing over global API keys or looping in an IT team that may not exist.
During the engagement itself, Iron Noodle stands up a working data dashboard pulling KPIs from systems the firm is still consolidating. The dashboard runs while the backend cleanup happens in parallel. Clients see results before the consultants leave. And because law firms handle privileged client data, the per-server permissions matter. The team can grant tool access and revoke it in one click. No lingering API keys, no broad OAuth scopes.
Why law firms
Robert and Darin chose the legal industry because it adopts slowly and runs a consistent tech stack. A solution built for one firm can be transferred to the next with minimal rework. Clio is pervasive. The pain points repeat. The model scales because the problems are the same; the firms just haven’t solved them yet.
Robert’s previous life was VP-level tech and IT security at Fortune 500 companies, including Wells Fargo. Darin arrived from the other side of the table — he grew up in a family of lawyers and has spent more than 25 years building applications and automation for legal practices. The shift to small law firms was deliberate: fewer committees, faster decisions, and clients who notice when something starts working on day three.
What MCP unlocks for the model
Before MCP, a 9-day consulting engagement could diagnose a firm’s problems but couldn’t ship working systems before the team left. The integration work took longer than the engagement. Now Iron Noodle delivers a live dashboard, scoped data access, and working automation inside the same window. The firm isn’t waiting on a follow-up project to see results.
That changes the economics of the whole consultancy. Each engagement is self-contained. The tech stack repeats across firms. And MCP’s per-server architecture means Robert and Darin can spin up a new client environment in minutes, not days.
What one of those automations looks like
One of Iron Noodle’s go-to builds is a real-time KPI dashboard that flags urgent client calls. The system pulls call transcripts, scans for actionable keywords that signal an upset or time-sensitive caller, and matches that call to the full contact record in Clio. By the time the support team calls back, they already know the client’s open matters, billing status, and what triggered the call. No tab-switching, no “let me look that up.”
The pattern is straightforward: connect your phone system and Clio via Zapier MCP, use an LLM to classify transcript urgency, and push the prioritized callback list to Slack or email. If your firm runs Clio, you can replicate this setup in an afternoon.
Try the urgent caller triage
We generalized Iron Noodle’s workflow into an open-source Urgent Caller Triage skill in Zapier’s gtm-superpowers repo. Copy SKILL.md into your agent harness, follow SETUP.md for your stack, and adapt the keyword patterns to your practice areas.
The pattern
Input: Call transcript from your phone system
Step 1 (MCP): Pull the transcript and match the caller to a contact record in Clio
Step 2 (AI): Classify urgency — Critical, Urgent, or Standard — based on keyword signals in the transcript
Step 3 (MCP): Enrich with open matters, billing status, assigned attorney, and recent activity from Clio
Step 4 (Output): Prioritized callback list pushed to Slack, email, or a shared dashboard
This runs when new calls come in — the support team gets a ranked list with full context before they call anyone back.
Get started: Enable Zapier MCP, connect your phone system + Clio, then add your MCP server URL in Claude, Cursor, or any MCP-compatible agent. Or browse the MCP template library for a faster starting point.
At a glance: Urgent caller triage · Phone system + Clio + LLM · Zapier MCP · Built by Iron Noodle for law firms running Clio
Robert Stanley and Darin Swayne are the principals of Iron Noodle, an AI and automation consultancy for law firms.
