The call went great. You were sharp and fluent. Then you opened Slack to send the follow-up. Twenty minutes later, you're still rewriting the first paragraph.
The call versus the inbox
On video calls, you're fluent. Your accent is there, but it doesn't matter because your thinking is clear. You articulate the point, the room gets it, and the conversation moves. A Swedish PM described this moment: "On a call, I'm sharp. In Slack, I'm the watered-down version."
This isn't a vocabulary problem. This isn't grammar.
It's the medium. Voice carries tone, pace, confidence. Writing in your second language strips all of that away and leaves you searching for precision in a system that doesn't reward it the way spoken English does. So you rewrite. You're not chasing perfect grammar. You're chasing the version of yourself that existed five minutes ago on the call.
Maria, a senior account executive from Spain with eight years selling into US enterprise, described her performance review like this: "Exec presence on calls" as a strength. "Could be more concise in writing" as a gap. But she knew the gap wasn't real. It was the medium.
Why translation and grammar tools miss the point
Grammarly surfaces corrections to help you finish faster. There's a gap in that logic, though. Grammarly gives you back time by catching errors. It doesn't give you back the thirty minutes you spent rewriting the same message four times because it didn't sound like you.
Translation tools are worse. They replace your English with "better" English, which usually means erasing the voice that survived your accent in the first place. You end up with something correct and hollow.
The assumption behind both tools is that the problem is a gap in your English. You and I both know the problem is different.
The identity tax of writing in your second language
This is why the rewrite loop hurts. It's not productivity friction. It's identity friction. On a call, you're present. In an inbox, you're guarded. You re-read your message three times before sending because you're aware that written English is where you feel exposed in a way speaking doesn't. You know you sound smaller on the page than you do with your voice.
Non-native English speakers in corporate settings experience this as a double tax. One is time. Every message that takes thirty minutes to write because you're editing for precision is thirty minutes not amplifying what you actually know. The other is confidence. It's the slow corrosion of presence that happens when you learn, over years of async communication, to make yourself smaller to feel safer.
The person your team hears on calls is sharp, decisive, fluent. The person they read in Slack is hesitant and careful. Those aren't two versions of you. One is real. One is what you construct when you have time to edit.
What voice-first actually changes
The premise is simple: if you could capture that sharp version from the call and keep it in the written version, what would change?
Voice-first writing works because it doesn't try to translate or correct your English. Recitey uses Whisper, which hits 96.3% accuracy on LibriSpeech, and it captures you as you speak in your pacing and tone, then refines the rough draft into clean sentences. No rewrite loop. No translation step.
The output sounds like the version of you that exists on calls, not the careful version that lives in Slack. And because Recitey runs locally on Windows with no word limits and no caps on the free tier, you're not paying per message or worrying about metering.
When this is for you
This matters if you're a knowledge worker in your second language who's already excellent in speech but becomes hesitant in writing. If you're a PM or engineer from the Nordic and DACH regions who's fluent on calls and stalled in Slack. If your performance reviews mention exec presence as a strength and written communication as a gap, and you know that gap is the medium, not your ability.
It doesn't matter if your friction is actually vocabulary. It doesn't matter if you prefer to think through your writing before it's spoken. It doesn't matter if you have unlimited time and rewriting is how you prefer to work. Those are different problems.
But if you've looked at a Slack message you drafted and thought, "This doesn't sound like me because I wrote it," this is what changes.
The trade-off you're actually making
The only cost is that you have to be willing to draft by voice. Some people prefer writing first. Some people think better on the page. If you're one of those, voice-first isn't for you.
The other cost is the habit: when you feel the hesitation before sending, you speak instead. That means accepting a different draft process. It means tolerating the rough transcript for the two seconds it takes to refine into sentences. It means trusting that capturing your voice is the harder part and cleaning it up is mechanical.
The people I've talked to who've made this switch describe the same moment: the relief of not rewriting the same message four times, and the presence you had on the call, now in your inbox.