GTM Engineer: James @ Profound

James Underhill, Head of GTM Ops at Profound, runs the ops and systems function through one of the more extreme growth curves you'll hear about: five times ARR in nine months, headcount from sixty to two hundred, and an AE team scaling from thirty toward a hundred by year end. His operating principle is simple: buy infrastructure, build applications. That single bias shapes how his team is staffed, what they buy, what they build, and where they draw the line on both. He built a deal desk bot in under twenty minutes on Dust without writing a line of code.  His team deflected 70% of support inquiries with an internal triage agent. And he replaced the traditional business partner role entirely by giving the field direct, semantic access to their own data. **Topics Discussed** - Why calibrating to the first derivative of growth matters more than current headcount - Using Dust as a low-code agent platform across GTM, CS, and internal ops - Deflecting 70% of support inquiries with a confidence-gated triage agent - Buy infrastructure, build application as a disciplined team operating principle - Why GTM engineering at this level requires actual software engineers, not just technical curiosity - GitHub fluency as the new hiring proxy for this function - Snowflake plus a semantic layer as the foundation for real-time, conversational data querying - Centralizing Claude Code skills in Notion for rep-accessible, field-ready workflows - The hidden maintenance cost of vibe-coded tools and why it compounds fast - Replacing business partner roles with self-serve data access - Where Gong's call intelligence falls short and why that becomes a build opportunity - How to decide what to build versus buy when your team could technically do both