Choosing an AI automation tier you can resell as your own

Count how many client workflows you intend to run, not how many people will log in. A reseller sells the finished result under their own name, so the useful measure is capacity per client, not seats per team. The tier table on softwareprogrammer.app sets that capacity by volume, and the BYOK unlimited level removes the volume ceiling in exchange for your own model key.

One connection screen carries the setup for every app you already pay for. That matters because each client brings a different stack, and reconnecting the same tools across several accounts is the part of reselling that quietly eats your week. A single screen for many apps keeps that work in one place rather than scattered across separate client builds.

Work runs inside your accounts, so the research, writing, sending, updating and logging happen where your data already sits. You are not exporting a client's records into a separate system to make the automation function. For a white-label partner, that keeps the arrangement simpler to explain and simpler to hand over when a client asks how the work gets done.

Three lifetime tiers sit on the published table: Starter lifetime, Growth lifetime and BYOK unlimited lifetime. They differ by volume and by how model usage is paid. Starter and Growth carry the volume allowance the platform supplies, while BYOK unlimited moves the model cost onto a key you provide. Read the table on softwareprogrammer.app for the exact allowances before you commit.

Guided setup and an activity log come with the platform itself rather than a single tier. The guided setup shortens the distance between connecting an app and running a workflow, which helps when you onboard a client stack you have not seen before. The activity log gives you a record of what the automation did, useful when a client asks what changed and when.

Growth sits above Starter on volume, so it suits a reseller running several client workflows rather than one. BYOK unlimited suits a partner whose request volume is hard to predict, provided you are willing to manage a model key and accept that your provider bills it. Choosing between them is a question of predictable volume against predictable model spend.

Behind the tier choice sits a licence question. A reseller needs permission to use the tool for client work and to present the outcome under their own name. Tiers by volume and by BYOK describe capacity, not rights. Before paying, read the terms on the vendor site and confirm that client use and white-label presentation are allowed, because a generous tier with a restrictive licence is no use to you.

The second question is whose accounts the work runs in. Because Automate acts inside your accounts, the reach of each workflow depends on the permissions those accounts already grant. If a client grants limited access, some steps will not run. Map that before you quote a client, so the scope you promise matches the access you will actually hold.

The third question is how you will charge. Selling the outcome rather than a login means your client does not need their own subscription or their own setup session. You carry the platform, you deliver the result. That model works when your tier capacity covers the client workflows you take on, and when your licence lets you present the work as your own.

Moving up a tier buys headroom, not new rights. The step from Starter to Growth widens the volume your workflows can use, which matters once you run the same automation for more than one client. It does not change what the platform can reach inside your accounts, because that stays bound by the permissions you hold.

The step to BYOK unlimited changes how model usage is paid rather than what the AI can do. You supply the key, your provider bills the requests, and the volume ceiling on the platform side lifts. For a partner with steady client demand and a model provider they already trust, that trade can be easier to forecast than a fixed allowance.

Whichever tier you choose, keep one client workflow as your test before you upgrade. Run it end to end, watch the activity log, and note where a permission gap or a confirmation step slows things down. That evidence tells you whether the next tier is genuinely needed or whether your current level already covers the work.