Freelance Proposals & Contracts

What Is a Freelance Proposal?

A freelance proposal is a structured document you send to a potential client to outline how you plan to solve their problem. It is not an invoice. It is not a contract. It is a sales document designed to demonstrate competence, build trust, and make it easy for the client to say yes.

Think of a proposal as the bridge between a discovery call and a signed contract. You have had the conversation, you understand what the client needs, and now you are putting it in writing so there is no ambiguity about what will happen next.

A good proposal does three things simultaneously. It shows the client you listened by reflecting their problem back to them in clear language. It demonstrates expertise by outlining a solution that feels considered rather than generic. And it removes friction by making pricing, timeline, and next steps completely transparent.

The worst freelance proposals read like templates with blanks filled in. The best ones feel like they were written specifically for this client and this project, because they were. Personalisation is not about flattery. It is about proving you understand the brief well enough to deliver on it.

Most freelancers underinvest in proposals because they feel like unpaid work. That is a mistake. The proposal is often the single most important document in the sales process. A well-crafted proposal can win a project against competitors who charge less, because clients buy confidence as much as they buy deliverables.

Proposal vs Scope of Work vs Contract

These three documents serve different purposes, and confusing them creates problems. Here is how they relate to each other.

A proposal is your pitch. It is persuasive writing designed to win the project. It covers what you will do, why your approach is right, what it costs, and a rough timeline. It should feel like a conversation, not a legal filing. The goal is to get the client to agree in principle so you can move forward.

A scope of work is the operational plan. Once the client agrees to the proposal, you define the scope of work in detail. This document lists every deliverable, milestone, revision round, acceptance criteria, and exclusion. It answers the question "what exactly am I paying for?" with zero ambiguity. This is the document you reference when a client asks for something that was not included.

A contract is the legal agreement. It covers payment terms, intellectual property transfer, confidentiality, liability limitations, termination clauses, and jurisdiction. Some freelancers fold this into their scope of work, creating a single document that serves as both the project plan and the legal agreement. That works fine for most projects.

The typical workflow looks like this: discovery call, then proposal, then signed scope of work with contract terms, then deposit invoice, then work begins. For smaller projects, you might combine the proposal and scope of work into a single document. For larger projects or agency work, keeping them separate gives you more flexibility.

What to Include in a Freelance Proposal

Every strong proposal covers the same core elements, regardless of industry. Here is what yours needs.

Problem Statement

Start by describing the client's problem in their own words. This might be a paragraph or two that restates what they told you during the discovery call. The point is to show them you listened and you understand the situation.

Do not make this generic. "You need a new website" is lazy. "Your current website loads in 8 seconds on mobile, your bounce rate is 73%, and your competitors are outranking you for every key search term" is specific and demonstrates that you have already done some homework.

The problem statement sets up everything that follows. If the client reads this section and thinks "yes, that is exactly right," you have earned their attention for the rest of the document.

Proposed Solution

Outline what you will do to solve the problem. Be specific about your approach without turning this into a technical manual. The client needs to understand what you are doing and why, not how to do it themselves.

Break the solution into phases if the project is complex. Phase 1 might be research and strategy, phase 2 might be design, phase 3 might be development, and phase 4 might be testing and launch. Each phase should have a clear outcome so the client can see progress.

Include your reasoning. Explain why you are recommending this approach over alternatives. If the client asked for a WordPress site but you think a static site would be faster and cheaper, say so and explain why. Clients value honest advice, even when it contradicts their initial assumptions.

Timeline

Give a realistic timeline with milestones. Do not promise to deliver a six-week project in three weeks to win the bid. Under-promising and over-delivering builds trust. Over-promising and under-delivering destroys it.

Include buffer time for client feedback. One of the most common reasons freelance projects run late is that clients take longer to review work than expected. Build this into your timeline from the start. If you say "design concepts delivered by week 2, client feedback due by week 3," you have set a clear expectation that delays on their side push the whole project back.

Be explicit about what happens if the timeline slips. If the client takes two weeks to give feedback instead of one, does the delivery date shift by a week? State this upfront so there are no surprises.

Budget and Pricing

Present your pricing clearly. You have three main options here. You can list a single project fee, you can break it down by phase, or you can offer tiered packages (good, better, best). The right approach depends on the project and the client.

For most freelancers, a single project fee with a brief breakdown of what is included works well. Something like: "Total project fee: £4,500. This includes discovery workshop (1 day), wireframes (5 key pages), visual design (5 pages with 2 revision rounds), development, testing, and launch support."

Always state what is not included. Content writing, stock photography, hosting, ongoing maintenance — if these are additional costs, say so. Clients hate surprises on the invoice. Learn more about structuring your freelance pricing strategy.

Terms and Conditions

Your proposal should include basic terms even if you will send a separate contract later. Cover payment terms (50% deposit, 50% on completion), revision limits, intellectual property transfer, and cancellation policy. These do not need to be in legal language at this stage — just clear statements of how the engagement will work.

How to Write a Winning Proposal Step-by-Step

Here is the process that consistently wins projects, based on what actually works in practice rather than theory.

Step 1: Have a real discovery conversation. You cannot write a good proposal without understanding the project. Ask about the client's goals, their budget range, their timeline, who the decision-makers are, what they have tried before, and why it did not work. Take notes. The information you gather here becomes the raw material for your proposal.

Step 2: Research before you write. Spend 30 minutes looking at the client's existing setup, their competitors, and any relevant market data. If you are a web designer, open their current site and take notes on what works and what does not. If you are a copywriter, read their existing content and identify gaps. This research makes your proposal specific rather than generic.

Step 3: Open with the problem, not with yourself. Resist the urge to start with your bio or your agency's history. Start with the client's problem. They already know who you are — they are reading your proposal. What they want to know is whether you understand their situation well enough to fix it.

Step 4: Describe the solution in terms of outcomes. "We will redesign your homepage" is a deliverable. "Your homepage will load in under 2 seconds and include a clear conversion path from landing to enquiry form" is an outcome. Clients care about outcomes because outcomes connect to business results.

Step 5: Price with confidence. Do not apologise for your rates. Do not say "our prices are competitive." State the fee, explain what is included, and move on. If your price is higher than competitors, your proposal should have already demonstrated why you are worth it through your understanding of the problem and the quality of your proposed solution.

Step 6: Make the next step obvious. End with a clear call to action. "If you are happy to proceed, reply to this email and I will send over the scope of work and deposit invoice within 24 hours." Do not leave the client wondering what happens next.

Step 7: Follow up. If you have not heard back in 3-4 business days, send a brief follow-up. Not a pushy sales email — just a genuine check-in. "Hi Sarah, just checking whether you had any questions about the proposal. Happy to jump on a quick call if anything needs clarifying." Most proposals are not rejected. They are forgotten. Following up is not annoying; it is professional.

Freelance Contract Essentials

Whether you use a standalone contract or build terms into your scope of work, these elements need to be covered before you start work on any project.

Scope and deliverables. List exactly what you will deliver. Not vaguely — exactly. "5 web pages" is better than "a website." "5 web pages (Home, About, Services, Portfolio, Contact) with responsive design, SEO meta tags, and cross-browser testing" is better still. The more specific your scope, the easier it is to push back on requests that fall outside it.

Payment terms. State the total fee, the deposit amount, when milestone payments are due, and the payment method. For most freelance projects, a 50% deposit before work starts and 50% on completion is standard. For larger projects, consider splitting into three or four milestone payments to maintain cash flow.

Timeline and milestones. Include start date, milestone dates, and the expected completion date. State that dates are contingent on timely client feedback and that delays on the client side may shift the timeline.

Revision policy. Specify how many rounds of revisions are included. Two rounds is standard for most creative work. Define what constitutes a "round" — a revision round is a single batch of feedback, not an ongoing back-and-forth. Additional revisions beyond the included rounds are billed at your hourly rate.

Intellectual property. In most freelance arrangements, intellectual property transfers to the client upon final payment. State this explicitly. Some freelancers retain the right to use the work in their portfolio — include this if it matters to you.

Cancellation and kill clause. If the client cancels the project, what happens? A standard approach is that the client pays for all completed work plus a cancellation fee (often 20-25% of the remaining project value). The deposit is non-refundable. Without a kill clause, you risk doing weeks of work and getting nothing if the client changes direction.

Liability limitation. You should not be liable for indirect or consequential damages. If you build a website and the client's business loses revenue because of a bug, your liability should be limited to the project fee, not the client's lost income. This is standard and reasonable.

Confidentiality. A basic confidentiality clause protects both parties. You agree not to share the client's proprietary information, and they agree not to share your pricing with competitors. Keep it mutual and proportionate.

When to Use a Proposal vs Contract

Use a proposal when you are trying to win the project. Use a contract when you have won it and need to formalise the terms before starting work.

For quick projects under £1,000, you can often combine both into a single document. A one-page proposal that includes deliverables, pricing, timeline, and basic terms, with a signature line at the bottom, is enough. The client signs it, pays the deposit, and you begin.

For projects over £5,000 or projects with multiple stakeholders, keep them separate. The proposal goes to the decision-maker to get buy-in. The contract goes to whoever handles the legal side, which might be a different person entirely. Mixing sales language with legal terms in a single document slows down both processes.

For ongoing retainer work, you need a master services agreement (MSA) rather than a project-specific contract. The MSA covers the general terms of the relationship, and individual project scopes are attached as addendums. This saves you from negotiating contract terms every time the client needs a new project.

Converting Proposals to a Scope of Work

Once the client accepts your proposal, the next step is to create a detailed scope of work. This is where you take the broad strokes from the proposal and turn them into a precise project plan.

The scope of work should include everything from the proposal's solution section, but with more detail. Where the proposal said "we will design 5 key pages," the scope of work says "Page 1: Homepage — includes hero section with CTA, 3 feature blocks, testimonial carousel, footer with contact form. Desktop and mobile layouts. 2 revision rounds included."

Add acceptance criteria to each deliverable. How will the client know when a deliverable is "done"? For design work, acceptance means the client has approved the design within the agreed revision rounds. For development work, acceptance means the feature works as described in the scope and passes the defined test criteria.

Include exclusions explicitly. If the proposal mentioned that content writing is not included, repeat that in the scope of work. If third-party integrations are out of scope, state that. Exclusions prevent scope creep by establishing clear boundaries from the start.

The scope of work is the document you reference throughout the project. When a client asks "can you also add a blog section?" you check the scope of work. If it is listed, you do it. If it is not listed, you quote it as an addition. No arguments, no awkwardness — just a reference to the agreed plan.

Common Freelance Proposal Mistakes

After reviewing hundreds of freelance proposals, the same mistakes come up repeatedly. Here are the ones that cost you projects.

Leading with your bio instead of the client's problem. The client does not care about your journey into freelancing. They care about whether you can solve their problem. Start with their situation, not yours.

Being vague about deliverables. "We will improve your online presence" means nothing. What exactly will you deliver? How many pages, posts, designs, or hours of work? Vagueness creates distrust because clients assume you are leaving yourself room to under-deliver.

Pricing without context. Dropping a number without explaining what the client gets for it feels arbitrary. Break down what is included so the client understands the value. This does not mean itemising your hourly rate — it means listing the deliverables that justify the total fee.

Taking too long to send it. If you had a discovery call on Monday, send the proposal by Wednesday. Every day you wait, the client's enthusiasm cools. They might talk to another freelancer. They might lose budget approval. Speed matters more than perfection.

Not including a deadline. Your proposal should have an expiration date. "This proposal is valid for 14 days" creates urgency and protects you from clients who come back six months later expecting the same price when your rates have increased.

Ignoring the competition. If you know the client is evaluating multiple freelancers, address it. What makes your approach different? Why should they choose you over someone cheaper? If you cannot articulate this, you are competing on price alone, and that is a race to the bottom.

Forgetting to follow up. About 40% of proposals are accepted on the follow-up, not the initial send. If you send a proposal and never follow up, you are leaving money on the table. Set a reminder for 3 days after sending and follow up with a brief, friendly message.

Making it too long. A 15-page proposal for a £2,000 project is overkill. Match the length of your proposal to the size and complexity of the project. A £2,000 project needs 1-2 pages. A £20,000 project might justify 5-8 pages. Anything longer and you are padding.

Not having a clear call to action. Every proposal should end with exactly one next step. "Reply to confirm and I'll send the scope of work and deposit invoice." If the client has to figure out what to do next, you have made the process harder than it needs to be.