Do we need to learn Clay?

No. Our GTM engineers build and operate the workflows. You see the output (enriched contacts in your CRM) without touching Clay yourself.

How much does Clay cost?

Clay credits depend on volume and the depth of enrichment. We size the credit pack during onboarding so you do not overpay or run out mid-month.

Integration · Data & enrichment

Clay: Programmable data enrichment and workflow engine for modern outbound.

Clay is where our GTM engineers spend most of their time. It is the orchestration layer that turns raw Apollo, ZoomInfo, LinkedIn, and signal data into clean, enriched, validated lists ready for sequencing.

Short answer

How do you use Clay for outbound prospecting?

Clay sits between your account list and your sequencer. You import or find accounts, waterfall-enrich contacts across multiple providers so you only pay when the cheaper source misses, score fit and signal in the table, generate the personalization line, then push only rows that pass the score into the sequencer. Run as a weekly refresh, one well-built Clay table replaces most of a list-building headcount.

Waterfall enrichment first: cheapest provider, then fall back, then verify.
Score in Clay, not in the sequencer, so bad rows never reach a mailbox.
Personalization is a claim about the account, not a merge tag.
Refresh weekly. A Clay table you build once decays in about 60 days.

What we operate

How our pod runs Clay.

Build waterfall enrichment for email, mobile, and firmographic data
Stitch signal sources (funding, hiring, tech installs, job changes) into one feed
Use AI (Claude, GPT) to score ICP fit and write 1:1 first lines at scale
Push validated, enriched, scored contacts into HubSpot/Salesforce/sequencers
Operate Clay as the central pipeline between every data source and the CRM

Use cases

Where Clay earns its place in the stack.

Email waterfall enrichment

Combine 5–8 providers (Apollo, Hunter, Datagma, Findymail, Prospeo) into a single waterfall that gets 85%+ coverage on ICP contacts.

AI-personalized first lines at scale

Pull LinkedIn activity, recent posts, company news, and 10-K filings into a Claude prompt that writes a 1:1 first line per contact.

Signal stitching

Combine funding rounds, leadership hires, job postings, and product launches into one ranked feed of accounts to work this week.

Example workflows

Real Clay plays we ship.

Series A funding play

01Crunchbase webhook fires on a fresh Series A in the ICP
02Clay enriches the account: tech stack, headcount, leadership
03Buying committee is pulled from LinkedIn + Apollo with mobile enrichment
04Claude writes a 1:1 first line referencing the round and the use case
05Contact is pushed to Smartlead/Outreach in a dedicated funded-co sequence

Job-change trigger

01Buyer changes jobs at an ICP account (LinkedIn or Champify signal)
02Clay verifies new email and enriches the new company
03Sequence fires with a personalized 'congrats + relevant use case' message
04SDR is notified to follow with a LinkedIn touch on day 3

Best fit

Any B2B SaaS that wants modern, signal-based outbound instead of static-list spray. Required for Scale and ABM Command pods.

Pairs well with

Apollo ZoomInfo Smartlead Instantly Outreach HubSpot Salesforce

Setup

How we configure Clay in week 1.

The Foundation build installs Clay in your own account in this order. Each step is documented in the operating playbook we hand over.

01
Define the row
Decide whether the table is account-level or contact-level before anything else. Mixing the two is the single most common reason a Clay build becomes unmaintainable.
02
Source the accounts
Import from your CRM, a Sales Navigator export, or a signal source such as job postings, funding, hiring, or technology installs. Dedupe against closed-lost and open opportunities immediately.
03
Waterfall the enrichment
Chain providers in cost order for work email, mobile, and headcount. Add a verification step at the end and drop anything that comes back catch-all or risky.
04
Score fit and signal
Write a formula column that combines firmographic fit with the freshness and strength of the trigger. Set an explicit cut line and store it, so you can tune it later against reply data.
05
Generate the angle
Use an AI column to summarize why this account is worth contacting this week in one sentence, with a source URL in a neighboring column so an SDR can verify it in five seconds.
06
Push and write back
Send passing rows to Instantly, Smartlead, Outreach, or Salesloft with the signal, score, and source URL as custom fields. Write the same fields to the CRM so reporting can attribute meetings to the trigger.

Benchmarks

What good looks like with Clay.

Metric	Benchmark	Context
Enrichment hit rate	70-85%	Verified work emails on a well-built waterfall for US mid-market.
Cost per verified contact	$0.08-$0.25	Blended across providers when the waterfall is ordered by cost.
Rows that pass scoring	20-35%	Of sourced rows, on a table with a real cut line.
Refresh cadence	Weekly	Signals decay fast. Monthly refresh visibly reduces reply rate.

Ranges reflect what we observe running B2B SaaS mid-market motions. Treat them as starting targets, not guarantees.

Failure modes

How Clay builds go wrong.

Enriching every row before scoring, which burns credits on accounts you will never contact.
Letting AI columns invent details. Always keep the source URL beside the claim.
One giant table doing sourcing, scoring, and messaging with no clear owner.
Pushing unverified emails straight into a sequencer and blaming deliverability later.
No refresh cadence, so the table quietly ages out of relevance.

FAQ