Resonant + Substack
Talk the first draft.
Ship on cadence.
The hard part of a weekly newsletter isn't the idea. It's the drafting grind that takes two hours every time and eats the morning you were supposed to use for something else. Voice turns that grind into a conversation.
Resonant runs entirely on your Mac. Press a key inside the Substack editor and talk. Clean prose — not raw transcript — lands in your draft, ready to edit. No cloud audio. No plugin.
Used by professionals at
Typed vs. dictated
Typed drafts sound polished.
Spoken drafts sound alive.
Opening paragraph
“This week I want to talk about why hiring your first engineer is harder than people think.”
“I've been arguing about this with three different founders in the last two weeks, so apparently it's time to write it down. Every single one of them is about to make their first engineering hire, and every single one of them is underestimating how much the first hire is going to shape everything that comes after. Not just the codebase — the hiring bar, the review culture, the way you talk about quality for the next three years. I want to walk through why that is, what I wish I'd understood the first time I did it, and how to decide whether you're actually ready.”
Story section
“A few years ago I worked with a founder who made the classic mistake of over-hiring before product-market fit.”
“A few years ago I was advising a founder who'd just raised a fifteen million dollar Series A. Smart guy, good idea, great timing. Within four months he'd gone from six people to thirty-one, because the board told him to and because that's what you're supposed to do after a Series A. Six months after that, he was doing layoffs, the product had stopped shipping, and the engineering leads he'd hired were openly interviewing. The thing I remember most clearly is a conversation we had in a coffee shop in Hayes Valley where he told me he didn't know any of his new hires' last names. Thirty-one people. He didn't know their last names.”
Call to action close
“If this was useful, share it and subscribe.”
“If any of this resonated, the most useful thing you can do is send it to the one founder in your life who's about to make their first hire. I'm not interested in growth for growth's sake — I'm interested in this getting in front of the specific people who need to read it before they sign an offer letter they'll regret. If you're one of those people, hit reply and tell me about the role you're thinking about. I read every response and I'll push back if I think you're making the mistake I just wrote about.”
The insight
Cadence beats brilliance.
Voice protects cadence.
Newsletter writers know the real competition isn't other writers. It's your own weekly schedule. Miss one week and the rhythm is off. Miss two and you start to dread the inbox. Miss three and you're quietly drafting the apology post you'll never send.
The thing that breaks cadence is almost always the drafting grind, not the ideas. Ideas are cheap — you have three in the shower every morning. What's expensive is the two-hour sit-down where you turn the idea into nine hundred words that actually say something. That's the block in the calendar that keeps slipping, and slipping is how newsletters die.
Voice changes that math. A draft you can talk out in twenty minutes is a draft you can fit into the time you already have. The grind compresses. The editing pass stays short because what you said out loud already sounds like you. And the cadence, which is the only thing that matters long-term, holds.
You schedule two hours to write the post. The first thirty minutes go to staring at the blank document and rewriting the opening sentence. The next ninety go to typing something you'll mostly rewrite tomorrow anyway.
Then life happens, and the two hours become four.
Twenty minutes of talking produces roughly 3,000 words of reasonably clean prose. Half of it won't survive editing — that's fine. The other half is a real first draft, in your voice, and it's already in the editor.
You get to spend the rest of your time editing, not producing.
Where it fits
Six stages of a post
where voice wins.
First draft of a weekly post
The first draft is the thing that hurts. Voice turns a two-hour typing session into a twenty-minute conversation with yourself, which you can then edit at leisure instead of dreading all morning.
The personal story section
Stories read better when they sound like you telling them, not like you wrote them. Dictate the anecdote, keep the voice, and skip the instinct to over-edit the rhythm out of it.
The unglamorous middle section
Every post has a section nobody wants to write — the transition, the definitions, the setup. Voice gets you through it fast enough that you don't lose momentum before the fun part.
Reply-to-comment drafts
A real reply to a reader's comment is the difference between a newsletter and a community. Voice lets you write a five-paragraph reply in the time it would take to type two sentences.
Weekly recap roundups
Five links, one sentence each, your take on why each one matters. The format is fast to explain and slow to type. Dictate the explanations, paste in the links, done in ten minutes.
Interview follow-ups and transcripts
When you're turning a conversation into a post, voice is already the native format. Dictate the framing, the pull quotes, the context — let the medium match the material.
Architecture
Drafts stay drafts.
Audio stays on-device.
A newsletter draft is a pre-publication document. It has your unfinished thoughts, the claims you're still fact-checking, the quotes you haven't confirmed, the hot takes you might yet walk back. That's not something you want flowing through a third-party audio service that logs everything it hears.
Resonant runs every speech model locally on your Mac. Nothing is uploaded, nothing is streamed, nothing is logged by anyone other than the macOS processes you already trust. The only thing the Substack editor ever sees is the finished text, which only you can see until you publish it.
Compare this to cloud tools like Wispr Flow or Otter, which send your audio to their servers for processing. For paid subscribers reading over your shoulder — and for your own peace of mind — drafting locally is the default that makes sense.
Free. Local. Works in any text field.
Keep the cadence.
Lose the grind.
Voice drafting for Substack writers. No subscription, no cloud audio, no more lost Saturday mornings.
Requires macOS 14+ · Apple Silicon
Related