Keeping six client lists apart in one provider

Your spend buys search filters that narrow prospects by role, industry and location, so each client's list begins from its own definition. Add scraping of public pages and profiles, contact enrichment, and verification of what you find. Saved leads keep each account's people apart, which answers the shared inbox worry before outreach starts.

Once a list is saved, enrichment and verification run against those contacts, so the addresses you hand to a client have been checked at the point of export. You can push finished leads onward through the API or receive a signal by webhook when a saved list changes, which fits an agency that already runs campaigns from its own tools.

Nothing here is billed by the month, because the published tiers are lifetime: Prospector, Agency and Enterprise. Your budget goes toward a fixed entry rather than a recurring seat, which suits an agency that wants to know the cost of prospecting before it pitches the next client on a retainer.

Prospector is the lifetime tier for testing a single client niche. Run a short search on one trade in one city, save the results, enrich and verify, then see how much of that list survives. This is where you learn whether your client's market publishes enough public detail to make the search worthwhile at all.

Agency is the tier named for buyers like you, and it is the point at which separate client work makes sense for an agency running outreach across six or seven accounts. Use it once you have proven one niche and want to repeat the same saved, enriched and verified steps for each client rather than rebuild a list from scratch.

Enterprise is the largest lifetime tier and suits an agency that expects continuous prospecting across many client accounts at once. The table on softwareprogrammer.app sets out what each tier publishes, so read it against your own completed-search estimate before you settle. Your tier choice should follow your list volume, not the other way round.

The worry is one shared pool of leads that mixes two clients into a single sending stream by mistake. Saved leads sit with the account that found them, so you build, enrich and verify per client. Hand each finished list to its own sender, and the separation holds through the handoff rather than breaking at export.

When you push a verified list through the API into a client's own tool, that list carries its own source details, so you can show the client which filters produced each contact. A webhook lets your systems respond when saved leads change, keeping the client's tool in step without an inbox in the middle.

This does not remove the need for care. You still decide which client owns which saved lead, and your own naming and handoff routine does the rest. The product gives you the structure to keep them apart; the discipline of naming each saved list is yours to keep.

Treat the move between tiers as a volume question rather than a feature hunt. Count how many completed searches and verifications one client campaign needs, multiply by the number of accounts you run, and compare that to what each lifetime tier publishes. If Prospector covers your test, stay there while you refine filters.

Agency earns its place when separated client work becomes the normal rhythm rather than an experiment, and Enterprise when the count of concurrent accounts outgrows what you can track by hand. Neither move should happen before you have run at least one real list through to a client's sender and seen the result.

Before you pay, pick one client with a clear niche and run a short list end to end: search by role, industry and location, save, enrich and verify. That single run tells you more about which tier fits than any comparison page, because it shows what your own client markets actually publish.