Meet Caddi in personFuture ProofSep 14–17Booth 248 · Zone 1ADVISE AIOct 20–22AI for Mid-Sized LawNov 5Legal InnovatorsNov 17–18

AI-native automation

Automate work acrossClio and Harveyby 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 one user.

Help me automate redline in Clio and Harvey. Caddi builds the loop and runs it.

ClioLegal
HarveyLegal

See it on your stack

See Caddi run Clio and Harvey 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 Clio and Harvey together

  • 01

    Redline document in Harvey when new matter in Clio.

    Caddi watches Clio for new matter and redline document in Harvey — no copy-paste, no missed records.

  • 02

    Create matter in Clio when document ready in Harvey.

    Caddi watches Harvey for document ready and create matter in Clio so the two systems stay in lockstep.

  • 03

    Summarize document in Harvey from Clio events.

    When new contact happens in Clio, Caddi summarize document in Harvey with the right context attached.

Actions Caddi can take across Clio and Harvey

  • 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.

  • Harvey

    Document ready

    Triggers when a document is queued for Harvey to process.

  • Harvey

    Review requested

    Triggers when a redline or review is requested on a draft.

  • Harvey

    Analysis complete

    Triggers when Harvey finishes a summary, redline, or extraction.

  • Harvey

    Redline document

    Send a draft to Harvey for AI redlining and markup.

  • Harvey

    Summarize document

    Generate a summary of a document or document set.

  • Harvey

    Extract clauses

    Pull key clauses, terms, or issues from a document.

  • Harvey

    Answer question

    Run a research or document question against Harvey.

Common questions

How does Caddi connect Clio and Harvey?

Clio and Harvey 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 Clio and Harvey 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 Clio and Harvey to other tools too?

Yes. Most Caddi loops span 3–6 tools. Once the first Clio + Harvey 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 Clio and Harvey?

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