Cut a 10+ Service Stack Down to a Managed Firm Brain
An anonymized demo map: how an owner-led estate planning and elder-law practice can cut a 10+ service stack to fewer tabs and a Managed Firm Brain. Not a finished rebuild.
Jonathan Mahler
Non-Attorney Partner & COO, Conduit Law
One workflow
See if FirmOps should be your Managed Firm Brain
Bring one recurring bottleneck. If it is a good first firm-brain build, the next step is a live demo — not a pitch deck.
Most owner-led firms do not have a software problem. They have a too many loosely tied services problem. A lawyer signs up for intake, tasks, drafting, marketing, and e-sign — then wakes up as the unpaid integration layer between all of them.
That list showed up first on a recent FirmOps demo with an owner-led estate planning and elder-law practice. This is not a finished engagement. We have not rebuilt the firm, cut these invoices, or shipped their brain. What follows is the stack from the call, then the keep / replace / integrate map a Managed Firm Brain would sit on.
The 10+ service stack on the demo
None of these tools are “bad.” They are only loosely connected, and the lawyer is the glue:
- Asana — first system: tasks, checklists, and matter organization. They already want it as CRM.
- Dropbox — documents.
- WealthCounsel — estate-plan drafting, plus a questionnaire API.
- Outlook — email. The useful AI already lives in the Microsoft stack.
- ChatGPT and Claude seats — firm-paid writing and research tabs the owner already uses.
- LEAP — estate data, relationships, and assets. Feeds WealthCounsel. Also used as CRM, and it is buggy.
- Spellbook — legal AI drafting layered on, with an integration path toward WealthCounsel.
- Adobe Sign — e-sign. Keep for now; a later cut can move this to optional DocuSeal or portal e-sign.
- Lawmatics — CRM they intend to stop.
- DecisionVault — client questionnaires and intake.
- Levitate — runs the website and the newsletter. That is the current public site, not a leftover host sitting beside it.
Phones stay human. The firm uses Uma for phone and SMS. FirmOps is not an AI receptionist, and this map does not replace a person on the line.
Keep / replace / integrate
A FirmOps demo is a fit-and-feasibility conversation: which tools stay, which go, and what a supervised firm brain should connect first so the stack gets smaller.
| Service | Move | Why |
|---|---|---|
| Asana | Keep / integrate | First system. Tasks, checklists, matter organization. Make it the CRM. |
| Dropbox | Keep / integrate | Documents. |
| WealthCounsel | Keep / integrate | Estate-plan drafting and questionnaire API. The drafting path already points here. |
| Outlook | Keep / integrate | Email. AI stays in the Microsoft stack. |
| ChatGPT / Claude | Keep | Firm-paid seats. They stay as people tools, not a twelfth operating system. |
| Uma | Integrate | Phone and SMS. Phones stay human. |
| LEAP | Keep, shrink later | Holds estate data that feeds WealthCounsel. Buggy as CRM. Not a day-one rip. |
| Spellbook | Keep, shrink later | Drafting layer with a path toward WealthCounsel. Shrink as the drafting path absorbs useful work. |
| Adobe Sign | Keep, later optional | E-sign for now. Later cut can be optional DocuSeal or portal e-sign. |
| Lawmatics | Replace | Phased cutover to Asana, then stop. |
| DecisionVault | Replace | Questionnaires and intake. Replace with a firm portal into Asana and Dropbox. |
| Levitate | Replace | Website and newsletter package. Cut for a FirmOps-managed site and a simpler cadence. |
How the map would work
If the firm moved forward, the first job is not a twelfth app. It is a smaller stack with one operating picture — the same exercise we run as law-firm operations work, not a rip-and-replace day one.
1. Make Asana the CRM of record
The owner already wanted Asana as the CRM for day-to-day client and matter work. Stages, owners, custom fields, and checklists live there. Lawmatics is a phased cutover: field map, Asana templates, migrate open matters, then retire the old CRM once a live path is trusted.
2. Replace DecisionVault-shaped intake with a firm portal
A firm website and client portal can capture the same questionnaire depth, then write into Asana and link documents in Dropbox. Intake stops being a separate island. The client fills one portal. The firm works one matter project.
3. Keep drafting tools; stop using the lawyer as the bridge
WealthCounsel stays for document assembly. LEAP stays while it still earns its seat as the estate-data store that feeds drafting. Spellbook stays as a drafting layer with a path toward WealthCounsel. Adobe Sign stays for e-sign for now, with an optional later move to DocuSeal or portal e-sign. ChatGPT and Claude stay as writing seats. The firm brain’s job is to make facts, folders, deadlines, and next steps clean before drafting starts — not to add another AI tab.
4. Cut marketing glue that does not compound
Levitate is the current website and newsletter package, so that is the cut: a FirmOps-managed site, basic SEO, and a simpler content cadence on the firm’s own domain. Fewer vendors between the firm and the clients who should find it. This call is not a website rewrite.
5. Grow a firm brain under approval gates
First connections are usually Asana, Dropbox, WealthCounsel, Outlook, and Uma. Read-first. Drafts for human review. No unsupervised client sends. Over time LEAP and Spellbook can shrink as the drafting path absorbs useful work — without a big-bang cut on day one. More AI tabs is not a firm brain. That distinction is usually the turning point on the call.
The crazy part is not one tool. It is the stack tax.
When services are only loosely tied, the firm pays three times:
- Cash — overlapping subscriptions. On this demo stack, DecisionVault and Levitate alone were roughly in the neighborhood of $800/month combined, with the newsletter package called out near $8,000/year. Those are the cut-first invoices. They are not a claim we already cancelled them.
- Attention — the lawyer becomes the integration layer. Every missing field, every Dropbox disconnect, every “where did that questionnaire land?” is a context switch.
- Time-to-cash — work that sits between systems is work that is not signed, not delivered, and not billed. Clients feel the lag as silence. Owners feel it as backlog.
On the demo, the practical pain was the handoff: Adobe Sign, Asana checklists, and DecisionVault questionnaires, then data into LEAP so WealthCounsel can draft. The owner is the bridge. Spellbook and Microsoft AI help with language. ChatGPT and Claude help with writing. They do not give the firm one operating picture across Asana, Dropbox, Outlook, and drafting.
This is the demo, not the finish line
To be clear: this article is an anonymized example of what a sales demo surfaces. It is not a claim that FirmOps has already rebuilt this firm, cut those invoices, or shipped the firm brain. The value of the demo is seeing the chaos named out loud — and leaving with a concrete map of what can be cut, consolidated, and connected under human approval gates.
If your firm is drowning in loosely tied services — CRM here, intake there, docs somewhere else, AI in yet another tab — Request demo. The booking page is a 30-minute live walkthrough of the same exercise: which tools should stay, which should go, and what a Managed Firm Brain should connect first so your people stay in control.
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
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.
Related Articles
How to Automate Law Firm Intake Without Dropped Balls
A sitting PI-firm COO explains where intake breaks, what to automate first, and how to keep human review in the workflow.
What is a firm brain?
A firm brain is a purpose-built operating layer for one law firm, implemented in partnership, then run for that firm. Not a chatbot. Not a boxed product.
Your practice management software added AI. Is that a firm brain?
No. A CMS AI feature answers questions inside that app. A firm brain is purpose-built across the firm's stack and run with the firm.
See if FirmOps should be your Managed Firm Brain
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