Paying for verified rows, not for a monthly seat

What you pay for is a single connection screen across many apps, a place where the work runs inside accounts your client already uses, and a guided setup with an activity log behind it. Nothing in that list is a list of contacts. You are paying for the machinery that touches the tools where your contacts live.

Think about how a delivery actually happens. You pull from a source, enrich, check, then write the finished rows into the client's own system. Automate connects those steps on one screen so the records move between apps without you rebuilding the handoff each time a new client arrives.

The activity log is the part a contractor should care about most when quoting. When a client asks where a row came from, the log gives you a trail of what ran and when. That trail is what turns a delivery into something you can defend, and it is bound to the accounts you connect.

Because the tiers are lifetime, the money question is not a monthly renewal that quietly eats your margin on a retainer. It is a single purchase you weigh against the volume of rows you expect to push through each month.

Across the three lifetime tiers, two things move. One is volume, which matters directly to a contractor whose client list grows or whose campaigns run hot in some months. The other is key ownership, which moves model billing to your own provider account on the BYOK unlimited tier.

You will see the named tiers as Starter lifetime, Growth lifetime and BYOK unlimited lifetime. The published split is volume on the first two and key ownership on the third, so the climb is not a feature ladder where each rung adds a new screen. It is a choice about how much work passes through and who pays for the model.

For lead generation specifically, volume is the axis that bites first. A client with a large list and frequent refreshes will push more rows than a client with a small, slow-moving database, so match the tier to the busiest retainer you carry.

Key ownership is the other axis, and it suits a contractor who already holds a provider account and wants model usage billed there rather than carried inside the tier.

The hesitation you named is unverifiable rows that damage the client relationship. Read the product against that fear and the activity log becomes the relevant part, because it records what ran. A row you cannot trace is a row a client can reject, and the log is where tracing starts.

The other half of the answer is about reach. What a run can touch stops at the permissions on each connected account, so a client app that has not been authorised stays outside the work. That is not a defect to work around. It is the boundary that keeps you from writing into places nobody approved.

Steps that would delete or overwrite records wait for your confirmation, so a cleanup sequence will pause rather than finish on its own. For a lead contractor that pause is useful, because it keeps a bulk write from running while you are not looking at it.

Start by counting the rows a normal month pushes through. If your clients ask for frequent refreshes on large lists, the volume side of the decision is settled by that number and by how often it spikes. Pick the tier that covers your busiest retainer, not your quietest one.

Then decide who should hold the model key. If you already run a provider account and want those requests billed there, the BYOK unlimited tier is the one that matches. If you would rather keep model usage inside the tier you paid for, compare the two volume tiers instead.

Whichever you pick, plan the verification step as part of the delivery. The log gives you the trail, but you still decide which rows are fit to hand over. The tier buys the machinery, and the checking stays with you.