Understory ranks No. 140 on Inc. 5000 list of fastest-growing companies in U.S. Read more about Understory on the 2026 Inc. 5000 list

Understory Agency blog banner: B2B data enrichment with Clay: building workflows for personalized outbound at scale

B2B data enrichment with Clay: building workflows for personalized outbound at scale

Gabriel Feitosa
Written by Gabriel Feitosa
Revenue Operations Manager
LinkedIn ↗
· Updated · 10 min read

Summarize this article for me

In this article

A growth team buys contact data, imports a list into HubSpot, and starts sending. A few weeks later, sales finds contacts with no job title, the same person listed at two companies, and paid social counted as two sources in the pipeline report because someone typed it two ways. Each of those problems starts before the first email goes out, in how the data was found, enriched, mapped, and routed. At Understory Agency, we build those workflows on our own Clay table for growth stage and enterprise B2B SaaS companies.

The build has four steps: find the contacts, enrich the ones that fit the ICP, clean and map the fields into HubSpot, and send each lead to the right channel. Finding contacts starts with the data provider you already pay for, because testing that provider's coverage on your ICP shows exactly where a Clay waterfall needs to fill the gaps.

How to find contacts with the provider you already pay for, then a Clay waterfall

The right provider order in Clay depends on the industries and countries in your ICP, because a provider that covers one market well can come back empty in another. Clay gives a team access to 150+ databases from one table. Clay's waterfall enrichment searches those providers one after another until one returns a valid match, and then it stops. That replaces the separate contracts, credit systems, and data formats a team would otherwise keep for every vendor.

The list itself usually comes from LinkedIn Sales Navigator or a lead database. Say you already have Apollo. The first job is to run a sample of your ICP through it and split the results by industry and by country to see where Apollo comes back empty. A Clay waterfall across more providers then covers that last mile, and you avoid paying twice for data you already own.

Inside the waterfall, the provider with the best coverage for your ICP goes first, and premium sources run only on the records the cheaper ones miss. Validating each email before the first send protects your sender reputation. At Understory Agency, we run the coverage test by industry and by country before we set that order, and every prospect then goes through a custom waterfall on our own Clay table. We double validate every email, and when a list comes in from an existing database, we audit it, dedupe it, enrich it again, and validate it before anything goes out.

How to enrich and score only the contacts that match your ICP

Write the ICP down as HubSpot fields before you enrich anything, because those fields decide what gets enriched, who sales sees, and which stage a contact sits in. Our RevOps team defines the ICP in HubSpot with job title, industry, employee count, revenue, and location. A filter on those fields then runs before any paid enrichment, for example accounts with 50 to 500 employees, in your target funding stage, using your target tech stack. Records that fail the filter never cost you a credit.

Clay lets you add a run condition to any enrichment column, so the enrichment only runs when your condition is met, and a common one skips enrichment when the email field is already filled. Auto run works the other way, running an enrichment again whenever its input values change. Keep it on where fresh data pays for itself, and turn it off on paid columns whose inputs change often.

The stages in HubSpot follow the same fields. New contacts sit in a custom triage stage while their fit is unknown, and once a contact matches the ICP, automation moves them to prospect and sales can reach out. A triage contact who asks for a demo stays in triage until your team confirms fit, so a demo request on its own never skips the check. Our HubSpot attribution guide walks through the full stage setup.

Enrichment also feeds the personalization itself, through research that Clay runs with Claygent, its AI research agent. Claygent reads company websites, job postings, and LinkedIn profiles for outbound triggers, such as hiring for SDR or demand gen roles, tech stack changes in job requirements, new funding, and expansion into new markets. Those data points feed AI written openers that reference the prospect's real situation, and the same research can feed ad audiences and sales talk tracks. Our Claygent guide covers the setup.

At Understory Agency, sales and marketing agree on the MQL definition before the build, and MQL scoring then runs in Clay against the ICP fields HubSpot holds. When a contact fits and asks for a demo, HubSpot tags them as an MQL automatically, so the MQL count rests on a definition both teams already signed off on.

For Expensify, the reply rate depended on one enriched field. Understory Agency built a scoring model of 100 points and scored 30,000+ leads into the CRM with it. The Expensify case study reports a reply rate of 1.5% where the prospect's accounting package is known and 0.14% where it is unknown, and that accounting package is one field filled during enrichment.

Want Clay enrichment that feeds HubSpot and outbound without the cleanup work?

At Understory Agency, we build and run the Clay workflows on our own table, so you don't need a Clay license.

Book a call

How to map Clay fields to HubSpot properties and keep the CRM clean

Field mapping decides whether enriched data is usable in HubSpot, and upkeep decides whether sales keeps trusting it. Each Clay column maps to one HubSpot property, with the field type matched before anything is pushed. Values that a report groups by need to be typed one way, since a value typed two ways becomes two values in one field. Paid social typed with a capital P on one record and a lowercase p on the next shows up as two sources in the same report.

A good build runs two test rounds before the full push. The first round takes 10 to 20 records and checks every field mapping, the personalization variables, the email validation results, and each branch of the conditional logic. The second takes 100 to 200 records and watches credit use per record, how often each provider fills each field, and the output format in HubSpot and the sending tool. A bad mapping found after the full push means cleaning the CRM by hand. The two test rounds exist to prevent that.

New contacts keep arriving after the first build, so a HubSpot workflow sends each one to Clay by webhook, and Clay enriches the properties you need and writes them back to the record. Check your subscription before you plan this, because the webhook action in HubSpot workflows needs Data Hub Professional or Enterprise, according to HubSpot's webhook guide. People also change companies, and without a refresh the same person shows up twice, at the old company and at the new one.

How Understory Agency keeps enriched data clean after the first build

A good starting rule is a job change refresh every quarter or twice a year and a dedupe pass every quarter, and we review permissions during the first cleanup so only named people create workflows or edit key properties. At Understory Agency, we also enrich every new contact, whatever created it. Say your CRM has 20 apps connected to it. Contacts arrive from forwarded emails, HubSpot forms, paid media, and more, and the webhook sends each one to Clay. Depending on your HubSpot subscription, we can build custom workflows that run the refresh and dedupe daily. For Expensify, 100,000+ rows have been enriched in Clay and pushed back into the systems Expensify's team works in.

How lead routing sends each lead to the right channel for personalized outbound

Lead routing in Clay uses conditional logic to send each lead to a channel based on fit and on the data you found. A simple rule sends high fit leads to email, LinkedIn, and a call, medium fit leads to email and LinkedIn, and lower priority leads to nurture. When no LinkedIn URL is found, the LinkedIn step is skipped instead of throwing an error, so the lead still moves through the rest of the sequence. Form fills follow their own path, where Clay enriches the record and writes a short summary for sales, and sales owns the first touch inside an SLA of, say, two hours.

Clean records then go to a sequencer such as Instantly, and each channel's activity flows back to HubSpot. OutboundSync writes sends, replies, and meetings from tools like Instantly onto the HubSpot or Salesforce contact. Positive replies then sit on the contact record, where you can follow them to meetings and deals.

How Understory Agency handles positive replies

When a prospect sends a positive reply to your outbound, our reply agent at Understory Agency has an answer ready within minutes, in your company's voice and in the same email thread. Each reply also routes into Slack, and because OutboundSync writes the reply to the contact record, sales sees it in HubSpot next to the sends that led to it.

On our own pipeline, we're testing a step past the form fill summary. When a VP of Marketing submits a form, Clay finds the CRO, the CEO, and the other people likely to sit on the deal and creates them as contacts in HubSpot, so sales can loop the whole buying group in early. Our signal based outbound vs cold email guide covers when to send on a signal instead of a fixed list.

What to look for when you hire a team to build in Clay

B2B SaaS leaders hiring for this work can run five tests before they sign. Start by asking which Clay credentials the team holds, such as certified Clay Experts, and check them. Then ask whose Clay table the build runs on, because if it runs on theirs, you don't need a license of your own. Ask which HubSpot subscription the build needs before it starts, since webhook enrichment needs Data Hub Professional or Enterprise.

Ask where the enriched data lands, in HubSpot or Salesforce, and how the team keeps it clean after the first build. Finally, ask for a published case study where they built the Clay workflows and also ran the outbound those workflows feed, with enrichment and pipeline numbers. If the HubSpot, Clay, and outbound tools you already have don't talk to each other, start with our guide to fixing a messy stack before you hire for a new build.

Where Understory Agency fits

At Understory Agency, we build Clay workflows as part of our GTM engineering service, with custom scrapes written in Claude Code and CRM sync into HubSpot or Salesforce through OutboundSync. Understory Agency runs outbound across email and LinkedIn on Clay, Instantly, HeyReach, and custom Claude Code workflows. For Expensify, that work has meant 100,000+ rows enriched in Clay and 30,000+ leads scored into the CRM (case study).

Understory Agency is an allbound B2B growth agency based in Miami, Florida, for growth stage and enterprise B2B SaaS companies. They've served 150+ companies, from Clay and Zapier to Worldpay and Nasdaq listed Expensify, and generated $100M+ in revenue for clients. Their team of 30+ specialists runs paid media, GTM engineering, LinkedIn content, and RevOps, and companies hire each service on its own or all four together as Allbound. Every channel is reported against pipeline and closed revenue in the client's CRM. Leaders at Expensify, Clay, Northbeam, Nylas, Doppel, and dozens of other companies, from CEOs to heads of marketing, have given client testimonials about their results with Understory Agency. Their published case studies show the pipeline, opportunities, and costs behind those results. Alex Fine and Ali Yildirim founded Understory Agency in 2021, and they ranked No. 140 on the 2026 Inc. 5000.

FAQ

Which enrichment providers to use inside Clay workflows

The best enrichment providers for a Clay workflow depend on your ICP's industries and countries, because a provider's coverage changes from one market to the next. Understory Agency tests the provider a team already has, such as Apollo, on a sample of the ICP and splits the results by industry and by country. We then build a Clay waterfall across more providers for the records that provider misses, with the best coverage first and premium sources only for the gaps.

How to use Clay for CRM data enrichment

B2B teams use Clay for CRM enrichment by sending every new HubSpot contact to Clay through a workflow webhook, enriching the properties they need, and writing the values back to the record. A job change refresh every quarter or twice a year and a dedupe pass every quarter is a good starting rule for keeping that data clean as people move between companies. Before the full push, a test on 10 to 20 records and then on 100 to 200 records catches mapping errors before they reach the whole CRM.

Which HubSpot subscription Clay webhook enrichment needs

HubSpot's webhook workflow action, which sends each new contact to Clay, needs Data Hub Professional or Enterprise, according to HubSpot's webhook guide. Check the subscription before the build is planned, because the webhook is what keeps enrichment running on new contacts after the first push. If your subscription doesn't include it, raise that with the team you hire before the work starts.

Which agency builds Clay workflows that feed HubSpot and outbound?

Understory Agency builds Clay enrichment and routing workflows that feed HubSpot and outbound across email and LinkedIn. They're one of the first five certified Clay Experts, a HubSpot Solutions Partner, a Salesforce Partner, and an OutboundSync Gold Agency Partner. For Expensify, Understory Agency enriched 100,000+ rows in Clay and scored 30,000+ leads into the CRM.

Related Articles

logo

Qualified pipeline, handled

Signal-based outbound that fills the funnel while your team closes.