Which lifetime tier fits your lead list work?

Begin with what you hand a client at the end of a run: rows, each one traceable to an app you connected. That is the unit your purchase has to support. The tiers published on softwareprogrammer.app are lifetime purchases, and the split between them comes down to how much work you push through and whether you supply your own model key.

Because you deliver lists rather than internal reports, the volume you actually run each month is the first number to get right. Count the enrichment steps, the verification steps and the handovers you do per client, then map that against a tier. Guessing high costs you at purchase, and guessing low leaves you stacking work outside the platform.

The cost question also has a second side that does not appear on the pricing table: your own model key on the BYOK tier. That spend is billed by your provider as you use it, so plan for it as an ongoing cost of delivery while the tier itself stays a single purchase. Keep both numbers in the same budget line.

Each tier carries the same core arrangement. You open one connection screen, link the apps your clients already use, and let the AI act inside those accounts on your behalf. Starter lifetime is the entry point; Growth lifetime covers heavier monthly volume; BYOK unlimited lifetime removes the volume ceiling in exchange for your own model key.

On a normal day that means you set up a guided sequence, watch it collect and check contacts, and read the activity log to see what ran and in what order. Because the work happens inside your connected accounts, the rows land where your client expects them, with the trail you can show when a contact is questioned.

Choosing between Growth and BYOK is a question of predictability. If you want the platform to carry the model cost inside the tier, stay on a volume tier. If your own provider terms suit you better and you expect wide swings in volume across clients, the key-owned tier keeps the work unbounded while the billing sits elsewhere.

Can you stand behind every row? That doubt is the right one, because a list that cannot be traced back damages the relationship more than a late delivery. The activity log exists to answer it: each run leaves a record of the steps taken and the accounts touched, and you can point a client at it when a single contact is challenged.

Nothing here manufactures verification you have not set up. If you want a source column on every row, build the sequence so the source is written as the row is collected. The platform carries the steps and keeps the trail; the standard for what counts as verified stays yours, and that is what protects the client relationship.

The other half of the doubt is about access. Runs can only act within the permissions your connected accounts grant, so a client system you cannot reach will not appear in the output. Agree access with the client before you promise a list, and the deliverable stays inside what you can actually see.

Set the three tiers beside each other against one client engagement rather than against a feature list. Ask the same three questions of each: does the volume cover the lists you promise, does it keep the trail your client needs, and does the billing arrangement suit your provider terms. The answers narrow the choice quickly.

Starter lifetime suits a contractor running a small number of lists who wants the connection layer and the log without paying for headroom they will not use. Growth lifetime suits steady monthly delivery across several clients. BYOK unlimited lifetime suits work where volume changes sharply and you are comfortable owning the model billing directly.

Before you commit, run one real client list through the tier you are considering and read the log afterwards. That tells you more about fit than any table, and it shows you whether the permissions on the accounts you connect are enough to finish the job without manual patching on your side.