GTM RevOps
Saved on this device
Free planning tool

Clay credits calculator

Model the data credits and actions your Clay workflows may use—before you build them.

Live estimate

Updates as you scope the workflow

Annual data credits116,4009,700 / month
Annual actions1,184,00098,666.7 / month
Action mix87% enrichment
Enrichment 1MExports 152K
By population
Accounts28.4K credits304K actions
Contacts88K credits880K actions
Signals0 credits0 actions
Step 1

Size the audience

Estimate how many CRM records this workflow will actually touch.

A

Accounts

Audience size

16,000
35,000 × 40%+ 2,000 new= 16,000
C

Contacts

Audience size

44,000
100,000 × 40%+ 4,000 new= 44,000
Step 2

Scope the enrichments

Set credit cost, coverage, frequency, and whether you bring an external API key.

How actions workA standard enrichment uses 1 action per run. A waterfall assumes 3 actions. Coverage affects data credits, while actions are based on the full audience.

Account enrichments

16,000 records in scope

28.4K credits · 240K actions
EnrichmentCredits eachWaterfallCoverageTimes / yrExternal key

Contact enrichments

44,000 records in scope

88K credits · 792K actions
EnrichmentCredits eachWaterfallCoverageTimes / yrExternal key

Signal enrichments

Recurring checks against an account or contact population

0 credits · 0 actions
SignalCredits eachChecks / yrPopulation
Step 3

Plan how you’ll act

Count the downstream syncs, notifications, content, and prospecting touches.

Account-level activation

16,000 records in scope

64K actions
times / year
32,000 actions
times / year
0 actions
times / year
32,000 actions
times / year
0 actions

Contact-level activation

44,000 records in scope

88K actions
times / year
0 actions
times / year
0 actions
times / year
88,000 actions
times / year
0 actions
Your scoped estimate

CRM Enrichment

Approximately 116,400 data credits and 1,184,000 actions per year.

Calculation assumptions

Audience size equals CRM volume × relevant percentage + expected new records.

Data credits equal audience × coverage × annual frequency × credits each. External API keys set data credits to zero.

Actions equal audience × annual frequency. Waterfalls assume three actions per record. Coverage does not reduce actions, matching the source template.

Estimates are directional. Actual Clay usage varies by workflow design, provider, retry behavior, and coverage.