Keep a freelance proposal to one to three pages that answer five questions: what is the problem, what will you do, what will the client get, how long will it take, and what does it cost. Everything else is optional. A short, specific proposal is easier to read, easier to approve, and easier to forward to whoever signs off.
This article covers the structure, how to word the parts that matter most, and what to cut. It assumes you have already talked with the client, since a proposal written before any conversation is a guess. For the full list of terms to check before you send, use what a freelance proposal should include.
Why proposals get overcomplicated
Freelancers over-build proposals for understandable reasons: they want to look professional, they fear leaving something out, and a short document can feel lightweight. The result is often a ten-page file with company history, generic service lists, and dense legal language the client skims.
Clients mostly want to know whether you understand their problem and what it will cost. Extra pages dilute that. A proposal is a decision document, and its job is to make a yes easy. Match the detail to the project: a small task does not need the document a large engagement does, but both need clarity about what is included.
A simple template
This structure fits on one to three pages:
- Title and date. Project, client, your name, date.
- Summary. Two or three sentences on the goal and your approach.
- Scope and deliverables. A bulleted list of exactly what the client receives.
- Timeline. Start date, key milestones, delivery date.
- Price and payment. Total fee, deposit, due dates.
- Terms. Revisions, changes, ownership, expiry date.
- Next step. One clear action, such as “Reply to confirm and I will send the agreement and first invoice.”
Write the summary the way the client would read it
The summary is the most-read part, so make it about them and borrow their words from the conversation.
Weak: “I am a creative professional with years of experience delivering high-quality solutions.”
Better: “You want more appointment requests from your website before spring. I will rewrite and restructure your four main service pages so visitors understand what you offer and how to book.”
The second version names the goal, the work, and the outcome sought, without promising a result. If you have call notes, turning a discovery call into a proposal shows how to convert them into this section.
Be specific about deliverables
Vague deliverables cause arguments later. Replace broad terms with items the client could check off.
| Too vague | Clear |
|---|---|
| “Website content” | “Copy for four pages: Home, Services, About, Contact, up to 500 words each” |
| “Design work” | “One logo with three initial concepts and two revision rounds, in standard file formats” |
| “Social media help” | “12 scheduled posts per month and one monthly summary” |
| “Support” | “Up to 3 hours of email support in the 30 days after delivery” |
Where useful, add a one-line “Not included” note, such as “Photography, translation, and hosting are not included.” The same discipline applies throughout the project; see setting a project scope that does not drift.
For the timeline, a short list beats a chart: kickoff, first draft, feedback due, final delivery. Add what you need and by when: “Dates assume I receive logins and photos by [date]. Delays in materials or feedback move later dates by the same amount.”
Present the price clearly
Show the total, and break it down only if that helps. One clear number is often easier to approve than an invoice-style list. If you break it down, use meaningful chunks such as phases, not every hour. Typical payment terms are a deposit to start and the balance on delivery, with milestone payments on larger projects, but terms vary by field and client.
Two or three options at different prices can help the client choose a level, as in this skeleton:
| Option | What is included | Fee |
|---|---|---|
| Basic | Core deliverables, one revision round | $X |
| Standard | Core deliverables, two rounds, one extra item | $Y |
Base the figures on a real estimate; how to price freelance work without undercharging shows how.
Keep terms short, and legal detail separate
Terms protect both sides, but long legal text can put clients off and may not hold up anyway. Put short plain-language terms in the proposal (revisions, how extra work is requested and priced, payment schedule, ownership, expiry) and detailed legal language in a separate agreement. Contract law and what is enforceable vary by state and country, so treat your terms as a basic framework and ask a qualified professional, such as a lawyer, to review your agreement, especially for larger projects, ownership of work, or anything unusual.
What to cut
If a proposal is too long, remove these first:
- Long biographies. One short paragraph and two or three relevant samples are enough.
- Generic service lists. List only what applies to this project.
- Process diagrams that do not change the decision.
- Buzzwords. Replace “robust, scalable solutions” with what you will actually do.
- Repeated points and excess legal text.
Ask of each paragraph whether the client would miss it if it were gone.
Make it easy to say yes
State the next step at the top and bottom, give a deadline that reflects your real availability, offer a short call to walk through it, and make acceptance simple, such as replying “approved” or signing a one-page agreement. A sample close: “If this looks right, reply and I will send the agreement and deposit invoice. I have an opening starting [date] and can hold it until [date].” After sending, follow up on a schedule; how to follow up without sounding desperate has message templates.
Common mistakes
Most come from rushing or reusing an old document unedited:
- Writing before understanding the problem. Talk first.
- Sending the same file to everyone. Customize the summary and deliverables.
- Burying the price at the end of a long document.
- Leaving out what you need from the client. Late materials are a frequent cause of delay.
- Promising outcomes you cannot control. State what you will deliver.
- No expiry date. Prices and availability change.
Read the draft once for content and once for names, dates, and totals.
Format and delivery
How you send it matters less than people think, but a few habits help. A PDF or a shared document keeps formatting stable and is easy to forward. Put the client’s name and the project title in the file name so it does not get lost among attachments. Check that it reads well on a phone, since many clients first open it there, and keep paragraphs short. If your tool lets the client accept with a click, that is fine, but a plain reply of “approved” works too as long as you then send the agreement.
Where this comes from
This article is based on commonly published guidance on freelance proposals, which generally describe an overview, scope of work, deliverables, timeline, and price, together with general plain-writing practice. No regulator sets a proposal format. Examples and figures are invented. Contract rules, prices, and market norms change, so check them with a qualified professional for your situation.
General information, not legal, tax, or financial advice.