Find people by role and place, then write to them

Think of your spend as buying two habits in one place: a search for a named role in a named place, and a note that goes out from the same window. You do not export a list to a second tool or retype anything into a sending client. The chat holds the request, and the reply carries both the address and the send.

Every address you pull is checked at the moment you look it up, so you are not writing to a string a scraper assembled months ago. On paid plans the number of finds and the number of sends come as equal allowances, which suits a recruiter who writes to most of the people they look up rather than hoarding a long list.

The assistant drafts the types of email a recruiter writes: a first approach, a follow-up, a note to a referral or a scheduling line. You can also reach the same searches and sends through an API, an MCP connection, webhooks or a CSV export if your team keeps records elsewhere. Prices sit on the publisher's own plan table, separate from this page.

Across the tiers the shape stays the same and the allowance changes. Free, Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited run in that order on the plans page, each widening how many finds and sends you get in a period. For a narrow specialism you rarely need the top of that ladder; a modest paid tier usually matches a shortlist you can actually call.

The lifetime options sit beside the subscriptions. Starter lifetime, Growth lifetime and a bring-your-own-SMTP lifetime tier are published on softwareprogrammer.app, and each carries a fixed allowance rather than a monthly reset. The bring-your-own-SMTP option matters if your agency already sends through its own mail server and wants messages to leave that way.

Because finds equal sends on paid plans, upgrading is mostly a question of volume. If your candidate searches and your approaches are close in number, a tier that matches the smaller of the two is the sensible buy. Compare that against the publisher's table rather than guessing from a marketing page.

Your worry is fair: a database can be out of date before you finish a search. Here the address is verified each time you look it up rather than served from a list built earlier, so what you see reflects the check at that moment. That is a narrower promise than a permanent record, and it is the honest one.

The limit follows from the same point. A check describes an address when you run it, and a candidate who changes employer or title can leave that address dead afterwards. You should expect to re-look a few people after a gap, especially in specialisms where moves are common. Plan your searches close to the day you write.

There is a second habit worth forming. The assistant writes the email, but you decide what goes out, and the text you approve is the text that sends. Give each draft a read before it leaves, particularly a first approach where tone carries as much as the facts. Nothing in any tier controls where a message finally lands in an inbox.

When you reach the end of a month and your allowance is gone, you have a signal. Either your searches have grown or your writing has. Look at which one ran out first. Because finds and sends arrive in equal amounts, the side you exhaust tells you whether to widen the tier or tighten the search terms you use.

Moving up a subscription is the low-risk route: you keep the same workflow and gain a larger allowance each period. A lifetime tier suits a recruiter who is confident the search volume will stay roughly steady, since the allowance is fixed rather than renewed. Neither choice changes the placement of your messages or the freshness of an address you checked earlier.

If a colleague handles the sending for your desk, look at the API and webhook connections before you commit to a tier. And keep the entry step in view: you can test with a free tier, move to a small paid tier, and let the lifetime options wait until your monthly pattern is clear.