Picking a sender account you can defend to a client

Begin with the deliverable you hand over, not with the feature list. If a client wants a named set of contacts with a source for each row, your tier needs to cover the finds those rows require, the sends that follow up, and the export that turns the result into a file the client can open. Compare tiers on volume first.

The published plans run from Free through Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited, and there are lifetime options listed separately: Starter lifetime, Growth lifetime and a bring-your-own-SMTP lifetime tier. Read each tier as a monthly capacity for finds and sends, then ask whether that capacity covers your heaviest client month or only your average one.

Paid tiers keep finds equal to sends, so you are not choosing between sourcing and outreach when you size the account. Prices sit on the FINDSEND.EMAIL plans page and the lifetime tiers are published on softwareprogrammer.app, so check both before you commit. Decide from the work you have contracted, not from the highest tier on the page.

Each tier carries the same core motion: one chat finds contacts and sends to them, so a researcher does not have to move a list between tools. Verification runs on every address before it reaches your hands, and the assistant can draft each email type you need for a client sequence, from first contact to the follow-up that asks for a reply.

What changes as you climb is scale and access. Higher tiers give you more finds and sends each period, and the delivery options widen to include API access, MCP, webhooks and CSV export. For a contractor, the export matters most: it is the artefact a client opens, checks and files alongside the invoice.

A lifetime tier suits a contractor with a steady book of clients who would rather not manage a recurring line. Bring-your-own-SMTP lifetime suits one who already runs sending infrastructure for clients and wants the finder and drafting layer without moving that infrastructure. Match the tier to how your clients receive lists, not to the biggest number available.

The doubt you hear from a contractor is rarely about features. It is about the moment a client opens a delivered list, spots a row that no longer works, and asks where it came from. That is a trust problem, and no plan removes it entirely. You manage it by keeping a record of when each address was checked and what source produced it.

Verification in FindSend.Email describes an address at the point of lookup, and an address can change after that as people move roles or companies close. So the answer to the client is a timestamp, not a promise. Deliver the list with the check date attached, and re-run older contacts before a client reuses them.

The same caution applies to anything the assistant writes. It is a draft, and the person who approves it owns what goes out. For a contractor that means reading every message before it leaves on a client's behalf. Build that review into your handover routine so it is a step, not a scramble.

Moving up a tier buys more room to work, not better outcomes. The extra capacity goes into the number of contacts you can find and the number of emails you can send inside one period, plus the delivery routes at the top end. If your clients ask for lists in a spreadsheet, the export path is what you are really paying for.

Allowances reset each period and unused finds and sends do not carry forward, so an oversized tier wastes money quietly. Size the account to your median month and accept that a heavy month may need a step up. That keeps the cost aligned with the work you have actually contracted rather than the work you hope to win.

No tier controls where a message lands in a recipient's inbox, so pay for capacity and tooling, not for placement. A client who expects every send to reach the primary folder is expecting something the account cannot promise. Set that expectation at the start of the engagement and the rest of the pricing conversation becomes straightforward.