Skip to content

Clare Persey Recruitment: A Recruitment Tech Transformation Case Study

This case study looks at a small U.K.

search firm that had spent six years on Access RDB Recruitment before deciding the system no longer fit how the team worked. The problems were practical: the software did not connect with everyday tools such as Slack and Zoom, and the team wanted more of their routine work automated. The account below describes what the firm changed, what it observed afterwards, and how a similar evaluation can be structured.

Why the switch happened

Clare Persey Recruitment had used Access RDB Recruitment for six years. Over time the team found the platform disconnected from the tools they relied on daily, and they felt the software was holding them back rather than keeping pace with their work. Clare, the Managing Director, wanted a system that could take over repetitive day-to-day tasks and raise the standard of service delivered to clients and candidates. The decision was not framed as a feature-by-feature comparison alone. According to the firm's own account in this case study, the relationship with the vendor's people and the ability to adjust the system to its processes weighed heavily alongside practical fit. That combination — practical fit plus a working relationship — is what moved the decision forward.

What changed after the move

Three changes stand out in the account. Each maps to a different part of the recruitment workflow, which makes them useful as separate evaluation criteria rather than a single verdict.

1. A system the team could actually use

The first change was usability. The team wanted simplicity rather than a platform that required constant navigation around complexity. With a more intuitive interface, recruiters could spend their attention on relationships with candidates and clients instead of on workarounds. Automation covered the path from sourcing through to communication, which reduced the number of manual steps in a process that otherwise repeats for every role. If you are evaluating a replacement system, treat usability as a measurable question: how many clicks does a routine action take, and can a new team member complete it unaided in the first week?

2. Shared visibility across the team

The second change was collaboration. Activities could be logged against specific roles, so every team member could see the latest state of a search without asking around. That removed the information silos that slow down communication in a growing business. A practical test here is whether the system records activity at the level of the role, not just the candidate or the client. If your team cannot answer 'what happened on this role this week?' from one screen, the visibility gap is the problem to solve.

3. A candidate database that supports proactive search

The third change was the candidate database. It moved from cluttered to clear, and the firm describes that as a strategic overhaul rather than a tidy-up. The practical result was faster candidate matching and a more proactive approach to headhunting. The distinction matters: a clean database is not an aesthetic preference, it is the input to matching. If records are inconsistent, matching slows down no matter how good the search tool is. In the same case study, the firm's Managing Director is quoted praising the vendor's client care, customer support and customisation as invaluable — a first-party statement from the account rather than an independent assessment.

Diagnose the real problem before you switch

Not every frustration with a recruitment system calls for a replacement. The case points to three distinct failure types, and they need different responses. Integration failure means the system will not connect to the tools your team already uses — that is usually a platform constraint and hard to fix from the inside. Usability failure means the software works but costs too much time to operate — sometimes training or configuration helps, sometimes it does not. Data hygiene failure means records are inconsistent or duplicated — that can often be cleaned up without changing platforms, but it will recur if the new system does not enforce better structure. Identifying which of these you actually have prevents a migration that solves the wrong problem.

A checklist for evaluating a recruitment ATS + CRM

Use these questions in a demo or trial, and ask for a concrete answer rather than a general one.

Worked example: mapping the firm's experience to a trial

Suppose your team runs a retained search and currently keeps candidate notes in a mix of email and a legacy database. In a trial of a new ATS + CRM, you would test three things against this case. First, connect the tools your team already uses daily and confirm the connection works in practice, not just on a feature list — the original problem here was a system that would not integrate with Slack and Zoom. Second, log activity against one live role and check whether a colleague can see the current state without asking you. Third, take twenty candidate records and confirm they can be structured consistently enough that a search returns the right people quickly. If all three pass, the trial has tested the same ground the firm described; if one fails, you have found the specific gap to raise before committing.

Looking ahead

The firm's stated plan is to go deeper into the platform's capabilities rather than stop at the initial gains. That is a reasonable expectation for a system that is meant to be configured around a business rather than used as delivered. For teams considering a similar move, the useful takeaway is the sequence: identify the specific failure, test the replacement against that failure, and only then judge the broader feature set.

Frequently asked questions

What system did Clare Persey Recruitment use before switching?

The firm used Access RDB Recruitment for six years before moving to an ATS + CRM.

What was the main problem with the previous system?

The team found it did not integrate with tools they used daily, including Slack and Zoom, and they wanted more automation of routine tasks.

What improvements did the firm report?

The account describes a more intuitive system, better team visibility through activity logging against roles, and a clearer candidate database that supported faster matching and more proactive headhunting.

Does a cluttered candidate database always mean you need a new platform?

No. Data hygiene problems can sometimes be fixed within the existing system. The case is useful because it separates integration problems, usability problems and data problems, which need different responses.