Play 55 · Software, web and AI
You described the problem on a podcast
A six-step play for a B2B software company or agency. It starts from YouTube, stacks Firecrawl on top, and ends in a message to the podcast guest that is useful before anyone replies.
Installs this workflow, five project tables and a draft campaign. Source access and any external outputs are checked before research.
- Category
- Software, web and AI
- Sources
- 2
- Steps
- 6
The workflow
- Trigger
YouTubeEpisode transcripts - Evidence
- ArtifactWhat you hand overA worked solution to the exact problem the guest described, in their terms.
- ContactGliderFinds the podcast guest, with a verified work email and a phone
- MessageSend itFrom your own mailboxes, evidence attached
Why it earns attention
When someone describes a problem on a podcast, they have already said what hurts and in what words. A solution to that exact problem, built from what they said, is hard to ignore.
The play in six steps
- 01
Find the problem in their words
YouTube- What you pull
- Episode transcripts where a guest describes a problem in your area: the quote, the timestamp and the episode date.
- Why it matters
- Their own words are the most persuasive thing you can quote back. The timestamp makes it checkable.
Example"Onboarding takes three weeks because every customer sends data in a different spreadsheet" · 24:10
- 02
Understand their business
Firecrawl- What you pull
- The guest's company site: product, customers and the formats or tools they mention.
- Why it matters
- It tells you what a working solution has to look like for them, not for a generic customer.
ExampleB2B logistics software · customers send CSV, Excel and an ERP export
- 03
Build the solution
Your artifact- What you build
- A working version of the fix for the three formats they mentioned, using sample files.
- Why it works
- It shows instead of tells. The guest sees their problem solved in a demo.
ExampleImporter for 3 formats · maps columns automatically · 2-minute demo
- 04
Check before you send
Quote them exactly and link the timestamp. Don't reach out about a problem they said they already solved later in the episode.
- 05
Find the podcast guest in Glider
Glider- Search for
- The guestHead of customer successVP operationsCTO
- Why them
- The guest owns the problem they described. Customer success runs onboarding day to day.
- What you get
- A work email and a direct phone, with the email verified before it goes into a sequence.
- 06
Send the evidence, then run the first test
To: the podcast guestEvery line comes from a step above On the episode last month you said onboarding takes three weeks because every customer sends data in a different spreadsheet format.1 Your customers mostly send CSV, Excel and an ERP export.2 I built an importer for those three formats. Here's a two-minute demo using sample files.3 Want to try it on a real one?
- Facts from the data (the number is the step)
- What you built for them
- One small ask
- Why it works
- It quotes them, solves the thing they said hurts, and asks for one file, not a meeting.
- First test
- Twenty guest quotes describing a problem the product solves.
- Success looks like
- Three trials out of ten guests.
The sample message is hypothetical and its numbers are illustrative. Verify every claim, date and rule before sending.
Sources used
The two sources this play names. Each links to the other plays that use it.
Related plays
3 sources · 7 stepsPlay 10Software, web and AIForNiche software companiesToThe person who askedYour competitor keeps telling these buyers they can't help
3 sources · 7 stepsPlay 52Software, web and AIForGEO agenciesToThe head of marketingAI search mentions your competitors and not you
4 sources · 8 stepsRun this play with Glider.
Deploy the full workflow into a project. Conway checks your scope and source access, builds the evidence, and prepares outreach for review.