The freelance proposal checklist (before you hit send)
A quick quality gate: clarity, proof, scope, risk, and a CTA that makes replying easy.
Use this like a pilot checklist: boring on purpose, fast to run, and effective at catching the mistakes that cost replies: not typos, but missing signal.
It works for Upwork-style cover letters, short marketplace messages, and longer email pitches. After the core checklist, you will find failure modes, a scoring shortcut, and a revision order when you are short on time.
The core checklist (mandatory)
- Client goal restated in one sentence (their vocabulary, your structure)
- One proof point tied to their job, not generic “years of experience”
- Plan with 3-5 steps; each step references something they asked for or implied
- Unknowns called out explicitly (access, content, approvals, legacy constraints)
- Timeline stated with at least one explicit assumption
- Pricing posture clear: range, model, milestone quote, or 2-3 smart questions that unlock a quote
- Easy next step: one primary ask: answer these bullets, approve milestone, or pick a window (do not bury three competing CTAs)
- No template smell: remove phrases you would not say aloud; add one sentence only true for this client
Extended checks (when the job is large or fuzzy)
- In-scope vs out-of-scope boundary: at least one line on what you are not including unless added
- Risk reducer: audit, trial milestone, or staging-first approach if codebase or stakeholder risk is high
- Communication rhythm: how often you update and through which channel
- Revision / change policy: one line so expectations match (especially for design and copy)
- Dependencies on the client: what you need from them and by when for dates to hold
Failure modes this catches
| Symptom | What is usually wrong |
|---|---|
| You reread and feel “fine” but get no replies | Missing specific proof or specific tie to their post |
| Client ghosts after enthusiasm | Next step unclear or pricing feels hidden |
| Scope fights after hire | Out-of-scope not stated; assumptions not named |
| “You sound like AI” | Generic adjectives; no proper nouns from their world |
If you fail one item
Do not rewrite everything. Fix in this order (highest leverage first):
- Proof + post tie-in: one detail quoted or paraphrased from their brief.
- Plan steps: each step must reference a requirement or risk.
- Pricing / path to pricing: remove ambiguity without being evasive.
- Next step: single action the client can take in one message.
- Trim: cut bio and repetition; density beats length.
30-second “score” (optional)
Rate each block 0-2 (0 missing, 1 weak, 2 strong): Hook · Proof · Plan · Risk · Price · CTA.
If any block is 0, fix it before sending. If everything is 1, you are probably competitive; make one block a 2 with specifics.
How this connects to the rest of the blog
- Examples of human-sounding openings: freelance proposal examples
- Why proposals get ignored: why clients ignore your proposals
- Vague job posts: short job post proposals
When you want this turned into a full draft, generate from the job post and then use this checklist as your final edit pass before you send.
Run your checklist, then let AI build the first draft
Save your experience, wins, and positioning once in Lervos. For each new lead, paste the job post. Our curated proposal AI builds a structured draft that sounds like you, not a generic template. Edit what you want, send when you are ready.