Podcast Launch for a Regional Mutual Aid Network
A grassroots network wanted to amplify member stories and reach beyond their immediate community. They had no media experience, a shoestring budget, and six weeks to launch.
The situation
A regional mutual aid network had been doing quiet, sustained work for three years — coordinating food distribution, emergency support, and community organizing across a seven-county area. They were good at what they did. Almost nobody outside their direct community knew they existed.
They came to us with a specific goal: use a podcast to document their members’ stories, share what mutual aid actually looks like in practice, and build connections with other networks doing similar work nationally.
Their constraints were real: no media experience anywhere on the volunteer team, a $400 total budget for equipment, and a self-imposed six-week deadline tied to an upcoming community event where they wanted to announce the launch.
What we did
Week 1 — Strategy and concept development: We spent the first week not touching equipment at all. Instead, we workshopped the show format: Who is it for? What would make someone keep listening? What stories does the network have that only they can tell?
We landed on an interview format — one host, one guest per episode, 25–30 minutes — focused on the specific mechanics of mutual aid: how did you set up the food distribution network? How do you handle conflict in a non-hierarchical organization? What does it look like when it works? This specificity was a deliberate choice. General “mutual aid is good” content was already out there. Granular, practical stories were not.
Weeks 2–3 — Equipment, setup, and recording environment: We recommended a single USB microphone (under $80), headphones they already owned, and Audacity for recording and editing — all free or one-time costs. The ongoing cost: $0 (using Spotify for Podcasters for hosting, which covers distribution to all major platforms).
We helped them set up a recording space in a volunteer’s home office (a closet adjacent to the main room, lined with bookshelves) and ran a test recording session to verify audio quality before the first guest interview.
Weeks 3–5 — Batch recording: We coached the host through the first three interviews, providing feedback after each. By the third recording, she needed minimal support. We then helped the team batch record episodes 4–8 over two consecutive Saturdays, building in the buffer they’d need to maintain a consistent publishing schedule.
Week 4 — Production workflow: We built a simple editing guide: what to cut (long silences, repeated false starts), what to leave (natural speech patterns, “um”s that flow with the conversation), and how to export. We also built their publishing checklist: episode title formula, description template, chapter markers, social post templates.
Week 6 — Launch: Eight episodes live on launch day. Show notes for each. A simple one-page website with an embed player and an email signup. Announced at the community event to an audience of 200+ people.
Weeks 7–12 — Handoff and support: Two training sessions with the volunteer who took over ongoing production. One session on editing in Audacity; one on the full publishing workflow. Recordings of both sessions left with the organization.
What changed
The numbers: 400+ subscribers in the first month, consistent listenership over the following six months, and an invitation to present at a national mutual aid conference based partly on the show’s reach.
The less quantifiable: the network now has an archive of their members’ stories in their own words. That has value that outlasts the subscriber count.
Several episodes were shared by other mutual aid networks and used in their own onboarding materials — which was, in retrospect, a better measure of success than download numbers.
What made this work
Two things: realistic expectations and batch recording.
We were clear from the start that the show would succeed or fail based on consistency, not production quality. An imperfect episode published on schedule does more than a perfect episode that comes out whenever. The batch recording approach meant they had a buffer before they’d developed a reliable solo production workflow. That buffer is the difference between shows that survive and shows that don’t.
The team’s willingness to start imperfect — to record the first episode knowing it wouldn’t be as polished as episode eight — was what made everything else possible.