On a call with her US clients, Maria is sharp. She frames problems clearly. She asks the right follow-up question. Her accent has never been the issue. But after the call ends and she opens Slack to send a follow-up to her team, something shifts. The message takes 30 minutes to write. Not because she's looking up words, but because she keeps rewriting it.
On a Call, You Sound Like Yourself
Maria works as a senior account executive at a European SaaS company. Her performance reviews confirm what her clients already know: "exec presence on calls." She thinks fast. She speaks faster. English is her third language, and by now, it isn't a constraint. She's fluent enough that the non-nativeness is invisible to everyone but her own internal calibration.
The call ends. She was sharp. She was present. The client heard that.
Then she has to write it down.
In Writing, Something Shifts
The shift from synchronous to asynchronous English creates a gap that fluency doesn't close. On a call, your thoughts come out at the speed you think them. You don't have time to edit. You don't have time to choose a more "professional" phrasing. Your actual voice, confident, direct, present, comes through.
In Slack, that voice disappears. Not because Slack is formal, but because it's just synchronous enough to feel like real communication while being just asynchronous enough for self-doubt to creep in.
Maria re-reads her own messages three or four times before sending them. She doesn't do this on calls. She does this because writing creates a gap between her thought and the moment she sends it. In that gap, she rewrites.
And rewrites.
And rewrites.
It Is Not Grammar. It Is Rewrite Time.
Her last performance review said "could be more concise in writing." She knows that's not actually the gap. She's concise when she speaks. The issue isn't brevity. The issue is confidence.
Grammarly would catch her spelling mistakes, if she made them. But her messages aren't wrong grammatically. They're just... smaller than how she actually communicates. They're the careful version of herself, written by the part of her brain that's still monitoring English, still choosing words, still afraid of being misunderstood.
On a call, that monitoring function is quiet. On Slack, it's loud.
The cost is time. Thirty minutes to write what, on a call, takes her six minutes to communicate.
The Async Translation Layer
Here's what actually happens in your head when you write in your second language, even when you're fluent:
You think something. You draft it. You read it back. You spot a phrase that sounds "off." You're not sure why. You rewrite it. You read it again. It's better, but it still doesn't sound like you. You try a different angle. Now it sounds more like you, but is it too casual? You adjust for formality. Now it sounds formal but cautious. You read it one more time, and this time you hit send.
This loop is invisible when you speak because there's no time for it. When you write, there's all the time in the world for it. And for non-native speakers in async-heavy workplaces, that time becomes a tax.
Maria spends 30 minutes every week just in this loop.
What If You Could Speak Your Way Through It?
Voice writing collapses the gap. When you speak, you think and speak at the same speed. The monitoring function doesn't have time to take over. Your actual voice, confident, direct, fast-paced, comes through in the first draft.
That draft is rough. It might have a few verbal tics, a repeated word, a fragment. It's what you actually sound like when you think out loud.
Then it gets polished. Recitey runs Whisper locally on your Windows device and cleans up the rough draft into a structured message in seconds. No word limits. No monthly metering. It works in Slack, email, browsers, your terminal, every Windows app.
Maria starts voice-drafting her follow-up Slack messages. The first draft takes three minutes (the speed of speaking). The polish takes another 30 seconds. She sends a message that sounds like her, not the careful version of herself, but the actual confident version that exists when she's not writing.
The 30-minute message now takes 3.5 minutes.
The Voice Stays. The Anxiety Goes.
This isn't a language fluency problem. It isn't a vocabulary problem. It isn't a grammar problem.
It's a medium problem. Writing in a second language, even at native-level fluency, creates friction that speaking doesn't. For non-native speakers in English-dominant workplaces, that friction is a constant micro-drain: the 30-minute message, the re-read before send, the careful version of yourself on Slack.
Voice writing doesn't make you sound like a native speaker (and why should it?). It makes you sound like yourself.
When you speak, your confidence comes through. When you write, it doesn't have to disappear. The gap between how sharp you sound on calls and how careful you sound in Slack isn't a language gap.
It's a medium gap. And it closes when you bring the speed of your voice into the medium of writing.