You're fluent in English on calls. You can handle objections in real time, build rapport with enterprise buyers, speak with the authority your title demands. Then you open Slack to reply to a colleague, and the certainty vanishes. You re-read the message three or four times. You swap words around. You check for grammar errors that weren't there. Thirty minutes later, you send something that sounds smaller than how you actually think.
The call-to-Slack gap
Maria, a senior account executive at a European SaaS company, talks to this gap every week. Her performance reviews consistently note "excellent executive presence on calls" and "could be more concise in writing." She knows the second assessment is wrong. The conciseness gap isn't real. It's a medium problem masquerading as a capability problem.
On a call, Maria has access to intonation, pace, and pause. She can layer meaning through tone. When she speaks, her voice carries the authority her role demands. In Slack, all of that disappears. The written version of her thoughts feels flatter, more cautious, more careful. The gap between how sharp she sounds on a call and how hesitant she sounds in writing isn't a vocabulary gap or a grammar gap. It's a time gap. It's a friction gap.
The rewrite tax
Most nonnative English speakers in professional roles experience this as a brutal arithmetic problem. A Slack message that should take 30 seconds to compose ends up taking 30 minutes. Not because they don't know English. Because they're running a verification loop in their head that native English speakers don't run.
The loop works like this: speak the thought, type it out, re-read it, notice something sounds off (even though it's correct), rewrite for tone, re-read again, verify the grammar is right, read it one more time, worry that it sounds too short or too formal, adjust phrasing, read it a fourth time, and finally hit send.
Native English writers don't do this. They type and ship. The asymmetry is brutal over time. If you send 20 Slack messages a day and each one adds 25 minutes of verification time, that's 500 minutes a week. That's more than eight hours of your week, every week, spent in a verification loop that the medium created, not your actual capability.
Voice-to-text sounds good. Then you try Otter.ai
It makes sense to consider existing voice tools. Otter.ai is probably the most popular choice. It's fast, it handles accents reasonably well, and it's built by people who understand what transcription can do.
But Otter.ai is built for a different problem. It's optimized for transcribing meetings, capturing what was said, and letting you review the transcript later. It's a record-keeping tool. You speak into Otter, it transcribes, you get a document you can edit and share. That's useful if you're documenting what happened in a call. It's not useful if you need to speak a Slack message and have it land in Slack immediately, sounding like you.
For Maria's workflow, Otter.ai creates extra friction. She'd have to speak a message into Otter, wait for transcription, copy the text, switch back to Slack, paste it, read it over, fix whatever auto-corrected wrong, and then send it. That's still a rewrite loop. It's just a different flavor of rewrite loop.
The problem isn't transcription quality. The problem is that the tool isn't designed for the workflow. It's designed for meetings, not for async writing.
The wedge: voice in Slack, no transcription step
What you actually need is a tool built for exactly this moment: you speak your message the way you'd say it on a call, and it lands in Slack sounding like you. No step in between. No transcription window. No copy-paste dance.
Recitey is built for this specific workflow. It runs on Windows and pipes voice into any app through the system clipboard (Slack, email, browsers, docs). No metering, no word limits, no capping on free tier. Speak the message, it transcribes in under 2 seconds, and it lands where you're writing. You can optionally polish it (Recitey smooths rough speech into clean writing), or you can ship it raw.
For Maria, the result is immediate. A message that would have taken 30 minutes to write by hand takes 30 seconds to voice and ship. The identity gap collapses. You sound in writing the way you sound on a call. The authority doesn't evaporate in the medium.
The tradeoff
There's a real cost. Voice-first writing means you lose the buffer of the rewrite loop. You can't obsess over word choice before shipping. You have to trust your voice the way you do on a call. For someone who's spent years in the verification-loop habit, that feels risky at first.
The risk is overstated. You're already confident in your spoken English on calls. You're already making real-time decisions about phrasing and tone in live conversations. Shipping a Slack message as voice-to-text is not actually riskier. It's just unfamiliar.
The moment it clicks
The shift happens when you realize the rewrite loop was a tax you paid out of habit and insecurity, not out of actual necessity. The first time you speak a message into Slack and ship it without the verification loop, you notice something: it sounds like you. It sounds exactly like how you'd say it on a call. The authority that vanishes in the medium doesn't vanish if the medium captures your voice.
Your written English doesn't need fixing. Your medium does.