Everett Berry's definition of GTM engineering is deceptively simple: remove the technical constraints that stop companies from growing as fast as possible. But in this episode, he unpacks what that actually requires in practice, and most senior GTM leaders will recognize immediately that the bottleneck almost never comes from a lack of ideas.

From how Canva monitors customer social feeds at scale to detect poor graphic design and route it into outbound plays, to how Clay itself rebuilt its entire events invite system from scratch over two to three months of painful iteration before it worked, this conversation goes deep on tactics, org design, and where the role is headed.

Topics discussed:

·       GTM engineering as a builder discipline, not an evolution of marketing ops

·       The three-layer implementation hierarchy: data quality, process automation, net new plays

·       Why centralization matters even when GTM engineers are embedded across functions

·       Rep ride-alongs as the primary method for finding plays worth scaling

·       Clay's infrastructure stack: Audiences on ClickHouse, Sequencer, Agents, and MCP connectors to ChatGPT and Claude

·       How PLG companies run self-serve to sales-led conversion plays, and why enterprise expansion still requires humans

·       The failure culture leadership must create before the first GTM engineer can succeed

·       Why vibe coders are often the wrong hire, and Clay's interview process for testing process thinking

·       GTM engineering as a small, permanent tiger team rather than a scaling headcount function

Listen to more episodes: 

Apple 

Spotify 

YouTube