Contents
GTM engineering is the sales hire everyone wants in 2026, and the tooling behind it is getting more capable every month. For vendors selling into UK hospitality, that is good news with one catch. An automated workflow does exactly what its inputs tell it to, at scale, and most of the data the GTM engineering playbook assumes was built for software companies selling to software companies, not for POS providers, suppliers and agencies selling to pubs, restaurants and cafés.
What is a GTM engineer?
The short answer is a sales operations person who builds. Bloomberry analysed a year of GTM engineering job postings (last updated 25 January 2026) and found the top three responsibilities were building and automating GTM workflows, integrating the GTM tech stack, and owning the CRM. Nine of the top ten responsibilities also appeared in RevOps postings. SQL and Python each showed up in 38% of GTM engineer postings, and the median advertised salary was $127,500.
Demand is the part nobody disputes. Bloomberry counted a 205% year-on-year increase in GTM engineering job postings for January to September 2025 against the same months of 2024.
Not everyone is convinced the title means much. In the Wall Street Journal on 30 September 2026, brand consultant Miranda Shanahan put the "go-to-market engineer, who helps with sales operations" in the same bucket as other reworked job titles. "People are motivated to get new labels for jobs that already exist because it makes them seem like they have an edge," she said.
Both things can be true. The work is RevOps. What changed is how much of it a single person can now automate.
Why is everyone suddenly hiring for it?
Because the platforms are betting on it. Clay, the company most associated with the role, announced a $115 million Series D at a $7.1 billion valuation on 9 September 2026, citing 4x revenue growth in 2025 and more than 17,000 customers. It also launched a $1 million scholarship fund to train GTM engineers.
The incumbents are moving the same way. On 30 September 2026 ZoomInfo announced it had acquired DoubleO.ai, an agent orchestration platform, to run what it calls full GTM motions with AI agents. Its examples are telling: track a champion who changes jobs, or take a closed deal and find ten lookalike competitors to approach with tailored messaging.
"Every revenue leader has seen an AI agent demo. Almost none have seen it actually run a real GTM motion end-to-end," said Henry Schuck, ZoomInfo's founder and CEO. DoubleO.ai's co-founder Derek Osgood was blunter about the state of most agent projects: "The agents don't run the same way twice, so a person has to babysit every step, and you get maybe a 20% improvement."
What does a working GTM engineering system look like?
Clay published the most detailed answer so far on 21 October 2026. Its GTM engineers now run sales plays the way developers ship code, with version control, test branches and a human approving every change before it goes live. Clay calls it GTM CI/CD.
The results it reports are concrete. Six months ago its SDRs spent about seven minutes drafting each prospect message. A message generator cut that to around five. After the team linked every AI draft to the email the rep actually sent, collected the reason for each edit, and A/B tested prompt changes weekly, drafting now takes one minute per prospect.
The more useful detail for hospitality vendors is the failure Clay found along the way. A nightly agent review of one lead routing workflow found that 47 of 159 leads had been put in a segment that did not match their company size. That is roughly 30%, caught inside one of the best-resourced GTM teams in the world.
Why is hospitality harder?
The GTM engineering playbook leans on a few assumptions: every target account has a company record, a headcount, a LinkedIn page and a set of decision makers with job titles. ZoomInfo describes its data as covering more than 100 million companies and 500 million contacts. That kind of coverage works when the buyer is a software firm.
An independent restaurant often looks nothing like that. The owner works the floor, not LinkedIn. "Company size" means covers, sites and opening hours, not employees in a database. Venues open, close and change hands faster than annual firmographic refreshes catch. A workflow that segments on headcount will misroute a busy three-site group as a micro business, and nobody will notice until a rep has sent the wrong pitch for a month.
Run the arithmetic. A rep on Clay's one-minute workflow can comfortably draft 40 messages a day, against 280 minutes of drafting on the old seven-minute process. That is a real gain. But at the misclassification rate Clay's own review caught, roughly 12 of those 40 messages land in the wrong segment, every day, with the workflow running exactly as designed. Automation does not fix bad inputs. It ships them faster.
What about compliance?
This is where UK vendors cannot copy a US playbook. Under PECR, marketing emails to corporate subscribers such as limited companies are allowed if you identify yourself and offer an opt-out, but sole traders and many partnerships count as individual subscribers and need prior consent. A large share of independent hospitality is run by exactly those businesses. Marketing calls must be screened against the TPS and CTPS registers. Since 5 February 2026, under the Data (Use and Access) Act 2025, the maximum PECR fine is £17.5 million or 4% of annual global turnover, whichever is higher.
An agent that finds ten lookalike venues and emails them all in an afternoon has to know which of those ten it is allowed to email. That is a data question before it is a workflow question.
What should vendors selling into hospitality do?
Three things, before anyone builds an agent.
1/ Define "good" for your segment. Clay's first learning loop made its emails worse until the team wrote down what good copy looked like. The same applies to segmentation. Decide what makes a venue a fit in hospitality terms: site count, venue type, trading status, ownership.
2/ Fix the input layer first. A GTM engineer's time is better spent on venue data that is current, correctly classified and legally contactable than on a cleverer prompt sitting on a stale list.
3/ Keep a human approving changes. Every working system in this piece, Clay's and ZoomInfo's alike, puts a person between the agent's proposal and the live workflow.
GTM engineering will become standard in hospitality sales the same way CRM did. The vendors who win with it will be the ones whose workflows run on data built for the market they sell into.
A note on Peach Data
Peach Data builds verified, TPS/CTPS-screened contact data across thousands of UK venues, for the vendors who sell into them. We now also build GTM engineering workflows for teams selling into hospitality, on data that was designed for this market from the start. ICO registered and UK GDPR aligned. peachdata.co.uk
