Matter-intake automation: Claude Code vs. a workflow across intake, conflicts, and the DMS
New-matter intake spans forms, conflicts, the practice-management system, and the DMS. Here's what Claude Code can prototype and what it takes to run it reliably.
Claude Code can prototype pieces of matter intake, like reading an intake form, but the real workflow spans intake data, conflicts, opening the matter in your practice-management system, and setting up the DMS workspace, and connecting those reliably and unattended is what a coding agent leaves to you.
You can absolutely build this with Claude Code. The question is which version you need. An individual, judgment-heavy helper suits Claude Code well. A high-volume workflow that has to connect to your real systems, run identically every time, and stay maintained is where most of these projects stall, and that version runs better in Caddi.
Why matter intake is hard to automate well
- It's a multi-system process. Intake flows into conflicts, the PM system (Aderant, Elite 3E, Clio), and the DMS, each a real connection with its own rules.
- Accuracy and conflicts are critical. A missed conflict or a miskeyed party is a serious risk, so variable output can't be trusted to run alone.
- Inputs are unstructured. Intake forms and engagement materials vary; extraction has to be consistent, not just demo-day correct.
What slows it down in production
A partial automation that still needs someone to run conflicts, open the matter, and set up the workspace by hand doesn't shorten intake, and intake delays plus errors are exactly where firms lose clients and create risk.
| Claude Code | Caddi | |
|---|---|---|
| Prototype the workflow | Yes, with prompting | Yes, show it |
| Connect your real tools | Custom code & credentials | Connected for you |
| Run it identically every time | Output can vary | Deterministic code at runtime |
| Run unattended at volume | Needs supervision | Hundreds of runs a week |
| Maintenance | Yours | Done for you |
| Best for | Individual, judgment-heavy work | High-volume, high-accuracy work |
| Monitoring | Per script, set up by you | Caddi runs and the skills it hands Claude |
How Caddi runs the high-volume version end to end
Caddi automates matter intake end to end: it extracts client and matter details from intake forms, runs the conflicts process, opens the matter in your practice-management system, creates the DMS workspace with your naming and security, and notifies the team, as deterministic code, identical every run, with an audit trail. It connects intake, Aderant/Elite 3E/Clio, and iManage/NetDocuments for you.
Connect Aderant to Caddi
Allow1Sign in to your tools
One click each for Aderant, iManage and Microsoft Outlook. No API keys.
Automate matter intake.
ScreenshareType it2Show or tell it
Screenshare the job, or type it in chat. Change it any time.
- Running
14 done1 for review
3Watch it run
Caddi does the work and flags anything unsure for review.
Keep reading
See deterministic automation in action
Caddi builds reliable automations from a screen recording and runs them across 150+ tools as deterministic code. Explore real workflows for law firms and RIAs & financial advisors, or book a demo to see your own workflow built live.
Caddi
See how Caddi AI Agents can run new-matter intake and open the matter in every system
Frequently asked questions
Can Claude Code automate matter intake?
It can prototype pieces like form extraction, but the full workflow across conflicts, the PM system, and the DMS, reliably and unattended, is what Caddi handles.
Does it open the matter in our PM system?
Yes. Caddi opens the matter in Aderant, Elite 3E, or Clio and sets up the DMS workspace as part of the intake workflow.
How are conflicts handled?
Caddi runs your conflicts process deterministically and routes genuine hits to a person for review, with every step logged.
Do I have to choose between Claude Code and Caddi?
No. Caddi Discover finds and ranks the repetitive work across your systems, with evidence, so you know which of these to build first. High-volume, high-accuracy versions run in Caddi as deterministic code, the same way every run. Individual, judgment-heavy ones can be exported to Claude as a skill. Caddi Govern monitors every Caddi run, and the skills Caddi hands to Claude report each decision and API call back to it, in one firm-wide view.