In B2B SaaS sales operations, a form submission or imported prospect list rarely tells you whether a lead fits your ideal customer profile or which account executive should own it. Most forms collect a name, a work email, and a company name, because every extra field costs conversions. The result is incomplete records, misallocated rep time, and slow first responses.
Clay closes that gap by putting enrichment providers, web scraping, custom AI research, scoring, and workflow automation in one workspace. What you get out of it depends almost entirely on how you design the architecture.
Enrichment exists to serve qualification and routing. It is not a contest to see how many columns a table can hold. Dozens of firmographic fields that no rep or rule ever uses inflate your bill and bury the few signals that matter.
A well-built Clay workflow runs one clean loop. It enriches only the account and contact fields it needs, evaluates fit and live intent, applies routing rules, and writes structured data back to downstream systems. Everything below follows that loop.
Define Your ICP Before Building the Clay Workflow
Good routing starts with business definitions, not platform features. Before you create a single table or connect a provider, growth and revenue operations need to agree on what a high-value account looks like. That agreement is the cheapest credit-saving measure you will ever make, because it stops you from paying to enrich records that were never going to buy.
Target account traits usually fall into a few groups. Company size covers headcount and, where relevant, revenue bands. Market covers industry vertical, operating region, and business model, such as usage-based pricing versus enterprise contracts. Context covers the installed technology stack, growth stage (a recent funding round is the classic marker), and whether the departments you sell into exist at all. Persona covers the job titles and seniority levels that actually sign or influence deals.
These criteria become the backbone of both enrichment and scoring inside Clay.
One rule separates disciplined operators from everyone else. Never enrich a field simply because a provider offers it. Enrich it because it changes a qualification decision, a score, a message, or an owner assignment. Anything beyond that adds execution overhead and no business value.
Enrich Accounts and Contacts With the Data Sales Actually Needs
B2B data needs to be split into two buckets. Account-level data describes the company, and contact-level data describes the person. Keeping them in separate table stages avoids duplicate lookups, especially when several contacts at one company share the same account data.
Account enrichment verifies scale, technical environment, and trajectory. The useful fields are employee count, primary industry classification, estimated annual revenue, headquarters location, installed software stack, and hiring growth signals.
Contact enrichment identifies the buyers inside accounts that already passed your fit checks. The fields that matter are official job title, seniority tier, department, buying role, verified work email, and LinkedIn profile URL.
Clay handles gaps through waterfall enrichment. When the first provider returns nothing, the workflow passes the query to a second or third source until a reliable value comes back.
Use Waterfall Enrichment for Important Missing Fields
A waterfall lets you chain specialist data vendors in a controlled order. Instead of trusting one provider for every field, you rank vendors by cost, accuracy, or coverage and let them compete for each lookup.
The sequence runs top to bottom and stops the moment a provider returns valid data, so you only pay for deeper tiers when the cheaper ones fail. A typical firmographic example starts with an inexpensive database for employee counts. If that comes back empty, Clay sends the domain to a second provider or triggers a targeted web scraping step.
Work email is the field where waterfalls earn their keep. A cost-conscious setup starts with lower-priced sources such as Hunter.io or Prospeo and escalates to a pricier provider like People Data Labs only when the first tier misses. Provider pricing inside Clay has shifted since the March 2026 overhaul, so check the live credit cost of each step in your own workspace rather than relying on older rate cards.
Resist the urge to build a deep waterfall for every column. Long chains burn credits fast. Reserve them for the handful of variables that directly move a score or an owner assignment.
Score Leads on Fit and Intent Before Routing Them
Once the fields are populated, Clay can turn raw data into qualification scores. Scoring is what lets a sales team spend its first hour on the best opportunities instead of the newest ones.
Fit measures how closely a record matches your ICP using relatively static data. You assign weight to employee count, target verticals, supported regions, technology compatibility, and decision-maker titles.
Intent captures signals that an account is actively looking for a solution right now. The strongest ones are open job postings for relevant operational roles, a fresh funding round, a technology being installed or removed, website activity, and new product launches.
Keep Fit and Intent as Separate Signals
The most common scoring mistake I see in RevOps reviews is collapsing fit and intent into one blended number. A single score of 72 tells a rep nothing about why it is 72, and the context that should drive the next action disappears.
Consider the two extremes. A company that matches your profile perfectly but shows no buying behavior belongs in long-term nurture, not on a rep’s call list. A small company with loud intent signals may fall below your core ICP threshold, and the right path for it is often self-serve signup rather than dedicated rep time.
When fit and intent stay as independent properties, your routing rules get real context to work with. High-fit, high-intent accounts surface for immediate outreach, and low-intent records flow into educational, low-touch streams.
Build Routing Rules Around Sales Ownership and Priority
Routing rules convert scores into handoffs. In Clay, conditional logic columns do this work by assigning each record to a queue, a segment pool, or a specific CRM owner.
Each qualification tier should trigger a different treatment. High-fit, high-intent records go straight to a dedicated account executive for fast outreach. High-fit records without intent go to sales development reps for cold sequencing, or into a targeted marketing nurture track. Lower-fit leads move to self-serve onboarding, while existing customers route automatically to their assigned Customer Success Manager. Additionally, territory boundaries, enterprise headcount thresholds, and SMB pod capacity act as overlays on every branch above.
The rules have to mirror how your sales organization actually works. Territory maps, headcount cutoffs, target segments, existing CRM account ownership, and live pod capacity all need to appear in the logic. A clever multi-branch design that does not match real team coverage creates ownership disputes, slow follow-up, and orphaned records in the CRM.
Send Clean, Qualified Records Into the CRM
After enrichment, scoring, and owner assignment, the last step is writing data into your CRM. This is where careless workflows do lasting damage. Duplicates and unstructured fields in Salesforce or HubSpot erode rep trust faster than any other data problem.
Protect hygiene with sync rules that run before a record leaves Clay. Check for an existing account or contact using domain and email matches, and update the existing record instead of creating a new one. Map Clay output columns to dedicated custom CRM properties. Preserve the original account owner. Pass fit and intent as separate ratings. Write a routing log so you can audit why a lead went where it did. Then alert the assigned rep by Slack or email in real time.
One plan detail matters here. According to Amplemarket’s 2026 breakdown, the Launch plan does not include native CRM sync, and SyncGTM’s comparison lists CRM integrations, HTTP requests, and webhooks as Growth-tier features. If your design depends on writing back to Salesforce or HubSpot, plan for Growth or a middleware layer from day one.
Think of Clay as the staging, enrichment, and filtering layer that improves your CRM. It should not become a second, unmanaged database that reps have to cross-check.
Keep the Workflow Efficient as Lead Volume Grows
Scale exposes weak table design quickly. Clay’s pricing rewards efficient workflows and punishes sloppy ones, so cost control is a design task, not an accounting task afterward.
Clay restructured its pricing on March 11, 2026, according to Amplemarket. The old Starter (149),Explorer(349), and Pro ($800) plans gave way to Free, Launch, and Growth. The bigger change is the meter. Usage is now split into Data Credits for third-party data lookups and Actions for platform work such as running workflow steps and AI calls, and both deplete independently, as Fast.io’s pricing guide explains.
Here is where the plans stand on Clay’s pricing page, as reported by Landbase and Fast.io:
The Free plan costs $0 per month and includes 100 Data Credits and 500 Actions. It is enough to prototype a workflow, not to run one.
The Launch plan costs $185 per month, or $167 per month on annual billing, with 2,500 Data Credits and 15,000 Actions.
The Growth plan costs $495 per month, or $446 per month on annual billing, with 6,000 Data Credits and 40,000 Actions, and it is the tier that carries CRM sync.
Enterprise is custom quoted. Docket’s research reports packages in the range of 200,000 to 500,000 or more Data Credits per month. Treat that as indicative and confirm with Clay.
Unused Data Credits roll over on Launch and Growth, capped at two times your monthly allocation, according to Landbase. Also note the jump between tiers. Valley’s August 2026 analysis calls the move from Launch to Growth a $310 per month step, which is worth knowing before you hit a volume cliff mid-quarter. Pricing moves, so verify everything at clay.com/pricing before any budget conversation.
The practical way to control spend is to filter before you pay. Strip out personal webmail addresses and non-target geographies at the very top of the table. Order provider waterfalls from cheapest to most expensive. Limit AI web research to accounts that already cleared your firmographic gates. Cache earlier lookups in your CRM so you never re-enrich a known domain, and set workspace spending limits so a runaway table cannot surprise you at invoice time.
The best workflow is not the one that collects the most data per row. It is the one that returns decision-grade information, fast enough to route a lead while it is still warm, at a cost you can predict.
Check the Quality of Your Enrichment and Routing
A green execution status only tells you the table ran. It says nothing about whether the data was right or the lead landed with the correct person. Audit the outcomes, not the jobs.
Track fill rates on every critical column, and spot-check accuracy for job titles and company size against a sample you verify by hand. Watch email bounce rate closely and keep it under 2%, the threshold most deliverability teams treat as the line before sender reputation starts to suffer. On the routing side, measure duplicate creation counts, assignment precision, the time between form submission and owner assignment, sales acceptance rate, first rep response time, and conversion rate by fit tier.
That last metric is the one leadership cares about, and it is also the best test of your scoring model. If your top fit tier does not convert meaningfully better than the middle tier, the weights need rework.
Revisit your routing formulas every time sales leadership redraws territories, changes ICP firmographics, launches a new product tier, or shifts headcount between teams. Stale routing logic fails quietly, and you usually find out from an angry account executive.
Clay Lead Enrichment and Routing Best Practices
Teams that run Clay well tend to follow the same short list of habits.
Start with the ICP. Lock down your ideal customer parameters before building tables or connecting vendors, and enrich only the fields that change a score, a message, or an owner.
Use waterfalls with discipline. Apply them to critical missing fields like work email, ordered by cost and accuracy. Keep account firmographics and contact demographics in separate table stages so you never pay for the same lookup twice.
Separate fit from intent. Track them as two properties, and finish every verification and scoring step before a record reaches the routing rules.
Mirror real ownership. Build formulas around actual territories, headcount tiers, and account owner structures, and always check the CRM for an existing match before creating anything new.
Gate the expensive steps. Put AI research actions and premium Data Credits behind a first-pass firmographic filter, then keep auditing provider match rates, email validation results, and routing accuracy so quality does not drift.
A B2B SaaS Clay Workflow From Lead to Sales Rep
Here is how an end-to-end workflow runs, in ten steps, from raw capture to rep outreach.
- Capture and clean. The lead lands in a Clay table, and the workflow standardizes company names and strips web domains down to a clean root.
- Match against the CRM. Clay checks Salesforce or HubSpot for an existing account or contact, using domain and email.
- Enrich the account. Provider waterfalls fill in headcount, industry, revenue band, location, and tech stack.
- Enrich the contact. The same logic fills title, seniority, department, and LinkedIn URL.
- Verify deliverability. Work emails and phone numbers are validated before anything gets sequenced.
- Score fit. A static ICP score is calculated from firmographic and persona data.
- Evaluate intent. Live signals such as hiring, funding, and tech changes are assessed as a separate property.
- Set priority. The two ratings, read together, determine how urgently the record needs a human.
- Apply routing rules. Territory, segment, and ownership logic assigns the record to an account executive, an SDR, a CSM, a self-serve path, or a nurture stream.
- Write back and notify. Clay updates or creates the master CRM record, stores the routing log, and alerts the assigned rep or enrolls the contact in marketing nurture.
The specific thresholds inside each step will differ by company. Your target account metrics, team structure, territory design, and inbound volume decide the exact parameters, and they should be reviewed on a regular schedule rather than set once and forgotten.