You spent 40 minutes on the proposal. You checked it twice with a translator. You sent it.
No reply.
The problem might not be the grammar. The problem might be specific patterns that are invisible to grammar checkers — phrases that are technically correct but sound off to a native English reader in the first three seconds of scanning your proposal.
The patterns that signal "non-native" before the second sentence
1. The formal opening
English professional communication is surprisingly casual. Many non-native writers open with formal phrases that are correct but sound stiff.
Sounds stiff
"I am writing to express my interest in the above-mentioned position and to present my qualifications for your consideration."
Sounds natural
"I've done this kind of work before — let me tell you what I noticed in your project description."
2. "I am a hardworking and dedicated professional"
Adjectives about yourself that aren't backed by evidence don't communicate anything. Native English writing leans on specifics, not self-description. The adjective "hardworking" in a proposal is almost always a signal that the writer has nothing specific to say about the job.
Vague
"I am a dedicated, detail-oriented professional with strong communication skills."
Specific
"I caught three bugs in a client's API before they went to production last month. Here's what I noticed in your spec."
3. Article errors (a / an / the / nothing)
This is the hardest category. English articles follow rules that most languages don't have equivalent structures for. Common mistakes: missing "the" before something specific, adding "a" before uncountable nouns, or writing "an" before a word starting with a consonant sound.
Typical errors
- × "I have experience in web development" → ✓ same (no article needed — uncountable in this context)
- × "I will deliver a quality work" → ✓ "quality work" (work is uncountable)
- × "I can fix issue you mentioned" → ✓ "the issue you mentioned"
4. Over-translated idioms
Phrases that work perfectly in your native language sometimes translate literally into English but mean something slightly different, or just sound unnatural. These are hard to catch without a native reader.
Common over-translations
- × "I will do my best efforts" → ✓ "I'll give this my full attention"
- × "Please do not hesitate to contact me" → ✓ "Feel free to reach out" or just nothing
- × "I am looking forward to having the opportunity to work with you" → ✓ "Happy to discuss further"
5. Missing contractions
Native English speakers use contractions constantly in professional writing: I'm, I'd, I'll, it's, we've, you're. Writing "I am" where a native would write "I'm" is technically correct — but across a full proposal it creates a formal, distant tone that reads as unnatural.
Too formal
"I am confident that I would be a strong fit for this project and I am available to start immediately."
Natural
"I'm confident this is a good fit and I'm available to start this week."
The fastest way to check your own proposal
Read it out loud. Slowly. If you stumble on a phrase, a native reader will too. If it sounds like something you'd say in a business conversation, it's probably fine. If it sounds like a formal letter, rewrite that sentence.
Proposal Engine generates proposals in natural, direct English — useful both as a draft and as a reference for how a native-sounding proposal reads. It also has a Review mode: paste in a proposal you wrote and it identifies what feels weak, including phrasing that might not land the way you intend.
One-time purchase · No subscription · ~$0.01 per proposal
Try Proposal Engine
Generate or review Upwork proposals in natural English. Generate, Review, and Refine modes included.
See how it works →Frequently asked questions
Do grammar mistakes hurt your chances on Upwork?
It depends on the mistake and the job. For writing, editing, or communication-heavy roles, grammar mistakes hurt significantly — the proposal is a sample of your work. For technical roles like development or data analysis, minor grammar issues matter less. That said, clarity always matters — if a client has to re-read your proposal to understand what you're saying, that's a problem regardless of the job type.
Should I use Grammarly for Upwork proposals?
Grammarly catches obvious errors well, but misses subtler issues like awkward phrasing, overly formal sentence structure, or idioms used incorrectly. It's worth running a proposal through Grammarly as a baseline check, but don't stop there — read the proposal out loud and ask whether each sentence sounds natural.
How do I make my proposal sound more natural in English?
Write short sentences. Remove filler phrases ('I would like to take this opportunity to...'). Avoid translating expressions word-for-word from your native language. Read English content from native speakers in your field — not to copy, but to absorb what natural professional communication sounds like in that context.
Is it okay to mention I'm not a native English speaker?
Generally, no — don't apologize for your English before the client has any reason to doubt it. If your proposal is clear and professional, mentioning non-native status introduces a doubt that didn't exist. If your proposal has obvious issues, fixing the issues is more effective than disclosing the reason for them.
What's the biggest mistake non-native English speakers make in proposals?
Over-formality. Writing 'I am eager to provide my expertise in service of your esteemed organization' instead of 'I'd love to help with this.' Native English professional writing is casual in register even when it's precise and professional in content. When in doubt, write the way you'd talk in a professional conversation.