Where the complaint lives
A competitor's customer base writes down the exact reason they left, in public, for free. Review sites, app stores, forum threads, and support communities all carry customers describing a problem in their own words, before anyone edited it into a case study. That raw complaint is the input this method runs on.
| Source | What it surfaces | How to filter it |
|---|---|---|
| G2, Capterra, Trustpilot | Detailed B2B software complaints, often several sentences long | Sort to lowest star rating, newest first |
| App Store and Play Store | Consumer-product frustration, usually shorter and blunter | Filter to 1 and 2 stars, recent versions only |
| Reddit and niche forums | Candid switch-away and cancel posts, unfiltered by a vendor | Search the competitor's name plus 'switched from' or 'canceled' |
| Public support communities | Users troubleshooting in the open before opening a ticket | Search the product name inside Discourse, Discord, or Slack communities |
Read for the sentence, not the score
A star rating tells you a customer was unhappy. It does not tell you why. Skip the rating and search the review text for the sentence that names the actual failure: a missing feature, a broken workflow, a support gap, or a price that stopped making sense once the product proved its limits.
- Search the review text for phrases like 'switched to,' 'had to hire,' 'still doing this manually,' 'support never,' or 'canceled because.'
- Copy the sentence itself, not a summary of it, into a tracking sheet next to the source link and the date.
- Group sentences that repeat the same failure. One customer's complaint is an anecdote. Five customers naming the same gap is a pattern worth a guest.
- Skip complaints about price alone. A guest cannot fix 'too expensive.' A guest can fix the workflow gap that made the price stop being worth it.
From complaint pattern to guest shortlist
A repeated complaint points at a specific problem, and the guest is whoever already has a public answer to it: the practitioner who wrote about the workaround, the consultant quoted solving it, or the founder of a tool built to close exactly that gap. Search the complaint's own language, not the competitor's name.
| What the reviews repeat | Where to find the guest | Confirm before pitching |
|---|---|---|
| "Still doing this part manually" | Process posts, workflow templates, or comparison write-ups about that exact task | They solved it themselves, not just described the theory |
| "Support never responded" | Operators who built an internal escalation process or a public support playbook | They can speak to the fix, not just the frustration |
| "Switched away and regretted it" | People who compared both tools in public and can speak to the tradeoffs | They are not paid by either vendor |
| "Priced us out once we scaled" | Operators who write about the build-versus-buy call at that scale | The story is current, not a years-old post |
The pitch writes itself
A pitch built on a mined complaint does not open with your show or your download count. It opens with the sentence the customer wrote: your industry keeps naming this problem, and you want forty minutes with someone who has actually solved it. That reads as a real question, not a booking form.
Some names on that shortlist double as prospects too, not only interview subjects. Using the podcast as a lead source covers how to keep the fit-for-the-show question and the fit-for-the-meeting question separate, since a guest who solves the complaint and a guest who could buy from you are not always screened the same way.
Build the sheet once, mine it every quarter
The extraction sheet does not reset after the first booking. A competitor's product keeps shipping, their reviews keep arriving, and the same read produces a new name without starting the search from a blank page. Revisit the same sources on a schedule instead of only when a guest slot opens up.
Pod Green Room holds each mined complaint, source link, and shortlisted name as a guest pipeline, so the names from this competitor's reviews and the next one that surfaces after their next product update sit on the same board instead of a spreadsheet you have to rediscover. Pod Green Room queues the outreach on each shortlisted name as guest tracking, so a strong candidate found in a one-star review does not sit unpitched because the sheet closed and stayed closed.
Not the same read as a rival's guest list
A competitor's own guest list shows who already agreed to talk about their world. Their customer reviews show who is currently struggling, and who already knows how to fix it. Mining a rival's guest roster for gaps reads their booked names for whitespace; this method reads their customers' words for a problem nobody on that show has solved on air.
Where the shortlist goes next
A shortlisted name is not a booked guest. Once you have the complaint, the person, and the pitch angle, prep the interview the same way you would any specialist booking, working from what they solved rather than what the review said about them.
The 60-minute guest research sprint is the next hour once the shortlist has a name worth booking. It turns the complaint you mined into the specific questions only this guest can answer, instead of a generic interview about a problem they already solved somewhere else.