You're sharp on the call. Present, direct, quick to land the insight that changes the conversation. Then you draft the follow-up Slack message and something shifts. The voice changes. You read it back and it sounds smaller, more cautious, like you're apologizing for speaking at all.
The daily friction: the Slack rewrite cycle
You rewrite it. Three times. Four times. Each version sounds more careful than the last. You strip out the directness. You add hedges. By the time you hit send, you've drained the message of the actual thing you meant to say, which was direct and fast and exactly what landed on the call.
This happens to people who are fluent in spoken English. For non-native speakers in professional contexts, the pattern is sharper and the cost is higher. The extra rewrite cycle isn't about grammar or vocabulary. It's about presence.
Maria's performance review gap
Maria is a senior account executive at a European B2B SaaS company with eight years selling to US enterprise. She speaks English better on live calls than most native speakers do. Her last two performance reviews noted "exec presence on calls" as a strength and flagged "could be more concise in writing" as a gap.
She knows the gap isn't real. It's the medium.
On a call, you have tone of voice, pacing, facial expression, the ability to read the room and respond. You're not managing the interpretation of your meaning; you're embodying it. The person on the call hears directness and confidence. When you write in Slack, none of that texture exists. The text box is flat. So you compensate. You become more formal. More hedged. More careful. You add qualifiers that flatten your actual intent into something that sounds like a non-native speaker apologizing for taking up space.
The gap isn't a language gap. It's a medium gap.
The research on async composition time
Multiple studies on async communication show that non-native English writers in professional contexts spend 40-60% more time composing written messages than their native-English peers. Most of that extra time is revision, not composition. You already know how to construct a sentence. You're stuck in the rewrite loop because the medium makes you self-conscious. You're checking and rechecking and hedging further.
The tool you're using doesn't make you more confident. It makes you more aware that you're being read, not heard.
Why the dictation tools you've tried don't solve this
You might have already tried Microsoft Voice Typing. It's built into Windows, you got it for free, and you probably opened it, spoke a Slack message, and got a rough transcription. Then you spent ten minutes editing it because it caught the wrong words or misread your accent. Or you stayed in Slack and typed instead because leaving the app killed the momentum.
Microsoft Voice Typing is fine if you're transcribing a meeting or taking voice notes. It's not built for the specific friction you face: drafting async professional messages in a second language without losing your voice in the rewrite cycle.
Otter.ai is better at transcription accuracy, but it's expensive, designed for meeting recordings and interviews, and it still leaves you with a transcript you then have to edit and reshape into Slack-format writing. You'd still be rewriting, still be in the self-conscious loop, still watching the minutes accumulate.
What you need isn't just transcription. What you need is the confidence to send a message that sounds like the person your team just heard on the call.
What happens when you speak into the writing tool
The instinct here is fear: won't speaking my Slack message make it sound too casual? Unprofessional? Unpolished? No. When you speak your actual thought without the rewrite filter, you sound more executive, not less. You sound like someone who knows what they mean and isn't afraid to say it directly. That's what presence looks like in writing.
The problem isn't your English. The problem is that the tool you're using to write, the text box, the rewrite cycle, doesn't give your competence anywhere to show. It shows self-doubt instead.
How Recitey works differently
Recitey doesn't ask you to fix your English. It transcribes what you actually say. You speak the message as you would say it on a call. Not in a "writing voice." In your actual voice, the one that was present and confident when you were speaking out loud. The system transcribes the audio locally on your device with no word limits and no metering, then polishes it into clean, readable text. You're not rewriting. You're not translating your thought into careful, hedged English. You're just saying what you meant.
The rough draft that comes back from transcription is already recognizable as you.
Maria's shift
Maria sent her last three follow-up messages to clients by voice instead of typing them in the Slack box. Her team noticed immediately. One colleague asked if she'd changed her writing style. She had. She was just writing how she talks.
The messages were faster to produce. The follow-ups sounded like the person the client had just been on a call with, not like a careful, more-formal version of that person. The response time was faster. The replies were more engaged.
Her manager asked what had changed. Maria said she'd stopped rewriting.
The time trade-off
The message that used to take 20-30 minutes in the Slack text box now takes 90 seconds to speak and polish. You stop the rewrite cycle. You stop editing yourself into a smaller version of yourself. The voice that got you through the sales call, the one your manager identified as a strength, now appears in your follow-up messages.
You still sound professional. You just sound professional as yourself, not as a carefully hedged approximation of yourself.
The 20-30 minutes you get back is time you can spend on the actual work: the follow-up action, the next call prep, the deal notes. Not on the anxiety of "did that message sound smart enough."
The real question
You can write good English. The question isn't whether you can do it. The question is whether the tool you're using to write is actually letting that competence show, or whether it's making you sound like a watered-down version of yourself while you wait for the rewrite cycle to finish.
That gap between how you sound on a call and how you write in Slack isn't a language gap. It's a tool gap. And it costs you 20-30 minutes per message, and it costs you the presence that got you here in the first place.