Sourcing narrow roles without a stale database

Your budget goes toward narrowing a search before you contact anyone. You set role, industry and location, and the tool reads public pages and profiles to assemble a list that matches that definition. For a recruiter in one specialism, that means starting each search from your own brief rather than from a shared export built for someone else.

Behind the search sits contact enrichment and verification. Once you have names that fit the brief, you run the contact details through verification so you are not dialling into dead inboxes. Saved leads keep a list in one place between sessions, and the API and webhooks let you push that work into whatever system already holds your pipeline.

Credits are drawn down by work that succeeds, not by attempts, so a search that returns little costs you little. That matters when you are testing a narrow specialism: you can probe a role and location combination, see what public data exists, and only spend where the results justify it.

Prospector lifetime suits a recruiter testing one specialism or running searches at a modest pace. Agency lifetime is built for someone whose search volume is sustained and who needs the tool to keep up across several role and location combinations. Enterprise lifetime sits above both, for larger operations. The published tiers on softwareprogrammer.app set out what each includes, and the price table beside this page shows the figures.

Compare the tiers on volume first, then on how you will connect the tool to your workflow. If you only need saved leads inside the product, the lower tiers may carry you. If you want verified lists flowing into an applicant tracking system or a spreadsheet through the API and webhooks, check which tier includes that before you commit.

Read each tier against a normal month rather than a busy one. Count the role and location searches you would realistically run, and the contacts you would verify from them. That count, not the label on the tier, decides which one you should buy.

You have probably paid for a candidate database before and watched it age. The worry is not the search interface, it is whether the people you find are still in the role you searched for. Scrape.Email works from public pages and profiles, so its freshness is tied to what those sources publish, which is a different proposition from a static list.

The honest boundary is that results depend on public data. Some candidates and companies keep a thin public footprint, so a search in certain specialisms returns fewer results than you would like. Verification does not fix that: it confirms an address when it is checked, not that the person stays reachable weeks later. Re-verify a saved list before you reuse it.

Knowing those limits lets you buy sensibly. Use the tool to find people whose public presence is current, verify before each outreach round, and keep saved leads as a working set rather than an archive. If you treat it as a live search rather than a permanent record, the concern about staleness stops being the deciding factor.

Take a recruiter placing backend engineers in two cities. Their month is a handful of role and location searches, each producing a short list, followed by verification before outreach. Prospector lifetime covers that pattern: the searches are narrow, the volume is modest, and saved leads hold the pipeline between sessions. Nothing in that month needs a heavier tier.

Now take a recruiter running four specialisms across several regions, with lists moving into an applicant tracking system through the API and webhooks. Search volume is higher, verification runs more often, and saved leads multiply. That is where Agency lifetime earns its place, because the work is sustained rather than occasional and the connections matter as much as the searches.

Choose Prospector if your month looks like the first case, and move up when the second case describes your week. Buy the tier you can justify against completed searches and verifications, and let the published table settle the rest.