Most newsletter writers who come to us have the same quiet worry, right, which is that they are good at writing and have no idea whether they are any good out loud, and on top of that they already spend most of their week on the issue itself, so the last thing they want is a second job editing audio at midnight on a Sunday.
That worry is fair, and I think it is the reason so many writer podcasts start with a burst of enthusiasm and then stop a handful of episodes in, not because the writing was not interesting but because the format did not fit the writer and the workflow was heavier than anyone planned for. So this post is about the two decisions that sort that out, which format suits the way you already work, and how light the editing workflow can be made, and then how the podcast and the newsletter can push readers and listeners towards each other.
Should a newsletter writer read the issue aloud or have a conversation?
Read the issue aloud if your newsletter is essay driven and your voice on the page is the product, and choose a conversation if your newsletter is about a scene, an industry or a set of people you could be talking to instead of writing about.
Both formats work, they just ask different things of you. A reading show is close to an audiobook of your issue, you sit down with the text you already wrote, record it in one go and the edit cleans up the stumbles, so it costs you an extra hour a week at most. The downside is that readers who already read the issue get nothing new from it, so the audience for a reading show is mostly people who prefer listening, on a commute or a run, and people who never open emails.
A conversation show is more work to book and record, but it gives your existing readers something they cannot get from the inbox, which is you thinking out loud with somebody else, and to my mind that is the version that grows a writer's audience in new directions, because every guest brings a few of their own people along. I went through the general choice in the post on picking narrative or conversation before you record, and for writers the question really comes down to whether your readers want more of your voice or more of your world.
What does editing a read-aloud episode actually involve?
It is mostly about removing the stumbles and restarts without making the reading sound stitched together, levelling the voice so it is comfortable through earbuds, and adding a short intro and outro so it sounds like a show and not a voice memo.
Writers reading their own work tend to restart sentences when they trip over a word, which is completely normal, and the editor's job is to keep the clean take and cut the false start so the join is invisible. Where a human editor earns the fee is the rhythm, because a reading has a pace the writer chose on the page, short paragraphs land with a breath after them and long ones run on, and a tool that removes every pause automatically flattens all of that into a breathless wall of speech. We listen to the whole recording and keep the pauses that belong to the writing.
Reading shows are very often solo, so a lot of what is in the guide on podcast editing for solo shows applies, especially the bit about pacing, and if you want the version of that problem from the host's side, the post on why solo episodes drag is worth five minutes.
How do you keep a conversation episode from wandering?
By deciding before you record what the one idea of the episode is, and then letting the editor trim the parts of the talk that do not serve that idea, so the conversation keeps its warmth but loses the twenty minutes where everybody was warming up.
Writers are used to editing their own drafts hard, so this is the part they usually enjoy, right, once they see that the same instinct works on a recording. A good guest conversation might run seventy minutes raw and fifty finished, with the slow start trimmed, a long tangent about scheduling the call removed and the strongest exchange left completely alone. You stay in control of what goes, because you get the cut back and can ask for anything to be restored. What I would say is, do not over-prepare a script for these, because the reason people listen is that you sound like yourself and not like an issue being read by two people.
Your readers already know how you write, the podcast is where they find out how you think.
Is a newsletter podcast better as audio only or with video?
Start with audio if your readers mostly listen on the move and you hate being on camera, and add video if you want the show to find new people on YouTube, because video is where clips come from and clips are how most writers reach readers who have never seen the newsletter.
There is no shame in an audio only show, right, plenty of writers run one for years and it does exactly what they wanted. We edit audio only shows as well, and they are priced on a call because the work varies a lot from show to show. The trade-off is that audio does not travel as easily, a two minute vertical clip of you making a sharp point is far more shareable than an audio file, so if growth is the goal the camera usually pays for itself. If you do go video, a reading show can work on camera too, you just need a simple setup and a good light, and the general comparison is in the post on audio only versus video podcasts.
For distribution, the audio goes to your podcast host and from there to the apps, and if you want the video version on Spotify as well, Spotify for Creators is where that is set up.
How do the newsletter and the podcast actually promote each other?
Each one should hand the audience of the other a specific reason to cross over, the issue linking to the episode with one line about what you will hear that is not in the text, and the episode pointing back to the newsletter for the thing that only exists in writing.
The bigger strategy is in the post on building the podcast newsletter loop, so I will not repeat it, and what I want to add here is the editing side, because the loop only runs if every episode produces the assets the newsletter needs. Basically, a writer adding a podcast needs four things from the edit besides the episode itself. That is one, a short pull quote from the episode that works as a line in the next issue. Secondly, one or two vertical clips for social, so people who follow you there hear your voice. The third is chapters and show notes, so a reader who clicks through from the email can jump straight to the part they were promised, which is the kind of thing covered on the page for show notes and chapters written by your editor. And the fourth is a clean audio file you can embed in the issue itself if your platform supports it.
The wider idea of getting a month of material out of one recording is in the podcast repurposing strategy guide, which was written for exactly this kind of one person operation.
A light weekly workflow for a writer
The workflow that sticks is the one that adds about an hour to your week, record on the same day you finish the issue, upload before bed, and review the cut when you would otherwise be reading your replies.
Here is how that tends to look in practice. You finish your issue on a Tuesday, say, read it aloud or record your guest that evening, and drop the files in the shared folder before you log off. The first cut is waiting for you within two days, you listen while doing something else, note anything that bothers you in one message, and the fixed version is back a business day later, with the clips and notes alongside it. You never open an editing app, and the podcast goes out on Friday next to the issue, does that sound like a week you could actually keep up? Because that is the whole test, right, a rhythm you can keep for fifty weeks matters more than a perfect episode you manage four times.
The thing to avoid is deciding every week what the show is. Pick a format, an intro and a length, and keep them, so the edit becomes routine for us and the habit becomes routine for you.
What a writer usually pays to add a show
A reading show or a short solo episode up to 30 minutes is 150 dollars on the Starter plan, and if you publish every week the monthly plan brings the hour long Starter episode to the same 150 dollars, so a writer's show is usually one of the cheaper things we edit.
That covers the full human listen-through, levelling and cleanup, intro and outro, with clips and show notes as add-ons if you want them, and the full list of plans and packs is in the pricing section. There is no retainer, which matters for writers because newsletters change shape, a paid tier launches, a section gets dropped, a sabbatical happens, and the podcast should be able to pause with it. Pixel Samy Podcast bills per episode, so a month off costs you nothing, and on the monthly plan any episode you did not use carries forward a month.
When you should not hire an editor yet
If you have not recorded at least a few episodes yourself, or you are not sure the podcast is something you want to keep doing, edit the first three yourself with a simple free tool, because you will learn what you like and the money is better spent once you know the show will last.
I say this to writers often, right, because hiring an editor for a show you might abandon is a waste, and the first few episodes teach you a lot about your own voice that no editor can teach you. Once you have done three, you will know whether it is a reading show or a conversation, how long it wants to be and whether you enjoy it, and at that point handing off the edit is what turns it from a project into a habit. A freelancer on a marketplace is also a reasonable choice for a very simple reading show, as long as you are happy to manage them, and a team like ours makes more sense once there is video, clips and a weekly schedule to hold.
What I keep coming back to with writers is that the podcast should feel like another way of publishing what you already do well, right, not a second business, and when the format fits and the editing stays out of your week, the show quietly turns readers into listeners and listeners into readers, which is the only reason to start it in the first place. So yeah. That's my way of saying it.