You sound sharp on calls. Your manager said so in your last review: "exec presence is a real strength." But somewhere between the Zoom window closing and your follow-up message landing in Slack, something shifts.
The same thought that came out confident and direct on the call gets rewritten. Four times. Before you hit send.
This isn't a vocabulary problem. This is a medium problem, and it costs you time you didn't know you were losing.
The rewrite tax is real, not imaginary
Maria, a senior account executive at a European SaaS company, runs through her day like this: calls to US enterprise clients in the morning (sharp, quick, present); internal Slack messages to her team in the afternoon (reworked, hedged, careful). She doesn't think in English, but she's fluent. Yet on calls she sounds like herself. In Slack, she sounds like a version of herself that's been translated twice.
Her performance review last year called it out: "Strong executive presence on calls. Could be more concise in writing." She knows the gap isn't real. It's the friction between thinking in one language and writing in another, then rewriting because the first draft feels too careful, too formal, or somehow smaller than the person who just led a 30-minute negotiation.
She spends roughly 15 to 20 minutes on a typical 3-sentence follow-up message. The first draft is always too cautious. The second is over-corrected. By the third, she's rewriting to reclaim her own voice, not to fix grammar.
This isn't unique to Maria. Talk to senior engineers, product managers, and founders from DACH or Nordics who sell or communicate in English, and you'll hear the same pattern. Fluent on calls. Frozen in writing. Not because their English is weak, but because the medium forces them into a narrower version of themselves.
Why Grammarly and Microsoft Voice Typing fall short
Grammarly catches mistakes. That's not the problem Maria has. She doesn't make grammar mistakes. What she needs is her voice back, which is a different thing entirely.
Microsoft Voice Typing, the native Windows dictation tool, promises to bridge the gap by letting you speak instead of type. But it's designed for raw transcription, not for the specific friction Maria faces. Speak a Slack message into it, and you get a raw transcript that still needs heavy editing. The rhythm of speech doesn't automatically become the clarity of writing. You end up editing the transcript almost as much as you'd edit a typed message, which defeats the purpose.
Translation tools promise something different: they'll rephrase what you wrote so it sounds more native. But they work in the opposite direction. They formalize, they neutralize, they erase exactly the personality that survives her accent on a call. Ask it to rephrase a Slack message and it comes back stiffer, more corporate, less like her.
The tools assume she's a beginner. She's not. She's got eight years of sales conversations, technical depth, and presence. The problem isn't skill; it's the medium. Writing in async channels flattens her. Speaking keeps her intact.
What Grammarly actually does is make her sound better to someone reading the rules of English. What she actually needs is to be herself on the page, which means preserving the directness and rhythm that already works on calls. Those two things are almost opposite.
The moment the friction becomes unbearable
It starts small. One careful message. Then another. Then you notice you've been sitting on a Slack draft for eight minutes, rereading it, because it doesn't sound like you sounded on the call 20 minutes ago.
The worst part is you can feel it happening. You know what you want to say. You know you said it well, out loud, maybe 30 minutes ago. But writing it down freezes you. The informality that works in speech reads as careless in text. The directness that sounds decisive on a call sounds blunt in Slack.
You're not being careful for no reason. You're being careful because writing creates distance between you and how you actually communicate. On a call, your accent is part of your credibility. In Slack, you worry it sounds like a liability. So you hedge. You soften. You write like someone who's apologizing for not being a native speaker, which is the opposite of who you are.
So you rewrite. You add hedging. You soften the tone. You reclaim some version of yourself, but a smaller version. The one your manager sees isn't the one who just closed a deal.
What changes when the medium stops constraining you
The moment you can speak instead of type, the friction drops. Your voice doesn't need translation. Your thought comes out at natural pace and rhythm. The rewrite cycle ends.
Not because voice is magical. Because your brain doesn't have to go through the medium shift. Call mode and Slack mode can finally be the same person.
Maria tested this with Recitey, a voice-to-text layer built for Windows that transcribes your speech using Whisper and runs locally on your device with no word limits, no metering. She speaks a follow-up to a client into her computer, Recitey handles the transcription and light polish in under two seconds, and she pastes it straight into Slack. Same thought, same voice, no 15-minute rewrite cycle. The tool works across every Windows app, email, Slack, docs, browsers, through the system clipboard, so it integrates into her existing workflow without friction.
The review score on exec presence stays the same. The writing gap evaporates, because it was never a writing gap.
The gain isn't just speed, though that matters. A typical message that'd take 12 to 15 minutes to write takes under two minutes to voice and clean up. The bigger gain is that you stop becoming a smaller version of yourself the moment you switch to async.
Think about what disappears when the medium is no longer the bottleneck: the reread, the hedge, the apology hiding inside a hedged sentence. The voice that was never weak to begin with.
The trade-off no one talks about
Using voice to write doesn't make you a better writer. It makes the medium stop fighting you.
There is a trade-off worth considering: you've got to be comfortable with slightly rougher first drafts. The output from Recitey is cleaner and faster than typing from scratch, but not as polished as a 15-minute handcrafted message. For most Slack and email use cases, that trade is worth it. For formal client proposals or legal documents, you might still reach for the keyboard.
The other trade-off is learning to talk to your computer without feeling self-conscious. That lasts about two minutes. After that, you stop noticing. The rhythm of speech becomes normal. The tool fades away.
And there's a third trade-off worth naming: you've got to trust that your voice is good enough. On calls, you already do. In writing, you're not sure. Voice writing asks you to bring the same confidence from calls into async channels. For people who sound great on calls and doubt themselves in writing, that's actually not a trade-off at all, it's a return.
Who this is actually for
This isn't for people who struggle with English. This is for people who are fluent but feel constrained by the medium. For someone whose call presence is their strength but whose async writing makes them sound smaller. For non-native speakers who know they're sharp but keep rewriting to prove it.
This is for the person who nails the call and then spends 20 minutes rewriting the follow-up because the written version feels like a betrayal of how well they just communicated.
If you sound like yourself on calls and someone else in Slack, the gap isn't your English. The gap is the medium.