The client relationship that taught me the most about international work wasn't difficult because of anything I couldn't say in English. It was difficult because of things I could say perfectly well, that meant something different to the person reading them than what I intended — and the reverse, feedback I read confidently and understood exactly backwards.
The project was content writing for a US-based startup: four articles a month, $800 total, a rate that looked perfectly reasonable going in. The first sign of trouble came after the first article. The only feedback was "the direction feels off" — no specifics. I'd written it to spec as I understood it, so this was genuinely confusing on my end. The actual problem turned out to be a tone mismatch that had never been made explicit: the client wanted casual and approachable, and I'd written something more formal and expertise-forward, a completely reasonable interpretation of the brief that just happened to be wrong. With a full day's turnaround on every question because of the time difference, a piece that should have taken three to four hours took five days to actually finish.
Where the real time went
The second article surfaced a sharper version of the same problem. A comment on the draft said "tighten this section." I read that as "this section needs more substance" and expanded it. What the client meant was the literal opposite — cut it down. That single misread cost a full extra revision cycle, and by that point the pattern was clear: ambiguous words weren't a minor friction, they were the majority of the actual cost on this project. By the time the pattern was under control, total time on the four articles that month had run past 28 hours — for a project sized and priced around something closer to half that.
A second, separate stretch of the same relationship surfaced a related but distinct problem: indirect, softened feedback. Phrases like "this might work better if..." or "maybe we can try another angle" read, at first, like optional suggestions. They weren't. They were close to outright rejections, phrased indirectly in a way that's common in professional English feedback but easy to underweight if you're used to more direct, explicit correction. Treating them as light suggestions rather than the real signal they were led to under-revising drafts that then bounced back again.
What actually fixed it
- Three tone samples before writing anything — instead of describing tone in the brief, sending three short sample paragraphs in different tones and having the client pick one removed the single biggest source of first-draft misses
- Forcing ambiguous words into specifics — "tighten," "polish," "refine," and similar words got a follow-up question every time: does this mean shorter, or does it mean something else specific? Guessing was never worth the revision cycle it risked
- A direction check before the piece was finished, not after — a quick outline or partial draft sent for a go/no-go on direction catches a wrong assumption at ten minutes of work instead of at the end of a finished piece
- Turning open questions into forced choices — "does this direction work?" reliably got a vague answer; "should this lean toward A or B, specifically?" reliably got a fast, clear one
- Restating feedback before acting on it — a one-line "so to confirm, you want X, is that right?" before starting a revision catches a misread in thirty seconds instead of a full revision cycle later
The actual lesson
None of this was really about English proficiency. It was about the fact that ambiguity is expensive, and it's easy to miss how much of it is sitting in perfectly fluent, perfectly polite feedback until a project's hours start running well past what the rate assumed. The fix wasn't getting better at English — it was designing the back-and-forth so there was less room for a reasonable-sounding misinterpretation to survive more than one round. After the changes above, round-trips on later projects with the same client dropped by more than half, with no change in the actual writing skill involved.
If international work is genuinely part of the plan, the payment side of it is worth getting right too — see our international payment platforms guide for the fee side of the same equation, and our guide to pricing freelance work if a rate that worked on paper needs a second look once revision time is counted honestly.
This account reflects one freelancer's experience on a specific project. Communication patterns and expectations vary significantly by client, industry, and individual working style — treat this as one data point, not a universal rule for international client work.
Frequently asked questions
Is this really about English fluency?
Not primarily. Reading and writing English at a professional level was never the blocker on this project — understanding what a specific piece of feedback actually meant, and what a client meant by a soft, indirect phrase, was where nearly all the extra time went.
How much did this actually cost, in real numbers?
On the project described here, work that should have taken 3-4 hours per article stretched to 5-6+ hours once ambiguous feedback and time-zone-limited back-and-forth were factored in, and the effective hourly rate on the engagement dropped to roughly half of what it should have been before the process changed.
Do these fixes only work for English-language clients?
No — forced-choice questions, restating feedback in your own words to confirm it, and getting a direction check before a piece is finished are generally useful communication habits for any client relationship where the two of you don't share full cultural or professional context, not just cross-language ones.
Isn't asking a client to choose between A and B annoying for them?
In practice it tends to be the opposite — a specific, answerable question is faster for a busy client to respond to than an open-ended one, and it removes the ambiguity that was costing both sides time and frustration in the rounds of revision that followed vague feedback.