Clay was named in 61% of the 98 GTM engineer job posts we tracked between 3 May and 5 October 2026. Instantly was named in 19% and Smartlead in 10%, so the tool that actually sends the email is missing from most of the ads written for the person who's meant to run it.
My read is that companies assume sending is the easy part. I don't think it is, and the numbers below show how narrow the margin for error gets.
What the job posts ask for
The work side of those 98 posts is pretty clear. Outbound came up in 57% of them, enrichment in 44% and sequences in 20%. Integrations sat at 37%, and 89% described building something from scratch rather than running a system someone else left behind.
The wider stack around Clay looked like this.
| Tool | Share of the 98 GTM engineer posts |
|---|---|
| Clay | 61% |
| HubSpot | 55% |
| Salesforce | 43% |
| n8n | 34% |
| Apollo | 27% |
| Instantly | 19% |
| Make | 16% |
| Smartlead | 10% |
| HeyReach | 5% |
Those shares count a post when the tool appears in its title, summary or extracted stack, so treat them as floors. Still, the shape is useful. CRM shows up about as often as Clay does, which means the person running outbound is also expected to get clean records back into HubSpot or Salesforce. A Clay table that books meetings nobody can find in the CRM is half a job.
For comparison, the 294 RevOps posts we tracked named Clay 13% of the time and Instantly 1% of the time. In our data, outbound tooling lives almost entirely in GTM engineer posts, so don't expect to find it in an ops manager's job spec. There's more on the full GTM post set in an earlier piece.
Sending is the part that breaks
Clay's own guide to automating outbound sketches a setup of 20 to 30 emails per inbox a day spread across 10 domains, for 400 to 600 sends a day. Instantly says in its 2026 benchmark piece that a warmed inbox can take about 100 cold emails a day, and that new accounts need two to four weeks of warmup first. That's a big gap between two vendors, and the person you hire needs an opinion on which one fits your domains, and a reason for it.
Then there's Gmail. Google's sender guidelines ask bulk senders to keep user-reported spam below 0.1% and never let it reach 0.3%. Once you're over 0.3%, you lose eligibility for mitigation support until you've stayed under it for seven straight days. Messages also need SPF and DKIM, with the From domain matching one of them.
Clay doesn't touch any of that. The work is in DNS records and inbox rotation, plus knowing when to pause a campaign that's going sideways. Instantly puts a normal bounce rate under 2% and calls anything above 5% a list quality problem. A good operator watches those numbers daily and kills a list before Google does it for them.
In my experience Smartlead and Instantly do broadly the same job, and someone fluent in one picks up the other fast. So for this seat, how a candidate sets up and protects sending domains matters a lot more than which sequencer they prefer.
What good looks like in month one
Month one is mostly plumbing. If domains need two to four weeks of warmup, as Instantly says, your new hire is not sending at volume in week two, and a plan that says otherwise is skipping the warmup.
A sensible first month, in order:
- Write down the ICP with the people who'll take the meetings, before building a single table.
- Buy and set up separate sending domains, with SPF and DKIM done properly, and start warmup.
- Build a test list of 200 to 500 companies in Clay, the size Clay's guide suggests for checking ICP quality, and run waterfall enrichment on it.
- Wire replies and meetings back into the CRM so you can see them in the pipeline report.
- Send the first small batches by week four and look at positive replies, not opens.
On the numbers to judge against, Clay treats a 1% to 3% positive response rate as viable and anything under 1% as a sign something basic is wrong. Instantly puts the average cold email reply rate at 3.43%, counting all replies rather than positive ones. lemlist's roundup of benchmarks shows how loose these figures are: one study it cites puts average replies at 3.7% across 53 million emails, another at 0.45% across 7.5 million. Different samples and different ideas of what counts as a reply both play a part. Pick one definition with your hire on day one and stick to it.
On a first test list of 500 contacts, Clay's range works out to 5 to 15 positive replies. Under 5 is a list or message problem, and sending more of the same won't fix it.
When you shouldn't hire for this
If you don't know who you're selling to yet, a full-time outbound engineer will build a very efficient machine for emailing the wrong people. Get a handful of customers who look alike first. Founder-led emails at small volume will teach you more than a Clay waterfall will.
Same if outbound is a one-off test. An agency on a short contract can prove whether cold email works for your market, and you stop paying when you have the answer.
The full-time hire makes sense once outbound is a channel you plan to keep running, because domains, lists and copy all need someone keeping an eye on them every week. The posts we tracked that printed a salary put the median GTM engineer base at $150,000, from a small sample of 23. What that turns into once benefits land is in our cost breakdown.
At Bubblegum we place GTM engineers full-time on your team, in your tools, from $4K a month all-in, with a free replacement if the fit is wrong.
Whoever you hire, ask them in the interview how they'd set up ten sending domains and what they'd do the day the spam rate hits 0.2%. Then ask to see a Clay table second.