Meet Caddi in personADVISE AIOct 20–22AI for Mid-Sized LawNov 5Legal InnovatorsNov 17–18
For law firm CIOs

Business teams automate.
IT sees every run.

Caddi AI Agents connect to Intapp, Elite 3E or Aderant, iManage and Microsoft 365 with the permissions each person already has. Business teams build their own workflows, and you see every agent and every run in one place.

Request demoSign up free
SOC 2 Type II150+ integrationsEvery run logged

Help me automate matter workspace in iManage and Microsoft 365. Caddi builds the loop and runs it.

The role

What a law firm CIO does

A law firm chief information officer owns technology strategy, the application portfolio, infrastructure and security, and reports to the COO or the managing partner. At larger firms the CISO, the director of applications and the knowledge and innovation leads report in. The job is split between keeping the firm's systems running and delivering the projects that change them, and in 2026, deciding how AI gets used safely across both.

Two pressures shape it. Clients audit their firms: security questionnaires before an engagement and periodically after, and outside counsel guidelines with data-security clauses. And AI arrived faster than policy. ILTA's 2025 Technology Survey of 580 firms found 80% using or exploring generative AI, while 19% had no generative AI policy and a quarter were still drafting one.

Owns
  • The application portfolio: financial system, DMS, intake and conflicts, Microsoft 365
  • Infrastructure, security and business continuity
  • Client security questionnaires and audits
  • AI governance and acceptable-use policy
  • Integrations between the firm's systems
  • Vendor security reviews and access controls
Measured on
  • Client security audit outcomes
  • Uptime and service levels
  • Project delivery against budget
  • Adoption of what the firm has bought
  • Incidents, and the automation nobody knows about
Lives in
Microsoft 365iManageNetDocumentsElite 3EAderantIntappSharePointRelativity
The week

Where IT's week goes on the business side

The requests that fill an IT queue are rarely infrastructure. They are business teams asking for two systems to talk to each other, one more time, for one more workflow.

The workWhere it happensWhat Caddi does
Integration requests between systemsCustom scripts, Power Automate, the vendor's roadmapThe business team builds the workflow on connections IT has approved, running through each system's API, logged run by run. See it
Matter workspace provisioningiManage, Microsoft 365, TeamsCreates the workspace, the team and the channel from your template when a matter opens. See it
Litigation workspace setupRelativitySets up the new matter's workspace from your template when litigation support requests it. See it
Access reviewsMicrosoft 365, the DMS, the financial systemPulls the user and access lists from each system into one review sheet for the owners to sign off.
Automation nobody can seeFlows and scripts built across the firmEvery agent built in Caddi shows in one firm-wide view: who built it, what it touches, and every run. See it

Caddi does not change your security policy or grant access. It runs with the permissions each person already has, in the systems you have approved.

Discover

Read only, with the access people already have.

Discover reads activity in the systems a team connects, under that person's existing access, and never writes. It reads reports, counts and recent activity rather than walking every record, so it does not turn into a spike in API usage, and it does not repeat a run for 30 days unless a new tool is connected.

  • Inherited, read-only access
  • No recorder on every desktop, no event-log extraction
  • Findings with the counts behind them
How Discover works
High confidence

Morning Inbox Triage and Matter Filing

Read each new message in Outlook, open any Docusign envelope, match it to the matter in Clio and file the executed copy to NetDocuments.

152hrs / yr5×/week · ~35 min each
Microsoft OutlookDocusignClioNetDocuments

What Caddi saw

  • 1,204messages read in Outlook in the last 30 days
  • 418Docusign envelopes opened from those messages
  • 412matters matched in Clio and filed to NetDocuments
  • 6exceptions raised for review in Teams

Why it’s worth automating

Every message already names the client and the matter. The four steps are the same each time, and the tools never talk to each other, so you carry the details between them by hand.

Per occurrence
35 min
Per week
2.9 hrs
Observed over
30 days
Build next
Automate

Workflows the business builds, that IT can read.

The person who does the work walks Caddi through it, and Caddi drafts the workflow as a plan you can open: which systems, which steps, what it asks a person. It then runs as verified code against each system's API.

  • No new privileged service accounts
  • Approved connections only
  • Caddi builds the workflow with you, then verified code runs it against your systems through their APIs, the same way every time. Any model step inside a run is scoped, logged and reviewable.
How Automate works
Govern

Every agent, every run, one view.

Govern shows every agent built across the firm, who owns it, what it touches and what it did, with every run logged with its inputs, steps and result. When a client's security questionnaire asks how automation is controlled, the answer is a screen, not a spreadsheet.

  • Firm-wide view of every agent
  • Run history, exportable
  • SOC 2 Type II attested
How Govern works
FAQ

Questions law firm CIOs ask us

What does a law firm CIO do?
A law firm chief information officer owns technology strategy, the application portfolio, infrastructure and security, and reports to the COO or managing partner. The role covers keeping systems like the financial system, DMS and Microsoft 365 running, delivering technology projects, answering client security audits, and setting AI governance for the firm.
How does Caddi handle permissions?
Caddi runs with the access each person already has in each system. It does not need new privileged service accounts, and Discover is read only. IT decides which systems Caddi may connect to.
Is AI making decisions inside our systems at runtime?
Caddi builds the workflow with the person who does the work, then verified code runs it against your systems through their APIs, the same way every time. Where a workflow includes a model step, such as reading a document, that step is scoped, logged and reviewable, and the workflow stops and asks a person when it is not sure.
How is Caddi different from Power Automate?
Power Automate asks someone to design the flow. Caddi finds the work worth automating, lets the person who does it build the workflow by walking through it, and puts every agent and every run across the firm in one view. The comparison page covers the detail.
What security documentation can we review?
Caddi is SOC 2 Type II attested, encrypts data in transit and at rest, and runs OpenAI and Anthropic calls under zero-data-retention terms. The security page and the trust documentation are available for your review.
Is our client data used to train models?
No. The contents of your connected systems are never used to train models. Calls to OpenAI and Anthropic run under zero-data-retention terms, and data is encrypted in transit and at rest. Caddi is SOC 2 Type II attested.

How to roll out AI across a law firm →

Get started

Review Caddi with your security team.

Bring your questionnaire. We will walk through permissions, the run record and the firm-wide view on the call.

Or sign up free