There’s an old freelance instinct that says a longer proposal looks more professional. It doesn’t. It looks like you’re nervous and trying to compensate by filling pages. Clients can feel the difference between a confident 3-page proposal and a padded 12-page one in about 30 seconds.
There’s no single right answer to how long a proposal should be, but there’s a useful range. Here’s how to think about it and what tends to work at each project size.
The short answer by project size
Here’s the rough length that closes well at different price points, based on patterns most agencies and senior freelancers settle into:
| Project price | Proposal length | Pages |
|---|---|---|
| Under $2,000 | 300-500 words | 1 page |
| $2,000-$8,000 | 600-1,000 words | 2-3 pages |
| $8,000-$25,000 | 1,000-1,800 words | 3-5 pages |
| $25,000+ | 1,800-3,500 words | 5-10 pages |
| Enterprise/RFP | Whatever they ask for | 10-30 pages |
Notice that the relationship between price and length flattens. A $50K project doesn’t need a proposal 25 times longer than a $2K project. The complexity of the work doesn’t scale linearly with the price.
Why most proposals are too long
If you’ve written more than 20 proposals, you probably have a template that’s grown over time. Every awkward client conversation added a section. Every lost deal made you add a case study or a guarantee paragraph. By proposal 50, the template is bloated.
Common bloat:
- A long opening paragraph thanking them for the opportunity
- An “about me” or “about the studio” section that has nothing to do with their project
- Three case studies, two of which aren’t relevant
- A methodology section explaining how you work in general
- A FAQ section that anticipates objections they didn’t have
- Terms and conditions copied from a template that doesn’t apply
Cut all of that. Every line in the proposal should either describe what they’re buying or help them say yes faster. If it doesn’t do one of those two things, it’s making the proposal worse.
The five sections that always earn their space
These are the only sections that consistently help close deals. Every other section is optional and most are subtractive.
1. The recap. One paragraph in your words showing you understood what they said on the call. Not the brief they sent. What you heard.
“Based on our call Tuesday, you need a new homepage and three product pages that explain the API to non-technical buyers. The current site converts at under 1%, and the goal is to double that by end of Q3 without changing the brand visual system.”
That single paragraph does more to build trust than three pages of methodology.
2. The scope. Specific deliverables. What you’re producing, in what format, with what acceptance criteria. Vagueness here costs you money later when scope drift starts.
3. The timeline. Milestones with dates or week numbers. Not “approximately 6 weeks.” Specific weeks with specific deliverables.
4. The price and terms. Total price, payment schedule, what’s included, what’s not. If you have a deposit and milestone structure, lay it out.
5. The next step. A single clear action. “Reply ‘approved’ to this email and I’ll send the contract.” Or “Sign here to lock in the start date.” One step.
That’s 600 to 900 words if you write tight. It closes better than your 12-page version. Try it on the next deal and see.
When the proposal should be longer
Some projects genuinely need more.
- Enterprise procurement. Their RFP says they want 12 sections including a security overview and a diversity statement. Write the 12 sections. This isn’t a real proposal, it’s a compliance exercise.
- Multi-phase, multi-deliverable. A 6-month engagement with 4 phases and 18 deliverables needs more space to lay out cleanly. Length follows complexity.
- High-stakes, technical work. When you’re charging $40K to migrate a database and the client needs to see you understand their stack before they sign, a longer technical section earns the price.
- Multiple stakeholders. When the proposal has to convince a champion, their boss, and a procurement team, you sometimes need separate sections for each audience.
For everything else, default to short.
When the proposal should be shorter
There’s a category of project where a long proposal actively hurts you. Quick-turnaround, repeat-client, or referral-based work.
If a past client emails saying “can you do another version of the campaign we did in Q1,” a 4-page proposal looks like you forgot they’re a friend. A 200-word email with scope, price, and timeline is the right answer. They’ll sign in an hour.
For referrals where the referrer has already pre-sold you, a 1-page proposal that gets to scope and price fast respects the relationship. A long deck makes you look like you didn’t trust the referral.
The opening paragraph problem
The single most common mistake in a freelance proposal is the opening paragraph. It almost always reads:
“Thank you so much for the opportunity to put this together. I really enjoyed our conversation last week and I’m excited about the possibility of working together on this exciting project…”
Skip it. The client knows you’re grateful. Open with the recap instead. The recap signals you listened, which is the actual emotional work the proposal needs to do in the first 10 seconds.
Perceived length matters more than actual length
Word count isn’t the whole story. A 1,200-word proposal with good headers, short paragraphs, a clean scope table, and white space reads faster than a 700-word wall of text.
Formatting that shortens perceived length:
- 2-3 line paragraphs, never longer
- A scope table instead of a bulleted list when there are more than 5 items
- A timeline table with week numbers
- Bold the deliverable names so a skimmer can find them
- Put price in its own section with breathing room around it
A well-formatted 1,000-word proposal feels like a 500-word one. Use that.
The test for whether your proposal is the right length
After you draft it, ask: if the client reads only the first page, do they have enough to either approve or ask one question?
If yes, length is fine.
If no, you either buried something important or you wrote too much. Both fixable.
The shift to make
Stop using proposal length as a stand-in for effort. The client doesn’t see your effort. They see how clearly you described what they’re buying and how fast they can decide.
Write the shortest proposal that covers the five sections. Send it. Watch your close rate. If it goes up (it usually does), shorten the next one too. Stop when you start losing deals because information was missing, not before.
Honest answer: as long as it needs to be, and not a paragraph longer.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
