How a 120-Person UK Advisory Firm Cut Contract First-Response Time to 38 Minutes

Background: A 120-Person UK Advisory Firm

This case study is a composite based on patterns Forfis has observed across multiple engagements in the UK professional services sector. No named client is represented; the figures are drawn from real pilot baselines and post-rollout measurements. The company in this story is a 120-person firm providing legal and financial advisory services to mid-market clients in London and Manchester. It runs on Microsoft 365, a mid-tier CRM, and a document management system that predates the current team. The firm sits in the 51-200 employee band, which means it has the volume to justify automation but not the headcount to run a dedicated AI team.

The Challenge: 4.2-Hour First Response and a 14-Week Deadline

The firm’s contract review process was the bottleneck. Clients sent contracts via email; a paralegal or junior associate extracted key clauses, flagged risks, and drafted a response. First-response time averaged 4.2 hours, with a peak of 11 hours during quarter-end. The error rate on clause extraction was 6.1%, meaning roughly one in sixteen contracts required a second pass. GDPR Article 22 required that no automated system make a decision solely on the basis of profiling without human oversight. The firm also faced a deadline: a major client contract was due in 14 weeks, and the existing team could not absorb the volume without hiring two additional paralegals at a cost of approximately GBP 78,000 per year.

Approach: Audit, Pilot Sprint, and Model-Agnostic Integration

Forfis began with a two-week process audit. The team mapped every step of the contract review workflow, measured cycle time and error rate on a sample of 200 contracts, and scored each sub-task by volume, error rate, and regulatory exposure. The audit produced a phased roadmap: a fixed-scope pilot on clause extraction and risk flagging, followed by rollout to the financial advisory team. The pilot used the Anthropic Claude API for extraction and classification, with a human-in-the-loop approval gate for anything touching contract terms. The integration sprint ran five weeks: Forfis built the extraction pipeline, connected it to the firm’s CRM and Microsoft Teams, and shipped a Slack channel where flagged clauses appeared as threaded messages with confidence scores. The model-agnostic architecture meant the firm could swap to an open-weight model on its own hardware if data residency requirements tightened.

Outcome: 38-Minute First Response and a 1.4% Error Rate

After the five-week pilot, the firm measured the new baseline. First-response time dropped from 4.2 hours to 38 minutes. Extraction error rate fell from 6.1% to 1.4%. The paralegal team redirected its time from manual extraction to higher-value risk analysis. The firm did not hire the two additional paralegals. Rollout to the financial advisory team took three additional weeks, extending the total engagement to three months. The managed operation phase began in week 13, with Forfis monitoring model performance, handling edge cases, and tuning the extraction prompts. The client retained ownership of the integration code and the Teams/Slack configuration, so it could extend the workflow internally without a new engagement.

Lessons for Similar Teams

• Baseline before you build. The audit’s 200-contract sample gave the firm a defensible before/after metric. Without it, the pilot’s success would have been anecdotal. Teams that skip the baseline struggle to justify scaling to stakeholders.
• Human-in-the-loop is not a compromise. The approval gate for contract terms kept the firm compliant with GDPR Article 22 while still cutting manual effort. The gate added 12 seconds per clause but prevented a single high-risk auto-approval that would have required a client call.
• Model-agnosticism is a risk hedge. The firm’s data residency requirements could have shifted mid-engagement. Because the architecture supported open-weight models on local hardware, Forfis could swap the backend without rewriting the integration layer.
• Integration over replacement. Plugging into the existing CRM and Teams meant the team did not have to learn a new tool. Adoption was near-complete in the first week because the workflow appeared in the channel they already checked every morning.
• Fixed-scope pilots reduce scope creep. The five-week sprint had a defined set of document types and a defined approval gate. Adding new document types was a separate decision, not a mid-sprint change request.