The word “proposal” can make freelancers anxious — it sounds like it should be long, formal, and exhaustively researched. It doesn’t need to be any of those things. A simple, clear proposal that addresses the client’s actual situation is more effective than a lengthy document that tries to cover everything.
The structure of a simple proposal
A simple proposal has five parts. You don’t need more than these:
1. The situation — One short paragraph demonstrating that you understand what the client is dealing with. Reference what they told you in your discovery conversation. This part isn’t about you — it’s about showing you listened.
2. Your approach — How you’ll solve the problem. Keep this concrete. “I’ll start with a brand audit, then develop three logo concepts based on your target audience and positioning” is better than “I’ll create brand assets.”
3. Deliverables — What the client will receive. Be specific. This is essentially the scope of work — list the outputs, formats, and revision rounds included.
4. Timeline — Estimated start date and delivery milestones. Even a rough timeline shows you’ve thought about the project, not just the price.
5. Investment — The price. Use “investment” or “project fee” if you prefer, but just “price” or “cost” is also fine. Present it clearly. If it’s itemized, show the breakdown. If it’s a single total, make sure the deliverables section has enough detail that the client understands what they’re paying for.
That’s it. Five sections, one to two pages.
Lead with the client, not yourself
A common proposal mistake is spending too much space on your background, your process, your awards, and your previous clients before you’ve shown any understanding of the client’s situation.
Clients don’t award work to the most impressive CV. They award work to whoever they’re most confident will solve their problem. Confidence comes from feeling understood, not from reading a credential list.
Keep any background information to two or three sentences, placed after the approach section, not before it. The proposal should start with the client’s situation, not your biography.
The most persuasive thing in any proposal is evidence that you understood the client before you started writing. Lead with their situation, not your credentials.
Keep the language simple
Proposals lose clients when they’re full of jargon, buzzwords, or overly formal language that doesn’t reflect how people actually talk. Write the way you’d explain it on a call.
Avoid phrases like “leverage synergies,” “holistic approach,” “best-in-class deliverables,” or “robust framework.” These mean nothing and signal that the proposal is a template, not a tailored document.
Use the client’s words where possible. If they described their problem as “our checkout process is confusing,” use that language. It shows you were paying attention.
Include a clear next step
Every proposal should end with a specific, friction-free way to say yes. This might be:
- “To proceed, please sign the proposal below” (if there’s a signature section)
- “Reply to this email to confirm you’d like to move forward”
- “Approve this proposal with the button below” (if sent digitally through a tool like Waco)
Vague endings slow things down. “Let me know your thoughts” puts the work back on the client. “Click to approve” removes all friction.
When a simple proposal isn’t enough
Some projects genuinely require more detail — competitive agency pitches, large multi-phase projects, government or enterprise contracts. In those cases, expand the proposal to include case studies, team bios, or a methodology section.
But for the vast majority of freelance work, a clean, specific two-page proposal beats a ten-page document with filler every time.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
