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

AI-native automation

Automate work acrossClio and Jumpwith Caddi AI Agents.

Connect Clio and Jump: Fetch meeting summary in Jump when new matter in Clio. Teach Caddi the job once, the way you'd train someone new, and it runs end to end. No workflow builder.

Free for one user.
ClioLegal
JumpFinance

Discover, automate and govern the work between Clio and Jump

Caddi AI Agents find the repetitive handoffs between Clio and Jump, learn them the way a new hire would, and run them for you, with every run on the record. No workflow builder, no code.

Discover the repetitive work across existing tools.
Automate the work by delegating to an AI agent.
Govern every workflow and every decision an agent makes.
  • The Planning Center
  • Beveridge & Diamond
  • Palace
  • Portner & Shure
  • Knight Law Group
  • Ervin Cohen & Jessup
  • Burney Wealth Management
  • JFS Wealth Advisors

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 · 150+ tools across legal, finance, and operations

Practical ways to use Clio and Jump together

  • 01

    Fetch meeting summary in Jump when new matter in Clio.

    Caddi watches Clio for new matter and fetch meeting summary in Jump. No copy-paste, no missed records.

  • 02

    Create matter in Clio when meeting summary ready in Jump.

    Caddi watches Jump for meeting summary ready and create matter in Clio so the two systems stay in lockstep.

  • 03

    Draft follow-up email in Jump from Clio events.

    When new contact happens in Clio, Caddi draft follow-up email in Jump with the right context attached.

Actions Caddi can take across Clio and Jump

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

  • Jump

    Meeting summary ready

    Triggers when Jump finishes a meeting summary.

  • Jump

    Action item created

    Triggers when Jump captures a follow-up task.

  • Jump

    Client fact captured

    Triggers when Jump records a new or changed client detail.

  • Jump

    Fetch meeting summary

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

  • Jump

    Draft follow-up email

    Draft the client recap from the action items.

  • Jump

    Sync to CRM

    Push notes and facts to the connected CRM record.

Common questions

How does Caddi connect Clio and Jump?

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

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

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