Which Automate plan suits contracted lead generation work

Set the price list beside the volume of contacts you hand over to clients each month. The tiers are named Starter lifetime, Growth lifetime and BYOK unlimited lifetime, and they differ by volume as well as by whether you bring your own model key. Read each tier as a ceiling on work rather than as a feature bundle.

Your client asks where each row came from, so the tier you choose must let you keep the research inside accounts your client can inspect. Because work runs inside your own accounts and the platform shows an activity log, the record of what was researched and sent stays with you. That record is what backs each row you deliver.

One connection screen handles many apps, which matters when each client brings a different stack. You connect once, then ask the AI to research, write, send, update and log. Pricing is a lifetime purchase published on softwareprogrammer.app, so treat it as a one-off cost to recover across the clients you serve, not a monthly line.

Match the tier to the number of rows you deliver, not to the number of apps you connect. If your output is steady and modest, the entry tier carries that load. If your client base grows, the higher volume tier gives you room without changing your working method. Check the published tiers for the volume each one covers.

The BYOK unlimited lifetime tier suits a contractor who already holds a model key and wants usage billed through it. On that tier the model provider bills you directly, so you can see model cost separately from the platform cost. For someone delivering lists with a source per row, that separation helps you quote accurately.

Guided setup shortens the time before your first delivery on any tier. You connect the apps each client already pays for, then describe the research and logging steps you want run. Setup is configuration, not development, and the activity log gives you a trail from the first run onward.

Check permissions before you quote a client. The platform can only reach what your connected accounts allow, so any app your client restricts stays outside the automation. If a row depends on data you cannot access, you cannot verify it, and that is the objection this buyer raises.

Confirm how much of the workflow needs a human in the loop. Steps classed as destructive wait for your confirmation, which is good for safety and slow for throughput. Plan delivery dates around that pause rather than assuming every step runs unattended.

Understand what the BYOK tier means for your costs. On that tier your own model key carries the usage and your provider bills you, so model spend sits with you rather than the platform. Budget for it before you commit to a fixed client price.

Compare adjacent tiers on volume first. The step from Starter to Growth buys headroom, so ask whether your current delivery rate would strain the lower ceiling within a reasonable period. If it would, the higher tier avoids a second purchase later.

Then compare Growth against BYOK unlimited on how you want model cost handled. Growth keeps usage inside the platform arrangement, while BYOK moves it to your own key. Neither is better in the abstract; the choice follows whether you prefer one invoice or separate ones you can attribute to clients.

Finally, weigh the risk of buying too high. A lifetime tier is bought once, so an oversized tier is money spent on capacity you may not use. Start where your delivery volume sits, and move up only when the current tier is the thing holding your output back.