The inbox model for podcasts
Why Reducer is built around an inbox you fill over time, not a recording session.
Most podcast tools assume you sit down, hit record, and publish. That works for an interview show. It’s the wrong shape for a personal podcast — the kind you make for yourself, out of the things you’d rather listen to than read.
When we started building Reducer, the obvious design was a single sitting: gather your content, make the audio, publish. Clean. Simple. Wrong.
The problem is that the good stuff doesn’t arrive all at once. You read an article over coffee. A thought lands on the walk back. At night you ask your assistant to summarize something and think, “I’d listen to that tomorrow.” These are separate moments. Forcing them into one sitting means either losing the late-night one or staying up to assemble the whole thing by hand.
So we built an inbox.
How it works in practice
Every show has an inbox. Things go in whenever they come up. The inbox just holds them. When you’re ready, you compile — on a schedule, or whenever you feel like it. Reducer takes what’s in the inbox, voices it, and clears what it used.
The compile step is the only moment that matters for timing. Everything before it is just the inbox catching what you toss in.
So a daily-brief show can fill up all week from wherever you happen to be: an article you saved, a note from your phone, a summary your AI assistant dropped in mid-conversation. None of it has to line up. It all just lands in the inbox, and the next episode picks it up.
The compile boundary
One thing surprised us: the compile step turned out to be useful, not just necessary.
It gives you a moment to be deliberate. Glance at what’s in the inbox, reorder a few things, pull out something that aged poorly. You don’t have to. The default is compile everything. But the option’s there when you want it.
On a schedule, you never look at it; the episode shows up on its own. For a personal show you care about, sometimes you do.
That’s the model. Try it.