AI GTM hacks from the GTM Clawllective

The GTM Clawllective is the Chili Piper-powered community for AI GTM builders. Operators share the prompts, skills, workflows, and vibe-built apps they run in production, so that everyone else can fork them instead of starting from a blank page. This article collects a handful of the hacks the community has flagged as Spicy Recipes (its badge for the builds other members should try first), plus the fastest way to get the rest.

Note: Every hack in this article is free to read, copy, and download from gtmclawllective.org, with no sign-up required. The Slack is where you ask the builders questions, get your own prompt sharpened, and hear about the next one before it hits the site: join the GTM Clawllective.

Table of Contents

• What is the GTM Clawllective?
• Workflows: two agents that prospect for you
• Vibe-built apps: tools members built with AI
• Prompts: copy, paste, run
• Skills: install once, reuse every day
• How do I join?
• Limitations

What is the GTM Clawllective?

Most "AI GTM" content is hype. The Clawllective is what is actually working in production: the tools teams pay for, and the workflows they wire them into. Members meet weekly, swap hacks in Slack, and publish the best ones on the site so the whole community can reuse them. Start with the Tech Map: it plots more than 595 AI GTM tools by funnel stage, so you can see what sits next to the tools you already own.

The community also meets live every week, at 12 PM ET:

• Thursdays – Sales and Ops AI GTM;
• Fridays – Marketing AI GTM.

Members present their own hacks in these sessions. The ones that land end up on the site with the Spicy Recipe badge.

Note: The site sorts hacks by what they are. A workflow is an end-to-end playbook (it can ship as plugin files); a skill is a reusable instruction set you add to your assistant; a vibe-built app is a working tool someone built with AI; a prompt is a single message you paste.

Workflows: two agents that prospect for you

Surgical Outbound – WAT Prospecting Agent

An Account Executive built this in Claude Code with zero coding background, while interviewing for the role. Name an account and the agent researches the company, maps the economic buyers, writes a multi-touch outreach cadence in your voice, and pushes it into Salesloft. Claude Code wrote every Python script underneath; the builder's job was to describe what they wanted and review the output.

The differentiator is the WAT framework (Workflows, Agents, Tools): agents detect broken connections and repair themselves instead of failing silently. The same starter file has since been reused to build an email manager and a food-ordering tool.

A typical cadence runs Day 1 (email and LinkedIn connection), Day 5 (email), Day 8 (LinkedIn message), and Day 14 (breakup). You review every touch for voice before anything ships.

Note: The guiding philosophy is baked into the agent instructions: prospecting is surgical, not volumetric. Every touch demonstrates homework. Multi-threading is the single highest-leverage activity.

Stack: Claude Code, LeadIQ (swap for ZoomInfo, Clay, or Apollo), and Salesloft (swap for Outreach or HubSpot Sequences). The two framework files the builder uses every day, CLAUDE.md and wat-framework.md, are free to download on the workflow page. To rebuild it yourself:

1. Install Claude Code and open a project folder;
2. Drop the WAT framework file into the project root;
3. In plan mode, describe the tool you want;
4. Review the plan, approve it, and let Claude Code build the workflows and tools;
5. Connect your sequencer and enrichment tool, then push your first cadence.

Your first named account comes back researched, multi-threaded, and sequenced before you finish your coffee.

em-gine – Strategic Allbound Machine

After you install its three plugins in Claude Desktop and follow the setup guide, you type /run-pipeline [account name] and nine sequential agents fire, each reading from and writing to a shared Supabase database. What comes out the other end:

• A seven-tab structured account plan with a Lead Flow Map;
• Verified, tiered contacts with five Salesforce guardrail checks;
• A personalized SDR outreach sequence of seven to 11 touches, pushed to Salesloft through n8n;
• Three LinkedIn ABM ad variations, ready for Campaign Manager.

em-gine ships as three installable .plugin files (core, intel, and outreach) that you can download individually or as one .zip. It was architected by Emma Carey and presented by Cece Renick, both at Chili Piper, and it is the first result on the Workflows page for a reason.

Stack: Salesforce MCP (swap for HubSpot or Pipedrive), Gong MCP (optional), LeadIQ MCP (swap for ZoomInfo or Clay), Supabase MCP, and n8n to Salesloft. The full setup guide, connector swap instructions, and ICP configuration are linked from the workflow page. One command later, the first account plan is sitting in your database.

Vibe-built apps: tools members built with AI

Competitive Intel Bot

A Slack agent that generates dynamic, never-stale battlecard insights on competitors and positioning. It answers from a vector database of AI analysis of closed-won and closed-lost deals, G2 reviews, customer stories, and Slack intel channels, so the answer reflects last week's deals rather than last year's deck. Built by Tom Leader, and the only vibe-built app carrying the Spicy Recipe badge.

The bot runs on its builder's own deal data, so treat the app page as the blueprint: read how it is put together, then ask Tom in Slack how to fork it for your battlecards.

Sales Ops Maturity Assessment

Built by Taft Love, this app deploys a small set of agents to run a lightweight audit of a company's Sales Ops maturity. You authenticate your CRM, answer a few discovery questions, and receive a Sales Ops report. Taft's team uses it internally and has opened it to the community: the Access App button on the app page launches it in your browser, no install required. A demo video sits right next to it if you want to see the report before you connect anything.

Prompts: copy, paste, run

Every prompt in the library has a Copy prompt button, a "why it works" breakdown, and a sample input. Two to try before your next call.

The 90-Second Account Brief

Turn a company URL into a first-call brief in under 90 seconds. Works in Claude and ChatGPT with web browsing turned on.

You are a senior B2B SDR briefing me before a first call with [COMPANY URL]. Visit the company's website and the LinkedIn pages of the top 3 leadership team members. Output exactly four sections:

(1) What they sell, in one sentence a 12-year-old would understand.
(2) Three signals from the last 90 days that suggest GTM pain (hiring, funding, exec moves, product launches, public statements).
(3) Two specific hooks I can open the call with — each tied to one of the signals above. No generic "I saw you raised a round" lines.
(4) One question I should NOT ask because the answer is obvious from public info.

Length: 200 words total. No fluff. No "I hope this helps."

Why it works: it forces specificity (four named sections and a word cap), bans clichés, and asks for the negative: what not to ask. That last move is what separates good prep from average prep. Sample input: https://www.figma.com.

Cold Email That Doesn't Feel Cold

An outbound first touch built on a real signal, written in a register that does not trigger the "this is from a bot" reflex. The prompt caps the email at 75 words, opens with the signal as an observation rather than flattery, offers one concrete thing that is not a meeting or a demo, and ends with a question that costs 10 seconds to answer.

It also bans five phrases outright. If you have ever typed "just circling back", you already know which ones. The full prompt is on the prompt page.

Note: Have a prompt that almost works? Post the draft in the #prompts-optimization-lab Slack channel. The community sharpens it, and the best versions graduate back into the library.

Skills: install once, reuse every day

Install one skill and your next demo prep, post-call recap, and closed-won handoff run from a single request instead of a blank chat window. A skill is a reusable instruction set that teaches an AI assistant how to do one job well. The library holds 28 of them, most from Corey Haines' open marketing skills collection (SEO audit, copywriting, page CRO, pricing strategy, launch strategy, and more). Two that speak directly to revenue teams:

Open a skill's page on gtmclawllective.org for its source and author. Chili Piper also maintains its own first-party set of skills for diagnosing routing, auditing routers, and managing configuration. See Chili Piper Skills (AI recipes) for the install steps, which work the same way for any skill packaged as a plugin or .zip.

How do I join?

1. Join the Slack and say hello in #gtm-hacks with what you are building;
2. Sign up on the site to receive the weekly meetup invitations (Every other Wednesday for MCP; and every Friday for Sales/Marketing Hack, 12 PM ET);
3. Pick one hack from this article, run it this week, and share what you changed;
4. Built something yourself? Submit a hack and present it live to the community.

Limitations

• Community hacks are built and maintained by their authors, not by Chili Piper, including the ones built by Chili Piper employees. Chili Piper Support does not troubleshoot them; ask in the community Slack instead;
• Several workflows require third-party tools, API keys, and in some cases your own infrastructure (for example Claude Code or Claude Desktop, Salesloft, LeadIQ, Salesforce, a Supabase database, and an n8n instance). Check the Connector requirements table on each workflow page before you start;
• The full Surgical Outbound build is not yet downloadable because it contains the builder's API keys. Today you can download the two framework files and rebuild it in Claude Code by following the steps above;
• The Competitive Intel Bot runs on its builder's private data and is shared as a blueprint rather than a ready-to-use tool;
• The Sales Ops Maturity Assessment asks you to authenticate a CRM to a member-built app. Its page does not list supported CRMs or data handling; confirm both with the builder before connecting a production CRM;
• Downloads, prompts, and counts change as authors ship new versions. The site is always the source of truth.

Stuck on any of the above? That is exactly what #gtm-hacks is for. The builders are in the channel, and so is the next Spicy Recipe. Join the GTM Clawllective.