Playbook · how-to · updated 5 November 2026
Claude Code for GTM engineering: six workflows, the skills behind them, and who runs it.
62.7% of GTM engineers run Claude Code and 35% of job postings ask for Claude by name, while 6% of engineers list it. This is what the work looks like when the logic lives in a repo you own.
Sources: State of GTM Engineering 2026; OneGTM GTME Data Report Q3 2026. Read 5 November 2026.
The six workflows
- ICP in code, not a slide. A scored definition of the account you want, as rules Claude can read and a human can argue with. Firmographics, tech, hiring and funding signals, each with a weight. Changing the ICP is a pull request, not a workshop.
- Lists from signals, on a schedule. A Claude Code skill that pulls accounts from job boards, funding feeds and tech-detection APIs when a signal fires, dedups against the CRM and writes to Clay or straight to the sequencer. Runs nightly; the log says what it added and why.
- Waterfall enrichment with a reason. Clay for the waterfall at volume; Claude for the exceptions. When three providers disagree on a title, an agent reads the profile and decides, and records the source it trusted.
- Research agents that write the first line. An agent reads the account page, the careers page and the last three posts, then writes the one line a good SDR would have written, with the source attached. Output is reviewed by a human the first two weeks, then sampled.
- Reply classification and routing. Every reply is read and classified (meeting, question, objection, out of office, not now, never). Each class has a route: calendar, human, nurture, suppression. The CRM gets the label and the reason.
- CRM sync that stays honest. One skill that writes activities, stages and reasons to HubSpot or Salesforce, reconciles weekly, and flags records the sequencer and the CRM disagree on. The runbook says what to do when a provider changes a field.
The skills that make it a system
Each workflow is a Claude Code skill: a folder with a SKILL.md, scripts and a test. Skills are files, so they are versioned, reviewed in pull requests and handed over like code. The set that ships with a Closer Method build:
icp-score (rules + weights, explain mode)signal-pull (job boards, funding, tech) with dedupenrich-exceptions (provider disagreement resolver)first-line (research agent with citations)reply-router (classes and routes)crm-reconcile (weekly drift report)runbook-writer (keeps the handover current)
Clay sits in the pipeline for the waterfall and the volume work. n8n carries the glue where a cron and a webhook are the right tool; postings outside the US ask for n8n in 42% of cases, inside the US in 28%.
Where to start if you build it yourself
- Write the ICP as rules with weights in one file. Make Claude explain a score before you trust it.
- Pick one signal (hiring is the cleanest) and one sequencer. Ship the signal-pull skill end to end before anything else.
- Add the first-line agent with citations. Review every line for two weeks.
- Only then add enrichment exceptions, reply routing and the CRM reconcile.
- Write the runbook as you go. The handover is the product.
Straight answers
How many GTM engineers use Claude Code?
62.7%: 143 of 228 respondents in the State of GTM Engineering 2026 survey. In-house 60.2%, freelance 63.3%, agency 67.2%. Cursor sits slightly higher at 69.7%.
Do job postings ask for Claude Code?
35% of GTM engineer postings name Claude and 53% ask for LLMs or agents, while 6% of GTM engineer profiles mention Claude (OneGTM GTME Data Report Q3 2026). In Upside's role map Claude appears in 18% of outbound GTM engineer postings.
Is Claude Code a replacement for Clay?
No. Clay is asked for in 56% of postings and is the best tool for lists and enrichment at volume. Claude Code holds the logic, the agents and the glue in a repo you own. The two are built together; the question is where the logic lives.
What is a Claude Code GTM skill?
A folder with a SKILL.md and scripts that Claude Code loads when the task matches: pull a list from a signal, score an account, write a first line with sources, route a reply. Skills are files, so they are versioned, reviewed and handed over like code.
Can I get this built rather than build it?
Yes. The Closer Method builds the six workflows above as a system in your tools, at $4,500 a month for the fractional seat or $7,500 as a one-time build, and hands them over as skills you own.
Or have it built
The Closer Method builds these six workflows as one system in your tools, documents them and hands them over: $4,500 a month for the fractional founding seat, no minimum after month one, or $7,500 once. Start with the $500 written map.