エピソード

  • AEO vs SEO: How to Measure AI Search 4 Signals
    2026/11/19

    https://www.gtmaipodcast.comIn this episode of the GTM AI Podcast, I sit down with Brittany Trafis, Co-Founder and CEO of Soarion Digital. She has spent more than 20 years in technology and marketing, and AI search is the only thing her company does. We met on a CMO Huddles road trip through Texas, where she analyzed every attendee's website for AI search performance. She shares her screen and walks through Soarion OS, the agent platform her team runs client work on. We cover:AEO vs SEO: AI search is a new channel "Call it AEO, AI search, AIO, whichever acronym. People searching with AI is a new channel." Why nobody ran Facebook ads like Google Ads, and what changes when a buyer types three or four sentences about their budget and pain points in place of a few keywords.20 agents for every human Soarion tracks agent traffic on its own site and sees 20 agents for every human visitor. What those agents are doing (indexing, retrieving, completing tasks), the tickets Brittany bought through Meta's Muse agent without visiting a website, and why an unready site means "game over."How to measure AI search Why Brittany can attribute one lead a month to AI search by click, and the four signals she reads together to see the real picture: presence, citations, branded search and referral source.Citations and the upper funnel "Citations are becoming gold." Why being the cited source comes before being the recommended vendor, and why the educational content most teams ignored is where buyers now start.PR, third-party sites and one narrative What stayed consistent while the Reddit hype came and went, and how a large enterprise gets conflicting product-line messaging onto one page by starting with a single product line.Strategy vs. slop What happens to teams that publish several pieces a day ("You'll get your peak, and then you're gonna plummet"), the release cadence Brittany called "the perfect strategy," and the stat she shared: 50% of the content LLMs cite is less than 13 weeks old.Human sites and AI sites Why Brittany expects the web to split into sites for people and sites for agents, and the agent-only site her team is experimenting with.Live demo: Soarion OS The agent teams behind the platform (audit, strategy, content, measurement), how clusters work as a hub with spokes, and where visibility platforms such as Profound and Scrunch plug in.Personas, platforms and focus Why a finance buyer points you at Copilot and away from Grok, why Soarion works only 2 to 3 clusters at a time, and why chasing 80% presence on one prompt misses the business.The 90-day turnaround An anonymized B2B client that was down to about 10 leads a month and reached 40 within 90 days, starting from the fact that AI could not reach their site.FREE FROM BRITTANY: THE AI SEARCH PRESENCE REPORTHer team runs the questions your buyers ask through ChatGPT, Gemini, Claude and Perplexity and shows you which ones name your competitors and leave you out, how often each competitor is named and cited, and where to focus first. Free, delivered in two business days, no obligation. https://soariondigital.com/ai-presence-report

    続きを読む 一部表示
    36 分
  • Context Engineering for AI Agents: The 3-Layer System
    2026/11/12

    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."

    続きを読む 一部表示
    50 分
  • How the Swarm Built $10M in Pipeline using Network Strategy
    2026/10/22

    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

    続きを読む 一部表示
    40 分
  • The AI Handoff Packet Most Teams Skip
    2026/10/07

    www.gtmaipodcast.com

    Marko Ladis runs an engineering team full time, consults on decision ownership, and hosts the Decision Load podcast. He is a solo operator, so he built three AI setups that handle the research, sorting, and production prep he refuses to do by hand. The rule across all of them: agents prepare, Marko decides. In this episode he walks through the real workflows, with anonymized outputs, and Coach K breaks down what GTM teams can copy.

    Links and resources

    Marko on LinkedIn: https://www.linkedin.com/in/marko-ladis/

    Decision Stability: https://decisionstability.co

    Decision Load podcast (YouTube, new episode every Wednesday morning, European time): https://decisionstability.co/decision-load

    続きを読む 一部表示
    53 分
  • How to make LLM’s Deterministic like Jev from an AI Researcher
    2026/10/01

    www.gtmaipodcast.com

    Same customer. Same data. Same prompt. High value on Monday, low value on Tuesday. Elin Nguyen hit that wall trying to vibe-code a sales intelligence tool, and it turned her into an accidental AI researcher. She explains interpretation drift, why "don't hallucinate" and "think step by step" barely move results, and how substrate engineering got GPT, Claude, Gemini, and Grok to return byte-identical output. If you run AI inside a revenue team, this one changes how you write prompts.

    https://www.gtmaipodcast.com

    続きを読む 一部表示
    43 分
  • He Built a $500K Business Solo With Claude Code (No Coding)
    2026/09/23

    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

    続きを読む 一部表示
    35 分
  • 200 AI Agents to 10: How a Founder Runs 90% of GTM in Claude
    2026/09/16

    https://www.gtmaipodcast.com

    Eli Portnoy has spent 15 years in AI across three companies. ThinkNear was acquired by Telenav, Sense360 by Medallia, and BackEngine.ai is the one he says he is not planning to sell. The premise of BackEngine: AI needs context, most company data is siloed and inaccessible, so BackEngine structures, permissions, and indexes private company data so every AI instance can use it.

    On this episode Eli shares his screen and walks through how BackEngine runs 90% of its go-to-market inside Claude.

    What you'll hear:

    • The connector stack. BackEngine, Fireflies, Gmail, Calendar, Granola, HubSpot, Notion, Slack, Superhuman, Zoom, plus a few vibe-coded MCP servers (website stats). The SaaS tools didn't go away; they moved inside Claude.
    • The scheduled jobs that survived. Founder Sales Daily Pulse (4pm outreach scan), end-of-day follow-up audit from transcripts, product-market fit review every 20 prospect calls, and weekly deal/customer health change alerts.
    • Why a direct CRM connector misses deals. Context windows force the model to sample. Eli's estimate: about 30% of the relevant data gets read. Joining systems, building an index, and permissioning at the data layer fixes it.
    • How to measure AI ROI when it's hard to attribute. The "30% smarter pill" thought experiment, and why scheduling turns AI from single-player into multiplayer mode.
    • Three mistakes. Capabilities weren't ready (jobs needed a computer on and permissions every run), running 200 jobs nobody read, and treating adoption as a technology problem instead of change management.
    • Two change-management rules. Fewer jobs with owners, and no job without a workflow attached.
    • Artifacts as dashboards. Rebuilding the siloed SaaS views (customer health by tier, account health, case studies) as shareable Claude artifacts.
    • Prompt vs. project vs. skill vs. plugin. Eli's 20-second taxonomy.
    • State of the market. 5-10% of employees in most companies are power users; 90% use AI lightly or for emails. Causes: fear, habit, immature tooling, no formula.
    • Advice for individuals. Play with it, give it context like you would a new hire, review every output, tell it to be concise.
    • The next 12 months. Chat becomes the central work surface; expect non-model-provider layers (Manus, Instinct) to compete on the machinery around the model; voice and other interfaces are coming. Eli's analogy: early TV filmed radio booths.
    続きを読む 一部表示
    35 分
  • The $1,800 Lead: Why Your Social Media Ads Keep Failing
    2026/09/02

    https://www.gtmaipodcast.comJoel Horwitz ran product-led growth for all of IBM, led growth at Sourcegraph, and now runs Synter, an ad platform operated by AI agents. In June he ran a LinkedIn campaign that came back at $1,800 per lead. In this episode he shares his screen and shows exactly why that happens, why it took him six months to figure out, and the workflow he uses now instead.

    You'll see the one-prompt "demand capture" workflow that turns your zero-click organic keywords into exact-match paid campaigns, the LinkedIn API tier problem that quietly sends your budget to Walmart employees and BDRs, the organic-first playbook that took Synter from 0 to 2,500 followers with no ad spend, how to scope permissions for agents that can spend money, and a warning about malicious skill files.

    Real screen share. Real numbers. No theory.

    🎙️ GTM AI PODCAST More episodes, the newsletter, and the community: https://gtmaipodcast.com

    👤 GUEST: JOEL HORWITZ Synter: https://syntermedia.ai/ Joel's DMs are open on X

    続きを読む 一部表示
    36 分