TL;DR
  • Garbage in, garbage out. Every sequence, every AI personalization, every conversion metric depends on the quality of your account and contact data.
  • Clay is the enrichment layer that pulls from 75+ data providers simultaneously and lets AI make sense of it.
  • AI scoring replaces gut feel โ€” every account gets a tier based on real fit signals, not who the rep felt like calling.
  • This playbook runs once and stays live โ€” new leads flow in enriched and scored without manual effort.
  • Without this foundation, every other playbook on this page is running at half-speed.

WHY MOST OUTBOUND *LISTS* FAIL

Walk into any early-stage B2B company running outbound and you'll find the same thing: a rep with a spreadsheet full of names, a sequencing tool, and a mystery reply rate somewhere between 1โ€“3%.

The instinct is to fix the copy. Or try a new channel. Or book a consultant to "optimize the sequence." None of that helps when the real problem is that the list is wrong โ€” wrong companies, wrong contacts, wrong timing, zero context.

Cold outbound converts when three things are true simultaneously: the account is the right fit, the contact is the right person, and you reach them with context that's relevant right now. A raw Apollo export or a scraped LinkedIn list gives you none of that.

Clay fixes this at the source.

HOW THE *ENGINE* WORKS

The Clay Enrichment & Scoring Engine is a living database that sits between your lead sources and your sequencing tools. Every lead that enters your pipeline passes through it โ€” getting enriched across 75+ data providers, scored by AI against your ICP definition, and routed to the right sequence automatically.

Layer 1 โ€” Account Enrichment

For every company in your list, Clay pulls firmographic data (headcount, revenue band, industry, tech stack, funding), enriches with real-time signals (recent funding, hiring velocity, tech changes, job posts), and stores a clean, normalized record in your Clay table.

โ†’
Why it matters

Waterfall enrichment across multiple providers means a 90%+ match rate on company data โ€” dramatically better than any single-source tool.

Layer 2 โ€” Contact Sourcing & Verification

Clay uses Findymail and BetterContact in a waterfall model to source and verify email addresses. Contacts that don't return a verified email don't enter your sequences โ€” keeping bounce rates under 3% and protecting sender reputation.

Layer 3 โ€” AI ICP Scoring

Once enriched, every account and contact runs through an AI scoring prompt you define. Claude or GPT evaluates the enrichment data against your ICP criteria and outputs a tier โ€” A (hot), B (warm), C (nurture) โ€” with a reasoning summary for the rep.

Example AI Scoring Prompt (Clay ยท Claygent)
You are a GTM scoring assistant. Score this account from 1โ€“10 for ICP fit and assign a tier (A/B/C). ICP Definition: B2B SaaS companies, 20โ€“200 employees, US-based, Series Aโ€“B funded, using Salesforce or HubSpot, hiring SDRs or AEs. Account data: {{account_enrichment_json}} Respond in JSON: {"score": X, "tier": "A/B/C", "reasoning": "2-sentence summary"}

Layer 4 โ€” Sequence Routing

Based on tier, Clay automatically pushes records to the right destination: A-tier accounts into high-touch, personalized sequences in Instantly or Apollo. B-tier into a standard sequence. C-tier into a nurture track or suppressed entirely. No manual routing, no rep judgment calls, no leads falling through the cracks.

THE BUILD IN *5 STAGES*

01
ICP Definition & Source Mapping

Before touching Clay, we lock in your ICP โ€” company size bands, industries, geographies, tech stack signals, and the job titles that matter. We also map your lead sources: Apollo exports, LinkedIn lists, inbound form fills, CRM segments. Every source gets a defined intake column in Clay.

02
Clay Table Architecture

We build the Clay table structure โ€” account columns, contact columns, enrichment result columns, score columns, and routing flags. Provider waterfall logic is configured so Clay tries Findymail first, then BetterContact, then Apollo email verification as fallback.

03
Enrichment Waterfall Build

Each enrichment provider is connected and mapped. We configure Clay to run enrichments only when upstream data is missing โ€” avoiding redundant API calls and keeping Clay credit burn predictable. Typically: Clearbit โ†’ People Data Labs โ†’ Apollo โ†’ LinkedIn scrape for firmographic, plus Findymail waterfall for email.

04
AI Scoring Claygent Setup

We write and test the AI scoring prompt against 20โ€“30 real accounts from your existing list, calibrating the scoring to match your actual ICP fit intuition. Once calibrated, the Claygent runs on every new record automatically.

05
HubSpot Sync & Sequence Routing

Scored records sync to HubSpot with tier and enrichment data mapped to custom properties. Workflows in HubSpot (or Instantly) pick up A/B/C tier and enroll contacts in the right sequence automatically. The loop closes: lead in โ†’ enriched โ†’ scored โ†’ sequenced. No human hand-off required.

WHAT *RUNS* THIS

ClayClay
ApolloApollo
FindymailFindymail
BetterContactBetterContact
HubSpotHubSpot
InstantlyInstantly
Tool Role in the Engine
ClayCentral enrichment layer, AI scoring, waterfall logic, CRM sync
ApolloLead sourcing, contact data, email verification fallback
FindymailPrimary email waterfall โ€” high deliverability verification
BetterContactEmail waterfall fallback โ€” mobile numbers, secondary enrichment
HubSpotCRM destination โ€” contacts, companies, tier properties, workflows
InstantlySequence enrollment based on tier routing from HubSpot

WHAT YOU GET *BUILT*

This isn't a template or a walkthrough video. Here's what exists inside your stack when we're done:

DeliverableDetails
Clay TableFully configured enrichment table with all provider waterfalls connected and mapped
AI Scoring PromptCalibrated Claygent prompt tuned to your ICP, tested against real accounts
Email WaterfallFindymail โ†’ BetterContact โ†’ Apollo fallback, auto-suppressing unverified contacts
HubSpot PropertiesCustom contact/company properties for tier, score, enrichment source, reasoning
Routing WorkflowsHubSpot or Instantly workflows that auto-enroll by tier into correct sequences
RunbookDocumentation covering how to add new sources, update ICP scoring, and monitor credit burn
โš 
Foundation First

This is the playbook every other Blue Line playbook builds on top of. If you're implementing multiple systems, start here. Running signal-based outbound or LinkedIn automation on a bad list defeats the purpose.