How to Choose the Best Recruitment Process Outsourcing Company

April 14, 2026
Min Read time

At SquareLogik, we've seen what happens when organisations choose an RPO company based on impressive presentations rather than the right questions. The contract gets signed, the mobilisation begins, and six months later the metrics are disappointing and nobody's quite sure whose fault it is. This guide covers what to evaluate, what to probe, what to ignore, and what the contract needs to say before you commit.

Table of Contents

Here is how most organisations choose an RPO company.

They put out a request for proposal. Three or four providers respond with polished decks, impressive client logo carousels, proprietary methodology names, and promises of transformative hiring outcomes.  

Someone from each provider does a confident presentation. The procurement team scores against a weighted criteria list.  

The one with the highest score — or the lowest price, depending on which way the wind is blowing that quarter — gets the contract.

Twelve months later, the metrics are underwhelming.  

The account manager has changed twice. The hiring managers are quietly going around the process. And the organisation is staring at an exit clause that makes leaving more painful than staying.

This is not a rare story.

Choosing the best RPO company for your organisation requires asking different questions from the ones most RFP processes ask. Not "how big is your global footprint?" but "who specifically will work on our account and what have they placed in the last six months?" Not "what is your methodology?" but "show me a client at similar volume to ours and tell me what their quality of hire metrics looked like twelve months into the engagement."

The gap between the pitch and the reality is where most poor RPO decisions live. This guide is about closing that gap before you sign anything.


Start With the Problem You're Trying to Solve

Before you evaluate a single RPO company, spend an hour getting precise about what you're actually buying.

Not "we need to improve our recruitment" — that's a category, not a problem. The specific problem.  

  • Time to hire is too long and we're losing candidates to faster-moving competitors.  
  • Quality of hire is inconsistent across teams and we can't work out why.  
  • We're scaling fast, need fifty hires in six months, and our internal team can't absorb the volume.  
  • Agency spend is unsustainable and we need a structural alternative.  
  • Compliance is a bottleneck and candidates are dropping out before they start.

Each of these problems has a different solution. And each solution requires different things from an RPO provider.  

A provider excellent at high-volume, process-driven hiring may be mediocre at the specialist, passive-candidate-heavy searching required for senior technical roles. A provider with deep compliance infrastructure for healthcare may have no relevant experience in fintech. A provider set up for enterprise multinational hiring may be completely the wrong scale for a 200-person company with thirty annual hires.

If you start the evaluation without being precise about the problem, you will evaluate providers against the wrong criteria and select the one that presented most compellingly rather than the one that will actually fix what's broken.


The Questions to Ask in the Request for Proposals Process

Standard RFP scoring criteria tend to cluster around things that are easy to measure and hard to interpret: company size, years in business, number of countries covered, technology partnerships, client retention rate. These are fine as background checks. They're not sufficient as selection criteria.

Here are the questions that tell you what you need to know.

Who will work on our account?

Not which partner presents in the pitch meeting. Not which senior figure signs the contract. Who are the actual recruiters, account managers, and sourcers who will run your day-to-day process? What are their names? What are their backgrounds? What roles have they placed in your sector in the last twelve months?

This question makes RPO sales teams visibly uncomfortable, which is itself informative. The best providers answer it specifically and confidently. The others deflect to team capacity, methodology, and training programmes — all of which tell you about the factory, not the product.

Can we speak to a reference client at similar volume and complexity?

Not the reference client the provider selects, who has been thoroughly pre-prepared and will tell you the engagement is going well. A client you find independently — ask for a list of current clients in your sector or at your scale and call one that isn't on the curated reference list. The conversation that results is worth considerably more than any case study.

What does your quality of hire data look like for placements in our sector?

Not just time to hire and cost per hire — those metrics tell you about process speed and efficiency. Ask about retention at six months and twelve months. Ask about hiring manager satisfaction scores. Ask what happened when a placement didn't work out and how they managed it. If they can't produce specific quality of hire data for comparable placements, either they haven't been measuring it or they don't want to show it. Neither is reassuring.

How do you handle the brief?

Ask them to describe their process for defining the hiring brief with a new client. If the answer is primarily about job description review and role profiling, probe further. A brief that only captures skills and experience isn't a brief — it's a job description with a different name. The best RPO providers spend meaningful time understanding what success looks like in the role, the team dynamics, the cultural environment, and the realistic candidate market. Ask how long this typically takes and what questions they'd ask your hiring manager. The answer reveals a lot about how they'll actually approach your roles.

What happens when a hire doesn't work out?

Every RPO provider has a guarantee policy. Most guarantees involve rerunning the search at no additional cost if a placement leaves within a defined period. Understand the period, the conditions, and what "rerunning at no cost" actually means in practice — does it include sourcing from scratch, or just processing referrals you provide? Also ask how frequently they invoke this guarantee. An honest answer to that question is considerably more useful than the policy document.

What does the exit clause look like?

Ask this before you're negotiating. The exit provisions in an RPO contract are often where the real commercial risk sits. Minimum notice periods, data return obligations, technology dependency at contract end, staff TUPE considerations if the provider has recruiters embedded in your team — these are not edge cases. They're the difference between a partnership you can exit if it's not working and one that's structurally very difficult to leave.


Evaluating Sector Expertise in RPO Companies

One of the most important — and most undersold — factors in RPO selection is genuine sector expertise.

An RPO provider that "works across all industries" is a provider with generalist recruiters who can run a process in any sector. That's a different thing from a provider with deep specialist knowledge of your talent market, your candidate community, and the specific compliance or credentialling requirements that apply to your hires.

The distinction matters most in three situations.


When your roles are specialist or scarce.

If you're hiring data scientists, clinical psychologists, cloud security architects, or any role where the qualified candidate pool is small and largely passive, you need sourcers who have relationships and credibility in that community — not generalists who can construct a Boolean search and hope. Ask specifically: how many roles at this level in this discipline have you filled in the last year? Who on your team has personal relationships with candidates in this space?


When compliance requirements are sector-specific.

Healthcare, financial services, legal, education — these sectors have compliance requirements that generic recruitment processes aren't built around. A provider that adds a compliance checklist to a standard process is not the same as one that has built their process around the compliance requirements from the start.


When employer brand is sector-specific.

The way an organisation presents itself to candidates in professional services is different from how it presents in creative industries, in technology, or in the public sector. An RPO provider who doesn't understand those cultural registers will present your employer brand in ways that either feel generic or actively miss the mark with the candidates you're trying to reach.

Ask every provider for specific examples of comparable roles filled in your sector. Not case study summaries. Specific roles, specific timelines, specific quality metrics. Then call the client and verify.


Evaluating Technology in RPO Companies

Most RPO providers lead with technology in their pitches, because it's a visible and impressive thing to demonstrate. Proprietary platforms, AI-powered matching, real-time analytics dashboards — the technology story is compelling and often genuinely useful.

It's also frequently oversold. Here's how to cut through it.

What does the technology actually do in the process?  

Not what it can do in principle — what does it do in your engagement, day to day? Which decisions does it inform? Which stages does it automate? Where does human judgement take over, and on what basis?

Does the technology produce better candidates or just faster process?  

Speed without quality improvement is not a technology benefit — it's a process change. Ask for evidence that their technology has measurably improved quality of hire outcomes for clients, not just compressed time to hire.

What technology do you expect us to bring, and what do you provide?  

If the provider expects to integrate with your ATS, understand what that integration actually means — data flows, access levels, system compatibility — before assuming it's seamless. If they're providing an ATS as part of the engagement, understand what happens to your candidate data when the engagement ends.

Is AI used in screening, and if so, how is bias monitored?  

AI screening tools can introduce bias if the training data reflects historical hiring patterns that weren't themselves unbiased. Any provider using AI in early-stage screening should be able to explain how they monitor for bias, what their oversight process looks like, and what human check exists on AI-generated recommendations.

Technology is an amplifier. It makes a good process faster and a bad one more consistently bad. The technology story should follow the quality story, not precede it.


Finding RPO Agencies for Scale and Volume

This is a selection factor that people often get backwards.

The instinct, particularly in large organisations, is to choose the biggest, most established RPO provider — the one with the global footprint, the enterprise client list, and the headquarters in a glass building. Safety in scale.

The practical reality is that the largest RPO providers are optimised for the largest clients. Their processes, their account management structures, their technology stacks, and their incentive models are built around enterprise-scale engagements. If you're a 500-person organisation hiring forty people a year, you are not their priority client. You may not be able to get their best talent. You may find that your engagement is managed by a team that's learning on your account because their senior people are busy elsewhere.

Equally, choosing a small boutique provider for a large, complex, multi-geography engagement is a different kind of mismatch. The provider may have excellent people and real expertise, but insufficient infrastructure to deliver at the volume and coordination level the engagement requires.

The best fit is a provider whose typical client is roughly your size, with roughly your hiring volume and complexity. Ask them directly: where does our organisation sit in your client portfolio? Are we a large client, a mid-sized client, or a small one? What does that mean for how the account will be resourced and who will run it?

The honest answer to that question is more useful than any reassurance about being treated as a valued partner.


Asking About Diversity, Equity, and Inclusion

Most RPO providers have a DEI section in their pitch. Most DEI sections in RPO pitches describe commitments, frameworks, and values rather than results.

What you want is results. Specifically:

What does the diversity of shortlists actually look like across their current client base? Not across all hires — shortlists, which is where sourcing strategy determines who gets assessed in the first place.

What sourcing channels do they actively use to reach underrepresented candidates? Not what channels they're aware of — which ones do they actually use in practice?

What structured assessment processes do they use to reduce bias in evaluation? And are those processes verified against outcomes, or implemented on faith?

How do they handle a client brief that — intentionally or not — contains criteria that would disproportionately filter out diverse candidates?

A provider who can answer these questions specifically, with data and examples, has actually operationalised their DEI commitment. A provider who answers them with mission statements and training initiatives has a policy, not a practice.


Contract Terms Worth Negotiating Before You Sign

The commercial negotiation in most RPO selections focuses almost entirely on price. The contract terms that actually determine how the relationship functions — and how painful it is to exit — get less attention than they deserve.


Performance-linked terms matter.

If the contract specifies time to hire and cost per hire targets but nothing about quality of hire, you have a contract that rewards speed without accountability for outcome. Push for quality metrics — retention at six and twelve months, hiring manager satisfaction scores — to be included in the performance framework. The provider's willingness to include these tells you a lot about their confidence in their own quality.


Exclusivity provisions deserve scrutiny.

Some RPO contracts require you to use the provider for all hires within a defined scope. If you have specialist roles where a sector-specific agency or executive search firm would genuinely outperform the RPO provider, you want the flexibility to use them. Understand where the exclusivity applies and where it doesn't.


Data ownership is non-negotiable.

Candidate data collected during the engagement — applications, assessments, correspondence — should be clearly yours, available in a usable format at contract end, and not retained by the provider in ways that create competitive conflicts. This is increasingly important as talent pipeline data becomes a strategic asset.


Transition provisions determine how gracefully you can exit.

If the engagement ends — whether because it worked and you're bringing the function in-house, or because it didn't and you're moving on — what does the handover look like? How long does it take? Who owns the in-flight searches? These aren't hypothetical edge cases. They're scenarios with a real probability of occurring and significant cost implications if they're not covered in the contract.


Review and termination rights give you leverage throughout the relationship.

Annual performance reviews with defined remediation processes, and a termination right tied to sustained underperformance, keep the provider accountable throughout the engagement rather than only at the point of renewal.


RPO Red Flags to Walk Away From

Not every red flag is a deal-breaker. Some are just signs that the conversation needs to go deeper. But a few are worth treating as signals to slow down considerably.

A provider that can't name specific people who will run your account during the pitch is a provider that either hasn't assigned the resource yet or is pitching capacity they don't yet have. Both are problems.

A provider that resists reference conversations with clients you identify yourself — rather than clients they suggest — is a provider whose reference list doesn't represent the full picture of their performance.

A provider that can't produce quality of hire data beyond time to hire and cost per hire is either not collecting it or not prepared to show it. In either case, quality measurement is not a core part of how they operate.

A provider that dismisses your concern about exit clauses as "we're confident in the relationship" is a provider that knows the exit clauses are onerous. Confidence in a relationship is not a substitute for fair exit terms.

A provider that prices significantly lower than comparable alternatives without a clear explanation of how they're achieving that cost structure is either about to deliver a significantly reduced service or is pricing to win the contract and renegotiate later. Both happen. Ask the question.


How SquareLogik Approaches This Conversation

We start every prospective engagement by trying to understand whether we're genuinely the right fit — not in a performatively humble way, but because placing ourselves in an engagement where we're not equipped to deliver is bad for the client, bad for the candidates, and bad for us.  

We'd rather have an honest conversation about whether something else might serve you better than win a contract we'll spend the next year underdelivering against.

We specialise in combining AI-assisted sourcing and structured quality tracking with human recruiters who know their markets. We work best with organisations that have consistent hiring needs across specific functions, that care about quality of hire as much as speed, and that want a recruitment partner rather than a procurement supplier.

If that sounds like your situation, the conversation is worth having. If it doesn't, we'll probably tell you so — and point you toward something that fits better. Which is, honestly, how this choice should work.


Frequently Asked Questions

How do you choose the best RPO company for your organisation?  

Start by being precise about the problem you're trying to solve — not "improve recruitment" but the specific failure: slow time to hire, inconsistent quality, unsustainable agency spend, compliance bottlenecks, or volume your internal team can't handle. Then evaluate providers against that specific problem rather than generic capability. The best RPO company for your organisation is the one whose expertise, scale, and sector knowledge match your actual situation — not the one with the most impressive presentation or the largest global footprint.

What should you look for when evaluating RPO companies?  

The factors that matter most are: who specifically will work on your account (not just who presents in the pitch), demonstrated quality of hire outcomes in comparable placements, genuine sector expertise rather than cross-industry generalism, scale fit with your hiring volume, fair and transparent contract terms including exit provisions, and the ability to speak to reference clients you identify yourself rather than ones the provider selects. Technology and methodology matter, but they're secondary to the quality and experience of the people actually running your recruitment.

What questions should you ask an RPO provider?  

The most revealing questions are: Who are the specific recruiters and sourcers who will work on our account? Can we speak to a current client at similar volume that we identify, not one you suggest? What does your quality of hire data look like for placements in our sector — including retention at six and twelve months? How do you define and refine the hiring brief? What happens contractually when a placement doesn't work out? And what does the exit clause look like? Providers who answer these specifically and confidently are worth shortlisting. Those who deflect are telling you something useful.

How important is sector expertise when choosing an RPO company?  

Critically important for specialist, compliance-heavy, or senior hiring. A generalist provider can run a recruitment process in any sector — they can source CVs, schedule interviews, and manage communications. A sector specialist has relationships with the relevant candidate community, understands the compliance requirements from the inside, and knows how to present your employer brand in the register that resonates with the people you're trying to hire. The difference shows up most in the quality and relevance of shortlists rather than in process efficiency.

Should you choose a large or small RPO company?  

Neither is automatically better. Large providers are optimised for large clients and have the infrastructure for complex, multi-geography, high-volume engagements — but they may deprioritise smaller clients and assign less experienced teams to mid-market accounts. Smaller boutique providers often have deeper expertise and more senior attention per client, but may lack the scale for significant volume or geographic breadth. The right fit is a provider whose typical client is roughly your size and complexity. Ask directly where your organisation would sit in their client portfolio and how the account would be resourced.

What contract terms are most important when selecting an RPO provider?  

Performance metrics that include quality of hire — not just time to hire and cost per hire. Data ownership provisions that ensure candidate data is yours and returned in usable form at contract end. Exit and termination provisions that are fair and don't make leaving prohibitively expensive if the engagement underperforms. Clarity on what's included in the headline price versus what's additional. And defined review rights throughout the contract, not just at renewal. The commercial negotiation usually focuses on price; the terms that determine how the relationship actually functions rarely get the same scrutiny.

What are the warning signs of a poor RPO company?  

Inability to name specific people who will run your account during the pitch. Resistance to reference conversations with clients you identify independently. No quality of hire data beyond time to hire and cost per hire. A price significantly below comparable alternatives without a clear structural explanation. Exit clauses defended with confidence in the relationship rather than fair terms. And a pitch that's heavy on proprietary methodology names and light on specific, verifiable outcomes from comparable client engagements. None of these individually is disqualifying, but more than two together should prompt significantly deeper scrutiny.

Related Articles

August 2026
Read time

How to Find Candidates as an SME Competing With Larger Employers

SMEs can't outspend large employers. But they can out-offer them on things that may matter more. Here's how to find candidates as a small business competing for the same talent.

SMEs assume the competition is about money and brand recognition. A large employer has both. SME has neither. Therefore, the SME loses.  

This logic is tidy, plausible, but mostly wrong.

The candidates who are exclusively motivated by salary and brand prestige are going to the large employer regardless of what you do. But that is not most candidates.  

Most candidates (particularly the experienced, mid-career professionals who make the best hires) are weighing a more complex set of factors:

  • Proximity to decision-making.  
  • Variety of work.  
  • Speed of progression.  
  • The ability to see the impact of what they do.  
  • A culture that doesn't require three approvals to change the font on a slide.

On every one of these dimensions, a well-run SME can and regularly does outperform a large employer. The problem is that most SMEs don't know this, don't say it, and therefore don't attract the candidates for whom it would be decisive.

This article is about fixing that.

The Advantages of Recruiting as an SME

Before sourcing a candidate, get clear on what your genuine competitive advantages are.  

SMEs offer things that large employers structurally cannot.

A new hire at a 40-person business will meet the founder in their first week, probably work directly with senior leadership, and have their work visible to the whole organisation almost immediately. A new hire at a 40,000-person business will spend three months learning which Slack channel to use.

Speed of progression is real and measurable.

An ambitious person who joins a growing SME can move from a mid-level role to a leadership position in two to three years if they perform. The same person at a large employer is probably queuing behind people who got there before them, waiting for a headcount approval, or competing in a talent programme with forty other people who are also quite good.

Variety of work is another genuine differentiator.

At a large employer, roles are defined, scoped, and bounded. At an SME, people routinely do things that weren't in their job description because the business needs it and they're the right person. For candidates who want breadth and interest, this is genuinely attractive — not a consolation prize.

The reason these advantages don't translate into hiring outcomes for most SMEs is that they don't communicate them. The job ad lists the same competencies any large employer would list. The interview process is the same. The offer lands next to a larger one and loses on the only dimension being compared.

Lead with what you actually win on.

Write Job Ads That an SME Would Write

Large employers write large employer job ads. They describe the role in the abstract, list twenty requirements, reference the company values from the careers page, and promise a "dynamic and fast-paced environment," which has described every job posted since the internet was born.

An SME job ad written honestly is a competitive advantage. Write it like a person who knows the role, the team, and the culture... because you do.

  • Describe the specific work the person will be doing in the first three months.  
  • Name the team they'll be joining, what the team is working on, and what's interesting about the problem.  
  • Be honest about the hard bits, like the pace, the ambiguity, the fact that there isn't an established process for everything and sometimes they'll have to build it.  

The candidates who read that and think "that sounds like exactly what I want" are your candidates. The ones who think "that sounds chaotic" were not going to thrive there anyway.

  • Also, mention salary. Not a range so wide it communicates nothing, but a realistic one.

Candidates filter by salary before they read anything else. Hiding it costs you application volume at the relevant level and wastes everyone's time at the relevant stage.

Specificity attracts the right people and filters out the wrong ones. A generic job ad does the reverse.

Use the Sources Where Your Candidates Are

As an SME, if you use the same channels large employers use, you can't wonder why you're competing with vastly better-known names for the same pool of active jobseekers.

Your own network is the most underused source you have.  

The founder, the leadership team, the existing employees — these people know people. A direct message from a founder to someone they respect in the industry, explaining what they're building and why they'd be a good fit, converts at a rate that no job board matches. It is also free.

Employee referrals are the extension of this. Your current team knows the field. They know who the good people are, who might be ready for a move, who would fit the culture. A referral scheme with a meaningful incentive and a dead-simple process for making introductions consistently produces the highest-quality candidates at the lowest acquisition cost. Most SMEs have a referral programme in theory. Most of them don't actively use it.

Niche job boards and communities outperform generalist boards for specific roles.  

A software engineering role posted in a relevant developer community will reach people who are engaged with the field and not getting lost in recruiter noise. A marketing role posted in a specialist marketing community reaches people who care enough about their discipline to be there. LinkedIn remains useful for direct sourcing — searching for people in the right roles at the right organisations, and reaching out with something specific and personal rather than a template.

Local presence matters more for SMEs than for large employers.  

A large employer with a recognisable name can hire nationally without much effort. An SME hiring locally benefits from being known in its community from:

  • Sponsoring relevant events
  • The founder being a visible presence in the local business network
  • The team attending industry meetups.  

You may also want be interested in our guide on building a talent pipeline before you need it.

Use Speed to Your Structural Advantage

One thing you can do as an SME can do that most large employers cannot is move fast.

A large employer running a competitive process involves multiple stakeholders, HR sign-off at various stages, a compensation committee review, and an approval chain for the offer. The candidate experience is often measured in weeks between touchpoints. The offer, when it arrives, has been through four people and taken eleven days to generate.

An SME can interview on Thursday and offer on Friday. The decision-maker is in the building. The approval chain has one step. The offer is a conversation rather than a document that needed three rounds of review.

This is not a small advantage. The candidates worth hiring are almost always running parallel processes. They have other conversations happening. The employer who moves decisively communicates something about how the organisation makes decisions. The one that takes three weeks to confirm a second interview communicates something too.

  • Map your hiring process and identify where time is being lost.  
  • Commit to 48-hour feedback windows.  
  • Pre-book interview slots before candidates are confirmed.  
  • Have the offer conversation ready before the final interview happens, not after.  

Speed doesn't compromise quality. But indecision after a thorough process does.

Build an Employer Brand Without a Budget

An SME employer brand is built from specificity, not spend.

Candidates research employers before applying and before accepting. What they find about you on LinkedIn, on Glassdoor, from people they know, etc., shapes whether the conversation goes anywhere. You don't need a careers microsite or a video series. You need enough genuine, specific content about what it's like to work there that a curious candidate can find it.

That might be the founder writing honestly on LinkedIn about what the company is building and why. It might be the team posting about the work they do. It might be a handful of authentic employee testimonials — not corporate-approved soundbites, but real accounts of what the role involves and why the person is still there.

Glassdoor matters. A company with three reviews, two of which are complaints, is a company that loses candidates at the research stage. Encouraging current employees to leave honest reviews (not pressuring positive ones, but making it easy and normal) builds a profile that converts curious candidates into applicants.

Lastly, specificity beats polish. A founder who writes one honest, thoughtful post about what they're building and why will reach more of the right people than a careers page that could have been written for any company.

Consider Working With a Specialist Recruiter

For roles where the right candidate is likely to be passive (currently employed, not looking, not going to find you through a job ad) a good recruiter with relevant market relationships changes the equation.

The value isn't the job board access. Any SME can post to job boards without help. The value of a recruitment agency is in the ability to:

  • Reach ideal candidates who aren't visible through advertising
  • Make a credible approach that gets a response
  • Present your opportunity persuasively to someone who had no plans to move

For an SME competing with large employers in a specific talent market, a recruiter who knows that market and has existing relationships within it is levelling the playing field in the most direct way available. The large employer has brand recognition working in their favour. The recruiter has a relationship and a credible pitch working in yours.

The economics make most sense for roles that are hard to fill, business-critical, or where the cost of leaving the position vacant is significant. For broadly available roles with active candidate pools, the SME's own network and direct advertising will usually suffice.


How SquareLogik Works With SMEs

We work with a number of SMEs who are hiring in markets where larger and better-known employers are also hiring. Our role in those searches is not to help them compete on resources they don't have, but to help them compete on what they do have, and to reach the candidates for whom those things are decisive.

That means:

  • Understanding what makes the opportunity compelling before we approach anyone
  • Reaching passive candidates who wouldn't find the SME through a job board
  • Moving with the pace that SME decision-making allows, which is often considerably faster than the large employer on the other side of the same search

If you're an SME finding it hard to attract the right candidates, we can assure you that the problem is not the size of your organisation, but the story being told about it, and where that story is being told.

We can help you with that.

Frequently Asked Questions

How can SMEs compete with large employers for talent?

By leading with advantages that large employers structurally cannot offer: proximity to decision-making, genuine breadth of work, speed of progression, and a direct line between individual contribution and business outcome. SMEs that try to compete on salary and brand recognition with larger employers lose. Those that lead with what they genuinely win on, and communicate it specifically and honestly, attract the candidates for whom those things are more important than the employer's name recognition.

Where should SMEs find candidates?

Start with your own network of founders, leadership, and current employees who know relevant people in the field. Referral schemes with meaningful incentives produce high-quality, low-cost candidates consistently. Niche job boards and professional communities outperform generalist boards for most specialist roles. LinkedIn is useful for direct outreach when the message is specific and personal. For passive candidates in scarce markets, a specialist recruiter with relevant relationships is the most direct way to reach people who won't find you through advertising.

How do you write a job ad that attracts candidates to an SME?

Write it like a person, not a large employer. Describe the specific work the person will do in the first three months. Name the team, the problem, and what's genuinely interesting about it. Be honest about the hard bits such as the pace, the ambiguity, the lack of established process in some areas. Include a real salary figure. Specificity attracts the candidates who are actually right for the role and filters out those who aren't, which is exactly what a job ad should do.

Is speed of hiring actually an advantage for SMEs?

Yes, significantly. The candidates most worth hiring are almost always running parallel processes. An SME that can interview on Thursday, offer on Friday, and have a signed contract the following week is communicating something about how decisions get made there — and is consistently securing candidates that slower-moving processes lose. Pre-booked interview slots, 48-hour feedback windows, and a decision-maker who is in the building and available make speed possible without compromising the quality of the assessment.

How do SMEs build an employer brand without a big budget?

Through specificity rather than spend. A founder writing honestly on LinkedIn about what the company is building. Team members posting about the work they do. Authentic Glassdoor reviews from current employees. A careers page that describes real work rather than aspirational values. None of this requires a marketing budget. It requires the willingness to be specific and honest about what working there is actually like, which is a lower bar than most SMEs set themselves and a higher bar than most of their competitors clear.

When should an SME use a recruitment agency?

When the right candidate is likely to be passive (currently employed and not looking) and direct advertising won't reach them. When the role is hard to fill and the cost of leaving it vacant is significant. When the SME is competing in a talent market where larger employers have more brand recognition and the recruiter's market relationships level the playing field. For broadly available roles with large active candidate pools, the SME's own network and direct advertising will usually produce sufficient results without agency support.

July 2026
Read time

Why Your Job Ads Aren't Finding the Right Candidates

Most job ads describe a role rather than attract the right person for it. Here's what's filtering out the candidates you want and pulling in the ones you don't.

Most job ads are written for the wrong audience.

They describe the role in terms the hiring manager understands. They list the requirements the HR team agreed on. They include the values from the company's website. They promise a competitive salary and a collaborative environment.

And then they go live, and either nothing happens or the wrong people apply.

The reason is not the platform, the timing, or the algorithm. The reason is that the ad was written as a document about the role rather than a communication aimed at a specific person. Those are different things, and the difference determines whether the right candidates recognise themselves in it and apply.

Before diving in, you may also be interested in our article on building a talent pipeline before you need it.


A Job Description Is Not a Job Ad

This is the root cause of most underperforming job ads and it is almost never discussed.

A job description is an internal document. It defines the scope of a role, the responsibilities, the reporting line, and the requirements. It exists for HR, for the hiring manager, for compliance purposes. It describes the job from the employer's perspective.

A job ad is an external communication. It exists to persuade a specific type of person that this opportunity is worth their time. It describes the role from the candidate's perspective: what they will actually do, what they will learn, what impact they will have, and why this particular role at this particular organisation is worth considering over the alternatives they have.

Most organisations write a job description and post it as a job ad. The result is a document that is technically accurate and practically useless for attracting the people it needs to attract.

The candidates you want are reading that ad and making a decision in about thirty seconds. If what they find is a list of responsibilities and a requirements section, they are not getting enough signal about whether this is actually for them. So they move on. The candidates who apply are often those with lower standards for what they'll pursue, because they'll apply to anything that roughly fits.


You're Advertising the Requirements, Not the Opportunity

Here is a thing that appears in almost every underperforming job ad.

"The ideal candidate will have five or more years of experience in a relevant field, a proven track record of delivering results, excellent communication skills, and the ability to work independently and as part of a team."

This sentence contains no information. It is a description of every employed professional in the country. It tells a candidate nothing about whether this role is right for them, whether the work is interesting, or whether the organisation is worth considering. It is filler that exists because someone had to write something.

The requirements section of a job ad should exist to filter, not to describe. Its job is to make the right candidates recognise themselves and make the wrong ones self-select out. A list of generic competencies does neither. It includes everyone who can read and excludes nobody.

What actually works: specific, concrete requirements that reflect what the role genuinely demands. Not "experience in a fast-paced environment" but "comfortable managing three to five client relationships simultaneously with competing deadlines." Not "strong communication skills" but "able to explain technical product changes to non-technical stakeholders clearly and without condescension." Specificity filters. Generality doesn't.


The Lack of Salary Transparency

Candidates filter by salary before they read anything else on most job boards.

A job ad with no salary, or a salary range so wide it communicates nothing, loses a significant proportion of its target audience before they reach the job title. The candidate at the top of the range assumes it's below them. The candidate at the right level isn't sure it's worth their time to find out. The only candidates who consistently apply to ads without salary information are those with fewer alternatives, which is not the pool you were hoping to fish in.

The reluctance to include salary is understandable in theory. You don't want to anchor too low. You don't want existing employees to make comparisons. You don't want competitors to know your budget.

None of those concerns outweigh the cost of filtering out the candidates you actually want. The market already knows roughly what the role should pay. Tools like LinkedIn Salary, Glassdoor, and Totaljobs Salary Checker mean that candidates have access to benchmarking data whether you include a number or not. The only person who doesn't know what you're offering is the candidate reading your ad.

Include a salary range. Make it honest. The candidates who would have applied at the top end of a realistic range and been disappointed by the actual offer are not candidates you were going to place anyway.


You're Writing for Everyone and Reaching Nobody

Generic job ads attract generic applicants.

An ad written to appeal to the broadest possible pool of candidates tends to produce the broadest possible pool of candidates, most of whom are not right for the role. This feels counterintuitive. More applications should mean better odds. In practice it means more screening time, more unsuitable conversations, more time between posting and placement, and a hiring process that exhausts the team before the right person appears.

The ad that says "we're looking for an ambitious, driven, results-focused individual who thrives in a fast-paced environment" is describing a demographic that includes roughly 800,000 people currently browsing job boards. The ad that says "we're looking for someone who has rebuilt a customer success function before, is comfortable with the ambiguity of a Series A business, and wants to own a team within eighteen months" is describing maybe two hundred people and most of them will be the right person.

Writing for a specific person means accepting that the ad will put some candidates off. It is the ad working correctly.


The Culture Section that Isn't Believable

"We're a passionate team of innovators who work hard and play hard, with a culture built on trust, collaboration, and continuous learning."

Every company says this. Every single one. Including the ones where the culture is none of those things. Candidates have read this paragraph approximately a thousand times and have learned to skip it entirely.

Culture copy that is generic is worse than no culture copy at all because it takes up space, adds nothing, and signals that nobody thought carefully about what to write. The candidate's reaction is not "this sounds like a great culture" but "everyone says this."

What actually signals culture is specificity. Not what you value but how those values appear in practice. Not "we believe in work-life balance" but "our engineering team doesn't do on-call rotations and hasn't shipped a weekend release in two years." Not "we invest in our people" but "everyone gets a personal learning budget and four days a year to use it." Details that could only be true of your organisation, not of every organisation.

If you can't write something specific about your culture, that is useful information about whether you have a culture worth advertising.


The Qualifications that Usually Aren't Required

Degree requirements for roles that don't functionally require a degree. Five years of experience for a mid-level role. A specific software tool listed as essential when it's actually learnable in a week. These requirements filter out candidates who could do the job and attract candidates who have checked the boxes without necessarily being able to do it.

Requirement inflation happens for understandable reasons. Someone writes a requirement into the template and it never gets removed. The hiring manager adds things they'd like rather than things they need. HR adds degree requirements because it feels like quality assurance.

The practical effect is a narrower candidate pool, a less diverse applicant group, and the exclusion of people who would have been excellent hires. Each unnecessary requirement costs you candidates who were right but didn't quite fit the description.

Before every requirement on the list: ask whether a candidate without this could learn it within three months in the role. If yes, make it a preference, not a requirement. The list of actual requirements for most roles is considerably shorter than the list that appears in most job ads.


How SquareLogik Approaches Job Ad Quality

We work on the brief before we work on the sourcing. Part of that is making sure the external communication about the role is actually doing what it needs to do.

An ad that filters out the right candidates before they apply makes the sourcing harder, the pipeline thinner, and the eventual placement less likely to be the strongest available person. Fixing the ad is often faster and cheaper than intensifying the sourcing effort.

If your current job ads are producing too many wrong-fit applications or not enough right-fit ones, the copy is usually where the problem starts. We are happy to look at what you are currently running and tell you honestly what is likely to be causing it.


Frequently Asked Questions

Why are my job ads not attracting the right candidates?

Usually one of four reasons: the ad is written as a job description rather than a candidate-facing communication, the requirements are generic rather than specific enough to filter effectively, salary is absent or too vague to be useful, or the culture and opportunity are described in language every employer uses rather than language specific to your organisation. The ad that reaches the right person needs to be specific enough that they recognise themselves in it and clear enough about the opportunity that they know why it is worth pursuing.

What is the difference between a job description and a job ad?

A job description is an internal document describing the scope and requirements of a role from the employer's perspective. A job ad is an external communication aimed at persuading a specific type of candidate that the role is worth their attention. Most organisations post their job description as a job ad and are surprised when it underperforms. A job ad should describe what the candidate will do, what they will gain, and why this opportunity is worth considering over the alternatives they have access to.

Should I include salary in a job ad?

Yes. Candidates filter by salary before reading anything else on most job boards. An ad without salary, or with a range so wide it signals nothing, loses a significant proportion of the right audience before they reach the job title. The concern about anchoring too low or triggering internal comparisons does not outweigh the cost of filtering out candidates who would have been right for the role. The market already has access to salary benchmarking data. The only person who does not know what you are offering is the candidate reading your ad.

How specific should a job ad be?

Specific enough that the right candidate recognises themselves in it and the wrong candidate self-selects out. Generic requirements like "excellent communication skills" and "ability to work independently and as part of a team" include everyone and filter nobody. Specific requirements and a specific description of the work attract a smaller, more relevant pool and produce a better quality pipeline than a broad ad generating high application volume from the wrong people.

What should the culture section of a job ad include?

Specific, concrete details that could only be true of your organisation rather than generic statements every employer makes. Not "we believe in work-life balance" but the specific practice that demonstrates it. Not "we invest in our people" but the actual investment: a learning budget figure, days allocated to development, a promotion that happened recently. Generic culture copy signals that nobody thought carefully about what to write. Specific details signal that the culture is real enough to describe.

How do unnecessary qualification requirements affect job ad performance?

They narrow the candidate pool, reduce diversity, and exclude people who could do the job well. Degree requirements for roles that do not need degrees, experience thresholds set above what the role requires, and specific tools listed as essential when they are learnable on the job all filter out candidates who would have been strong hires. Before each requirement, ask whether a candidate without it could learn it within three months in the role. If yes, it should be a preference rather than a requirement.

July 2026
Read time

How to Build a Talent Pipeline Before You Need It

Reactive hiring is expensive and slow. Building a talent pipeline before you need it changes the cost, speed, and quality of every hire that follows. Here's how to do it properly.

Here is how reactive hiring works.

A role opens. Everyone agrees it needs to be filled quickly. A job ad goes up. Applications come in over two weeks. The recruiter spends another week screening. Interviews happen in week four. A decision is made in week six. The preferred candidate is working three months' notice. Someone starts in week eighteen.

By which point the team has absorbed the workload for four months, the manager has had three awkward conversations with the finance director, and the person who eventually starts is the best of whoever happened to apply to that specific job ad during that specific two-week window — which is a much smaller pool than the full available talent in the market.

This is not a process problem. It is a timing problem. You started too late.

The organisations that hire best aren't better at moving faster once a vacancy opens. They're better at having relationships in place before it does. That's what a talent pipeline actually is — and it is considerably more useful than the definition most people give it.


What a Talent Pipeline Is (And Isn't)

A talent pipeline is not a database of CVs collected from previous applications and left to go cold.

That is a talent archive. It sits there, dating itself, until someone searches it desperately during a vacancy and discovers that half the people in it moved on two years ago and the other half applied for something completely different.

A genuine talent pipeline is a set of active, maintained relationships with people who might be right for future roles — people who know your organisation, who have some level of existing engagement with you, and who, when the right role opens, are already warm enough to have a real conversation rather than receiving a cold approach from a stranger.

The distinction matters because the value of a pipeline is entirely in the warmth of the relationships within it. A list of names is not a pipeline. A list of names attached to a history of meaningful touchpoints, a clear sense of mutual interest, and some degree of established trust — that is a pipeline.

Building one requires deliberate effort over time. It also produces returns that compound. Every relationship built before a vacancy opens is a vacancy that costs less to fill, takes less time, and produces a stronger shortlist than starting from scratch.


Which Roles Actually Need a Pipeline

Not every role justifies proactive pipelining. The effort required is real, and spreading it across every position on the org chart is a reliable way to do none of it well.

Prioritise roles with any of the following characteristics.

They're hard to fill when vacant.

If a role has taken three months or more to fill in the past, or if the candidate pool is genuinely scarce, a pipeline is not a nice-to-have — it's the difference between a structured search and a crisis scramble. Specialist technical roles, registered managers in care, senior commercial appointments, niche engineering disciplines — these are exactly the roles that benefit most from having warm relationships in place before the vacancy opens.

They're business-critical.

A vacancy in a role that directly affects revenue, patient safety, client relationships, or operational continuity is expensive every day it remains open. Knowing who you'd call first if that role became vacant is basic risk management.

They're high-turnover.

Roles that cycle regularly — not because of organisational failure but because of sector norms, role design, or natural career progression — benefit from a perpetually warm pipeline rather than a perpetual reactive search.

They're senior.

Senior and executive roles take the longest to fill from a standing start and are the most damaged by the pressure to fill quickly. A maintained pipeline of senior relationships allows a search to begin from a position of intelligence rather than a position of urgency.

Identify your top five to ten priority pipeline roles. Focus the effort there first.


How to Source Proactively: Finding the Right People Before the Job Exists

Proactive sourcing — finding and engaging potential candidates before a vacancy is open — is the foundation of a talent pipeline. It is also the part most organisations treat as optional until they're in trouble.

The starting point is knowing who the right people are. For most roles, this means identifying individuals currently in comparable positions at comparable organisations — people who are demonstrably doing the job you'll eventually need to fill, and doing it well enough that they haven't obviously needed to move.

This market mapping can be done manually for a handful of roles or with AI-assisted tools for broader coverage. The output should be a prioritised list of people worth building a relationship with — not a mass outreach list, but a targeted group of individuals where the effort of engagement is proportionate to the value of the relationship.

Initial outreach should not mention a vacancy, because there isn't one. It should be genuine, specific, and low-pressure: an industry observation, a piece of relevant content, a shared connection who made an introduction. The goal is not to recruit — it is to begin a relationship that might eventually be relevant. This requires patience and a recruiter who understands that forcing the timeline undermines the whole approach.

Employee referrals are one of the most underused proactive sourcing channels. Your current high performers know who the other high performers in their field are. A structured referral scheme with a meaningful incentive and a clear, simple process for making introductions builds pipeline from warm intelligence rather than cold database searching.

Professional communities, events, and networks are also genuinely productive for specific disciplines. Being present in the spaces where your target candidates spend their time — industry conferences, professional associations, online communities — creates organic relationship opportunities that cold outreach doesn't replicate.

You may also want to: Read our article on how AI is changing what recruitment agencies do.


Nurturing the Pipeline: Staying Relevant Without Being Annoying

This is the part that defeats most organisations. They build a list, make initial contact, and then go quiet until a vacancy opens — at which point they reach out again, months later, asking for something.

That is not a pipeline. That is a list of people you occasionally contact when you need something.

Maintaining genuine pipeline relationships requires a different cadence. Not relentless contact — that tips into harassment — but consistent, low-pressure, value-adding touchpoints over time.

Sharing relevant industry content with a brief, genuine observation. Congratulating someone on a career milestone or a piece of published work. Making an introduction to someone they should know. Inviting them to something genuinely relevant — a roundtable, a webinar, a conversation — rather than a thinly veiled recruitment pitch.

The standard to hold this to is simple: would this contact make sense even if you never had a vacancy? If the answer is yes, it's a relationship. If the answer is only makes sense when you need something, it's still a list.

CRM systems — whether a specialist recruitment CRM or a well-maintained spreadsheet — are necessary for managing this at any real scale. Recording what you know about each person, what the last interaction was, what their career situation appears to be, and when it makes sense to reach out again prevents the pipeline from becoming an archive.


The Internal Pipeline: Succession and Development

Talent pipelining doesn't only apply to external candidates. The most immediately actionable pipeline for many organisations is internal.

Identifying which current employees could, with development, step into more senior or specialist roles — and then actively developing them toward that readiness — is a form of pipelining that costs less, produces faster time-to-productivity, and retains institutional knowledge that an external hire never has.

Succession planning for critical roles doesn't require a formal HR programme with documentation that nobody reads. It requires answering one question for each business-critical position: if this role became vacant tomorrow, who internally would be closest to ready, and what would they need to be genuinely ready within six to twelve months?

Answering that question honestly, and then investing in closing the gap, is proactive talent management in its most practical form. It also reduces external hiring pressure — which is the point.


Employer Brand as a Pipeline Tool

The organisations with the warmest talent pipelines are usually the ones where candidates already want to work before being approached.

Employer brand — the reputation an organisation has in its relevant talent market — is a passive pipeline mechanism that works at scale. A company with a strong employer brand in its sector has potential candidates who are already familiar with it, already positively disposed toward it, and already more likely to respond to a thoughtful approach.

Building employer brand for pipeline purposes means being visible in the places your target candidates spend time. Engineering teams blogging about interesting technical problems. Leaders speaking at industry events. Consistent, authentic content about the culture, the work, and the people — not a careers page written by marketing, but evidence of what it actually looks and feels like to work there.

This is a long-term investment with compounding returns. The candidate who follows your company's content for a year before being approached is a warm conversation. The candidate cold-approached without any prior awareness is starting from zero.


How to Know Whether the Pipeline Is Working

A talent pipeline that nobody measures is a pipeline that gradually becomes an archive without anyone noticing.

The metrics worth tracking are not complicated. When a vacancy opens for a priority role, what proportion of the shortlist comes from pipeline relationships rather than new sourcing? How long does it take to get to a first interview from vacancy opening for pipeline-supported roles versus non-pipeline roles? What is the offer acceptance rate for candidates sourced from the pipeline versus those sourced reactively?

If the pipeline is working, time-to-hire for priority roles should be shorter, quality of shortlist should be higher, and the cost of reactive sourcing for those roles should be falling. If those metrics are not moving, the pipeline is a list.

The feedback loop matters. A pipeline that is regularly reviewed — which relationships are warm, which have gone cold, which roles need new relationship-building effort — stays useful. One that is built once and then left runs down within twelve months as people move, change priorities, and forget who you are.


How SquareLogik Approaches Pipeline Building

We maintain talent pipelines for the clients we work with on a sustained basis — not as a theoretical capability but as a practical operating model.

For roles where we know a client's hiring needs are recurring or where the candidate pool is scarce enough to justify proactive maintenance, we build and nurture candidate relationships between searches rather than starting from scratch each time. When a vacancy opens, the first call goes to people who already know us, know the client, and have some existing level of interest — which compresses the search and produces a better quality conversation.

We also use AI to extend the mapping and identification phase — finding the right people faster, tracking market movements, and surfacing candidates whose situation may have recently changed in ways that make them newly open to a conversation.

If you're looking to move from reactive to proactive hiring for your priority roles, the conversation about what a talent pipeline strategy looks like for your specific situation is worth having before the next vacancy opens.


Frequently Asked Questions

What is a talent pipeline?

A talent pipeline is a set of active, maintained relationships with people who might be right for future roles — before those roles are open. It is not a database of CVs from previous applications. The value of a pipeline is entirely in the warmth and relevance of the relationships within it. A pipeline means that when a vacancy opens, you already have people to call who know you, have some existing engagement with your organisation, and are warm enough for a real conversation rather than a cold approach.

Which roles should you build a talent pipeline for?

Prioritise roles that are hard to fill when vacant, business-critical, high-turnover, or senior. These are the roles where reactive hiring is most expensive, most damaging, and most likely to result in a pressured appointment that doesn't hold. For broadly available roles with large active candidate pools, the investment in proactive pipelining rarely justifies the effort. Focus pipeline effort where the cost of a vacancy and the difficulty of filling it quickly is highest.

How do you proactively source candidates for a talent pipeline?

Market mapping — identifying people currently doing comparable roles at comparable organisations — is the foundation. Employee referrals from current high performers are consistently the warmest and most productive source. Professional communities, industry events, and networks create organic relationship opportunities. AI-assisted sourcing tools can extend this mapping significantly for broader or more complex pipelines. Initial outreach should not lead with a vacancy — it should be genuine, low-pressure, and add some value independent of whether a role ever materialises.

How do you maintain candidate relationships in a talent pipeline?

With consistent, low-pressure, value-adding contact over time — not relentless outreach. Sharing relevant content with a genuine observation, congratulating someone on a career milestone, making a relevant introduction, inviting them to something genuinely useful. The test is whether the contact would make sense even if you never had a vacancy. A CRM system is necessary for managing this at scale — recording interaction history, current status, and when the next touchpoint makes sense.

How long does it take to build a talent pipeline?

Meaningful pipeline relationships typically take six to eighteen months to develop to the point where they meaningfully accelerate a search. This is why the best time to build a pipeline for a critical role is before there's any urgency. Organisations that start pipelining only when a vacancy opens are still starting too late — they're just starting slightly earlier in the reactive cycle. The compounding returns of an established pipeline are most visible twelve to twenty-four months after the investment begins.

How does a talent pipeline reduce recruitment costs?

A warm pipeline reduces cost per hire in several ways: less time spent on active sourcing, shorter time-to-hire reducing vacancy costs, higher offer acceptance rates from candidates who already know the organisation, and lower agency dependency for priority roles. Reactive sourcing for a scarce-candidate role from a cold standing start is consistently the most expensive recruitment model. A maintained pipeline converts that cold start into a warm conversation — which reduces every downstream cost in the process.