GTM Tool Adoption: Which Tools Are Winning
228 GTM Engineers told us what they use, what they love, and what drives them crazy. Here's where the market stands.
Clay Runs the Table
69% of GTM Engineers use Clay. That's adoption, not just awareness. Seven out of ten practitioners run Clay as part of their daily workflow. According to Clay's own data, the platform processes billions of enrichment data points monthly, and GTM Engineers represent their fastest-growing user segment.
Clay's dominance makes sense when you understand what GTM Engineers do. The role is fundamentally about data orchestration: pulling from multiple sources, enriching, scoring, and routing. Clay was built for this workflow. It's not the cheapest option, and it's not the simplest. But it handles the complex multi-waterfall enrichment patterns that define modern GTM Engineering better than anything else on the market.
The frustration data is equally revealing. Clay tops both the "most loved" and "most frustrating" tool lists in the survey. Engineers love the flexibility and power. They hate the pricing model, the occasional data quality issues, and the steep learning curve. It's the tool you can't live without and can't stop complaining about. For the full review, see our Clay analysis.
The Enrichment Layer
Data enrichment is the core workflow. Beyond Clay, the enrichment market includes Apollo (used by 40% of respondents), ZoomInfo (18%), Clearbit (12%), FullEnrich (8%), and Lusha (6%).
Apollo occupies an interesting position. It's both a data provider and an outbound sequencing tool, which makes it a partial substitute for Clay + Instantly/Smartlead. For GTM Engineers at smaller companies with limited budgets, Apollo's all-in-one approach is appealing. But most survey respondents who use Apollo also use Clay. The two tools complement more than they compete. For the direct comparison, see Clay vs Apollo.
ZoomInfo's 18% adoption is lower than its enterprise market share would suggest. GTM Engineers skew toward startups and mid-size companies where ZoomInfo's pricing ($15K-$30K/year minimum) is prohibitive. Engineers at enterprise companies that already have ZoomInfo contracts use it. Everyone else doesn't.
FullEnrich and Lusha are growing, particularly among cost-conscious teams. FullEnrich's waterfall approach (checking multiple data providers sequentially for the best result) clicks with GTM Engineers who understand data quality variance across providers.
The Outbound Sequencing Battle
Outbound email sequencing is the second most critical tool category. The market is split between Instantly (28% adoption), Smartlead (19%), Outreach (15%), and Salesloft (12%).
Instantly and Smartlead dominate the startup and mid-market segments. Both tools focus on high-volume cold email with inbox rotation, warm-up, and deliverability management. Instantly leads on ease of use. Smartlead leads on pricing and volume capabilities. The choice between them often comes down to personal preference and team size.
Outreach and Salesloft serve the enterprise segment. They're more expensive, more complex, and tightly integrated with Salesforce. GTM Engineers at enterprise companies typically use one of these two. The outbound sequencing category page covers the full market.
Lemlist, HeyReach, and Woodpecker each hold 3-7% market share. Lemlist's strength is LinkedIn integration. HeyReach focuses specifically on LinkedIn outreach automation. Woodpecker appeals to agencies with its white-label capabilities.
CRM: HubSpot vs Salesforce
The CRM split mirrors company size. HubSpot dominates among startups and mid-market companies (used by 42% of respondents). Salesforce dominates enterprise (used by 35%). The remaining 23% use alternatives like Pipedrive, Close, or Attio, or have no CRM at all (agency GTM Engineers often use client CRMs rather than maintaining their own).
GTM Engineers generally prefer HubSpot. The API is cleaner, the workflow builder is more intuitive, and the free tier makes it accessible for early-stage companies. Salesforce's advantages (customization depth, AppExchange ecosystem, enterprise reporting) matter more to RevOps teams than to GTM Engineers.
Attio deserves a mention. With 4% adoption and growing, Attio is the CRM that GTM Engineers build with, not just configure. Its flexible data model and API-first architecture appeal to the builder mindset that defines the role. Watch this space.
Workflow Automation
Make (formerly Integromat) leads workflow automation at 31% adoption. Zapier follows at 24%. n8n holds 11%. The remaining engineers either write custom code or use built-in tool integrations.
Make's dominance among GTM Engineers is notable. In the broader market, Zapier has higher overall market share. But GTM Engineers prefer Make for its visual workflow builder, better error handling, and lower cost at high volumes. A Make Pro plan handles the workflow volume that would cost 3-4x on Zapier.
n8n's 11% share is concentrated among the most technical practitioners. n8n is self-hosted, open-source, and infinitely customizable. Engineers who prefer n8n tend to also write Python and manage their own infrastructure. It's the Linux of workflow automation: powerful, flexible, and not for everyone.
The AI Layer
AI tools are integrated into GTM workflows, not used standalone. 71% of respondents use AI coding assistants (Claude, GitHub Copilot, or ChatGPT) for writing enrichment scripts, debugging API integrations, and generating outbound copy. These tools augment the engineer's work rather than replace it.
Claude and OpenAI's GPT models are the most-used LLMs for GTM automation. Engineers use them for lead scoring logic, email personalization at scale, company research summarization, and data classification. The integration pattern is consistent: LLM APIs as a step within Clay, Make, or custom pipelines, processing data as it flows through the enrichment chain.
According to G2's AI sales assistant market reports, the category grew 140% in 2025. GTM Engineers are both users and builders in this space. They use AI tools, and they build AI-powered workflows for their companies.
The Stack Problem
84% of GTM Engineers use three or more tools daily. The average stack size is 5-8 tools. The dream of a single all-in-one GTM platform remains unfulfilled. No tool handles enrichment, sequencing, CRM, workflow automation, and analytics in a single product. Clay comes closest on the enrichment side. Apollo comes closest on the all-in-one side. But neither eliminates the need for a multi-tool stack.
The all-in-one tool analysis covers why this gap persists. The short answer: the GTM Engineer workflow spans too many functions for any single vendor to cover well. Enrichment requires specialized data provider integrations. Sequencing requires deliverability infrastructure. CRM requires deep customization. Automation requires flexible logic and branching. Each category demands domain expertise that's hard to replicate as a feature within a broader platform.
Tool fatigue is real. Survey respondents cite "too many tools" as their second-biggest frustration (after data quality issues). The integration tax of maintaining 5-8 tools, keeping API keys current, managing webhook failures, and debugging data flow between systems eats into productive work time.
What's Gaining Momentum
Three trends stand out in the adoption data.
Multi-waterfall enrichment is replacing single-source. Engineers are moving away from relying on one data provider. Instead, they chain multiple providers (Clay's waterfall, FullEnrich, or custom Python scripts) to maximize coverage and accuracy. One source might have 60% coverage. Three sources chained together hit 85-90%.
LinkedIn automation is growing fast. HeyReach, Expandi, and PhantomBuster all showed adoption increases in 2025. As email deliverability becomes harder (thanks to Google and Yahoo authentication requirements), LinkedIn becomes a more important outbound channel. GTM Engineers are adding LinkedIn to their multi-channel sequences.
Custom code is eating no-code. The share of GTM Engineers writing Python increased from roughly 25% in 2024 to 30% in 2025. As workflows get more complex, no-code tools hit their limits. Engineers who can write code build faster, debug quicker, and handle edge cases that break visual workflow builders.
For the complete tool market, see the tools index. For category-specific analysis, see the data enrichment category.
Source: State of GTM Engineering Report 2026 (n=228). Salary data combines survey responses from 228 GTM Engineers across 32 countries with analysis of 3,342 job postings.