Which Scrape.Email tier do you resell under your own brand?

The cheapest tier and the one above it differ in how much finished work you can put behind your own logo. Read the list with your delivery model open beside it: how many client lists a month, how many verifications each list needs, and whether you hand over a file or a login. The tier you choose should follow that shape.

Scrape.Email lets you filter by role, industry and location, scrape public pages and profiles, enrich and verify contacts, and keep results through the API, webhooks and saved leads. For a reseller, those are the parts of the job you rebrand. Your client sees a list that meets their description; they need not see which search produced it.

The price list also tells you where your margin sits. A tier that covers the searches and checks you complete in a month leaves room to price your own service around the outcome. A tier that runs dry before the month ends turns every extra client into a top-up conversation. Compare the tiers against your busiest month.

Before you read a single figure, write down what one client actually receives. If you deliver a checked contact list as a file, your cost is finished searches and verifications. If you hand over saved leads inside your own portal, add the setup work of moving those results into your brand. That written scope is the honest unit you compare every tier against, and it stops a cheap tier looking like enough when your delivery is heavier than one export.

Start at the lowest tier that covers one full client cycle. Run a single niche through the filters, collect the profiles, verify the contacts and hand the list over. If that cycle finishes inside the tier, you have a working base to resell from and a real number to compare against the next tier up.

Move up when a second client arrives, or when the same client asks for a second list. The step from Prospector to Agency usually matters less for features than for volume: more finished searches and checks before you have to think about the balance. That is the point where white-label delivery becomes predictable enough to promise a date.

Enterprise lifetime suits a partner running several client accounts at once, where the person buying is not the person running the searches. You need headroom for overlap, for re-checks when a client reuses an old list, and for the failed attempts that still cost you time. Choose the tier you can fill from your own pipeline, not the one with the most room.

Keep the same test discipline when you step up. Take the client who stretched the lower tier and run their cycle again on the higher one, then compare what finished. That comparison tells you whether the extra volume pays for itself in repeat work or whether you simply bought idle headroom. Resellers lose margin on tiers they cannot fill, so let one real client justify each move before the next one.

Read the licence first. Your objection is fair: a tier that permits your own searching but forbids client-facing use cannot support a reseller model. Check the published terms for how you may pass results to a client, whether you may present them under your name, and what stays with the tool. Get that in writing before you sell anything.

Then look at how the results are produced. The tool filters by role, industry and location and works from public pages and profiles, so each list reflects the sources behind it. Some client niches have a thin public footprint and return shorter lists. Test your first client's niche before you quote a number to anyone.

Verification is not permanence. A contact can be checked and correct on the day and change later, so build a re-check into your delivery rather than promising a forever-valid list. Tell the client when the check ran. That habit protects you from disputes and makes the second delivery easier to price, because your client already understands what verification covers.

Watch the credit balance as you would an account. Completed searches and checks use credits, so a reseller who quotes from a sample and then delivers at scale can meet a bill sooner than expected. Forecast your heaviest client month, add room for re-checks, and hold that forecast against the tier. If the numbers do not meet, lower the promise rather than raise the tier on hope.

A worked comparison removes the guesswork. Take one client, one niche and one deliverable: contacts in a named role and location, checked and passed on as a file. Run that job on Prospector and note what completed, what needed a re-check and what the client did with it. Then run a second client on the same tier.

When the second client pushes the balance, that is your signal to test Agency with the same two jobs. Compare the completed work, not the feature list. If the higher tier finishes both clients without strain and leaves headroom for a re-check, the step up is doing its job. If the lower tier already covers both, stay where you are and keep the difference.

Enterprise lifetime only makes sense when your pipeline already carries several accounts. Compare it the same way: count completed searches and checks across all your clients in your busiest month and set that against the lower tier. The question is never which tier is larger; it is which tier your finished work fills without leftovers.

Repeat the comparison each quarter. Client mix shifts, niches dry up and a list that took two searches may take four next time. A tier that fitted in spring can crowd by autumn, and a tier you outgrew is not a failure. Keep the written scope, keep re-checks in the promise, and let the finished work decide when to move.