A talent pool is the group of people you have already met or attracted - past applicants, interview runners-up, sourced leads, referrals - kept on hand so the next opening starts warm instead of from scratch. The problem is rarely that you do not know good people. It is that they are scattered across spreadsheets, inboxes, and saved LinkedIn searches, and nobody circles back. 100Hires turns that scattered memory into named, searchable Talent Pools you can re-engage with automated email sequences.
Stop losing the good candidates you already met
You talked to dozens of strong candidates last quarter. You can probably name a handful of them today. The runner-up who narrowly lost out in March is sitting in someone's inbox, the speculative applicant from a careers-page form is in a spreadsheet no one opens, and the three sourced leads who were "not quite ready" have no home at all. When a similar role opens, the search begins again as if none of those conversations ever happened.
Recruiters describe the same trap on every forum. Keeping a pool warm feels like unpaid busywork next to live reqs, so it never gets done. "We will keep your resume on file" almost never turns into a real follow-up. Pools go stale as contact data decays. The fix is not more discipline - it is software that stores the people you already met, keeps them warm without manual effort, and surfaces them the moment a matching role opens.
What a talent pool actually is, and how it differs from a pipeline or a database
The three terms get used as if they mean the same thing, and that confusion is exactly why pools get neglected. A talent pool is proactive: a curated, re-engageable group you build before the vacancy exists. A talent pipeline is the active flow of qualified people moving toward one specific role that is open now. A candidate database is the raw store of everyone your team has ever captured. The database is the raw material; you carve pools out of it; you pull from a pool to build a pipeline when a real role opens.
If you want the active pipeline side of this, the talent pipeline page covers moving candidates toward a live role, and the resume database page covers searching the raw store of everyone. This page is about the layer in between: the pools you deliberately segment and keep warm.
When a talent pool earns its keep
- Evergreen or high-volume roles you hire for again and again
- Seasonal spikes and sudden backfills where speed decides the hire
- Hard-to-fill niche skills worth nurturing for months
- Post-interview silver medalists who already cleared your bar
- Building ahead of planned headcount before the req is approved
100Hires Talent Pools vs a typical ATS
Most applicant tracking systems can store past candidates. Far fewer turn that storage into a pool you actually re-engage. The rows below cover the day-to-day difference. Entry-tier pricing is shown on the 100Hires row; the full breakdown by team size lives on the pricing page.
One honest note: 100Hires is built for in-house recruiting teams. If you run a staffing agency placing hundreds of contractors a month and need a dedicated agency sourcing-CRM, that is a different category of tool. For a company building pools for its own future roles, the Talent Pools workflow above is the right fit.