Jimenez Julien

Why a booking desk for podcasts, of all things

I did not set out to build software for podcasters. I set out to help a friend who hosted a fortnightly interview show out of a converted garage in Ohio and kept losing his Sundays. He was not struggling with the recording, the editing or the writing. He was struggling with the twenty small administrative acts that sit between saying yes to a guest and pressing record: the scheduling thread, the time zone confusion, the bio that arrived as a paragraph in a chat window, the headshot that turned up at 400 pixels wide two hours before publication.

I sat in on four of his bookings and wrote down everything that happened. Ninety percent of it was retyping information a guest had already given him, in a slightly different form, into a slightly different place. That is the shape of a product. Not a smarter recorder, not another feed host, not one more place to write show notes. Just the desk that sits between the yes and the record, doing the retyping so a host does not have to.

MicPrep started as a shared spreadsheet with a form attached. The first ten shows used it because it was better than the thread they had. The first real feature request was the name recording, and it came from a host in Tucson who had mispronounced a guest's surname in a cold open and could not face re-cutting the intro a third time. The second was the required headshot field, because a producer in Ohio was tired of publishing with a screenshot. Almost everything in the product today came in through that door: a host writing to say that a specific Tuesday went badly, and why.

What I have learned about this trade

Independent podcasting runs on borrowed time. Most of the hosts I talk to have a full day job, a family, and a release day that never moves. They are not looking for a platform to live inside. They want a tool that does a narrow thing without asking for a new habit, and then gets out of the way for six days a week. That is why MicPrep does not try to be a content calendar, an analytics dashboard or a community. It books guests, collects what you need from them and hands you a sheet.

I have also learned that the guest experience is the whole product. A host is judged by the invitation. If the questionnaire feels like a corporate intake form, a good guest quietly decides your show is smaller than it is. So the form carries your artwork, your show name and your voice, and it is short enough to finish on a phone between meetings. Every field we add gets argued about, because every field costs completion rate, and completion rate is what buys a host their Sunday back.

The last lesson is about honesty in numbers. Hosts read a claim of hours saved and mentally halve it, and they are right to. So the figures on this site come from show accounts we can actually measure, stated as medians, with the comparison period named. When a number changes, the page changes.

How I work with hosts and producers

Every walkthrough is run on the caller's own show. We build their question set live, publish a real booking link and generate a real prep sheet from a test submission. They keep the question set whether or not they subscribe, because a good question set is worth having on its own. I do the walkthroughs myself, which limits how many happen in a week and keeps me honest about what the product actually does.

Support runs the same way. Messages come to one address, they are answered by me, and if the answer is that MicPrep is the wrong tool for a show, that is the answer that gets sent. Three or four times a year I ask a small group of hosts to sit with a rough version of something before it ships. They are paid for that time in months of service, and their names are never used in marketing without written permission.