What a GTM engineer builds with it, real examples with sources, what you should see in month one, and the guardrails to set first.
A GTM engineer uses Claude Code to build revenue workflows from plain-language instructions: inbound routing, CRM updates, outbound audiences, and ad copy at volume. 62.7% of GTM engineers surveyed use it (State of GTME 2026). In month one, expect working workflows, a written context file, and human review.
Claude Code is Anthropic’s agentic coding tool. It reads and edits files, runs commands, and connects to outside tools. A GTM engineer uses it to build the scripts, workflows, and small apps that used to need a developer, and to change them in minutes when your process changes.
It’s already standard kit for the role. In the State of GTME 2026 survey, 143 of 228 GTM engineers (62.7%) use Claude Code. Cargo found Claude or Claude Code named in 38% of GTM engineer job posts in the most recent month it tracked, and some form of AI in 70%.
Four features from Anthropic’s documentation matter most to a revenue leader, in our view:
Claude Code comes with every paid Claude plan. A Team standard seat is $20 a month billed annually or $25 monthly, and a Team premium seat is $100 or $125, per Anthropic’s pricing page on October 29, 2026. The Free plan doesn’t include it.
These come from Clay’s and Anthropic’s own teams. Both companies sell the tools involved, and the results are self-reported, so treat them as examples of what’s possible.
| Your team’s problem | What was built with Claude Code | Who, and the reported result |
|---|---|---|
| Inbound leads wait while someone builds the routing | Claude Code read a customer’s written description of their inbound flow and built a workflow with a suppression gate, Salesforce lookups, enrichment, ICP scoring, and assignment | Carolyn Ann Jones, Forward Deployed GTM Engineer at Clay. Built in minutes. She estimates a manual build would take days. |
| Workflows fail and nobody notices | A plain-language status check on Clay’s deal-routing workflow | Matthew Quan, Product at Clay. It found 4 failures in 196 runs. |
| Reps build outbound lists by hand | An audience of accounts in one stage of the sales process, the most technical contact at each, and a two-email sequence, all from one spoken request | Matthew Quan at Clay. The audience and campaign landed in Clay with a preview link. |
| Event follow-up waits on someone to load the attendee list | A workflow that takes attendees from a segment or an uploaded CSV and enrolls them in an outbound campaign | Chris Viglietta, GTM Engineering Workshops Lead at Clay. Two entry triggers, with personalized drafts waiting in Clay’s Sequencer when the event ends. |
| Paid search copy takes days | A /rsa command that checks campaign data, existing copy, and keywords against skills for brand voice, product accuracy, and Google Ads best practices, then outputs an upload-ready CSV with 15 headlines and 4 descriptions per ad | Austin Lau, growth marketer at Anthropic. 30 minutes per ad down to 30 seconds. Each CSV goes through manual review before upload. |
| Ad creative needs dozens of sizes | A Figma plugin, built in 45 to 60 minutes, that turns headline copy from a Google Sheet into dozens of ad variants | Austin Lau at Anthropic. Saves nearly 30 minutes each time he updates a large batch. |
| Hundreds of ads go stale | A workflow that reads CSVs of hundreds of ads, flags underperformers, and writes new variations within character limits, using two sub-agents | Anthropic’s Growth Marketing team. Hundreds of new ads in minutes instead of hours. |
One detail a hiring manager should notice: Anthropic says Austin Lau had never written code before this work. Building got easier. Your hire still has to pick what’s worth building.
No study tracks a GTM engineer’s first month with Claude Code, so this is our recommendation. Hold your hire to something close to it.
| Week | What you should see | What to ask |
|---|---|---|
| 1 | Read-only access to the CRM and Clay. A written context file with your ICP, offers, CRM field definitions, and words to avoid. A list of manual work, ranked by hours per week. | "Which three manual jobs cost us the most hours?" |
| 2 | The first workflow live on a small segment, with a person approving anything that reaches a customer | "Show me it running, and show me a row it got wrong." |
| 3 | A second workflow, plus a health check that reports failed runs, like the one that found 4 failures in 196 at Clay | "How many runs failed this week, and why?" |
| 4 | A handoff doc for each workflow, its cost per run, and one before-and-after number | "What number moved, and what should we build next?" |
By day 30 you should be able to open every workflow, see who approved what, and run it without the engineer in the room. If you can’t, the work lives in one person’s head.
An agent that can write to your CRM can also break it at scale. Set these on day one.
When Claude Code is the wrong call: if nobody else on your team can read or run what it builds, every workflow becomes a single point of failure. A team that lives in Clay’s interface can keep building there and use Claude Code for one-off jobs. And if your process changes every week, there’s nothing stable to automate yet.
Cargo suggests a short conversation about whether the candidate uses Claude Code or Codex every day, and looking for a system that’s still running with a version history. Three checks you can run in any interview:
Our GTM engineer interview questions cover AI in production in more depth, and GTM engineer skills sets the coding bar for reviewing what an AI agent writes.
We recruit, vet, and pay Marketing Engineers, who build GTM systems inside your team: Clay tables, n8n workflows, and CRM routing. We vet them on a 16-tool stack that includes Claude, Codex, Cursor, Clay, Make, and n8n, and GrowthPair University adds 6 courses and 43 lessons across 13 AI tools. Every candidate goes through five steps: a resume screen, a phone interview, a proctored skills assessment, a live interview with a marketer, and your interview. 1.5% of applicants are accepted, and every one passes a C1 English test. A full-time hire costs about $4,000 a month, all-in, covering the marketer’s pay, payroll, benefits, and HR. For the rest of the stack they’ll run, see the GTM engineer tech stack.
To build and change revenue workflows from plain-language instructions: inbound enrichment and routing, workflow health checks, outbound audiences and sequences, and ad copy at volume. Clay’s and Anthropic’s teams have published examples of each.
They work together. Clay’s Agent Plugin connects Clay’s API, CLI, MCP, and skills to Claude Code, so a GTM engineer can build Clay workflows from a prompt and review them in Clay. Of the 228 GTM engineers in State of GTME 2026, 83.8% use Clay and 62.7% use Claude Code.
It comes with paid Claude plans. A Team standard seat is $20 a month billed annually or $25 monthly. Pro is $17 a month billed annually or $20 monthly. The Free plan doesn’t include it.
Yes, through HubSpot’s remote MCP server, which can read, write, and update contacts, companies, deals, and tickets. It signs in with OAuth and acts as the signed-in user, so set that user’s permissions first.
A written context file in week one, a first workflow live on a small segment by week two, a health check on failed runs by week three, and a handoff doc with a cost per run and one before-and-after number by week four.
With guardrails, yes. Start read-only, add write access one object at a time, keep a person approving anything customer-facing, and test changes on historical data before they go live.
