Read for the problem behind the request
A client may ask for captions, a dashboard, or product listings, but the business problem could be inconsistent publishing, scattered information, or slow store updates. Reflect the actual problem in the opening sentence so the client knows you read the brief.
Use a five-part proposal
- Relevant observation: name the specific need you noticed.
- Proposed approach: explain how you would handle it in one or two sentences.
- Proof: link one closely related sample or describe relevant experience honestly.
- Clarifying question: ask for information that affects scope or quality.
- Next step: suggest a short call, reply, or small paid first milestone.
Keep the opening specific
Avoid openings such as "I am the perfect candidate" or a long list of tools. A stronger opening sounds like this: "You need twelve existing product listings rewritten into one consistent format before the new collection launches. I would first standardize the title, benefit bullets, and product details, then review the full set for missing information."
Use proof that matches the job
One relevant sample is stronger than a folder of unrelated work. If you have no client example, share a clearly labeled concept sample and explain how it relates. Never invent a client, testimonial, or result.
Ask a question that moves the project forward
Good questions expose a decision the client must make: audience, source material, approval process, access, brand rules, or deadline. Avoid asking for information already stated in the brief.
Make the proposal easy to scan
- Use short paragraphs.
- Remove generic compliments.
- Do not paste a full biography.
- State availability only when it affects the deadline.
- Proofread names, links, dates, and attachments.
The goal is not to sound impressive to everyone. The goal is to sound useful to this client.
A practical proposal template
Opening: I saw that you need [specific deliverable] because [business context].
Approach: I would start by [first step], then [second step], and deliver [defined output].
Proof: Here is a relevant [sample or example] showing [specific capability].
Question: Before confirming scope, do you already have [important input], or should that be included?
Next step: If this matches what you need, reply with [simple action] and I can outline the first milestone.