Scrape.Email pricing, read the recruiter way

Pricing for Scrape.Email is published as lifetime tiers rather than a monthly subscription, which changes how you should think about the cost. Instead of a recurring charge you absorb each month, you are looking at a single commitment tied to a tier name. The tiers are Prospector, Agency and Enterprise, all lifetime, listed on softwareprogrammer.app.

Before you weigh any figure, work out what a tier actually buys in your day. Your searches start with filters by role, industry and location, then move to scraping public pages and profiles, then to enriching and verifying the contacts you keep. Campaigns run from the same workspace, so one tier covers the whole chain rather than one step of it.

The practical question is volume. Credits are used by successful work, meaning the searches and verifications that return something. A recruiter filling a handful of niche roles may sit comfortably in a lower tier, while someone running continuous searches across several locations will want headroom. Read the tier table with your own monthly search pattern beside it.

Each tier carries the same core capabilities, and the difference lies in scale and workspace needs. Prospector lifetime suits a solo recruiter building candidate lists in one specialism. Agency lifetime points to a team sharing saved leads and campaigns. Enterprise lifetime is the tier named for larger operations. The published table sets out what each one includes.

Your daily work touches all four capability areas regardless of tier: filters by role, industry and location to narrow a search, public page and profile scraping to gather details, contact enrichment and verification to check what you found, and saved leads with API and webhooks for keeping records tidy. Check that the tier you pick covers the volume of each you expect.

Saved leads matter more for recruiters than they might first appear. A shortlist you keep in the workspace becomes the base for a campaign, and API or webhook access lets that list move into other systems you already use. If your process involves handing lists to colleagues or to an applicant tracking tool, confirm the tier supports that flow before committing.

The doubt you raised is staleness: databases that are out of date by the time you search them. Scrape.Email approaches this by scraping public pages and profiles at the point of search rather than relying on a stored index alone. That is the design intent, and it is worth testing against the roles you actually fill.

Test it honestly. Run a search in your specialism using role, industry and location filters, then check whether the people returned match the titles and locations you asked for. Enrichment and verification add a further check on the contact details. What you are judging is whether the results reflect current public information in your market.

Set expectations in line with the limits. Results depend on public data, so some candidates and companies will not appear at all, particularly those with a light public footprint. Verification confirms a contact at the moment it runs, not permanently. Treat each campaign as needing a fresh check rather than reusing an old verified list indefinitely.

Compare tiers on three counts: how many searches you run, how many contacts you verify, and how many people need access to the workspace. Write down a typical month for your desk, then look at which tier absorbs it without you rationing searches halfway through a shortlist. That comparison is more useful than staring at tier names.

A second comparison is workflow. If you work alone and run campaigns from the same workspace, a smaller tier may cover the chain from search to outreach. If lists are shared, or if you push leads into other tools through the API and webhooks, weigh the tiers that support that collaboration. Match the tier to the process, not to ambition.

Finally, compare against the alternative of doing it by hand. Public page scraping, enrichment and verification done manually take time you could spend on candidate conversations. The tier price should be read against that time, plus the cost of re-checking stale records later. Keep your own numbers in view when you read the published table.