Choosing a lead scraper and verifier when you run client outreach

Your money goes toward search filters that narrow prospects by role, industry and location, so each client's list starts from a different definition rather than a shared export. Public page and profile scraping supplies the raw contacts, and enrichment fills in what the page leaves out. Verification then checks those contacts before anything is sent.

Credits follow successful work rather than attempts. That matters when you build lists for several clients in a week and some searches return little. You are paying for the contacts the tool actually produced, not for the time spent looking. Read the tier terms to confirm how your usage is counted before you commit.

The workspace also holds the campaign side: API access, webhooks and saved leads. For an agency, saved leads are the practical part, because a list built for one client can be stored and reused without being rebuilt. Webhooks let your own systems react when new leads arrive, which keeps client records current.

Three lifetime tiers are published on softwareprogrammer.app: Prospector, Agency and Enterprise. The names suggest increasing capacity, and the Agency tier is the one whose label matches your situation. Before paying, open the publisher's table and check what each tier allows for saved leads, credits and workspaces, because those are the things that decide whether six or seven clients fit.

Capacity is the dividing line in practice. A tier that suits one client's outreach may not hold the volumes and stored lists you need across a portfolio. Look at how many leads you can save at once and how credits are consumed, then compare that with your busiest month rather than an average one.

Access to the API and webhooks may also differ between tiers. If you plan to push leads into your own client records or trigger your own follow-up, confirm that the tier you choose includes it. Buy the tier that covers your client count and your integration needs, not the smallest one that appears to work.

The objection you raised is a shared inbox that mixes clients together. It is a fair worry, because an agency's reputation rests on keeping each client's sending separate and being able to show where every lead came from. Before you buy, ask how the workspace separates saved leads and campaigns between clients, and whether your tier supports that separation.

Provenance is the other half of the same concern. You need to show a client which source produced a contact and when it was checked. Scrape.Email records saved leads, and webhooks can carry that information into your own systems. Confirm what the export and API include, so your records can answer a client's question without manual reconstruction.

Treat the inbox question as a setup decision rather than a reason to walk away. Map each client to its own saved leads and campaign, and decide who on your team can see what. If the tier you are considering cannot keep those boundaries, move up a tier or wait until your client list justifies it.

Take Prospector first. Imagine one client at a time: you filter by role and location, scrape public pages, enrich and verify, then run the campaign. That suits an agency testing the tool on a single account before moving others across. Check whether saved leads and API access at this tier cover the client you have in mind.

Now take Agency. Picture six or seven clients, each with its own saved leads and its own campaign, all fed by the same filters and verification. The question to answer is whether the tier's capacity holds that many separate lists and the credits your monthly volume needs. Compare the publisher's table against your busiest client.

Enterprise is the third name on the list. If your portfolio grows or your integrations become heavier, that is the tier to examine rather than assuming the middle one scales indefinitely. In all three cases, the decision rests on saved leads, credits and separation between clients, not on the label alone.