Hire a GTM engineer, buy the system, or run it from the terminal.
The title is two years old and the job postings have doubled. Before you open a req, here is what the role actually builds, the three ways to get it, and what each one costs when it goes wrong.
By Daria Dovzhikova · September 2026
The short version
- A GTM engineer builds six things: the list, enrichment, scoring, drafts, a human review step, and delivery with logging. The review step is the product.
- Hire when the motion is core and continuous. Use an agency when you need it run for you. Buy a build when you want to own it and have someone to operate it.
- The workbench is optional. Outbound is starting to run from a coding agent against the APIs, and the people best at it were SDRs first.
- Whatever you choose, ask one question first: whose accounts does this run in on the day the engagement ends.
What a GTM engineer actually builds
The definition page covers the role, the skills and the salary. This page is for the person with budget. Strip the tooling talk away and every GTM engineer builds the same six-step pipeline. The tools change; the steps do not.
| Step | What it is |
|---|---|
| The list | Who you are allowed to contact, from what source, refreshed how often. Most broken outbound is broken here, before any tool is opened. |
| Enrichment | Firmographics, tech stack, hiring, funding, product events. Joined into one table with the duplicates removed. |
| Scoring | A rule or a model that says which rows deserve a message this week. Written down, so it can be argued with. |
| Drafts | First-pass messages from the enriched row. Generated, never sent as generated. |
| Human review | A person approves, edits, or kills each draft. The review step is the product; skip it and you have built a spam cannon. |
| Delivery and logging | Sends through your own domains and sequencer, every touch written back to the CRM so the next person can see it. |
Notice where the value sits. Steps one and five are judgment. Steps two, three, four and six are plumbing. Most of the market sells the plumbing and calls it a GTM engineer.
Three ways to get one
| Option | Cost | Time to first pipeline | Who owns it | Failure mode |
|---|---|---|---|---|
| Hire full-time | Base salary commonly $100K to $180K in US postings, more with equity; add tools and data. | Two to four months: hiring, then building. | You do. The knowledge sits in one head. | The seat is filled before there is a system to run. The hire builds tooling nobody asked for, or leaves and takes the logic with them. |
| Agency or fractional | Published agency guides put retainers at about $3,000 to $12,000 a month depending on scope; hourly builders less, with no ownership of results. | Two to six weeks if the list and the offer already exist. | Often the agency. Ask where the tables live and who holds the API keys. | The engagement ends and the pipeline stops, because the system lived in the agency's accounts. |
| Buy a built system | A fixed price for the build, then your own tool and data costs. Here, a signal-scored pipeline is one of the two experiment cards in a four-week Growth Pilot ($5,000). | Four weeks to a running pipeline measured on qualified conversations per month. | You do, from day one. Built on your accounts and your infrastructure. | Nobody on your side is named to review drafts and act on replies each week. A system with no operator decays in a month. |
The salary figures come from Apollo's 2026 read of US postings, which also counts the postings themselves: from over 1,400 in mid-2025 to more than 3,000 by January 2026. Check current postings for your own market before you budget; the title is young and the spread is wide.
When the hire is wrong. Before there is a list that converts by hand and an offer that has closed ten times, a full-time engineer automates a guess. The seat gets filled, the tooling gets built, and the pipeline stays empty, because the problem was never the plumbing.
When the agency is wrong. When the tables, the sequencer and the domains live in the agency's accounts. The retainer ends, the pipeline ends, and the six months of tuning leave with them. Ask where the API keys live before you sign.
When the build is wrong. When nobody on your side is named to sit in the review step every week. A built system is a set of habits with software around it. Without the operator it produces drafts nobody sends and replies nobody answers. This is why every engagement here names that person before it starts; the build is one of the two experiment cards in the Growth Pilot, four weeks on your own infrastructure, measured on qualified conversations per month.
GTM from the terminal
The workbench was the whole story for two years: Clay tables, enrichment waterfalls, a sequencer on the end. That is changing. The people I follow who build these systems now describe running them from a coding agent against the provider APIs, with the table replaced by a repository. Michel Lieben put it in one line in September: "You can run an entire cold email campaign inside claude code without ever opening clay".
I have watched the same shift happen for marketing. Origin, the open-source release loop I run on my own product, is the same idea: a release tag opens a reviewable marketing pull request, the agents draft, a person merges. The pattern is not "the agent does outbound". The pattern is that the system is code, lives in your repository, and the human review step is a pull request instead of a spreadsheet column. That is a better place for step five to live, because it leaves a diff.
Two consequences if you are hiring. First, the skill you are buying is less "knows the tool" and more "can specify a pipeline and read its output". Second, ownership gets simpler: a repository in your GitHub organisation is yours in a way a table in someone else's workspace never was.
The backlash is already here
Cheap automation has a cost, and the receiving end is starting to write about it. Ernie Smith's piece on iLands, a platform whose agents email strangers offering research work for about $25, ran on Tedium in September and drew 127 points and 56 comments on Hacker News. His line: "These agents are not trying to make money for their creators. These agents are hustling to keep their own lights on." Over a dozen emails in three hours, no unsubscribe, aimed at freelancers.
That is what steps one and five look like when they are missing. No list discipline, no human review, and the send button wired straight to a model. Every buyer of GTM engineering should read that piece before the kickoff, because the same pipeline that books meetings at ten sends a day is a reputation fire at a thousand.
Who to hire, if you hire
A thread on r/gtmengineering this month came from someone who spent five years in manual B2B outbound before moving into GTM engineering, and the argument in it holds up: former SDRs make the best automation builders because they know which step actually breaks. They have watched a good list die to a bad first line, and a good first line die to a list nobody cleaned. Someone who has only ever built the plumbing optimises the plumbing.
The same subreddit is asking what happens to GTM jobs in the next three to five years. My read: the volume roles go, the judgment roles stay, and the judgment roles get a terminal. If you are hiring one person, hire the judgment and teach the terminal. It goes the other way far less often.
For how this fits the rest of the stack, the agentic GTM stack page lays out the five layers, and the marketing engineer page covers the measurement side that has to exist before any of this can be judged.
Questions
How much does it cost to hire a GTM engineer?
In US postings in 2026 the base salary range is roughly $100K to $180K, with junior roles starting around $90K and senior forward-deployed roles above that. Add data and tooling, which for a serious outbound stack runs into four figures a month. Check current postings for your market; the title is young and the spread is wide.
GTM engineer vs SDR: what is the difference?
An SDR works the list by hand: research, message, follow-up, book. A GTM engineer builds the system that does the research and the first drafts, then supervises it. The best GTM engineers I have seen came from SDR work, because they know which step actually breaks. The role replaces volume dialing, not judgment.
Do I need Clay?
No. Clay is a good workbench for joining and enriching data, and most agencies build on it. But the same pipeline can be run from a coding agent against the provider APIs directly, and an increasing number of operators do exactly that. Buy Clay when your team wants a spreadsheet they can see; skip it when your team is comfortable in a terminal.
What is a GTM engineering agency, and what does it cost?
An agency designs, builds and often runs the enrichment, scoring and outbound systems so you do not add headcount. Published guides put retainers between $3,000 and $12,000 a month depending on volume and whether they operate it or just build it. The question to ask before signing: whose accounts does this run in, and what happens on the day the retainer ends.
Should a seed-stage developer-tool company hire a GTM engineer?
Usually not yet. Before there is a repeatable offer and a list that converts by hand, an automated system multiplies a guess. Get ten conversations the manual way, write down what worked, then build the system around that. The build is faster and cheaper than the hire at that stage.
What is the difference between a GTM engineer and a marketing engineer?
A GTM engineer builds the execution layer of a revenue motion: lists, enrichment, sequences, agents. A marketing engineer owns the measurement and plumbing under the whole marketing stack: attribution, server-side tracking, AI and search visibility, and the demand systems. On a small team one person holds both.
Related guides
Pipeline that depends on one person?
Thirty minutes to find out whether you need a hire, a build, or neither yet.