--- title: "GTM Engineering: What It Is, the Stack, and How to Start" description: "GTM engineering explained by a practitioner: what it is, how it differs from RevOps and sales ops, the stack, five core workflows, and how to start or hire." url: https://getaob.com/gtm-engineering --- # GTM engineering: what it is, how it works, and how to start **GTM engineering** is the practice of building the systems that find, score, and reach the right accounts, so a revenue team grows pipeline with code, data, and automation instead of only adding headcount. It covers the account list, enrichment, scoring, buying signals, outbound and inbound automation, and the CRM plumbing that ties them together. This guide is about the practice: what it is, what gets built, and how a company starts doing it. If you want the job itself (pay, skills, how to get hired), read [what is a GTM engineer](https://getaob.com/gtm-engineer) instead. By [Garrett Wolfe](https://garrettawolfe.com), founder of OneGTM, employee #9 at Unify, and author of the [State of GTME report](https://stateofgtme.com). Updated November 1, 2026. Key takeaways - GTM engineering builds the machinery a revenue team runs on. RevOps governs it, and reps use it. - Most of the work falls into five workflows: TAM and scoring, signals, enrichment waterfalls, inbound routing, and reply handling with CRM sync. - Fit and timing are different things. Keep the fit score and the signal in separate fields, and only reach out when both are there. - Start with one motion end to end, measure it, then add the next. A half-built stack across everything produces nothing. - Hire in-house for steady system work. Bring in a [GTM engineering agency](https://getaob.com/gtm-engineering-agency) to get the first systems live before the hire starts. ## What GTM engineering is For most of the last decade, a B2B company that wanted more pipeline hired more SDRs. Each rep built their own lists, guessed at timing, and wrote their own emails. GTM engineering replaces the guessing with systems: a scored account list, a feed of events that say an account might need you now, verified contacts, and sequences that fire when the two line up. The term took off in 2024 and 2025. GTM engineer job postings went from 63 in 2024 to more than 3,300 in 2025, and the live count is on the [GTM engineer jobs tracker](https://getaob.com/gtm-engineer-jobs). The [GTME Data Report](https://getaob.com/gtm-engineering-hiring-report) adds who is hiring, how many roles are remote, and where the people in the role came from. The tools caught up at the same time: [Clay and its competitors](https://getaob.com/clay-alternatives) made waterfall enrichment something an operator could run, and AI coding agents like [Claude Code](https://getaob.com/claude-code-gtm) made custom pipelines cheap to build. I did this work as employee #9 at Unify, where a growth team of two ran 40+ plays a day across 100+ sequences. Now I build the same kind of systems for other companies at OneGTM. ## GTM engineering vs. RevOps vs. sales ops | | GTM engineering | RevOps | Sales ops | | --- | --- | --- | --- | | Owns | The systems that create pipeline: data, signals, scoring, outbound and inbound automation | Process, forecasting, reporting, and CRM governance across the revenue org | Territories, quotas, comp, and rep tooling | | Typical output | A scored TAM, signal feeds, live sequences, routing, a reply bot | Clean CRM, stage definitions, dashboards, forecast | Territory plans, comp plans, rep onboarding | | Tools | Enrichment APIs or Clay, a sequencer, the CRM API, Python or TypeScript, AI models | Mostly the CRM and a BI tool | The CRM, CPQ, and comp software | | Measured by | Meetings and pipeline per signal, cost per verified contact | Forecast accuracy, data quality, cycle time | Quota attainment, ramp time | At a seed or Series A company one person often covers all three. As the team grows they split, and the GTM engineer usually reports into RevOps or growth. If your gap is the governance column, a [RevOps consultant](https://getaob.com/revops-agency) is the better first call. Need GTM engineering before you can hire for it? I build the system now, and your team keeps it when the hire starts. The call is with me directly. Talk to Garrett ## The GTM engineering stack | Layer | What it does | Common tools | What I run | | --- | --- | --- | --- | | Data sources | Companies, people, emails, phones, firmographics | Apollo, ZoomInfo, People Data Labs, LinkedIn data APIs | Several providers behind one API, picked per field | | Enrichment and orchestration | Waterfalls, AI research, scoring, scheduling | Clay, Deepline, n8n, custom code | Deepline plays and Claude Code; Clay for teams already on it | | Signals | Events that say an account may need you now | Job posting feeds, visitor ID, funding data, intent providers | Custom feeds matched to the scored TAM | | CRM | System of record for accounts, people, and activity | HubSpot, Salesforce, Attio | Whatever the client runs; Attio for OneGTM itself | | Sequencing | Cold email and LinkedIn outreach | Instantly, Smartlead, lemlist, HeyReach | Instantly for email, HeyReach for LinkedIn | | AI models | Classification, scoring, research, drafts, reply triage | OpenAI, Claude, Gemini | Cheap models for classification, stronger ones for copy and judgment | | Storage and hosting | Where the pipeline lives and runs on a schedule | Postgres, Supabase, BigQuery, Railway, Vercel | Supabase plus scheduled cloud jobs | Every category has its own comparison in the [GTM tool guides](https://getaob.com/gtm-tools). The model choices, with per-token cost math, are in [best LLM for GTM](https://getaob.com/best-llm-for-gtm). ## Five workflows GTM engineers build ### 1. TAM build and fit scoring Pull every company that could buy, from data providers, public registries, or scraped directories. Add firmographics, then have a model read each website and answer the questions that matter for your ICP (do they sell to hospitals, do they run field reps, are they PE backed). Turn the answers into a 0 to 100 fit score and sync it to the CRM so reps see it on the record. Check the distribution before anyone uses it. If most accounts land on the same score, the model is not separating anything. For one vertical SaaS client, with a TAM of about 45,000 companies, a rebuild moved the median score from 0.25 to 0.50 and left 2,001 accounts above 0.75, which is the shape you want: a clear top tier to work first. ### 2. Signal to outreach Watch for events: a new VP in your buyer seat, a job posting that describes the problem you solve, a funding round, a pricing page visit. Match each event to an account in the scored TAM, find the right person, verify their email, and drop them into a sequence written for that signal. The signal goes in its own field, separate from the fit score, because a signal fades in weeks and fit does not. The full list of signal types, and how to detect each one, is in the [buying signals guide](https://getaob.com/buying-signals). ### 3. Enrichment waterfall No single provider finds everyone. A waterfall asks the cheapest good source first and only pays the next one when the first comes back empty, then verifies every address before it is used, including catch-all domains. Track coverage and cost per verified email by provider, and reorder the waterfall when the numbers move. The providers are compared in [email finder tools](https://getaob.com/email-finder-tools) and [email verification tools](https://getaob.com/email-verification-tools). ### 4. Inbound routing A form fill gets enriched, scored, and assigned to the right rep, and the buyer books a meeting on the spot instead of waiting for a reply. Speed to lead is the whole game here, and most companies lose more pipeline in the gap between form and first touch than anywhere in outbound. Tools for this are in [lead routing tools](https://getaob.com/lead-routing-tools). ### 5. Reply handling and CRM sync Every reply gets classified (interested, not now, wrong person, out of office, unsubscribe), posted to Slack with a suggested response, and written back to the CRM with the campaign and signal that produced it. That last part is what lets you report pipeline by signal, which is how you decide what to build next. ## What a GTM engineering build looks like, week by week 1. **Week 1:** ICP written as fields a machine can check, the first TAM pulled, and the signals worth testing picked. 2. **Weeks 1 to 3:** Sending domains and mailboxes bought and warming. This runs in the background and is why outbound never starts on day one. 3. **Weeks 2 to 4:** Scoring calibrated against known customers and lost deals, waterfalls wired, signal feeds matched to the TAM. 4. **Weeks 3 to 5:** Sequences written per signal, every merge variable checked, first sends in small batches. 5. **Week 5 onward:** Weekly review of replies and meetings by signal and segment. Kill what is not working, add the next signal, and write the handoff so your team can run it. The full module list is on [how I work](https://getaob.com/how-i-work). ## How to start GTM engineering at your company 1. **Pick one motion:** Outbound to one segment, or inbound routing. Not both at once. 2. **Write the ICP as fields:** Industry, size band, region, tech, ownership. If a rule cannot be checked against data, it is a hope, not an ICP. 3. **Inventory your data:** What is in the CRM, what is missing, and what it costs to fill. The [TAM calculator](https://getaob.com/tam-calculator) prices the enrichment. 4. **Build one workflow end to end:** From account to booked meeting, with every step logged. Ugly and complete beats elegant and half-done. 5. **Guard the send path:** Most outbound failures are silent. A sequencer will happily send "Hi ," when a first name is blank, and it will not bounce or warn you. Check every variable on every enrolled lead before a campaign goes live. 6. **Measure by signal:** Positive reply rate and meetings per signal and segment, reviewed weekly. Then decide what to build next. ## Hire a GTM engineer, use an agency, or both | | Hire in-house | GTM engineering agency | Both | | --- | --- | --- | --- | | Best when | Steady system work and someone to manage it | You need systems live in weeks, or before the hire starts | An agency builds, then hands over to the hire | | Cost to know | Fully loaded salary plus tools; see the [cost calculator](https://getaob.com/calculator) and [salary data](https://getaob.com/gtm-engineer-salary) | Market range in the State of GTME report: about $2,000 to $33,000+ a month | Both, for an overlap period | | Risk | A long search, and one person who knows how everything works | Knowledge leaves with the agency unless the handoff is real | Paying twice if the overlap drags on | Openings and who is hiring are on the [GTM engineer jobs tracker](https://getaob.com/gtm-engineer-jobs). The field of agencies is compared in [best GTM engineering agencies](https://getaob.com/gtm-engineering-agencies). OneGTM's own offer is the [GTM engineering agency](https://getaob.com/gtm-engineering-agency) page. OneGTM is me plus a small team: the person who scopes the build is the person who builds it, and your team owns everything afterward. ## Learning GTM engineering You can learn this for free if you build as you go. I put together a [free GTM engineering course](https://getaob.com/gtm-engineering-course): an eight-week path with one project per week, using free tools and the guides on this site. The [GTM glossary](https://getaob.com/gtm-glossary) covers the vocabulary, and the [open-source Claude Code skills](https://getaob.com/skills) show how the send path is guarded in practice. ## GTM engineering FAQ ### What is GTM engineering? GTM engineering is the practice of building the systems that find, score, and reach the right accounts: account lists, enrichment, fit scoring, buying signals, outbound and inbound automation, and the CRM plumbing behind them. It lets a revenue team grow pipeline with code, data, and automation instead of only adding headcount. ### How is GTM engineering different from RevOps? RevOps owns process, forecasting, reporting, and CRM governance across the revenue org. GTM engineering builds the machinery that creates pipeline: data, signals, scoring, and outreach automation. At small companies one person often does both, and as the team grows the GTM engineer usually reports into RevOps or growth. ### What tools do GTM engineers use? A data layer (several enrichment providers, often through Clay or an API like Deepline), a CRM such as HubSpot, Salesforce, or Attio, a sequencer such as Instantly or HeyReach, AI models for classification and drafting, and increasingly code written with AI coding agents like Claude Code, stored in a database like Supabase and run on a schedule. ### Is GTM engineering just Clay? No. Clay made waterfall enrichment accessible and many GTM engineers learned in it, but the practice is the system design: what to score, which signals to watch, how leads route, and how results get measured. The same workflows can run in Clay, n8n, or code. ### Do you need to code to do GTM engineering? Not to start. No-code tools cover a lot. Some SQL and the ability to read and run scripts written with an AI coding agent will take you much further, because custom logic, scheduled jobs, and cost control at volume are easier in code. ### How do I start GTM engineering with no budget? Pick one motion, write your ICP as checkable fields, pull a small account list from a free source, enrich a few hundred records on free tiers, and build one workflow end to end. Measure replies and meetings by signal before adding anything else. ### Should I hire a GTM engineer or use a GTM engineering agency? Hire in-house when there is steady system work and someone to manage the role. Use an agency when you need systems live in weeks or before your first GTM engineer starts. Many teams do both: the agency builds, then hands the system to the hire. Want the first GTM systems built before you hire for them? ## Related - [GTM engineering agency](https://getaob.com/gtm-engineering-agency): Founder-led outbound, signal, CRM, and AI systems for seed to Series C teams. - [What is a GTM engineer?](https://getaob.com/gtm-engineer): The role, salary ranges, skills, and tools, from the State of GTME report. - [The GTME Data Report (Q4 2026)](https://getaob.com/gtm-engineering-hiring-report): Quarterly data on GTM engineers and job postings: pay, applicants, time open, and where the two sides differ. - [History of sales technology](https://getaob.com/sales-tech-history): A sourced timeline of sales tech by year, from CRM and contact data to signals and agents, and what comes next. - [Free GTM engineering course](https://getaob.com/gtm-engineering-course): An eight-week, self-paced learning path with one hands-on project per week. - [GTM engineer salary calculator](https://getaob.com/gtm-engineer-salary): Estimate GTM engineer pay by region, company size, and coding depth, from 228 survey responses. - [GTM engineer jobs tracker](https://getaob.com/gtm-engineer-jobs): Open GTM engineer roles, companies hiring, and weekly trends, refreshed every Monday. - [Best GTM engineering agencies](https://getaob.com/gtm-engineering-agencies): The full landscape of GTM engineering, RevOps, and Clay agencies. - [Buying signals guide](https://getaob.com/buying-signals): The 15 B2B buying signals worth tracking, how to detect each one, and how to turn a signal into outreach. - [How a OneGTM engagement works](https://getaob.com/how-i-work): The end-to-end build from account list to booked meeting, the 12 work modules, and who owns what. - [GTM engineering services](https://getaob.com/systems): Everything OneGTM builds, from CRM enrichment to signal-based outbound. ## Start GTM engineering with OneGTM Tell me what you're building. I reply the same day. Book a call at [getaob.com/#contact](https://getaob.com/#contact) or email [team@getaob.com](mailto:team@getaob.com).