Choosing an agent when candidate databases go stale

Start with what your payment actually covers. The product is sold as lifetime tiers published on softwareprogrammer.app, and the tiers carry the names Starter, Growth and BYO-SMTP. Your money goes towards an agent that plans a campaign, assembles the list, drafts the templates and launches the send once you approve it. That is preparation work removed, not a database subscription.

Think about the objection that brought you here. A database that is stale by the time you search it leaves you paying for rows you cannot use. An agent that builds a list per campaign frames the cost differently: you are buying the act of assembling and writing, repeated for each role you work, rather than access to a fixed pool that ages.

Value for a recruiter in a narrow specialism sits in repetition. Each role needs a fresh list by title and location, a fresh template and a fresh send, and the agent handles that cycle with a health-checked sending mailbox behind it. Weigh the tier against how many campaigns you run, not against the size of any list.

Tiers differ in what they include, and the published table on softwareprogrammer.app is the place to compare them. Read the tier names as a structural choice: whether you bring your own sending server or take the managed mailbox. The interface runs in English and Spanish, which matters if your team or your candidate markets work in either language.

Between the tiers sits a single question: who supplies the sending mailbox. The BYO-SMTP tier assumes you have a server and reputation of your own. Starter and Growth sit on the managed mailbox, where the product health-checks the sending setup for you. That difference shapes your setup time and the amount of technical work you take on.

Consider your own capability first. If your agency already runs sending infrastructure and a domain with history, bringing your own SMTP may suit you. If you would rather not manage servers, the managed option removes that task. Neither route changes what the agent does: it still plans, lists, writes and launches on your confirmation.

Volume matters less than you might assume, because the agent works per campaign. What shifts between tiers is the package around the sending side, not the core loop of listing and writing. Compare what each tier states plainly, and treat anything the table leaves out as something to ask before you pay rather than something to infer.

Language is a smaller but real line. The interface works in English and Spanish, so a recruiter placing bilingual candidates across two markets can run campaigns from the same tool. Check that the tier you choose includes the sending arrangement you want, since that is the structural difference the names point to.

Run one live test before you commit to a tier. Pick a single role in your specialism with a clear title and location, let the agent plan the campaign and build the list, then read the drafted templates as a recruiter would. You are checking whether the list matches the brief and whether the writing sounds like your agency, not whether it impresses at first glance.

Confirm the review step fits how you work. The agent waits for your confirmation before any send, which keeps a human check in the loop. For a recruiter that is useful, because a poor list going out under your agency name costs more than a delay. Budget the review time into your week and decide whether it is time you can spare.

Ask about the mailbox. A managed sending mailbox is health-checked, yet delivery still depends on sending reputation, which builds over time. If you bring your own SMTP, understand that the reputation question moves to you. Either way, early campaigns may not travel as widely as later ones, and no setting changes that reality.

Set expectations with your hiring managers. No replies are promised, so present the tool as a way to prepare and send targeted campaigns, not as a source of placements. Judge it after a few campaigns on how much preparation time you saved and how closely the lists matched your brief.

Treat an upgrade as a decision about the sending side and about how many campaigns you run, not about features you have yet to use. Start on the tier that matches the mailbox arrangement you want. If you began with the managed mailbox and later build your own server, the BYO-SMTP route becomes relevant. Move only when your own workflow gives you a reason.

Before you move up, review what the current tier left you short of. If the answer is preparation time, the agent itself is doing its job and the tier is not the constraint. If the answer is control over sending, the mailbox question returns. Write down the reason for the change in one sentence, and if you cannot, stay where you are.

Use a simple test across a month of roles. Count the campaigns you prepared, the review time each one took and how often the list needed correcting before you approved it. Those three numbers tell you whether more capacity helps or whether your bottleneck is the review step, which no tier removes.

Keep the confirmation habit as you scale. Every launch still needs your approval, so a larger package does not free you from reading the list and the templates. The agent plans, lists, writes and launches, and you remain the person who decides that a campaign goes out under your agency name.