On a Slack call with your US team, you're sharp. Then the follow-up message takes 30 minutes to write.
The Pattern No One Names
You speak English every day on calls. Your accent is there, but it doesn't slow you down. People listening to you know exactly what you mean. Your manager's last review said "excellent exec presence in synchronous meetings," but then added: "could be more concise and direct in async channels."
The thing is, you are concise and direct on calls. Somehow writing steals that.
You're not alone. Thousands of senior engineers and PMs across Northern Europe and Germany experience the same thing: fluent on calls, hesitant in Slack. What they experience isn't language anxiety. It's a rewrite loop.
You draft: "I think we should consider moving the launch date."
You re-read it. Sounds tentative. Rewrite: "Let's move the launch."
You pause. That sounds abrupt. Rewrite three: "I'd suggest we move the launch to avoid."
Twelve minutes later, you've rewritten it four times. The message that finally ships is technically correct. It's also not how you sound when you're thinking out loud on a call.
On a call, the filter is off. Your voice carries confidence that words alone don't.
The Hidden Tax
Here's what's invisible: the time cost.
Not the time to type. The time to feel safe sending.
Maria is a senior account executive at a B2B SaaS company, and her sales cycle is Slack-heavy. After a call with a US prospect, she needs to send a follow-up summary to her internal team and then a separate note back to the prospect's buying committee.
Two messages. Probably 800 words total across both.
On a call, she'd explain the same thing in eight minutes and land three times as much nuance, all without notes.
In writing, she budgets 30 minutes. Not because English is hard. Because checking herself before sending takes time. Rereading to catch any phrase that sounds "off." Running it through one more filter to make sure it reads like competence and not caution.
That's 22 minutes that aren't real writing work. They're doubt work.
The same Maria that can negotiate pricing on a call, confident, fast, adaptive, becomes someone who erases nuance from her own sentences because written English feels like the place where she'll be judged.
What Voice Tools Actually Do (and Don't)
You might think voice-to-text tools solve this. Wispr Flow, Otter.ai, Microsoft Voice Typing, Apple Dictation all exist for exactly this moment.
But here's what they do: they transcribe you. They capture what you said and turn it into words.
That's not what you need.
Most voice tools assume you want a transcript. Or maybe they'll clean up the stumbles. Wispr Flow charges $14 per month and caps free users at 2,000 words per day. Otter.ai meters by the minute. Microsoft Voice Typing is free but doesn't work consistently across every app. Apple Dictation works on Mac but you're on Windows.
All of them give you raw transcription. None of them give you back your voice and your confidence at the same time.
They capture what you said. They don't polish it into something that feels like you made a choice.
The Real Friction: Identity
Here's what actually happens when you rewrite a Slack message four times.
Each rewrite is removing something. A contraction that sounds too casual. A direct opinion that might sound aggressive in writing but wouldn't on a call. An idiom you use in speech but aren't sure translates to your US team in text.
Each version is slightly more guarded.
The message that finally leaves your Slack client isn't actually more correct. It's safer. It's the version of yourself that apologizes a little, qualifies a little, softens the edge a little.
Your performance review says you're excellent on calls and could be more concise in writing. But the truth is simpler: you sound like yourself on calls and you sound like someone playing it safe in Slack.
On a call, confidence carries you. In writing, you have to build confidence into every word, and that takes time.
What Changes When You Get the Time Back
Some tools try to expand your written English to sound more native. That's backwards. You don't need to sound more American or British or Australian. You need your own voice back, just faster.
What helps is capturing what you're trying to say in the moment you're trying to say it, then letting something actually good smooth it into readable form. Not changing it. Polishing it.
Voice-first writing is the shortcut. Speak your thought at natural speed, the way you'd say it on a call, and let the system turn rough audio into clean written English. No rewriting. No identity translation. No sitting with a message for twelve minutes wondering if it sounds right.
The difference is physics. When you speak, you're capturing intention before the doubt filter kicks in. When you write, doubt is built into the process from keystroke one.
How This Actually Works
Recitey works in every app you use: Slack, email, browsers, terminals, Salesforce, documents. No monthly caps. No metering. No credit card to start. Speak your thought naturally and it hands you back something polished in seconds, all without changing your voice or your meaning.
No transcription you have to edit. No "trying to sound more native." Just your thought, your speed, your voice.
The Shape of Getting It Back
For Maria, that 22-minute tax became instant. Speed became just the speed of thinking.