What a proposal is for
A proposal answers four questions a prospective client is silently asking: Do you understand my problem? What exactly will you do? How long and how much? What happens next? It also shows how you think and communicate, which clients often weigh as heavily as price.
Many proposals fail not because the freelancer is unqualified but because the document is about the freelancer rather than the client: long lists of credentials, general claims and jargon. A good proposal is shorter and more specific than most people expect.
Do the groundwork first
A proposal written without a conversation is mostly guesswork. If possible, begin with a short call or a set of written questions:
- What is the goal of the project, and what prompted it now?
- Who is it for?
- What does success look like, in the client’s words?
- What are the deadline and any fixed constraints?
- Is there a budget range, or an existing process or materials?
- Who makes the final decision?
Notes from this conversation provide the language for the proposal. Reusing the client’s own words signals that you listened.
A simple structure
A one- to three-page proposal is usually enough for small and medium projects. Larger projects may need more detail, but the same order works.
1. The problem and goal. Open with a few sentences describing the situation as you understand it and what the client wants to achieve. This invites the reply “yes, exactly” and builds trust. Do not open with a biography.
2. The approach. Briefly describe how you would tackle it. A short numbered list of steps is often clearer than paragraphs. Explain choices in plain terms, and avoid technical language the client may not know.
3. Scope and deliverables. State what the client will receive: items, formats, quantities. Add what is not included and any assumptions, such as the client providing content by a certain date. If the proposal is accepted, this section often becomes the basis of the scope agreement, so write it carefully.
4. Timeline. Give start date, key milestones and delivery date. Note the dependencies on the client, such as feedback within a set number of days. Allow a realistic margin; a date you can meet beats an impressive one you may miss.
5. Price and terms. State the price clearly, whether fixed, hourly with an estimate or a retainer. If useful, show how it breaks down. Include payment terms such as a deposit and due dates. Considerations for deciding the figure are covered in the discussion of freelance rates. Mention revisions and what extra work would cost.
6. Relevant experience. Two or three sentences, or one or two samples closely related to this project. A link to your portfolio website can sit here. Keep it relevant: “I have worked on similar guides for small training providers” says more than a general list of skills.
7. Next steps. Say exactly what happens if they want to go ahead: sign or reply to confirm, pay the deposit, schedule a start date. Add how long the proposal remains valid, since prices and availability change.
Offering options
Some freelancers present two or three options, such as a basic package, a standard one and a fuller one. This can help a client choose by scope rather than by whether to hire at all. Keep the differences easy to compare, perhaps in a small table:
| Basic | Standard | Extended | |
|---|---|---|---|
| Deliverables | Core items only | Core items plus extras | Everything plus ongoing support |
| Revisions | One round | Two rounds | Three rounds |
| Timeline | Shorter | Medium | Longer |
Do not offer so many options that choosing becomes work. Three is usually plenty.
Writing style
- Use plain language. Short sentences, familiar words and concrete details. Treat it like writing website copy for a busy visitor.
- Be specific. “Two rounds of revisions within ten days” is more useful than “fast turnaround.”
- Avoid hype. Do not promise results you cannot control, such as particular sales, rankings or growth. Describe what you will do, not what will inevitably happen.
- Format for scanning. Headings, short paragraphs and lists let someone grasp the gist in a minute.
- Check the details. Names spelled correctly, figures adding up and dates matching your calendar. A proposal with a visible error undermines trust. Simple checking of totals matters, and basic spreadsheet skills help if your pricing has several lines.
A hypothetical pricing line might read: 12 hours at $50 = $600, plus a 20% buffer for revisions ($120), for a total of $720. Check that: 12 × 50 = 600; 20% of 600 = 120; 600 + 120 = 720.
Make it easy to say yes
Provide the proposal in a common format that opens easily on any device, such as a PDF or a shared document. Send it with a short covering message that summarizes the key point and the main next step. Follow up politely after a few days if you have not heard back. A short note asking whether they have questions is courteous and usually welcome.
When the answer is no, or silence
Not every proposal is accepted, even good ones. Budgets shift, someone else is chosen, or timing changes. Ask, if appropriate, whether there was something that could have been clearer, and keep the relationship warm for later. Over time, notice patterns in which proposals succeed, and refine your template.
After acceptance
A signed or confirmed proposal should lead into the next stage: a written scope agreement, a first invoice or deposit request, and a kickoff message that sets out how you will work together, including communication and client expectations. A clear proposal makes each of these easier because the main decisions are already written down.
No format guarantees a win, and clients vary in what they value. But a proposal that is clear, specific and focused on the client’s problem gives you the best chance of being understood, and of starting the project on a firm footing.