← BlogFor non-native-english

Sounded like the careful version of yourself

You're sharp on calls. Your manager knows it. Your clients hear it. Then you move to Slack and you rewrite the message three times.

The gap between how you sound when speaking and how you sound when writing isn't a language problem. It's a medium problem.

The call versus the message

On a call, you're direct. You interrupt yourself to correct mid-sentence. You use your hands. You speak faster than you think. Native speakers do the same thing, so your accent is just part of the rhythm. You're present.

In Slack, you slow down. You write a sentence and read it back. Does "take care of this issue" sound efficient or dismissive? Would "prioritize this" sound more professional? You rewrite it. Then you read it again.

This is not a vocabulary gap. Your English is good. Your clients validate this constantly on calls. The problem is that async writing surfaces the part of communication that native speakers control through tone, pace, and presence, none of which survive the text-only medium.

Most tools that claim to help with this assume you're a beginner. Grammarly corrects your grammar. That's not your problem. You're not missing semicolons; you're missing the 12 minutes you spent deciding whether your tone was right. Translation tools make this worse because they erase the voice that survived your accent in the first place.

The cost is time, not competence

Maria is a senior account executive at a European B2B SaaS company. She's exceptional on calls, which is why her performance review mentioned "excellent exec presence on calls" as a strength. It also mentioned "could be more concise in writing" as a development area.

She knows that gap isn't real. It's the medium.

Research on non-native English speakers shows that drafting async business communication takes 2 to 3 times longer per message than it does for native speakers. That's not because they're less capable. It's because the translation between thought, which happens at conversational speed, and written text, which requires careful editing, creates a bottleneck. Your accent doesn't matter when you're speaking. It matters when you're rewriting your own English.

Maria tracks this. Three to four complete rewrites per Slack message. Six to seven rewrites for an important email. A customer follow-up that should take 3 minutes takes 20 because you're not drafting anymore; you're editing a version of yourself that sounds smaller. That lost time adds up. If you're sending five important messages a day, that's an hour lost per week just to the rewrite cycle.

The tools miss the point

The existing solutions all make the same assumption: you need help writing better English. Grammarly polishes grammar. Otter.ai transcribes. MacWhisper captures voice. But none of them solve the real problem.

You don't need grammar help. You need to write like you speak, which you already know how to do fluently. You need the medium to stop forcing you into a slower, more cautious version of yourself. You need a tool that gets out of your way and gives you back your voice.

Speak your thought; get your thought back

What would it mean if the tool did what you already do on calls: take your natural speed, your direct phrasing, your present voice, and deliver it clean?

Recitey works differently. You speak the message at the speed you think it. Locally, your device runs Whisper, the same model powering professional transcription with 96.3% word accuracy on industry benchmarks. It captures what you said, not a guess at what you meant. Then it polishes the rough draft into a clean sentence in under two seconds. No word limits. No artificial caps. No "speaking is for beginners" framing.

You get a written version that sounds like you. Not the careful version. You.

The workflow shift

For Maria, this changes something small but durable. A sales follow-up email used to be: speak the thought, then spend 20 minutes rewriting until the tone felt right. Now it's: speak the thought, get back your thought in clean English, hit send.

The time reclaimed is real. Eight to ten minutes per message, when you're sending five or six important ones a day. But the shift is also psychological. You're not remaking yourself for the medium anymore. You're using a medium that adapted to how you already communicate on calls.

Who this is for

This is for people whose strength is how they sound when present, on calls, in meetings, in conversation. People who know their English is good because clients and colleagues validate it constantly. People who feel exposed in async writing not because they're missing skills, but because the medium stripped away everything that makes them sound like themselves.

If you've ever noticed that your written Slack sounds smaller than your spoken self, that's not a gap. That's just what happens when the medium doesn't match how you communicate best. The solution isn't to become a better writer. It's to find a medium that lets you communicate at the speed and presence you already have.

More posts
Keep reading

More like this.

  1. For non native english

    The 30-minute Slack problem nobody talks about

    You're sharp on the call; your manager noticed it. Your last review said "executive presence." Then you write the follow-up in...

  2. For non native english

    The Slack message you spent 30 minutes on still sounds careful.

    Maria's performance review this year mentioned what it always does: sharp on calls, could be more direct in writing. She'd heard...

  3. For non native english

    The Confident Call, The Careful Slack Message

    You get off a sales call sharp and present. You explain the deal clearly, you ask the right questions, your boss would call it...

All posts →