The Economics
The economics moved before the job titles did.
The category is young enough to be worth treating carefully. Clay coined the term, funds the main newsletter and certifies the agencies, so a good deal of what is written about GTM engineering is written by people selling GTM engineering. We have published our own read of the research, including the figures that conflict and the vendor claims we would not repeat.
Five phases to our engagement over three months
The order is not negotiable, because each phase inherits the errors of the one before it. A signal engine built on a list nobody validated will industrialise the wrong accounts, faster than a human ever could.
01
ICP and offer
We define who you sell to precisely enough to automate against it: firmographics, the technologies they run, the roles that sign, and the events that tell you a company has moved closer to buying. We pressure-test that definition against your closed-won and closed-lost deals rather than against a positioning document, because the system can only find more accounts resembling the ones you tell it to look for.
You Get:
A written ICP with the attributes the system will filter on, and the offer the outreach will carry.
02
Data foundation
We build the account and contact layer, sourcing lists from the providers that actually cover your geography, then running waterfall enrichment so each provider only fires when the previous one missed. A single provider returns 30 to 60% of contacts, whereas a waterfall across a dozen pushes that to 80 to 93%, and every layer above inherits the difference.
You Get:
A live, deduplicated account list with verified contacts, wired into your CRM.
03
Signals and routing
We wire up the evidence that an account has moved: funding rounds, relevant hires, technology changes, job changes among your past champions, and behaviour on your own site. Each signal gets a filter against the ICP, a score, and a rule for who it goes to and how fast, because a funding announcement at a company that would never buy from you is news rather than a signal.
You Get:
Scored, routed signal feeds with the logic documented in plain language.
04
Outreach and activation
We build the sequences those signals trigger across email and LinkedIn, including the sending infrastructure most teams get wrong: secondary domains, authenticated mailboxes, warm-up periods and volume limits per mailbox. Google and Yahoo throttle senders whose spam complaint rate passes 0.3%, so deliverability is engineered before volume rather than repaired after it.
You Get:
Live campaigns running, sent from infrastructure built to stay in the inbox.
05
Measurement and handover
We instrument stage-to-stage conversion so you can see whether the gap sits at the top of the funnel or leaks in the middle, attribute results by workflow so you know which plays to kill, and hand the system over through a structured programme rather than a documentation dump.
You Get:
Reporting your team reads weekly, and a team that has already run the system before we leave.
What differentiates us
We build it with your team, not next to them
A revenue system nobody on your team can modify degrades in weeks. Webhooks fail silently, providers deprecate endpoints, a sequence starts double-sending, a CRM field stops syncing; none of it announces itself, and all of it is invisible to whoever inherits a system they only watched being built. So we do not build it from the outside.
Embedded in your workflow
We work inside your Slack and join your standups for the three months, so decisions get made where your team already makes them.
Every decision gets made and logged where your team already works, not buried in a deck from a call three weeks ago.
Live working sessions
Your RevOps or growth owner builds alongside us through each phase rather than receiving a finished system at the end of it.
Changes get made live, in front of the person who inherits the system, so nothing ships that they have not already seen work.
Walkthroughs throughout
Every workflow gets a recorded walkthrough as it is built, so the reasoning is captured while it is fresh rather than reconstructed months later.
Each recording explains why the workflow is built that way, so a new hire can watch it in month six and still follow the logic.
Structured handover
The engagement closes with a training programme and a final session that tests understanding rather than assuming it.
The closing session tests your team on running and modifying the system themselves, before we leave rather than after something breaks.
Six layers, wired as one system
These are six functions, not six purchases. Most wasted spend in this category comes from two subscriptions covering the same function without anyone noticing, so we price the layer rather than the tool.
The alternative
What this replaces
Hiring a GTM engineer
This engagement
Hiring is the right call in one situation, and it is worth naming. When a process already works manually and the constraint is hours, a full-time engineer pays for itself: founder-led outbound is getting replies, the ICP has survived contact with closed deals, and the team is losing days each week to list building and CRM admin. What a hire will not do is find product-market fit on your behalf.
The Research
We published the whole method
These are six functions, not six purchases. Most wasted spend in this category comes from two subscriptions covering the same function without anyone noticing, so we price the layer rather than the tool
What is GTM engineering?
GTM engineering treats go-to-market as a system you build, not a team you staff. What the discipline is, the economics driving it, and what survives the hype.
The GTM engineering tech stack
Read
The data layer
Every signal runs through an account list. How to build, enrich and maintain the data layer under a GTM engine, and what waterfall enrichment really costs.
Read
Signals and routing
Companies House SH01s, SEC Form Ds, certificate logs and trademark filings: the public-record buying signals most teams miss, and how to route them.
Read
Outreach and deliverability
How to write outreach off a trigger, sequence it across email, LinkedIn and Telegram, and stay under the 0.3% spam rate that gets senders filtered out.
Read
What a GTM engineer does
What a GTM engineer does day to day, how the role differs from a GTM manager, and when hiring one pays back. The data behind B2B's fastest-growing job title.
Read
GTM engineering case studies
Companies House SH01s, SEC Form Ds, certificate logs and trademark filings: the public-record buying signals most teams miss, and how to route them.
Read
Consultancy or in-house
How to write outreach off a trigger, sequence it across email, LinkedIn and Telegram, and stay under the 0.3% spam rate that gets senders filtered out.
Read
GTM engineer versus RevOps
What a GTM engineer does day to day, how the role differs from a GTM manager, and when hiring one pays back. The data behind B2B's fastest-growing job title.
Read
Frequently asked questions
03
Why is tooling billed separately rather than bundled into the fee?
Because you should own the accounts. Where an agency holds the subscriptions, your data, sequences and sending domains leave when the agency does, and you pay a margin on software you could buy directly. We also tell you which layers you can skip; most teams at startup scale need fewer tools than the category sells them.
04
Should we hire a GTM engineer instead?
Sometimes, and it is worth naming when. Hiring is the right call once a process already works manually and the constraint is hours: founder-led outbound is getting replies, the ICP has survived contact with closed deals, and the team is losing days each week to list building and CRM admin. What a hire will not do is find product-market fit on your behalf. On cost, Apollo's hiring data puts the median GTM engineer salary at $127,500 and Clay puts it at $160,000, before tooling and recruitment, and one person then holds the whole system and can leave with it.
05
What does our team need to commit?
One owner, usually in RevOps or growth, who builds alongside us through each phase rather than receiving a finished system at the end of it. We work inside your Slack and join your standups for the three months. A revenue system nobody on your team can modify degrades within weeks, because webhooks fail silently, providers deprecate endpoints and CRM fields stop syncing, and none of it announces itself to someone who only watched the system being built.
06
What happens after the three months?
You keep a live system, a trained team, and a recorded walkthrough of every workflow captured as it was built rather than reconstructed afterwards. The engagement closes with a training programme and a final session that tests understanding rather than assuming it. An optional retainer covers maintenance and new plays, priced on scope, because what a maintained system costs depends on how much of it you are running.
07
How is this different from an outbound or lead generation agency?
An agency runs the outbound for you and keeps the machinery. We build the machinery inside your business, run the first campaigns alongside your team, train them to own it, and then leave. The commercial incentive follows from the structure: an agency is paid to keep you dependent, whereas a fixed three-month build is paid to make you self-sufficient.
08
Why is the order of the five phases fixed?
Each phase inherits the errors of the one before it. A signal engine built on a list nobody validated will industrialise the wrong accounts faster than any human could, and a well-built stack running against a vague ICP produces waste faster than a spreadsheet does. That is why phase one is the ICP and the offer rather than the tooling.
09
What is waterfall enrichment, and why does it matter?
Waterfall enrichment runs data providers in sequence so each one fires only when the previous one missed. A single provider returns 30 to 60% of contacts, whereas a waterfall across a dozen pushes that to 80 to 93%, and every layer above the data foundation inherits the difference. A cheap list with 40% bad addresses does not save money; it moves the cost to your sending reputation.
10
How do you stop our outreach landing in spam?
Deliverability is engineered before volume rather than repaired after it: secondary sending domains, authenticated mailboxes, warm-up periods and volume limits per mailbox, all built during phase four rather than bolted on once reply rates fall. Google and Yahoo throttle senders whose spam complaint rate passes 0.3%, and a sending reputation takes far longer to rebuild than to protect.
11
What are the six layers you build?
Data and list building, signal capture, enrichment and verification, orchestration, execution, and the glue and system of record. These are six functions rather than six purchases; most wasted spend in this category comes from two subscriptions covering the same function without anyone noticing, so we price the layer rather than the tool.
12
What results should we expect?
Targets are scoped and agreed on signing, against your deal sizes and your sales cycle rather than a published average taken from a business unlike yours. We instrument stage-to-stage conversion so you can see whether the gap sits at the top of the funnel or leaks in the middle, and attribute results by workflow so you know which plays to kill.
