UK SaaS Team Cuts Candidate Screening from 18 Days to 6 in a Four-Week AI Pilot

Background: A 30-Person UK SaaS Team with a Screening Bottleneck

This case study is a composite based on patterns observed across multiple engagements. We do not name real customers. The company, the metrics, and the timeline are drawn from a recurring profile: a 30-person B2B SaaS firm in the UK, mid-growth stage, running on a standard stack of Notion for documentation, a CRM for pipeline, and a helpdesk for support. The team had no dedicated AI function. The founder had read about LLMs and wanted to test whether one process could be automated without a six-month build. The engagement ran for four weeks, end to end, from process audit to measured baseline.

The Challenge: 18-Day Screening Cycle and a Hiring Deadline

The team was hiring for two roles simultaneously: a senior engineer and a customer success manager. The screening process was manual. A recruiter read each CV, wrote a summary in Notion, and flagged the candidate for the hiring manager. The average cycle time from application to first screening decision was 18 days. The error rate was not measured, but the hiring manager reported that roughly one in five candidates who passed screening were later found to be a poor fit. The pressure was operational: the founder needed to close both roles before the next funding round, and the manual process was the bottleneck. There was no compliance constraint, but the team wanted a clean, auditable trail of who approved each screening decision.

Approach: Audit, Build, and a Human-in-the-Loop Gate

The engagement started with a three-day process audit. The dedicated AI team mapped the screening workflow step by step, identified the two highest-impact automation points (CV extraction and screening summary), and selected candidate screening as the single pilot process. The build used Anthropic Claude API for the extraction and classification. The integration was read-write against Notion: the AI read the job description and the CV, wrote the screening summary back to the same Notion page, and tagged the candidate with a classification label. The human-in-the-loop step was a simple approve/edit/reject button on the Notion page. The multilingual coverage was built in from day one: the model handled CVs in English, French, and German without a separate translation step. The build took nine days. The remaining time was spent on the baseline measurement and the rollout to the two open roles.

Outcome: 18 Days to 6 Days, 20% to 8% Error Rate

The measured baseline showed a cycle time reduction from 18 days to 6 days for the screening step. The error rate, measured as the percentage of candidates who passed screening but were later rejected at interview, dropped from 20% to 8%. The human-in-the-loop step added 3 minutes per candidate, but the total time per candidate fell from 22 minutes to 9 minutes. The team screened 47 candidates in the four-week window, compared to 19 in the previous four weeks. The founder reported that the hiring manager could now review all screening decisions in a single 30-minute session per day, instead of spreading them across the week. The multilingual coverage meant the team could accept applications from candidates in France and Germany without a separate translation step, which the founder estimated saved roughly 4 hours per week.

Lessons for Similar Teams

• Start with one process, not a platform. The pilot succeeded because the scope was a single workflow with a clear input and output. Teams that try to automate three processes in four weeks end up with three half-built integrations and no clean baseline. – Measure the baseline before you build. The 18-day cycle time and 20% error rate were recorded in the first week. Without that number, the outcome would have been anecdotal. The baseline is the most valuable deliverable in the pilot. – Human-in-the-loop is not a compromise; it is the product. The approve/edit/reject gate is what made the hiring manager trust the output. Remove it, and the team reverts to manual screening within two weeks. – Multilingual coverage is a feature, not a nice-to-have. For a UK team hiring in a European market, the ability to screen CVs in French and German without a translation step is a direct operational gain. Build it in from day one. – The integration is the moat, not the model. The AI layer plugs into Notion through its API. If the team later switches to Confluence, the integration work is a day, not a rebuild. The model is swappable; the integration is the asset.