The Revenue Leadership Podcast with Kyle Norton

The episode delivers a genuinely above-average density of actionable ideas - a custom-built GTM OS replacing 6Sense, dynamic ICP scoring engines, the 'love letter' ABM tactic, and the counterintuitive point that most of the system is deterministic rather than LLM-driven. The signal-to-noise ratio is hurt by recurring AI-native framing overhead and some repetition before getting to specifics.

“almost 70 to 80% of GTMOs is not LLM based. It's actually very deterministic. But there's automation and workflows below certain activities”

“running this every week for around $500 at max, I think we're going to get it to 50 very soon. That's just out of this world”

Several genuinely fresh angles emerge - the GTM architect versus GTM engineer distinction, the argument that GTM engineering as a standalone function will become a bottleneck, and the love-letter tactic for C-suite outreach are non-obvious. The overarching 'go all in or nothing' AI-native framing, however, is well-travelled territory in 2025 B2B discourse.

“love letters are a public charade of the executive team of the account”

“I do believe in a GTM architect, like a heavyweight senior player that knows their stuff, owns and governs the architecture and the pipelines”

Tim Rutten is a genuine practitioner - decade-long CMO at a real enterprise SaaS company with $350M+ ARR, an engineering background he actively uses, and he is personally building the system he describes. He is not a keynote-circuit thought leader and the specificity of his claims is consistent with someone who has actually done the work.

“I have 35ft in total running a book of business of 350 million and up ARR”

“I myself got into the terminal, fired up Claude code and basically the universe open to me”

The episode is well-stocked with named vendors (Vercel, Cursor, Exa, FireCrawl, 6Sense, Casisto), named accounts (JP Morgan Chase, DBS Singapore, Westpac), concrete timelines (three months to build the reporting stack), headcount ratios (35 marketing FTEs on $350M ARR), and cost figures ($500/week, $15k deprecated tool, $100k target by year-end). A few ROI claims remain vague ('multimillion gain') and the pipeline improvement data is directional rather than hard.

“we deprecated a tool for 15k per year. Beginning of last. No, uh, this is Q4, we were able to not renew six sense”

“15 minutes right. And it's ridiculously high quality”

Kyle Norton asks sharp structural follow-ups - pressing on team composition, longevity of GTM engineering as a role, and whether pipeline numbers have actually moved - and the 'Is it the same people though?' challenge is a good probe. The host does not push back on unverifiable superlatives ('fastest growing podcast of 2025', 'multimillion gain') and the quickfire section at the end is soft filler, but the mid-episode architecture dialogue is genuinely well-excavated.

“Is it the same people though? Like are you know, you need people to drive this org chart, but not everybody is going to make that transition”

“Wait, so say more about that. Why do you don't you think GTM engineering is, is a role with longevity?”