# GTM Playbooks

> A directory of practical AI agent and Clay workflow playbooks for GTM, sales, RevOps, and finance teams that make money, save time, or improve efficiency.

Each playbook lists the problem it solves, the tools involved (Clay, HubSpot, Salesforce, Apollo, Zapier, n8n, OpenAI or Claude APIs, and others), numbered steps, a difficulty level, a template outline, and an hours-saved figure that is an estimate, not a measured result.

## Main pages

- [Homepage and full playbook listing](https://gtmplaybooks.io/): search and filter all 51 playbooks
- [Full playbook content](https://gtmplaybooks.io/llms-full.txt): one plain-text file with the steps, template outline, tools, difficulty, and hours-saved estimate for all 51 playbooks, plus every comparison verdict
- [Agent skills](https://gtmplaybooks.io/skills/): every playbook as a SKILL.md agent skill at https://gtmplaybooks.io/skills/<slug>/SKILL.md, with a JSON index at https://gtmplaybooks.io/skills/index.json
- [Sitemap](https://gtmplaybooks.io/sitemap.xml): every playbook, category, tool, and comparison URL
- [Sponsor](https://gtmplaybooks.io/sponsor/): Founding Sponsor offer, $99/month for featured placement on the site plus a newsletter mention, price locked for the first 5 sponsors
- [Playbooks by tool](https://gtmplaybooks.io/tools/): one page per tool used by at least 3 playbooks
- [Tool comparisons](https://gtmplaybooks.io/compare/): side-by-side comparisons of GTM tools with a verdict for each
- [Affiliate disclosure](https://gtmplaybooks.io/disclosure/): some vendor links may be affiliate links; commissions do not decide verdicts

## Tool comparisons

Each comparison covers features, the pricing model (with a link to the vendor pricing page instead of quoted prices), the playbooks that fit each tool, a "pick X if" verdict, and an FAQ.

- [Instantly vs Smartlead: Cold Email Sending for Clay Outbound](https://gtmplaybooks.io/compare/instantly-vs-smartlead/): Cold email sending. If Clay already does your list building and enrichment, both tools will send your campaigns well enough that agency needs and add-ons should decide. Agencies with many clients will find Smartlead's workspace and white-label options a closer fit. Teams that want lead data and AI reply handling bundled with sending will find more of that packaged in Instantly.
- [Apollo vs Clay: Prospecting and Enrichment Compared](https://gtmplaybooks.io/compare/apollo-vs-clay/): Prospecting and enrichment. If reps prospect by hand and need data, sequences, and calling in one place, start with Apollo. If you are building automated enrichment and research workflows that several people maintain, start with Clay. Many teams end up with both: Apollo for rep-facing search and sequences, Clay for enrichment and automation, with Apollo as one provider in the waterfall.
- [Make vs n8n for GTM Automation and AI Agents](https://gtmplaybooks.io/compare/make-vs-n8n/): Workflow automation. If your team wants a hosted tool and builds mostly app-to-app scenarios, Make is the simpler start. If you are building AI agents, loop over many records per run, or need to self-host, n8n is the stronger fit.

## Tools

Each tool page explains how the playbooks use that tool, lists every matching playbook, and links any comparison that covers it.

- [HubSpot playbooks](https://gtmplaybooks.io/tools/hubspot/): 36 playbooks. HubSpot is the CRM in most of these playbooks, usually listed as "HubSpot or Salesforce". It is where enriched data lands, where workflows assign owners and enroll contacts in sequences, and where Clay or Zapier look up existing contacts, companies, and deals before creating anything new.
- [Clay playbooks](https://gtmplaybooks.io/tools/clay/): 31 playbooks. Clay does the enrichment and research in these playbooks: waterfalls that try several data providers until one returns a verified email, CRM lookups that skip records you already have, AI columns that score or classify rows, and Claygent web research. Many of these playbooks also include a Clay CLI script you can paste into your own Clay CLI to build the workflow in your own workspace.
- [Salesforce playbooks](https://gtmplaybooks.io/tools/salesforce/): 26 playbooks. Salesforce appears as the CRM option in playbooks for routing, enrichment, outbound, and reporting. The playbooks use it as the system of record: look up accounts, contacts, and opportunities before acting, write scores and research back to records, and let assignment rules or flows decide ownership.
- [Zapier playbooks](https://gtmplaybooks.io/tools/zapier/): 22 playbooks. Zapier is the glue in playbooks that move data between apps without code: pipeline snapshots into Google Sheets, deal alerts into Slack, invoice reminders, revenue entries, and calendar or form events relayed to a Clay webhook. Each one runs on a schedule or a single trigger.
- [Slack playbooks](https://gtmplaybooks.io/tools/slack/): 20 playbooks. Slack is where these playbooks deliver the result to a person: a routed lead with the reason it fits, a deal that changed stage, a churn risk, a champion who changed jobs, or a pre-meeting brief. The pattern is the same across them: do the work in Clay, Zapier, or the CRM, then send the owner a short message with the context to act on.
- [Apollo playbooks](https://gtmplaybooks.io/tools/apollo/): 13 playbooks. Apollo is used for contact data in these playbooks: finding work emails and titles, pulling people from saved searches, and finding buyers at accounts flagged by a signal. Several pair it with Clay, either as one provider in a waterfall or as the first lookup before Clay tries others.
- [Google Sheets playbooks](https://gtmplaybooks.io/tools/google-sheets/): 13 playbooks. Google Sheets is the reporting layer in these playbooks: pipeline and campaign dashboards, revenue forecasts, board deck metrics, expense logs, and lost-deal summaries, usually filled by a Zapier step on a schedule. It is a practical choice when the team already works in spreadsheets and does not need a BI tool.
- [Instantly playbooks](https://gtmplaybooks.io/tools/instantly/): 12 playbooks. Instantly is the cold email sender in these outbound playbooks, usually listed as "Instantly or Smartlead". Clay or Apollo find and verify the contact, an AI step writes a first line or angle, and the lead goes into an Instantly campaign with those fields as custom variables.
- [OpenAI API playbooks](https://gtmplaybooks.io/tools/openai/): 11 playbooks. The OpenAI API is the language model step in these playbooks: scoring inbound leads against a written ICP, classifying support tickets for churn risk, extracting fields from receipts, drafting short notes, and categorizing lost-deal reasons. The prompts are written into each playbook so you can adapt them.
- [Smartlead playbooks](https://gtmplaybooks.io/tools/smartlead/): 10 playbooks. Smartlead is the cold email sender option in these outbound playbooks, alongside Instantly. The workflows find and verify contacts in Clay or Apollo, write a short opener, and add each lead to a Smartlead campaign with custom fields for the signal behind the email.
- [Claygent playbooks](https://gtmplaybooks.io/tools/claygent/): 9 playbooks. Claygent is Clay's AI web research agent. These playbooks use it to read company websites, careers pages, review sites, and news, then return answers a workflow can use, such as tech stack notes, recent company changes, hiring signals, or reviewer details. Every Claygent playbook here also uses Clay, so see the Clay hub for the full set.
- [Make playbooks](https://gtmplaybooks.io/tools/make/): 7 playbooks. Make is the visual automation option in these playbooks: syncing Apollo searches into Instantly, moving support tickets through an LLM for churn scoring, and relaying calendar events to a Clay webhook.
- [Stripe playbooks](https://gtmplaybooks.io/tools/stripe/): 4 playbooks. Stripe is the billing data source in these finance and RevOps playbooks: revenue entries for QuickBooks, MRR for a quarterly board deck, and renewal dates from subscription periods for usage health alerts.
- [Gmail playbooks](https://gtmplaybooks.io/tools/gmail/): 4 playbooks. Gmail is both a trigger and an output in these playbooks: forwarding receipt emails to be parsed into an expense log, logging sent intro requests to a sheet, and sending escalating invoice payment reminders, all through Zapier.

## Categories

- [Outbound](https://gtmplaybooks.io/category/outbound/): Prospecting, enrichment, and sequencing workflows for reaching net-new accounts.
- [Inbound](https://gtmplaybooks.io/category/inbound/): Enrich, qualify, and route the leads and buying signals that come to you.
- [RevOps](https://gtmplaybooks.io/category/revops/): CRM syncs, deduplication, alerts, and reporting that keep pipeline data accurate.
- [Finance/FP&A](https://gtmplaybooks.io/category/finance-fpa/): Invoicing, revenue, expense, and forecasting workflows for finance teams.
- [Content](https://gtmplaybooks.io/category/content/): Turn CRM, analytics, and support data into marketing content and distribution.
- [Research](https://gtmplaybooks.io/category/research/): Account, market, and competitor research run with Clay, Claygent, and LLM APIs.

## Playbooks

- [Enrich Inbound Leads with Apollo and Clay Waterfalls](https://gtmplaybooks.io/playbooks/enrich-leads-apollo-clay/): Marketing passes incomplete lead data to sales, forcing reps to research the basics by hand before every first touch.
- [Auto-Prospect Companies After Funding Announcements](https://gtmplaybooks.io/playbooks/auto-prospect-funding-events/): Sales teams miss narrow timing windows when companies raise capital and need new vendors.
- [Sync Salesforce Pipeline to Google Sheets Dashboard](https://gtmplaybooks.io/playbooks/sync-crm-to-google-sheets/): Executives ask for pipeline reports in spreadsheets, but pulling data manually creates version control chaos.
- [Route Gong Feature Requests to Product Board](https://gtmplaybooks.io/playbooks/gong-to-product-feedback/): Customer feature requests mentioned in sales calls never make it to product teams.
- [Personalize Outbound at Scale Using LinkedIn Data](https://gtmplaybooks.io/playbooks/personalize-outbound-linkedin/): Generic cold emails get few replies, and reps cannot manually research every prospect on a high-volume list. Includes a Clay CLI build.
- [Automate Stripe Revenue Recognition in QuickBooks](https://gtmplaybooks.io/playbooks/stripe-revenue-to-quickbooks/): Finance teams manually export Stripe transactions and re-key them into QuickBooks weekly, risking errors.
- [Analyze Lost Deals with Claygent and OpenAI](https://gtmplaybooks.io/playbooks/lost-deal-analysis/): Lost deal reasons in CRM are vague ("pricing", "timing"). Reps rarely document specifics.
- [Qualify Inbound Leads with AI Before Routing](https://gtmplaybooks.io/playbooks/qualify-inbound-with-ai/): SDRs lose a meaningful share of their day to unqualified inbound leads (students, competitors, wrong market).
- [Monitor Competitor Hiring to Spot Market Moves](https://gtmplaybooks.io/playbooks/scrape-competitor-job-posts/): Competitor intelligence is reactive. You learn about their new product after launch, not during the build.
- [Rotate LinkedIn Engagement Pods for Founder Accounts](https://gtmplaybooks.io/playbooks/linkedin-pod-rotation/): Founder posts on LinkedIn need early engagement but manually coordinating a pod is tedious.
- [Track Warm Intro Requests Across Your Network](https://gtmplaybooks.io/playbooks/warm-intro-tracker/): AEs lose track of warm intro requests sent via email and LinkedIn. Follow-ups fall through the cracks.
- [Automatically Update Case Study Metrics from CRM](https://gtmplaybooks.io/playbooks/automatically-update-case-studies/): Case studies quote metrics that were accurate when published and drift out of date. Marketing has no system to refresh them.
- [Parse Receipt Emails and Auto-Create Expense Reports](https://gtmplaybooks.io/playbooks/expense-report-automation/): Employees manually forward receipts to finance. Someone re-keys them into expense software.
- [Sync Apollo Saved Searches to Instantly Campaigns](https://gtmplaybooks.io/playbooks/apollo-to-instantly-sync/): Sales ops manually exports Apollo lists and imports them to Instantly weekly, delaying campaign launches.
- [Enrich Event Attendee Lists for Post-Event Follow-Up](https://gtmplaybooks.io/playbooks/enrich-event-attendees/): Event badge scans give you name and company, but no job title, email, or tech stack for targeting.
- [Build Blog Performance Dashboard from Google Analytics](https://gtmplaybooks.io/playbooks/content-performance-dashboard/): Marketing pulls blog traffic reports out of GA4 by hand each month, so trends are hard to compare over time.
- [Analyze Firmographics of Closed-Won Deals to Refine ICP](https://gtmplaybooks.io/playbooks/icp-firmographic-analysis/): Your ICP doc was written years ago, and the company profile it describes may no longer match the deals you actually win.
- [Auto-Generate Monthly Revenue Forecast from Pipeline](https://gtmplaybooks.io/playbooks/monthly-revenue-forecast/): Finance builds revenue forecasts by hand, applying historical close rates to current pipeline. It eats hours every month.
- [Monitor Website Intent Signals and Alert Sales](https://gtmplaybooks.io/playbooks/intent-signal-monitoring/): High-value accounts visit your pricing page repeatedly, but sales never finds out.
- [Track Multi-Channel Campaigns in One Unified Dashboard](https://gtmplaybooks.io/playbooks/multi-channel-campaign-tracking/): Marketing runs email, LinkedIn ads, and webinars, but attribution lives in a different tool for each channel.
- [Use Claygent to Research Target Account Tech Stacks](https://gtmplaybooks.io/playbooks/claygent-tech-stack-research/): Sales needs to know if prospects use competing tools before the first call, but researching each account by hand is slow.
- [Send Automated Invoice Payment Reminders](https://gtmplaybooks.io/playbooks/automated-invoice-reminders/): AR team manually checks which invoices are overdue and sends canned reminder emails. Pure busywork.
- [Scrape G2 and Capterra Reviews for Competitor Leads](https://gtmplaybooks.io/playbooks/scrape-review-sites-for-leads/): People leaving negative reviews on competitor G2 pages are in-market buyers, but finding them manually is slow.
- [Post Real-Time Deal Alerts to Slack by Stage](https://gtmplaybooks.io/playbooks/slack-deal-alerts/): Leadership wants to celebrate wins and coach deals in real time, but they live in Slack, not the CRM.
- [Generate Blog Post Ideas from Customer Questions](https://gtmplaybooks.io/playbooks/blog-post-idea-generator/): Support tickets are full of recurring customer questions that would make great blog content, but no one mines them.
- [Prevent Duplicate Contacts Across HubSpot and Salesforce](https://gtmplaybooks.io/playbooks/hubspot-salesforce-duplicate-prevention/): Marketing creates contacts in HubSpot while sales creates them in Salesforce, leading to duplicates and broken reporting.
- [Auto-Populate Quarterly Board Deck Metrics](https://gtmplaybooks.io/playbooks/quarterly-board-deck-automation/): Finance spends hours before each board meeting copying metrics from several systems into the board deck.
- [Get Alerted When Key Contacts Change Jobs](https://gtmplaybooks.io/playbooks/job-change-alerts/): Your champion at a customer changes jobs. By the time you notice, they have already bought a competitor.
- [Turn Anonymous Website Visitors into Outbound Sequences](https://gtmplaybooks.io/playbooks/website-visitors-to-outbound/): Marketing and sales cannot tell which ICP companies hit pricing, docs, or blog pages, so high-intent traffic dies without a follow-up.
- [Score Churn Risk from Support Tickets with an LLM](https://gtmplaybooks.io/playbooks/support-tickets-to-churn-risk/): CS and RevOps find churn late because ticket themes stay buried in Zendesk/Intercom while CRM health scores ignore qualitative signal.
- [Outbound When ICP Companies Hire AEs or SDRs](https://gtmplaybooks.io/playbooks/hiring-spike-outbound/): Competitors and category peers hiring sellers is a timing signal that budgets and territory plans are expanding, but most teams notice weeks late.
- [Reactivate Closed-Lost Deals When Fresh Intent Appears](https://gtmplaybooks.io/playbooks/closed-lost-reactivation/): Closed-lost accounts sit untouched while they later raise, hire, or install related tools, and AEs rediscover them too late.
- [Turn LinkedIn Ad Engagers into Sequenced Outbound](https://gtmplaybooks.io/playbooks/linkedin-ad-engagers-to-outbound/): People who like, comment, or click LinkedIn ads are warm, but the engagers never make it into CRM or a sequence unless someone exports by hand.
- [Alert AMs Before Renewal When Product Usage Drops](https://gtmplaybooks.io/playbooks/renewal-usage-health-alerts/): Account managers learn about churn risk at renewal time because usage and support signals are never joined to contract end dates.
- [Build a Clay Waterfall to Find Verified Work Emails](https://gtmplaybooks.io/playbooks/clay-waterfall-enrichment/): A single data provider misses many contacts, so reps either work incomplete lists or pay for several tools and copy results between them by hand. Includes a Clay CLI build.
- [Turn Buyer Intent Signals into Outbound Sequences](https://gtmplaybooks.io/playbooks/intent-signals-to-outbound/): Intent data shows which accounts are researching your category, but it sits in a dashboard nobody checks daily, so the signal is stale before a rep acts on it. Includes a Clay CLI build.
- [Keep CRM Data Clean with an AI Hygiene Agent](https://gtmplaybooks.io/playbooks/crm-hygiene-ai-agent/): CRM records decay as people change jobs and reps type titles and industries in different formats, so segmentation, routing, and reporting quietly break. Includes a Clay CLI build.
- [Automate Inbound Lead Routing with Enrichment and Fit Scoring](https://gtmplaybooks.io/playbooks/inbound-lead-routing/): Inbound leads wait in a shared queue or get assigned round-robin regardless of fit, so the best leads reach a rep late and poor-fit leads take up AE time. Includes a Clay CLI build.
- [Track Champion Job Changes to Open New Accounts](https://gtmplaybooks.io/playbooks/champion-job-change-tracking/): Former champions who move to a new company are some of the warmest prospects you have, but most teams notice the move months later, after the new team has picked its tools. Includes a Clay CLI build.
- [Route Product-Qualified Leads from Sign-Ups to Sales](https://gtmplaybooks.io/playbooks/pql-signups-to-sales/): Self-serve sign-ups pile up in the product, and sales either ignores them or chases every free account, so the few sign-ups from ICP companies who are actually using the product wait for a rep. Includes a Clay CLI build.
- [Rebook Demo No-Shows with a Short Personalized Sequence](https://gtmplaybooks.io/playbooks/meeting-no-show-rebook/): Booked demos that end as no-shows usually get one "sorry we missed you" email or nothing at all, so meetings the team already worked to create quietly drop out of the pipeline. Includes a Clay CLI build.
- [Launch Outbound When Target Accounts Add or Drop a Competitor](https://gtmplaybooks.io/playbooks/competitor-tech-churn-outbound/): When a target account drops a competitor or adds a tool that pairs with yours, there is a short window to start a conversation, but static tech stack lists only show what is installed today, not what changed. Includes a Clay CLI build.
- [Keep Clay Credit Spend Predictable on Enrichment Tables](https://gtmplaybooks.io/playbooks/clay-credit-budget-guardrails/): Clay tables that enrich every row, re-run on every edit, and call providers in no particular order burn through credits faster than planned, and the overspend usually shows up only when the monthly balance runs low.
- [Send Reps a Researched Account Brief Before Every Meeting](https://gtmplaybooks.io/playbooks/pre-meeting-account-brief/): Reps walk into first calls after a quick scan of LinkedIn and the CRM, or skip prep entirely when the calendar is full, so they miss recent company news, past conversations, and open deal context the team already has. Includes a Clay CLI build.
- [Find Lookalike Accounts from Your Closed-Won Customers](https://gtmplaybooks.io/playbooks/lookalike-accounts-from-closed-won/): Outbound lists are usually built from broad filters, while the best predictor of who will buy, the customers you already closed, sits in the CRM unused, so reps spend sequences on accounts that look nothing like your wins. Includes a Clay CLI build.
- [Answer Demo Requests Within Minutes, Even After Hours](https://gtmplaybooks.io/playbooks/inbound-speed-to-lead-after-hours/): Demo requests that come in at night or over the weekend wait until a rep logs on, so the buyer who was ready to talk on Friday evening gets a first reply on Monday, often after they have booked with someone else. Includes a Clay CLI build.
- [Run CRM-Writing AI Agents in Dry-Run Mode with Bulk Approvals](https://gtmplaybooks.io/playbooks/crm-agent-dry-run-approvals/): An AI agent that writes straight to Salesforce or HubSpot can change thousands of records before anyone notices a bad rule, and each change can trigger syncs, workflows, and sequences that are hard to trace and harder to reverse. Includes a Clay CLI build.
- [Build Prospect Lists from Plain-English Requests in Slack](https://gtmplaybooks.io/playbooks/slack-list-builder-agent/): Reps and marketers wait days for RevOps to build a prospect list, or pull their own from Apollo with inconsistent filters, no CRM dedupe, and no check on how many credits the pull will burn.
- [Weekly New Contractor Licenses into Clay for Outbound](https://gtmplaybooks.io/playbooks/new-contractor-licenses-to-outbound/): Newly licensed contractors are setting up insurance, software, suppliers, financing, and payroll for the first time, but each state board publishes licenses in its own format, so reps find them late or never. Data source: Multi-State Contractor License Search on Apify (https://apify.com/dynamic_jingle/multi-state-contractor-license-search).
- [Cut Demo Forms to Email Only and Fill the Rest with Clay](https://gtmplaybooks.io/playbooks/short-form-inbound-enrichment/): Long demo and contact forms ask buyers for company size, industry, role, and tech stack, fields people skip or fill with junk, while routing still needs them to send each lead to the right rep.
- [Check Sales Commissions Against Billing Before They Are Paid](https://gtmplaybooks.io/playbooks/sales-commission-accuracy-check/): Commissions are calculated from CRM closed-won data that can disagree with what was invoiced and collected, so wrong close dates, amount mismatches, split errors, and missed clawbacks surface after payroll, when they are harder to recover and explain.

## Clay CLI builds

Some playbooks include a "Build it in Clay" section: prerequisites, a workflow spec (trigger, ordered steps, inputs), and a copy-paste bash script for the Clay CLI. Readers run these commands in their own Clay workspace with their own login; nothing runs on GTM Playbooks servers. The Clay CLI cannot create tables, add columns, or import rows into a table, so each build creates a Clay workflow instead. Scripts are written against the CLI help output and have not been run by GTM Playbooks. Config shapes the help does not document are marked "Verify in your workspace" on the page and VERIFY in the script.

- [Personalize Outbound at Scale Using LinkedIn Data: Build it in Clay](https://gtmplaybooks.io/playbooks/personalize-outbound-linkedin/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 3 steps (research recent linkedin posts, write the first line, add the lead to an instantly campaign)
- [Build a Clay Waterfall to Find Verified Work Emails: Build it in Clay](https://gtmplaybooks.io/playbooks/clay-waterfall-enrichment/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 4 steps (find email with provider 1, find email with provider 2, verify the email, update the crm record)
- [Turn Buyer Intent Signals into Outbound Sequences: Build it in Clay](https://gtmplaybooks.io/playbooks/intent-signals-to-outbound/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 4 steps (enrich the account, find the best-fit contact, write the opener, add the contact to a sequence)
- [Keep CRM Data Clean with an AI Hygiene Agent: Build it in Clay](https://gtmplaybooks.io/playbooks/crm-hygiene-ai-agent/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 3 steps (verify the email, standardize title and fill firmographics, update the crm record)
- [Automate Inbound Lead Routing with Enrichment and Fit Scoring: Build it in Clay](https://gtmplaybooks.io/playbooks/inbound-lead-routing/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 4 steps (enrich the lead and company, score icp fit, assign the owner in the crm, alert the owner in slack)
- [Track Champion Job Changes to Open New Accounts: Build it in Clay](https://gtmplaybooks.io/playbooks/champion-job-change-tracking/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 3 steps (find current company and title, check the new company, alert the owner in slack)
- [Route Product-Qualified Leads from Sign-Ups to Sales: Build it in Clay](https://gtmplaybooks.io/playbooks/pql-signups-to-sales/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 4 steps (enrich the person and company, score fit and pql status, write the pql to the crm, alert the owner in slack)
- [Rebook Demo No-Shows with a Short Personalized Sequence: Build it in Clay](https://gtmplaybooks.io/playbooks/meeting-no-show-rebook/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 4 steps (look up the contact and deal, write the rebook note, flag the contact for rebooking, tell the rep in slack)
- [Launch Outbound When Target Accounts Add or Drop a Competitor: Build it in Clay](https://gtmplaybooks.io/playbooks/competitor-tech-churn-outbound/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 5 steps (pull current technologies, classify the change and write an opener, find the contact, add to the sequence, save the new list to the crm)
- [Send Reps a Researched Account Brief Before Every Meeting: Build it in Clay](https://gtmplaybooks.io/playbooks/pre-meeting-account-brief/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 6 steps (look up crm history, enrich the company and attendee, research recent changes, write the brief, send the brief in slack, save the brief to the crm)
- [Find Lookalike Accounts from Your Closed-Won Customers: Build it in Clay](https://gtmplaybooks.io/playbooks/lookalike-accounts-from-closed-won/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 5 steps (check the crm by domain, score the fit, find the buyer, add to the sequence, create the company in the crm)
- [Answer Demo Requests Within Minutes, Even After Hours: Build it in Clay](https://gtmplaybooks.io/playbooks/inbound-speed-to-lead-after-hours/#build-in-clay): Clay CLI v1.3.1, webhook trigger, 7 steps (check customers and open deals, enrich the lead, classify fit and escalations, write the first reply, send the reply, update the crm record, post the handoff in slack)
- [Run CRM-Writing AI Agents in Dry-Run Mode with Bulk Approvals: Build it in Clay](https://gtmplaybooks.io/playbooks/crm-agent-dry-run-approvals/#build-in-clay): Clay CLI v1.3.1, csv_upload trigger, 3 steps (read the current value, write the approved value, record the result)