Paying for demo booking, not for list size

What you pay for is the run itself: a named set of operations managers in named countries, contacted through the apps you already use, with the activity written back where you can see it. The platform does not sell you a bigger list. It sells the work of turning a target definition into booked demos, executed inside accounts you already hold.

Set-up happens on one connection screen rather than a project of integrations. You authorise the mail, calendar and record apps your team already pays for, and the platform reaches them through those permissions. Model usage is either carried by the tier you buy or pushed to your own key, depending on which tier you choose at checkout.

The practical question is what a demo costs you in effort now. A two-person team spends its day in mail threads and calendar links, and the tier replaces part of that routine. Read the lifetime tiers on softwareprogrammer.app before you compare anything else, because the split between volume and key ownership is the whole decision.

Moving up a tier changes how much work can run, not which steps exist. The connection screen, the guided set-up and the activity log arrive with the product, and the tiers divide on volume and on whether you supply a model key. A two-person team should map its monthly outreach to that volume before choosing.

Volume is the first lever. If your target list of operations managers in named countries is small and you contact each one a handful of times, the lower volume tier fits the shape of your week. If you widen to more countries or more titles per country, the ceiling arrives sooner and the higher tier starts to make sense.

The other lever is the key. Taking the tier where you bring your own key moves model billing to your provider account, which suits a team already holding a key and watching that spend. It is not a discount on the tier itself; it is a different place for one cost to land, so decide which account should carry it.

The worry is sound: a list can look large and still hold no one who signs off a purchase. Automate does not answer that by handing you a bigger list. It answers it by letting you define who counts as a decision maker and by putting the booking work inside your own accounts, so every demo booked traces back to a person you chose.

In practice you write the target as operations managers in the countries you name, and you keep the record apps that already hold your contacts. The platform reaches those records through the permissions you grant, and the activity log shows what ran and when. Reviewing that log is how a small team checks quality instead of trusting a count.

Two people can watch every reply, so the objection is best handled by your own checks. Qualify each booked demo against the definition you wrote, and drop titles that never book. The tier pays back when the demos are real, so treat the definition of a decision maker as part of the purchase, not an afterthought.

Compare the lower volume tier with the key-owned tier, since those two sit at opposite ends of the split for most small teams. One takes on volume while the platform carries model usage; the other removes the volume ceiling and sends model billing to your provider. Neither changes the guided set-up, the activity log or the confirmation pause.

Ask a direct question about your week. How many operations managers in your named countries can you genuinely contact and follow up with this month? If the number is modest, the lower tier covers it and keeps all cost in one place. If it grows as you add countries, the key-owned tier keeps the ceiling out of your way.

Then check your key situation. A team without a provider account it can bill cleanly should stay with the lower tier and keep one cost. A team already spending on a key can move that spend onto its own account and read both bills side by side before committing to either lifetime purchase.