TL;DR: Clay handles lead enrichment, ICP scoring, waterfall data lookups, and automated routing inside one spreadsheet-like table. This guide covers five practical use cases: building outbound lists from scratch, enriching inbound leads automatically, scoring contacts against your ICP with formula columns, filling data gaps with waterfall enrichment, and routing qualified leads to reps or sequences without manual triage.

Clay Platform Use Cases: Lead Enrichment, Scoring, Routing, and List Building

Last updated: June 2026

Clay crossed a $1.25B valuation in 2024 after 6x year-over-year growth, and in 2026 it has become the default enrichment and workflow layer for B2B GTM teams that have outgrown point solutions. The questions GTM builders are asking have shifted from whether to try Clay to which use cases to tackle first, and in what order.

Does Clay Handle Enrichment, Scoring, AND Routing. or Just One?

Clay handles all three, and most teams underuse at least two of them. Founders typically set it up for enrichment, discover the formula columns, and never build routing. That leaves most of the platform unused.

The full pipeline works like this: import a list or pull leads directly from Clay's built-in prospecting tools, enrich every record using data from 100+ providers through waterfall lookups, score each lead against your ICP using formula columns in the same table, and route the top scorers to a rep via Slack or into a CRM sequence automatically. Each use case in this guide maps to one layer of that pipeline. You can work through them in sequence or start with whichever gap your GTM stack has right now.

Use Case 1: Building Lead Lists Without a Prospecting Team

Most teams think of Clay as an enrichment tool. They import a list from somewhere else, run enrichment, and export the results. That's the narrow version. Clay also includes native prospecting: you can search for companies and people directly inside the platform, filter by the criteria that define your ICP, and build an outbound list from scratch without touching a separate data tool.

The search columns pull from sources including LinkedIn, Apollo's API, Google search results, and website scrapers. You can stack filters: companies with 50 to 500 employees, Series A or later funding, a CTO or VP of Engineering job title, and no existing record in your CRM. Clay queries each source and surfaces the contacts that match, directly inside your table.

A common scenario for early-stage founders: you need 200 ICP contacts with verified emails for a first outbound push, but you don't have an SDR or a Lusha subscription. Clay handles the prospecting and enrichment in one workflow. Once the table is built, you push the contacts directly into your sequencing tool via a webhook or native integration. No CSV export, no re-import, no reformatting.

Where this saves the most time is in the setup overhead. Building a targeted list manually across LinkedIn Sales Navigator, Apollo, and a data enrichment tool used to mean three browser tabs, a spreadsheet to reconcile duplicates, and a verification step before outreach. In Clay, those steps live in a single table, and changes to filters update the list in real time.

If you are doing your first outbound push or rebuilding prospecting from scratch, outbound lead generation is worth reading alongside this guide for the fuller picture of how list building fits into an outbound motion.

Use Case 2: Enriching Inbound Leads Automatically

When a lead fills out a demo request or a contact form, your sales rep typically gets a name and an email address. Everything else requires manual research: find the company size on LinkedIn, check the funding stage on Crunchbase, figure out what tech stack they use from their job postings. Reps at SaaS companies spend most of their research time on tasks like this before they can make a qualified call.

Clay eliminates that research step through webhook-based enrichment. When a lead submits a form, the form tool fires a webhook to a Clay table. Clay receives the record and runs enrichment automatically: company headcount, funding round and stage, tech stack (what tools they use, pulled from job listings and Clearbit), LinkedIn headline and seniority, company website, and any custom signal you want to check.

You can also add AI columns that answer specific questions about each record. For example: 'Is this company in fintech or insurtech?' or 'Does their tech stack include Salesforce, HubSpot, or a competing product?' These AI columns process each row and return a structured yes/no or a short answer, which you can then use in routing logic.

Once enrichment runs, Clay pushes the updated record back to your CRM and triggers a Slack alert to the assigned rep. A full enrichment pass typically takes under 60 seconds from form submission to CRM update. The rep's first view of the lead includes company size, funding status, tech stack, and job title seniority, without doing any research themselves.

For the inbound side of the funnel, this is one of the highest-use Clay setups. According to research cited across multiple sales reports, responding to a lead within one hour makes you seven times more likely to qualify them. Automated enrichment means the rep is not doing background research during that first hour.

For more on the inbound side, how to automate lead qualification covers the broader workflow including scoring and handoff.

Use Case 3: ICP Lead Scoring with Formula Columns

Lead scoring in Clay uses formula columns, which work like spreadsheet IF and SUM formulas but reference enriched data fields in your table. You define the scoring logic once and every row scores automatically as enrichment runs.

Start by identifying the explicit attributes that correlate with closed deals. For a B2B SaaS company targeting mid-market companies, those might be company size (employees), funding stage, job title seniority, industry vertical, and whether the prospect uses a competing tool. Then assign points to each attribute based on how strongly it signals fit.

A practical example scoring table:

Each attribute maps to a formula column. Clay sums the columns into a total score field. You then define threshold bands that determine what happens next: leads above 60 route to sales as hot; leads between 30 and 59 go to nurture sequences; leads below 30 stay in top-of-funnel awareness.

The more sophisticated version is two-axis scoring: a separate formula column for ICP fit (firmographic attributes like company size, funding, title) and a second column for intent signals (behavioral data like page visits, downloads, email engagement). A lead with a high fit score but low intent needs nurturing. A lead with high intent but low fit might convert this month but churn in six. Scoring them separately keeps the routing logic honest.

According to Salesforce's 2024 State of Sales report, sales reps spend about 70% of their week on admin work, data research, and CRM cleanup. A Clay scoring model shifts that overhead: instead of a rep manually reviewing 200 leads to decide who to call, the formula runs on all 200 and surfaces the 20 that actually qualify.

For more context on ICP frameworks that inform scoring criteria, ICP scoring methodology for B2B sales covers how to define and weight the attributes.

Use Case 4: Waterfall Enrichment to Fill Data Gaps

Single-provider enrichment tools have a ceiling on match rates. Clearbit might find an email for 60% of your contacts. Hunter might find a different 20%. If you only run Clearbit, you're leaving 40% of your list without contact data and paying for every lookup regardless of whether it returns anything useful.

Clay's waterfall enrichment solves this by stacking providers in a sequence. You configure which provider to try first for each data type, then which to fall back to if the first returns nothing. A typical email waterfall might run Clearbit first, fall back to Hunter, then Lusha, then Datagma. Clay only charges credits when a provider actually returns a result. If Clearbit finds the email, the other providers do not run.

The match rate improvement is substantial. Teams report doubling or tripling their email match rates compared to single-provider setups, which directly affects how many contacts in an outbound list are actually reachable.

Waterfall enrichment matters most in a few specific situations:

Imported lists with missing data. Apollo exports, LinkedIn scrapes, trade show attendee lists, and conference badge scans rarely come with verified emails or accurate firmographics. Running them through a waterfall fills the gaps before you pass the list to a sequencer.

Stale CRM records. B2B contact data decays at roughly 25-30% per year. Job titles change, people leave companies, phone numbers go out of service. A waterfall re-enrichment pass on your existing CRM data catches what single-provider enrichment missed the first time.

High-value accounts. For enterprise accounts where a single deal is worth significant revenue, exhausting every enrichment source before reaching out is worth the credit cost.

For a deeper look at how enrichment tools compare beyond Clay, best B2B data enrichment tools has current pricing and coverage comparisons.

Use Case 5: Automated Lead Routing Based on Score and Tier

Scoring a lead only matters if something happens differently based on the score. Clay's action columns connect scores to destinations: once a row meets a threshold, the action column fires the appropriate output without manual intervention.

The routing logic maps score bands to different outcomes:

High score (60+ points): Clay creates or updates a CRM record with all enriched data, logs the scoring rationale in a notes field, and sends a Slack notification to the assigned rep. The rep gets the lead with full context: company, title, score breakdown, and the behavioral signals that pushed the score above threshold. Some teams also trigger a calendar invite to the rep so they can book response time immediately.

Mid score (30-59 points): Clay adds the contact to a HubSpot email sequence or updates a marketing automation tag that triggers a nurture campaign. The lead gets ongoing contact without a rep manually moving them between lists.

Low score (below 30 points): The contact stays in awareness, gets pushed to a retargeting audience, or holds for future re-scoring as their behavior or company signals change.

For teams with multiple reps, Clay supports round-robin routing. Instead of sending every high-scoring lead to the same rep, Clay cycles through the rep pool and assigns each lead to the next in rotation, keeping workloads balanced without a sales ops person managing the queue.

The speed argument for automation is concrete. Research consistently shows that responding to a lead within one hour makes you seven times more likely to qualify them than teams that wait longer. When routing is manual, that one-hour window gets eaten by triage: someone has to look at the lead, decide its priority, figure out who should handle it, and pass it along. Automated routing removes that triage step entirely. The right rep gets the right lead immediately, every time.

What Clay Can't Do on Its Own

Clay is a powerful enrichment and workflow layer, but it has real limits worth knowing before you commit to building on it.

Clay does not send outreach. It enriches, scores, and routes. Actual emails go through a sequencer: Smartlead, Instantly, HubSpot Sequences, or a similar tool. Clay feeds the sequencer with enriched contacts and can trigger sequence enrollment via API or native integration, but sending and tracking deliverability is outside its scope.

Setup takes real time. Building a functional Clay workflow means designing table structure, configuring waterfall sequences, writing formula column logic, and testing routing actions before it works correctly. Teams typically spend several hours on initial setup and additional time debugging edge cases. This is not a plug-and-play tool.

Credit costs scale with list size. Clay charges per enrichment result. Enriching a large list without pre-filtering for ICP fit can get expensive quickly. The fix is to filter first (company size, industry, funding stage) before enriching, so you only pay for contacts that could actually convert.

Clay is not a CRM. It is a workflow layer that feeds into your CRM. It does not store longitudinal contact history, manage pipeline stages, or generate activity reports. You still need HubSpot, Salesforce, or a similar CRM downstream.

No native intent data. Clay has no built-in website visitor identification or first-party behavioral tracking. For page-visit signals and anonymous visitor enrichment, you need a separate tool like RB2B or 6sense, which then feeds into Clay.

Knowing these limits up front helps you design a stack that uses Clay for what it is good at and fills the gaps with the right complementary tools.

How Miniloop Handles the Clay Execution Busywork

Clay handles enrichment, scoring, and routing. But running Clay involves more, the busywork: building tables from scratch for each new campaign, writing formula logic for scoring models, configuring waterfall sequences across a dozen providers, recalibrating thresholds when conversion data changes, and debugging enrichment when a provider's data goes stale or a webhook stops firing.

That work has to get done. But it should not be the founder's job or the GTM engineer's full-time occupation.

Miniloop handles that busywork. We build and run Clay-based GTM workflows for your team:

• Inbound enrichment pipelines: form submission to enriched CRM record, automatically, with the fields your reps need before the first call
• Outbound list building: targeted ICP lists built directly in Clay against the criteria you define, ready for sequencing
• Scoring model setup: formula column scoring configured against your ICP attributes, with threshold bands tied to your actual routing destinations
• Lead routing logic: score-based routing to Slack, CRM queues, or sequence enrollment, with round-robin distribution when needed
• Ongoing maintenance: when providers change, data quality drops, or your ICP evolves, we update the workflow so you don't have to

Whether you have a GTM engineer building the stack, are hiring one, or are doing this yourself while also running the product, Miniloop handles the execution work so the workflow keeps running without constant attention.

Try Miniloop or browse templates.

How Often Should You Recalibrate Your Lead Scoring Model?

Lead scoring drifts over time. The attributes that correlated with closed deals six months ago shift as your ICP evolves, as the market changes, and as your product adds or loses features that matter to specific buyer segments. A scoring model that is not reviewed regularly becomes less accurate without anyone noticing.

The cadence that works: a quarterly review with your sales lead. Pull your closed-won deals from the past three months and check their scores against the current model. If the deals your reps loved closing were scoring 50 points while you were routing everything above 60 to sales, your threshold is miscalibrated. Update it.

Watch for these specific signals that the model needs adjustment:

• High-scoring leads (80+) converting at similar rates to mid-scoring leads (50-60): the top tier is not actually better qualified, so the point weights are off
• Sales team consistently rejecting leads above threshold: the routing threshold is too low or the scoring criteria do not match actual ICP
• A specific attribute that used to matter no longer predicts deals: drop its points or remove it

Data freshness is a separate issue. B2B contact data decays at roughly 25-30% per year. People change jobs, get promoted, leave companies, and change email addresses. Running a waterfall re-enrichment pass on your highest-scored accounts quarterly keeps the scoring inputs accurate.

Clay makes recalibration fast. Updating a formula column value recalculates every score in the table immediately. Changing a threshold that triggers routing updates routing behavior on the next run without rebuilding anything.

For more on the broader qualification system this feeds into, how to qualify leads covers the process from ICP definition through hand-off.

Related Reading

• Clay Pricing in 2026: Plans, Credits & Real Costs Explained
• How to Build a Lead Enrichment Workflow in Clay: Step-by-Step Guide for B2B Teams in 2026
• Smartlead Review 2026: What It Does, What It Doesn't, and Who Should Use It
• Clay Email Finder: Features, Pricing, and How to Use It in 2026

Related Resources

• Solutions - GTM use cases Miniloop supports
• Platform - How Miniloop's GTM agent platform works
• AI Agent Platform - Build and deploy autonomous AI agents