Emre Jacob Solak

Emre Jacob SolakMay 28, 2026

GTM Engineering is dead... 95% of GTM-E's will cease to exist by the end of 2027 Not because you're being repalced by AI (Which you are), but because you haven't learnt the basics... You might have; - Finished Clay University - Watched every single Eric video on YouTube - "Built" a Clay Table from scratch But you haven't done anything that can't be automated, you've not learnt the theory behind why it works. Becuase of that, you can't come up with new ideas. You need to learn; - Basic Deliverability Exposure - Offer Creations and the importances of Phycological triggers in Copy - Bottom of the barrel sales techniques It's a growing frustration for alot of operators in the space, the lack of sales first talent. Every GTMe I've spoke to in the 30day's has been 100% technical. IF you're worried after reading this, fear not. Comment "GTM" below I'll send you the roadmap to NOT get replaced by AI in 6 months

Emre Jacob SolakMay 11, 2026

Clay is dead GTM teams have spent 5 months building with Claude Most have realised Clay isn't as vital to their operation as it used to be. All teams have realised DATA is their biggest asset, and their biggest problem. We had 3 main issues at solak: - Data Quality from Apollo got worse and worse - API Limits and Export times - Pricing at scale as we started needing larger data volumes Luckily we found a solution, much better than scraping Apollo, or relying on 3rd Party Vendors... Access to the same data-set Clay uses as their foundational layer If you're still scraping data from apollo and have had enough of slow, third party vendors I'll share the video where I explain how exactly we've fully replaced clay, and moved to our new data vendor. Just comment "data" below

Emre Jacob SolakMay 6, 2026

Most people are talking about WHAT to automate with Claude Almost nobody is talking about WHERE the state lives. And that’s where every cold-email stack at scale eventually breaks. Because if you don’t understand how your no-code tool stores execution state, you’re not just losing data… you’re paying for the same workflow run again and again. So I rebuilt my entire outbound stack last month, not chasing a better workflow, but tearing out the architectural commitment N8N was forcing on me. A few things that changed the game for me: • Step 4 fails → don’t re-run from the start, write state at every step • Execution log → Postgres rows that survive crashes • Spaghetti chain → state machine (received → classified → drafted → approved → sent) • “Where is this lead?” → SELECT * FROM replies WHERE status=’send_failed’ • Re-pay for Claude on retry → resume from the failed step, draft still attached • 15 N8N workflows → 24 TypeScript + Postgres workflows, all resumable And the biggest one: Most people optimize their workflows. Very few optimize their architecture. That’s the difference between a tool that works for 100 leads and a tool that works for 11,000. Comment “Autopsy” and I’ll send you the full breakdown