r/gtmengineering
Anyone here building actual AI employees for GTM
- upvotes
- 9
- comments
- 23
Post
ive been building GTM agents and lately I've been thinking a lot about where the line is between an automation and an actual AI employee most gtm workflows today are still pretty structured like clay finds the leads, enrichment tools pull the data, an LLM personalizes something, and Instantly or another tool handles outreach but what happens when you want an agent that actually owns a workflow end to end? Like an AI SDR that has its own email inbox, can make calls, follow up on WhatsApp, coordinate meetings, talk to people on Slack, and continue conversations over days or weeks without someone manually triggering every step. At that point, it starts feeling less like a workflow and more like an employee that needs its own identity and communication infrastructure I've been exploring this agent identity space, particularly the idea of giving an agent its own communication identity through a single API, rather than stitching together Gmail, Twilio, Slack, calendars, and everything else. I'm still trying to understand whether this is a real infrastructure gap or whether most GTM builders are perfectly happy using existing tools. For those building autonomous GTM agents, how are you handling their communication and identity today?
Extracted from these lines
[comment u/jedsdawg] honestly I don't think identity is the gap, the stitching is. we ran the same Clay plus enrichment plus Instantly chain and every handoff was another place it broke.