Contract management · Production

NEXT Insurance standardizes contract management with Ironclad CLM and Jurist AI, achieving 100% attorney adoption

The problem

NEXT Insurance employees were signing contracts and agreeing to terms without legal review, creating significant compliance risk. Ironclad had been purchased before a dedicated legal operations role existed, and without expert implementation it was inconsistently adopted — some employees used the system while others continued to use email.

First attempt

Ironclad had been purchased but was inconsistently implemented — without a dedicated system expert, adoption was uneven and some employees bypassed the system entirely for email, creating visibility gaps.

Workflow diagram · grounded in source
1
Mandatory Ironclad submission
Trigger
All contracts must be submitted through Ironclad before the legal team will review them.
▾ source quote
“Legal is not going to review any contract unless it goes through Ironclad”
2
AI Playbook clause enforcement
Ai action
AI-powered clauses are trained to run across all contracts in the system via playbooks created for each contract type.
▾ source quote
“create playbooks for each contract type and then train the AI powered clauses to run AI across all contracts in the system”
3
Equal attorney distribution
Routing
Contracts are assigned equally across attorneys using the workflow designer in Ironclad CLM.
▾ source quote
“Using workflow designer [in Ironclad CLM], I assigned contracts equally across our attorneys”
4
Jurist AI contract review
Ai action
The prompt library is used to review contracts against company policies and perform real-time legal research with complete links and legal citations.
▾ source quote
“We can utilize the prompt library to review contracts against company policies/positions. Perform real-time legal research with complete links and legal citations”
5
Attorney human verification
Human review
Attorneys review AI-assisted analysis using a trust-but-verify philosophy.
▾ source quote
“We at Next Insurance still approach this technology with the philosophy of trust but verify”
6
Contract approval or modification
Output
Contracts are approved or modified — for example, a termination clause is added when an auto-renewal clause cannot be eliminated.
▾ source quote
“if there's no way to eliminate that, we add a termination clause”
Reported outcome

Ironclad became mandatory for all contracts, Jurist achieved 100% user adoption in a single week, and the legal team cut the time to draft termination letters in half.
The team can now demonstrate measurable AI innovation to executive leadership.

Reported metrics
Jurist user adoption100%
Jurist messages per user per week9
Jurist prompt library uses in one week20
Documents added from repository weekly2-8
Show all 7 reported metrics
Jurist user adoption100%
Jurist messages per user per week9
Jurist prompt library uses in one week20
Documents added from repository weekly2-8
New Jurist threads per week4-26
Average weekly Jurist threadsabout 20
Time to draft termination letterscuts my time in half
Reported stack
IroncladJuristAI Playbooksworkflow designer
◆ Does this fit your context?

Compare to your context

Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.

Compare to your context →
~30 seconds · free
Source
https://ironcladapp.com/resources/customer-stories/next
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Ironclad became mandatory for all contracts, Jurist achieved 100% user adoption in a single week, and the legal team cut the time to draft termination letters in half.

What tools did this team use?

Ironclad, Jurist, AI Playbooks, workflow designer.

What results were reported?

Jurist user adoption: 100%; Jurist messages per user per week: 9; Jurist prompt library uses in one week: 20; Documents added from repository weekly: 2-8 (source-reported, not independently verified).

What failed first in this deployment?

Ironclad had been purchased but was inconsistently implemented — without a dedicated system expert, adoption was uneven and some employees bypassed the system entirely for email, creating visibility gaps.

How is this contract management AI workflow structured?

Mandatory Ironclad submission → AI Playbook clause enforcement → Equal attorney distribution → Jurist AI contract review → Attorney human verification → Contract approval or modification.

Related contract management cases

WHAT TO DO WITH THIS

Now compare it to your context

This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.

Browse the Contract management cases →