The 2026 State of GTM Engineering
Data from 228 respondents. Here is exactly what the highest earners are making, and the tools they actually use.
This newsletter is sponsored by Swan AI.
AI without context is just autocomplete with confidence. It sounds right, moves fast, and produces nothing you’d actually send.
Swan built 6 FREE skills - one for every stage of the GTM motion - that give your AI agent the methodology and context it’s missing. Works in Claude, Swan AI, or any AI agent.
Dear GTM Strategist!
It is time to revisit one of the most controversial themes in our space: GTM Engineering.
Over the last year, the discussion has been heated. Some claim the title exists because GTM tech is broken. Others argue that GTM Engineers are simply tool jockeys with more love for automation than for real business fundamentals. There are even voices suggesting the entire role is vendor hype designed to sell more software.
Despite all that, the demand keeps growing.
GTM Engineers are being hired across companies and continents, and many of them are earning serious money while building the infrastructure that powers modern revenue teams.
Even if the concept irritates you a little, it is difficult to argue with the data.
So what does the data actually say?
Together with Garrett Wolfe and Alex Lindahl, we ran the largest GTM Engineering Report to date to understand what this role really looks like in practice.
Thanks to our wonderful partners who supported the report: Rho, Wiza, Juicebox, Watt Data, and Exportly.
228 respondents
30+ countries represented
The first benchmark study of compensation, tooling, and org design for GTM Engineers.
Some highlights from the data:
US median compensation sits around $135K
72% report direct revenue impact
84% of GTM engineers use Clay
Nearly 68% hold no meaningful equity
Coding skills create a $40K compensation premium
Thank you to everyone in the community who contributed data, experience, and insights. This report would not exist without you 🙏.
I want to walk through the findings and answer the questions that keep coming up in every conversation about GTM Engineering:
How much can a GTM Engineer actually earn?
Is this role just an agency hype, a Clay trend, or is it becoming core infrastructure for in-house teams as well?
Do you really need to know how to code to get into GTM engineering?
And which tools are actually powering this new wave of revenue builders? Because I do love tools as much as you do.
Now, let’s dive into the weeds of GTM Engineering.
How Much Do GTM Engineers Actually Earn?
The first thing everyone asks about GTM Engineering is simple.
Is this a real role with real compensation, or just another fancy title for someone building outbound workflows?
The data makes one thing very clear. This is a very real role and the compensation is already significant.
Across the 228 respondents in our survey, the median base salary for in-house GTM Engineers in the United States sits at around $135K.
But the distribution is extremely wide.
At the lower end, salaries fall between $60K and $90K. These are typically junior operators focused on tooling execution, list building, and basic automation workflows.
At the top end of the market, compensation climbs well beyond $200K, especially for operators who combine technical depth with ownership of pipeline generation and revenue systems.
This spread reveals something important.
The market has not figured out how to price this role yet.
Two people with the same title can be doing completely different work. One might be managing enrichment workflows and outbound tooling. Another might be designing signal engines, building automation layers, and architecting the entire revenue data stack.
Those roles are not even remotely comparable, yet the market keeps calling both of them “GTM Engineers.”
The geographic compensation gap is equally striking.
While US-based operators report a median base salary of $135K, their non-US peers sit closer to $75K. That is a difference of roughly $60K, or an 80% premium for US talent.
Even in an increasingly remote world, location still plays a major role in compensation.
Company maturity also matters.
Mid-size companies with 201 to 1,000 employees currently pay the highest median salaries for GTM Engineers. Funding stage also influences compensation, with Series B and Series D companies leading the market at roughly $145K median base salary.
Early-stage startups tend to offer lower base salaries, with pre-seed and seed companies averaging closer to $85K, often expecting equity to compensate for the lower cash component.
Except that is not what the data actually shows.
Equity distribution across GTM Engineers is surprisingly low, even in early-stage environments. Nearly 68% of respondents report holding little or no meaningful equity, despite directly influencing pipeline generation and revenue outcomes.
In other words, companies are asking these operators to build their revenue engines without always giving them a meaningful share of the upside.
This mismatch becomes even more obvious when you look at the technical side of the role.
Because there is one factor that consistently moves operators into the highest compensation bands.
Coding. And it makes me wonder - is the next GTM system a structure of folders and GTM as a code?
Do GTM Engineers Need to Know How to Code?
The short answer is no. You can absolutely enter the field without coding skills. But you are likely to earn much more if you do know how to code.
Our data shows that technical depth has a very real impact on compensation and scope.
When we analyzed the survey responses, a clear pattern emerged. GTM Engineers fall into three broad categories based on their technical proficiency.
Low-code operators.
Mid-level technical builders.
High-code engineers.
Low-code operators typically rely on no-code platforms and workflow builders. They connect tools, manage enrichment pipelines, and run outbound programs using existing platforms. Their work focuses on configuration rather than engineering. Typical tools in this category include Clay, Zapier, Make, Airtable, and no-code CRM automation inside HubSpot or Salesforce.
These operators report a median salary of around $90K.
The next group sits somewhere in the middle. These professionals understand scripting, basic APIs, and data manipulation. They might write small pieces of code, automate tasks, or build lightweight integrations when needed. They often combine platforms like Clay or HubSpot with scripts written in Python, JavaScript, or SQL to extend what existing tools can do.
Their median compensation rises to roughly $105K.
Then there is the top tier.
High-code GTM Engineers regularly work with Python, JavaScript, SQL, and modern AI coding tools. They build custom workflows, write scripts, create data pipelines, and sometimes bypass traditional vendors entirely by building their own internal tooling. Tools in this group often include Python environments, data warehouses like Snowflake or BigQuery, and AI-assisted development tools such as Cursor or Claude Code.
This group reports a median salary closer to $135K.
That is roughly a $40K to $45K premium compared to low-code operators.
In practice, the role is splitting into two different types of operators.
Some GTM Engineers focus primarily on operating the modern sales stack. They configure tools, manage enrichment workflows, and run outbound systems using existing platforms.
Others spend most of their time building the infrastructure behind those systems. They write scripts, build custom automations, and design the data pipelines that power the go-to-market engine.
Both roles are valuable, but they require very different skill sets and experience levels.
Interestingly, the rise of AI-assisted coding is already changing the skill requirements. Tools like Cursor and Claude Code allow GTM Engineers to generate scripts, build automations, and experiment with custom workflows without needing the background of a traditional software engineer.
This does not eliminate the value of technical knowledge. If anything, it increases the leverage of operators who understand how systems work.
But the data suggests that the closer you move toward engineering, the more valuable and better compensated your role becomes.
GTM Engineering in Agencies vs In-House Teams
One of the most common questions around GTM Engineering is where this role actually belongs. Is it something companies should build internally as your core capacity - if so, where should GTME sit in an org, or is it better suited for agencies and external specialists to test the grounds?
The data suggests that both models exist and are growing quickly, but they operate very differently. A large part of the early momentum around GTM Engineering came from the agency ecosystem.
Over the past two years, a wave of specialized agencies and fractional operators started offering GTM engineering services. The barrier to entry was relatively low, demand from founders was extremely high, and the tooling ecosystem made it possible for a single operator to build fairly complex outbound infrastructure.
Our data reflects this rapid growth and the chaos that comes with it.
Monthly agency retainers range from as little as $1K to as high as $33K per month. The median minimum fee sits around $5K, while the median maximum retainer lands closer to $8K.
This is an enormous spread.
The reason is simple. Buyers and sellers are often talking about completely different services while using the exact same label.
Some agencies provide done-for-you outbound. They build lists, run enrichment, and launch campaigns.
Others operate as systems architects, designing signal engines, building data pipelines, and integrating the entire revenue stack.
These are fundamentally different services.
Yet they are both marketed as GTM Engineering.
At the same time, the role is increasingly appearing inside companies themselves.
A growing share of respondents work in-house inside revenue teams, not as consultants or agencies. These operators sit directly within marketing, RevOps, or growth teams and own the internal automation layer that connects the entire go-to-market motion.
Instead of running campaigns for multiple clients, they focus on a single company and build long-term infrastructure.
Signal monitoring.
Pipeline automation.
Data enrichment systems.
CRM architecture.
This is where the role becomes far more strategic.
In-house GTM Engineers are not just launching outbound sequences. They are designing the systems that determine how pipeline is generated, routed, enriched, and converted across the entire funnel.
Agencies often help companies get started. In-house teams are where these systems are maintained and scaled over time.
So while agencies helped popularize the category, the role itself is quickly becoming core infrastructure inside modern revenue teams.
The most mature organizations are not outsourcing this capability.
They are building it internally.
The GTM Engineering Tool Stack
If you want to understand a new role, look at the tools the operators actually use.
The GTM Engineering stack reveals a lot about how modern revenue teams are evolving.
CRM platforms remain the foundation. Salesforce and HubSpot still dominate the ecosystem, with roughly 88% adoption among respondents. Almost every GTM Engineer is building automation layers on top of one of these systems.
But the real story sits above the CRM.
Clay has quickly become the default infrastructure for this function. Across the survey, 84% of GTM Engineers report using Clay, making it the most widely adopted tool in the entire stack.
Among agencies the adoption climbs even higher, reaching 96%.
This level of dominance is rare for such a young platform.
Clay essentially acts as the connective layer between enrichment providers, data signals, outbound workflows, and automation logic. For many operators it has replaced large portions of the traditional outbound stack.
At the same time, Clay is also the most polarizing tool in the ecosystem.
Operators love the flexibility. They can combine dozens of data sources, trigger workflows based on signals, and build highly customized outbound engines.
They also complain about the complexity.
Workflows often rely on multiple APIs, fragile integrations, and complex logic chains. Running a single campaign can require stitching together several tools and enrichment providers. When one piece breaks, the entire workflow stops.
This creates a strange paradox.
Clay is the most powerful platform in the stack and also one of the most frustrating to maintain.
Meanwhile, AI-native development tools are spreading quickly across the GTM engineering community.
Tools like Cursor and Claude Code now show adoption rates approaching 70% among respondents. These tools allow operators to generate scripts, build small internal tools, scrape data, and automate workflows without relying entirely on third-party vendors.
This shift toward AI-assisted development is changing how GTM Engineers operate.
Instead of waiting for vendors to build new features, many operators simply build their own solutions.
When we asked respondents what they value most in their tools, the answers were very consistent.
44% pointed directly to AI capabilities.
Another 24% highlighted automation power and speed.
At the same time, the frustrations are equally clear.
26% complain about poor integrations and closed ecosystems.
18% struggle with clunky interfaces.
11% cite expensive platforms that deliver limited flexibility.
Despite the massive popularity of Clay and the rapid rise of AI tooling, a clear gap still exists in the market.
About 12% of respondents say they wish a true all-in-one outbound platform existed.
The demand for a unified system is obvious.
So far, no vendor has fully solved it.
For now, GTM Engineers continue to build their own stacks.
The Maturity Gap and the Hype Train
GTM Engineering might be one of the fastest-growing roles in modern revenue teams.
It is also one of the youngest.
When we analyzed the age distribution of survey respondents, the results were surprising.
Nearly 30% of GTM Engineers are between 18 and 22 years old. Another 25% fall between 23 and 26.
That means more than half of the talent pool entered the workforce only a few years ago.
This explains a lot of the confusion surrounding the role.
Many operators entering the space are extremely strong technically. They know how to use modern sales tech. They can build workflows, connect APIs, and automate data enrichment pipelines.
But deep experience with complex sales processes is still relatively rare.
That experience gap matters.
GTM Engineering sits directly at the intersection of marketing, sales, RevOps, and data infrastructure. The operators building these systems are shaping how pipeline flows through the entire organization.
When someone with limited business experience is suddenly responsible for designing revenue systems, mistakes are inevitable.
This does not mean the role is flawed.
It simply means the category is still very early.
The tooling ecosystem exploded quickly. Clay, enrichment APIs, signal platforms, and AI coding tools dramatically lowered the barrier to building automation systems. Suddenly, a single operator could do work that previously required an entire RevOps team.
Naturally, a wave of ambitious builders rushed into the space.
Some are incredibly talented. Others are still learning the fundamentals of how revenue organizations actually operate.
This creates a chaotic market.
Companies are hiring junior tool operators and expecting them to perform like senior revenue architects. Operators are experimenting aggressively without always understanding the long-term implications of the systems they are building.
The result is a wide maturity gap across the industry.
Some GTM Engineers are quietly becoming some of the most valuable operators inside modern revenue teams.
Others are still figuring out what the role actually requires.
This is exactly what early categories look like.
Messy. Fast-moving. And full of experimentation.
Where GTM Engineering Goes From Here
For all the discussion about tools, AI, and automation, the biggest constraint facing GTM Engineers is surprisingly simple.
Time.
In our survey, 25% of respondents said bandwidth is their number one bottleneck. Most GTM Engineers operate as a team of one, responsible for designing automation systems, maintaining the data layer, supporting sales workflows, and experimenting with new go-to-market infrastructure.
At the same time, many companies are still figuring out what this role actually is.
Only 45% of respondents say their organization clearly understands what a GTM Engineer does. Another large group reports only partial understanding across leadership and revenue teams.
This combination creates an interesting moment.
The tools are evolving quickly. The talent pool is growing. But the organizational structure around the role is still catching up.
The companies that figure this out early will have a real advantage.
Because modern go-to-market is becoming increasingly technical. And the operators who can connect systems, automate workflows, and build revenue infrastructure are quickly becoming some of the most valuable people inside revenue teams.
So there you have it. A snapshot of where GTM Engineering stands today, what the market pays for it, and which skills will make you indispensable in the years ahead. If you want more information, download the full The State of GTME Report here. What I shared in this article are my key takeaways, the report itself is 80-slides long - and you can get it FREE:
✅ Need ready-to-use GTM assets and AI prompts? Get the 100-Step GTM Checklist with proven website templates, sales decks, landing pages, outbound sequences, LinkedIn post frameworks, email sequences, and 20+ workshops you can immediately run with your team.
📘 New to GTM? Learn fundamentals. Get my best-selling GTM Strategist book that helped 9,500+ companies to go to market with confidence - frameworks and online course included.
📈 My latest course: AI-Powered LinkedIn Growth System teaches the exact system I use to generate 7M+ impressions a year and 70% of my B2B pipeline.
🏅 Are you in charge of GTM and responsible for leading others? Grab the GTM Masterclass (6 hours of training, end-to-end GTM explained on examples, guided workshops) to get your team up and running in no time.
🤝 Want to work together? ⏩ Check out the options and let me know how we can join forces.