You crush it on the call. Exec presence, sharp thinking, the full version of you. Then you open Slack to follow up and spend the next thirty minutes writing a message that takes two minutes to say.
This isn't a vocabulary problem. This isn't a grammar problem. This is what happens when your best thinking mode (speaking) and your required writing mode (async text) are different mediums and your brain knows it.
The Call-to-Slack Gap
A sales call with a US executive. You're tracking their objections, you're riffing on solutions, you're laughing at their jokes. You sound like yourself. Sharp, present, credible.
Twenty minutes later, you're drafting the follow-up in Slack. You type a sentence. You re-read it. It sounds cautious. You delete it. You try again. Now it sounds stiff. Delete. Again. By the fourth revision, you've added qualifiers and softened your language so much that your colleague doesn't recognize you in the message.
This is the friction that Grammarly and Google Docs voice typing don't address. Grammarly assumes you need grammar help. You don't. Your English is fluent. Google Docs voice typing captures your spoken words, then you're still rewriting them because they don't sound professional enough when transcribed raw. Same problem, same medium shift.
What you actually need is to get your actual voice back into your writing without the time tax of four rewrites and thirty minutes of revision.
The Career Cost of Disappearing in Writing
Here's what nobody talks about: written language is where team perception hardens.
On a call, your tone carries the idea. Your pace, your emphasis, your laughter signal confidence. Async, those signals are gone. So your brain compensates by adding disclaimers. "Maybe" instead of "yes." "I'm thinking we could consider possibly..." instead of "We should do this."
Your manager hears both versions of you. They see you own the room in meetings. Then they read your Slack messages and see someone tentative. Over time, that gap narrows their read on who you actually are. Your written self becomes the baseline in their memory. Not the sharp version from the call.
For career momentum in async-first companies, this matters. A lot.
Maria, a product manager at a Berlin fintech, described it this way after her promotion cycle stalled: "On calls I am the person I believe I am. In writing, I became someone I don't recognize. My boss saw more of the writing."
She wasn't wrong about the language gap. But she was also watching her identity in the organization shrink to fit the medium. The careful version of yourself is not just slower. It's a tax on how people perceive your capability.
Beyond Slack: Email, Technical Documentation, RFP Responses
The problem isn't Slack-specific.
Email to senior stakeholders: you're requesting budget or proposing a strategic pivot. You spend 45 minutes on a three-sentence email because every word feels like it might reveal hesitation. The result sounds like a committee wrote it.
Technical documentation: you're onboarding a new engineer or documenting a decision. The tone flattens. Your actual reasoning (fast, conversational, confident) becomes a stilted manual voice.
RFP responses: you're explaining why your company is the right fit. The stakes are higher, so the writing becomes more defensive. Qualifiers multiply. By the time you hit send, the authentic case you made on the discovery call has been diluted into something safer and weaker.
Every async context where people form opinions of your expertise, you're running the same cycle: speak it naturally, then edit it into careful.
What Actually Happens When You Get Your Voice Back
Recitey runs Whisper locally on your Windows machine. No word limit. No monthly metering. No cloud recording of your drafts.
You speak your follow-up message the way you'd say it on a call. The software cleans it into a polished sentence in under two seconds. Not word-for-word transcription. Actual polish. The kind that makes your thinking clear without your voice disappearing.
For Maria, this changed the texture of three parts of her job:
Slack to the team used to take: research call plus four rewrites plus 30 minutes. Now: research call plus one voice draft plus send. 8 minutes total. Her internal notes sound like her, not like someone performing professionalism.
Email to investors (she's raising a round): she speaks the email the way she'd pitch it. The software cleans it. Her actual reasoning survives the async medium. Investor feedback shifted from "sounds cautious" to "clear and confident."
Architecture decision document (RFD for a major refactor): she voice-drafted the reasoning section instead of sitting with a blank page. The result felt more like her actual thinking. Engineers engaged differently with it. Less "let me interpret what Maria meant" and more "I understand the tradeoff she's weighing."
The trade-off is straightforward: you need to be in a space where you can speak your draft aloud. A quiet office, a private call, headphones with a mic. That's not overhead for async-first work. It's a feature.
The Trade-offs Are Real, and They're Worth It
Recitey isn't magic. It's a medium shift, and every medium shift has constraints.
Environment: You can't draft your important email in an open office or on a noisy commute. You need quiet. Most people at senior levels already have that built into their routine (morning focus time, private office, working from home). For those who don't, it's a real constraint. But it's also why many async-first companies are building quiet time into the day. This isn't a Recitey problem. It's a symptom of async-first work that already exists.
Privacy: You're speaking something that used to stay in your head. Some people feel self-conscious saying drafts aloud. But that feeling fades after three or four times. More importantly, you're speaking to software that runs locally on your device. Not a cloud service recording everything. Not a transcription company archiving your words. Your voice stays on your machine.
The learning curve is shallow. There is no complex setup. No special dictation language to learn. You open the app, select your text field, press the hotkey, and speak. That's the interface. Most people get comfortable in under five minutes of actual use.
What nobody tells you is the psychological shift: the first time you send an important message without rewriting it four times, you second-guess yourself. Did I sound too casual? Too direct? The answer is: you sounded like yourself. That version of you that your manager sees on calls. That's the point.
The Version of You on Calls Doesn't Have to Disappear in Writing
Your fluency in English is real. Your hesitation with writing is not about the language. It's about the medium and the identity friction of performing carefulness when you're not a careful person.
The solution is not to get better at writing in your second language. You already write well. The solution is to stop paying a 30-minute tax every time you need to sound like yourself in async.
When your brain doesn't have to do four rewrites to feel safe, when your voice survives the medium, when your team sees the sharp version of you in writing the way they see you on calls, the work changes.
The medium shouldn't erase you.