Independent benchmark · 2026

State of GTM Engineering 2026 — Key Stats

Q: What tools do GTM Engineers actually use?

CRM (Salesforce / HubSpot) at 88.6% and Clay at 83.8% are table stakes. AI coding tools — Cursor and Claude Code — have hit 70.6% adoption with the strongest love-to-frustration ratio in the data. n8n is at 58.8%, scraping tools at 60.5%, intent-signal tools at 51.3%. Notably, Unify registers just 8.8% adoption despite positioning squarely in this market — the all-in-one outbound platform space is wide open.

Q: Why is Clay both the most-loved and most-frustrating tool?

Clay sits at 83.8% adoption (96% among agencies) and accumulates more love mentions than any other tool — but it also accumulates the most frustration mentions. The pattern reflects a genuinely powerful and genuinely complex product: workspaces sprawl, AI columns burn credits, and the specialist trap (one operator builds everything; nobody else can debug it) is common. Adoption alone is not a fit signal — the love-to-frustration ratio matters more.

Q: What are GTM Engineers asking for that does not exist yet?

The #1 most-requested tool by GTM Engineers is an "all-in-one outbound platform" (28 mentions in free text) — a consolidation play that no current vendor has captured. Second is "better / more data tool" (25), then better reporting (11), global RevOps / tool visibility (9), AI SDR (6), and text-to-outbound (6). The market signal: GTM operators are tired of stitching point tools and want consolidation, not more sprawl.

Q: Is GTM Engineering really growing 5,205% YoY?

Yes — per the Sentrion job-postings dataset cited in the report (230+ job boards, six years of data), GTME job postings went from 63 in 2024 to 3,342 in 2025, a 5,205% YoY increase. December 2025 alone hit 624 postings — roughly 10x the January baseline. The role moved from "few hundred true GTM Engineers globally" framing to mainstream demand inside a single year.

Q: How does StackSwap relate to the State of GTME data?

The State of GTME 2026 documents the role and the patterns. StackSwap is the decision engine for the operators in it. 71% of GTMEs do "tool evaluation / stack architecture" as part of the job, and the #1 unmet tool need is consolidation. StackScan applies a consistent keep / replace / remove rubric to your stack in 60 seconds — the same assessment an experienced RevOps lead would do, except quantified, repeatable, and free.

The State of GTM Engineering 2026, published by OneGTM LLC, is the first independent benchmark for the role: 228 GTM Engineers across 32 countries surveyed in Q4 2025 – Q1 2026. This page distills the numbers most relevant to anyone making stack decisions, hiring decisions, or agency-vs.-in-house calls in 2026 — with attribution back to the source on every data point.

TL;DR

71% of GTM Engineers do “tool evaluation / stack architecture” as part of the role — stack design is a first-class workflow, not an annual procurement event.
Clay sits at 83.8% adoption — and is simultaneously the most-loved AND most-polarizing tool in the data. Adoption alone is not a fit signal.
The #1 wished-for tool is an all-in-one outbound platform (28 mentions). Unify, the obvious incumbent for that pitch, has just 8.8% adoption. The category is wide open.
Job postings grew 5,205% YoY in 2025 (63 → 3,342 listings). December alone hit 624 — 10x the January baseline.
67% of in-house GTMEs hold zero or negligible equity, including 70%+ at Seed and Series B. The pay floor is too low; the equity floor is lower.
25% cite bandwidth as their #1 bottleneck — not budget (3%). The blocker is capacity, not spend.

Independent benchmark · 2026

What 228 GTM Engineers actually said

The first independent compensation, tooling, and org-design benchmark for GTM Engineering. Survey of 228 respondents across 32 countries. Five numbers worth keeping next to your stack decisions:

71%
of GTM Engineers do tool evaluation / stack architecture as part of the role
Stack design is a first-class workflow for the operators building modern revenue systems — not an annual procurement event.
n=228 across 32 countries
84%
use Clay — and it is also the most-frustrating tool in the stack
Clay is the #1 most-loved AND most-polarizing tool. Adoption alone is not a fit signal — the love-to-frustration ratio matters more.
#1
tool GTM Engineers wish existed: an all-in-one outbound platform (28 mentions)
Despite hundreds of point tools, the top unmet need is consolidation. Unify registers just 8.8% adoption. The platform space is wide open.
5,205%
YoY growth in GTM Engineering job postings (63 → 3,342 in 2025)
GTM Engineering went from niche to mainstream demand in twelve months. The category has hit escape velocity.
Per Sentrion, 230+ job boards, 6 years
25%
of GTMEs cite bandwidth as their #1 bottleneck — not budget (3%)
Modern GTM teams are blocked by capacity, not spend. Decisions that buy back time beat decisions that cut cost.

Source: The State of GTM Engineering 2026 · OneGTM LLC · stateofgtme.com. StackSwap analysis at /state-of-gtm-engineering-2026-stats.

Compensation

Self-reported base salary medians by cohort. Note that 21 respondents declined to share salary, and several high-profile employers opted out (see methodology notes below) — these figures likely sit slightly below true market rate.

Cohort	Median base	n	Context
US in-house GTME	$135K	61	Range $60K–$250K+
Non-US in-house GTME	$75K	43	~80% gap vs US
High coding proficiency (7-10/10)	$135K	41	+$45K vs low coders
Mid coding (4-6)	$105K	39
Low coding (1-3)	$90K	27
Series D+ in-house	$145K	7
Series B in-house	$145K	15
Pre-Seed/Seed in-house	$85K	15
4+ years GTME experience	$135K	9
<1 year GTME experience	$105K	27
Posted job listings (Clay job board)	$140K avg / $160K max	224

Equity

67% of in-house GTM Engineers hold zero or negligible (<0.10%) equity. At Seed and Series B — the stages where GTM systems are being built from the ground up — 70%+ carry near-zero equity. Only at Series D+ does the share with meaningful equity (>0.10%) cross 50% (71.4%). For a role this leveraged on revenue outcomes, the equity gap is a structural mismatch.

Tool adoption

% of GTM Engineers using each tool category (n=228). CRM and Clay are table stakes; AI coding tools have hit majority adoption inside a single year; the consolidation layer (Unify, AI CRMs, AI SDRs) sits in single digits despite positioning attempts.

Tool / category	Adoption	Bucket
CRM (Salesforce / HubSpot)	88.6%	Foundational
Clay	83.8%	Growth
Cursor / Claude Code	70.6%	AI
ZoomInfo / Apollo / Outreach / Salesloft	65.4%	Foundational
Scraping (Phantombuster, Apify, Captain Data)	60.5%	Growth
n8n	58.8%	Growth
Intent signal tools (Common Room, RB2B, Warmly, Vector, 6sense)	51.3%	Growth
Homemade scraping tools	44.7%	Growth
Zapier	42.5%	Foundational
Looker / Tableau / Redash	16.2%	Foundational
Unify	8.8%	Niche
AI SDRs (11x, AISDR)	6.1%	AI
AI CRM (Attio, Clarify, Day AI, Lightfield)	3.5%	AI
Rox	2.6%	Niche

Tool sentiment — love vs. frustration

From free-text mention counts. Clay is the most-loved AND most-polarizing tool in the dataset. Cursor / Claude Code have the strongest love-to-frustration ratio — a signal the AI coding wedge is mature in this audience.

Tool	Love mentions	Frustration mentions	Ratio
Clay	150	28	5.4×
Claude / Cursor	70	3	23.3×
n8n	38	5	7.6×
HubSpot	30	12	2.5×
Salesforce	18	18	1.0×
Apollo	28	8	3.5×
ZoomInfo	12	14	0.9×
Make	12	4	3.0×
Zapier	14	4	3.5×
Instantly	14	3	4.7×
Smartlead	10	3	3.3×
Heyreach	8	2	4.0×

Why GTMEs love (and hate) their tools

Why love

AI capabilities	44.3%
Automation power	23.7%
Flexibility / customization	14.9%
Data enrichment	11.8%
Speed / efficiency	7%
Easy to use	6.6%
Cost effective	5.3%

Why frustrate

Poor integration / closed ecosystems	13.6%
Clunky / hard to use	8.8%
Poor support / documentation	7.9%
Expensive / overpriced	6.1%
Slow / buggy	4.4%
Lack of customization	3.9%
Bad data quality	2.2%

Workflow breadth — what GTMEs actually do

% of respondents reporting each workflow as part of their role (multi-select). The top five all exceed 70%. The role is broad by default.

Workflow	% of respondents
Lead generation / outbound	91%
Data pipelines / enrichment / integration	79%
Sales ops / CRM admin	72%
Tool evaluation / stack architecture	71%
Marketing automation / workflows	70%
Inbound lead handling	64%
Growth experimentation / A/B testing	64%
Dashboarding and reporting	60%
Forecasting / attribution / revenue metrics	42%
Customer success / retention / expansion	41%

Tools they wish existed

From open-ended free-text responses to “What tool do you wish existed?” The #1 unmet need is platform consolidation — an all-in-one outbound tool. The #2 is better data quality. Together they tell the same story: GTM Engineers are tired of stitching point tools.

Wished-for tool	Mentions
All-in-one outbound tool	28
Better / more data tool	25
Better reporting	11
Global RevOps / tool visibility	9
AI SDR	6
Text-to-outbound tool	6
Better A/B testing	5
Documentation & enablement tools	5
LinkedIn inbox	5
AI CRM	4

Most exciting new tools

From “What new tool are you most excited about?” AI-native tools dominate.

Tool	Mentions
Claude / Claude Code	39
Clay (new features)	19
Cursor	11
n8n	8
Octave	7
Sumble	4

The job market — 5,205% YoY growth

Per the Sentrion dataset (230+ job boards, 6 years), GTM Engineering postings exploded from 63 in 2024 to 3,342 in 2025 — a 5205% YoY increase. December alone hit 624 postings vs. 58 in January.

Top technologies in GTME job descriptions (% of postings mentioning):

Technology	% of postings
Clay	49.7%
HubSpot	45%
Salesforce	37.6%
Zapier	25.6%
Instantly	24.3%
Python	23.7%
SQL	23%
n8n	22%

Where GTMEs report

Reporting line is genuinely fragmented. The role is owned at the top (38% of respondents report into C-Suite or run as a standalone) more often than it sits inside a traditional revenue function.

Reports to	Count	%
C-Suite	72	32%
Standalone	47	21%
RevOps	42	18%
Marketing	34	15%
Sales	33	14%

Bottlenecks — bandwidth, not budget

The single most-cited bottleneck is capacity, not cost. Tooling and people problems outweigh budget problems by an order of magnitude.

Bottleneck	% of respondents
Bandwidth / capacity	26.3%
Tool complexity	16.2%
Client management	11%
Internal buy-in	6.6%
Market change speed	5.7%
Hiring / solo work	4.8%
Cross-functional alignment	4.4%
CRM / tech debt	3.5%
Budget constraints	2.6%
Data quality	1.8%

Agency / freelancer pricing

Agency engagements range widely — $1K–$33K/mo — reflecting genuinely different services bundled under the same label. Median minimum monthly fee: $5K; median max: $8K. Most engagements run 3–6 months; nearly half of operators serve fewer than 5 clients at a time.

What GTMEs predict for the next 3-5 years

Themed analysis of free-text responses to “Where is the role headed?”

Theme	% of respondents
General AI / automation	36%
More technical / coding	34.6%
RevOps convergence	9.6%
AI agents / agentic	9.2%
Tool consolidation	6.6%
Orchestration / system design	6.1%
Personalization at scale	5.3%

FAQ

The State of GTM Engineering 2026 is the first independent benchmark report on compensation, tooling, org design, and the lived reality of GTM Engineering. Published by OneGTM LLC (Garrett Wolfe, Alex Lindahl, Maja Voje) based on a survey of 228 GTM Engineers across 32 countries, collected Q4 2025 – Q1 2026. The full report is at https://stateofgtme.com.

A hybrid operator who designs and ships the technical infrastructure of a revenue org — part sales strategist, part RevOps architect, part automation builder, part systems thinker. The State of GTME 2026 found that 71% of GTM Engineers work on tool evaluation and stack architecture as a core part of the role, and 91% work on lead generation / outbound. The function reports into C-Suite (32%), runs as a standalone (21%), or sits inside RevOps (18%), Marketing (15%), or Sales (14%).

Per the 228-respondent survey: US in-house GTM Engineers earn a $135K median base (range $60K–$250K+, n=61). Non-US peers sit at $75K median (n=43). Coding proficiency drives a meaningful premium — high-coding GTMEs ($135K, n=41) earn $45K more than low-coding peers ($90K, n=27). 67% of in-house GTMEs hold zero or negligible (<0.10%) equity. Note: several major employers (Clay, Linear, Descope, Apollo, Ramp, others) declined to share comp data, which likely depresses these figures.

CRM (Salesforce / HubSpot) at 88.6% and Clay at 83.8% are table stakes. AI coding tools — Cursor and Claude Code — have hit 70.6% adoption with the strongest love-to-frustration ratio in the data. n8n is at 58.8%, scraping tools at 60.5%, intent-signal tools at 51.3%. Notably, Unify registers just 8.8% adoption despite positioning squarely in this market — the all-in-one outbound platform space is wide open.

Clay sits at 83.8% adoption (96% among agencies) and accumulates more love mentions than any other tool — but it also accumulates the most frustration mentions. The pattern reflects a genuinely powerful and genuinely complex product: workspaces sprawl, AI columns burn credits, and the specialist trap (one operator builds everything; nobody else can debug it) is common. Adoption alone is not a fit signal — the love-to-frustration ratio matters more.

The #1 most-requested tool by GTM Engineers is an "all-in-one outbound platform" (28 mentions in free text) — a consolidation play that no current vendor has captured. Second is "better / more data tool" (25), then better reporting (11), global RevOps / tool visibility (9), AI SDR (6), and text-to-outbound (6). The market signal: GTM operators are tired of stitching point tools and want consolidation, not more sprawl.

Yes — per the Sentrion job-postings dataset cited in the report (230+ job boards, six years of data), GTME job postings went from 63 in 2024 to 3,342 in 2025, a 5,205% YoY increase. December 2025 alone hit 624 postings — roughly 10x the January baseline. The role moved from "few hundred true GTM Engineers globally" framing to mainstream demand inside a single year.

The State of GTME 2026 documents the role and the patterns. StackSwap is the decision engine for the operators in it. 71% of GTMEs do "tool evaluation / stack architecture" as part of the job, and the #1 unmet tool need is consolidation. StackScan applies a consistent keep / replace / remove rubric to your stack in 60 seconds — the same assessment an experienced RevOps lead would do, except quantified, repeatable, and free.

Methodology & caveats

The report variously cites "220+", "225+", and "228" respondents in different sections. The underlying survey count is 228.
23 respondents declined salary, 20 declined equity, and 70 declined bonus details. Comp medians may be biased low.
Several high-profile GTM organizations declined to share comp data: Clay, Linear, Descope, Starbridge, Primary Venture Partners, Extend, Windmill, SurveyMonkey, Apollo, and Ramp. Their absence likely depresses reported figures.
The "Posted Pay Range" data uses ~894 listings from Clay's job board (a different population from the 228 survey respondents).
Only 7 respondents (4%) reported 4+ years of GTME experience — the "senior" cohort is statistically thin.

State of GTM Engineering 2026 — Key Stats

Compensation

Equity

Tool adoption

Tool sentiment — love vs. frustration

Why GTMEs love (and hate) their tools

Workflow breadth — what GTMEs actually do

Tools they wish existed

Most exciting new tools

The job market — 5,205% YoY growth

Where GTMEs report

Bottlenecks — bandwidth, not budget

Agency / freelancer pricing

What GTMEs predict for the next 3-5 years

FAQ

What is the State of GTM Engineering 2026 report?

Who is a GTM Engineer?

How much do GTM Engineers earn?

What tools do GTM Engineers actually use?

Why is Clay both the most-loved and most-frustrating tool?

What are GTM Engineers asking for that does not exist yet?

Is GTM Engineering really growing 5,205% YoY?

How does StackSwap relate to the State of GTME data?

Methodology & caveats

Related reading