At a US recruitment firm I worked with, the sales team spent most of the day on work no one wanted to do. Every inbound message landed in the same inbox: someone looking for a job, a company wanting a consultation, a firm that needed a search. A human had to read each one, decide what it was, filter the spam, and hand it to the right person. By the time a real lead got a reply, the moment of interest had passed.
Their instinct was reasonable: we are drowning, so let’s hire more people to sort the inbox. But another SDR would not fix the problem. The sorting, filtering, and routing was not a staffing gap. It was a system that nobody had built yet.
The reflex to hire
When a revenue team falls behind, the common move is to add people. More SDRs to work the inbound. More researchers to prep the calls. More ops headcount to keep the CRM clean. It feels like progress because you can point to the new seats.
The trouble is that a lot of this work is repetitive and rule-based. Read a lead, classify it, look up the company, decide where it goes, draft the first reply. A person can do that. A system can do it in seconds, every time, at any hour, without getting tired at 4pm. When you hire a person to do work a system should do, you pay for it twice: once in salary, and again in the leads that go cold while they catch up.
What a GTM Engineer actually does
Clay coined the term “GTM Engineer” in 2023 for the person who builds this missing layer. I think of it simply: an engineer who understands revenue. Someone who can take a fuzzy problem (“our inbound is a mess”) and ship a working system that fixes it, instead of a slide that describes it.
The job is not to replace the sales team. It is to take the manual work off their plate so they spend their hours on the parts that need a human: the call, the relationship, the close. Here is what that looked like across three builds.
Three systems, not three hires
A recruitment firm’s inbound. I built an engine that reads every lead from email and phone, classifies it (candidate, search, consulting, and so on), filters the spam, routes it to the right team or partner, and drafts the first reply. The team gets a Slack notification with the context and one click to act. It gave the SDRs back more than 6 hours a day, and revenue grew 45% over the first three months, because leads got handled fast, at the point of interest, instead of hours later.
A creative agency’s pipeline. They had plenty of form fills but only wanted to spend time on leads that fit. I built a system that researches every intake lead, scores it against their ICP and budget, and routes it to the internal team, a partner, or a polite no. Research and meeting notes are attached automatically, so a rep walks into a call already briefed instead of prepping for an hour. Their calendars filled with qualified calls, not busywork.
A SaaS company’s outbound. The best time to reach their prospect is the moment that business is about to launch. I built a system that watches business license filings across multiple US states, catches the ones that fit, researches each one, and reaches out with a pitch built for their specific situation. Cold outreach conversion went from 3% to over 25% in two months, because timing and relevance did the work that volume never could.
Different companies, different problems. The same shape underneath: find the signal, and build something that acts on it.
Most teams already have the data
Here is the part that surprises people. The bottleneck is rarely missing data. The CRM has the leads. The inbox has the intent. The pipeline has the pattern. What is missing is anything that acts on it automatically. The signal sits there, and a human has to notice it, interpret it, and do something, which means most of it gets missed.
A GTM Engineer closes that gap. Clean the data so it can be trusted, find the few signals that actually predict a sale, then wire them into the workflow so the right thing happens on its own. Fast response. A qualified lead in the right rep’s hands. An outreach that lands when the prospect is ready.
Before the next hire
If your team is buried in manual sales work, it is worth asking a different question before you open a new role. Not “who can we hire to keep up,” but “what would a system do here.” Sometimes the honest answer is still a person. Often it is a system that pays for itself in the leads you stop losing.
That is the work I do. If your sales motion is doing by hand what it could be doing by system, I can help.
[ work with me ]