When your candidate list is out of date before you call

Picture a shortlist pulled from an old database where two of the six phone numbers ring out and one email bounces. Your payment to Scrape.Email buys the finding and checking work instead: searches narrowed by role, industry and location, public page and profile scraping, then contact enrichment and verification before you save anyone.

Search filters do the filtering that a general database cannot do for a narrow specialism. You are buying a way to define the person you want, not a fixed pool of records that was compiled months ago. The scraping step reads public pages and profiles, and the enrichment and verification step turns what it finds into contact details you can act on.

Nothing here is tied to a monthly seat. The tiers are lifetime, listed on softwareprogrammer.app as Prospector, Agency and Enterprise. Read those tiers against your own weekly volume of searches and checks rather than against a flat subscription you cancel later. The question is whether your completed work fits the tier you choose.

Which tier suits you comes down to volume and workflow, not to a feature list you cannot reach. The published line runs Prospector lifetime, Agency lifetime and Enterprise lifetime. If you source alone in one specialism, your searches and verification checks are fewer per week than an agency desk running several roles at once.

The practical divide shows up in saved leads and in automation. Saved leads are how you keep a shortlist ready between conversations, so a recruiter who works many roles in parallel leans on that more than one who places occasionally. An API with webhooks moves results into your own tools, which matters if your process already lives somewhere besides the Scrape.Email interface.

Work out your completed search and verification count for a typical week before choosing. Credits are used by successful work, so the number that matters is finished operations, not attempts. Stack those up against each lifetime tier at softwareprogrammer.app and the choice narrows quickly.

Before you pay, run one narrow search in the specialism you actually recruit for. Pick a role, an industry and a location you know well, then look at what comes back. Results depend on public data, so a specialist market with a thin public footprint will return a shorter list than a broad one. Knowing that early stops a surprise later.

The next check is verification. It tells you what a contact looks like when the check runs, so treat a saved lead as something to confirm again at the point you reuse it. Build that habit into your shortlist routine rather than assuming a saved list stays as it was on the day you built it.

Finally, watch how credits move through your first real searches. Successful work draws them down, so your trial should use the same pattern you would use in a live week. A test that understates your usual volume gives you a tier choice built on the wrong number.

Start with a single role you are actively filling. Set the role, industry and location filters, let the scraping gather public pages and profiles, and run enrichment and verification over the shortlist. Note how many completed searches and checks that took, and how many of those leads you would genuinely approach.

Then compare that against the lifetime tiers on softwareprogrammer.app. If your week of completed work sits comfortably inside Prospector, stop there. Move to Agency when parallel roles push your saved leads and volume higher, and consider Enterprise when you want API and webhook access into your own systems rather than working inside the interface alone.

The upgrade question is not about getting more features for their own sake. It is about whether your real completed workload, your saved shortlists and your existing tools fit the tier you are on. Re-run the same test in a second specialism and you have two data points for the decision.