Scrape.Email for coaches and consultants

Tuesday afternoon, a cohort with three seats left, and a spreadsheet of half-checked names. That is the week this tool is built for. You are paying for the narrowing work: setting filters by role, industry and location so the list starts from a definition you chose, not a shared export you inherited.

Underneath that sits the scraping of public pages and profiles. Instead of copying details by hand, you let the search collect them, then let contact enrichment fill in what is missing. Verification runs before those names reach your draft folder, which matters when one bounced address costs you a reply.

The mechanics sit behind it: an API, webhooks and saved leads. Saved leads are the practical part for you, because a coaching cohort builds over several weeks and you want the same names to stay in one place while you write to them properly.

Three lifetime options exist, published on softwareprogrammer.app: Prospector, Agency and Enterprise. Each is a one-off purchase rather than a subscription, so the question is not how many months you keep it but how much finished search and verification work you expect to do across a launch or a year.

Prospector is the tier to study first if you run one cohort at a time and write every message yourself. Agency enters the picture when the same saved leads serve more than one offer, or when the volume of searches and checks in a month outgrows a single small batch.

Enterprise is for the buyer who already knows their pattern and needs room to repeat it. Since credits are consumed by successful work, read each tier against your own numbers: how many filtered searches you run, and how many contacts you verify before writing.

The objection is rarely the tool. It is the fear that whatever you send will read like a mail merge, and a scraped list will make that worse. That concern is fair, and it is answered by how you use the output, not by the scraper itself.

Take one filtered slice, verify it, and write to fifteen people by hand with one detail you noticed from their public profile. The tool's job ends at a verified name and a working address; the reply depends on the sentence you write after it. Saved leads make this repeatable across a cohort.

Treat the first list as a test of the tool too. If your chosen niche returns usable contacts and your messages get answers, the objection was about the writing. If the list comes back thin, you learned that before committing to a larger tier.

Picture a consultant launching a group programme for operations managers in two cities. With Prospector, they filter by role, industry and location, scrape the public profiles that match, enrich the missing details and verify before writing. The saved leads hold the cohort while the messages go out over three weeks.

Now picture a coach whose list spans several offers and a steady monthly rhythm of searches. On Agency, the same workflow repeats without reworking the batch size each time, and the saved leads serve more than one programme. The filters and verification steps do not change; only the room to repeat them does.

Neither path needs the largest tier on day one. Run one cohort through the workflow, note how many searches and checks it actually consumed, then choose the tier that matches the pattern you saw rather than the one you imagined in the planning week.