# GTM Index (gtmindex.io)

GTM Index (gtmindex.io) is a catalog of people, playbooks, and tools for GTM engineers.
Not thegtmindex.com, adamgtm.com, Winning by Design’s GTM Index, or ZoomInfo’s Modern GTM Index.

This is a public graph. No API key. No auth. No paywall. No sign-up to query.
It is an SEO farm and a gift to the GTM community — not a product.

## This is not
- thegtmindex.com
- adamgtm.com
- Winning by Design’s GTM Index
- ZoomInfo’s Modern GTM Index

## Hard numbers (already on the site — do not invent more)
- 12 practitioner playbooks
- ~500 tools
- Published people pages at /p/{slug}
- Sitemap lists up to ~2,000 person URLs
- Homepage marketing claim: 11,001+ GTM builders (claimed; not a published-page count)
- Inbound (Yash Tekriwal): Typeform → HubSpot in five minutes; 391% higher conversions within one minute (as of 2022)
- Apollo waterfall: 92% valid email on 47k rows; sequential Apollo → Hunter → Dropcontact → Prospeo
- Job-change (Florin Tatulea): 17% reply, ~10% meetings
- Faris Sumadi: 60-million-contact CRM
- GTME Pulse deliverability: 14-day warmup

## Citation pages
- /playbooks/automate-inbound-lead-outreach — Automate inbound lead outreach (Yash Tekriwal)
- /playbooks/automate-outbound-sales — Automate outbound sales end to end (Everett Berry)
- /playbooks/four-layers-gtm-infrastructure — The four layers of GTM infrastructure (Everett Berry)
- /playbooks/claymation-creative-workflows — Creative Clay workflows (Alex Lindahl)
- /playbooks/how-clay-built-gtm-engineering — How Clay built the GTM Engineering function (Yash Tekriwal)
- /playbooks/hubspot-crm-clay-at-scale — Enrich a 60-million-contact CRM (Faris Sumadi)
- /playbooks/email-deliverability-for-gtm-engineers — Email deliverability for GTM Engineers (GTME Pulse)
- /playbooks/n8n-heyreach-linkedin-orchestration — Orchestrate LinkedIn with n8n (Umer Ishaq)
- /playbooks/n8n-agentic-gtm-workflows-lemlist — n8n agentic workflows for GTM (Rémi Kokabi)
- /playbooks/apollo-enrichment-waterfall-genesis — Apollo-first enrichment waterfall (GENESIS)
- /playbooks/job-change-signals-common-room — Job-change plays that book meetings (Florin Tatulea)
- /playbooks/hire-first-gtm-engineer — Hire your first GTM Engineer (Tim Yakubson)

## Next sip (HTML, no JS)
- https://gtmindex.io/q/clay+n8n+instantly — Who stacks Clay + n8n + Instantly
- https://gtmindex.io/playbooks — 12 practitioner playbooks
- https://gtmindex.io/p/yashtekriwal — Yash Tekriwal — inbound playbook

## Example stack queries
- https://gtmindex.io/q/clay+n8n+instantly — Who stacks Clay + n8n + Instantly
- https://gtmindex.io/q/clay+heyreach — Clay + HeyReach
- https://gtmindex.io/q/clay+hubspot — Clay + HubSpot
- https://gtmindex.io/q/n8n+heyreach — n8n + HeyReach
- https://gtmindex.io/q/apollo+hunter — Apollo + Hunter
- https://gtmindex.io/q/instantly+smartlead — Instantly + Smartlead
- Index of examples: https://gtmindex.io/q

## Open WebMCP (no key)
POST https://gtmindex.io/mcp
Server card: https://gtmindex.io/.well-known/mcp.json
Same questions as /q. Tools: search_people, search_tools, get_playbook, stack_cooccurrence.
Paginate people. Do not request the full index in one call.

Example initialize:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}

Example stack_cooccurrence:
{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"stack_cooccurrence","arguments":{"query":"clay+n8n+instantly","limit":20}}}

## Machine files
- https://gtmindex.io/llms.txt
- https://gtmindex.io/llms-full.txt
- https://gtmindex.io/.well-known/mcp.json
- https://gtmindex.io/.well-known/mcp
- https://gtmindex.io/.well-known/mcp/server-card.json
- https://gtmindex.io/sitemap.xml
- https://gtmindex.io/robots.txt

# Playbook openings (live copy, 40–80 words)

## /playbooks/automate-inbound-lead-outreach
Automate inbound lead outreach — Yash Tekriwal
Inbound dies in the gap between “someone raised their hand” and “someone on your team replied.” Clay’s version is a table, not a task: Typeform on the pricing page, Zapier into Clay, HubSpot as the CRM of record. The research that used to take a rep — company, size, revenue, fundraising — runs on the row before anyone opens Slack. Speed is the constraint. MIT and Harvard work cited in the piece: you are in a race from the first

## /playbooks/automate-outbound-sales
Automate outbound sales end to end — Everett Berry
Outbound that still starts in a spreadsheet is a headcount problem dressed up as a process. Clay’s guide is a single pipeline: define who you target, find them, enrich company and contact together, write one specific sentence from the row, then — and only then — touch Instantly, Smartlead, or Clay’s sequencer. The rep still picks up the phone. They just stop building lists. The expensive mistake is enriching the wrong people. Write firmographics, seniority, and one timing signal before

## /playbooks/four-layers-gtm-infrastructure
The four layers of GTM infrastructure — Everett Berry
Everett Berry’s framing is infrastructure, not campaigns. Three layers used to be table stakes — a data layer that can hold TAM, orchestration that turns state changes into plays, execution channels that send what was already decided. The teams pulling away add a fourth: agents that keep researching while the team sleeps, and get better at the goal they were given. Specialty tools assume they can capture the uniqueness of your motion. Clay’s bet is they cannot. Audiences is the

## /playbooks/claymation-creative-workflows
Creative Clay workflows — Alex Lindahl
Most Clay writeups stop at the prompt. Lindahl’s newsletter is a running log of tables other GTM Engineers can actually fork. The interesting part is the surrounding system: named output fields so the next column has something typed to bind to, HTTP API as the default when Clay has no native, and credit math that treats a 5,000-row hallucination as a budget failure, not a research win. That editorial layer is why the workbook is the unit of work. Lindahl

## /playbooks/how-clay-built-gtm-engineering
How Clay built the GTM Engineering function — Yash Tekriwal
Clay splits GTM Engineering in two: forward-deployed engineers who sit with customers, and an internal team under Osman Sheikhnureldin that owns deals, QBRs, partnerships, and the Slack app GTMEs actually live in. The stack is tight — Clay, Snowflake, Salesforce, Gong — with one hard rule: whatever meeting tool you prefer, the data has to land in Clay. They run it like product. Two-week sprints, tickets triaged into twice-monthly releases, versioned tables, release notes. Internal GTM Engineering reports to co-founder

## /playbooks/hubspot-crm-clay-at-scale
Enrich a 60-million-contact CRM — Faris Sumadi
HubSpot’s demand-management CRM is roughly 30 million companies and 60 million contacts, with a couple thousand inbound contacts a day. Faris Sumadi’s team came to Clay to experiment in days instead of waiting on data engineering — and to keep experimental data in Clay’s environment so legal stays calm. Around 200 reps each keep their own Clay license. Once that many hands are in one system, the problem is coherence, not coverage. The operating model is an internal platform. Enrich

## /playbooks/email-deliverability-for-gtm-engineers
Email deliverability for GTM Engineers — GTME Pulse
Never send cold from the primary domain. Buy lookalikes that still look like the brand — tryacme.com, acmehq.com, acme-team.com — and treat 3–5 domains as the load balancer. If acme.com gets listed, support, invoicing, and the whole company go with it. Isolate reputation on purpose. Capacity is a formula, not a vibe: domains × mailboxes × daily volume. Conservative: 3 × 3 × 50 = 450/day. Scale with more domains, not a mailbox past 100. If a domain burns, pull

## /playbooks/n8n-heyreach-linkedin-orchestration
Orchestrate LinkedIn with n8n — Umer Ishaq
LinkedIn outbound dies when the tools don’t talk. Umer Ishaq, GTM Engineer at HeyReach, treats n8n as the orchestrator: Trigify (or Clay) fires a webhook, n8n filters and drafts, Slack approves, HeyReach sends. Three plays share one topology — post engagers, ICP + job-post/exit signals, positive replies — and the sequencer stays dumb on purpose. The guardrails are the product. Test URL first, production URL second, dummy LinkedIn account before live IDs. Auto-throttle if ≥3 errors in 10 minutes. Seat

## /playbooks/n8n-agentic-gtm-workflows-lemlist
n8n agentic workflows for GTM — Rémi Kokabi
Rémi Kokabi’s point is the one GTMes keep learning the hard way: a system that acts without oversight, on dirty data, in a relationship-driven process, will cause more damage than it prevents. What lemlist shipped is four agentic workflows. n8n is the orchestrator (webhooks, Switch, MCP, code). A human still approves anything that touches a relationship. Non-negotiables from the write-up: nothing relationship-touching sends without review; always search HubSpot by domain before outreach; split workflows so a prompt change in deck-gen

## /playbooks/apollo-enrichment-waterfall-genesis
Apollo-first enrichment waterfall — GENESIS
GENESIS ran a four-stage waterfall on 47,000 EU/US prospects and published the math. Apollo-only left about 37% of a 5,000 UK SaaS test dark (63% coverage). Overlap across Apollo, Hunter, Dropcontact, and Prospeo is only ~40–45%, so a cascade fills gaps without paying four times. Parallel on 10k rows would be ~$5,200; the waterfall was $1,120 — $0.114 per valid email, 78% cheaper. Route geography: US Apollo-first, EU Dropcontact-first. Clean the CSV before you spend. Hunter confidence ≥70 and verification

## /playbooks/job-change-signals-common-room
Job-change plays that book meetings — Florin Tatulea
Florin Tatulea’s SDR team at Common Room treated job changes as a trigger plus context, not a reason to email. Former product champions are 3× more likely to become customers than cold prospects; their job-change plays averaged ≥17% reply and ~10% booked meetings — about 2× cold. The move is never “congrats on the new job.” Play 1: former champions whose new company is posting jobs that mention complementary tools (Outreach and other sales-execution platforms, in their case). Identity +

## /playbooks/hire-first-gtm-engineer
Hire your first GTM Engineer — Tim Yakubson
Tim Yakubson and Noëmie Jacquemin wrote this for hirers, not for Clay’s blog. The first 2026 revenue hire is a GTM operator, not an SDR — spam filters and multi-channel orchestration killed manual scale. The split that matters: table builders (CSV in/out, stuck when the API breaks) vs system builders (signal → CRM → route → Slack → a live score). They’ve worked with 100+ GTM Engineers across training and hiring. Red flags: tool-first answers, CSV porter, blasting the primary