How to Write Proposals That Win for Agencies
Most proposals are boring. They're comprehensive.
They cover everything. Clients skim them and feel tired.
Winning proposals solve a problem clients care about. They're written for how clients actually make decisions, not how you think projects should be described.
They lead with value. They're easy to approve.
The difference between a proposal that gets signed and one that sits in an inbox is how it's structured.
The Proposal Structure That Works
Open With Their Problem, Not Your Solution
Don't start with "Here's what we'll do."
Start with "Here's the problem you described and why it matters."
"You mentioned your current website doesn't convert visitors into leads effectively. You're getting 10,000 monthly visitors but only 50 leads.
That's a conversion rate of 0.5%, when industry standard is 2-3%. Fixing this is worth potentially $50,000+ per year in additional revenue."
You've named their pain. You've quantified why it matters. Now they're reading.
State Your Approach Clearly
What's your methodology? How is it different?
"We'll spend two weeks understanding your user behavior through research and testing. We'll identify the barriers preventing conversion.
Then we'll redesign the site and user flows to remove those barriers. Finally, we'll test the new design before launch to confirm it's improving conversion."
You're showing you have a process. You're showing it's thoughtful, not just building stuff.
Break Down What They're Getting
List specific deliverables, not vague outcomes.
Bad: "Website redesign and optimization."
Good: "Deliverables include:
- Competitive analysis report
- User interview synthesis
- Wireframes for homepage, services page, contact, and case studies
- High-fidelity mockups in Figma
- Responsive design assets for mobile
- Development-ready component library
- Launch documentation"
They know exactly what they're getting.
Specify Timeline With Milestones
"Timeline: 8 weeks
- Week 1-2: Research and planning
- Week 3-4: Design and stakeholder review
- Week 5-6: Revisions and finalization
- Week 7-8: Development handoff and deployment"
Specific dates if you have them: "Start date: January 15. Launch date: March 10."
State The Investment Clearly
"Investment: $24,500
This includes all deliverables listed above, three rounds of revisions, and unlimited stakeholder feedback during the project."
Be specific. Round numbers ($25,000) feel less researched than specific numbers ($24,500).
Add A Closing Section: Why Now
"Why This Matters Now: Every week you're converting at 0.5% is a week you're missing potential revenue. Competitors are investing in experience.
If you delay six months, you'll be further behind. Starting now means you capture spring lead generation season with an optimized site."
You're creating light urgency without being pushy.
The Psychology Of Proposal Language
Use "We'll" Not "I'll"
"We'll handle research, design, and testing." Sounds like a team. Sounds stable. Sounds professional.
Avoid Jargon Unless They Use It
If they said "user experience optimization," cool, use it. If they said "make it better," don't say "we'll improve the UI/UX metrics."
Be Specific About Problems
"You're losing customers because the checkout process is confusing" not "we'll improve checkout."
Specific problems are more credible.
Show That You Understand Their Business
"For a SaaS company, onboarding is critical. Every day a customer struggles to activate is a day they might churn. That's why we're prioritizing the first-time user experience."
You're showing you understand their industry, not just your service.
Use Numbers
"Most clients see 30-50% improvement in conversion rates after optimization" not "most clients see improvements."
Numbers make claims more believable.
The Sections That Actually Get Read
Executive Summary (Top of Proposal)
One paragraph. What are we solving? How? For how much? When?
"You're getting 10,000 monthly visitors but converting only 0.5% to leads. We'll redesign your website and user flows to improve conversion to 2%. The investment is $24,500.
Timeline is 8 weeks. Start date is January 15."
If they only skim one section, make it this one.
The Situation
Summarize what they told you. Quantify the problem. Show why it matters.
"You mentioned your current website feels dated and isn't converting visitors. You're right. Looking at your analytics, you're converting at 0.5%.
Your competitors are at 2%. That's costing you approximately $50,000 per year in lost potential revenue."
The Approach
How will you solve it? What's different about your method?
"Most redesigns focus on looks. Ours focus on behavior. We'll research why visitors leave.
We'll identify the barriers. We'll design specifically to remove them. Only then will we focus on aesthetics."
The Deliverables
Detailed list. No surprises.
The Timeline
Specific dates and milestones.
The Investment
What it costs. What's included.
The Next Steps
"If you'd like to move forward, we'll need: [approval, signed agreement, deposit schedule]. We'll send you the agreement by [date]. Questions?"
You're guiding them to yes.
What NOT To Include
Don't Include:
- Your full case studies or portfolio (that's for a separate document)
- Your company history (they don't care)
- Detailed technical explanations they didn't ask for
- Multiple pricing options (give them one option, or clearly position option A as recommended)
- Overwritten flowery language
Keep it focused on them and what you're solving.
The Length That Works
One to three pages. That's it.
A proposal longer than three pages doesn't get read. You're overwhelming them. If they need more detail, they'll ask.
Design Of The Proposal Itself
Use A Simple Template
Clean layout. Readable fonts.
Not over-designed. They're reading for information, not admiring graphic design.
Make It Skimmable
Headers. Bullet points. White space. Someone should be able to scan it in 60 seconds and understand the gist.
Include Your Logo and Contact Info
They need to know who they're saying yes to. Include your phone number, email, and website.
Use A Professional Delivery Method
PDF is safest. Google Docs if you want them to ask questions inline.
Not a Word doc. Not a PowerPoint.
Before You Send
Spell Check
Typos kill credibility. Read it three times.
Have Someone Else Read It
Your co-founder, your partner, a trusted colleague. Do they understand what you're proposing? Does it feel credible?
Customize It For Their Business
Don't send a template. Every proposal should reference their specific situation. Their problem.
Their business. Their timeline.
Follow Up
Send the proposal. Wait 48 hours.
Call them: "Got a chance to review the proposal? Any questions?"
You're not pushy. You're just checking in.
FAQ
Q: Should I include references or testimonials in the proposal?
A brief one-liner testimonial is good: "A similar client saw 35% improvement in conversion within 90 days of launch." Don't fill it with testimonials though.
Q: How do I price when I'm not sure of the complexity?
Build in a discovery phase. "We'll start with a two-week research and scoping phase.
At the end of that, we'll provide a detailed estimate for the full build. Discovery investment is $5,000, which is credited toward the full project if you move forward."
Q: Should I send a proposal if they didn't ask for one?
Only if they asked about pricing or next steps. If they're just exploring, don't push a proposal yet. Have a conversation first.
Q: How do I handle clients who want to negotiate the price after seeing the proposal?
"The price is based on the scope. If budget is tight, we can reduce scope or extend timeline. Which would you prefer?"
You're not budging on price without reducing scope.
Q: How long should I wait to follow up on a proposal?
48 hours is good. A week is too long. They've forgotten about it by then.