On a Wednesday morning sales call, you explain a product roadmap to a customer in perfect English. You're precise, present, confident. The client asks a follow-up; you answer without hesitation. The call ends, and your manager later tells you your exec presence was strong.
Then you open Slack to send the same customer a follow-up note.
Thirty minutes later, you're still typing.
This isn't a vocabulary problem. Your English is fluent. This is a medium problem, and the cost is invisible.
The Call Is Easy
The call happens in real time. There's no time to overthink. Your accent stays. Your pace is natural. Your personality fits into the space you've occupied for the entire conversation. You sound like yourself because there isn't enough space to become someone else.
Research from the European Commission shows that non-native English speakers in knowledge work spend 3-4 times longer on written communication than on spoken communication. Not because they're less skilled. Because writing creates room for doubt.
The Slack Draft Is Hard
You open a message to send to the customer. You type: "Hi, I wanted to follow up on the roadmap timeline we discussed."
Then you reread it.
It doesn't sound right. It's too formal. Stiff. Less like you than you want. You delete it. Try again: "Following up on what we talked through on the call regarding the roadmap."
That's longer. Worse. You don't like it. You delete again.
Maria, a senior account executive at a European B2B SaaS company, does this three or four times per message. Her performance reviews note "exec presence on calls" as a strength and "could be more concise in writing" as a gap. She knows that gap isn't real. It's just the medium. On a call, she doesn't edit herself. In Slack, she can't help it.
The friction is identity-protective. Written English is where she feels exposed in a way speaking doesn't.
Why Grammarly Misses the Point
Grammarly catches comma splices. It flags repeated words. It normalizes passive voice. None of that is your problem.
Your problem is that you're spending 30 minutes writing what took 5 minutes to say. Grammarly doesn't give you back time. It just tells you your gerund construction was sloppy.
Translation tools are worse. They smooth out your voice entirely. An accurate translation isn't the same as your voice translated. Something gets lost in the mathematical equivalence.
What you need isn't grammatical polish. It's permission to sound like yourself in writing the way you sound in calls.
What Voice-First Writing Changes
Voice writing doesn't solve the medium problem directly. But it collapses the rewrite cycle.
When you dictate instead of type, you're speaking, not translating. Your natural rhythm survives. You capture the thought before it gets filtered through the self-editor. The rough draft is closer to how you actually communicate.
Then the tool cleans up the syntax without erasing the voice. What comes out is recognizable as you, not as a cautious version of you.
Recitey works directly in Slack, email, browsers, and every Windows app you already use. You speak the message. It transcribes locally on your device with no word limits or metering. The output polishes the rough draft into a clean sentence you can send without the rewrite cycle.
The point isn't faster writing. It's writing that sounds like the version of you that showed up on the call.
The Cost of the Rewrite Tax
Thirty minutes per message across a week of work adds up. A study by Otter.ai found that remote workers spend 23% of their working day on written communication. For non-native speakers in async-first environments, that number is higher.
But the cost isn't just time. It's authenticity. Every rewrite is a small retreat. You're making yourself smaller to fit into the medium. On the call, you didn't do that. Neither should your Slack.
What Actually Matters
Your English doesn't need to be perfect on the first draft. It needs to sound like you. The medium shouldn't force you to choose between authenticity and fluency.
That choice is where the 30 minutes come from. It's not language skill. It's the gap between how you communicate in real time and how you communicate in writing.
Close that gap, and the message writes itself.