You explained the idea in real-time. Shared the context. Made them laugh. They got it. But then you had to write it down, and suddenly you weren't sure anymore. You rewrote the message three times. Four times. Five. Because the version that sounded sharp on the call sounded too careful in writing.
This is the opposite of what anyone assumes about language learning. But it is what happens to thousands of senior knowledge workers in DACH, the Nordics, and beyond: fluent on calls, hesitant in async.
The medium is the message, not your English
Maria is a senior account executive at a B2B SaaS company, Spanish background, eight years of selling to US enterprise. On calls she is sharp. Fast. Present. Her executives comment on her "exec presence." And then she opens Slack, and the gap between the voice in the call and the voice on the screen becomes impossible to ignore.
"I rewrote that message four times," she told us. "On the call, I said it in 20 seconds. In Slack, I need it to be perfect."
The problem isn't that her English got worse. The problem is that something about the medium, the asynchronicity, the permanence, the isolation, makes her second-guess every word. Spoken English has rhythm, presence, and momentum. Written English, especially in async, has silence and time to overthink.
Grammarly will not give you back the 30 minutes
This is where existing tools fail most senior professionals. Grammarly catches a comma splice. It doesn't explain why your tone sounds smaller than it is.
Translation tools make this worse, not better. They erase the voice that survives your accent. They assume you're a beginner learning grammar, when what you actually need is to sound like the person you are when no one is waiting for a response.
Voice dictation tools have been around for years, Apple's Dictation since 2012, Dragon NaturallySpeaking since the 1990s. But most of them either cap your free usage (Wispr Flow: 2,000 words per month), assume you're dictating to transcribe, require you to keep a tab open breaking your workflow, or produce rough output that still needs heavy editing. They solve transcription, not presence.
The identity-protective rewrite cycle
When you aren't a native speaker, async writing becomes identity-protective. You reread your messages. You check the tone. You make sure you sound smart enough. On calls, none of that happens. Someone asks a question, you answer, and your accent and imperfect grammar don't matter because they hear the intelligence underneath the delivery.
In writing, the intelligence has to survive on the page without your tone of voice, your eye contact, your presence in the room. So you rewrite. You worry. You make the message more formal, more careful, less like yourself. And it takes forever.
What actually needs to change
The real gap isn't vocabulary. It isn't grammar. It's time. The solution isn't to write more carefully or use a translation layer. It's to write closer to how you think on calls, at the same speed, with the same momentum. The system should handle the polish.
Recitey works locally on your device with no word caps, no metering, no send-to-the-cloud processing. You speak like you do on calls. The system polishes the rough draft into a clean sentence in seconds. No overthinking. No rewrite loop. It works in Slack, Gmail, Google Docs, browsers, and anywhere else you type on Windows.
The performance review pattern
Here's what Maria noticed: her last two reviews mentioned "exec presence on calls" as a strength and "could be more concise in writing" as a gap. She knew the gap wasn't real. It was just the medium. On a call, you can't be verbose. In Slack, you can, so you hedge. You qualify. You explain more because you're anxious that your meaning won't survive without your voice.
The fix isn't to write more carefully. The fix is to write faster, closer to how you think. To bypass the rewrite loop. To sound like yourself on the page the same way you do on the call.
The 30-minute moment
One customer told us: "A call where I made perfect sense took me half an hour to write down in Slack. Not because I didn't know the words. Because I was rewriting to sound like what I thought written English should sound like, instead of sounding like me."
That half hour is the tax. That's what you get back.