Which Automate tier suits a freelancer's client work?

Start with what the tiers actually change. Automate connects the apps you already pay for once, then the AI works inside your own accounts: researching, writing, sending, updating and logging. The published list splits into Starter lifetime, Growth lifetime and BYOK unlimited lifetime, so the choice is about volume and about who pays for model usage, not about a renewal date you have to keep meeting.

A freelancer's objection is usually the monthly contract that costs more than the work brings in. Lifetime tiers remove that recurring commitment from the decision, but they do not remove the need to think about what you get. Look at the volume each tier allows and at whether model usage sits inside the tier or on your own key, because those two things shape how much work you can push through.

Read the list next to your own tool spend. You are already paying for the apps the platform connects, so the question is whether one purchase makes those existing accounts do more of the outreach and admin you currently do by hand. Write down the tasks you would hand over first, then check which tier covers that volume before you commit to anything.

For most freelancers the sensible starting point is the lowest tier that covers your actual monthly workload. Starter lifetime suits someone sending a small number of researched, personalised approaches and keeping a simple pipeline updated. Growth lifetime is the step up when you want more volume through the same connected apps, and BYOK unlimited lifetime is the option when you would rather supply your own model key.

The deciding factor is not the label on the tier but the number of runs you expect. Count the outreach messages, follow-ups, research tasks and record updates you would hand to the platform in a typical month, then add a margin for the months when a client project lands and your admin doubles. A tier that fits your quiet month will frustrate you in a busy one.

If you already hold a model key and are comfortable managing it, the bring-your-own-key route gives you one place to control model spend. If you would rather not think about provider billing, stay on a tier where model usage is handled inside the platform. Either way, the setup is guided and the activity log shows what ran, which matters when you are the only person checking the work.

The practical risk is scope. The platform works inside your connected accounts, so what it can do is bounded by the permissions those accounts already grant. If a client gives you limited access to their inbox or their project tool, the automation inherits that limit. Before paying, list the accounts you would connect and confirm you have the access level the work needs.

A second thing to weigh is pace. Steps that delete or overwrite data wait for your confirmation, so sequences that would otherwise run unattended will pause for you. That is a sensible guard for a solo operator, but it means some workflows still need your attention at the point of approval. Plan those approvals into your day rather than assuming the work disappears entirely.

The third is billing on the key tier. If you choose BYOK unlimited lifetime, model usage is billed to your own provider key rather than being part of the platform price, so your model spend moves with how much you run. That is controllable, but it is a separate line to watch. None of these points rules the product out; they are the things to confirm before you pay.

Compare Starter with Growth by asking how much more work you would genuinely send. If the extra volume would sit unused because your pipeline is small, the lower tier is the honest choice and you can revisit later. If you are already turning away research or follow-up work because you run out of hours, the higher volume tier earns its place in the decision.

Compare Growth with BYOK unlimited by asking who should carry model spend. Growth keeps billing inside the platform, which is simpler to budget. BYOK unlimited puts model usage on your own key, which suits a freelancer who already manages a provider account and wants that spend visible in one place. Neither route changes the connection work, which is done once.

Whichever pair you are weighing, apply the same test: the tier should cover the tasks you would hand over in a normal month, with room for a busy one. Then check permissions on the accounts you plan to connect and confirm you are comfortable with where model billing lands. That order keeps the decision grounded in your actual work.