How a 2,400-Person US Insurer Cut Contract Review Time 40 Percent in 8 Weeks

Background: A 2,400-Person US P&C Insurer

This case study is a composite drawn from patterns Forfis has observed across multiple insurance engagements in Tier-1 US markets. No named customer appears. The details below reflect a realistic engagement profile: a mid-to-large insurer, a specific compliance pressure, and a fixed-scope pilot that moved from audit to measured rollout in eight weeks.

The company in question is a property and casualty insurer with roughly 2,400 employees, headquartered in a Tier-1 US metro. It operates a hybrid stack: a legacy policy management system for underwriting, Notion for internal knowledge management, and Confluence for compliance documentation. The legal and compliance team of 38 analysts handles contract review for vendor agreements, reinsurance treaties, and policyholder addenda. The team’s primary pain is not legal judgment but data entry: extracting clause-level details from PDFs, populating tracking spreadsheets, and flagging deviations from standard terms. Each contract consumes 4 to 6 hours of analyst time before it reaches a senior reviewer.

Challenge: 5.2 Hours per Contract and a 90-Day Audit Clock

The trigger was a regulatory audit cycle. The company’s compliance officer needed to demonstrate, within a 90-day window, that contract review processes met internal risk thresholds and that no policyholder data was handled outside approved systems. The existing process relied on manual PDF reading, spreadsheet tracking, and email chains. Error rates on clause extraction sat at roughly 12 percent, and cycle time averaged 5.2 hours per contract. Headcount was frozen, so the team could not absorb the volume increase from a new reinsurance program launching in Q3.

The specific need was not to replace legal judgment but to eliminate the data-entry layer: the repetitive extraction, classification, and flagging that consumed 70 percent of analyst time. The compliance team needed a system that could read a contract, score each clause against the company’s standard terms, and surface only the deviations that required human review. Everything had to stay inside the company’s data perimeter to satisfy GDPR Article 4 definitions of personal data and the company’s internal data residency policy.

Approach: n8n Orchestration with a Human Approval Gate

Forfis ran a two-week process audit across the compliance team’s workflow. The audit identified three automatable stages: clause extraction from PDFs, risk scoring against a predefined rubric, and structured output into Notion and Confluence. The team chose contract review as the pilot scope because it had the highest volume and the clearest before/after metrics.

The architecture used n8n as the orchestration layer. A new document upload triggered an n8n workflow that called an LLM API for clause extraction, applied a predictive scoring model to flag deviations, and wrote the structured result to a Notion database. A summary posted to the relevant Confluence page. The model was model-agnostic: the pilot used an API-based LLM for quality, with a documented path to migrate to an open-weight model on the client’s own hardware if data residency requirements tightened. A dedicated AI team of four Forfis engineers and one product designer worked alongside two compliance analysts assigned by the client. Every output that touched policyholder data or contract terms required a human approval gate before it moved to the next stage.

Outcome: 40 Percent Faster, 67 Percent Fewer Extraction Errors

The pilot ran for six weeks after the two-week audit, for a total of eight weeks from kickoff to measured rollout. Baseline metrics were captured in weeks one and two: 5.2 hours average cycle time per contract, 12 percent clause-extraction error rate, and 38 analyst-hours per week spent on manual data entry.

After the n8n workflow went live in parallel with the manual process, the team measured the following over four weeks:

• Cycle time dropped to approximately 3.1 hours per contract, a 40 percent reduction.
• Clause-extraction error rate fell to roughly 4 percent, a 67 percent relative improvement.
• Analyst time on data entry dropped from 38 hours per week to about 14 hours per week.
• The compliance team redirected the freed capacity to the 15 percent of contracts that required deep legal review, which had previously been buried under routine processing.

The system did not replace the policy management system. It fed structured data back through the same APIs the team already used, and every flagged contract still required a named human reviewer before signature. The audit deliverable was a documented before/after report with timestamps, error logs, and reviewer sign-offs.

Lessons for Similar Teams

Five lessons from this engagement apply to any insurance or compliance team considering AI-assisted contract review:

• Start with the data-entry layer, not the judgment layer. The highest ROI in legal and compliance automation is eliminating repetitive extraction and classification, not replacing legal reasoning. Scope the pilot to the 70 percent of work that is mechanical.
• Measure the baseline before you build. Two weeks of manual tracking before the pilot gives you a defensible before/after number. Without it, the outcome is anecdote, not evidence.
• The approval gate is not a bottleneck; it is the product. In regulated environments, the human-in-the-loop step is what makes the system auditable. Design the reviewer interface in Notion or Confluence so the approval action is a single click, not a form fill.
• Model-agnostic architecture protects you from lock-in. If your data residency requirements change, you should be able to swap the LLM without rewriting the workflow. n8n’s abstraction layer makes this a configuration change, not a rebuild.
• Eight weeks is realistic if data access is clear. The timeline holds when API access to the policy management system and read access to Notion and Confluence are available in week one. Delays almost always come from access approvals, not from the build.