Most work proposals fail before the client finishes reading the first page. Not because the freelancer isn’t qualified — but because the proposal leads with credentials instead of the client’s problem. Here’s how to structure a proposal that actually wins the work.
Writing a proposal for work sounds simple: explain what you’ll do, say what it costs, send it. But the difference between a proposal that closes and one that gets ghosted usually comes down to structure, specificity, and sequence. This guide covers all three.
Why most proposals don’t work
Before the structure, the diagnosis. Most weak proposals share the same problems:
- They open with a bio or credentials section. The client doesn’t care yet — they care about their problem.
- They describe services in general terms (“I provide marketing strategy and implementation”) rather than specific deliverables.
- They leave pricing vague or confusing, which makes clients stall.
- They end without a clear next step, so the proposal just sits in an inbox.
The fix is a structure that reverses the order most people use: start with the client, end with you.
The six-section proposal structure
Section 1: Problem statement (50–80 words)
Open with the client’s situation, in their own language. Show you understood what they told you. This section does three things: it proves you listened, it anchors the proposal in their reality, and it sets up your solution.
Example:
“Acme Co. is launching a SaaS product in Q3 and needs a product landing page that converts trial signups from paid traffic. Current site converts at 1.4%; the target is 3% or better. Timeline is 6 weeks. The main constraint is that the existing brand guidelines must be followed.”
Notice: no mention of you yet. This section is 100% about them.
Section 2: Proposed solution and deliverables (100–150 words)
Now introduce your solution, framed around their outcome. List deliverables specifically — named outputs, not service categories.
Example deliverables list:
- Landing page copy (approximately 1,400 words), final version in Google Doc + launch-ready format
- Two headline/subheadline variants for A/B testing
- Mobile-first layout brief for your design team
- Two rounds of revisions based on your feedback
- 30-day post-launch review memo
Specific deliverables remove ambiguity. When clients can see exactly what they’re buying, they sign faster.
The deliverables section is where most proposals lose. Vague language like “marketing support” or “strategic consulting” creates uncertainty, and uncertainty kills decisions. Name every output. If you’re unsure what to list, think about what you’d hand over on the final day of the project.
Section 3: Timeline
Show the client when things happen. A simple milestone table works better than paragraphs.
Example:
| Milestone | Timeframe |
|---|---|
| Kickoff call and brief review | Week 1 |
| First draft delivered | Week 2 |
| Client feedback due | Week 3 |
| Revised draft delivered | Week 4 |
| Final copy + layout brief | Week 5 |
| Launch | Week 6 |
Keep dates realistic. Clients remember timelines, and missing them damages trust for future work.
Section 4: Pricing and payment terms
State the number clearly. Don’t hide it in paragraph text. Include payment terms on the same line.
Example:
Total: $7,500 Terms: 50% on signing ($3,750), 50% on final delivery ($3,750) Payment via bank transfer or card. Invoice sent on signing.
If you offer tiered options, use a simple table with three columns. But for most projects, a single clear price closes faster than a menu.
Common pricing mistakes: leaving out payment terms (creates confusion), offering too many options (creates paralysis), burying the price in a paragraph (makes it seem like you’re hiding something).
Section 5: Why you (40–80 words)
One paragraph. One specific proof point. Not a list of credentials.
Example:
“I’ve written landing pages for 12 SaaS companies at seed to Series B stage. The most recent, [Client Name], went from 1.8% to 3.1% trial conversion in 60 days post-launch. Product SaaS conversion pages at your stage of growth are specifically what I work on.”
One relevant example beats a full credential list every time. The client wants confidence, not a résumé.
Section 6: Call to action
End with a specific next step. Not “let me know if you have questions.” Something actionable.
Example:
“If this proposal works for you, sign below and I’ll send an invoice and kickoff call link within 24 hours. If you’d like to adjust scope or timeline before signing, reply to this email and we’ll sort it quickly.”
A clear CTA reduces the time between “this looks good” and “yes.” Every day of ambiguity is a day the client might find someone else.
What makes proposals win
Beyond structure, the proposals that consistently win share a few traits:
They’re sent fast. Speed of response is a signal of competence. Sending a proposal within 24 hours of a discovery call keeps momentum. Waiting 5 days kills it.
They use the client’s language. Proposals that echo the exact words the client used in discovery feel personal. Generic language feels templated, even if it isn’t.
They address the obvious concern. Every project has a risk the client is silently worried about. Naming and addressing it in your proposal removes the objection before it’s raised.
They’re easy to say yes to. One clear price. One clear next step. No ambiguity. The client shouldn’t need to ask a single clarifying question to move forward.
What makes proposals lose
Leading with credentials. The client opens the proposal hoping to see their problem understood. If the first thing they read is your bio, they mentally check out.
Vague scope. “Website design and development” could mean anything. Specific deliverables close; vague services stall.
Unclear pricing. If the client has to email to ask what the total is, you’ve lost time and possibly the deal.
No deadline. Proposals without expiry dates sit forever. Add: “This proposal is valid for 14 days from the date above.” It creates urgency without pressure.
No next step. The proposal ends and the client doesn’t know what to do. They wait for you to follow up. Sometimes you do; sometimes the deal dies quietly.
Template structure summary
Here’s the bones of the structure you can customize for any project:
[Your name / logo] | [Client name] | [Date] | Proposal #[number]
---
SECTION 1: THE SITUATION (50–80 words)
[Restate their problem, goals, timeline, constraints]
SECTION 2: WHAT I'LL DELIVER
- [Deliverable 1]
- [Deliverable 2]
- [Deliverable 3]
- [Deliverable 4]
[Note: X rounds of revisions included]
SECTION 3: TIMELINE
[Milestone table]
SECTION 4: INVESTMENT
Total: $[amount]
Terms: [payment structure]
SECTION 5: WHY ME (40–80 words)
[One relevant proof point]
SECTION 6: NEXT STEPS
[Specific action for the client to take]
[Signature line]Fill each section with the client’s specifics. Every proposal should feel written for that client, not assembled from parts.
Using proposal software vs. Word/PDF
A Word doc or Google Doc converted to PDF works fine for most proposals. The limitation: you don’t know if the client opened it.
Proposal software adds open-tracking, e-signature, and sometimes view-time analytics per section. For high-value proposals ($10K+), knowing the client opened your proposal but hasn’t responded is useful data — it tells you to follow up, not wait.
Tools like Waco handle the full workflow: send, track opens, collect signatures, and convert to invoice once signed. For freelancers sending more than a few proposals a month, the time savings add up quickly.
Related reading
- How to write a proposal for a new client — first-engagement strategies
- Simple proposal template for a new client — ready to customize
- What to do after sending a proposal — the follow-up plan
Start with section 1
The fastest way to improve your next proposal: write the problem statement before anything else. Force yourself to describe the client’s situation — their goals, their constraints, their timeline — in 60 words or less, without mentioning yourself.
If you can do that, the rest of the proposal flows naturally. And you’ll immediately notice how different it feels to receive a proposal that opens with your own problem versus one that opens with someone’s credentials.
That difference is what wins the work.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
