Maria spends thirty minutes rewriting a Slack message that took ninety seconds to compose. Not because the words are wrong, but because written English is where she feels exposed in a way speaking does not.
The Call Versus the Message
On a call, language flows because you can course-correct in real time. Your client hears the idea, not the syntax. If you stumble, you keep moving. The medium forgives you.
Writing in English as a non-native speaker is different. Every sentence is permanent. You know this, so you rewrite.
What actually happens in those rewrites is linguistic work that a native English speaker rarely notices. On a call, you can say, "So this approach, it's interesting because we're solving for the user's workflow, right?" That conversational hedge and question-tag survive in speech. In writing, "So this approach, it's interesting because we're solving for the user's workflow, right?" looks uncertain. It looks like you're asking permission.
So you rewrite: "This approach solves for the user's workflow."
But now it sounds formal. Too formal. So you rewrite again: "This approach is interesting because it solves for the user's workflow." Still not quite right. On the call, your tone made it clear. In text, you have to signal that tone through punctuation, word choice, sentence structure. Without real-time feedback, you can't tell if you've succeeded.
That's the real tax. Not vocabulary. Tone markers don't translate to async text.
The Rewrite Cycle That Eats Thirty Minutes
Here's what actually lives in those thirty minutes. Maria writes:
"I think we should probably consider moving forward with the TypeScript migration next quarter because our velocity on that team has been pretty strong lately"
She reads it. Hears herself being careful. Tentative. Too many qualifiers. She rewrites:
"We should move the TypeScript migration to next quarter. The team's velocity supports it."
Now it's sharp. But is it too direct? Will it land wrong in writing when there's no face-to-face context? She reads it again, thinking about how she said it on the call. On the call, she'd opened with "This might be worth thinking about..." and the team had nodded along. In writing, she can't do that.
So she tries: "I'd recommend moving the TypeScript migration to next quarter, given the team's strong velocity."
That's closer to the call version. It acknowledges her voice. But she reads it one more time, second-guessing the comma after "quarter," wondering if "strong velocity" sounds data-driven or weak.
Thirty minutes in Slack. Ninety seconds on the call.
Why Grammarly and Otter.ai Don't Solve This
Grammarly catches grammar and typos, but Maria's message never had either. She writes well. The app finds nothing to fix, so she's still stuck in the rewrite loop, doubting her tone.
Otter.ai transcribes spoken English with 96.3% word accuracy on long-form audio. But transcription is just the first step. Maria still faces the same problem: the transcript sounds conversational and she feels like she has to polish it. The tool got her the draft, but she still has to translate herself from spoken to written.
Apple Dictation has been native to macOS and Windows since 2012, yet knowledge workers still avoid it for professional writing. Why? Because dictation products solve for volume, not for tone. They get the words out, but the second-guessing starts immediately after.
The problem was never how to get the words down. It was never about accuracy. It was about staying in flow, about not breaking to translate yourself.
What Becomes Possible When the Loop Stops
When you speak into Slack and get a polished version back in seconds, without word limits or the weight of a rewrite session ahead of you, something changes. You stop translating yourself. The hesitation disappears because you don't have to wait for it.
Recitey runs Whisper, the same model Apple uses, on your device with zero variable cost. There's no word limit on the free tier, no metering, no soft cap that makes you plan your messages. You speak, Recitey polishes it to something that sounds like you, not a formal version of you, your actual voice, and it goes into Slack, into email, into your Notion doc, into every Windows app via the system clipboard. No browser tab. No additional step. Your momentum carries through.
What that unlocks is simple: you write like you speak. The careful version of yourself disappears because there's no time and no reason to second-guess.
For Maria, this means she's no longer the person who is sharp on calls and cautious in writing. She's the same person in both. On calls, in Slack, in email. The gap closes.
When the rewrite loop stops, your voice stops being a tax and starts being a feature. Other people see what your manager sees in the Gong recordings: sharp, commanding, clear. They just see it in writing too.