A provider brief for contractors handing over verified lists

Three decisions sit in front of you before any payment: how many contacts a month you must hand over, how much sending sits inside the same allowance, and whether you want a recurring plan or a lifetime tier. Take them in that order, because the first two set your tier and the third only changes how you pay for it.

The budget pays for one chat where finding and sending happen together, so a researcher does not export a list and pass it to a separate sending tool. Verification runs on every address as it is found, which is the part your client is really buying when they ask for a source on each row.

On paid plans, finds and sends are matched, so growing the list also grows the outreach you can run against it. For delivery work that matters: a batch you verify can be worked in the same place, and the export gives your client the trail they asked for without a second subscription sitting beside it.

Below the paid tiers, the free plan lets you test the chat workflow before committing to a volume. Starter and Growth sit at the entry end for smaller handovers, while Pro and Agency carry the monthly allowances a contractor working across several client accounts tends to need. Scale and Enterprise sit above those for heavier list volumes.

Each paid tier carries the same core: one chat that finds and sends, verification attached to every address, matched finds and sends, AI-written drafts for each email type, and the export routes. What moves between tiers is the monthly allowance, so the tier question is really a volume question about how many verified rows you promise a client each month.

The lifetime options sit outside the monthly ladder. There are lifetime tiers for Starter and Growth, plus a bring-your-own-SMTP lifetime tier for contractors who already send through their own mail infrastructure. Plans and lifetime pricing are listed on the FINDSEND.EMAIL plans page and on softwareprogrammer.app, so read both before you choose.

The objection you raised is unverifiable rows damaging a client relationship, and the answer is that verification happens on every address as it is found, so each row carries a check at the moment of lookup. That is the evidence you pass on. It is not a permanent guarantee, and you should say so to your client rather than imply otherwise.

What you cannot promise through any tier is where a sent message lands. Placement sits outside the tool, so if a client expects replies from every send, set that expectation early and keep the sending work framed as outreach rather than delivery. The list quality and the placement question are separate, and mixing them is what usually causes friction.

AI drafts are written for every email type, and each one still wants your own read before it goes out. Treat the drafts as a first pass you edit, because the text you approve is the text that sends from your account. That habit protects the client relationship more than any single feature.

Start on the lowest tier that covers one month of real client volume, then move up only when you are consistently hitting the ceiling before the period ends. Matched finds and sends mean an upgrade buys both list growth and outreach room at once, so measure which one runs out first and let that decide the step.

The upgrade question changes if you send through your own mail server already. The bring-your-own-SMTP lifetime tier keeps your existing infrastructure and removes the monthly decision, which suits contractors with steady delivery work. If your volume swings by client, the monthly ladder remains the safer fit because you can step back down.

Decide before you sign a client, not after. Map each client's expected row count onto a tier, add the sending you plan to run, and check that the total fits inside one allowance rather than two. If the numbers do not fit, quote the client for the tier that does, because under-provisioning shows up as a late delivery.