A credit is not a universal unit

Two subscriptions advertising the same credit count may buy different work. One pool might fund email finding; another might charge separately for checking, enriching a company record or obtaining a phone number. A workflow can use more than one action for a single contact. Count the required actions before comparing prices per nominal credit.

Write a small specification: what information you already have, what field is missing, what result qualifies as usable and where the result must go. Do not assume that every returned row is a newly discovered contact or that every data action includes permission to export through your preferred route.

Separate platform work from purchased information

Clay’s official explanation distinguishes Actions from Data Credits. Its platform work and purchased data are therefore separate budget dimensions. A team using an external provider key may still incur platform activity as well as a separate external-provider bill. Treat that distinction as a question about the whole workflow, not a shortcut to calling one option free.

We have not pinned one payable Clay configuration to a single plan, billing cycle and allowance combination. Use a named quote to settle those dimensions together. Do not multiply a quantity from one configuration by a price from another and call the result a verified plan.

Use a small action ledger

For an illustrative 500-record project, suppose every record needs one company enrichment and one email check, while only 100 need an additional phone lookup. Your ledger contains 500 enrichment attempts, 500 checks and 100 phone attempts. It does not establish 1,100 billable credits: the provider’s action rates, successful-result rules and treatment of retries are still needed.

Keep attempted, successful and billable counts distinct. A no-result refund rule can change paid usage, but it does not make the missing field usable. The correct comparison might favor fewer enrichment steps, a smaller pack or no new subscription until the required sample is understood.

Expiry and recurring add-ons change the decision

Apollo’s pricing FAQ says unused credits expire at the billing boundary and describes recurring add-on credits. A buyer with irregular demand should therefore inspect the renewal setting and unused-value exposure. Do not value a pool as if it were permanent stock when its terms make it a period entitlement.

Hunter needs an additional product distinction. Its Data Platform gives Search and Verification pools upfront for a 12-month plan that automatically renews unless canceled; those credits do not refresh monthly. All-in-one uses unified credits, and its optional extra credit packs have their own three-month expiry. Do not carry the term or action rate from one purchase into the other.

Compare a useful delivered workflow

Ask about the exact API endpoints, user permissions, result fields, export format and account-level limits. Confirm whether retries or repeated requests incur another charge, and how you can audit usage. Estimate tax and external costs separately. Finish with a list of verified quantities and open constraints. SendCost leaves missing values unknown; a low estimated unit price cannot compensate for an unsupported integration or an undefined billable action.

Turn a monthly credit label into a purchase test

A quote for 2,500 credits per year is not a fresh allowance of 2,500 every month. If the project needs 500 of the same action each month, twelve months would require 6,000 actions before retries. That would mean 6,000 credits only under an explicit one-credit-per-action rule. Conversely, a one-time batch may not need a recurring subscription. Record the demand period separately from the invoice period: a monthly bill can still provide an annual or one-off allocation.

For each provider, write an action ledger with input field, operation, successful-result rule, unit charge, reset or expiry date and output destination. Keep external-provider charges separate from orchestration charges. Ask for one itemized sample workflow when a waterfall or retry can charge more than once.

Sources and further reading

Source-based editorial research. Vendor terms can change; confirm the current contract before purchase.

Continue your research