Recruitment prospecting that doesn’t become a list nobody works
Prospecting is a prioritization problem.
This guide gives you a simple process to define your ideal client profile, build a target-account universe, identify hiring activity, and separate fit from right-now timing. Less list-building. More useful outreach.
A repeatable recruitment prospecting process (7 steps)
-
Define your Ideal Client Profile (ICP) with “yes / no” rules
Start with rules your team can actually use. A good ICP should say what to exclude, not just what looks attractive.
ICP inputs to decide:
- Role families: e.g. backend engineers, warehouse supervisors, clinical coders
- Seniority band: entry, mid, leadership
- Geography: where you can place (and where you can’t)
- Company type: product vs services, regulated vs not, on-site vs remote-first
- Hiring motion: steady BAU hiring vs project bursts
- Commercial fit: fee tolerance, typical salary bands, volume potential
Write 5–10 hard “no” rules (examples):
- “No single-site restaurants”
- “No roles under $X salary band”
- “No companies with fewer than Y employees”
If your ICP doesn’t change who makes the list, it isn’t an ICP. It’s a description.
-
Build a target-account universe (small enough to work)
You don’t need thousands of companies. You need a list your team can research, monitor, and contact properly.
Two good starting sizes:
- Solo/lean team: 50–150 accounts
- Agency BD team: 200–500 accounts split by patch
Where your first universe comes from:
- Past clients you’d happily win again
- Competitors’ customers (the company, not the agency)
- Companies already hiring in your role families
- Local/regional “repeat hirers” (the ones always building)
Add a structure from day one:
- Account owner (one name)
- Segment (A/B/C)
- Primary role families
- Core locations
- A “why us” note (one sentence)
The list is not the work. The workflow is the work.
-
Research each account fast: 15 minutes, not an afternoon
You are not writing an analyst report. You need enough context to score the account and write outreach that sounds relevant.
Use a consistent template:
- What they sell / build (1 sentence)
- Where they operate (HQ + key hiring locations)
- Teams you can help (functions that map to your desk)
- Hiring constraints (shift patterns, on-site, clearance, licensing)
- Recent changes (growth announcements, expansion, new site)
Output: a short account note you can copy into your CRM.
If the only reason you can give is “I saw you’re hiring”, keep researching.
-
Identify hiring activity (and classify it)
Hiring activity is not one thing. One company can show low demand in one team and heavy demand in another.
Look for signals you can observe repeatedly:
- New roles posted on the company career page
- Reposted roles (hard-to-fill or persistent demand)
- Multiple roles in the same function/location (team build-out)
- New sites, expansions, or reorganisations mentioned in press/news pages
Classify the hiring into one of three buckets:
- Always-on (steady flow; best for long-term relationship building)
- Burst (sudden clusters; best for timing-based outreach)
- Backfill (single roles; can be real but usually lower leverage)
The bucket matters more than the raw job count.
-
Separate “fit” from “right-now opportunity” (two scores)
Most prospecting scores get messy because they mix everything together.
Use two independent scores:
A) Fit score (0–5): how well they match your ICP
- Strong role-family match
- Your placements are credible there
- Locations you cover
- Salary/fee fit
B) Timing score (0–5): how urgent the outreach is this week
- New cluster of roles
- Reposts over multiple weeks
- Hiring-related company changes
- Multiple teams hiring the same function
How it changes behaviour:
- High fit, low timing: add to monitoring cadence + light touches
- Low fit, high timing: don’t get distracted (or only pursue if strategically important)
- High fit, high timing: priority outreach
This is how you stop a large list turning into guilt and admin.
-
Turn priority accounts into an outreach plan your team will actually run
Once you have Fit + Timing, the next action is easier to choose.
Create 3 account tiers:
- Tier A: high fit + high timing (work now)
- Tier B: high fit + mixed timing (work every week)
- Tier C: everything else (monitor; don’t spend calls)
Define minimum outreach standards per tier:
- Tier A: 3–5 touches across 10–14 days (email + call + LinkedIn), with role-specific relevance
- Tier B: 1–2 touches per month, value-led (market info, candidate availability, salary notes)
- Tier C: no active sequence; only react if timing changes
Make handoff explicit:
- Who owns first contact?
- Where do notes live?
- What counts as “qualified to progress” vs “keep warm”?
Prospecting works when the CRM reflects the plan. Not when the plan sits in someone’s head.
-
Monitor accounts over time (so timing comes to you)
A lot of good BD comes from being early and consistent.
Set up a monitoring loop that updates your Timing score without manual checking every page.
Practical cadence:
- Tier A: check weekly (or daily if you have automation)
- Tier B: check every 2–4 weeks
- Tier C: check monthly or only when something changes
What to monitor:
- The career pages and job boards that matter for that company
- Hiring-related news pages and press rooms
When timing changes, the next step should be clear: move the account from Tier B to Tier A and start the sequence.
Prioritization frameworks that keep prospecting honest
A simple account scoring sheet (copy/paste)
Use a scorecard you can fill in in under 5 minutes after research.
Fit (0–5)
- Role match: 0–2
- Location match: 0–1
- Credibility: 0–1 (case studies / previous similar placements)
- Commercial fit: 0–1 (salary band, volume, typical fees)
Timing (0–5)
- New roles posted recently: 0–2
- Role clusters / multiple similar roles: 0–1
- Reposts / persistent open roles: 0–1
- Hiring-related company changes: 0–1
Decision rule:
- Fit 4–5 + Timing 4–5: immediate outreach
- Fit 4–5 + Timing 0–3: monitor + nurture
- Fit 0–3: only pursue with a strategic reason
Don’t confuse “hiring” with “buying recruitment support”
A company can be hiring and still not be a good agency prospect this week.
Treat hiring activity as a timing signal, not proof that they need external recruitment support.
Your prospecting workflow should produce three outputs
If you’re doing real prospecting, you should be able to show:
- A target-account list with clear ownership
- A ranked queue for this week’s outreach (Tier A)
- A monitoring list that feeds the queue over time
If you only have #1, you don’t have a workflow. You have a list.
Where RecruitmentSignals fits (if you want monitoring)
If manual checking is slowing you down, RecruitmentSignals can monitor the career pages and public sources you configure, extract job listings from those pages, filter them with keyword matching, and send a daily digest by email when there’s something to send. It can also send alerts via webhooks, and generate shareable dashboards and trend reports for teams who opt in.
That gives your Timing score a regular input without opening the same career pages again and again.
FAQ: recruitment client prospecting
How many target accounts should we start with?
Start with a number you can research and monitor properly.
- If you’re a solo 360: 50–150
- If you’re a small BD team: 200–500, split by patch or vertical
If you can’t explain why each account is on the list, the list is too big.
What’s the difference between “fit” and “opportunity” in prospecting?
Fit is “would we want this client if they were hiring?” (ICP match).
Opportunity is “is there a reason to reach out right now?” (timing).
Keep them separate. High timing without fit creates busywork. High fit without timing belongs in monitoring and nurture.
What should we track in the CRM for each prospect account?
Minimum fields that make prospecting runnable:
- Account owner
- ICP segment / vertical
- Fit score + 1-line justification
- Timing score + what triggered it
- Last touch + next planned touch date
- Notes on teams/locations you can help
If your CRM doesn’t show the next action, the process will drift back to random outreach.
How do we identify hiring activity without spending hours on research?
Pick a small set of sources you can check repeatedly:
- The company career page (new roles, clusters, reposts)
- The company’s press/news pages (expansions, new sites, hiring plans)
Then score Timing. You’re not trying to read everything. You’re trying to catch repeatable patterns.
How often should we revisit accounts that aren’t hiring right now?
Use a tiered cadence:
- Tier A: weekly checks
- Tier B: every 2–4 weeks
- Tier C: monthly (or only when something changes)
The aim is to be early when timing changes, not to send endless “checking in” messages.
Can RecruitmentSignals tell us which companies use recruitment agencies?
No. RecruitmentSignals monitors the public sources you configure, such as career pages and hiring-related news pages, then turns what it finds into filtered alerts and trends. It doesn’t know whether a company uses agencies.
How does RecruitmentSignals handle people/contact info on job pages?
If a public job detail page includes a name, title, or reporting line, RecruitmentSignals may extract it as part of the page content. This is opportunistic extraction from public pages. It is not a people database, and it is not guaranteed for every role.
Related content
Want your target accounts monitored automatically?
RecruitmentSignals monitors the career pages and public hiring sources you configure, extracts job listings, filters them with keywords, and sends a daily digest when there’s something to send. You can also push signals into your workflow with webhooks, and share results and trends with tokenized dashboards.
If your team keeps checking the same pages by hand, this is the part we can take off your plate.