Creative Clay workflows (Claymation)
Prompt patterns, HTTP APIs, and the weird-but-working plays GTMes actually steal.
Always backlinked
Playbooks
How GTM Engineers work — systems already shipped, always linked to the source. Not templates. Documented plays with a person and a stack.
Category
Tools
12 playbooks
Claymation Inbound Automate inbound lead outreach
Form fill to first touch — enrich, score, and sequence without a human in the loop.
Outbound Automate outbound sales end to end
ICP to sequencer in one pipeline: waterfall, AI openers, warmed domains. No spreadsheet.
Infrastructure The four layers of GTM infrastructure
Data, orchestration, execution, agents — compounding systems, not one-off campaigns.
Function How Clay built the GTM Engineering function
How Clay named the role — and ran it like a product team.
Scale Enrich a 60-million-contact CRM
Functions, credit ROI, and what survives at tens of millions of HubSpot records.
Deliverability Email deliverability for GTM Engineers
Secondary domains, 14-day warmup, rotation math. Copy is irrelevant if it never hits the inbox.
LinkedIn Orchestrate LinkedIn with n8n
Webhooks, Slack approvals, and HeyReach campaigns — n8n as the glue, not another sequencer.
Orchestration n8n agentic workflows for GTM
Not autonomous agents. Four n8n workflows with a human in the loop — LinkedIn, trials, replies, decks.
Data Apollo-first enrichment waterfall
Stage 1 Apollo, then Hunter, Dropcontact, Prospeo. 92% valid email on 47k rows. Not four providers in parallel.
Signals Job-change plays that book meetings
Not “congrats on the new role.” Champions who moved, plus job listings at the new company. 17% reply, ~10% meetings.
Hiring Hire your first GTM Engineer
System builders vs table builders. Whiteboard the waterfall miss, the half-failed webhook, the job-change. Then look at salary.
Hiring or looking for people behind these systems? Browse people · Tools