How to Write a Freelance Proposal (With a Template)

A freelance proposal has one job: turn a good conversation into a signed yes. That means writing it in four parts — the client's situation, what you'll do, the price, and the next step — right after the call, while the details are still fresh, and sending it within a day or two while the conversation is still warm. Below is exactly how to write one, start to finish, plus a fill-in template and a prompt that drafts it from your call notes.

Before you write anything: get the call right

A strong proposal is written, not invented. It comes from a discovery call where you asked enough to write something specific — the client's actual problem, a deadline they mentioned, a budget range, and anything they seemed worried about. If you're still working out what to ask on that call, preparing for a discovery call covers exactly that step, and it comes before this one.

Write the proposal within 24–48 hours of the call. Any longer and two things happen: the details blur in your memory, and the client's attention has moved on to whoever replied first.

The four-part structure

Every proposal that gets read in full follows the same shape:

1. Situation — one or two sentences proving you listened, referencing something specific from the call, not their industry in general.
2. What I'll do — a short numbered list of the actual deliverables, in plain language.
3. Investment — the price, stated once, plainly, with payment terms.
4. Next step — one sentence telling them exactly how to say yes.

A fill-in template

Copy this straight into a document and fill in the brackets from your call notes:

[Client name] — [Project name]

Situation: [One or two sentences referencing the specific problem or deadline they mentioned on the call.]

What I'll do:

1. [Deliverable one]
2. [Deliverable two]
3. [Deliverable three]

Investment: [PRICE], [PAYMENT TERMS, e.g. 50% upfront, balance on delivery].

Next step: Reply "yes" and I'll send the agreement and deposit invoice today.

That's the entire document. No cover page, no company history, no bulleted "our process" — if you want to talk about how you work, that's what your portfolio or the call itself is for.

Common mistakes worth avoiding

Restating their industry instead of their situation. "As a growing skincare brand, you understand the importance of strong visuals" is generic and could be sent to anyone. "Your last shoot didn't match your new packaging" proves you were actually listening.

Vague timelines. "A few weeks" isn't something a client can plan around. If they mentioned a deadline, name it specifically and show your delivery date lands ahead of it — that one sentence often does more to win the job than anything else in the document.

A price that hedges. Tiered options, "starting from" language, and fine print all signal you're nervous about the number. State it once and let the deliverables you described justify it.

Once a proposal is signed, the two things that actually protect the relationship are getting the payment terms enforced without awkwardness — a late-payment email template covers that — and staying ahead of any request that creeps past what you scoped, which how to say no to scope creep walks through.

The copy-paste prompt

Paste your raw call notes in — they don't need to be tidy — and this turns them into a finished proposal in the four-part structure above.

You are a plainspoken proposal writer for a freelancer or solo service business. Turn my
call notes into a short, clear client proposal — no filler, no company history, no hedging
on price.

Context:
- My name / business: [NAME]
- Client name and business: [CLIENT NAME]
- Call notes (paste as-is): [NOTES]
- The offer: what's included, scope limits: [OFFER]
- Timeline, including any deadline the client mentioned: [TIMELINE]
- Price and payment terms: [PRICE / TERMS]

Task: write a proposal with exactly four sections — Situation (1-2 sentences proving you
understood their specific problem, from the notes), What I'll do (a short numbered list),
Investment (the price stated once, plainly, with terms), and Next step (one sentence on how
to say yes).

Constraints: under 300 words total. No company bio, no vague timelines — use the specific
date if one was mentioned. Ask me for the client's name if it's missing rather than leaving
a placeholder.

What it looks like in practice

Fed notes from a call with a coach whose client wants a six-week group programme launched before the new year, worried about it feeling generic like her last cohort — offer: curriculum design, five live sessions, private community setup; price $2,800, 50% upfront — the situation line comes back as:

Your last cohort felt templated to your members, and this one needs to feel built specifically around where your group is starting from, with everything ready before the new year.

That's a sentence a client reads and recognises immediately — which is what gets a proposal replied to the same day it lands, instead of filed away to "look at properly later."

FAQ

How long should a freelance proposal be?

Under one screen, ideally under 300 words. Length signals nervousness, not thoroughness — a client who has to scroll is a client who stops reading.

Should I send a proposal before or after a call?

After. A proposal written from a real conversation is specific and lands faster than one written from an enquiry form, because it can name the client's actual situation.

Do I need to include my full terms and conditions in the proposal?

No — keep the proposal to scope, price, and timeline, and reference that a short agreement or contract follows once they say yes. Bundling everything in one document makes it heavier and harder to read.

Writing a proposal from scratch every time is one of 30 ready-made workflows in the AI Business OS — paste your call notes in, and it's drafted in well under a minute, in our runs.