Freelance proposal examples that sound human (not salesy)

If you are staring at a job post and your brain goes blank, you are not alone. Most freelancers do not need more motivation. They need a structure that reads like a real person wrote it, with slots for proof, plan, and next step.

Below are three example openings and bodies you can adapt. They are intentionally plain. The goal is clarity and relevance, not hype. After the examples, there is a short checklist for adapting tone by niche (dev, design, writing) without sounding like a different person entirely.

If the brief is thin, pair these patterns with how to write a strong proposal when the job post is basically empty.

Example A: short intro + proof + plan

When to use: The post is reasonably clear; you can name the outcome and constraints.

---

Hi [Name],

I read your brief and the outcome you want is clear: [one sentence restating the goal in plain language].

I have done similar work for [type of client / industry], including [one concrete detail: stack, niche, deliverable, or metric]. Here is how I would approach your project:

1. [Step 1]: tied to a requirement they named (e.g. integration, page set, migration).
2. [Step 2]: tied to a risk or constraint (deadline, legacy code, content readiness).
3. [Step 3]: tied to delivery: reviews, handoff, documentation, or training.

Timeline / scope: [Ballpark or milestone] assuming [assumption you are willing to state]. If [X] is different on your side, I will adjust.

If it helps, I can start with [small milestone] so you can evaluate quality before committing to the full scope.

---

Why this works: Goal first, one proof point, visible thinking, optional de-risking milestone.

Example B: when the job post is vague

When to use: The post is a sentence or two; you need to show judgment without faking certainty.

---

Hi [Name],

Your post is light on details, so I will be direct about what I need from you and what I can deliver.

Based on what you wrote, I am assuming you want [best good-faith guess]. If that is wrong, tell me the correct outcome and I will adjust.

My default approach would be:

• [Phase 1]: clarify [X] and lock [Y].
• [Phase 2]: build / deliver [Z] with [check-in rhythm you prefer].

What I need from you to quote accurately:

1. [Specific question about “done”]
2. [Specific question about assets / access]
3. [Specific question about deadline / stakeholders]

Once I have those, I will reply with a fixed scope, timeline, and price range (or a short paid discovery step if the work needs it).

---

Why this works: You still show a point of view while being honest about missing info.

Example C: when you need to show you read their post

When to use: They mentioned something unusual, technical, or easy to miss. Quoting it builds instant trust.

---

Hi [Name],

You mentioned [exact phrase or requirement from their post]. That matters because [one sentence on impact: SEO, performance, legal, UX, data integrity, etc.].

I would handle it by [specific approach], and I would avoid [common mistake] because [short reason tied to their situation].

Plan in brief:

1. [Step tied to that requirement]
2. [Step for validation / review]
3. [Step for launch or handoff]

Open point: [One question if something is still ambiguous].

---

Why this works: It is hard to fake; it signals close reading and domain judgment.

Adapting the examples without sounding generic

Swap these levers per send:

Lever	What to change
Outcome	Their words, not your service label.
Proof	One project, one metric or artifact, not your whole resume.
Plan	Three steps max in the first message; details can follow.
Risk	Name an assumption; invite correction.
Ask	Numbered questions; easy to reply in one message.

Tone by discipline (same skeleton, different vocabulary)

• Development: Name stack, environments, and what “done” means (tests, deploy, docs). See also web developer proposal template.
• Design: Reference users, brand constraints, and revision boundaries.
• Writing / marketing: Reference audience, channel, and success metric (CTR, signups, clarity).

You do not need a different template for each. Just different nouns and proof.

What usually makes these work

• You repeat their goal in your own words.
• You show one specific proof point, not a generic bio.
• You give a plan with steps, not adjectives.
• You end with a next step they can take without guessing.

What to edit last (the “human 10%”)

After you draft from a structure, manually adjust:

• One sentence that only fits this client.
• One honest caveat or assumption.
• The exact milestone you would actually offer.

If you want this tailored to a real post you have open right now, use Lervos to generate a first draft in your voice, then edit the specifics.

For more on why proposals get ignored before you even get to examples, see why clients ignore your proposals. For a quality gate before you send, use the freelance proposal checklist.