A proposal’s sections aren’t arbitrary. Each one exists because the client has a question at that point in their reading. Get the structure right and you’re answering questions in the right order. Get it wrong and you’re either answering questions the client hasn’t asked yet or leaving out ones they’re definitely asking.
Section 1: Header
The header establishes the basics. Your business name and contact info, the client’s name and company, the date, and a proposal reference number (e.g., “Proposal 2026-011”).
The reference number looks small but it matters. It tells the client this is a formal document, makes filing easy on both sides, and gives you a consistent way to track which proposals are out.
Section 2: Project summary
This is the section most freelancers write poorly. It should be 50–100 words that restate the client’s situation in your words. Not their words copied from the brief — your interpretation.
What were they trying to solve? What context made this a priority right now? What does success look like?
This section does one job: make the client think “this person understood exactly what I told them.” When that happens, the rest of the proposal gets read with trust instead of skepticism.
Section 3: Deliverables
Specific, named outputs. Bullet points work better than prose here.
Bad: “Website redesign including all pages” Good: “Redesigned homepage, about page, services page, and contact page in Figma (desktop and mobile), delivered as developer-ready components with an annotated style guide”
Every deliverable should answer: what will physically exist when you’re done that didn’t exist before? Vague deliverables create scope disputes later. Specific ones prevent them.
Section 4: Timeline
How long each phase takes and when each milestone occurs. A simple table is more readable than a paragraph:
| Phase | Description | Duration |
|---|---|---|
| 1 | Discovery and research | Week 1 |
| 2 | Initial designs (2 concepts) | Weeks 2–3 |
| 3 | Revision rounds | Week 4 |
| 4 | Final delivery | Week 5 |
Include a note about when you need the client’s input. If their feedback delays are your biggest scheduling risk, say so here.
The timeline section protects you as much as it informs the client. A proposal without a timeline makes scope creep almost inevitable, because there’s no agreed reference point when the project starts drifting.
Section 5: Pricing
Your total fee, stated plainly. Include:
- The total amount
- Payment schedule (what percentage is due when)
- What’s included and what’s billed separately (revisions beyond the stated rounds, rush fees, travel)
Don’t bury the price. Some freelancers put it at the end to “build value first,” but most clients scroll straight to the number anyway. Putting it in a logical position in the document flow is more professional than hiding it.
Section 6: About you
One paragraph, 60–100 words. Not a resume summary — a specific, relevant proof point.
“I’ve designed onboarding flows for nine B2B SaaS companies, including [X], where we reduced drop-off from first to second login by 34% in 60 days. I work primarily with Series A to B companies and have been doing this full-time since 2019.”
Every sentence in this section should be relevant to this client’s specific project. If you’re writing copy about your photography experience for a software client, cut it.
Section 7: Next step
A single, specific instruction. What should the client do to say yes?
“Reply to this email to confirm, and I’ll send the contract and first invoice within 24 hours.” “Sign below — I’ll send a kickoff calendar link the same day.” “Let me know if you have questions; otherwise, I’m ready to start the week of [date].”
Remove all ambiguity. The proposal’s job is to get a decision — not to leave the client wondering what happens if they like what they see.
Optional sections worth knowing
Executive summary: For proposals over 4 pages, add a 3–5 sentence executive summary before the project summary. Senior stakeholders often read only this. Put your strongest framing here.
Methodology: Add this for consulting or strategy work where the process is as important as the output. Describe your approach in phases.
Terms: For longer engagements, a brief terms section covering IP ownership, kill fee, and change order policy saves later friction. Keep it short — 150 words maximum in the proposal, with a full contract to follow.
Social proof: A one-line testimonial or a reference to a specific past result. Add this only if it’s directly relevant to the current project.
What order to use
The 7 sections in order: header → project summary → deliverables → timeline → pricing → about you → next step. This order mirrors the questions a client asks in sequence: What is this? What will I get? When? How much? Can I trust you? What do I do now?
Don’t rearrange it dramatically. Some freelancers move pricing to the end to delay sticker shock — but clients know there’s a price somewhere and they’re scanning for it. Putting it in the natural flow is cleaner.
If you want to see what sections clients actually spend time reading, tools like Waco’s proposal tracking show you time-on-section data after you send the proposal. That feedback helps you figure out whether your pricing section is holding attention or your deliverables section is unclear.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
