AI-native automation
Automate work across
CASEpeer 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.
Help me automate redline in CASEpeer and Harvey. Caddi builds the loop and runs it.
See it on your stack
See Caddi run CASEpeer and Harvey together.
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.
- 01Measure
Caddi watches how the work gets done today.
- 02Create
You teach it the job once. The loop ships.
- 03Improve
Caddi flags upgrades to existing loops and new automations to deploy.
Practical ways to use CASEpeer and Harvey together
- 01
Redline document in Harvey when new case in CASEpeer.
Caddi watches CASEpeer for new case and redline document in Harvey — no copy-paste, no missed records.
- 02
Create case in CASEpeer when document ready in Harvey.
Caddi watches Harvey for document ready and create case in CASEpeer so the two systems stay in lockstep.
- 03
Summarize document in Harvey from CASEpeer events.
When case stage changed happens in CASEpeer, Caddi summarize document in Harvey with the right context attached.
Actions Caddi can take across CASEpeer and Harvey
- 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.
- 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 CASEpeer and Harvey?
CASEpeer 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 CASEpeer 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 CASEpeer and Harvey to other tools too?
Yes. Most Caddi loops span 3–6 tools. Once the first CASEpeer + 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 CASEpeer and Harvey?
Drop your work email and we'll show you Caddi running end-to-end against CASEpeer, Harvey, and the rest of your stack.
Or skip the demo: sign up free and build it yourself.