Try SpecBot free — send focused proposals clients accept in one click.
“How long should my proposal be?” is one of the most common questions new freelancers ask. The answer isn’t a number — it’s a principle: a proposal should be exactly as long as it needs to be to communicate scope, rationale, and next steps clearly. No longer.
Here’s how to apply that principle in practice.
The right length by project type
Simple, clearly scoped projects: 1-2 pages
A returning client who wants a blog article. A small business that needs a five-page brochure site on a platform you know well. A social media content package with a defined deliverable set.
For these projects, a long proposal adds no value — it creates friction. A one or two-page document with scope, pricing, timeline, and next steps is professional and appropriate.
A one-page proposal can include:
- A brief executive summary (1 paragraph)
- Scope and deliverables (bullet list)
- Timeline
- Investment (line items + total)
- Next step
That’s enough. Adding more to this project doesn’t make the proposal more impressive.
Standard freelance projects: 2-4 pages
The most common case: a web design project, an SEO engagement, a brand identity, a content strategy. You’ve had a discovery call. The scope requires explanation. The price needs justification.
For these projects, 2-4 pages (or equivalent) is the standard range. A typical structure:
- Executive summary (1/2 - 1 page)
- Scope of work with deliverables (1 page)
- Timeline (1/2 page)
- Investment (1/2 page)
- Next steps (1 paragraph)
This gives the client everything they need to make a decision without forcing them to read a document the length of a report.
Complex, multi-phase, or high-value projects: 4-8 pages
A multi-phase digital transformation. A branding project that includes strategy, identity, and rollout. An ongoing retainer with multiple workstreams.
For these projects, more depth is appropriate because:
- The scope is genuinely complex and needs explanation
- The investment is large enough that the client wants thoroughness
- There are multiple stakeholders who need different pieces of information
Even here, 8 pages is usually the ceiling. Proposals above 10 pages are almost always padded.
Enterprise and large agency proposals: 8-20+ pages
Enterprise and large agency RFP responses occupy a different category — they often require detailed methodology, team bios, references, case studies, and pricing matrices. These aren’t typical freelance proposals; they’re formal bid documents. The length expectations and format requirements are usually specified by the client.
If you’re operating in this space, follow the client’s stated requirements.
What to include vs. what to cut
Always include:
- Executive summary (tailored to this specific client)
- Scope with specific deliverables, quantities, and formats
- Scope exclusions
- Timeline with phases and milestones
- Pricing (line-item breakdown)
- Payment terms
- Next steps (one clear action)
Usually include:
- Brief relevant experience or credential (1-3 sentences or a short bullet list)
- Process description (how you work together — valuable for complex projects, optional for simple ones)
- Assumptions (conditions that could affect scope or timeline)
Usually skip:
- Extended “about us” sections (2-3 sentences is enough)
- Generic capability statements (“we have extensive experience with…”)
- Process details the client doesn’t need to know
- Legal boilerplate (this belongs in the contract, not the proposal)
- Case studies that aren’t directly relevant to this project
- A mission statement
Always cut:
- Filler language (“I am pleased to present…”)
- Redundant sections that repeat scope already stated
- Generic industry statistics that don’t connect to the client’s situation
- Padded paragraphs that say nothing specific
The padding test
Before sending any proposal, do a padding audit. Read each section and ask: “If I remove this, does the client lose any information they need to make a decision?”
If the answer is no — cut it. Every section that doesn’t earn its place makes the client work harder to find the information that matters.
The best proposals feel efficient. The client reads through and gets exactly what they need to decide without wading through filler. That efficiency itself signals competence.
Length and format
Proposal length also depends on format. A word-processed document uses space differently than a proposal tool with section layout. A slide deck proposal reads differently than a narrative document.
Some general principles across formats:
- Word/Google Docs proposals: 2-4 pages for standard projects
- Proposal tool (Bonsai, HoneyBook, SpecBot): Typically shorter because the visual formatting carries structure that requires words in plain text
- Slide decks: 10-20 slides for standard projects, but each slide is usually quick to read
- Email proposals: 400-800 words for simple projects; use a document attachment for anything complex
The “would I read this?” test
The final test for any proposal is simple: would you read the whole thing if you were the client?
Read your proposal as if you’re a busy person who received it unexpectedly. Does it hold your attention? Does it answer questions without making you search? Does it get to the point?
If you lose interest halfway through, the proposal is too long. If you reach the end and still have fundamental questions, it’s too short or too vague.
The right length is whatever it takes to pass that test.
Start free on SpecBot — SpecBot turns your offers into proposals clients accept in one click, with a signed PDF for both sides. Free is 3 proposals a month with every feature; Pro is unlimited proposals at €12/month, or €9/month billed yearly. Write them in the web app, by voice, or inside ChatGPT and Claude.