You're sharp on calls. Then you switch to Slack and spend 28 minutes rewriting a follow-up that should take two. This isn't an English problem, it's a medium problem.
On calls you're fluent. In async you're careful.
Most non-native English speakers in senior corporate roles hit the same wall: fluent on video, hesitant in writing. The friction isn't vocabulary or grammar. It's that writing feels like an audit of your English in a way speaking doesn't.
Maria, a senior account executive at a European B2B SaaS company, experiences this exactly. On a call with US enterprise customers, she's present, quick, and sharp. The conversation flows. She pushes back on objections, clarifies requirements, makes the buyer feel heard. Her boss mentions it: "Good exec presence." Forty minutes later, she's writing the follow-up email. And she's a different person.
She drafts: "Thanks for the call. I wanted to follow up on the budget timeline." She reads it back. Too casual. Too short. She rewrites: "I wanted to circle back regarding the budget timeline for Q3 implementation." Better, but now it sounds like she's performing. Rewrite again: "Following up on our discussion about the Q3 budget, I'd like to confirm the timeline works for both teams." Still not right. She does this once more. Twenty-eight minutes pass. The message is sent, correct, but it doesn't sound like her. It sounds like someone being very careful about English.
This gap is real. It has nothing to do with English level.
Grammar tools and dictation apps won't solve this
At least three categories of tools exist to address this problem. None of them actually solve it.
Grammar tools like Grammarly catch mistakes: apostrophes, run-ons, passive voice, occasionally suggest stronger synonyms. They don't touch the actual cost, which is the rewrite cycle itself. Grammarly gives you confidence about correctness. It doesn't give you back the 28 minutes.
Dictation tools like Microsoft Voice Typing and Otter.ai exist specifically to skip typing. Voice Typing is built into Windows and free. Otter.ai is cloud-based and accurate. But both hand you a raw transcript, and you still face the same moment: you read it and think "This doesn't sound like me. I need to rewrite." The transcription is accurate, but the Slack message still goes through four drafts because something feels wrong. The tool has solved typing. It hasn't solved the rewrite tax.
Translation tools, which most non-native speakers have tried and abandoned, erase the voice that survived your accent. None of these touch what actually costs you time: the distance between your first draft and your final send.
The rewrite tax is consistent and substantial
The pattern shows up reliably among professional non-native writers in async environments:
- You have a thought. You speak it aloud or type quickly, the same message you'd say on a call.
- You read it back. It doesn't sound right. Not ungrammatical. Wrong. Stiff. Unfamiliar.
- You rewrite for tone as much as for grammar. Better, but now it sounds cold.
- You rewrite again. Tighter, but performative.
- You do this three to four times, spending 25 to 40 minutes on a message that took two minutes to think.
Research on non-native writers shows they spend significantly more time revising their own work than native speakers do, not because the English is weaker, but because they're less confident in the voice they're hearing. Every sentence is a choice. Every word is checked twice.
By the time you send, the message isn't incorrect. It's just flattened. It's the careful version of you.
What changes when the tool doesn't require rewriting
When you can speak naturally into a tool and receive a clean, readable draft immediately, the dynamic reverses. You're not performing. You're just speaking. The tool handles the shape.
Recitey does this without the constraints other tools impose. It runs locally on your Windows machine, no cloud processing, no privacy questions about where your voice goes, no variable cost per word. No monthly word meter. No cap. You speak, the draft refines in seconds, and you review it right there in Slack or Gmail.
For Maria, this means 28 minutes becomes three. She speaks a sentence or two, gets a clean draft, reads through once, maybe tightens one word, and sends. No rewrite loop. The message sounds like her. Not like someone being very careful. Just her.
She notices something else, too: when there's no rewrite cycle, she includes details she normally cuts out. The message is longer, but also more human. It performs better because it sounds like someone living in the role, not someone auditing their own English.
You're not the gap
The performance review that says "Could be more concise in writing" isn't about your English. Your English is strong. It's about the cost of the medium. On a call, you can't rewrite, there's no time. So you sound like yourself. Concise. Direct. Sharp. In Slack, you can edit endlessly, which means you do. That's not a character flaw. That's how the medium works.
The fix isn't to become a better writer. It's to write the way you speak, like you do on calls. That's exec presence.