One workspace, six clients, no mixed inboxes

Your monthly outlay here covers a single screen where the chat finds an address and sends the first approach, so a researcher does not hand a list to a separate sending tool. For an agency carrying six or seven clients, that means one place to run the work rather than a stack of subscriptions to reconcile each month.

Because paid plans tie finds to sends, the value sits in what you actually push out the door rather than in a stockpile of names. You can see the trade when you sit with a client's brief: the same allowance covers the lookup and the message, so estimating a campaign is a matter of counting sends, not guessing two separate budgets.

The published plan ladder runs from Free through Starter, Growth, Pro, Agency, Scale, Enterprise and Unlimited, with lifetime options for Starter, Growth and bring-your-own-SMTP. Those detail sheets sit on the plans page and the lifetime tiers on softwareprogrammer.app. Read both before you commit a client, because the shape of the ladder tells you where your volume lands.

Where the tiers separate is volume, not client count. The brief does not promise a per-client seat or a client switcher, so treat each client as a body of work you schedule and record, and pick the tier that matches the combined finds and sends across the accounts you run.

That distinction matters most when one client's campaign is heavy and another is quiet. If your monthly allowances do not roll over, a heavy month for one account and a light month for another do not balance out, so you plan the tier around your busiest realistic month rather than an average.

The lifetime entries sit on the other side of the line. A lifetime Starter, Growth or bring-your-own-SMTP option changes the cost question from a monthly one to a single decision, which suits an agency that wants a fixed tool cost while client retainers vary. The brief gives no figures, so compare the published pages yourself.

Before you pay, ask how a lead's origin stays attached to its client. The brief lists CSV export, API, MCP and webhooks, so you can push records into your own reporting and keep the trail outside the tool. Confirm that your export or webhook setup captures the client label you need for the proof your clients expect.

Verification is worth checking against how you work. Every address is checked, but a result describes the address at lookup time and can go stale as people change roles. Plan a refresh habit for older contacts rather than treating a past check as permanent.

Test the reply path on one account before you commit the rest. Inbox placement is not guaranteed, so some messages will finish outside the primary folder, and you need to know how your client's domain and your sending setup behave together. Run a small campaign first and watch where it lands.

Start on Free or Starter with a single client and a modest batch. Use the chat to find and send, then export the results by CSV so you can show the client exactly which leads were contacted and when. This gives you a real sample of the workflow before you move other accounts across.

When the sample holds, move to the tier that matches your combined volume. The AI writes every email type, which shortens the drafting step across several client voices, but read each draft before it sends so the tone fits the account it belongs to. Your approved text is the text that reaches the lead.

Keep the client separation in your own records, using the API or webhooks to tag each lead to its account. Review the tier each month against what you actually sent, and step up or down as retainers change. That habit keeps the tool cost tied to real work rather than to a plan you outgrew or never used.