Top 10 Clay Workflow Templates for GTM Engineers
Skip the blank-table anxiety. These 10 templates cover 90% of what GTM Engineering teams build in Clay every week.
Why Templates Matter
Every GTM Engineer I know has rebuilt the same Clay table at least three times. Company enrichment. Contact finding. Lead scoring. The logic is identical across companies, but everyone builds from scratch because there is no shared template library worth using.
That changes here. These 10 templates come from production workflows running at B2B SaaS companies doing $5M-$100M ARR. They have been tested on real data, debugged through real edge cases, and refined through real pipeline outcomes. Each template includes the column structure, enrichment provider sequence, formula logic, and CRM integration pattern.
Clay appears in 69% of GTM Engineer job postings for a reason. It is the orchestration layer where enrichment, scoring, and routing converge. But a tool is only as good as the workflows you build inside it. These templates give you a 60-70% head start on build time.
Template 1: Company Enrichment Master Table
Start here. Every other template feeds from or into this one.
Input: Company domain (one column). That is it.
Enrichment sequence: Clay's built-in company enrichment fires first. It pulls employee count, industry, headquarters location, funding data, and tech stack from Clay's aggregated sources. If Clay returns incomplete data (happens roughly 15-20% of the time for smaller companies), a second column calls Apollo's company enrichment API as a fallback. A third column calls Clearbit if both Clay and Apollo miss. This three-provider waterfall hits 94%+ coverage on US-based B2B companies.
Output columns: Company name, employee count (bucketed: 1-10, 11-50, 51-200, 201-500, 500+), industry, HQ city, HQ state, founded year, estimated revenue range, tech stack (comma-separated), LinkedIn URL, last funding round, funding amount.
Formula logic: A "Data Quality Score" column assigns 1 point for each populated field. Companies scoring below 6/12 get flagged for manual review. Companies scoring 10+ are routed directly to the contact-finding table.
This table runs 24/7 on a scheduled import. New domains from your CRM, from inbound form submissions, or from account list uploads land here first. Everything downstream depends on clean company data.
Template 2: Contact Finder with Waterfall Logic
The workhorse. Takes enriched companies and finds the right people to contact.
Input: Company domain + target title keywords (e.g., "VP Sales, Director Revenue, Head of GTM").
Enrichment sequence: Clay's people search runs first, filtered by title keywords. If Clay returns fewer than 2 contacts per company, Apollo's contact search fires. For high-value accounts, a third layer uses Lusha or Cognism.
Output columns: Full name, title, email (verified), phone (when available), LinkedIn URL, confidence score.
The critical piece is email verification. Add a verification column using ZeroBounce, NeverBounce, or MillionVerifier ($0.0029/verification). Only contacts with verified emails pass to the sequence table. Bounced or catch-all emails get routed to a LinkedIn-only outreach track.
This template saves 3-4 hours per week compared to manual contact research. At scale (500+ accounts per month), it saves 15-20 hours.
Template 3: ICP Scoring Table
Not every company deserves the same outreach effort. This table separates the 10% of accounts that will drive 80% of pipeline.
Scoring criteria: Employee count match (0-25 points), industry match (0-20 points), tech stack overlap (0-20 points), funding recency (0-15 points), hiring signals (0-20 points). See the ICP framework and buying signal guide for details.
Output: Total score (0-100), tier assignment (A/B/C/D), recommended action. Tier A (70+) gets personalized sequences. Tier B (50-69) gets standard multi-step. Tier C (30-49) enters nurture. Tier D gets archived.
Building the formula: Create individual score columns for each criterion first. Employee count: use an IF chain. If 51-200 and your ICP is 51-200, score 25. If 201-500, score 15 (adjacent fit). Below 10 or above 1,000, score 0. Industry: exact match = 20, adjacent (e.g., fintech for a SaaS product) = 10, unrelated = 0. Tech stack: count overlapping tools from a predefined list. Each match = 4 points, cap at 20.
Tier routing automation: Connect the tier output to a Clay action column. Tier A rows trigger a webhook to your CRM (HubSpot or Salesforce) that creates the account, assigns the owner, and sends a Slack notification to the rep. Tier B rows push to your outbound tool via API. Tier C rows get tagged in your CRM as nurture with a 90-day re-score trigger. This eliminates manual sorting entirely.
Calibration tip: Run your first 50 accounts through the scorer, then compare against your own gut ranking. If the model and your instinct diverge on more than 20% of accounts, adjust weights. Most teams find they overweight industry and underweight hiring signals in their first pass.
Template 4: Job Posting Signal Monitor
When a company posts a job for a role you sell into, that is a buying signal. This table monitors job boards and flags hiring accounts.
Enrichment: Clay's job posting enrichment checks LinkedIn, Indeed, and Greenhouse. A formula categorizes postings by signal strength: direct buyer, adjacent role, or general growth.
Companies hiring for roles your product supports close at 2.4x the rate of cold accounts. This template costs pennies per check.
Column structure: Company domain (input), job title (enrichment output), posting date, posting URL, signal category (formula), signal score (formula), days since posted (calculated). The signal category formula checks title against three keyword lists you define: "direct_buyer" keywords (titles that buy your product), "adjacent" keywords (same department, different seniority), and "growth" keywords (general headcount expansion).
Scheduling: Run this table on a weekly schedule. Daily is overkill for most TAMs and burns credits. Weekly catches 95% of postings within a useful window. Set the table to import from a static list of target account domains, or connect it to your company enrichment table (Template 1) so new accounts automatically get monitored.
Action triggers: Direct buyer postings (score 10) should trigger same-day outreach with a subject line referencing the hire. "Saw you're hiring a [title]. Most teams at that stage..." Adjacent postings (score 6) go into standard sequence with signal context. Growth signals (score 3) get logged but don't trigger immediate outreach unless combined with other signals from Template 5.
Template 5: Tech Stack Change Detector
When a company adds or removes a tool, it signals a workflow change. Someone made a purchasing decision, which means budget exists and processes are being re-evaluated.
Method: Clay technographics with monthly snapshots. A formula compares current vs. previous and flags changes. Tech stack changes create 60-90 day buying windows.
Implementation detail: Create two columns: "Current Tech Stack" (live enrichment) and "Previous Tech Stack" (static, manually refreshed monthly). A formula column compares the two arrays and outputs three lists: added tools, removed tools, and unchanged tools. A second formula assigns signal scores: added competitor = 10 points, removed tool in your category = 9 points, added complementary tool = 7 points, general change = 3 points.
Monthly refresh process: On the first of each month, copy "Current Tech Stack" values to "Previous Tech Stack" column. This creates your baseline for next month's diff. Automate this with a Make scenario that runs on the 1st: export current values via Clay API, store in a Google Sheet, and re-import as the baseline. Total setup: 45 minutes. Monthly maintenance: zero.
Outreach angle: When a target company adds a tool you integrate with, that is your opening. "Noticed you just adopted [tool]. Most teams pair it with [your product] to handle [specific workflow]." This is 5x more relevant than a generic cold email because you're referencing a decision they made last month.
Template 6: LinkedIn Profile Enrichment
Takes names and companies, resolves verified LinkedIn profiles through a waterfall: Clay lookup, Apollo people search, then PhantomBuster Google scraper. Validation checks company domain match, not just name.
Why validation matters: Name matching alone produces 15-25% false positives. "John Smith at Acme" might match 8 LinkedIn profiles. The validation column checks that the LinkedIn profile's listed company matches your target domain (or a known subsidiary). This drops false positives below 3%.
Column structure: Full name, company domain, Clay LinkedIn lookup, Apollo LinkedIn lookup, PhantomBuster Google search (query: "[name] [company] site:linkedin.com/in/"), validated URL (COALESCE of verified results), confidence score (high/medium/low based on source and match quality). The PhantomBuster step costs $0.01-0.02 per lookup and catches 8-12% of contacts that Clay and Apollo miss.
Use case: LinkedIn profile URLs are required for HeyReach, Expandi, and other LinkedIn automation tools. Without verified URLs, connection requests go to the wrong person. This template is a prerequisite for any LinkedIn outreach campaign.
Template 7: CRM Data Hygiene
Title standardization, email re-verification (90+ day contacts), firmographic refresh, stale contact flagging. Push cleaned records back via Clay's native CRM integration. Run monthly to keep decay below 3%. See the CRM hygiene playbook.
Title standardization formula: Map variations to canonical titles. "VP of Sales" = "VP Sales" = "Vice President, Sales" = "Vice President of Sales." Build a lookup table of 30-40 common variations. This makes filtering and segmentation reliable instead of guessing which title variation your CRM stores.
Email re-verification flow: Filter contacts where "last verified date" exceeds 90 days. Run through ZeroBounce or NeverBounce ($0.003/verification). Flag bounced emails for removal. Flag catch-all domains for manual review. Update the verified date. At 2-3% monthly decay, a 10,000-contact database loses 200-300 valid emails per month. Re-verification costs $30 to catch them.
Stale contact detection: Flag contacts where the person's LinkedIn shows a different employer than your CRM record. Clay's enrichment catches company changes with 85-90% accuracy. Stale contacts waste sequence credits and hurt deliverability. Mark them "needs research" and route to Template 2 for replacement contacts at the same company.
Template 8: Inbound Lead Enrichment
Webhook-triggered enrichment from a single email address. Clay returns full context in under 30 seconds. Scoring formula assigns tier. Tier A triggers immediate Slack alert. Speed is the differentiator here.
Webhook setup: Your form tool (Typeform, HubSpot forms, or custom) sends a POST to Clay's webhook URL on submission. Clay receives the email, triggers enrichment, and runs the scoring formula. Total latency: 15-45 seconds depending on provider response times. For HubSpot, use the native Clay-HubSpot integration to trigger on "contact created" events.
Enrichment depth: From a single email address, this template populates: full name, title, company, company size, industry, tech stack, LinkedIn URL, phone (when available), funding stage, and hiring activity. That is 10-12 data points from one input. The ICP score formula runs on these enriched fields to produce a tier assignment.
Speed-to-lead matters: Harvard Business Review found that responding within 5 minutes produces 21x higher qualification rates vs 30 minutes. This template gets enriched data to your rep in under a minute. Tier A contacts get an immediate Slack DM with full context so the rep can call within 5 minutes of form submission. This is the single highest-ROI template on this list for inbound-heavy teams.
Template 9: Competitive Displacement
Clay technographics identify competitor users. G2 review data surfaces dissatisfied accounts. Job posting data flags accounts hiring for roles your product eliminates. Displacement campaigns convert at 1.5-2x greenfield rates because the prospect already understands the problem and has budget allocated.
Three-signal approach: Signal A: technographic detection (they use the competitor). Signal B: negative G2/Capterra reviews in the last 6 months (they're unhappy). Signal C: hiring for a role your product automates (they're trying to solve the problem with headcount). Any single signal justifies outreach. Two signals together produce 3x reply rates compared to cold.
Messaging framework: Never trash the competitor directly. Lead with the specific limitation you solve: "Most [competitor] users hit a wall when they try to [specific workflow]. Built something that handles it differently." Reference the exact pain point. G2 reviews are gold for identifying the specific complaints to reference in your copy.
Clay implementation: Column 1: Clay technographics filtered for competitor names. Column 2: G2 review sentiment (use Clay's web scraping or a dedicated enrichment). Column 3: Job posting signal (clone from Template 4). Scoring formula: competitor user = 8 points, negative review = 6 points, relevant hire = 5 points. Total 12+ = priority displacement target.
Template 10: Event Lead Enrichment
Post-conference lead cleanup: name parsing, company resolution from email domain, full waterfall enrichment, event source tagging. Turns messy spreadsheets into CRM-ready records in under an hour. The 48-hour post-event window is when response rates peak.
The problem: Conference badge scans and booth sign-up sheets give you names and emails with no context. Half the emails are personal Gmail addresses. Some names are misspelled. You have 48 hours before the prospect forgets meeting you. This template turns that chaos into actionable data fast.
Processing flow: Import the raw CSV. Column 1: name parsing (split first/last, fix capitalization). Column 2: domain extraction from email. Column 3: company resolution (Clay company enrichment from domain). Column 4: personal email detection (flag gmail.com, yahoo.com, etc. for LinkedIn-based company lookup). Column 5-8: full enrichment waterfall (title, phone, LinkedIn, company data). Column 9: event source tag. Column 10: ICP score from Template 3.
Personal email handling: 20-30% of event leads use personal emails. For these, Clay's people search by name + approximate company (from the booth conversation notes) resolves the business profile 70-80% of the time. The remaining 20-30% require manual LinkedIn lookup, but that is 5-8% of your total list, manageable in 30 minutes.
Timing: Upload the list within 4 hours of the event ending. Have the follow-up sequence ready to trigger within 24 hours. Day 1 email: reference the event and your conversation. Day 3: value-add content. Companies that follow up within 48 hours convert event leads at 3-4x the rate of those that wait a week.
Getting Started
Don't build all 10 at once. Start with Templates 1-3 (company enrichment, contact finding, scoring). Those form the core pipeline. Then layer in signal monitoring (4-5) and hygiene (7). Advanced templates are for teams with dialed-in fundamentals.
Each template takes 1-3 hours to build. Test with 20-50 records before scaling. For Clay pricing, see the full Clay review. For waterfall theory, check the enrichment waterfall architecture guide.
Common Mistakes to Avoid
Over-engineering the first version. Your initial template should do one thing well. Add complexity after you've validated the core logic works on real data. Teams that try to build the perfect 15-column table on day one never finish it.
Skipping the test batch. Always run 20-50 records before scaling to 500+. Check enrichment accuracy manually. Verify that scores align with your intuition. Fix edge cases before they multiply across thousands of records.
Ignoring credit consumption. A waterfall with 4 providers and 12 enrichment columns can burn 20-30 credits per row. At 1,000 rows, that is 20,000-30,000 credits. Map your credit usage per template and per row before running at scale. Clay Pro ($349/month) includes 10,000 credits. Clay Explorer ($149/month) includes 5,000. Plan accordingly.
No documentation. You'll forget why you built a formula in 3 months. Add a "Notes" column to every table explaining the logic. Name columns descriptively: "Apollo_Email_Fallback" not "Column_G." Your future self and your teammates will thank you.
Template Maintenance Schedule
Weekly: Check for failed enrichment runs, review error logs, process any flagged manual-review records.
Monthly: Update CRM hygiene baseline (Template 7), refresh tech stack snapshots (Template 5), review scoring calibration against recent closed-won deals.
Quarterly: Full audit of all active templates. Check that enrichment providers haven't changed their API responses. Recalibrate scoring weights based on 90-day conversion data. Archive or consolidate templates that overlap.
Frequently Asked Questions
How many Clay tables does a typical GTM team maintain?
Most GTM teams run 5-12 active Clay tables at any given time. A small startup might have 3 core tables (enrichment, scoring, routing). A mid-market team with multiple ICPs and segments can easily run 10-15 tables with dedicated workflows for each persona, territory, and signal type. The key is naming conventions and documentation so your team can find and maintain them.
Can I share Clay tables between team members?
Yes. Clay supports workspace-level tables that any team member can view, edit, or clone. You can also export table configurations as templates and share them outside your workspace. For teams with multiple GTM Engineers, create a shared folder structure with naming conventions like [ICP]-[Stage]-[Action] so everyone knows what each table does.
How long does it take to build a Clay enrichment workflow from scratch?
A basic enrichment table (company domain in, contacts out) takes 30-60 minutes to build. A full multi-step workflow with waterfall enrichment, scoring, and CRM push takes 2-4 hours for the initial build. After that, maintenance is 1-2 hours per week. Templates cut initial build time by 60-70% because the logic and column structure are already configured.
What is the difference between Clay templates and Clay formulas?
Templates are pre-built table structures with configured columns, enrichment steps, and logic. Formulas are individual cell-level calculations within a table (like spreadsheet formulas). Templates contain formulas, but they also include the overall workflow architecture: which enrichment providers to call, in what order, and what to do with the results.
Do Clay templates work with the free Clay plan?
Most templates work on any Clay plan, but enrichment-heavy templates consume credits faster on lower plans. The free plan gives you 100 credits per month, which is enough to test a template but not enough to run it at production scale. The Explorer plan ($149/month) includes 5,000 credits, which covers most single-ICP workflows.
Source: State of GTM Engineering Report 2026 (n=228). Salary data combines survey responses from 228 GTM Engineers across 32 countries with analysis of 3,342 job postings.