A sample proposal is only useful if it shows you what actually goes inside and why. Most template libraries give you the shell without the reasoning. This breakdown goes section by section through a real working proposal format.
Let’s be direct about what a project proposal needs to accomplish: the client should be able to read it and make a decision. Every section exists to give them the information they need for that decision. When a section doesn’t serve that purpose, cut it.
Here’s a complete breakdown of what a working project proposal looks like.
Section 1: Project summary (½ page)
This is a two to four sentence overview of the entire proposal. Write it last. It should answer:
- What is this project?
- Who is it for?
- What’s the core outcome?
- What’s the total investment and timeline?
Example:
“This proposal outlines a website redesign for [Company Name], covering the homepage, services page, and about page. The goal is a professional, conversion-focused web presence ahead of your Q3 product launch. Total investment: $5,400. Timeline: 4 weeks from project start.”
Section 2: The situation (½ page)
Brief context on why this project exists. Not a lengthy analysis — two to four sentences establishing that you understand the client’s current situation and what they’re trying to change.
This section should be written specifically for this client. It’s not boilerplate. If you could send the same section to a different client without changing it, rewrite it.
Section 3: Scope of work (1 page)
This is the core of the proposal. Be specific about:
- What you will deliver
- What format it will be delivered in
- How many rounds of revision are included
- What is explicitly out of scope (optional but valuable for complex projects)
Use a structured format. Tables or bulleted deliverable lists are easier to evaluate than paragraphs:
| Deliverable | Description | Timeline |
|---|---|---|
| Discovery session | 90-minute briefing + positioning summary | Week 1 |
| Homepage design | Figma prototype, 2 revision rounds | Week 2–3 |
| Copy | Page copy for all three pages | Week 3 |
| Final files | Figma handoff files + copy document | Week 4 |
The scope section does double duty: it gives the client enough information to say yes, and it protects you from scope creep later. Time spent being specific here saves many hours of difficult conversations during the project.
Section 4: Timeline
A simple visual or table showing when major phases and deliverables happen. For a four-week project, a week-by-week summary is sufficient:
- Week 1: Discovery and strategy
- Weeks 2–3: Design and copy
- Week 4: Revisions and final delivery
For longer projects, mark key milestones and any client review checkpoints explicitly. Note anywhere the timeline is dependent on client feedback or approvals.
Section 5: Investment
State the price clearly. Present it as a single line or as a simple breakdown if components are priced separately. Then state payment terms immediately after.
Example:
Total project investment: $5,400 Payment: 50% ($2,700) due at project start. 50% ($2,700) due upon delivery of final files. Revisions beyond included rounds: $120/hour.
Avoid presenting pricing in a way that looks like it’s hiding from the client. Put it in a legible format. If there’s a range rather than a fixed price, explain what determines where within the range the project lands.
Section 6: Next steps
The last section should tell the client exactly what to do. One action, clearly stated.
Examples:
- “To move forward, reply to confirm and I’ll send over a project agreement and first invoice.”
- “Sign below to accept this proposal. I’ll send your deposit invoice within 24 hours.”
- “If you’d like to discuss before confirming, I’m available for a 15-minute call any day this week.”
Formatting and delivery
For PDF proposals: use clean typography, a header with your name and the client’s name, and enough whitespace to make the document readable at a glance. Avoid dense paragraphs, small fonts, and overly colorful designs that distract from the content.
For digital proposals (sent as a link rather than a PDF): the same structural rules apply, with the added benefit of read tracking. Knowing when and how often the client views your proposal changes your follow-up approach entirely. If they open it four times in two days, that’s a signal to reach out. If it was opened once three days ago and never again, a different follow-up is needed.
A good proposal PDF isn’t impressive because it looks polished. It’s impressive because it makes the client’s decision easy.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
