The moment you hang up the call, you're sharp. Clear. Present. You explained the deal logic perfectly, asked the right questions, closed the decision maker. Your manager's latest feedback about "exec presence on calls" is sitting there for a reason.
Then you open Slack.
The follow-up message sits in the draft box. You read it. It sounds smaller than you are. More tentative. The grammar is fine. The structure is fine. But it doesn't sound like the person who just led that call. So you rewrite it. Again. Once more. You're now four minutes into a message that took 90 seconds to think of, because the version of you that appears on the screen has to be perfect in a way the version of you on Zoom does not have to be.
This is not a vocabulary problem. This is not a grammar problem. The people reading your Slack know you're fluent. The person struggling with your writing is you.
The call is live. Slack is permanent.
On the call, you speak in real time. Your accent is part of your voice, not a liability. You self-correct mid-sentence and it sounds natural. You use pace and tone to emphasize. Your hands move. Your face communicates. There are eight other people in the room confirming that what you just said made sense. You're not alone with the blank screen trying to prove your competence in a medium that doesn't let you use half your communication tools.
Writing in English as a non-native speaker is identity work. You're not translating words. You're translating the entire presence you have on a call into a text box, and that presence does not fit.
That gap is real. According to research on code-switching and professional identity, multilingual professionals report a 23% gap between their self-perception of competence in spoken versus written contexts, even when objectively proficient. The friction isn't ability. It's medium mismatch.
Grammarly doesn't close that gap. Grammarly corrects comma placement and tense consistency. It doesn't give you back the fifteen minutes you spent rewording the same message because the version of you on the screen sounded too careful, too measured, too different from the person on the call. Translation tools make it worse. They erase the voice that survives your accent and replace it with something generic and flattened.
The real tax is time, and it compounds.
Maria, a senior account executive at a B2B SaaS company, spends an average of 8 minutes per Slack message that goes to a US client or her leadership. Four minutes to write it. Four more to rewrite and second-guess. She sends 6 to 8 of these messages a day. That's 48 to 64 minutes of additional time per day. Over a year, that's roughly 200 hours. Two hundred hours spent not on deal progression or strategy, but on the invisible tax of sounding like yourself in a language that isn't native.
She knows the gap isn't real. Her last two performance reviews said "exec presence on calls" as a strength and "could be more concise in writing" as a gap. She knows the gap is not about concision. It's the medium. It's the permanence. It's having to edit yourself down to what looks safe on a screen instead of letting the full version of you through.
The cognitive load is exhausting in a way that isn't obvious to the people reading the messages. You're not translating. You're performing a narrower version of yourself every time you hit send.
Why existing tools make this worse.
Voice dictation has existed on Windows for years. It's fine for transcription. MacWhisper exists. Otter.ai exists. They all assume the same thing: that the problem is transcription accuracy, and if you can just get the words down, you're done.
But if the problem were transcription, Maria would already be solved. She can type fine. She can structure sentences. The issue is that when she types, she self-edits. When she speaks, she doesn't. The tools assume she needs to talk and hear her exact words written down. What she actually needs is to talk and get the confident version of that thought, the version she has on calls, into Slack without the three layers of self-doubt that happen when her fingers hit the keyboard.
Recitey works offline. There's no transcription accuracy problem to solve, and no word limit, no metering, no pause-and-restart dance. Speak the message. It polishes the rough draft into a clean sentence in under 2 seconds. No variable cost, no network latency, no third-party transcription. What comes out is the version of you that exists on calls, not a degraded copy of it.
What changes when you don't have to rewrite.
The first week using voice for Slack instead of typing, Maria sent a message directly. No rewrite. No four-minute review loop. She noticed something strange: the message was shorter than her typed version, but somehow sharper. She sounded more like herself.
By week two, she noticed she was sending more follow-ups. Not because she was more productive, but because the rewrite tax was gone. Ideas that felt too risky to commit to text, because text required a three-iteration approval process in her own head, now moved straight to Slack. Her team started responding differently. Same confidence level. Fewer carefully hedged qualifications. The writing sounded less like someone translating and more like someone thinking out loud.
That's the invisible piece: removing the rewrite tax doesn't just save time. It changes what you're willing to communicate. The thoughts that survive four rewrites are the safe thoughts. The thoughts that survive one speak are the actual thoughts.
The wedge is specificity, not speed.
Non-native English speakers who are excellent on calls do not need faster transcription or better grammar checking. They need a tool that understands that the person on the call and the person typing in Slack are the same person, and that person is not broken, the medium is.
Maria still writes emails. She still documents complex ideas in docs. She still uses Slack for moments that need care. What changed is which medium she chose for the moments that don't need editing, and that turns out to be most of them.
The version of you on the call is competent. The version of you in Slack should be too.