One page. For most freelance projects, a single page covering the problem, plan, deliverables, price, and next step is the right length — and two pages is the ceiling. Length does not signal effort to a client; it signals reading time, and reading time delays decisions.
Why long proposals feel safer but close worse
Freelancers pad proposals for an understandable reason: more pages feel like more professionalism, more justification for the price, more proof of seriousness. But the person reading it is busy, skimming on a phone, and looking for three things — what do I get, what does it cost, what do I do next. Every extra page is another place for those answers to hide.
A long proposal also invites a dangerous response: "Let me read this properly over the weekend." Proposals that get parked get ghosted. A one-pager gets read in the same sitting it arrives, while the client is still warm from your call.
What actually belongs on the page
The word budget for a strong proposal is roughly 300 to 500 words, split like this:
- Problem statement: 2–3 sentences restating the client's goal in their words.
- Approach: 3–5 short steps with a rough timeline.
- Deliverables: a bullet list of concrete, countable items, plus one line on what is excluded.
- Price: one bold number and what it covers.
- Next step: one sentence, one action, one link.
Notice what is missing: your life story, a services catalog, a methodology essay, legal boilerplate. None of those move a client from interested to paid.
The exceptions that earn a second page
Some projects genuinely need more room. A six-month retainer with phased milestones, a project involving multiple stakeholders who each need their section, or an RFP with mandated headings can justify two pages. Even then, the rule holds in miniature: the first page should still work as a standalone summary, because the decision-maker may never reach page two.
What never earns a second page: repeating yourself, hedging the scope in three different ways, or listing services the client did not ask about.
What to cut first when trimming
If your current template runs four pages, cut in this order:
- The about section. The client already decided you are credible — that is why they asked for a proposal. One line of relevant proof inside your approach section is plenty.
- Generic testimonials. A single specific result ("increased signups 40% for a similar SaaS") beats three vague quotes.
- Process theory. Explain what you will do, not your philosophy of doing it.
- Multiple pricing tiers. One price, maybe one add-on. Tier matrices are for software pages, not proposals.
Short is a speed advantage too
A one-page structure is not just easier to read — it is dramatically faster to write, which means you can send it the same day as the call, while the client's enthusiasm is at its peak. Speed and brevity compound: the short proposal arrives first and gets read first. Tendrly leans into both — you answer five questions, it drafts a tight branded one-pager with a one-click Stripe payment link, so approving the proposal and paying the deposit happen in the same moment.
FAQ
Will a short proposal make me look junior?
No — the opposite. Senior freelancers write short proposals because they know exactly what the project needs. Padding reads as uncertainty, not seniority.
What about big corporate clients who expect detail?
If procurement mandates a format, follow it. Otherwise, even enterprise buyers prefer a crisp summary — they just may also need a scope-of-work attachment for their files, which can live as a separate document.
How many words is a one-page proposal?
Roughly 300 to 500 words with clear headings and a bullet list of deliverables. If you are past 700 words, something on the page is not earning its place.