Freelancers often use the same proposal format for every opportunity. That’s a mistake. The right proposal type for the wrong situation wastes time and kills deals. Understanding when to deploy each type is the foundation of proposal strategy.
The 4 Types at a Glance
| Type | Who initiated it | Length | Converts at |
|---|---|---|---|
| Solicited informal | Client asked you | 1–2 pages | 30–50% |
| Solicited formal | Client sent an RFP | 5–15 pages | 40–60% |
| Unsolicited informal | You reached out | 1 page max | 2–5% |
| Unsolicited formal | You reached out | 5–15 pages | under 1% |
Solicited proposals convert 10 to 30 times better than unsolicited ones. The gap is almost entirely about the client’s mindset when they open it, not the quality of what’s inside.
Type 1: Solicited Informal Proposals
Use this when: A client reached out, you’ve talked or exchanged emails, and they know what they want.
A client reaches out asking for a bid. You’ve talked on the phone or exchanged emails. They know what they want. You respond with a short proposal: scope, timeline, price, and next steps. One to two pages.
This is the fastest proposal type. A good solicited informal proposal takes 30 minutes to write. It converts well because the client already wants to hire you. They’re just checking that price and timeline align.
Use this for straightforward projects with clear scope. A web redesign. A copywriting project. A design refresh. When the client has already qualified you, keep the proposal simple.
Structure: Lead paragraph restating their goal. Scope section outlining deliverables. Timeline with key milestones. Price with payment terms. Closing paragraph with next steps.
The danger with informal proposals is ambiguity. If you’re vague on deliverables, scope creep happens. Be specific about what’s included and what’s not. “I will deliver three rounds of revision” beats “revisions as needed.”
Type 2: Solicited Formal Proposals
Use this when: The client issued an RFP, formal request, or the project is large enough that a short proposal would look underprepared.
The client issued an RFP or formal request. It’s a larger project worth significant money. They want detailed documentation: your approach, team bios, case studies, timeline, costs, and terms.
Formal proposals are 5-15 pages depending on complexity. They take one to three hours to write. They’re necessary for enterprise clients, government contracts, and projects over 10,000.
Structure: Executive summary. Problem statement. Your proposed solution. Methodology and approach. Timeline and milestones. Team bios. Case studies. Pricing breakdown. Terms and conditions.
The formal proposal proves you’ve done your homework. You’ve understood their problem deeply. You’ve designed a custom solution. You’re offering a strategy, not a template.
For competitive bids where multiple vendors respond, the formal proposal separates serious contenders from casual ones. Clients often don’t read all formal proposals, but they notice when one is missing.
Type 3: Unsolicited Informal Proposals
Use this when: You spotted a specific problem you can solve, and the pitch is too targeted to ignore.
You reach out to a prospect with an idea. No request. Just a cold pitch followed by a short proposal showing how you could help them.
Unsolicited informal proposals rarely work because the prospect didn’t ask. They’re screening your pitch in their mind before reading your proposal. Use this only if you have a very specific idea that solves a clear problem they’re facing.
Example: You notice a SaaS company has a confusing landing page. You send a short email with three specific improvements. You include a one-page proposal showing the changes. That’s unsolicited informal.
The key: make it specific enough that they see value immediately. Generic unsolicited proposals are ignored. Specific ones get responses.
Type 4: Unsolicited Formal Proposals
Use this when: Almost never — only when a warm referral has specifically told the prospect to expect your proposal.
You spend hours building a detailed proposal for a company that didn’t ask. This rarely converts. It feels like work they didn’t request. And it signals you’re desperate.
The exception: you’re pitching a major partnership or significant project that required research and planning. You show them your thinking in detail because the opportunity is big.
Even then, unsolicited formal proposals usually fail. They sit in inboxes. They get forwarded to the wrong person. They lack urgency because nobody asked.
Use unsolicited formal proposals only when you’re confident they’ll read it. For example, you’ve been referred by a trusted contact who told them to expect your proposal, or you’re responding to a specific pain point they mentioned publicly.
Which Type Converts Best
Solicited formal proposals convert 40-60% of the time. The client already wants to hire someone. Your proposal just needs to confirm you’re qualified.
Solicited informal proposals convert 30-50% for smaller projects. Speed helps. Clients appreciate the quick response.
Unsolicited informal proposals convert 2-5%. Most are ignored. The ones that convert usually came from strong referrals or addressed a specific pain point perfectly.
Unsolicited formal proposals convert less than 1%. Avoid them unless you have a specific reason to believe the prospect is interested.
Common Mistakes With Each Type
Mistake 1: Using informal when formal is needed. A 10,000+ enterprise project expects formal documentation. A casual one-pager looks unprepared.
Mistake 2: Using formal when informal will do. Overcomplicating simple projects wastes your time and the client’s patience.
Mistake 3: Treating unsolicited proposals as equally likely to convert. They’re not. Focus your effort on solicited proposals where conversion is higher.
Mistake 4: Not matching proposal length to project scope. A small project shouldn’t get a ten-page proposal. A complex one shouldn’t get a single page.
How to Write Each Type Efficiently
For informal proposals, build a template. Change names, details, and price. You should get it down to 20 minutes for simple projects.
For formal proposals, maintain a component library. Methodology sections, case study templates, team bios, and terms that you mix and match. This reduces formal proposal time from three hours to 60-90 minutes.
For unsolicited, keep it extremely specific. Show you understand their exact situation. One page is fine if it’s targeted.
Avoid building proposals from scratch every time. The format changes, but your core content stays similar. Build once, reuse many times.
Solicited proposals convert 30-60% of the time. Unsolicited proposals convert under 5%. Match proposal type to situation, not vice versa.
Tracking Proposal Performance by Type
Track which proposal types yield the best conversion rates for your business. Track solicited vs unsolicited. Formal vs informal. By project type or client industry. Over time, you’ll see clear patterns about what works for your business model.
Once you have data, optimize accordingly. If unsolicited proposals never convert, stop writing them. If formal proposals convert better for your niche, write more of them. Let your conversion data guide your effort allocation.
Related: Proposal Win Rate Data: What the Numbers Actually Show
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
