Choosing a Scrape.Email lifetime tier for niche recruiting

You are buying a way to turn a job spec into a shortlist. Pick the role, the industry and the location, and the scraper works through public pages and profiles to assemble people who match that brief, so a niche search in one city starts from your own definition rather than someone else's export.

Behind that, contact enrichment fills in the details you need to reach a candidate, and verification checks an address before you write. Saved leads keep a working shortlist intact between searches, while the API and webhooks let a list you have already built feed whatever system holds your pipeline.

The lifetime tiers sit on the publisher's table, priced once rather than monthly. For a recruiter filling roles in a narrow specialism, that structure matches how the work arrives: quiet weeks and busy weeks, with no reason to pay a subscription through the quiet ones. You pay for capacity to search and verify, then use it when the vacancy appears.

Smaller tiers are not broken versions of the larger ones. The difference is capacity: a lower lifetime tier gives you less room to search, enrich and verify, which matters most when you are working several vacancies at once and re-checking contacts before each new campaign rather than sending once.

Consider a recruiter running three roles in the same specialism. Each role needs its own search by title and location, its own enrichment, and its own verification pass before outreach. That is three times the work behind a single tier decision, and it is the sort of volume where a lower allowance starts to feel tight.

The other thing a cheaper tier does not change is the underlying data. You are searching the same public sources whichever tier you choose, so a lower tier does not narrow your reach, only how much searching and checking you can do with it. That is the trade to weigh before you pay.

The worry is a database that has gone stale by the time you search it. Scrape.Email does not hand you a stored file; it queries public pages and profiles when you run the search, which is a different proposition from a bought list that was compiled months ago and never touched again.

That does not make the result permanent. A verified address reflects the moment the check ran, so a shortlist you built for a role last quarter should be re-checked before you reuse it, and a candidate who has moved on may still appear because the public page has not caught up.

Reach is also set by what is public. Some specialisms publish a great deal about their people, and others publish very little, so a search in a quiet sector will return a shorter list than one in a visible sector. Knowing that before you pay keeps expectations honest.

The deciding comparison is not between Scrape.Email and a rival tool but between the three lifetime tiers and your own vacancy volume. Prospector suits a recruiter who searches occasionally in one specialism, while Agency and Enterprise suit heavier and more repeated use, with the published table setting the exact terms.

Work it through with your last month of recruiting. Count the roles you filled, the searches each needed, and the verification passes before outreach. That number tells you which tier's allowance you would actually have drawn on, and whether a lower tier would have run out halfway through a busy fortnight.

If you cannot estimate the volume yet, run a single specialism through the scraper first, count what a verified shortlist actually costs you in credits, then choose the tier that covers a typical month with room for a busy one. The tier decision is easier once you have a real search behind it.