You sounded sharp on that call. Clear. Present. The kind of presence that closes deals.
Then you drafted the follow-up message in Slack and rewrote it four times.
On calls, you're in your element. Your English flows. You think, you speak, you land the idea. In writing, something shifts. You become more careful, smaller somehow. And you're not alone. The hidden tax on being a knowledge worker writing in your second language isn't vocabulary. It's time.
The speed gap is real, and your tools ignore it
You speak at roughly 120 to 150 words per minute. On a good call, faster. Your typing speed is 40 to 60 WPM. By the time your fingers catch up to your thought, the thought has already shifted. You second-guess the phrasing. You soften the language. You add qualifiers. The message that arrives in Slack is accurate but smaller than how you actually communicate.
Wispr Flow claims to capture your voice in dictation. Otter.ai transcribes it. Grammarly cleans up the grammar. But none of them give you back the 30 minutes you just spent rewriting a message that took three minutes to say on the call. They all assume the problem is mechanics, vocabulary, grammar, accuracy. The problem is momentum.
The real friction: written English is where you feel exposed
Maria, a senior account executive at a European SaaS company, articulated it in a customer call on May 5: "It sounded like the careful version of myself."
On a call, your accent is there. It's part of how you communicate. It doesn't weaken what you say; it anchors it. People listen differently when they hear authenticity. But in written English, that accent becomes a marker. A sign of non-nativeness. So you rewrite. You remove the colloquialisms. You flatten the rhythm. You add formal hedges and qualifiers. "Could" instead of "can." "It might be worth considering" instead of "let's do this." Three rewrites later, what arrives in Slack sounds professional but not like you.
James, an engineering lead at a Nordic fintech, described the team dynamics: "My Slack messages are so carefully constructed that they come across as indecisive. The developers think I'm uncertain about direction. On a call I'm not uncertain. In Slack I sound like it." He rewrites technical decisions three or four times because he's aware of how written English is read. The cost: urgency disappears. Authority flattens. The message that should convey clarity arrives sounding tentative.
The invisible tax compounds across a full day
It's not just one message. It's twelve. A sales follow-up after the 10 a.m. call (30 minutes of revision). A status update to leadership (15 minutes). Feedback on a proposal from the product team (20 minutes). A technical decision on the engineering Slack (25 minutes). Quick onboarding message to a new hire (10 minutes).
That's 100 minutes of pure rewriting in a single day. Two hours. Every day. Over a month that's 40 hours of revision time spent making your English sound safer, not sharper. Over a year, that's a full work month spent softening your own thoughts into acceptable written form.
And this matters because async communication is where executive presence is built now. It's where decisions move. A 30-minute call sets direction; Slack creates documentation and momentum. If your Slack messages read as careful instead of clear, the org reads you as careful instead of clear. The performance review calls it out without naming the real cause: "Could be more concise in writing." As though the problem is economy of language. It's not. The problem is the medium is slower than your thinking.
Why existing tools make this worse, not better
Grammarly catches grammar mistakes. Wispr Flow captures dictation. Otter.ai transcribes meetings. They all assume you need help with the mechanics of English. None of them solve the real problem: the 70-word-per-minute gap between how fast your mind works and how fast your fingers move.
And there's something else. These tools assume you need your voice smoothed. They erase the accent, the rhythm, the presence that makes your speech effective. They turn dictation into flat, safe, standard English. Which is exactly what you don't want. You don't want to sound safer. You want to sound like yourself, but faster.
What changes when you draft at speaking speed
Imagine capturing your call energy while it's fresh. Not dictation that gets transcribed and needs a second round of editing. Not grammar cleanup that takes 15 minutes per message. Imagine drafting at 120 WPM, the speed your mind actually works, and having the rough edges polished into a message ready to send in under two seconds.
The follow-up email after a sales conversation, written in the 60 seconds after you hung up, at speaking speed, before the careful version of yourself takes over. What arrives in Slack or email sounds like the actual you. Not smaller. Not more careful. Not filtered through a translator's idea of "professional English." The real you, at real speed.
Recitey runs locally on your device, no cloud, no variable costs, no metering, no word limits like Wispr Flow or other services impose. It works in Slack, in email, in browsers, in your terminal. It doesn't assume you're learning English. It doesn't try to flatten your voice into a standard. It captures your thought at speaking speed and polishes it into a clean sentence. That's it.
The gap isn't English. It's the medium.
You aren't bad at written communication. You're brilliant on calls, which is the truest test of communication. The tools available to you just happened to be slower than your thinking. They solved for accuracy when the real problem was velocity. They solved for safety when the real problem was presence.
There's a different way to approach this. One that doesn't assume you're a beginner. One that doesn't erase the voice that survived your accent. One that trusts the intelligence and presence you already have on calls and gives you a way to carry that into writing.