The Clay playbook for mid-market revenue teams

Clay has the highest hype-to-value ratio of any tool in the modern revenue stack. Teams hear the pitch, sign the contract, build one table, run one enrichment, and call it a Clay rollout. Six months in, the only thing it's replaced is half their Apollo seats.

Clay is not an enrichment tool. It's a programmable data layer for revenue ops. The value isn't in the table you build on day one, it's in the four or five always-on workflows you wire into it over the next quarter. The teams getting outsized return are the ones treating Clay as infrastructure, not as a list-building app.

This piece covers the plays we build for mid-market clients (typically $5M to $200M, US-based, running a real outbound or ABM motion), how they integrate with the rest of the stack, and what ROI usually looks like once the pipelines are live.

The Enrichment Stack Problem (Clay Solves)

Walk into the average mid-market revenue team and audit their enrichment spend. You'll usually find some version of this:

• ZoomInfo or Apollo at $20k to $60k a year for firmographics and emails.
• LeadIQ or ContactOut for mobiles, billed per seat.
• LinkedIn Sales Navigator seats for every SDR and AE.
• Hunter for email verification, BuiltWith or HG Insights for technographics, Crunchbase for funding data.
• A scraping vendor or two for LinkedIn signals and intent data.

Each tool has its own contract, its own data model, and its own seat-count negotiation. Records get exported, cleaned in a Google Sheet, re-uploaded, and slowly drift out of date. The CRM has six versions of the same contact. Reporting is built on data that was true four months ago.

Clay's waterfall enrichment is the simplest answer: hit Apollo first for the email, fall back to Hunter if Apollo misses, fall back to BetterContact if both miss, verify with NeverBounce, write the result back to the CRM. One contract, one table, one source of truth. The cost saving alone usually pays for the build in the first quarter; the cleaner data is the bigger win.

Automation Plays We Build with Clay

Four plays cover most of the value we ship for mid-market teams. Each one is a specific workflow with a clear trigger, a defined data path, and a measurable outcome.

1. Waterfall Enrichment + CRM Write-Back

Trigger: new contact appears in the CRM (form fill, manual creation, list import). Workflow: contact is pushed to a Clay table, runs through a waterfall of Apollo, Hunter, ContactOut, and BetterContact for email and mobile, hits BuiltWith for technographics, hits Crunchbase for funding. Result: a fully-enriched record is written back to Salesforce or HubSpot inside three minutes.

Outcome: enrichment cost per contact drops by 40-60% versus running ZoomInfo + Apollo + LeadIQ in parallel, and your CRM stops needing manual cleanup.

2. Claygent Agents for Account Research

Trigger: any account on the target-account list. Workflow: a Claygent agent reads the company's LinkedIn page, recent press, their last earnings call (if public), the careers page, the product changelog, and any podcast appearances by the leadership team. It returns a structured brief: top three current priorities, recent strategic moves, hiring signals, and a personalised first line tied to one of them.

Outcome: an SDR who used to spend 15 minutes researching one account now gets a research brief and a first line pre-written for 200 accounts a day. AE-led account prep stops being an afternoon job.

3. Signals-Based Outbound

Trigger: a buying signal fires (new VP of Sales hired, $10M+ funding round closed, competitor tool detected on the website, key champion changes companies). Workflow: the matching account is pulled into Clay, the relevant buying committee is enriched, a Claygent agent writes a context-aware opening that references the signal, the contact is dropped into Smartlead or Salesloft in a sequence tagged to that signal type. Sales leadership gets a Slack ping summarising what fired and to whom.

Outcome: outbound shifts from "contact 1,000 cold names a week" to "contact 200 hot signals a week". Reply rates typically triple. Meetings per SDR per month go up even as send volume drops.

4. List Refresh and Job-Change Pipelines

Trigger: rolling cadence (typically weekly). Workflow: every CRM contact older than 90 days gets re-verified, every champion gets checked for a job change, every dead account gets re-scored. Job changes flow into a "warm new logo" list, verified contacts stay in routing, unverifiable contacts get archived.

Outcome: a steady drip of high-intent warm leads (a former buyer at a new company is one of the highest-converting outbound segments there is) and reporting that runs on data that's actually current.

How Clay Should Integrate With Your Stack

Clay sits in the middle of the revenue stack, not at the edge. The build only works if every adjacent tool is wired in.

• CRM (Salesforce or HubSpot): two-way sync, with Clay as the system of enrichment and the CRM as the system of record. Field mapping is deliberate. Nothing overwrites without a confidence check.
• Sequencer (Smartlead, Salesloft, Outreach, Instantly, Lemlist): Clay pushes sequence-ready records, including custom variables for the personalised first line and any signal context.
• Slack: a dedicated channel for signal firings, hot job-changes, and inbound enrichment summaries. Reps see the alert before they touch the lead.
• Data warehouse (Snowflake, BigQuery): product usage flows in, enriched buying-committee data flows out, so PLG-to-sales handoffs and customer health both have current firmographics.
• Webhooks and HTTP: anything Clay doesn't natively integrate with (Gong, Mutiny, Common Room, an internal tool) hangs off webhooks. We default to native where it exists, webhooks where it doesn't.

What ROI Actually Looks Like

Numbers vary by motion, but the shape is consistent across the mid-market builds we ship. Indicative, not promised:

• Subscriptions retired: typically 3-6 standalone tools (ZoomInfo, LeadIQ, ContactOut, BuiltWith, Crunchbase, one scraper), worth $40k-$120k a year in seat fees.
• Cost per verified enriched contact: usually drops from $0.50-$1.00 (multi-tool, with overlap) to $0.10-$0.25 (Clay waterfall with one credit pool).
• SDR hours saved on research: 5-10 hours per SDR per week, redirected into reply handling and meeting prep.
• Reply rate on signal-triggered cold outbound: 2-4x cold-list baseline, on lower send volume.
• Meetings booked per dollar of enrichment spend: typically 2-3x, driven by tighter targeting and personalisation more than by raw volume.

The line we draw with clients: Clay should pay for itself on subscription savings alone in the first quarter. Everything past that, the lift in reply rate, the SDR time freed up, the cleaner CRM, is upside.

Where Teams Go Wrong

The same handful of mistakes show up across almost every Clay rollout we audit.

Over-Enriching Everything

Credits are not free. Running every column on every contact, every week, burns budget on records that will never get touched. We segment: high-priority accounts get the full waterfall, the long tail gets a cheaper subset, and we only re-enrich on a defined cadence or trigger.

No List Hygiene Layer

Clay enriches what you feed it. If the upstream list is junk (scraped at random, no ICP filter, no deduplication), you get expensively enriched junk. We build the filtering and dedup in before the waterfall, not after.

Claygent Prompts That Never Ship

Claygent's output is only as useful as the prompt and the schema. Most teams write a vague "summarise this company" prompt, get vague summaries, and stop using the agent. The build is in the prompt engineering: tightly scoped questions, structured output, validation rules, fallback logic when the agent can't find the data.

Treating Clay as a One-Time Enrichment Tool

The single biggest pattern: Clay is used to clean up one list, then ignored. The compounding value is in the always-on pipelines: signal triggers, weekly refreshes, inbound routing, ABM hygiene. If nothing runs on a schedule, you've bought a worse Apollo.

Where Moonira Comes In

Clay sells itself. The reason teams still bring us in is the integration work: getting the waterfall right for a specific ICP, building the Claygent agents that actually produce sequence-ready output, wiring the signal triggers, holding the CRM sync stable as the team scales. We design the plays, build the tables, write the prompts, manage the integrations, and hand over documentation your ops lead can run.

If you're paying for Clay but only using one corner of it, or you're staring at the trial and not sure what to build first, this is the build we do most. Get in touch and we'll scope what your version looks like.