FirmOps.io
Law Firm AIUpdated August 28, 20268 min read

Live in Claude Cowork or ChatGPT, or get left behind

Staff must live in Claude Cowork or ChatGPT. A legal AI browser app leaves the firm behind. A firm brain (MCP) is how they stay there with the file.

J

Jonathan Mahler

Non-Attorney Partner & COO, Conduit Law

#Claude#ChatGPT#firm brain#MCP#legal AI

One workflow

Request demo

Bring one recurring bottleneck. If it is a good first firm-brain build, the next step is a live demo — not a pitch deck.

Lawyers and paralegals have to live in Claude Cowork or ChatGPT. If they do not, they are getting left behind.

Last updated: August 28, 2026

TL;DR

  • The home surface is Claude Cowork or ChatGPT, the frontier vendor workspace. Staff who leave it get left behind.
  • A legal AI startup puts the firm in a browser app. That firm will not compete, will not move as fast, and will not have software as good as Anthropic or OpenAI.
  • To stay in those workspaces with the firm's real files, you need a firm brain, also known as an MCP server, connected to Clio, mail, and docs.
  • Legal AI startups sit between the firm and the model, take margin, and serve a weaker model. That is the business.
  • This is not a remake of tool vs purpose-built partnership. That post already exists. This is the home-surface argument.
  • We dogfood. Conduit Law is the live PI-firm proof, not a slide deck. The people who built the brain already stay in Claude Cowork or ChatGPT with the stack connected.
  • Request demo if you want that layer mapped against one job on your stack.

Why do lawyers and paralegals have to live in Claude Cowork or ChatGPT?

Because that is where the frontier models and the frontier software live. A firm that works somewhere else is choosing to be slower on purpose.

Anthropic and OpenAI train the models. They also ship the workspace those models live in: Claude Cowork, ChatGPT work. Staff who stay there get the next model when it ships, in software a legal AI startup will not out-build. That is not a branding preference. It is the only place a working lawyer or paralegal can keep pace.

This is not a Claude versus ChatGPT article. Pick the frontier surface the firm will actually live in. The comparison that matters is those workspaces versus a legal-looking browser tab. Safe-use notes for the seats themselves are on Claude for lawyers and ChatGPT for lawyers. The operating rule is simpler: live there.

A chatbot seat with no file behind it is still not a brain. That distinction is already written: what is a firm brain, and legal AI software vs a purpose-built firm brain. Keep the seats. Connect the file. Do not leave the surface.

What happens if the firm lives in a legal AI browser app instead?

The firm ends up living in a browser. It will not compete. It will not move as fast. It will never have software as good as Anthropic or OpenAI.

Legal AI startups sell a legal-looking tab. Staff leave Claude or ChatGPT to work in that tab. The product looks specialized. The actual software is a wrapper around a model those labs already ship, plus a UI a twenty-person team can maintain. Every week the frontier vendors ship. The wrapper waits. The firm waits with it.

That is how a firm gets left behind without noticing. The demo was smooth. The logo said legal. Six months later the staff still live in the startup's browser, the model is a generation behind, and the owner is paying for the privilege. The startup has to take margin. Weaker models are how that margin appears. The firm is the spread.

Do not confuse this with keeping Clio or Filevine. Those are systems of record. Keep them. The trap is making a legal AI app the place people work. CMS AI inside Clio or Filevine is a different question, answered in CMS AI vs a firm brain and Clio Work vs Filevine vs a purpose-built firm brain. This post is about the home surface, not a CMS bake-off.

How does a firm brain keep you in those workspaces?

A firm brain, also known as an MCP server, connects the firm's real systems to Claude Cowork or ChatGPT so staff can stay there with the file. That is the whole job.

Without the brain, every useful question still starts in Clio, the folder, or the inbox. Staff copy the facts into Claude or ChatGPT, get a draft, copy it home. That paste loop is how a legal AI vendor talks the firm into moving house. The pitch is that their app already has the files. The cost of that move is leaving the frontier surface.

With a brain, the frontier workspace can look up the matter, the folder, and the thread, then draft for a human to release. Staff do not leave Claude Cowork or ChatGPT to go hunting. MCP is the plug. FirmOps configures the short, approved menu and operates it. The protocol is not a product. The Managed Firm Brain is the offer: purpose-built in partnership, then run. There is no boxed SKU that installs a brain.

Keep Clio or Filevine. The brain sits on the CMS. The operator walkthrough of a staff window on that plug is Claude Desktop plus MCP. This page is the rule, not the tool tour. The rule sits under law firm operations.

Is this proven on a live firm, or a slide deck?

It is proven on a live PI firm. Conduit Law is the proof. Not a deck.

We dogfood. FirmOps is not a hypothetical stack. It already covers what a firm actually needs in one place: marketing, sales, intake, onboarding, case management, closing, settlements, trust, accounting. The people who built the brain already stay in Claude Cowork or ChatGPT with that stack connected. That is why you stay there too. A firm brain is how the file lives in the frontier workspace instead of across twenty tabs.

We know the pain for attorneys, office, and staff because we do the work. Conduit people are not buried in admin, data entry, copy-paste, or twenty tabs. Ask anyone at Conduit. Public-safe receipts are on the Conduit Law case study. The layer is still purpose-built in partnership, then operated. Not a SKU.

Where do you work, and who takes the margin?

The table is the decision. Not a ranked list of legal AI tools, and not a scorecard of FirmOps against logos.

Live in Claude Cowork or ChatGPT, with a firm brainLive in a legal AI browser app
Where you workAnthropic or OpenAI's workspace. Staff stay as those vendors ship.The startup's browser tab. You left the frontier surface.
Whose software you wait onAnthropic or OpenAI.A legal AI product team.
Which model you getThe actual frontier model in that workspace.Whatever cheaper model the startup can wrap and still take margin.
Who takes marginYou pay the frontier vendor for the seat. The brain is a layer on your stack, not a wrap around the model.The startup sits between you and the model and keeps the spread. That is the business.
Clio / mail / files connectedYes, through a purpose-built firm brain (MCP) on the CMS you already run.Maybe a shallow integration. Often still paste. The home is still their app.
Who owns the layerThe firm. Purpose-built in partnership, then operated. Managed Firm Brain is the offer. Not a SKU.The startup. You rent the tab. Their roadmap. Their model.

Read the table as a home-surface choice. Buying a writing seat can still be right. Making that startup the office is how the firm falls behind. The partnership version of buy-a-tool versus purpose-built is already in legal AI software vs a firm brain.

What should the firm do instead of shopping another legal AI tab?

Stay in Claude Cowork or ChatGPT. Keep Clio or Filevine. Put a firm brain on the stack so the file is in that workspace. Then have it operated. Do not move house to a browser app.

Pick one recurring job that currently dies between the CMS, the folder, and the inbox. Connect that job to the frontier workspace through a short, approved menu. Read first. Draft for review. A person releases the send. Phones stay human. That is one job under a Managed Firm Brain, not a catalog of products.

Do not rip the case system to get AI. Do not treat FirmOps as a SKU on a best-of list. Do not wait on a legal AI startup to catch Anthropic or OpenAI. They will not. If that first job is a fit, Request demo.

Questions owners actually ask

Do we have to pick Claude or ChatGPT?

Pick the frontier workspace the firm will actually live in. The argument is not Claude versus ChatGPT. The argument is those workspaces versus a legal AI browser app.

Can we just buy a legal AI startup instead?

You can buy the tab. You will live in a browser. You will wait on their software. You will get a weaker model because that is how they make money. Tool versus partnership is legal AI software vs a firm brain. This post is the home-surface version of the same trap.

Is a firm brain a product we install in Claude?

No. A firm brain is purpose-built in partnership, then operated. MCP is how it connects. Managed Firm Brain is the offer. Not a boxed SKU. See what is a firm brain.

Does this replace Clio or Filevine?

No. Keep the CMS. The brain sits on it. See Clio Work vs Filevine vs a purpose-built firm brain.

How do we start?

Request demo. One job. We map whether the frontier workspace can see that job through a brain on your stack.

Keep moving up the operating system

Get the Managed Firm Brain Notes

Follow the practical path: live workflow builds, CRM-aware automation when the data is ready, and supervised work after approval.

Demo Context

What to watch for in the Managed Firm Brain walkthrough

Live-Lab Proof

How Conduit informs the first external deployments

Fit Criteria

API-ready systems, workflow scope, and approval gates

Low-volume updates only. The primary CTA remains reviewing the offer or booking an AI live demo. Follow our insights in Google.

J

About Jonathan Mahler

Jonathan Mahler is the non-attorney partner and COO of Conduit Law and the operator behind FirmOps. He runs the systems of a live PI firm every day, then turns reusable patterns into practical Managed Firm Brain workflows: approved context, supervised drafts, approval gates, and a path into deeper automation when the first workflow proves value.

Request demo

Bring one recurring bottleneck and see whether it is a good first firm-brain build. If the first workflow is concrete, the next step is a live build session, not a broad advisory project.

Live demo | Human approval before external action