GTM AI Podcast with Coach K and Jonathan Moss

AI Business Network

Details

Welcome to the GTM AI Podcast, your go-to independent resource to help GTM Professionals become AI Powered. We will cover strategies, new AI tools, AI news and trends, all for the purpose of helping you create real measurable business impact and help your life be easier. We do weekly episodes ranging from interviews to updates to strategy sessions. Sponsored by the AI Business Network www.aibusinessnetwork.ai and GTM AI Academy www.gtmaiacademy.com

Recent Episodes

NOV 12, 2026
Context Engineering for AI Agents: The 3-Layer System
www.gtmaipodcast.com In this episode of the GTM AI Podcast, I sit down with returning guest Justin Parnell, CEO of Justin GPT and a forward-deployed engineer who builds AI agents inside startups, local businesses and publicly traded companies. He walks through the context engineering system he runs his own consultancy on, live on screen. We cover: Why the model is never the problem "You're not really ever going to have the model be the problem." The four context failures behind bad AI output: facts asserted from memory, documents that rot, pages that restate stale numbers, and more than one source of truth. The three layers of context Operating files (the harness), the canon (declared context) and live data. What belongs in each layer, where each one lives, and how often it refreshes. Harness vs. context layer Where context engineering sits next to model harnesses, loop engineering and graph engineering, and why a harness without context underperforms. Business vs. consultancy context engineering One company with one canon, versus a practice that has to keep every client's context isolated so data never lands in the wrong CRM. The campaign agent that works for a day and a half to two days One campaign brief in. Ad assets, landing pages, sales enablement decks, a CRM loaded with leads and 1:1 copy for around 1,000 people out. Plus why that agent never works without the context layer underneath it. Staying model-agnostic How to keep context portable in Notion, Obsidian or GitHub so a switch between model providers does not leave your team starting from zero. Starting from zero Justin's plan for getting scattered files into a context layer in two to three days of weekend work, and his estimate of 20 to 30% off your token budget once it is running. Live demo: the Friday 8pm routine The cloud routine that refreshes his canon every week, plus the call-ingest and invoicing routines. His recipe for "poor man's context engineering": Notion, Google Drive, GitHub, Supabase and cloud routines. FREE: JUSTIN OPEN-SOURCED THE SETUP FROM THIS EPISODE Template repo (click "Use this template" for a private copy): https://github.com/justin-gpt/context-engineering-template Setup runbook (single-session path with a done-when test for every step): https://github.com/justin-gpt/context-engineering-template/blob/main/docs/07-setup-runbook.md Sample Notion workspace (duplicate any page into your own workspace): https://app.notion.com/p/3f1dbc7f21e08149a8fed4399166cc3f Setup skill for Claude Code or Cowork. It interviews you, recommends a stack from what you already run, then walks the build step by step: claude plugin marketplace add justin-gpt/context-engineering-template claude plugin install context-engineering-setup@context-engineering Then say: set up context engineering Not on Claude? The skill is a plain SKILL.md any agent can run: https://github.com/justin-gpt/context-engineering-template/tree/main/skills/context-engineering-setup From Justin: "Justin Parnell (Justin GPT) open-sourced the context engineering setup from this episode: a template repo for a governed context layer for AI agents. A thin canon with an owner and a review date on every page, a machine-readable contract agents read, a gap tracker they write to, a metrics catalog that holds definitions but never values, and a nightly sync through a pull-request gate. It covers a single company and a consultancy serving many clients, ships a setup skill that interviews you and recommends a stack from what you already run, and includes a sample Notion workspace to duplicate."
49 MIN
OCT 22, 2026
How the Swarm Built $10M in Pipeline using Network Strategy
www.gtmaipodcast.comThe Swarm built over $10M in pipeline in 12 months by getting warm intros from its own investors, advisors, and team. Co-founder and CEO David Connors shows exactly how they do it with Clay, Claude, and their own relationship graph.In this episode, David walks through the full warm intro motion: mapping your company's network without forcing everyone to sign up, scoring which relationships are real, carving warm accounts out of your target list, and the once-a-month batched ask that keeps investors and advisors happy to help. We also get into the Sequoia origin story, the Claude MCP demo, and why trust becomes more valuable as AI floods every inbox. Built for founders, CROs, and GTM teams selling into complex, high-ACV deals.What you'll learn:- How to carve warm-intro accounts out of a 10,000-account list, then route the rest to cold and ads- The three intro plays (direct, indirect, mention) and which one drives the most pipeline- Why batching 10 intro asks per connector per month protects social capital and trains your cap table on your ICP- Why the top 20% of your people hold 80 to 90% of your best relationships- How to recruit advisors for their networks and turn them into a repeatable channel- How to use suppression lists and a "top 1%" vouch exercise to capture what's in people's headsChapters:00:00 Intro00:43 Who is David Connors02:04 What The Swarm does and the Sequoia origin story04:26 The $10M+ pipeline play and the tech stack05:35 Connectors and passive network mapping08:05 Warm vs in-market: carving out target accounts10:14 Finding warm intro paths inside Clay14:09 Building a hit list with the Claude MCP15:52 Attributing pipeline to network intros17:42 Why the top 20% of contributors is enough19:15 Chrome extension: ranking 300 mutual connections20:36 How relationship strength scoring works22:21 What sets The Swarm apart24:50 The three intro plays: direct, indirect, mention27:51 Lessons: batch asks monthly, train your cap table30:16 Network-led GTM: recruiting advisors for their networks32:11 Stacking warm intros with ads and outbound34:03 Suppression lists and Sequoia's top 1% vouch exercise36:10 Using network data for recruiting37:10 Will AI agents replace relationship selling?40:36 Wrap-upAbout David ConnorsCo-founder and CEO of The Swarm. Previously founded Automately (acquired by Sequoia Capital), then built network-mapping tools inside Sequoia that became The Swarm.The Swarm: https://www.theswarm.comSwarm MCP for Claude: https://www.theswarm.com/integrations/mcpLinkedIn: https://www.linkedin.com/in/connorsdavid/About the hostJonathan "Coach K" Kvarfordt, GTM AI strategist and host of the GTM AI Podcast.GTMAIpodcast.comTools mentioned: The Swarm, Clay, Claude, Claude MCP, Attio, Google Workspace, HubSpot, Salesforce, Clarify, ZoomInfoFree resource: Get the Warm Intro Engine, a copy-paste Claude skill that runs David's monthly warm intro play with your own LinkedIn exports. Link at GTMAIpodcast.com#GTMAI #WarmIntros #RevenueAI
39 MIN
SEP 23, 2026
He Built a $500K Business Solo With Claude Code (No Coding)
https://www.gtmaipodcast.comMark Fershteyn calls himself "a dumb sales guy with too many ideas." He ran sales at App Academy, founded Recapped, raised $8M, built a 26-person team, reached seven figures, and eventually shut it down and returned money to investors.Then AI changed the math. For his whole career, building an idea meant raising money and hiring engineers. Now he builds it himself.In this episode, Mark shares his screen and walks through:How to keep up with AI without burning out (filter for step changes)Why he starts almost every session in plan modeThe "one agent per task" rule and his 6-agent content pipelineA skill built from 300 LinkedIn posts that interviews him, drafts, and scores 5 hooksHow he structures folders and a personal wiki so AI can find everythingZealos: 5 calendars, every inbox, every DM, website visitor identification, and sequences in one appThe revenue: a $500K run rate in 6 months, solo, part-timeBuild vs. buy vs. hire, and where the software market goes nextIf you are not technical and you think this stuff is out of reach, watch this one.Chapters00:00 Intro: Mark's second time on the show01:11 From VP of Sales to an $8M-raised founder02:10 Founder tip: don't create a new category02:40 Why AI changed everything for a non-technical builder04:03 How to keep up without drowning05:14 Filter for step changes, then build something05:58 AI as playtime07:00 What you'll learn: skills and a real build08:15 Claude Code in the terminal vs. the app09:24 Use AI to use AI: start in plan mode10:26 One agent per task11:31 The prompt that builds your content agent system12:20 Coach K's rule: four rounds of feedback13:07 Treat your agent like an intern13:30 The 300-post LinkedIn skill14:08 Make every skill improve itself14:49 Building an AI CMO (plus a video editing tool tip)16:00 Folders, GitHub, and the /clients folder17:08 Hierarchy vs. graph: building a personal wiki18:58 Zealos: the super app20:39 From 20 tabs to one view21:58 Identifying website visitors and enrolling them in sequences23:05 From personal tool to product24:20 The revenue impact25:16 4 years and 26 people vs. 6 months solo26:00 UI vs. chat: everyone gets a Jarvis29:20 Build vs. buy vs. hire30:41 SMBs build, enterprises buy, the middle gets squeezed32:00 The build-happy pendulum32:37 Where to find MarkLinksMark on LinkedIn: https://www.linkedin.com/in/markfer/Mark's links: markfersh.comMastering AI: masteringai.ioZealos: zealos.ioPalmier (video editing via Claude Code, mentioned by Coach): palmier.ioRemotion (video editing, mentioned by Mark): remotion.devFree Content Engine skill: https://www.therevenueaireport.com/agent-skills/content-engine-suite
34 MIN