How to Write Freelance Proposals That Win Work in 2026
You found a project that fits your skills, and now you must explain why the client should choose you. A good answer to how to write a freelance proposal is a short, clear document that shows you understand the problem, states exactly what you will deliver, and makes the next step easy. This guide covers both formats you will use most: the short bid you send on a freelance platform, and the longer proposal you send to a direct client. It also covers pricing, scope, follow up, and the mistakes that lose work.
What a proposal is, and what it is not
A proposal is a written offer to do a defined piece of work for an agreed price and by an agreed date. It is not a CV, and it is not a list of everything you can do. The client reads it to answer one question, which is whether you can solve their problem without creating extra work for them. A quote is shorter than a proposal, because it usually states only the price for work that is already defined. A contract comes after acceptance, and it records the legal terms both sides agree to follow. Keep these three documents separate in your mind, because each one has a different job. Your proposal should persuade, your quote should price, and your contract should protect. If you mix them up, the client gets a long document that does neither job well. If you are new to freelancing, read our guide on how to start freelancing before you send your first proposal, so your offer rests on a clear service and not on guesswork.
The short platform bid
On a platform, the client reads many bids, and most bids get only a quick scan. Your first two lines matter most, because the platform often shows only a preview before the client clicks to read more. Open with the client's problem in their own words, not with a greeting about yourself. Then name the result you will deliver in one sentence. Follow that with a short plan of two or three steps, one line of relevant proof, your price or price range, and one clear next step. Keep the whole bid to about 120 to 200 words. Longer bids look unfocused on a platform, and they bury the result the client cares about. End with one question that shows you read the brief, such as asking which format the final files should use. A question also invites a reply, which starts a conversation. If you need help finding suitable jobs to bid on, see how to find freelance clients.
The longer direct client proposal
A direct client proposal is a longer document, usually two to six pages, and it follows a clear order. Start with the situation as the client described it, in one short paragraph. Then state the outcome the project should achieve, so both sides agree on what success looks like. Next, list the deliverables, which are the finished items you will hand over. After that, list what is not included, so extra work has a price later. Then present the price, the schedule, what you need from the client, the terms, and the next step. This order works because it follows the client's thinking, from problem to result to cost to action.
Scope as counted deliverables
Vague scope is the most common cause of unhappy freelance projects. Words like website, content, or design mean different things to different people, so count your deliverables instead of naming them vaguely. A deliverable is a finished item you can count, such as four blog posts, one landing page, or ten product descriptions. Write each one as a noun with a number, and add the format and length where it matters. For example, write five blog posts of about 800 words each, delivered as editable documents, rather than writing blog content. Also state how many revision rounds are included, and define a revision round clearly. One revision round means one set of changes from the client, not endless small edits over many weeks. List exclusions in the client's own language, with a price note where you can. If photography, stock images, or extra pages cost more, say so in the proposal, not after the work starts. A clear scope protects the client too, because they know exactly what their money buys.
| Proposal section | What it must answer | Common mistake to avoid |
|---|---|---|
| Situation | What problem does the client have | Repeating the brief word for word |
| Outcome | What result will the project achieve | Promising results you cannot control |
| Deliverables | What finished items will you hand over | Naming work without counting it |
| Not included | What costs extra if requested | Leaving exclusions unstated |
| Price | What the work costs, and when payment is due | Hiding the price until the end |
| Schedule | When each stage will be ready | Giving dates without client duties |
| Terms | Deposit, revisions, ownership, and cancellation | Copying terms you do not understand |
| Next step | What the client should do to accept | Ending without a clear action |
Presenting the price with confidence
Clients trust a price they can understand. You can present a fixed fee for the whole project, a tiered offer with two or three options, or a day rate for work that is hard to scope in advance. A fixed fee suits defined work with counted deliverables, and it gives the client certainty. A tiered offer suits clients who are unsure how much help they need, because they can choose a basic, standard, or fuller package. A day rate suits consulting, troubleshooting, or work where the scope will emerge as you go. Choose one presentation and commit to it, rather than mixing all three in one proposal. State the price plainly, name the currency, and say when payment is due. If you charge a deposit, state the amount and the point at which work starts. A deposit is a payment made before work begins, and it confirms that the client is committed. If you are unsure how to set your fee, read how to set freelance rates before you price the proposal. Add a validity date to your price, such as stating that the price holds for 14 days. A validity date is fair to both sides, because your diary and costs change over time.
A schedule the client can follow
A schedule is more useful when it names what the client must do, as well as what you will do. List each stage with a date, a deliverable, and any input you need from the client before that stage can start. For example, a design stage may need the client's logo files and brand colours by a set date. State what happens if client input arrives late, in plain language. You can say that late input moves later dates by the same number of working days. This is not rude, and it is not a threat. It is a clear rule that stops a project from drifting without anyone knowing why. Send the schedule as part of the proposal, not as a separate message later, so the client accepts the timing along with the price.
Terms in plain language
Terms are the rules of the project, and they should be written so a non lawyer can understand them. Cover the deposit, the payment schedule, the number of revision rounds, what happens when work goes beyond scope, who owns the work and when ownership passes, and how either side can end the project. Ownership usually passes when the client has paid in full, and you should state that plainly. Also state what happens if the client cancels, such as payment for work completed up to that point. Keep terms short in a proposal, because the full detail belongs in the contract. Electronic signatures are widely accepted in many places, as the Law Commission confirms in its electronic execution of documents report, and United States law on electronic signatures is explained in this contracts and electronic signatures guide. The proposal terms should match the contract terms, so the client is not surprised later. Our companion guide on freelance contracts explained covers each clause in more detail.
Sending the proposal and following up
Send the proposal in the format the client prefers, and make it easy to open. A shared link works well for longer proposals, because you can update it and track whether it was opened. A PDF works well when the client needs to share it inside their company or keep a fixed copy. Do not send an editable document as the main proposal, because the client or a colleague may change it by accident. After sending, follow up on a schedule, and stop at a clear end point. A polite message after three days, another after about eight days, and a final closing message after about fifteen days gives the client time without pressure. Each message should add something useful, such as answering a question or offering a short call. Never write that many proposals close on the follow up nudge as if it were a measured fact, because that claim has no source. Follow up because it is polite and professional, not because a statistic promises a result.
Writing with no experience yet
A new freelancer can still write a strong proposal without inventing past work. Never claim clients, results, or experience you do not have. Instead, show proof that is honest. You can include samples you made for practice, clearly labelled as practice samples. You can describe relevant experience from a job, study, or voluntary project, and state honestly where it came from. You can offer a small paid trial, such as one article or one design, so the client can judge your work with low risk. A trial also helps you, because you learn whether the client is easy to work with. Focus your proposal on the client's problem and your plan, not on a long list of credentials. Clients hire freelancers who understand the task and explain their method clearly, not only freelancers with long client lists. If your freelance portfolio is still small, link to your best two samples rather than a long page of unfinished work.
What it costs and what to expect
Writing proposals costs time, and that time is part of running a freelance business. A short platform bid may take 20 to 40 minutes when you tailor it properly. A longer direct client proposal may take two to four hours, including a short call, a plan, and a price check.
Mistakes to avoid in proposals
The most common proposal mistakes are easy to fix once you see them. Sending a generic bid that could fit any job tells the client you did not read the brief. Opening with your life story delays the result the client wants. Promising outcomes you cannot control, such as a set number of sales, creates a dispute later. Leaving scope vague invites extra work without extra pay. Hiding the price until the last line wastes everyone's time. Forgetting a validity date leaves an old price open for months. Following up every day annoys the client and harms your reputation. Copying another freelancer's proposal word for word produces a document that does not match your skills or terms.
Risks and limitations
A proposal is an offer, not a guarantee of work, and it does not protect you on its own. A client can accept your proposal and still delay, change scope, or pay late, which is why a signed contract and a deposit matter before you start.
Frequently asked questions
How long should a freelance proposal be
A platform bid should be about 120 to 200 words, because the client scans many bids quickly. A direct client proposal is usually two to six pages, because it must cover scope, price, schedule, and terms.
Should I include the price in my proposal
Yes, in most cases you should include the price, because clients need it to decide. A proposal without a price forces extra messages and can look evasive. If the scope is truly unclear, state a price range, explain what moves the price up or down, and offer a short call to fix the scope.
How much deposit should I ask for
A deposit is a payment made before work begins, and it confirms commitment on both sides. Many freelancers ask for a deposit on larger projects, and the right amount depends on the project size, the client, and local practice. State the deposit, the payment point, and whether work starts before or after it arrives, so there is no confusion.
How often should I follow up on a proposal
Follow up politely after a few days, then again after about a week, and send a final closing message after about two weeks. Each message should add value or ask a useful question, rather than repeating the same nudge. After the final message, stop, and keep the relationship open for future work.
What if I have no past client work to show
Show honest proof instead of inventing experience. Use practice samples labelled as samples, describe relevant work from a job or study honestly, and offer a small paid trial where it fits. Focus on the client's problem and your clear plan, because those matter more than a long client list.
What should I do if a client asks for extra work after acceptance
Quote the extra work in writing before you start it, and state the price and the effect on the schedule. Do not start extra work on a verbal promise, because the scope and the fee can be remembered differently later. A short written update keeps the project and the relationship in good shape.
Conclusion: write the next proposal with a clear structure
A winning proposal starts with the client's problem, states counted deliverables, shows exclusions, presents a clear price, sets a schedule with client duties, and ends with one next step. Send it in an easy format, follow up politely on a schedule, and learn from every reply. Your next step is to write one proposal using the structure in this guide, then check it against the mistakes section before you send it. For the next stage of the process, read freelance contracts explained and how to invoice freelance clients, and browse all our guides on the freelancing category page.
