Growth · 14 min

Podcast-Led Growth

Using podcast tours as a top-of-funnel channel.

One great podcast can outperform a quarter of paid — if you pick the right ones and follow up.

tl;dr
  • Podcast tours work when Clay scores guests and 11x books 20% to 35% faster.
  • One operator, Attio, and n8n beat a 4-person SDR pod for guest ops.
  • Framer + Relume turns each episode into 1 landing page, 3 clips, 1 CTA.
  • PostHog + Northbeam should attribute 60%+ of assisted pipeline, not just clicks.
  • Cold pitch volume dies; a 2026 rule is 50 targets, 1 narrative, 1 CTA.
Action plan
Action plan0/3 · 0%
Progress saved locally. Sign in to sync

Strategy and positioning

Podcast-led growth only works in 2026 if the show is a distribution asset, not a vanity badge. Use Clay to rank 200 hosts by audience overlap, buyer density, and social reach, then push the list into Attio as the single pipeline. Common Room and Keyplay should validate whether a host’s listeners already touch your ICP in PLG or community channels. The agent loop is simple: Clay enriches, Claude 4.5 Sonnet drafts the angle, and 11x books the first 20 qualified guests. A strong podcast tour needs 1 narrative, 3 proof points, and 1 CTA. If the pitch needs 4 follow-ups, the angle is wrong.

  1. 01

    Build the host graph

    Use Clay to pull 200 hosts, then score with Common Room, Keyplay, and Apollo AI for audience fit, LinkedIn velocity, and category relevance.

    Clay prompt: 'Rank hosts for CFO SaaS buyers, 2026 audience overlap, and guest frequency >6/mo.'
  2. 02

    Define the episode offer

    Write 1 positioning memo in Claude 4.5 Sonnet and store it in Attio; every pitch should map to 1 buyer pain and 1 measurable outcome.

    Prompt: 'Turn this founder story into 3 podcast angles with one CTA to a 14-day trial.'
  3. 03

    Automate qualification

    Trigger n8n when Clay finds a match, then let 11x or Lindy send the first outreach and route replies into Attio by source.

    n8n flow: Clay row updated -> 11x draft -> Attio task -> Slack approval.
IfThen
a host audience overlap score is below 60/100do not pitch; find a sharper ICP or a different category angle in Clay.
the CTA cannot be stated in 12 wordsrewrite the offer before booking any episode in Attio.

Guest pitch and booking

Guest booking is a workflow problem, not a persuasion problem. Clay plus Apollo AI should enrich every target with recent episodes, funding, and trigger events, then Relevance AI can generate 3 pitch variants per persona. Use 11x or Lindy to send the first wave, book meetings, and log objections into Attio. For replies, Claude Code should query Attio and PostHog so you can see which angles convert by host type, segment, and topic. Dead tactic: manual mass emailing from a generic inbox. Winning tactic: 50 targets, 3 angles, 1 acceptance path, and 1 calendar link backed by a real event reason.

  1. 01

    Enrich every target

    Clay should pull title, company stage, recent interview topics, and social proof; Apollo AI adds intent and contact validation.

    Clay prompt: 'Find podcasts where this founder can credibly discuss AI RevOps and pipeline attribution.'
  2. 02

    Generate three pitch angles

    Use Relevance AI or Claude 4.5 Sonnet to create 3 versions: contrarian, tactical, and data-led; store them in Attio.

    Prompt: 'Write 3 podcast pitches for a B2B growth guest with one sharp hook each.'
  3. 03

    Book and track replies

    11x or Lindy handles first contact; n8n updates Attio stage and posts booked slots to Slack for review.

    n8n rule: reply contains 'yes' -> Attio status 'Booked' -> task assigned to operator.
IfThen
reply rate is below 8%change the offer or the host list; do not increase volume.
a host asks for a generic biosend a 3-line angle sheet, not a longer email thread.

Production and distribution

A podcast episode without a distribution system is just an expensive transcript. Build the production loop in Framer + Relume, then reuse the episode page as the canonical asset for clips, summaries, and CTA capture. Runway or Google Veo 3 can turn one recording into 3 social cut-downs, while Clay plus Claude 4.5 Sonnet should extract quote-level segments and topic tags. PostHog tracks scroll depth, click-through, and demo intent; Northbeam reads paid retargeting lift from listeners who return later. The rule is simple: every episode must ship 1 page, 3 clips, 1 email, and 1 retargeting audience within 48 hours.

  1. 01

    Publish the canonical episode page

    Use Framer + Relume to create 1 page with title, summary, clips, and a hard CTA; keep the template identical across episodes.

    Framer prompt: 'Create a podcast episode page with one demo CTA and one newsletter CTA.'
  2. 02

    Extract clips and quotes

    Use Runway or Google Veo 3 plus Claude 4.5 Sonnet to cut 3 clips and mark 5 quotable moments for social and email.

    Prompt: 'Find the 5 strongest 20-second clips that mention pipeline, attribution, or buying triggers.'
  3. 03

    Measure behaviour

    Install PostHog events for play, scroll, CTA click, and form submit; Northbeam should attribute retargeting-assisted sessions.

    PostHog event: `podcast_cta_click` with `episode_slug=podcast-marketing`.
IfThen
the episode page does not hit 3% CTA click-throughtighten the headline and move the CTA above the fold in Framer.
a clip does not create 2x more saves than the full postreplace it; weak hooks do not deserve distribution.

Attribution and RevOps

Podcast-led growth fails when RevOps cannot connect listeners to deals. Use Attio as the system of record, PostHog for on-site behaviour, and Northbeam for assisted touchpoints; then let Claude Code or Cursor query the warehouse for source paths and episode cohorts. A small MCP server should expose Attio, PostHog, and calendar objects so the agent can label deals by host, guest, and topic. You do not need Salesforce-style complexity; you need 1 clean source, 3 events, and 1 weekly review. If an episode drives meetings but not opportunities, the CTA or ICP is wrong, not the dashboard.

  1. 01

    Wire the data model

    Create Attio fields for host, guest, episode, source, and CTA; sync PostHog and Northbeam identifiers into the same account record.

    Attio field rule: `source_detail = podcast::{host_name}::{episode_slug}`.
  2. 02

    Build the SQL views

    Use Cursor or Claude Code to generate 3 SQL views: episode-assisted deals, host cohort conversion, and CTA-to-opportunity lag.

    Prompt: 'Write SQL for deals influenced by a podcast page view within 30 days.'
  3. 03

    Run the weekly retro

    Every Monday, review the 5 best and 5 worst episodes in Attio, then adjust messaging, host tier, and CTA placement.

    Weekly query: `top_5_episodes_by_opp_created_last_30d`.
IfThen
listener-to-lead matching falls below 70%fix identity resolution in Attio before scaling more outreach.
Northbeam shows paid lift but PostHog shows no CTA clickstreat the lift as retargeting only and do not credit the episode alone.
Pitfalls

What goes wrong

Mistake

Treating the podcast as a brand project with no weekly pipeline owner.

Fix

Assign 1 operator, 1 Attio dashboard, and 1 Monday review with booked guests and opps.

Mistake

Pitching 500 hosts from a raw list with no Clay scoring.

Fix

Filter to 50 qualified targets per month and enrich with Clay before any 11x outreach.

Mistake

Publishing episodes without a Framer landing page and a single CTA.

Fix

Use 1 reusable Framer + Relume template and keep the CTA identical for 10 episodes.

Mistake

Judging success by downloads instead of PostHog and Attio outcomes.

Fix

Track play, CTA click, booked call, and opportunity created as the only 4 signals.

Mistake

Hand-logging podcast data in spreadsheets and losing host history.

Fix

Sync every host, guest, and reply into Attio via n8n or Trigger.dev.

FAQ
How many hosts should a 2026 podcast tour target?

Target 40 to 80 hosts per month, not 400. Clay should score the list first, then 11x or Lindy should handle the first send. A tighter list beats volume because host fit, audience overlap, and a clear CTA matter more than raw outreach count.

What is the best stack for podcast-led growth?

Use Clay for enrichment, Attio for the pipeline, Framer + Relume for landing pages, PostHog for behaviour, and n8n for workflow. Add 11x or Lindy for outbound and Cursor or Claude Code for RevOps SQL. That stack removes 3 manual jobs and keeps the loop auditable.

How do you know if a podcast episode actually worked?

If PostHog shows CTA clicks, Attio shows new opportunities, and Northbeam shows assisted return visits, the episode worked. Downloads alone are noise. A strong benchmark is 2% to 6% episode-to-demo conversion and $25k to $150k in assisted pipeline.

Should founders do their own guest outreach?

Founders should record the angle and approve the first 10 pitches, but not send every message. In 2026, one operator plus Clay and 11x does the booking work better than a founder spending 6 hours in Gmail. The founder’s job is the narrative, not the inbox.

When should you stop podcast-led growth?

Stop if 10 episodes produce less than 3 meaningful opportunities, or if the CTA never reaches 3% clicks in PostHog. At that point the offer, host tier, or ICP is wrong. Do not scale a channel that cannot prove assisted pipeline in Attio.

Get one system like this in your inbox each week

No fluff, no upsell. Unsubscribe anytime.