Case studies

What happens when the pitch is grounded in something they actually said.

Hosts who book better guests do not send more pitches. They send pitches that reference a specific moment from a specific appearance and make the case for a conversation that has not been had yet.

The examples below are illustrative, drawn from realistic usage patterns. Identifying details have been changed.

Founder-led show · B2B SaaS

She replied within four hours. She said the angle I raised was the exact tension she had been trying to articulate for two years.

The host ran HADEF on a VP of Product he had been trying to book for six months. The pipeline surfaced a keynote from a developer conference where she described the gap between roadmap velocity and organizational trust. The pitch opened on that specific moment. The response came the same day.

4 hours to first reply
Independent podcast · Communications & PR

I had pitched him twice before with templated messages. The HADEF pitch was the first one he actually responded to.

The research agent found a Substack post where the CCO had written about the difference between crisis communications and consequence communications — a distinction he had drawn himself but never been asked to develop on a podcast. The pitch led with that framing. He booked a call three days later.

Third outreach attempt, first response
Studio network · Leadership & strategy

We went from 14% response rate to 31% in six weeks. The QA check alone changed how we think about what a pitch is.

A studio running three shows started routing all guest outreach through HADEF. The transcript cache meant repeat targets across shows cost nothing extra. The QA verification flagged pitches where the hook quote could not be verified — which turned out to be a larger percentage than expected. Fixing those systematically moved the response rate.

31% response rate (up from 14%)
What the pattern shows

The pitch that works is not the pitch that flatters.

Across every use pattern, the common thread is the same: a pitch that opens on something the guest said — a specific quote, a specific tension, a specific moment — outperforms a pitch that summarizes their career. The research does not need to be exhaustive. It needs to be accurate. One verified quote from one real appearance is worth more than three paragraphs of general praise.

Response rate is a quality signal, not a volume signal.

The studio example shows what happens when you fix the pitch before you send it, rather than after you fail to get a reply. The QA verification exists for this reason: to surface the pitches where the hook quote is not actually in the transcript, where the source URL is dead, where the specificity would not survive scrutiny. Fixing those before sending is the entire model.

The transcript cache compounds over time.

The third time a guest appears on a source you have already extracted, the pipeline is instant. The Supabase transcript cache is shared across all your pitches, and the cost is amortized across every future run on the same source. Studios and networks see this compound fastest — a guest who appeared on three shows in your portfolio has their transcripts cached after the first pitch.

Want to see it on a specific guest?
Run a free pitch and see what the pipeline finds. Start here.

Run it on your next guest.

Three free pitches. No credit card. Sixty seconds to the first one.

Start free How it works