week 3 of looking for GTM work in public
got a pilot, said no to 2 other projects, and one of my posts here did over 350k views
here’s the week 🧵
1
25
2/ numbers
12 calls
6 interviews
3 pilot offers, took 1
2 rejections
1 process I walked away from
1
5
This is based on projections from Professor Jose García Montalvo (Economics Professor), who modeled ~1.5M U.S. workers skipping launch day - costing roughly $1B in daily output. He also highlighted that tech companies and remote workers aged 18-30 will see the sharpest drop-off
1.5M Americans are expected to take leave this Thursday (Nov 19) for the GTA 6 launch 🇺🇸
If you're running US outbound right now:
→ Pause your Thu/Fri sends (they'll get buried)
→ Test a GTA 6 pattern-interrupt hook on a small gen z audience
Cultural timing > cold volume
1
2
1,233
I’m not against companies asking for Loom videos in applications, understand the signal they’re trying to get.
But if you’re going to ask for one, watch it before you reject the candidate.
That’s the bare minimum.
1.5M Americans are expected to take leave this Thursday (Nov 19) for the GTA 6 launch 🇺🇸
If you're running US outbound right now:
→ Pause your Thu/Fri sends (they'll get buried)
→ Test a GTA 6 pattern-interrupt hook on a small gen z audience
Cultural timing > cold volume
Kavish Lodha retweeted
You don't need to worry about progressing slowly. You need to worry about climbing the wrong mountain.
two 2nd-round interviews today
both are companies I’d genuinely love to work with
→ one is growth-focused
→ one is pure GTM engineering
clearing my whole day to prep for both
wish me luck 🤞
11
29
891
Kavish Lodha retweeted
what a day
8 calls on the calendar
-> 5 done
-> 2 asked to reschedule
-> 1 left before i wrap up
GTM work in one tweet
what a day
8 calls on the calendar
-> 5 done
-> 2 asked to reschedule
-> 1 left before i wrap up
GTM work in one tweet
the SDR playbook made sense when outbound was a volume game
now it’s an infrastructure game
signals > data > automation > then people
your first GTM hire should build the system, not just run it
Hot take: Your first sales hire should always be a GTM engineer. Why? He can figure out what works. But instead... most companies get a founding SDR. And that’s a mistake.
But before I explain why, let me tell you my definition of a GTM engineer:
A well-rounded growth employee. They can setup Clay tables, run Claude Code automations, setup Instantly campaigns, call from parallel dialers; they can do it all.
Examples: Benyamin Holley, Chris Fry, and Justin Chi are all operators who meet this criteria.
I’m writing this post after an old friend reached out. He’s giving up his $115K/yr job in construction to be an SDR.
He asked me for some advice. He saved about 10 open SDR roles to a Google sheet and sent them to me.
John: “Ben, you’ve been in tech for a while. Should I stay away from any of these?”
I looked through the jobs. I recognized the companies but wasn’t sure what they sold. All of them were recently funded $10M-$75M in the last year. And probably 8/10 were hiring for 10 SDRs.
Me: “John, these are mostly red flags.”
John: “How so?”
Me: “Anytime a company is hiring this fast, this early on, they usually don’t have a plan. And you’ll probably get ‘laid off’ after 5 months.”
TLDR
If you’re looking for your first SDR role, apply at an established company.
And if you’re a company hiring your first GTM role, let it be a seasoned engineer
6
3
179
Kavish Lodha retweeted
yesterday was nuts, 7 calls back to back
(4 networking, 2 interviews, 1 fractional GTM sales call)
then a date
and today’s somehow even busier
send black coffee and a brownie lol













