Tools
Clay credits: how to keep enrichment costs under control
Practical ways to reduce Clay credit usage in outbound: filter early, order waterfalls by cost, cache results, limit AI columns and monitor spend.
Founder, OretonGTM · ·1 min read
Clay is powerful precisely because every column can call something. That’s also why costs surprise people. A few structural habits keep spend predictable.
Where credits go
| Cost driver | Common mistake |
|---|---|
| Company enrichment | Running on accounts that obviously don’t fit |
| People search | Searching every account instead of Tier 1 and 2 |
| Email and phone waterfalls | Expensive providers first |
| AI columns | Running on every row, including disqualified ones |
| Re-runs | Re-enriching data you already have |
Seven habits that cut costs
- Dedupe against your CRM first so you never pay for existing contacts (dedupe guide).
- Filter early with cheap firmographic data before anything else.
- Run conditional columns: only enrich rows that pass the previous filter.
- Order waterfalls by cost and stop at the first valid result.
- Run phone enrichment only for accounts reps will call.
- Run AI columns last, on qualified rows only.
- Cache and reuse: keep a master table of enriched accounts instead of re-enriching per campaign.
My take: Design every Clay table like a funnel. The expensive columns should only see the rows that survived every cheaper filter.
Monitor usage
- Track credits per table and per campaign
- Compare against qualified contacts produced (cost per valid contact)
- Review monthly and prune columns that don’t change decisions
Use your own keys where it makes sense
If you already pay for a data provider or an LLM, connecting your own API key may reduce costs. Compare total cost at your volume before switching.
New to Clay? Start with Clay for beginners and how to compare data providers.
Frequently asked questions
Why do Clay credits run out so fast?
Usually because enrichments run on every row before filtering, waterfalls query expensive providers too early, or AI columns run on accounts that will never be contacted.
What is the cheapest way to structure a Clay table?
Cheap columns first (company enrichment and filters), then contact search only for qualified accounts, then waterfalls ordered by cost, with AI columns last and only on qualified rows.
Should I use my own API keys in Clay?
For providers you already pay for, connecting your own keys can lower costs. Compare the total cost of both options for your volume.