Transitioning from AI Engineering to GTM Engineering: Seeking Guidance on Clay Workflows and Portfolio Building

·Mar 17, 2026 05:04 PM·

Hi, I'm Bhuvan. I come from a technical background three years as an AI Engineer working with Python, RAG systems, and n8n. Recently, I took on outreach responsibilities at my company, and it became clear to me that driving revenue and reaching the right people creates more real-world impact than building the technical pipeline alone. That shift in perspective is what brought me to Clay, which I've been hands-on with for the past two months. I'm now looking to transition into GTM Engineering and would really appreciate any guidance whether on Clay workflows, building a portfolio, or breaking into the space.

👋2

3 comments

· Sorted by Oldest

Tyler P.
·
·
Apply for the alpha program
Ketan A.
·
·
+1 to what Tyler said, but you can also go through the Clay cohorts to get a fundamental understanding of the tool. You'll be able to pick it up quickly and start contributing and building systems that scale revenue
Rohan C.
·
·
Hey Bhuvan! Three years in AI Engineering and now stepping into GTM - honestly that's a really exciting crossover and you're probably going to move faster than most people here because you actually understand what's happening under the hood. One thing I'd say from brief experience here - start with the problem, not the tool. The best workflows I've built weren't because I knew Clay well, they were because I was painfully clear on who I needed to reach and why. That clarity designs the table for you. A scrappy table that solved a real problem >> polished demo with no real use case. I've been doing a lot of this manually up until now and I'm genuinely excited to be getting into Clay at a time when I'm planning the scaling quarter for my own startup - so we're kind of on the same journey from different angles. Happy to chat more!