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 acrossHarvey and Zocksby 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 meeting notes to CRM in Harvey and Zocks. Caddi builds the loop and runs it.

HarveyLegal
ZocksFinance

See it on your stack

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

  • 01

    Fetch meeting summary in Zocks when document ready in Harvey.

    Caddi watches Harvey for document ready and fetch meeting summary in Zocks — no copy-paste, no missed records.

  • 02

    Redline document in Harvey when meeting summary ready in Zocks.

    Caddi watches Zocks for meeting summary ready and redline document in Harvey so the two systems stay in lockstep.

  • 03

    Draft follow-up email in Zocks from Harvey events.

    When review requested happens in Harvey, Caddi draft follow-up email in Zocks with the right context attached.

Actions Caddi can take across Harvey and Zocks

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

  • Zocks

    Meeting summary ready

    Triggers when Zocks finishes structuring notes for a client meeting.

  • Zocks

    Action item created

    Triggers when Zocks extracts a follow-up task from a meeting.

  • Zocks

    Client fact captured

    Triggers when Zocks records a new or changed data point (goals, family, accounts).

  • Zocks

    Fetch meeting summary

    Pull the structured summary, tasks, and data points for a meeting.

  • Zocks

    Draft follow-up email

    Generate the client recap email from the meeting's action items.

  • Zocks

    Sync to CRM

    Push the meeting notes and extracted facts to the connected CRM record.

Common questions

How does Caddi connect Harvey and Zocks?

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

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

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