Building shortlists by role and place without a stale database

Picture the search you run when a client brief lands: a job title, a sector and a commutable radius. Scrape.Email works from that brief. You set filters by role, industry and location, and the scraper pulls matching people from public pages and profiles rather than handing you a fixed file that was assembled months ago.

From there the contact work happens in the same place. Enrichment fills in the details you need to reach someone, and verification checks the address before it reaches your outreach. Saved leads keep a shortlist intact between sessions, so you can return to a longlist and work it down as the brief sharpens.

The buying question is how much completed work you expect in a month. Each tier is a lifetime purchase, not a subscription, and credits are drawn down by successful searches and checks. Estimate the searches and verifications your desk runs per vacancy, then choose the smallest tier that covers it comfortably.

Moving from Prospector to Agency, and on to Enterprise, buys headroom rather than a different product. The filters, scraping, enrichment and verification behave the same way; the larger lifetime tier simply carries more room for completed work. For a recruiter the practical difference appears when several live roles need fresh lists at once.

A busier desk also leans harder on the plumbing. API access, webhooks and saved leads matter when you want new matches to flow somewhere else, such as a tracker or a CRM, without rebuilding the search each time. That is where an upper tier earns its place: the repeat work stops being manual and starts running on its own.

Choose by counting operations, not by ambition. If you place a handful of specialists a quarter, the entry tier is likely enough. If you run parallel searches across sectors and verify every contact before a send, price the larger tier against the volume you would otherwise spread across several tools.

The worry is understandable: a candidate list that felt current when it was built can age quietly before you use it. Scrape.Email sidesteps part of this by working from public sources at the time you search, so the list reflects what is published then rather than a snapshot from an earlier crawl.

That does not make any record permanent. Public pages change, people move roles, and an address that verified on Tuesday can be different later. Treat verification as a check at a point in time and re-run it before you reuse an old export. Saving leads and re-checking them is the habit that keeps a shortlist usable.

The other half of the hesitation is cost certainty. Because the tiers are lifetime purchases and credits are consumed by successful work, your exposure is set by how much searching and checking you actually do. Test a narrow brief first, see how many usable contacts come back, and scale the tier to that evidence.

Set Prospector against Agency as a thought experiment. Prospector suits a recruiter who runs occasional searches in one specialism, saves promising leads and verifies before a small send. Agency suits a desk with several live vacancies, where the same filters run repeatedly and the saved leads list grows into a working pipeline.

The features are shared; the difference is capacity for completed work. If your month is a few focused searches, Prospector covers it. If you are scraping, enriching and verifying across parallel briefs and want API and webhook output feeding your tracker, Agency fits the rhythm better. Enterprise is the option when the volume outgrows both.

Check the published lifetime tiers on softwareprogrammer.app before you commit, and read them against your own numbers. Count the searches and verifications per vacancy, multiply by the roles you expect, and pick the tier that absorbs that with room to spare. A tier chosen on volume is easier to justify than one chosen on hope.