Sourcing candidates without a stale database

Four decisions sit between you and a usable candidate list: which filters describe the role, how many profiles you pull, whether the contact details survive verification, and how the finished leads reach your workflow. Scrape.Email covers those four together rather than selling you a fixed database that ages from the day it is compiled.

Search filters narrow by role, industry and location, which matters when your specialism is narrow and a broad export returns dozens of near misses. Scraping runs against public pages and profiles, so the list reflects what is published now rather than a snapshot taken months ago and sold on to everyone.

Contact enrichment and verification then sit next to the search, so you check an address before it reaches a candidate sequence. If you work through an applicant tracking system or a spreadsheet, an API, webhooks and saved leads move the finished records into it without a manual copy step each time.

Three lifetime tiers are published: Prospector, Agency and Enterprise. The split is about how much finished work you need each month, not about hiding the search filters behind a higher tier, so read each one against your own search and verification volume rather than against the label.

Prospector suits a recruiter testing one specialism and a repeatable weekly search. Agency suits a desk running several roles at once, where saved leads and webhooks keep each client's list separate. Enterprise suits a team that needs the API wired into existing systems and a higher ceiling on volume. Confirm current tier contents on the vendor's own page before you decide.

Because credits are used by successful work, the right tier is the one that covers your completed searches and checks with headroom. Estimate that volume from a real week of sourcing, not from a hoped-for month, and the tier choice becomes a capacity question rather than a guess.

The objection is that databases go stale before you search them, so what changes here? Scraping runs against public pages and profiles at the moment you search, which keeps a list closer to current than a compiled export, though it still depends on what is published and public for your specialism.

Verification is the second half of the answer, and it is a check rather than a promise. A verified address is accurate when the check runs and can change later, so re-verify saved contacts before you reuse them in a new campaign. Treat verification as a step in your workflow, not a permanent stamp on a record.

Do not take coverage on trust. Pick one narrow role and location you know well, run that search, and inspect whether the returned profiles and contacts are the people you would have found by hand. That single test tells you more about fit than any feature list.

Work out your weekly finished volume before comparing tiers: how many searches you run, how many profiles you pull, and how many addresses you verify. That number, not the tier name, tells you whether Prospector covers a single desk or whether Agency is the honest fit for a busier one.

If your work already lives in a tracking system, weigh the API and webhooks early. Moving verified leads automatically saves a manual step on every search, and that recurring saving compounds across a month of sourcing in a way a one-off larger credit balance does not.

Then decide how much risk you can carry in a lifetime purchase. Start small, run your own niche through the workflow, and only move up when the returned lists reliably match the roles you recruit for. Upgrading after a clean test is a calmer decision than upgrading on a sales page.