Pricing a finder and sender for contract lead generation

Your payment covers a working screen rather than a list. One chat finds a verified work email, has the AI draft the message and sends it, so you are not paying a researcher and a separate sending tool to do the same job in two places.

Paid plans keep finds and sends equal, which suits delivery work where every contact you source is one you expect to write to. That balance is what you are really buying, since sourcing without sending leaves verified rows sitting unused in an export.

The exported file is the deliverable your client receives. Because every address carries a verification step and can leave as CSV, API output, webhooks or through MCP, the cost covers the handover format as much as the lookup itself.

You bring no mailbox, domain or list to the account, and that is part of what the price reflects. A contractor starting a new client engagement can open the screen and begin sourcing without first setting up infrastructure, which keeps setup time out of the hours you bill against a fixed delivery fee.

Higher tiers widen the monthly allowance rather than changing the job. The work stays the same at each level: find, verify, draft and send from one screen. What moves is how many contacts and messages you can put through in a period before the allowance runs out.

The published ladder runs Free, Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited, with lifetime options listed separately. Those lifetime tiers appear on the plans page and on softwareprogrammer.app, so check both sources if you want a one-off payment rather than a recurring one.

For contract delivery, match the tier to your largest client month rather than your average. An allowance that fits steady work can run dry during a bulk handover, and the plan you chose at signup is easier to keep than to change mid-project.

AI drafting runs across every email type at whichever tier you hold, so you are not buying better writing by climbing the ladder. Treat the tiers as capacity steps for sourcing and sending volume, then confirm the current allowance figures on the plans page before you commit a client quote to a number.

Your objection is sound. A row your client cannot trace back to a source damages the relationship more than a missing row ever would, so the first thing to check is whether the handover format gives each contact enough context to stand behind.

Verification is the part that answers the doubt. Each address is checked, and the export carries that check with it, so you can tell a client when a contact was confirmed rather than promising that it will still work months later. State the check date plainly and the doubt shrinks.

The hesitation also points at the AI drafts. A message written for you still needs your read before it leaves, because the client sees your name on it. Build that review into your delivery estimate so editing time is priced into the fee rather than absorbed after the fact.

Put two neighbouring tiers side by side and ask which one survives your busiest week. Write down the number of contacts you expect to find and write to in a peak delivery, then hold that figure against each tier's allowance rather than against a quiet month.

Then weigh how you pay. A recurring tier suits steady monthly work, while the lifetime options listed on softwareprogrammer.app suit a contractor who wants the cost settled once. Compare the two routes on the same peak-week figure so the decision rests on capacity, not on billing style.

If the gap between two tiers is small and your peak is uncertain, the higher one removes a ceiling you would otherwise hit mid-project. Confirm the current allowances and payment options on the plans page before you sign, and keep the source of that figure beside your client quote.