Candidate CRM

Candidate rediscovery is the cheapest pipeline you will ever build, and most teams throw it away. You already paid to attract the person. They already wrote a resume, maybe sat an assessment, maybe interviewed. Then the req closed, the card disappeared, and six months later you buy the same profile from a job board.

Silver medalist candidates are the obvious example: finished second, still would have done the job. The quieter example is the SDR who applied to Account Executive too early, or the AE who needed a different territory. If your ATS cannot find them again, you do not have a CRM. You have a per-req bucket.

The problem this solves

Per-job databases pretend hiring is a series of unrelated campaigns. It is not. The same humans cycle through your market. Agencies feel this daily. In-house teams feel it the first time they backfill a role they filled last year.

Spreadsheets of "people we liked" rot. LinkedIn Recruiter is a search product, not a record of what happened inside your process. Rediscovery only works if the original application, tags, and outcome live in one place.

Aptimal keeps a candidate CRM across jobs. Skill tags are generated from what you already collected — resume and process data — so you can re-invite past applicants to a new role without reconstructing why you liked them.

How candidate rediscovery works in Aptimal

1. Candidates who apply are in the CRM, not only on that job's Kanban board.
2. Aptimal generates skill tags from the application materials so you can find "Salesforce" or "BDR" later without relying on whatever title they used that month.
3. When a new req opens, search the CRM for people who already made it past noise once.
4. Re-invite them to the new job. They are not a cold inbound. They have history.
5. If they proceed, they can sit a new assessment and book interviews on the new pipeline — you are not stuck with last year's score as if nothing changed.

This is not an outbound sequence engine. There is no drip campaign builder. If you need that, keep your marketing stack. Aptimal covers the hiring record and the re-invite.

What this looks like for an SDR req

You hired one SDR in March and had two more who cleared assessment and interview. You rejected them because there was one seat. In September you open another SDR role and a slightly more senior AE role.

Without a CRM, those two people are gone. With candidate rediscovery, you filter on the tags from their last process, re-invite the silver medalists to SDR, and only consider the AE invite if their assessment actually showed discovery skill rather than "I want to get off the phones."

You still should not re-invite someone you rejected for a knockout that still applies — no, they still do not have the work authorization you require. Rediscovery is for qualified leftover demand, not for undoing filters you were right to set.

What it replaces

Old step	What usually happens	What Aptimal replaces it with
Re-posting the same job	You buy the same applicants again	Re-invite people you already screened
"Good candidate" Slack message	Lost in a month	CRM record with tags and history
LinkedIn search for past applicants	You remember two names	Search on tags and prior process
Agency resubmitting the same talent	You pay again	Your own rediscovery first
Spreadsheet of silver medalists	Nobody updates it	The rejected-but-strong stay findable

Staffing agencies will recognize this as the job. In-house teams should steal the habit. High-volume hiring (warehouse, hospitality, trucking) produces a lot of almost-fits. That pool is an asset if you keep it.

Which plan it is on

Candidate CRM and rediscovery are on every plan, including Small Businesses at $65/mo. Higher tiers add seats, jobs, Checkr, and AI generation — not the CRM itself. See Aptimal pricing.