Choosing a Scrape.Email plan for one city's owners

Where the cheapest tier stops and the next one begins is the first thing to settle. Prospector sits at the entry point of the published lifetime list, with Agency and Enterprise above it, and the difference between them matters more than the numbers themselves to a team working one city.

Each tier buys the same kind of work: filters by role, industry and location, scraping of public pages and profiles, enrichment, verification, plus API access, webhooks and saved leads. You are choosing how much of that work you can run, and the list of capabilities stays broadly constant as you climb.

Prices sit in a table published on softwareprogrammer.app, so read the tiers there next to this page. A team contacting developers and owners in a single city rarely needs the largest allowance at the outset, because its universe of prospects is bounded by geography rather than by a national market.

Note that the tiers are displayed as lifetime options. That shape suits a property team that wants to build lists campaign by campaign without a recurring line in the budget, but it also means the allowance you choose has to carry you through quieter and busier months alike.

Picture a two or three person team working a city's planning applications and agent listings, pulling owner and developer names and checking their addresses before a mailout. Prospector is the sensible first tier for that shape of work, run against one postcode or district at a time.

You would set filters for the roles and industries relevant to your patch, scrape public pages and profiles, then enrich and verify the contacts before saving them to a lead list. Webhooks let a CRM or spreadsheet receive new saved leads as they are confirmed, so the list grows while the team works elsewhere.

If the team runs several campaigns across a wider region, or fields enquiries from multiple agents each needing their own list, Agency is the tier to compare. Enterprise is aimed at the end of the list for volume, and a single-city property team should treat it as a later step rather than a default purchase.

The objection you raised, national data with no local detail, is worth testing before any payment. Run a narrow search in your own city and look at what comes back: whether owners and developers in your patch appear with usable detail, or whether the public footprint is thin for the kinds of property you target.

Results depend on public data, so some segments will give you a shorter list than the campaign plan assumes. That is a property of the sources, not of the tier, and it is best discovered with a small test rather than after buying the largest allowance on the list.

Verification is a check at a moment in time, not a permanent guarantee, so re-run checks on saved contacts before a later campaign. Credits are used by successful work, which means your search and verification volume against the chosen tier should be estimated before you commit.

Set Prospector beside Agency and the comparison turns on throughput rather than on features. Prospector covers a single team working one district; Agency covers a team spreading work across several campaigns or clients and needing more completed searches and checks within the lifetime allowance.

Compare Agency with Enterprise in the same way. Enterprise is the top of the published list and suits the highest volume of successful work, which a city-focused property team is unlikely to reach unless its list-building runs continuously across multiple areas and agents.

A practical order is to buy Prospector, run your city searches, measure how many credits successful work consumes, then upgrade only if the figures point that way. Saved leads carry forward, so early work is not lost when you move up a tier.