How to Write a Proposal That Doesn’t Get Rejected: From the First Line to the Signature

A potential client opens twenty proposals in a single session. Twenty translators and writers want the same project — all of them say they are professional, all of them promise quality and on-time delivery.

What makes them stop at your proposal specifically?

Usually not the lowest price. And not the longest proposal. What makes them stop is the feeling that this person actually understands what I need — not that they are sending the same message to everyone.

In this piece we look at the structure of a proposal that gets read in full and leads to a conversation — not the proposal that gets closed in seconds.

(See our article: How to Price Your Freelance Services: Neither Underselling nor Overreaching)

I. The Most Common Mistake in Project Proposals

Most proposals begin with a sentence that resembles this: “I am a professional translator with five years of experience, fluent in Arabic and English, and committed to deadlines and quality.”

The problem? This sentence does not speak about the client — it speaks about you. And when a client reads your proposal, they are not looking for your CV — they are looking for the answer to one question: does this person understand my problem?

The proposal that begins by demonstrating understanding before demonstrating competence advances past nine out of ten competing proposals — even if their authors are objectively more experienced.

“The client is not buying your experience — they are buying their confidence that you will solve their problem. The difference between the two is the difference between a proposal that gets read and one that gets deleted.”

II. The Structure of a Proposal That Gets Read in Full

An effective proposal is not long — it is organized. Five sections, each serving a specific function:

1. The Opening: Prove That You Read

The first sentence must prove to the client that you actually read their request — not that you sent a mass message. Reference a specific detail from their request, the challenge they face, or the context they mentioned.

Weak example: “I am a professional translator and would like to apply for this project.”

Strong example: “I noticed the legal document you need translated contains specialized arbitration clauses — which is precisely the type of document I work with more than any other.”

The difference between the two sentences is not length — it is evidence of attention.

2. Understanding the Problem: Restate What They Need

Before presenting yourself, prove you understand what the client actually needs. One paragraph in which you restate the project in your own words — not a repetition of what they wrote, but proof that you understood what lay behind their words.

When the client reads this paragraph and feels understood — the acceptance rate of your proposal rises significantly before you have even mentioned your name.

3. The Solution: What Will You Do Specifically?

No general promises — a clear plan. “I will translate the document, create a terminology glossary for the legal field used, and deliver the final version with notes on any ambiguity in the original.” This shows a methodology most applicants do not possess.

4. The Evidence: One Sample Is Worth a Thousand Descriptions

After the plan, one link or one sample from a previous piece of work similar to the project at hand. Not a large portfolio of everything you have done — one sample with direct relevance. This ends the uncertainty and builds trust in a single move.

5. The Close: A Price and a Clear Next Step

The price with what it includes, the timeline, then one sentence inviting the next step: “If this works for you, I am happy to answer any questions or start right away.” — no pressure, no hesitation.

III. The Right Length — Shorter Than You Think

A long proposal does not demonstrate seriousness — it demonstrates that you do not respect the client’s time.

The ideal proposal for most translation and writing projects falls between one hundred and fifty and three hundred words. If the project is large or complex, up to five hundred words is acceptable — no more.

The simple rule: every sentence in the proposal must answer a question in the client’s mind — not fill a gap in yours.

IV. What Not to Say in Your Proposal

Some phrases weaken a proposal even if everything before them is strong:

• “I am a beginner but I am enthusiastic and will work hard.” — Enthusiasm is not a professional skill. If you are a beginner, prove it through work samples, not promises.
• “My price is flexible and I can negotiate.” — Before anyone has rejected your price. This sentence implicitly says your original price was not serious.
• “I am better than others because…” — Comparing yourself to unknown competitors diminishes the proposal rather than elevating it. Speak about your value, not about others’ weakness.
• A long list of skills: “I am skilled in legal, medical, technical, literary, and marketing translation…” — This tells the client you specialize in nothing. Better: focus on what is relevant to their specific project.

V. Tailoring Each Proposal — No Copy and Paste

It is acceptable to have a basic template for your proposals — this saves time. But the template must be a structure, not a ready-made text.

What must be customized in every proposal:

• The opening sentence — always specific to the particular project.
• The problem understanding paragraph — reflecting the context the client mentioned.
• The sample or evidence — the closest to the nature of the requested project.

What can be reused:

• How you explain your work methodology.
• The closing formulation and the call to connect.
• Your standard terms and guarantees.

The client who feels your proposal was written for them alone — even if it took you five extra minutes — responds differently from one who feels they are a number on a mailing list.

“A personalized average proposal beats an excellent mass proposal — because the first proves interest and the second proves laziness.”

VI. Following Up After Sending the Proposal

You sent your proposal and have not received a response after two or three days. What do you do?

One follow-up message — no more — is entirely acceptable and professional. Not pressure, but a gentle reminder that opens a door:

“I wanted to check that my proposal arrived and whether you have any questions. I am available to talk whenever that suits you.”

That is sufficient. A third message after silence turns interest into annoyance.

And the client who does not respond to two messages has, in most cases, made their decision. Do not invest more time following up — move on to other projects.

(See our article: Soft Skills Every Freelancer Needs: What Courses Don’t Teach You)

VII. A Sample Proposal — A Complete Applied Example

Below is an applied example of a project proposal for translating a legal document — embodying the five-part structure described above:

—

Opening:
I read your request carefully — the document you need translated involves commercial agreements between two parties from different legal systems, which requires a translator who understands the differences in legal phrasing between the two contexts, not simply one who owns a legal dictionary.

Understanding the Problem:
What you need is not just a literal translation — but an Arabic text that carries the same legal binding force as the English original, comprehensible in a way that does not lead to different interpretations in the event of a dispute.

The Solution:
I will translate the document while preserving the original legal structure, attach a terminology glossary for future reference, and flag any ambiguity in the original that warrants a lawyer’s review before signing.

The Evidence:
Here is a sample from a similar contract I translated last year for a client in the logistics sector: [sample link]

Price and Next Step:
The total project price is $250, which includes the full translation, the terminology glossary, and one revision round, with delivery within four business days. If this works for you, let me know and I will begin upon receiving the advance payment.

—

Notice: the proposal never said “I am professional” or “I work hard” — because every word in it proves that instead of claiming it.

Conclusion

A good proposal does not convince the client you are the best — it convinces them you are the most suitable for their specific project. And this is an important distinction: the objectively best does not always win — the most contextually suitable wins almost every time.

Read the client’s request twice before writing a single word. Then write for the client — not about yourself.

(See our article: How to Market Yourself as a Translator or Content Writer: From Unknown to In-Demand)