A strong freelance proposal does more than describe your skills: it helps a prospective client understand the work, the expected result, the cost, and the next step. This guide explains how to write a freelance proposal for fixed-price projects, hourly engagements, retainers, and competitive marketplace bids, with practical templates and a simple way to estimate effort, pricing, and proposal quality before you send.
Overview
A freelance proposal is a short decision document. It should connect the client's stated problem to a realistic plan for solving it. The best proposals are not necessarily the longest or most elaborate. They are specific enough to reduce uncertainty without burying the client in background information.
Most effective freelance proposals answer five questions:
- What does the client need?
- How will you approach the work?
- What exactly will be delivered?
- How long will the work take and what will it cost?
- What should happen next?
Before writing, separate the proposal from a general introduction or portfolio page. A portfolio proves that you can produce a certain type of work. A proposal explains how you would apply that experience to this particular project.
If you are still defining your service or looking for your first client, the guide on how to start freelancing and find your first client can help you establish the wider process. For proposal writing itself, use the structure below as a repeatable system rather than copying a script word for word.
How to estimate the work before writing
A proposal becomes more credible when its price and timeline are based on visible assumptions. Start by estimating the work in stages instead of guessing one large number.
- List the deliverables. Write down every item the client will receive, such as a landing page, research summary, edited video, design concept, or set of social media assets.
- Break each deliverable into tasks. Include discovery, preparation, production, revisions, communication, quality checks, and handover.
- Estimate active work time. Consider how long each task would take if the required information were available and decisions were made on schedule.
- Add project management time. Messages, meetings, file organisation, and status updates are part of the engagement even when they are not visible in the final deliverable.
- Add a clearly explained contingency. A modest buffer can account for uncertainty such as incomplete inputs or an unclear review process. Do not use a vague buffer to hide an undefined scope.
A simple estimate is:
Estimated hours = production hours + communication hours + revision hours + handover hours + contingency hours
For an hourly engagement, multiply the estimated hours by your chosen hourly rate. For a fixed-price project, use the same estimate as an internal check, then present one project fee or a small number of milestones. If you need help setting the underlying rate, compare your assumptions with the freelance rates calculator guide or the freelance rate calculator guide.
Do not promise a precise outcome when the brief is incomplete. Instead, state what your estimate assumes. For example: “This estimate assumes the client provides final copy, brand assets, and one consolidated round of feedback.” That sentence protects both sides and gives the client a useful opportunity to correct the brief.
Inputs and assumptions to include
A proposal should make its important inputs visible. This is especially useful when a client is comparing several freelance bids or when the project may change after work begins.
Scope
Describe what is included in plain language. A web design proposal might include a homepage concept, two revision rounds, and delivery of editable source files. It might exclude development, copywriting, and additional page layouts. Stating exclusions is not confrontational; it prevents different interpretations of the same project.
Timeline
Give a start condition and a working schedule. “Delivery in seven days” is less useful than “Work begins after the brief and required assets are received; the first draft is delivered within three working days, followed by revisions and final handover.” A timeline should also identify what could delay delivery, such as late feedback or missing access.
Price and payment structure
For fixed-price work, connect the fee to milestones or deliverables. For hourly work, state the rate, estimated hours, billing interval, and how additional work will be approved. For a retainer, define the recurring capacity, response expectations, included services, and treatment of unused time. Avoid presenting a low price without explaining the reduced scope or assumptions behind it.
Proof
Choose one or two relevant examples rather than sending a long list of unrelated work. Explain the connection: “This example is relevant because it involved simplifying a complex service for a non-specialist audience.” If you are early in your career, use a carefully labelled sample project, internship project, volunteer assignment, or previous role where it genuinely demonstrates the required skill. The guide to listing freelance work on your resume and LinkedIn can help you present that experience clearly.
Next step
End with one easy action. Ask the client to confirm the preferred option, answer two specific questions, or schedule a short project call. A proposal that ends with a clear decision is easier to act on than one that simply says, “Let me know what you think.”
Worked examples and adaptable templates
Fixed-price project proposal
Subject: Proposal for [project]
Hi [client name],
Based on your brief, you need [specific outcome]. I would approach this by [short method or sequence], with the goal of delivering [measurable or observable result].
The project includes:
- [Deliverable one]
- [Deliverable two]
- [Number or description of revision rounds]
- [Final files, documentation, or handover]
The estimated timeline is [timeline], assuming [key assumptions]. The fixed project fee is [fee], divided into [milestones or payment stages]. Work outside this scope would be discussed and approved separately before it begins.
A relevant example is [brief example and why it matters]. If this approach fits, the next step is to confirm the scope and share [required materials].
Best,
[name]
Hourly engagement proposal
For hourly work, make the uncertainty visible without making the proposal sound open-ended:
“I can support [type of work] at [hourly rate]. Based on the current brief, I estimate [range] hours for the first phase, including [tasks]. I would provide a progress update after [milestone or time period]. Any work likely to exceed the estimate would be discussed before additional time is used. The first step would be [specific task].”
Retainer proposal
A retainer proposal should describe capacity rather than promise unlimited availability:
“Each month, I would reserve [number of hours or defined capacity] for [services]. This includes [core activities], a regular status update, and [defined response or meeting arrangement]. Requests would be prioritised against the agreed monthly capacity. Work beyond that capacity would require separate approval. The arrangement can begin with a [trial or initial] period focused on [priority outcome].”
Competitive marketplace bid
An Upwork proposal or other marketplace bid should be concise and personalised. Open with one observation from the listing, then state the relevant result you can help produce. Include a short plan, one relevant proof point, a realistic estimate, and one useful question. Do not repeat the client's entire job description or use a generic introduction that could apply to every project.
For example: “Your brief highlights inconsistent product descriptions across the catalogue. I would first create a short style guide, then revise a representative sample before applying the agreed approach to the remaining entries. I have handled comparable consistency and editing work, and I would begin by reviewing five sample products. Which product category should be treated as the priority?”
When to recalculate or revise your proposal
Revisit your estimate whenever an input changes. That includes a new deliverable, additional decision-maker, extra revision round, faster deadline, missing source material, new software requirement, or change from a one-time project to ongoing support.
You should also review your proposal process after several bids, whether they succeed or not. Track the project type, estimated hours, quoted fee, response, questions raised by the client, and whether the eventual work matched the estimate. This creates a private record of which assumptions are reliable and which need adjustment.
If your proposals are frequently ignored, first check relevance and clarity rather than immediately lowering your price. If clients regularly ask what is included, improve the scope section. If projects overrun, record the missing tasks and add them to future estimates. If work is profitable but difficult to manage, refine the communication and revision terms.
Use a simple proposal checklist before sending:
- Have I addressed this client's actual goal?
- Are the deliverables and exclusions clear?
- Does the timeline identify assumptions and dependencies?
- Is the price connected to scope or capacity?
- Have I included relevant proof?
- Is there one clear next step?
- Have I checked names, links, attachments, and figures?
Finally, record each application and follow-up in a simple workflow. The remote job application tracker template can also be adapted for freelance bids by adding fields for proposal type, quoted amount, follow-up date, and outcome. A consistent process makes it easier to improve your proposals without relying on memory.
