A freelance proposal template is only useful if you understand why each section is there. Most freelancers either copy a format without thinking about the logic behind it, or they invent their own structure that buries the information the client needs to say yes. What follows is the complete structure, six sections in order, with what each one should actually say.
Section 1: Problem Statement
The proposal opens with the client’s problem, not with who you are or what you offer. This is the section most freelancers get wrong, and it’s the one that matters most.
Two to three sentences that demonstrate you understood the brief. Reference specifics from your conversation or the materials they shared. The goal is not to diagnose their business, it’s to show that you listened carefully enough to articulate their situation accurately. A client who reads an opening paragraph that captures their problem precisely is already more than halfway to saying yes.
What this looks like:
“You’re launching a new product line in Q3 and need your website to reflect the brand repositioning before then. The current site was built three years ago and no longer matches your visual identity or how you want to position the company. The project is time-sensitive, you need final pages live by [date].”
That’s it. No preamble, no company description, no explanation of what a website is. The client already knows all of that. They want to know if you understand what they specifically need.
Section 2: Proposed Solution
One to two paragraphs describing your approach. Not a methodology, your specific thinking about this project.
What will you do first and why? What’s the hardest part of this project and how will you handle it? What’s your angle? This section is where you briefly show that you have a point of view, not just a process. Clients hire freelancers who think, not just execute.
Keep this section short. The details live in the scope section. Here you’re giving the client a sense of your thinking and confidence. Two strong paragraphs beat five detailed ones.
Section 3: Scope of Work
This is the most important section in the proposal. The scope defines what “done” looks like, and it’s the document both of you will reference when something is unclear mid-project.
Write scope as a deliverable list, not a narrative. Specific formats, quantities, and versions. If the project has phases, list them separately.
What this looks like:
Phase 1: Discovery and Design (Weeks 1–2)
- Brand review and design direction document
- Homepage wireframe (desktop and mobile)
- Client approval required before Phase 2 begins
Phase 2: Full Design Execution (Weeks 3–5)
- Five pages designed in Figma: Homepage, About, Services, Case Studies, Contact
- Two rounds of consolidated revisions per page
- Final files exported and ready for development handoff
What’s not included: Copywriting, development, SEO setup, ongoing maintenance.
The “what’s not included” section is the one most freelancers skip. It matters. Every dispute about “I thought that was included” started with a scope section that didn’t state what was excluded. A client who reads this and says “wait, copy isn’t included?” is a client you want to have that conversation with now, not four weeks into the project.
Section 4: Timeline
Specific dates, not ranges. “Approximately three to four weeks” is not a timeline.
What this looks like:
- Project start: [date]
- Phase 1 delivery: [date]
- Client feedback on Phase 1 due: [date, typically 5 business days after delivery]
- Phase 2 delivery: [date]
- Client feedback on Phase 2 due: [date]
- Final delivery: [date]
Include a single line about timeline dependencies: “This schedule assumes client feedback is received within five business days of each delivery. Delays in feedback will extend the timeline accordingly.”
Without that line, you’re holding yourself to a deadline that depends on client behavior you can’t control. With it, the responsibility for timeline slippage is clearly shared.
Section 5: Pricing
Lead with the total fee. Not the itemized breakdown, the total. Clients scroll to the price first regardless of where you put it, putting it on page three just makes them scroll more.
What this looks like (fixed price):
Total fee: $4,800
- 30% deposit ($1,440) due upon signing this agreement
- 70% ($3,360) due within 14 days of final delivery
Invoices unpaid after 30 days accrue a late payment fee of 1.5% per month.
That’s the complete pricing section for most projects. Clean, specific, no negotiation invitation embedded in the structure.
On itemized pricing: Avoid it. When you break out “discovery: $600, design: $2,400, revisions: $800,” you turn a scope conversation into a cost conversation. The client starts wondering if they really need the discovery phase. Fixed pricing presents the project as a whole and lets the scope section justify the number. Itemized pricing invites the client to audit your work before they’ve seen it.
On tiered options: Use them when the project genuinely has different scope levels. Three packages at $3,200 / $4,800 / $7,200, each with distinct scope, works. Three packages that are the same thing with different revision counts is not tiered pricing; it’s a negotiation trick clients see through.
Include a brief note that this proposal does not constitute a contract and that a separate contract will be issued upon acceptance. One sentence. For more on structuring the deposit and payment splits, see freelance payment terms and how to write them into your contract.
Section 6: Next Steps
End with a clear action, not a closing platitude.
What this looks like:
To move forward: reply to confirm this proposal and I’ll send the contract and deposit invoice within one business day. If you have questions or want to adjust scope, I’m happy to schedule a short call, [your scheduling link or preferred contact method].
This proposal is valid for [14] days.
The “valid for” line does two things: it creates mild urgency without being pushy, and it protects you from being held to a price that may not reflect your availability three months later.
The clear call to action matters. “Looking forward to hearing from you” puts the entire weight of the next step on the client with no guidance. “Reply to confirm” tells them exactly what to do.
After the Proposal: The Contract
When the client confirms, your next step is the contract. The proposal described the project; the contract governs it.
The contract scope should match the proposal scope exactly. If there were any verbal clarifications between sending the proposal and receiving acceptance, capture those in the contract. Don’t let things that were “agreed on the phone” stay verbal, the contract is where the phone conversation becomes binding.
Send the contract promptly after acceptance. Delays in the proposal-to-contract handoff give clients time to second-guess. If you have a clear sense of what to include in your contract, the document should take less than an hour to produce from the proposal scope you’ve already written.
A Note on Length
This entire proposal structure fits on one to two pages. If yours runs longer, something is wrong: either the scope is too complex to have defined clearly yet, or you’re including information the client doesn’t need to make a decision. Cut anything that doesn’t help the client say yes.
The proposal that gets read is the one that wins more often than the one that’s thorough. A client who has to commit an hour to reading your proposal before they can say yes is a client who’s putting off saying yes. Brevity signals confidence. A freelancer who knows their scope and pricing doesn’t need eight pages to explain it.