Keeping six client campaigns apart on one plan

Your agency budget buys a single chat window where finding and sending happen together, so nobody has to hand a list across to a second tool. Prospecting for one client stays in one place from the first lookup to the sent message. That is the work the fee covers, rather than rows in a database you never touch.

Every address the chat returns is checked before it reaches your sending step, which matters when a client asks how a contact was sourced. On paid plans the number of finds equals the number of sends, so a month of research and a month of outreach pull from the same allowance. You can show a client where a lead came from without rebuilding a trail by hand.

The assistant writes each email type you need, from a first approach to a follow-up, and the plan also gives you API, MCP, webhooks and CSV export. Those routes let you push leads into a client's own systems or keep a copy outside the tool. For an agency, that is how one plan serves several accounts without copying text between inboxes.

Plan names run from Free through Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited, with separate lifetime options for Starter, Growth and a bring-your-own-SMTP route. The tiers are published on the FINDSEND.EMAIL plans page and on softwareprogrammer.app, so you can compare them side by side before committing a client retainer to a subscription.

What rises between tiers is the monthly allowance of finds and sends, and with more volume you cover more client campaigns inside one account. The features listed in the brief stay consistent across paid plans: one chat for finding and sending, checks on every address, matched find and send counts, the writing assistant, and the connecting routes for your own tooling.

Where an agency feels the difference is capacity. Six or seven clients with cold outreach each month add up quickly, and an allowance sized for one client will stall mid-campaign. Decide the tier from the total volume you expect, not from the size of your largest single account, then check the lifetime options if you would rather not renew monthly.

The usual objection is that one shared inbox will mix clients together. Before you pay, confirm how the plan keeps each client's sending separate, because the buyer's concern is proving that a message for one client never reaches another client's audience. That is a setup question about how you organise projects inside the account, not a feature you can assume.

Read the limits first. Inbox placement is not guaranteed, and no tier changes where a message finally lands. A verification result describes an address only at the moment of lookup and can fail later as people change roles. Every AI draft needs your own read, since the approved text is what sends.

Allowances also reset rather than roll over, so an unused month is lost when the period closes. Size the tier to your real monthly volume rather than buying headroom you will not spend. Agencies that plan for a quiet month and a busy one should treat the allowance as a ceiling, not a bank.

Compare two adjacent tiers by the volume your six or seven clients actually need in a month. Add up the new contacts you expect to find and the messages you expect to send, then pick the tier that covers the larger of the two, because finds and sends draw from the same allowance on paid plans.

Then check what the extra money buys beyond volume. The brief lists the same finding, checking and writing features on paid plans, so if your only reason to climb is a bigger allowance, take the smaller tier and keep the difference for client work. If you need the API, MCP, webhooks or CSV export in a client's own systems, confirm those routes are present on the tier you choose.

A lifetime option is worth weighing for an agency that expects steady outreach. Starter lifetime, Growth lifetime and a bring-your-own-SMTP lifetime route are published separately on softwareprogrammer.app, so read them alongside the monthly tiers. Keep the client separation question in view whichever route you take.