---
title: "Clay × LeanScale: how we run Clay"
type: "partner"
partner: "Clay"
tier: "Standard"
practice: "Growth Operations"
category: "Enrichment & Orchestration"
vendor_url: "https://clay.com"
publisher: "LeanScale"
date_modified: "2026-10-06"
canonical_url: "https://www.leanscale.team/knowledge/partners/clay/"
source: "LeanScale Knowledge Hub, https://www.leanscale.team/knowledge"
license: "Free to quote and cite with attribution to LeanScale."
---

# How LeanScale runs Clay

The core system of our Growth Operations practice. We design the waterfalls, size the plan and run the workspace, and a shared channel with Clay has kept builds moving since 2024.

**Tier:** Standard. We build on it. A core system.

**Standard seats held:** Growth Ops, Enrichment & Orchestration (Standard).

**Relationship:** Shared Slack channel, Named partner contact, Co-sell.

- Projects we run on it: 15
- Native integrations in our stack: 8
- Hub documents: 54

## What we build on Clay

15 projects from the LeanScale catalogue run on Clay, each with a typical timeline from our delivery record.

- **Inbound capture** (Growth Ops, Playbook, Inbound campaigns): Forms, conversion paths, hidden tracking fields, enrichment and speed to lead. Typical timeline: 1 week. Cadence: Per page or form request.
- **Outbound** (Growth Ops, Playbook, Outbound and signal campaigns): Target lists, enrichment, sequence construction, enrollment and reply handling. Typical timeline: 1–2 weeks. Cadence: Per campaign.
- **Warm signals and PQLs** (Growth Ops, Playbook, Outbound and signal campaigns): Intent, product and web signals captured, scored, prioritised and acted on. Typical timeline: 1–3 weeks. Cadence: Per signal campaign; evergreen once live.
- **ABM and paid audiences** (Growth Ops, Blueprint, Outbound and signal campaigns): Target-account plays and the audiences, suppression and tracking behind your paid programs. Typical timeline: 2–4 weeks.
- **Campaign system (brief to launch)** (Growth Ops, Blueprint, Campaign spine): Templates and an assistant your marketer drives from a brief: audience, campaign, tracking and review queue built for them. Typical timeline: 4 weeks.
- **Engine setup (Clay, Amplemarket)** (Growth Ops, Blueprint, Campaign spine): The enrichment and sending tools stood up properly before campaigns lean on them. Typical timeline: 4–8 weeks.
- **Expansion and win-back** (Growth Ops, New, Customer and partner campaigns): Campaigns to existing customers and closed-lost accounts, timed on signals. Typical timeline: 1–2 weeks.
- **Automated inbound** (Marketing Ops, Playbook, Capture and routing): Every inbound lead enriched, deduped and account-matched on arrival. Typical timeline: 3–5 weeks.
- **Market map** (RevOps, Playbook, Territory and planning): Your TAM scored and tiered against ICP, then refreshed every quarter. Typical timeline: 2–3 weeks.
- **Agents and AI workflows** (Data and AI layer, Blueprint, AI and agents): Agents and workflows that do a real job for your team, reviewed by a person. Typical timeline: 2–6 weeks.
- **Data hygiene and dedupe** (RevOps, Blueprint, CRM foundations): Clean, deduplicated records with real account hierarchies, before anything reads from them. Typical timeline: 2–5 weeks.
- **Intent and signal setup** (Marketing Ops, Blueprint, Targeting and scoring): Intent and product signals flowing into the CRM, ready for campaigns to use. Typical timeline: 2–3 weeks.
- **Lead and account scoring** (Marketing Ops, Blueprint, Targeting and scoring): One score, agreed by sales and marketing, that decides who gets worked first. Typical timeline: 3–5 weeks.
- **Persona and segment mapping** (Marketing Ops, Blueprint, Targeting and scoring): Personas and segments defined in the database, paired with the market map. Typical timeline: 1–2 weeks.
- **Renewals and expansion** (RevOps, Blueprint, Customer and partner lifecycle): Renewals worked on a clock and expansion found from signals, not memory. Typical timeline: 3–6 weeks.

## The Field Report: Clay, from the operator’s seat

A Standard benefit: how the product performs across our own implementations, read from the Arsenal. No vendor can source this view anywhere else.

- Implementations: 9 (In the LeanScale delivery record)
- Build types: 9 (Distinct kinds of work we have shipped)
- Effort band: 25–150 hours (Typical build, smallest to largest)
- AI-nativeness: #3 (of 19 in Growth Ops · AI-Native)
- Usage rank: #6 (of 142 systems in the Arsenal)
- Reach: A quarter of the customer book (Share of the client book running it)

> Ubiquitous in our Growth Operations delivery, and the system we teach most often. The recurring operator theme is that the power is in the setup: it rewards an owner who maintains the waterfalls and watches credit burn, and punishes teams who expect it to work out of the box.
>
> Operator’s note, LeanScale Growth Ops

## How Clay fits the rest of the stack

Headless readiness and native integrations, read off the vendors’ own pages. Nothing here is asserted from memory.

**Headless readiness:** API, Webhooks, MCP server, Zapier. Source: https://www.clay.com/integrations, checked 2026-09-21.

**Connects natively with 8 partners we run:** [Amplemarket](https://www.leanscale.team/knowledge/partners/amplemarket/), [HubSpot](https://www.leanscale.team/knowledge/partners/hubspot/), [Salesforce](https://www.leanscale.team/knowledge/partners/salesforce/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Gong](https://www.leanscale.team/knowledge/partners/gong/), [Outreach](https://www.leanscale.team/knowledge/partners/outreach/), [Salesloft](https://www.leanscale.team/knowledge/partners/salesloft/), [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/).

## The outcomes Clay helps us deliver

The LeanScale stacks Clay sits in, and the systems it runs alongside.

- **Sales Engagement Platform** (RevOps, Growth Ops): alongside [Salesforce](https://www.leanscale.team/knowledge/partners/salesforce/), [HubSpot](https://www.leanscale.team/knowledge/partners/hubspot/), [Amplemarket](https://www.leanscale.team/knowledge/partners/amplemarket/), [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/), [Outreach](https://www.leanscale.team/knowledge/partners/outreach/), [Gong](https://www.leanscale.team/knowledge/partners/gong/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Salesloft](https://www.leanscale.team/knowledge/partners/salesloft/), [Chorus](https://www.leanscale.team/knowledge/partners/chorus/), [Cognism](https://www.leanscale.team/knowledge/partners/cognism/), [Lusha](https://www.leanscale.team/knowledge/partners/lusha/)
- **Customer Segmentation** (Growth Ops, RevOps): alongside [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Gainsight](https://www.leanscale.team/knowledge/partners/gainsight/), [ChurnZero](https://www.leanscale.team/knowledge/partners/churnzero/), [Planhat](https://www.leanscale.team/knowledge/partners/planhat/), [Vitally](https://www.leanscale.team/knowledge/partners/vitally/), [Cognism](https://www.leanscale.team/knowledge/partners/cognism/), [Totango](https://www.leanscale.team/knowledge/partners/totango/), [Lusha](https://www.leanscale.team/knowledge/partners/lusha/), [Catalyst](https://www.leanscale.team/knowledge/partners/catalyst/)
- **Automated Outbound Process** (Growth Ops): alongside [Amplemarket](https://www.leanscale.team/knowledge/partners/amplemarket/), [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/), [Outreach](https://www.leanscale.team/knowledge/partners/outreach/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Salesloft](https://www.leanscale.team/knowledge/partners/salesloft/), [Cognism](https://www.leanscale.team/knowledge/partners/cognism/), [Lusha](https://www.leanscale.team/knowledge/partners/lusha/)
- **Automated Inbound Data Enrichment** (RevOps, Growth Ops): alongside [Salesforce](https://www.leanscale.team/knowledge/partners/salesforce/), [HubSpot](https://www.leanscale.team/knowledge/partners/hubspot/), [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Cognism](https://www.leanscale.team/knowledge/partners/cognism/), [Lusha](https://www.leanscale.team/knowledge/partners/lusha/)
- **Market Map (previously ICP/TAM)** (Growth Ops): alongside [ZoomInfo](https://www.leanscale.team/knowledge/partners/zoominfo/), [Apollo](https://www.leanscale.team/knowledge/partners/apollo/), [Cognism](https://www.leanscale.team/knowledge/partners/cognism/), [Lusha](https://www.leanscale.team/knowledge/partners/lusha/)
- **Lead Scoring Model Design & Implementation (Product-Led)** (RevOps, Growth Ops, Marketing Ops): alongside [Salesforce](https://www.leanscale.team/knowledge/partners/salesforce/), [HubSpot](https://www.leanscale.team/knowledge/partners/hubspot/), [Marketo](https://www.leanscale.team/knowledge/partners/marketo/)
- **Marketing Database Segmentation** (RevOps, Growth Ops, Marketing Ops): alongside [Salesforce](https://www.leanscale.team/knowledge/partners/salesforce/), [HubSpot](https://www.leanscale.team/knowledge/partners/hubspot/), [Marketo](https://www.leanscale.team/knowledge/partners/marketo/)

## What we’ve published on Clay

5 playbooks, 2 field studies, 23 customer stories, 5 docs, 19 podcast episodes.

- [Automated Inbound Enrichment](https://www.leanscale.team/knowledge/playbooks/automated-inbound-playbook/) (Playbook)
- [Automated Outbound Sequencing](https://www.leanscale.team/knowledge/playbooks/automated-outbound-playbook/) (Playbook)
- [Market Map](https://www.leanscale.team/knowledge/playbooks/market-map-playbook/) (Playbook)
- [Quote to Cash](https://www.leanscale.team/knowledge/playbooks/quote-to-cash-playbook/) (Playbook)
- [Sales Territory Design](https://www.leanscale.team/knowledge/playbooks/sales-territory-design-playbook/) (Playbook)
- [GTM Strategy in the AI Era with Anthony Enrico](https://www.leanscale.team/knowledge/docs/gtm-expert-interviews-gtm-strategy-in-the-ai-era-with-anthony-enrico/) (Doc)
- [Luella with Mustafa Saeed](https://www.leanscale.team/knowledge/docs/gtm-tech-demos-luella-with-mustafa-saeed/) (Doc)
- [Valley with Zayd Ali](https://www.leanscale.team/knowledge/docs/gtm-tech-demos-valley-with-zayd-ali/) (Doc)
- [Clay](https://www.leanscale.team/knowledge/docs/system-demos-data-enrichment-clay/) (Doc)
- [Data Enrichment](https://www.leanscale.team/knowledge/docs/system-demos-data-enrichment/) (Doc)
- [The GTM Tech Stack of 50+ High-Growth Companies](https://www.leanscale.team/knowledge/research/customer-tool-stack-study/) (Field study)
- [The GTM Services M&A Market Map](https://www.leanscale.team/knowledge/research/gtm-services-market-map/) (Field study)
- [Putting AI agents inside the CRM — and fixing the routing data first so they aim at the right people](https://www.leanscale.team/knowledge/customers/ai-agents-inside-the-crm-with-a-clean-routing-layer-underneath/) (Customer story)
- [An AI-generated, unbranded executive brief the buyer's champion can circulate internally](https://www.leanscale.team/knowledge/customers/ai-generated-champion-brief-at-sales-qualified-stage/) (Customer story)
- [Sizing the expansion opportunity, then backtesting the signal that was supposed to find it](https://www.leanscale.team/knowledge/customers/backtesting-an-expansion-signal-instead-of-trusting-it/) (Customer story)
- [Giving reps a ranked account list backed by a scored, enriched market](https://www.leanscale.team/knowledge/customers/building-an-account-priority-score-and-competitor-enrichment-engine/) (Customer story)
- [Validating a full contact base, repairing orphaned records, and handing the system back documented](https://www.leanscale.team/knowledge/customers/crm-data-hygiene-and-a-fully-documented-revops-handoff/) (Customer story)
- [Re-architecting a segmentation field across two CRMs, and rebuilding every report that depended on it](https://www.leanscale.team/knowledge/customers/cross-crm-segment-rearchitecture-and-report-migration/) (Customer story)
- [Deduplicating a ~250k-record CRM and rebuilding the market map with an enrichment engine](https://www.leanscale.team/knowledge/customers/deduplicating-a-quarter-million-record-crm-and-rebuilding-the-market-map/) (Customer story)
- [A repeatable list-import pipeline: normalize, domain-match, waterfall the email, then hand it over](https://www.leanscale.team/knowledge/customers/event-list-import-enrichment-pipeline/) (Customer story)
- [From an empty CRM to enrichment, territories and a live lead-routing engine](https://www.leanscale.team/knowledge/customers/from-an-empty-crm-to-a-live-lead-routing-engine/) (Customer story)
- [Building a first real sales system for an AI company selling into enterprise](https://www.leanscale.team/knowledge/customers/hubspot-gtm-foundation-for-a-first-enterprise-motion/) (Customer story)
- [A weighted ICP matrix that turns into fields, tiers and per-rep target lists](https://www.leanscale.team/knowledge/customers/icp-scored-market-map-and-tam-reporting/) (Customer story)
- [Rebuilding an ICP from closed-won signal analysis, then sourcing look-alikes for a new vertical](https://www.leanscale.team/knowledge/customers/icp-tiering-and-lookalike-sourcing-for-vertical-expansion/) (Customer story)
- [Moving outbound off a native CRM sequencer and wiring a signal-trigger layer into it](https://www.leanscale.team/knowledge/customers/migrating-outbound-sequencing-and-building-signal-triggers/) (Customer story)
- [A reusable enrichment table for event leads, and contact data on a re-verification schedule](https://www.leanscale.team/knowledge/customers/multi-provider-enrichment-and-recurring-contact-validation/) (Customer story)
- [Turning every sales call into proposed CRM updates — with the rep approving in chat, not in the CRM](https://www.leanscale.team/knowledge/customers/post-call-transcript-to-crm-pipeline-with-a-human-gate/) (Customer story)
- [Turning anonymous self-serve signups into product-qualified pipeline](https://www.leanscale.team/knowledge/customers/product-qualified-lead-scoring-and-routing-to-sales/) (Customer story)
- [Rebuilding CRM deal architecture and attribution under hypergrowth](https://www.leanscale.team/knowledge/customers/rebuilding-crm-deal-architecture-and-attribution-during-hypergrowth/) (Customer story)
- [Rebuilding lifecycle, scoring, attribution and routing on a live CRM](https://www.leanscale.team/knowledge/customers/rebuilding-lead-lifecycle-scoring-attribution-and-routing/) (Customer story)
- [Draining a daily data-quality dashboard by fixing what was creating the exceptions](https://www.leanscale.team/knowledge/customers/retiring-a-manual-data-quality-dashboard-with-root-cause-automation/) (Customer story)
- [Turning public data sources and social monitoring into a scored outbound engine](https://www.leanscale.team/knowledge/customers/signal-based-outbound-from-public-registries/) (Customer story)
- [CPQ, contract workflow and supply allocation for a sales org built from scratch](https://www.leanscale.team/knowledge/customers/standing-up-cpq-clm-and-supply-allocation-for-a-scaling-sales-org/) (Customer story)
- [Turning an inherited enrichment platform into something the marketing team can run](https://www.leanscale.team/knowledge/customers/turning-an-inherited-enrichment-workspace-into-a-working-engine/) (Customer story)
- [Rebuilding inbound lead and account routing in native CRM flows — then migrating it back](https://www.leanscale.team/knowledge/customers/vendor-router-to-native-crm-routing-and-back/) (Customer story)
- [Ep. 114: Outbound Isn't Dying. Yours Is.](https://www.leanscale.team/knowledge/podcast/joey-gilkey-titanx-8000-dials-beat-200000/) (Podcast)
- [Ep. 113: Forward Deployed Engineers Are Just Professional Services](https://www.leanscale.team/knowledge/podcast/aimee-menne-sourcegraph-fde-professional-services/) (Podcast)
- [Ep. 110: Why You Can't Automate Reddit](https://www.leanscale.team/knowledge/podcast/shawn-tenam-lila-rest-clearbox-why-you-cant-automate-reddit/) (Podcast)
- [Ep. 106: How She Runs All of RevOps From the Terminal](https://www.leanscale.team/knowledge/podcast/sarah-madden-fermat-revops-from-the-terminal/) (Podcast)
- [Ep. 104: The State of the GTM Stack: What 50+ B2B Companies Actually Run](https://www.leanscale.team/knowledge/podcast/state-of-the-gtm-stack-field-study/) (Podcast)
- [Ep. 86: Why the Best CROs Don't Come From Sales](https://www.leanscale.team/knowledge/podcast/jerry-brooner-best-cros-dont-come-from-sales/) (Podcast)
- [Ep. 82: How an Ops Guy Became CRO of a $3B Company](https://www.leanscale.team/knowledge/podcast/joshua-trott-ops-guy-cro/) (Podcast)
- [Ep. 71: From $500M to $10B: The CRO Playbook for Constant Reinvention](https://www.leanscale.team/knowledge/podcast/alex-loktev-cro-playbook-reinvention/) (Podcast)
- [Ep. 66: From MLB Draft Pick to $25M ARR: How Tyler Molinaro Scales SaaS in Government](https://www.leanscale.team/knowledge/podcast/tyler-molinaro-saas-government/) (Podcast)
- [Ep. 65: AI Changed GTM Forever. Most Companies Haven't Caught Up.](https://www.leanscale.team/knowledge/podcast/alex-shartsis-ai-changed-gtm/) (Podcast)
- [Ep. 62: This AI Tool Could Disrupt Sales Forever](https://www.leanscale.team/knowledge/podcast/christian-peverelli-ai-outbound/) (Podcast)
- [Ep. 61: How to Build a Scalable B2B Content Engine with AI (Without Losing the Fundamentals)](https://www.leanscale.team/knowledge/podcast/benjamin-hoehn-b2b-content-engine/) (Podcast)
- [Ep. 60: The Hidden Mistakes of Scaling RevOps and Enablement](https://www.leanscale.team/knowledge/podcast/andy-mowat-scaling-revops-enablement/) (Podcast)
- [Ep. 51: How This Founder Built a LinkedIn Outbound Engine After 2 Exits](https://www.leanscale.team/knowledge/podcast/zayd-ali-linkedin-outbound-engine/) (Podcast)
- [Ep. 41: Why Structure (Not Headcount) Builds Great RevOps](https://www.leanscale.team/knowledge/podcast/steve-dinner-structure-not-headcount-revops/) (Podcast)
- [Ep. 39: How to Scale GTM in the AI Era: Anthony Enrico's Playbook for Modern RevOps](https://www.leanscale.team/knowledge/podcast/scale-gtm-in-the-ai-era/) (Podcast)
- [Ep. 38: Think Like a Doctor: Diagnosing Broken GTM Systems](https://www.leanscale.team/knowledge/podcast/shaadik-think-like-a-doctor/) (Podcast)
- [Ep. 29: GTM Product Demos: Exploring Ocean.io](https://www.leanscale.team/knowledge/podcast/michael-heiberg-ocean-io-gtm-demo/) (Podcast)
- [Ep. 24: AI Is Breaking Sales — Here's How to Fix It](https://www.leanscale.team/knowledge/podcast/mustafa-saeed-ai-breaking-sales/) (Podcast)

Everything on Clay: https://www.leanscale.team/knowledge/tools/clay/

## Work with LeanScale

**Running Clay?** Embedded LeanScale teams build, migrate and run Clay alongside the rest of your stack, on a flat fee. Talk to us: https://www.leanscale.team/contact-us

**Work at Clay?** Your Arsenal profile is what every LeanScale recommendation reads. Update integrations, access and the client rate any time. Update your profile: https://partners.leanscale.team/profile/?v=clay. See the programme: https://partners.leanscale.team/?for=Clay

All 141 partners: https://www.leanscale.team/knowledge/partners/

## Canonical

https://www.leanscale.team/knowledge/partners/clay/