Finding and writing to one specialist candidate

Picture a shortlist for one hard-to-fill role in a single city. You type what the role is and where it sits, the tool returns addresses with a check on each one, and the email is drafted and sent from the same conversation. What you are weighing up is that whole loop rather than a directory you search and then leave.

Your objection about stale data is the right one to bring. A directory built months ago describes a market that has moved, and specialist roles turn over quickly. Here the data is fetched when you ask for it, which changes the question from how big the database is to how good each lookup is on the day you search.

Value depends on how often you repeat that loop. Find equal sends on paid plans means a find and a send are spent together, so the cost of an approach is visible rather than buried. Read the plans page and the lifetime tiers on softwareprogrammer.app, then measure them against the number of approaches you genuinely make in a month.

Between the free tier and the paid plans sits a simple line: whether you can send at all at the volume your desk needs. Free lets you test the loop on a small search. Paid plans bring equal finds and sends, so every address you pull can be written to without a second purchase decision.

Further up the ladder the difference is capacity and access rather than a different product. The API, MCP, webhooks and CSV export matter if you keep records in an applicant tracking system or want results to flow into your own tooling. A recruiter working alone may never touch them; a small team that pipes candidates into a shared system will.

The lifetime tiers published on softwareprogrammer.app sit apart from the monthly ones, including a bring-your-own-SMTP option. Those suit a recruiter who wants a fixed arrangement rather than a recurring subscription, provided the allowance model still fits the way you work through a specialism month by month.

Before you pay, run a live search on the roles you actually fill. Not a generic test, but the awkward title and the specific location you struggled with last week. Look at whether the addresses returned are the people you meant, because verification confirms an address exists, not that the person is the right hire for the brief.

Then read a set of AI drafts as a hiring market would read them. The tool writes every email type, from a first approach to a follow-up, but the tone has to sound like you. If the drafts need rewriting each time, the time saved on finding is partly spent again on editing, and that changes the arithmetic.

Finally, check how the allowance resets. Monthly allowances do not roll over, so a quiet month spends nothing and saves nothing. If your work is seasonal, with a heavy push followed by quiet weeks, a lifetime tier or a smaller monthly plan may suit you better than a large one.

Start on the free tier and treat it as a trial of the workflow rather than of the database. Run two or three searches in your specialism, send a handful of approaches, and note how many drafts you keep as written. That gives you a rough ratio of usable output to effort, which is the number that decides whether an upgrade pays.

If the loop works, move to the smallest paid tier that covers your real monthly volume, remembering that finds and sends are paired. Track the point where you run out before the month ends. That is the honest signal to move up, rather than a feature list or a comparison with a competitor's seat count.

Upgrade beyond that only when a specific need appears: a colleague joining, a system that needs the API, or records that must reach your own tooling through webhooks or CSV export. Each step should answer a problem you have met, not a problem you expect. The plans page lists what each tier holds.