A GTM engineer builds the machine that finds buyers and starts conversations with them. Revenue operations keeps the record of those conversations honest and moves them to closed-won. One works before a lead exists. The other works after it does. The two roles share an ICP, a workflow tool, and often a reporting line, which is why people call them the same job. The work, the failure modes, and the numbers each is judged on say otherwise.
Where one job ends and the other starts
Every B2B revenue motion has a moment where a company stops being a row on a list and becomes a lead in the CRM. That moment is the border.
Upstream of it, the GTM engineer decides which companies exist for the business, which ones are worth contacting this month, who at each one should hear from us, and what they hear. The output is a reply from a real buyer.
Downstream of it, RevOps decides what the reply is worth, who works it, what stage it sits in, and whether the number the CEO sees on Friday is true. The output is a pipeline that can be forecast.
The border is not always drawn where the org chart says. A useful test: whoever is on the hook when reply rates fall is the GTM engineer. Whoever is on the hook when the forecast misses is RevOps.
What a GTM engineer owns
The upstream work clusters into six kinds, covered in detail in the full article on the role.
- The list. Turning a written ICP into companies, then people, with sources beyond the usual databases when those run thin.
- Enrichment. Waterfalls across providers until each record has a verified email and the fields the play needs.
- Signals. Hiring, funding, leadership changes, technology shifts, competitor engagement. Each one turned into a trigger and a message.
- The message. Research per account, done by an agent with guardrails, written into lines a buyer would believe a person wrote. This is why GTM engineers end up shaping positioning: the system ends in copy, and copy nobody answers is a system that failed.
- Sending infrastructure. Domains, mailboxes, warm-up, placement, and the incident response when a domain lands in spam.
- Measurement. Which list, signal, and message produced replies and meetings, with experiments small enough to read and large enough to trust.
What RevOps owns
The downstream work is the system of record and everything that depends on it.
- CRM design. Objects, fields, stages, and the rules for what can move where. The design is a position on how the company sells.
- Routing. Which rep gets which lead, by territory, segment, or round robin, and how fast.
- Lifecycle definitions. What makes a lead qualified, what makes an opportunity real, what closes it. Shared vocabulary for sales, marketing, and finance.
- Forecasting. Stage probabilities, coverage ratios, and the weekly number that has to hold.
- Reporting. Dashboards that sales leaders trust enough to run a meeting from.
- Rep enablement. Sequences inside the CRM, call tooling, scheduling, and the training that gets people to use them.
Underneath all six is one job: the CRM has to stay the single source of truth. When RevOps is good, nobody notices. When it is bad, every number in the company is in dispute.
Where they overlap
Three decisions belong to both roles, and both should be in the room.
- The ICP. Written tightly enough that a list can be built from it upstream and a lead scored against it downstream.
- Account tiers. Which accounts get a person, which get a sequence, which get ads only. The tier drives both the outbound play and the routing rule.
- Tool choice. The two roles live in the same automation layer. A workflow tool one picks is a tool the other inherits.
Routing is the handoff that gets dropped most. The GTM engineer sends a reply somewhere. RevOps writes the rule that says where. Agree on who owns that rule before the first reply arrives, or it will be owned by nobody.
The stack, by category
Brands change yearly. The categories do not.
A GTM engineer's week runs in a workflow workspace, a set of company and contact data providers, enrichment and verification tools chained in a waterfall, signal feeds, website visitor identification, and the sending tools: an email sequencer and a LinkedIn tool.
A RevOps week runs in the CRM and the layer around it: a workflow automation tool, a data warehouse, a scheduling and routing tool, call and conversation tooling, and the connectors that keep the sequencer and the CRM in sync.
The overlap is the workflow workspace and the sync layer. The same table that enriches a list upstream can clean a CRM field downstream, which is why both roles end up in the same tool.
In 2026 the work on both sides is moving into AI coding agents, with the tools above called through their APIs. The GTM skills library on this site is the upstream half of that, written as installable skills.
What each is measured on
| GTM engineer | RevOps |
|---|---|
| Replies from buyers who match the ICP | Forecast accuracy |
| Meetings booked, and the reply to meeting rate | Stage conversion and pipeline coverage |
| Cost per qualified meeting | Lead response time and routing accuracy |
| List coverage: how much of the TAM is reachable | CRM completeness and duplicate rate |
| Deliverability: inbox placement by domain | Rep adoption of the system |
Read the columns together. One counts conversations created and what they cost. The other counts whether the system of record can be trusted and whether people use it. Titles vary by company. The column a person is judged on tells you which job they have.
Why it looks like one job
The tools overlap, the ICP is shared, and in a company of twenty one operator carries both lists. That operator maps a TAM in the morning and fixes a CRM workflow after lunch, and the title on their job post is whichever one the founder heard first.
It is still two jobs because the failures are different. Upstream, the system fails quietly: the list runs thin, a domain lands in spam, replies dry up over a month. Downstream, the system fails loudly: a forecast misses, two dashboards disagree, a lead sits unrouted for a week. Each kind needs someone watching for it every day. Past a certain headcount, one person cannot watch both.
Hiring for the gap you have
If leads arrive and then get lost, routed late, or forecast badly, the gap is RevOps. If the CRM is clean and nothing new arrives in it, the gap is a GTM engineer.
If the gap is upstream and the team is too small to keep a GTM engineer busy, the alternative is to run that half through a partner whose GTM engineers already have the stack built. That is the model behind our outbound service, and the skills library is the visible part of how that team works.