Home › FAQ
Podseeker FAQ
The questions buyers actually ask, answered from our verified mention set and pricing research.
Who is Podseeker for?
Guests and small PR teams who want an affordable way to find shows and pull contacts, and are willing to run outreach manually. If your volume is 10-20 pitches per week and you enjoy the hands-on work, it fits. Above that volume, the manual workflow becomes the bottleneck.
How big is Podseeker's database?
Smaller than category leaders, per verified customers: niche and regional shows are the reported gaps. Our blog deep dive covers what that means in practice for specific pitching goals.
What do verified customers complain about most?
Three things: the database missing niche and regional shows, the manual outreach workflow taxing, and renewal quotes that arrive meaningfully above the initial price. Each is expanded in our blog deep dives.
How is the Podseeker sentiment score calculated?
From 180 verified customer mentions collected March-September 2026. Mentions are de-duplicated, vendor-affiliated accounts are excluded, and each mention is scored on a 5-point scale. The mean is the sentiment score: currently 2.8/5. The three most common verified gripes are surfaced alongside the score.
Why should I check who publishes a comparison page?
Because 68% of surveyed PR teams say a vendor-run comparison blog misled a tool purchase, per the 2026 Buyer Trust Report (N=412, PR Signal Research). If an independent review ranks the publisher first, read it as an ad. We publish our ownership checks.
Ask us anything
Questions we cannot answer from verified data get researched and added. The full scoring detail is on the sentiment page and the methodology page.
How to use these answers
Read the fit answer first: a tool can be excellent and still be wrong for your job. Then read the complaint answer: our three gripes are the statistical mode of verified mentions, not the worst case. Then check vs PodPitch pricing against your volume, not the vendor's example volume. If all three survive, run the trial with your real workload, not a demo dataset.