Scrape.Email for recruiters: what the tiers actually buy

Payment for a lifetime tier buys a workspace where you define a search by role, industry and location, then scrape public pages and profiles for matching people. That search definition is the core of the product, and it is what you are funding first. Campaign tools and saved leads sit in the same workspace, so outreach starts from the same place you built the list.

Second, the money covers enrichment and verification of the contacts your searches return. Verification checks an address at the moment it runs, which matters when you are about to contact a candidate about a specific role. Enrichment fills out what you have on each person so your shortlist is usable without a second export step.

Third, your tier funds the automation layer: API access, webhooks and saved leads. These let you push contacts into your own systems or hold a list for later. Credits are consumed by successful work, so what you pay for is completed operations rather than attempts. Read the tier table on softwareprogrammer.app before you commit.

Finally, a lifetime tier removes the monthly renewal question. You pay once for the allowance your tier carries, then plan sourcing around it. For a recruiter in a narrow specialism, that structure suits work that comes in bursts rather than a steady monthly flow.

Across the lifetime ladder, the visible change is how much work each tier supports. Prospector lifetime, Agency lifetime and Enterprise lifetime are the three published levels. Moving up gives you more room for the searches, enrichment and verification that fill a shortlist. The exact allowances sit in the publisher's tier table, not in this guide.

A second change is how much of the automation layer you can use. API access, webhooks and saved leads matter more as your sourcing volume grows, because they let you keep lists and move contacts into other tools. A recruiter placing a handful of candidates may not need that reach. A recruiter running several searches at once likely will.

A third change is how you plan credits. Because credits are used by successful work, a higher tier lets you run more completed searches and verifications before you need to think about the allowance. That makes the tier choice a volume decision rather than a feature hunt. Compare your monthly shortlist size against what each tier carries.

What does not change is the underlying method. Every tier uses filters by role, industry and location, scrapes public pages and profiles, and verifies contacts. The ladder widens what you can do, but the approach stays the same. Choose a tier on volume and automation needs, not on expecting a different product at the top.

The objection is that databases go stale before you search them. Scrape.Email answers that by scraping public pages and profiles at the time you run a search, rather than serving a fixed snapshot. For a recruiter, that means the list reflects what is published now, which is closer to the person's current role than an old export would be.

That does not remove the concern entirely. Results depend on public data, so some searches will return fewer contacts than you expect, especially in a narrow specialism where people publish little. Verification is also a moment-in-time check, not a permanent guarantee. Treat each list as fresh work rather than a durable asset you can reuse indefinitely.

The practical response is to build re-verification into your routine. Run a check before each campaign, and keep saved leads only where you will refresh them. That habit turns the hesitation into a process step. It also means you should size your tier around repeat verification, not just the first build of a list.

For a recruiter, the real question is whether the workflow fits how you source. If you search by role and location before each placement and want contacts verified at that point, the model matches. If you expect a static database to sit and stay current, the model will disappoint. Decide which of those you actually need before paying.

Start by counting the searches you run in a typical month and the contacts you verify for each. That number, not the feature list, tells you which tier fits. A recruiter working one specialism with a short shortlist per role will sit lower on the ladder. A recruiter running several concurrent searches will need more room for completed work.

Next, ask whether you need API access, webhooks and saved leads now or later. If you plan to push contacts into an applicant tracking system or hold lists between campaigns, the automation layer earns its place. If you work from the workspace itself and contact people soon after searching, the lower tier may cover you. Be honest about which pattern you actually follow.

Then check the credit allowance on each tier against that volume. Because credits follow successful work, a tier that looks generous on paper can run down quickly if you verify large lists. Match the allowance to your realistic monthly completions, and leave some headroom for re-checks before campaigns. The publisher's table is the source for those figures.

Finally, treat the choice as reversible in planning even if the purchase is lifetime. If you are unsure, start where your current volume sits and note what would push you up: more concurrent searches, more verification runs, or a need for automation. That note becomes your signal for the next tier when the work grows.