When to Hire a GTM Engineer: The 30-Minute Test I Actually Use

I run go to market for B2B companies for a living, and the question I get asked most by founders isn't "which tool should I buy." It's "when do I actually need to hire someone for this." I recorded a conversation about it with Harri Konola, who runs GTM engineering work of his own, and the most useful thing either of us said in 48 minutes wasn't about tools at all. It was a test.

I'm Hlib Storchak. I build and run outbound systems for B2B founders and sales teams, and I've booked 2000+ meetings for B2B clients doing it. What follows is the test, why it works, and what I'd actually build once you've passed it.

The 30-minute test I use before recommending a hire

Here's the test, in Harri's words paraphrased: if you, as a founder, can sit down for 30 minutes, write a message by hand, send it to a handful of prospects, and get a reply that tells you the message resonates, then you already have what you need. You have a product people want and a way of talking about it that lands. What you don't have is scale.

That's the moment to bring in a GTM engineer, and the job description is simple once you frame it this way: take the exact thing that worked for ten companies and make it work for ten thousand. Find the bottlenecks along the way and remove them. That's it. It's not a magic trick, it's operational leverage on something already proven.

The reverse is the part founders get wrong. If you can't get a reply from 30 minutes of your own manual outreach, hiring a GTM engineer, an agency, or buying another tool won't fix that. You'll just be paying someone to scale a message that doesn't work yet, faster.

GTM strategy and GTM engineering are not the same job

The term GTM got pushed hard through 2025 and it's now vague enough that two people can use it and mean different things in the same sentence. Some people think a GTM engineer needs to code. Some think it's just a sales title with a new coat of paint.

My working definition, and I think Harri would sign off on it too, is that a GTM engineer sits at the back end of the sales function. It's the person responsible for the direction a company's outbound and pipeline take, and for actually executing on it: building the ideal customer profile, translating that into messaging, and running that messaging across more than one channel at once rather than one platform in isolation. The role itself is young enough that the definition is still being argued out in public, which is worth reading if you want the fuller picture of how the title came to exist.

What separates it from a one-off outreach freelancer is that a good GTM engineer builds a system, not a single campaign. Anyone can send a batch of personalized emails once. The job is building something that keeps generating pipeline without you rewriting it every month.

Product market fit is not the fit you're missing

An ideal customer profile isn't "B2B SaaS company under 50 employees." Half the market describes itself that way and it tells you almost nothing about who actually converts. Building a real one means picturing the specific person, in the specific situation, who has the problem your product solves right now, not eventually.

Where founders actually get stuck usually isn't product market fit. It's message market fit: they have a product people want, validated by inbound requests and people asking questions on LinkedIn, but they don't know how to package that same value proposition for a cold audience that has never heard of them. That's a different problem than the product being wrong, and it needs a different fix. If you haven't nailed down who the message is for yet, that's worth solving before anything else, and I've written separately about how to build an ICP that actually converts.

Where a GTM engineer fits in your company's lifecycle

Early on, before you have product market fit, a GTM engineer can still be useful, just for a narrower job: building accurate lists to understand the real size of your addressable market, and surfacing the pain points that show up across those companies so you can adjust your offer around them.

Once you're getting inbound and can talk to the people already paying you, that's usually the highest leverage moment. Ask them directly why they bought, in their own words, and you'll get the beginning of your message market fit for free. Take that language and multiply it across companies that look like theirs.

The 30-minute test is what tells you the transition point. Once your manual messaging is converting, a GTM engineer's entire value is compressing the time between "this works for ten" and "this works at scale," while catching the bottlenecks and dead weight in the process that a founder stretched thin usually misses.

What a good GTM engineer actually does first

It's a common misconception that GTM engineering means writing personalized cold emails all day. That's part of it, but if I joined a company tomorrow, the first thing I'd look at is the CRM, not the outbound sequences. Almost every company I've worked with has a CRM full of empty fields, duplicate records, and contacts that should have been archived a year ago.

After that comes database reactivation: going back through people you've already talked to, including deals that stalled or clients who churned, and reopening the ones worth reopening. It's some of the cheapest pipeline available because the relationship already exists. CRM hygiene doesn't get talked about as much as cold email does, but the companies ignoring it are going to feel the consequences of that sooner than they expect.

The intent signals worth building around

Once the basics are in order, the highest-leverage work is layering intent signals on top of your outreach instead of messaging a cold list blind. In the conversation, the reply lift Harri cited for messaging someone who had just visited your website, versus a cold list, was about five times higher. That gap alone is worth building a system around rather than leaving to chance.

Website visitor tracking is the one with the sharpest split by region. In the US, tools can identify the actual person browsing your site, which is what makes the reply lift so large: you can reference the exact page they looked at. In Europe, GDPR makes person-level identification a lot harder, and I go through what each approach can and can't do in RB2B vs Common Room for website visitor identification, which is worth reading before you commit budget to either category.

Champion tracking is the most underused of the four, mostly because it's tedious to do by hand. If someone at 500-plus LinkedIn connections changes jobs, you're not going to catch that by scrolling their profile. It needs to run as a system, not a habit, and it's a good example of what I mean by turning buying signals into meetings rather than just collecting them.

Why none of this matters if the infrastructure is wrong

You can have the best offer and the best message in the world, and if it lands in a spam folder, none of it matters. Nobody checks the spam folder. If your messages get flagged, the game is already over before the prospect ever reads a word.

Good infrastructure means buying domains and inboxes from trusted providers, warming them up properly, and giving Google and Outlook a reason to trust you as a real sender rather than a mass mailer. It also means avoiding the obvious spam triggers: words like "free" or "guarantee," heavy use of links or images in a first message, and sending the exact same copy to a thousand people without any variation. Plain text, no spam words, genuinely relevant copy. That's the baseline, not the advanced version.

The same logic applies to LinkedIn. Using the wrong kind of automation there gets accounts restricted or banned outright, so the setup has to be treated with the same seriousness as email infrastructure, not as an afterthought bolted onto it.

Why one tool ends up at the center of the stack

If I had to draw the GTM tech stack as a solar system, one tool sits at the center and everything else orbits it: an enrichment and workflow platform that ties list building, contact enrichment, signal tracking, and message personalization into one place, then hands the finished message off to whatever sends it out over email or LinkedIn.

The mistake people make is treating that tool as just a way to send hyper-personalized emails. In practice it's closer to a single source of truth: building the initial company and contact lists, running waterfall enrichment across multiple data providers so you get better coverage than any one source gives you, checking each company against your ICP, pulling in the intent signals from the table above, and only then writing the message. Sending it out is the last step, not the point of the exercise.

Write the message by hand before AI touches it

This is the part of the conversation I think about the most, because it runs against almost everything being sold right now. People are starting to feel AI fatigue in their inbox. You don't have to be an expert to spot a fully AI-written message anymore, and once a reader spots it, the message is dead regardless of how relevant the targeting was.

The practice we both use, on the campaigns we actually run for clients, is to write the first version of a message by hand, on paper, before any model touches it. That draft becomes the backbone of the campaign. Only after it exists do we use AI, and the job it does is closer to reverse engineering that draft into variations at scale than generating the idea from nothing. It's a small ordering change, hand first, model second, and it produces messages that read like a person wrote them, because one did.

Hyper-personalization at scale has a place, but relevance from a real signal usually beats a paragraph of AI-generated flattery about someone's job title. The two aren't the same thing, and treating them as interchangeable is how a lot of AI-assisted outbound ends up sounding the same as everyone else's.

Why GTM should sit between sales and marketing, not above them

GTM has mostly lived as a function that fills the top of the pipeline and hands it off, without much connection to sales or marketing beyond that handoff. I think that changes going forward, and it should, because the whole thing works better as one system than as three departments trading leads over a wall.

The clearest example is speed to lead. If a GTM engineer generates a strong reply from cold email and the sales team doesn't respond within five to ten minutes, the odds of converting that reply into a meeting drop fast, and the work that produced the reply was wasted for no good reason. That's an alignment problem, not a GTM problem or a sales problem on its own.

The reverse direction matters too. In my own client work, once a campaign is running, marketing teams increasingly want the same up-to-date lists and the same language that's converting in outbound, because it tells them what resonates before they spend on ads or rewrite the website copy. Treating GTM as the connective tissue between sales and marketing, rather than a standalone lead-gen function, is where I'd put my money for the next year.

Where I'd put AI in 2026, and where I wouldn't

My read, and Harri's too, is that AI's role in GTM will grow in some places and shrink in others at the same time. On the back end, for handling the two or three most common objections that show up across a campaign, automating that reply is a reasonable use of AI, because the pattern is repetitive and low stakes.

On the front end, where a prospect is actually deciding whether to trust you, I want less AI, not more, especially for anything technical enough that it needs a real answer to convert. That split, more automation behind the scenes and less of it customer-facing, is the version of AI adoption I'd bet on holding up better than the alternative of automating everything just because it's possible.

FAQ