Clay Setup: Day-Zero Path to a Working Outbound Loop
Set up Clay for day-zero outbound — seats/credits, one ICP list, sequences or dialer, and CRM sync — before optional enrichment packs.
LMBy Lee M.Updated Aug 17, 20266 min readFact-checked
Quick answer
Set up Clay in this order: qualify seats/credits for day-one outreach, name one stack owner, build one ICP list, connect CRM sync, enable sequences or dialer, then have a non-admin find a contact, enrich, outreach, and log to CRM. You’re done when that walkthrough works — not when every enrichment pack is switched on.
Start on Free
Name one stack owner
One ICP list only
Connect CRM sync
Sequences or dialer
Prove a rep can run it
Clay day-zero setup media
Verified captures and vendor tutorials for configuring Clay before go-live — pipeline, contacts, and first workflows.
Official Clay setup walkthrough
Vendor tutorial for onboarding and configuration. It is not a SoftwareGlimpse rollout plan — use this guide for judgment.
This video is hosted on YouTube
This content is hosted by YouTube. The player loads only after you allow marketing cookies.
Official vendor tutorial
Clay 101: Claygent AI Web Scraper
What this shows
✓Claygent AI web scraper setup
✓Multi-provider research enrichment in Clay
Product screenshots
Product screenshots coming soon
We only publish verified captures from Clay's product interface — never stock images, mockups, or teaching diagrams. Screenshots appear here once editorial review confirms them.
What Clay actually is — Go-to-market data and enrichment platform that lets growth and RevOps teams build multi-provider waterfall workflows (Claygent AI research, enrichment, outreach prep) with Free, Launch, Growth, and Enterprise plans.
Configure these first — Research lists contact data, prospecting, data enrichment, and email outreach as supported — that is your day-zero surface.
Check gates and usage — Our research does not flag plan-gated capabilities for Clay, but confirm your must-haves — including credits and seats — against the packaging you actually intend to buy.
Start on the right package — Researched plans: Free, Launch, Growth, Enterprise. Never invent list prices here — confirm seats, credits, and quote terms on /pricing/clay/.
Sync only what the loop needs — Research names HubSpot, Salesforce, Apollo, Clearbit, and Zapier on the Clay side — confirm CRM sync and the connectors your daily loop depends on.
AI comes after habits — Research lists AI assistant, AI recommendations, AI automation, and AI email drafting for Clay. Research places AI assistance on Free, Launch, Growth, and Enterprise. Leave it off until the manual outbound loop is boring and reliable.
Finish the Clay outbound loop — prospecting, data enrichment, email sequences, and lead scoring — before optional packs.
Clay must vs nice
Must-have
✓One ICP list + suppressions
✓prospecting
✓CRM sync for logged activity
✓email sequences
Nice-to-have
•data enrichment
•AI assistance
Clay checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
1Qualify Clay seats and creditsDay-one must-haves on the cheapest researched package.
2Name one stack ownerCredits, lists, sync, and hygiene need an owner.
3Build one ICP listFilters match how you prospect in the next 90 days.
4Connect CRM syncPlus mailbox or dialer — document other gaps.
5Enable one outreach channelSequence or dialer — not both on day zero.
6Prove the non-admin loopFind · enrich · outreach · log — then write the setup note.
1. Start on the Clay package your must-haves need
Package choice decides what you can prospect and outreach in Clay at all.
Write five day-one jobs, map each to researched Clay packaging, and pick the cheapest tier that covers all five — including credits if usage-based. 1. List the five things the pod must do on day one.
Match each one to researched Clay packaging. Our research does not flag plan-gated capabilities for Clay, but confirm your must-haves — including credits and seats — against the packaging you actually intend to buy.
Pick the cheapest package that covers all five.
Check seats and credits, not just feature checkmarks. Confirm seat/credit caps for Clay before inviting everyone. Our pricing snapshot records a 14-day trial on Launch and Growth — confirm current terms on the Clay pricing page before you build a schedule around it. Never invent list prices here — confirm seats, credits, and quote terms on /pricing/clay/. Worked example: an 8-person B2B outbound pod needs prospecting, data enrichment, email sequences, and lead scoring plus CRM sync on day one in Clay. They start on Free and note which capabilities would force an upgrade.
2. Create the workspace and name one stack owner
Name Responsible + Accountable for Clay before anyone builds lists.
Name one stack owner — not a committee — before you invite the pod. 1. Create the workspace with real company identity and timezone.
Name one owner with ~2 hours a week for credits, lists, users, and sync hygiene.
Agree: new lists, sequences, and credit packs go through that owner only.
In Clay, open workspace, team, or billing settings — confirm the current control labels in the product, docs, or trial. Worked example: an 8-person B2B outbound pod makes ops the Clay stack owner, writes the two-hour commitment into the week, and blocks everyone else from buying credit packs for 30 days.
3. Build one ICP list — not five experiments
One clean Clay ICP list beats a folder of untrusted experiments.
Configure one ICP list that matches how you actually prospect for the next 90 days. 1. Freeze firmographics, personas, and exclusions in writing.
Build one saved list / search in Clay. prospecting is researched across every Clay plan we snapshot
Spot-check 20 records for title, email/phone quality, and company fit. Worked example: an 8-person B2B outbound pod builds one mid-market SaaS VP Sales list in Clay, suppresses existing customers, and rejects the list until 18 of 20 spot-checks look call-ready.
4. Connect CRM, enable one channel, prove the non-admin loop
Exit setup when a non-admin can finish the Clay outbound loop unaided.
Finish day-zero by proving a seller can run the loop without screenshots of another tool. 1. Connect CRM sync for contacts and activities. Research names HubSpot, Salesforce, Apollo, Clearbit, and Zapier on the Clay side — confirm CRM sync and the connectors your daily loop depends on.
Enable one outreach channel — sequences or dialer, not both. email sequences is researched across every Clay plan we snapshot
Have a non-admin: find a contact, enrich if needed, send or dial, and confirm the activity landed in CRM.
Write a one-page setup note: package, owner, list, channel, known gaps. Worked example: an 8-person B2B outbound pod connects HubSpot, turns on a three-step email sequence in Clay, and only invites the rest of the pod after Priya completes find → enrich → send → CRM without help.
Frequently asked questions
How long should Clay setup take?
A focused pod can finish day-zero setup in one working day if seats/credits, ICP list, CRM sync, and one outreach channel are already decided. Multi-week “setup” usually means undecided packaging or missing ownership.
Do we need every enrichment feature on day one?
No. Prove prospecting → outreach → CRM logging first. Add enrichment packs only when a named decision depends on them.
Where do we confirm seats and credits?
Never invent list prices here — confirm seats, credits, and quote terms on /pricing/clay/.