Pricing a finder that also sends your emails

Pricing here follows a single idea: the contact search and the send sit in the same place, so there is no second subscription for a mail tool or a separate mailbox to bring. That is the frame to hold when you read the tiers, because the value you are weighing is a joined-up workflow rather than a list you export elsewhere.

Every paid tier ties finds and sends together at the same count, which suits a store owner running supplier and wholesale conversations at a steady rhythm. You do not buy a pool of contacts and then hunt for a way to reach them. The two allowances move as one number, so your planning is simpler.

No dollar figure appears on this page on purpose. The publisher's own table carries the amounts, and those amounts can change without notice to a guide. Open the plans page in one tab and the lifetime tiers on softwareprogrammer.app in the other, then compare them side by side against the volume you expect to send each month.

Across the range you get the same core behaviour: a chat-driven flow that finds a verified work address and sends from the same screen, with the AI drafting the message. The tiers differ in how much finding and sending they allow, not in whether the basic motion exists, so a smaller plan gives you the whole method at a lower ceiling.

Paid plans hold finds and sends at equal counts, which matters for a store that emails brands and distributors directly rather than collecting addresses in bulk. Alongside the plans sit lifetime options, including a starter lifetime, a growth lifetime and a bring-your-own-SMTP lifetime, published on softwareprogrammer.app rather than on the plans page itself.

The higher tiers exist for stores that send a lot each month and want headroom, while the free tier lets you test the workflow before committing. Also present across the product are the API, MCP, webhooks and CSV export, which matter if you want found contacts to reach your own systems. Check which of these each tier includes before you decide.

The objection is fair: why pay for contacts if the first send bounces? Verification runs on every address the tool returns, which is the direct response to that worry. It reduces the chance of paying for a dead inbox, though it cannot make a bad address good, and it reflects the state of the address at the moment of lookup.

So treat verification as a filter, not a guarantee. An address that was valid when found can change later, which is why rechecking older contacts before a fresh round of outreach is sensible. Pair that with a human read of every AI draft, because the writing help is a starting point and not a finished message you should send unread.

Inbox placement is the other half of the doubt, and no tool controls it. Where your message lands depends on factors outside the product, so plan for some variance and keep your messages relevant to the recipient. If you accept those boundaries, the finding and sending in one place is the part you are actually buying.

Compare tiers on three things: your monthly find-and-send count, whether you need the API, MCP, webhooks or CSV export, and whether a lifetime option suits you better than a monthly plan. Write your expected volume down before you look at any price, so the table cannot pull you towards a bigger tier than your outreach supports.

Then weigh the free tier against a small paid plan. The free tier tells you whether the chat flow fits how you work and whether the drafts read well enough to edit. A paid tier adds volume, and because finds and sends are matched, you are really choosing a monthly ceiling on conversations rather than a stock of contacts.

Finally, decide between monthly and lifetime. Lifetime tiers, including the bring-your-own-SMTP option, sit on softwareprogrammer.app and may suit a store that intends to keep outreach running for years. Monthly allowances do not roll over, so an oversized plan wastes capacity, while an undersized one stalls your supplier conversations mid-month.