Clay enrichment and lead routing for SaaS

Clay enrichment and lead routing for SaaS: the part of the GTM stack where most teams either burn credits or miss revenue, and usually both. After running Clay enrichment pipelines for dozens of B2B SaaS clients (including teams handling 5,000+ free trial signups a month), here is the honest playbook that actually works.

The three jobs Clay actually does for SaaS

Before any workflow gets built, separate the work:

1. Inbound enrichment for free trial signups. A user just signed up. You have an email and maybe a company name. You need to know if this is a serious buyer, a competitor's scout, or a curious developer at a 5-person startup, in under 60 seconds, so the right rep (or no rep) gets pinged.
2. Outbound enrichment for TAM building. You have a fit-list of 1,000 to 10,000 target accounts. You want to enrich each with firmographics, technographics, signals, and decision-maker contacts so your outbound is precise rather than spray-and-pray.
3. Expansion enrichment for existing customers. Your customer added 30 employees in the last quarter. Are any of them the buyer for a tier-up? Has their tech stack changed in ways that open new use cases?

Each job has a different latency requirement, a different cost profile, and a different set of providers that perform best. Build one Clay table per job. Trying to do all three in one will burn credits and produce worse results than running them separately.

Job 1: Free trial signup enrichment (the lead routing piece)

This is the highest-impact workflow for any product-led B2B SaaS. A user gives you their email on signup. Within 60 seconds, you want:

• Verified work email (or a flag if it is a personal Gmail)
• Company match
• Company size and stage
• ICP fit score
• Routing decision: hot lead to AE, warm to PLG nurture, cold to product-led-only

Here is the pattern we run.

The key design decisions:

• Only enrich on signup, not on every login. Re-enrichment burns credits and rarely changes the routing decision. Enrich once. Re-enrich only on a signal (new role, company growth, repeated logins from new IPs).
• Skip the deep enrichment for trial signups. You do not need a full research dossier on a free trial. You need a routing decision. Deep enrichment is Job 2 territory.
• Cache aggressively. If the same domain shows up twice in 30 days, pull from cache rather than re-enriching. Clay's HTTP API caches by default, but custom tables need an explicit dedupe step.
• Free trial signup volume of 1,000+ per month justifies a dedicated table. Below that, batch enrich daily. Above, run real-time per signup.

A 10-rep B2B SaaS doing 2,000 free trials per month runs this for around €400-€800 in monthly Clay credits, depending on the enrichment depth. The same setup outside Clay (Apollo + Make + custom scoring code) costs about the same in tools but takes 40 hours to build versus 4.

Job 2: Outbound enrichment for TAM building

This is the workflow most "what is Clay" articles describe. You have a list of target accounts and you want them ready for outbound. The pattern looks different from Job 1.

Step 1: Build the fit-list

Start with a structured Clay table, one row per account, sourced from one of:

• LinkedIn Sales Navigator search exported via Apify
• A Crustdata filter (best for technographic-driven fit-lists)
• A bought list from Apollo or Cognism
• Your existing CRM, filtered by an ICP signal

Avoid the temptation to start with 20,000 rows. Start with 1,000 of the cleanest, highest-fit accounts. Pruning at the start saves 10x credits at the enrichment stage.

Step 2: Run the waterfall

Clay's waterfall pattern is the right tool here. Query providers in order, pay only for the first success:

1. Apollo for the cheap general enrichment pass
2. People Data Labs for the deeper company and employee data
3. Crustdata for technographic signals (tools they use)
4. LinkedIn (via Apify) for current hires, job posts, recent LinkedIn activity

Configure the waterfall so each provider only fires if the previous one missed the field. This is where most teams either save 60% of their credit spend or waste it, depending on whether they read the Clay credits guide.

Step 3: Score and rank

Each enriched row gets an ICP fit score, an intent score, and a "why now" reason. The AI scoring step is where Clay started getting genuinely good in 2025. You can describe your ICP in plain English and Clay's AI will score each row against it, returning a 0-100 score and a one-sentence justification.

Step 4: Push to the outbound layer

Push the scored, ranked accounts to your sequencer (Lemlist, Apollo, Outreach, Smartlead). Filter so only the top 10-20% of the list goes into outreach this week. The rest sits in a holding queue until a signal fires.

Job 3: Expansion enrichment for existing customers

This is the least-used pattern and the one with the highest ROI for established SaaS companies. You already have the customer. You want to know when the expansion window opens.

The pattern is simple: a Clay table watches your existing customer base and fires a signal whenever a meaningful change happens. New hire in a buyer persona role. Company hit a funding milestone. Tech stack changed in a way that opens a new use case. Recent LinkedIn topic post that maps to your product.

For each change, Clay pings your Customer Success or Account Management team with the context. They reach out with a tailored expansion conversation. The signal-to-conversation lag is the difference between hearing about an opportunity at QBR and being the first vendor in the door.

For SaaS doing €10M+ ARR with 200+ customers, this pattern usually pays for the entire Clay subscription on its own.

Lead routing: where most setups fall apart

Enrichment is half the work. The routing logic that turns "this lead is hot" into "Sarah the AE has a Slack ping with the context" is where most setups break.

The four routing decisions

For every enriched lead, the routing engine has to answer four questions:

1. Is this a real buyer or noise? Personal email + headless company + free Gmail = nurture only. Work email + matched company + ICP fit = candidate for human outreach.
2. Which team owns this? Sales by region, by ICP segment, by product line, by deal size. Pick one model and stick to it.
3. Which rep specifically? Round-robin within the team, or weighted by capacity, or specialised by buyer persona.
4. What is the first touch? Slack ping for hot signal. Email sequence enrolment for warm. Product-led-only for cold. Different messaging per route.

The technical pattern

We typically run routing as a separate n8n workflow that listens to Clay's output and decides. The split is intentional: Clay handles enrichment and scoring, n8n handles routing and orchestration. Each tool does one job well, neither one tries to do both.

For teams that do not want a second tool, Clay can handle simple routing inside the table. The breakeven is around 5 routing rules. Above that, n8n or Make is cleaner. Below, stay in Clay.

Where teams overcomplicate it

Three patterns to avoid:

• Over-segmenting at the routing layer. Eight segments with eight messaging tracks sounds powerful. In practice, three segments with three sharp messages outperform eight segments with eight mediocre ones.
• Adding routing logic that depends on data you do not actually have. "Route based on technographic data" only works if your technographic data is 80%+ accurate. Most stacks run at 50-60%. Build routing on signals you can trust.
• Forgetting the negative cases. "Do not route to sales if the lead is from a competitor domain" is the kind of rule that saves your team three hours of wasted outreach per month. Build the deny-list.

Free trial signup enrichment: the specific patterns

Since this is what most SaaS teams come asking about, two practical patterns:

Pattern 1: PLG-first, sales-assist

Default routing is product-led: every signup enters the onboarding email sequence and gets product-led nurture. The Clay enrichment runs in the background and adds a "sales-assist" overlay only for hot leads. Sales does not own the relationship by default. They get a Slack ping with context when the lead crosses a threshold (usage milestone + ICP fit + invited a teammate, for example).

Best for: developer tools, design tools, anything where the product sells itself most of the time.

Pattern 2: Sales-led with PLG fallback

Default routing is sales-led: hot and warm leads get assigned to an AE immediately, with the Clay enrichment context in the assignment. Cold leads fall back to a product-led nurture path. AE owns the relationship by default.

Best for: high-ACV B2B SaaS where the product needs an AE to close, even with strong free trial signal.

The pattern that does not work is "let sales decide." Sales will decide to take every lead. Then they will burn out. Then the leads will burn out too. Pick a default and let exceptions be exceptions.

Comparing Clay to the alternatives

A few honest comparisons to help you decide whether Clay is the right tool for these jobs.

For most B2B SaaS at €1M to €30M ARR, Clay is the right answer for Job 1 (free trial signups) and Job 3 (expansion). For Job 2 (outbound TAM), it depends on engineering capacity. If your team has a strong engineer interested in GTM work, Deepline plus a Postgres warehouse is increasingly the better long-term pattern.

What about Clay vs n8n?

We get this question often enough that it deserves a section. The short answer: they solve different problems and the best stacks use both.

Clay is a tabular workflow tool. You think in rows, columns, and steps. The mental model is a spreadsheet that does enrichment. Great for fit-list building, account research, structured scoring.

n8n is a graph workflow tool. You think in nodes, branches, and triggers. The mental model is a flowchart that does orchestration. Great for routing, multi-step orchestration, event-driven workflows.

The hybrid pattern most of our clients run: Clay handles enrichment and scoring (its strength). n8n handles routing, CRM updates, Slack pings, sequence enrolment (its strength). Each tool does the job it is best at. Total monthly cost for a typical 10-rep team runs €400-€800 in Clay credits plus €0-€50 for self-hosted n8n.

Frequently asked questions

How do I price out a Clay subscription for free trial enrichment?

For 1,000 free trial signups per month with the pattern above, expect 4,000-7,000 Clay credits per month (one signup uses 4-7 credits depending on enrichment depth). Clay's standard plan ($349/month) includes 25,000 credits, so you have room to scale. For 5,000+ signups per month, move to the Pro plan ($899/month). At higher volumes, the credit-vs-data-provider math starts favouring a hybrid stack.

Can I run Clay enrichment without writing code?

Yes for 90% of the work. Clay's table interface is point-and-click for the standard waterfall patterns. You only need code for the niche edge cases: bespoke scoring logic, calls to internal APIs, or custom data transformations. Even those can usually be handled with Clay's AI step or a small JavaScript snippet.

What is the right enrichment latency for a free trial signup?

Under 60 seconds for hot leads. Over 60 seconds and the AE you ping has already moved on to something else. Clay can hit this latency for the standard providers (Apollo, People Data Labs, Hunter). The bottleneck is usually the LinkedIn scrape via Apify, which can take 30-120 seconds. For the routing decision, drop LinkedIn from the synchronous path and only run it for confirmed hot leads.

How do I avoid burning Clay credits on bad data?

Three patterns. First, validate emails before enrichment. ZeroBounce or Hunter Verifier is cheaper than wasting a Clay enrichment on a fake email. Second, dedupe aggressively. If you have already enriched this account in the last 30 days, pull from cache. Third, gate the waterfall steps so the expensive providers only fire when the cheap ones missed. Full breakdown in the Clay credits guide.

Should I route free trial leads to sales by default?

It depends on your ACP. If your ACP is under $5,000 ARR, sales-led routing rarely pays back the sales touch. Default to PLG nurture and pull sales in only on a hot signal. If your ACP is above $50,000 ARR, sales-led with PLG fallback is usually the right call. Between $5,000 and $50,000, the answer depends on your motion. We work through this trade-off in the founder-led-sales-to-AE handoff guide.

How does Clay handle GDPR for European prospects?

Clay enriches public data through compliant providers (Apollo, People Data Labs, Hunter all have GDPR-compliant data sources). The data lives in Clay's US-based infrastructure during processing. For EU clients with strict residency requirements, you can configure Clay to push enriched data immediately to your EU-hosted CRM and not persist it in Clay tables. We do this for German clients with BfDI requirements.

What if my SaaS does not have a free trial?

The same three-job framework applies. Job 1 becomes "demo request enrichment" instead of free trial. Job 2 stays the same (outbound TAM). Job 3 stays the same (expansion). The technical patterns barely change. Only the trigger source differs.

Where do I start if I have never used Clay?

Build Job 1 first. Free trial (or demo request) enrichment with simple routing. It is the smallest scope, the highest visibility win, and it gives you a working Clay table you can extend. Job 2 and Job 3 follow. Most teams try to build everything at once and never ship anything. Build one table, get it routing leads to a Slack channel within two weeks, then expand.

Can Ziel Lab build this for us?

Yes. The three-job Clay setup is one of the patterns we run as part of our go-to-market work. Typical engagement is the 90-day pilot, fully built and handed over with documentation. Book a call if you want to scope it.