Use case
Collaffy for Podcasters
Episodic deliverables, host-read CPMs, multi-episode flights. Podcast collabs have more moving parts than most — and lose the most when they're not tracked.
Podcast sponsorships look different from a one-off Instagram post. There are host-read CPMs, multi-episode flights, mid-roll vs pre-roll vs post-roll placement, ad-read scripts that need approval, and downstream questions about whether the spot ran clean. Tracking that in DMs or email is unreliable; tracking it in a creator-economy 'all-in-one' tool tends to mean a generic inquiry form that doesn't speak podcast vocabulary.
Collaffy gives each sponsor its own thread and each flight its own status. The intake form captures the brief at submission time; the inbox holds the conversation; the pipeline tracks whether the ad actually shipped.
Where it breaks today
- Multi-episode flights need real tracking — 'episode 1 of 4 aired clean, episode 2 has a scheduling issue, episode 3-4 not yet recorded' isn't an email-thread problem.
- Sponsor approval cycles (script → revision → final) get lost between Google Docs comments and Gmail replies.
- Repeat sponsors return three months later and you don't have a clean record of what was agreed last time.
- Agencies represent multiple brands; the same agency contact may submit on behalf of three different sponsors over a year.
Where Collaffy fits in
Each request becomes its own threaded deal. Multi-episode flights live under one request with status tracking; you can mark IN_PROGRESS when episode 1 records and COMPLETED only when the final episode airs.
Approval cycles happen inside the thread. Scripts, revisions, and final approvals stay attached to the original brief, not scattered across Gmail.
Repeat brands keep a record. When the same brand returns a quarter later, the prior request still lives in your inbox under its terminal status (COMPLETED, DECLINED, or NOT_INTERESTED) and is searchable by brand name.
Practical tips
Add your Collaffy link to your podcast show notes.
Most prospective sponsors find creators by listening, not by Googling. Show notes are where they land first — drop your Collaffy link with 'sponsor this show' as the anchor.
Use status to track multi-episode flights, not deals.
A four-episode flight is one request, not four. Use the status pipeline to track the flight's progress; use the thread to track per-episode delivery.
Ask for the ad-read intent in the brief.
Until configurable intake fields ship, use the existing free-text `brief` and `customDeliverables` fields to invite sponsors to specify placement (pre-roll / mid-roll / post-roll / host-read / dynamic insertion). Mention it in your show notes — 'please include preferred ad placement in the brief' — and you'll get the info up front.
Ready to drop a real workflow into your bio?
Claim your link