CRM Adoption: 92% of GTM Engineers
CRM is the most adopted tool category in the GTM Engineer stack. 92% of practitioners use one. The Salesforce vs HubSpot split defines how GTM workflows get built at different company stages.
The One Tool Everyone Agrees On
At 92%, CRM has the highest adoption rate of any tool category for GTM Engineers. Higher than Clay (84%), higher than AI coding tools (71%), higher than everything else. That makes sense: CRM is where pipeline lives. Every outbound campaign, enrichment workflow, and sequencing tool eventually pushes data into a CRM.
But CRM adoption for GTM Engineers is different from CRM adoption for sales reps. Sales reps log calls and update deal stages. GTM Engineers treat the CRM as a data layer. They build custom objects, write API integrations, manage field mapping between Clay and the CRM, and create automated workflows that update records without human intervention.
That distinction matters for compensation. GTM Engineers who can architect CRM data models (custom objects, complex field relationships, automated workflow triggers) earn more than those who just push data in through standard integrations. CRM knowledge at the admin level is a skill multiplier.
HubSpot vs Salesforce: The Company Size Split
The split is predictable but the implications for GTM Engineers are underappreciated. HubSpot dominates at companies with fewer than 200 employees: startups, scale-ups, and agencies. Salesforce takes over above 500 employees.
The HubSpot camp
55% of surveyed GTM Engineers use HubSpot. The platform's appeal for GTM work is straightforward: native workflow automation is strong, the API is well-documented, and the free tier lets agencies spin up client instances without upfront cost.
HubSpot's Operations Hub added custom code actions and data sync features that directly serve GTM Engineering workflows. You can run JavaScript inside HubSpot workflows, which means lighter integrations don't need external automation tools. For agencies managing multiple client CRMs, HubSpot's multi-portal architecture and agency partner program create practical advantages.
The limitation: HubSpot's data model is simpler than Salesforce's. Complex multi-object relationships, custom reporting at scale, and enterprise-grade permission models hit walls that frustrate GTM Engineers working on sophisticated enrichment pipelines.
The Salesforce camp
35% of GTM Engineers use Salesforce, concentrated at companies above 500 employees. Salesforce offers the most flexible data model of any CRM: custom objects, formula fields, complex validation rules, and an API that can handle virtually any integration pattern.
For GTM Engineers, Salesforce's depth is both an asset and an obstacle. The platform can do anything, but doing it requires Salesforce-specific knowledge (Apex, Flow, SOQL) that takes months to develop. Many GTM Engineers at Salesforce companies describe their role as part GTM, part accidental Salesforce admin.
The data hygiene challenge is more acute in Salesforce environments. Years of accumulated custom fields, deprecated integrations, and inconsistent data entry create messy records that undermine enrichment accuracy. GTM Engineers in Salesforce shops often spend 20-30% of their time on data cleanup that HubSpot's simpler data model would have prevented.
The Alternatives: Pipedrive, Close, and Attio
10% of GTM Engineers use something other than HubSpot or Salesforce. Pipedrive and Close are popular among solo operators and small agencies who want CRM functionality without the complexity. Both offer clean APIs and straightforward data models.
Attio is the interesting newcomer. It's essentially a CRM built like a database, with custom objects and relationships as first-class features. Tech-forward GTM teams are experimenting with Attio because it feels more like a tool built for people who think in data structures. Adoption is under 5% but growing among exactly the kind of technical practitioners who define where the GTM stack is heading.
CRM as the Data Layer
The way GTM Engineers use CRM is evolving. Traditionally, CRM was the system of record for deals. For GTM Engineers, it's becoming the central data bus. Enrichment data from Clay flows in. Lead scores get calculated. Sequencing tools pull prospect lists out. Product usage signals from Segment or Mixpanel get appended to contact records.
This data layer model demands CRM skills that go beyond basic usage. Understanding custom objects, managing field types for clean data, building automated workflows that trigger on data changes, and writing API integrations that keep everything in sync. These skills show up in compensation data: GTM Engineers with CRM admin capabilities earn 10-15% above those who treat the CRM as a black box they push data into.
For how CRM skills connect to overall compensation, see our salary by company size data. For the role CRM plays alongside Clay in the enrichment workflow, check the Clay deep-dive.
Frequently Asked Questions
Which CRM do GTM Engineers use most?
HubSpot leads at startups and mid-market companies, while Salesforce dominates enterprise. The split is roughly 55% HubSpot, 35% Salesforce, and 10% alternatives like Pipedrive, Close, and Attio among surveyed GTM Engineers. The choice is usually inherited from the sales team rather than selected by the GTM Engineer.
Do GTM Engineers need CRM experience?
92% of GTM Engineers use a CRM daily, making it the highest-adoption tool category. CRM experience is expected in virtually every job posting. You don't need deep admin skills, but understanding data models, custom fields, workflows, and API access is essential for connecting enrichment and sequencing tools.
Is HubSpot or Salesforce better for GTM Engineers?
HubSpot is easier to work with for automation and has better native workflow builders. Salesforce offers more customization and handles enterprise-scale data better. GTM Engineers at startups and agencies generally prefer HubSpot. GTM Engineers at companies above 500 employees typically work in Salesforce. The best answer depends on your company's existing stack.
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.