What Bangladeshi freelancers get wrong about their own English level

Rafi has been doing WordPress development for four years. His proposals are detailed, his code is clean, and he once wrote a 600 word Upwork cover letter that landed him a $4,000 project with a company in Manchester. He has never, in four years, spoken to a client on a video call.

Not because clients do not ask. Because he says no.

He tells them he prefers async communication. This works, until the client is big enough to want a proper conversation before signing, and then the project goes to someone else.

The mistake Rafi is making, and it is not grammar

Rafi believes his English is not good enough to speak. He will tell you this directly. He has been telling himself this since secondary school, where English was taught as a subject to pass rather than a language to use, and where getting a tense wrong in front of thirty classmates had consequences.

That belief is doing enormous damage, and the strange thing is that it is factually incorrect.

His written English proves it. The 600 word proposal was not translated. It was not corrected by anyone. It came out of his head, in English, and a client in Manchester read it and trusted him with $4,000. A person whose English is insufficient cannot do that.

What Rafi cannot do is speak under pressure to a stranger who is deciding whether to pay him. That is a completely different problem, and it has a completely different solution. He has been preparing for the wrong exam for four years.

What clients in the US and UK actually hear

Here is something worth sitting with: the clients most Bangladeshi freelancers are trying to impress are not grammarians.

The average client at a small company in Austin or Bristol is a founder, a marketing manager, or a product lead. They are busy. They are not parsing your verb tenses. They are asking one question, almost always the same question: can I trust this person to understand what I need and tell me when something is going wrong?

That question gets answered in the first ninety seconds of a call. It gets answered by whether you can explain your thinking clearly, by whether you ask a sensible follow up question, by whether you say "I have not done exactly that before, but here is how I would approach it" instead of going silent.

It does not get answered by whether you said "whom" instead of "who."

A client will hire someone who says "we make the homepage load more fast" with total confidence over someone who says "I would humbly like to suggest that perhaps the page speed optimisation could be considered as a potential area for improvement" and sounds terrified the whole time. Both sentences have problems. Only one of them signals competence.

The thing Bangladeshi schools actually taught you

Bangla medium schools taught English as a literature and grammar subject. This is worth being honest about, because the legacy of it is specific and real.

It means most Bangladeshi freelancers can read English extremely well. They can write carefully constructed sentences. They understand complex documentation. They can follow a fast speaking American client on a call without missing the meaning.

What it did not teach was the performance of speaking. Not because the English was missing, but because there was almost no environment where a student was asked to speak conversational English out loud, unprepared, to a person who might push back. The grammar was corrected constantly. The speaking was almost never practised at all.

So the gap is not knowledge. It is exposure to a specific kind of pressure.

The grammar was never the weak point. The call was always the weak point. Those are not the same thing.

This matters because fixing the wrong thing wastes years. If Rafi spends the next six months studying grammar he does not need, he will have better grammar and still say no to video calls.

Why speaking feels so different from writing

When you write a proposal you control the clock entirely. You can think of a sentence, decide it is wrong, delete it, make tea, come back and try a different structure. The client never sees any of that. They see the final version, which looks fluent, because you had unlimited time to make it fluent.

A call removes all of that in one second.

Now you have to produce a complete, confident answer to a question you did not expect, while a real person watches your face, in somewhere between one and three seconds. And you are also monitoring your own grammar, reading their expression, deciding whether they understood you, and remembering what you were going to say next.

The monitoring is the part that breaks everything. It is the specific habit that grows in environments where being corrected publicly was routine. You start a sentence, notice halfway through that the word is not exactly right, and you stop and restart. The client hears that restart as hesitation. The restart is actually happening because you are trying to be correct. The irony is genuinely painful.

A fluent speaker with fewer ideas will say something grammatically loose with complete confidence and get the project. You will say something more accurate while visibly doubting yourself and not get it.

This is what nobody says out loud.

Practising writing more is the wrong answer

Some freelancers respond to this problem by getting better at written communication. Longer messages, more detailed updates, meticulous documentation. All of that is genuinely valuable, and none of it moves the needle on the call.

Others practise speaking with a friend. This is closer, but the friend is kind. The friend will wait while you find the word. The friend will not say "honestly $1,200 seems high for a landing page, the last person I spoke to quoted $600" and then go completely silent and look at you. The friend does not have money and is not deciding whether to give it to you.

The pressure is the actual training. Remove it and you are rehearsing the wrong thing.

This is what Fluenstra is designed for. You speak out loud against an AI client who behaves the way a real buyer does: pushing back on your rate, asking you to justify a decision, going quiet after you say something. After the call you get a scored report on what you actually said, not what you meant to say. A native English teacher who has already read that report then works through the specific moments where you lost ground.

It is not an English course. The English is not the problem.

The call you have been avoiding

Here is something uncomfortable to say, but it is true and you probably already know it.

If you have been avoiding calls for more than a year, the avoidance itself has become the habit. Every time you steer a client toward email or Slack, you get a small relief, and that relief trains you to do it again next time. You are now very practiced at avoiding the thing, and completely unpracticed at the thing itself.

There is no clean answer to this. The only way through it is a call that feels uncomfortable, which goes reasonably well, which teaches your nervous system that the uncomfortable thing does not kill you. Then another. Then another.

What you can control is how much the first one costs if it goes badly. A real client call with $3,000 on the table is a terrible place to discover you do not know how to answer "why should I pick you over the other developers I am speaking to." A practice call where the worst outcome is a scored report is a much better place for that discovery.

The way Fluenstra structures this is specifically so that the practice has enough pressure to be useful but no real money at stake. That is the gap between practising with a friend and practising on real clients, and it is the gap that most freelancers fall into for years.

One thing you can do before any of that

If you have a call this week and you are anxious about it, there is one change that costs nothing and has an immediate effect.

Stop filling the silence.

When a client asks something you did not expect, the instinct is to start talking immediately and figure out the sentence while you are saying it. That instinct produces "yeah so um, basically, I think what I would do is, like." Every freelancer knows that sound. Every client notices it.

Two seconds of actual silence produces nothing. It reads as thinking. It sounds like someone who is not panicking.

After the silence, say a shorter sentence than you planned. "There are two things I would do differently. The first is the information architecture." Then stop. Let them respond. You do not have to deliver everything in one breath.

The grammar can be imperfect. The thinking needs to be visible.

Rafi's English was never the thing standing between him and that Manchester client picking up the phone. It was the assumption that it was, and the four years of practice calls he never had because of it.