Which Automate plan keeps each client's sending apart?

Start with what the platform actually is. Automate links the apps you already pay for through one connection screen, then the AI carries out research, writing, sending, updating and logging inside your own accounts rather than in a shared pool. That shape matters to an agency because the work stays attached to whichever client account you connected, which is the separation you are looking for.

The published list shows three lifetime tiers: Starter, Growth and BYOK unlimited. Each is a one-time purchase rather than a recurring seat charge, so the question is not what a month costs but which tier covers the volume of work you expect to run across your client roster. Match the tier to the sending and task volume you handle now, not to a number you hope to reach.

Because the tiers are lifetime, treat the decision as a capacity choice. If you run outreach for six or seven clients, estimate how many research, writing and sending steps each client needs in a typical week, add them together, and see which tier sits above that figure. Leave room for a client joining, but do not buy capacity you cannot describe in tasks.

Agencies usually land on Growth, because a single client rarely justifies the entry tier once you spread the work across six or seven accounts. Growth is the middle lifetime step, and the honest way to choose is to compare the volume each tier allows against the combined task load of your roster rather than against one client's needs.

The exception is the BYOK unlimited tier, which suits an agency that already holds a model key and prefers to pay the model provider directly. That tier trades a fixed platform volume for your own key arrangement, so the platform price is only part of your outlay. If you have no key and no wish to manage one, the volume tiers are the simpler route.

Whichever tier you shortlist, test it against a single client first. Guided setup and the activity log are the parts that tell you whether the work is landing where you intended. Read the log after the first sequences run and confirm each entry sits under the right client account before you extend the same pattern to the rest of the roster.

The objection you raised is the right one to test. A shared inbox that mixes clients together would undo the value of running separate outreach, so before paying, confirm how each client's accounts are connected and whether the activity log records which client each action belonged to. If you cannot trace a lead back to a named client, the tier is not yet doing its job.

The second risk is scope. The platform works inside your accounts, which means it can only reach what those accounts already permit. If an agency login has restricted access to a client's sending tool, the automation inherits that restriction. Check the permissions on each client account before you assume a sequence will run end to end.

The third is pace. Steps that delete or overwrite data wait for confirmation, so some sequences will pause for a person. Plan for that in your client workflows rather than promising unattended sending. On the BYOK unlimited tier, model usage is billed by your own provider, so keep an eye on that bill alongside the lifetime purchase.

Compare Starter against Growth by counting tasks, not clients. Starter is the entry lifetime tier and suits a small, steady load; Growth is the step above it and fits an agency spreading work across a fuller roster. Write down the weekly task count for each client, total it, and see which tier sits comfortably above the total.

Compare Growth against BYOK unlimited by asking who pays for the model. Growth keeps model usage inside the platform arrangement, while BYOK unlimited sends every request to your own key and your provider bills you for it. If you already hold a key and want that control, the trade is clear; if not, the volume tiers keep billing in one place.

Across all three, the practical comparison is the same. One connection screen, work running inside your own accounts, guided setup and an activity log are shared. What changes is volume and who pays the model provider. Choose on those two facts, then verify separation per client in the log before you commit.