Proposals

What to put in a freelance proposal that wins the work

The structure of a proposal that closes — what to include, what to leave out, and why most freelance proposals lose to better-structured ones.

·8 min read·Proposals

Quick answer

A winning freelance proposal opens by mirroring the client's problem in their own words, lists concrete deliverables (not vague descriptions), shows a milestone-based timeline, states a single project price (not an hourly rate), and ends with a one-click next step. Keep it 1-4 pages of actual content. Send within 24-48 hours of the discovery call.

A freelance proposal isn't a document — it's the deal you're asking the client to agree to, written down so they can read it twice. Most proposals lose because they read like resumes (lots about the freelancer, little about the client) or like contracts (lots of terms, little persuasion). This guide is about the structure that wins: client first, problem first, decision easy.

Open by mirroring the client's problem

The first paragraph of your proposal should restate the client's situation in their language. Not yours, theirs. If they said 'we're launching a new product line and need brand work that distinguishes it from the parent company without losing visual continuity,' your opening should reflect that — not 'My approach to brand identity is rooted in research and craftsmanship.' This is the single highest-leverage move in proposal writing. A client who reads the first paragraph and thinks 'they get it' is already 70% sold; one who reads a generic intro is already half-checked-out.

Define what the engagement covers in concrete deliverables

List exactly what the client will receive. Not 'comprehensive brand identity work' — 'logo with three variants (primary, mark, monochrome), colour palette, type system, brand guidelines (12-page PDF), and three round of revisions per deliverable.' The reason for this specificity isn't pedantry; it's that the client is making a buying decision and needs to know what they're buying. Vague proposals lose to specific ones, every time.

Show the timeline as milestones, not a flat number of weeks

'8 weeks' is hard to evaluate. 'Week 1: research and discovery; week 2-3: concept exploration and selection; week 4-5: refinement and revisions; week 6-7: brand guidelines and asset preparation; week 8: handoff' is a project plan. The milestone view also gives you a structure for milestone payments, which protects your cashflow on longer projects.

Price the engagement, not the time

State a single project fee, not an hourly rate (unless the engagement is genuinely open-ended). If the work has natural tiers (a basic, standard, and premium version), present them — three options with clear differences let the client pick rather than negotiate. If you're offering one option, state the fee, what it includes, and what is explicitly out of scope. The most common reason clients negotiate is that they're trying to figure out what's flexible. Make the structure clear and they negotiate less.

Make the next step a one-click decision

End the proposal with a single, clear next step. 'To accept this proposal, click Approve below; you'll receive the contract and deposit invoice within an hour.' Not 'let me know your thoughts.' Not 'happy to discuss further.' Clients who like the proposal want to act on it, and the easier you make it to act, the higher your close rate. A proposal that ends in ambiguity becomes a thread of follow-up emails; a proposal that ends in a clear action gets approved or rejected within days.

What to leave out

Leave out the long bio. Leave out the lengthy 'about my process' section unless the client has specifically asked. Leave out anything that doesn't help the client decide. The proposal is not the place to demonstrate the breadth of your knowledge — it's the place to show you understand this client and have a clear plan for their work. Anything else dilutes attention and reduces close rate.

Key takeaway

A winning proposal is the client's situation, your concrete plan, and an obvious next step. Everything else is filler.

Send proposals as approve-with-one-click links

Build a proposal in kinako, send it as a link, and the client approves with one click — which automatically generates the contract and deposit invoice.

Get started free

Free plan · No credit card required

Frequently asked questions

How long should a freelance proposal be?

Most winning proposals are 1–4 pages of actual content (about 800–2,000 words), plus the deliverables list and timeline. Longer proposals don't win more deals — they often lose deals that a tighter proposal would have closed, because clients skim. The exception is enterprise procurement, where the proposal has to satisfy a formal RFP structure.

Should I send a proposal as a PDF or a link?

A link, when possible. A link lets you update the document if the client requests a small change without a new file round-trip; it lets you see when the client opens it; and it lets the client approve the proposal with a single click. PDFs are still appropriate for procurement-driven processes that require a static document, but for the typical freelance engagement, links win.

Should I include client logos or testimonials?

If they're directly relevant to the engagement, yes — a designer pitching a SaaS rebrand benefits from showing a SaaS rebrand they've done. If they're generic 'look how popular I am' content, leave them out; they read as filler. The bar is whether the proof point makes the client more confident in this engagement specifically.

How quickly should I send the proposal after a discovery call?

Within 24–48 hours. The client is most engaged in the days immediately after the call; if the proposal doesn't arrive while their interest is fresh, the deal stalls. If you can't realistically write a proposal in 24 hours, send a same-day note with a date you'll deliver by, so the client knows it's coming.

Related templates

Graphic Designer proposal template →Consultant proposal template →Web Designer proposal template →

Built for

For graphic designers →For consultants →For web designers & developers →

Keep reading

Pricing · 9 min

How to set freelance rates that don't undersell you

A grounded approach to pricing — how to think about hourly versus project rates, how much to charge, and how to raise prices without losing clients.

Contracts · 9 min

How to write a freelance contract that actually protects you

The clauses, structure, and language that prevent the disputes most freelancers learn about the hard way.

Project management · 8 min

How to prevent scope creep on freelance projects

The clauses, language, and habits that stop projects from drifting — without making you the freelancer who says 'no' to everything.