Building a recruitment CRM shortlist

A recruitment CRM shortlist is a selection of systems you have a reason to investigate further. Start with the work and agreements your agency depends on. Ask each supplier to demonstrate the same situation, then record the evidence and the unanswered questions. You may find that no option is ready for a next round yet.

Search for the best recruitment CRM and you’ll quickly find names beside rows of ticks. Those lists can give you a starting point. A tick against ‘relationship management’, though, won’t tell you whether a colleague can pick up a client conversation during an unexpected absence.

Key takeaways

• Use your existing requirements and decide what would rule an option out.
• Give each supplier the same working situation to demonstrate.
• Separate what you’ve seen from written assurances and unanswered questions.
• Decide what the next round must establish before you consider a contract.

Which requirements can rule a system out?

Separate conditions your agency needs to operate from preferences that would make work more pleasant. An exclusion criterion describes a limit you can’t accept. Agree it before the demo so an attractive screen or discount doesn’t quietly change the basis of your decision later.

Use the requirements you’ve already gathered. This isn’t the moment to create a second long feature inventory. You might need two teams to serve the same client without exposing confidential notes to one another. Or you may need candidate and client information in a usable form when leaving the service.

Specify what counts as evidence. ‘Has permissions’ is vague. ‘Checked which notes appear using a test account’ gives you an action to carry out. Missing evidence leaves the requirement open; it doesn’t necessarily establish that the product fails it.

What should every supplier demonstrate?

Choose a familiar situation involving several people or records. Ask to see it completed, including a change or handover. This reveals how the parts of the work connect. A tour of separate screens can leave you guessing about what happens between them and how a colleague carries on.

Here’s a fictional example. Recruiter Daniel is unexpectedly away. A colleague takes over a client who wants to change a vacancy, while a candidate is waiting for a promised call. The colleague needs to understand the client agreement, follow up with the candidate and find the updated vacancy afterwards.

Using fictional information, ask the supplier to show:

1. Where the colleague finds the client agreement and the relevant contact.
2. How they identify the candidate awaiting a response.
3. What changes when they update the vacancy.
4. How Daniel can see what happened when he returns.

Add a difficult situation your own agency encounters, such as missing information or a colleague with limited access. This example isn’t a universal CRM test. It shows how to turn a feature label into a task you can observe.

Let the people who will use the software ask questions. A director can assess the business direction; a recruiter will notice whether the next step is clear without a supplier repeatedly pointing out where to click.

How should you record the evidence?

Give each observation a clear status. You may have seen something work, received written confirmation, not investigated it yet or established that it fails your requirement. Those distinctions explain why an option remains on the shortlist and what uncertainty you still need to resolve before going further.

Use an empty log like this one. Refer to a specific file, dated note or relevant document. A supplier’s general homepage is too broad to support a precise conclusion.

Question	Evidence to request	Status	Next action
Can a colleague take over the client conversation?	Completed demo scenario, including date and test role	Not assessed	Recruiter follows the handover
What can each team see?	Test accounts and relevant permissions documentation	Not assessed	Check access with two roles
What can we take with us if we leave?	Sample export and applicable contract terms	Not assessed	Review fields, files and relationships
What does implementation require from us?	Plan naming tasks, dependencies and responsibilities	Not assessed	Confirm available capacity
What does this scope cost?	Dated quote with users, usage and conditions	Not assessed	Align the assumptions

Label a roadmap item as planned. A promise about later is different from something you can inspect today. If that function is needed before your team can start, make the next decision depend on it.

Be precise about claims that software ‘works with our data’. A demo using one sample file doesn’t establish what happens to all your documents, history and relationships. Record what the test covered and which situations remain untested.

What belongs outside the product demo?

Some questions need evidence beyond a screen demonstration. Contract terms, security responsibilities and incident support are examples. Ask for suitable documentation and involve the colleague who can assess it. Access to a trial account tells you little about the agreements that would govern your service.

The UK NCSC’s guidance on choosing a cloud provider explains how to assess security assurance using evidence. A website logo or certificate isn’t a complete assessment of your intended use. Check what the supplied evidence covers and which responsibilities remain with your organisation.

For exports, ask how you’ll receive the files, what help is available if something is missing and which charges or time limits apply. A list of candidate names might exclude the associated documents or relationships. Ask the supplier to explain those details using a sample.

For cost, align the assumptions: who needs access, what usage is included, which services are one-off and what happens at renewal? You don’t need to predict a return on investment during this round. You do need to know whether two quotes cover the same work.

When is the shortlist ready?

Your shortlist is ready for a next round when you can explain why each remaining option fits and what you still need to check. There’s no required number of suppliers. Adding a name simply to fill the list does little if that option already fails a condition you cannot compromise on.

Discuss the open points with the people who will use, manage and approve the software. A significant unknown needs a focused test or written agreement. Extra ticks against less important preferences don’t resolve it.

Use this decision note:

This option goes forward because [observation] meets [requirement]. Before deciding to buy, we will check [open question]. [Person or role] will assess that evidence. If [exclusion criterion] cannot be met, this option stops.

You can also decide to keep your current approach for now. Perhaps your team hasn’t yet agreed on the workflow the software is meant to support. Settling that question can be more useful than booking another demonstration.

For an agency managing candidate and client relationships together, Simply’s ATS and CRM provides connected objects and relationships, custom fields for your specialism and pipelines for tracking progress. Use Daniel’s handover to decide which records and permissions your team needs. Bring that scenario when you request a demo.