Meet Caddi in personILTACONAug 23–27Booth 159Future ProofSep 14–17Booth 248 · Zone 1

AI-native automation

Automate work acrossCASEpeer and Clioby teaching Caddi like a new hire.

Pick any number of tools and Caddi automates them end-to-end. No workflow builder. You teach it the job once, the way you'd train someone new.

Sign up freeFree for 14 days.

Help me automate initials-Based File Naming in CASEpeer and Clio. Caddi builds the loop and runs it.

CASEpeerLegal
ClioLegal

See it on your stack

See Caddi run CASEpeer and Clio together.

  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group

What Caddi is and how it works

An AI teammate that runs your back-office loops.

  • Doesn't break. Caddi reads intent, so when fields move or UIs change, your loop keeps running.
  • Taught like a new hire. Walk Caddi through the work once. Tweak it later by chat, with no workflow builder to re-architect.

SOC 2 attested · Human-in-the-loop · Full audit trail · 70+ tools across legal, finance, and operations

One continuous loop.

  1. 01Measure

    Caddi watches how the work gets done today.

  2. 02Create

    You teach it the job once. The loop ships.

  3. 03Improve

    Caddi flags upgrades to existing loops and new automations to deploy.

Practical ways to use CASEpeer and Clio together

  • 01

    Create matter in Clio when new case in CASEpeer.

    Caddi watches CASEpeer for new case and create matter in Clio — no copy-paste, no missed records.

  • 02

    Create case in CASEpeer when new matter in Clio.

    Caddi watches Clio for new matter and create case in CASEpeer so the two systems stay in lockstep.

  • 03

    Create contact in Clio from CASEpeer events.

    When case stage changed happens in CASEpeer, Caddi create contact in Clio with the right context attached.

Actions Caddi can take across CASEpeer and Clio

  • CASEpeer

    New case

    Triggers when a new case is created in CasePeer.

  • CASEpeer

    Case stage changed

    Triggers when a case advances to a new stage.

  • CASEpeer

    New intake

    Triggers when a new lead enters the intake pipeline.

  • CASEpeer

    Create case

    Open a new CasePeer case with client, incident, and intake fields.

  • CASEpeer

    Create contact

    Add a contact (client, witness, opposing party) to a case.

  • CASEpeer

    Add note

    Log a timestamped note against a case.

  • CASEpeer

    Update case stage

    Advance a case to the next stage with optional owner change.

  • Clio

    New matter

    Triggers when a new matter is opened in Clio.

  • Clio

    New contact

    Triggers when a new contact is created.

  • Clio

    Time entry posted

    Triggers when a new time entry is recorded.

  • Clio

    Communication added

    Triggers when a call, email, or meeting is logged.

  • Clio

    Create matter

    Open a new Clio matter with client, billing, and intake fields.

  • Clio

    Create contact

    Add a person or company contact to Clio.

  • Clio

    Create note

    Log a timestamped note against a matter.

  • Clio

    Create time entry

    Record time against a matter with rate and activity code.

  • Clio

    Upload document

    Attach a document to a matter with metadata.

Common questions

How does Caddi connect CASEpeer and Clio?

CASEpeer and Clio just run together. You teach Caddi the way you'd teach a new hire: walk it through how you use them today, with no workflow builder to wire up. Caddi turns that walkthrough into a verified loop and runs it against CASEpeer and Clio end-to-end.

Do I need engineering help?

No. Whoever does the work today walks Caddi through it on a call, the same way they'd train a new hire. Caddi builds the loop. No code, no IT ticket.

Is my data safe?

Yes. Caddi is SOC 2 attested. The AI watches and builds the automation, and once the loop ships it runs as deterministic code, repeatable and logged, with any model step scoped and reviewable.

Can Caddi connect CASEpeer and Clio to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + Clio loop is live, Caddi suggests other tools and other workflows to fold in.

How fast can it go live?

Typical first loops ship within a week of that first walkthrough. The Caddi team reviews every loop before it runs in production.

Ready to automate CASEpeer and Clio?

Drop your work email and we'll show you Caddi running end-to-end against CASEpeer, Clio, and the rest of your stack.