The Stack Index / What operators run / The tools GTM engineers run, by operator count
GTM Vault · The Stack Index · operator evidence only
The tools GTM engineers run, by operator count
On the GTM Vault record, 18 operators described running 18 tools across the enrichment and resolution layer, the signal layer, the reasoning layer and the orchestration layer. Ordered by how many operators run each: Claude Code (8), Clay (7), Claude (5), ChatGPT (3), Cursor (2). The number in brackets is operators on the record, not reviews, traffic or revenue.
Updated 20 Oct 2026, the date of the latest episode or confirmation citing any tool on these layers. Cite as: GTM Vault, The Stack Index, “The tools GTM engineers run, by operator count”, https://pro.gtmvault.co/stack/most-run/gtm-engineering, updated 20 Oct 2026.
How to read this page. The order is a count, not a score. Each number is how many operators described running the tool on a GTM Vault episode or in a confirmed stack, one citation per episode, in their own words. A tool named only as displaced by something else is not counted as run. Nothing is inferred from reviews, traffic or pricing, nothing here is a recommendation, and placement in the index is not for sale.
At a glance
Every tool run by more than one operator, by count. Each row jumps to who runs it and what they built.
What these layers do
GTM engineering is the work of resolving records, reading signal, orchestrating what happens next and reasoning over all of it. These are the four layers that work sits on.
What is a GTM engineer? The definition, and the six builds on the record.
Run by more than one operator
- 1
Claude Code8
Reasoning layer. Self-serve tier. 8 operators on the record.
- Alexander Shartsis, Skyp
Orchestration environment in plan mode
- Garrett Wolfe, OneGTM
Built the Intent HQ action layer
- Jai Toor, DeepLine
Runs the niche signal discovery skill end to end
- Tim Scheuer, Oxygen
Executes scrape, enrich, personalise and launch from prompts
- Angelo Quiambao, Intellistack
Terminal layer the agent infrastructure is built and run from
- Michael Bartimer, Clarify
Analysis behind the PQL agent spec
- Joseph Lee, Supademo
Internal prototyping and builds
- Riley Timmins, Kintsugi
Built the custom ad manager and the landing pages; named it as fast and cheap for animations
- 2
Clay7
Enrichment and Resolution layer. Mid-market tier. 7 operators on the record.
- Vinayak Mishra, Graphmain
Master data layer, three tables
- Garrett Wolfe, OneGTM
Account scoring and enrichment waterfall
- Umar Farooq Adam, Hitachi Vantara
Account research and enrichment
- Tim Scheuer, Oxygen
Campaign build layer, later replaced by CLI orchestration
- Elliot O'Connor, Frontier
Data and workflows behind the extension's one-click actions
- Charles Cormier, TopLeads
Enrichment and list automation
- Michael Saruggia, Clay Operator
Core of the GTM engineer stack
- 3
Claude5
Reasoning layer. Self-serve tier. 5 operators on the record.
- Vinayak Mishra, Graphmain
True or false relevance check on negative reviews, with reasoning
- Jason Patel, Open Forge AI
Assistant surface where visibility is tracked
- Gorish Aggarwal, Sybill
Agent surface with MCP connector
- Riley Timmins, Kintsugi
Creative edit step in the ad manager: an ad is sent to the Claude design surface before launch
- Sean Ellis, Hacking Growth
Part of his daily working AI use alongside ChatGPT and Lovable
- 4
ChatGPT3
Reasoning layer. Self-serve tier. 3 operators on the record.
- Jason Patel, Open Forge AI
Generative engine optimised for
- Michele Shepard, Emburse
Enterprise ChatGPT holding messaging, content and roadmaps
- Sean Ellis, Hacking Growth
Part of his daily working AI use alongside Claude and Lovable
- 5
Cursor2
Reasoning layer. Self-serve tier. 2 operators on the record.
- Alexander Shartsis, Skyp
Runs Claude Code with parallel agents
- Joseph Lee, Supademo
Internal prototyping and builds
- 6
Lovable2
Reasoning layer. Self-serve tier. 2 operators on the record.
- Olivier Roth, The Swarm
Fast prototypes he shows customers and co-founders
- Sean Ellis, Hacking Growth
Builds with it as part of his daily working AI use
Run by one operator
One operator on the record each. Named here because the record holds them, not because the index ranks them lower.
These counts move with every episode
Every Show Me Your Stack episode adds operators and tools to this index. Subscribe to GTM Vault and get each one as it lands.
Common questions
- What tools do GTM engineers use?
- On the GTM Vault record, 18 operators described running 18 tools across the enrichment and resolution layer, the signal layer, the reasoning layer and the orchestration layer. Ordered by how many operators run each: Claude Code (8), Clay (7), Claude (5), ChatGPT (3), Cursor (2). The number in brackets is operators on the record, not reviews, traffic or revenue. Every count is one citation per episode, in the operator's own words, from Show Me Your Stack, the GTM Vault Podcast or a confirmed stack.
- Which tool is run by the most operators?
- Claude Code, with 8 operators on the record: Alexander Shartsis (Skyp), Garrett Wolfe (OneGTM), Jai Toor (DeepLine), Tim Scheuer (Oxygen), Angelo Quiambao (Intellistack), Michael Bartimer (Clarify), Joseph Lee (Supademo) and Riley Timmins (Kintsugi). It sits on the reasoning layer.
- What do these layers do?
- GTM engineering is the work of resolving records, reading signal, orchestrating what happens next and reasoning over all of it. These are the four layers that work sits on. Enrichment and Resolution: Waterfall enrichment, dedupe, entity matching across sources. Signal: What changed and when: intent, reviews, hiring, monitoring. Reasoning: The models and agent runtimes that score, decide, draft and build. Orchestration: What runs the sequence between systems without a human in the loop.
- Is this a ranking of the best tools?
- No. The order is the number of operators who described running the tool on a GTM Vault episode, nothing else. The index carries no score, no sponsored placement and no editorial preference. Placement is not for sale and no count is edited. Updated 20 Oct 2026.
- How many operators are behind these numbers?
- 18 distinct operators across these layers. A tool appears only once an operator described running it in a working system; tools named only as displaced by something else are not counted as run.
Also: The enrichment and data tools operators run, by operator count · The outbound tools operators run, by operator count · The AI tools operators run in their GTM stack, by operator count · Compare two tools: Clay vs ZoomInfo · Apollo vs ZoomInfo · Clay vs Apollo · All layers