An account that finds, writes and sends in one screen

The plans page is a ladder of monthly allowances rather than a menu of features. Free, Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited sit alongside lifetime options published on softwareprogrammer.app. Read each tier as a count of finds and sends per period, then match it to the number of roles you expect to work in that period, not to the number you worked last year.

Because finds and sends are paired on paid plans, the figure that matters is the smaller of your two habits. A recruiter who shortlists heavily but writes few first messages will run out of sends before finds. Estimate both numbers for a typical month, add room for a quiet month, and treat the result as your floor rather than your target.

Lifetime tiers are listed separately, including a bring-your-own-SMTP option. Those suit a recruiter who has settled on a volume and wants to stop renewing. If your specialism shifts, a monthly tier keeps the decision reversible. Either way, the pricing table is the only place to read figures, and this page deliberately leaves amounts out.

Every tier carries the same core: a chat that finds and sends, verification on each address returned, and AI drafting across the email types you write. The lowest tiers simply cap how many times you can do that in a period. For a recruiter working two or three roles at once, the cap is the whole decision, so count contacts per role before choosing.

Middle tiers raise the paired allowance and keep the same interface, so nothing about your routine changes as you move up. That matters for a specialist who searches by role and location many times a day: the work is repetitive, and the account should absorb repetition rather than make you ration it. The API, MCP, webhooks and CSV export appear as ways to move results onward.

The upper tiers and the lifetime options exist for volume and for continuity. A recruiter placing candidates across several specialisms at once will find the higher paired allowances easier to live with than a low tier used carefully. None of this changes what the tool does, only how often you may ask it to do it.

The common worry is a database that has gone stale between the search and the send. FindSend.Email answers that by verifying each address at lookup, so what you get is checked when you ask for it. That is a real difference from a static list, though it is a point-in-time result and not a permanent guarantee about any contact.

A second hesitation concerns the sending side, since recruiters often arrive with an existing mailbox. Here there is no mailbox, domain or list to bring, which removes setup but also removes the familiarity of your own inbox. If your process depends on a particular mail client, check how the sent items reach you before you commit to a tier.

The third is trust in drafted text. The AI writes every email type, and you approve each message before it leaves. Treat the draft as a first pass from a colleague who has not met the candidate, and the hesitation resolves into a simple editing step rather than a reason to avoid the account.

Moving up a tier buys volume, not new capability. The extra allowance is what you are paying for, and it exists so that a busy month does not force you to stop searching halfway through a shortlist. If your months are even, a lower tier used steadily will cover the same ground as a higher one used unevenly.

Part of the price reflects the pairing of finds and sends. You are not buying two separate quotas that can drift apart; the paid plans tie them together, which keeps the account honest about what a full workflow actually costs. A recruiter who only ever searches will notice this more than one who searches and writes in equal measure.

The rest goes to the surrounding plumbing: verification at lookup, drafting, and the routes out through API, MCP, webhooks and CSV export. Those matter if you feed a candidate database or an internal system. If you work entirely inside the screen, you are paying for them anyway, so weigh whether you will use them.