You sound sharp on calls. Then you draft a Slack message and spend three minutes wondering if "utilize" sounds too formal. You rewrite it four times.
The presence you lose between speaking and typing
Maria, a senior account executive at a European SaaS company, closes deals in English all day. On calls with US prospects, she's direct, confident, persuasive. Her accent is audible but her thinking is clear.
Then comes the follow-up Slack message. She knows what she wants to say. But on screen, she hesitates. Is that sentence too short? Does this sound abrupt? She rewrites the same message four times, removing words, adding softness, trying to sound less like she's giving an order. Twenty minutes later, she hits send. It says what she meant to say. It doesn't sound like her.
Why async writing in a second language taxes your identity
Speaking happens in real time with immediate feedback, tone, pace, interruption. You adjust as you go. Your personality survives.
Writing in a second language strips this away. You can't rely on tone to carry meaning. You have to over-specify. You have to be certain before you commit the words. Most non-native writers choose safe. They rewrite to sound more neutral, more careful, less like the person who speaks with confidence on Zoom.
Studies show non-native English speakers spend 40% more time on written communication than native speakers do. But the real cost isn't time. It's the erosion of presence. Your boss reads your Slack and thinks you're "more concise" when really you're just afraid.
The performance review that confirms the problem
Maria's last two reviews praised her "exec presence on calls." Then: "could be more concise in writing." She knows better. She is not less precise in writing. She is just more afraid.
The moment she hits send on anything async, she's filtering her voice through a check that doesn't exist on calls. Will this read as too blunt? Too casual? Too formal? Will they take me seriously? This internal review process is expensive. It's invisible to everyone except the person doing it.
Why Grammarly and translation tools make this worse, not better
The tools that exist assume the problem is technical. Grammarly catches comma errors. DeepL polishes output. But none of them give you back the time. None of them restore your voice to the writing.
Because the real problem isn't grammar. It's the gap between how you think and how you're willing to sound in writing. Grammarly can't close that gap. It can only make your careful version more grammatically correct.
Maria used Grammarly for two years. Her messages became more polished. They also became slower to write. She was still rewriting. She just had one more tool in the loop.
What actually helps: rough drafts that sound like you
The shift happens when you separate thinking from polishing. Speak your thought exactly as it lands. Don't edit for tone. Don't filter for professionalism. Don't translate. Then clean it up without erasing your voice.
Recitey does this in Slack itself. You voice-draft directly in English, without the typing tax. Whisper's accuracy is 96.3% (OpenAI benchmarks), so the draft arrives clean. Free tier has no word limits. One quick pass to tighten. You hit send. It sounds like you.
For Maria, the follow-up message that took thirty minutes now takes four. And it sounds more like the person who closed the deal.
The unspoken cost of performing professionalism in writing
Every person who writes in a second language carries this tax. But the difference isn't skill. It's friction. And friction is solvable.