Start with discovery, not a template
A proposal written before discovery is usually a price with decoration around it. Ask enough questions to understand the problem, the decision-maker, and what success looks like.
- What is the business problem behind this project?
- What has already been tried, and what happened?
- Who needs to approve the work, and what does each person care about?
- What is fixed, and what is still open?
- What deadline matters, and why?
- What would make this project a clear success six months from now?
Write down the client's words. Reusing their language in the proposal is more useful than filling it with generic agency phrases.
A practical proposal structure
- Title and client context: project name, client, date, and a one-line summary of the problem.
- Understanding: what you heard, what it means, and the outcome the client wants.
- Proposed approach: the phases, deliverables, and decisions you will make together.
- Scope and exclusions: what is included, how many review rounds, and what triggers a change request.
- Timeline: milestones, client dependencies, and assumptions about response time.
- Investment: price, payment schedule, what is included, and what is not.
- Terms: validity, cancellation, ownership, confidentiality, and payment terms.
- Next step: exactly how to approve the proposal and what happens after approval.
A practical outline
Project: Website redesign for Harbor Studio
Prepared for: [Client name]
Goal: Make the studio's services easier to understand and give prospective clients a clear enquiry path.
What we heard: The current site has strong project visuals, but visitors cannot tell which services fit their needs. The team also wants to update case studies without rebuilding the site.
Approach: Discovery and content structure, design direction, build, testing, and a short handover session. The project includes two structured review rounds at the design and build stages.
Keep the opening focused on the client. A short "About us" paragraph can follow, but it should not be the first thing the client reads.
Present the price clearly
Show the price next to the scope it buys. A number without context invites comparison with unrelated quotes. A fixed project price should state the deliverables, assumptions, review rounds, and payment schedule.
- Fixed project: best when the scope is clear and the main risk is delivery effort.
- Milestone payments: useful for larger projects where work can be reviewed in stages.
- Retainer: appropriate for an ongoing capacity or support commitment, not for hiding unclear project scope.
If you offer options, make the differences meaningful. "Option A: smaller scope, lower price" and "Option B: expanded reach, higher price" is more useful than three numbers with no explanation.
Use your hourly rate as a floor, then price the project as a whole. Do not silently pad hours. Show any explicit risk allowance or contingency in your own notes and apply it consistently.
Terms and next step
Terms should reduce ambiguity, not create a legal maze. State how long the proposal is valid, when payment is due, what happens if the project is paused, who owns the final work, and how changes are handled. Have a qualified professional review contract language where needed.
End with one clear action: approve the proposal, pay the deposit, or book the kickoff. Provide the exact link or instruction. If multiple approvals are required, name the sequence.
Do not promise an outcome you cannot control. Describe what you will do, what the client will provide, and how success will be reviewed. Avoid invented guarantees, rankings, or revenue claims.
Common mistakes
- Leading with your biography. The client wants to know that you understand their problem.
- No exclusions. Unclear boundaries turn small requests into unpaid scope creep.
- Vague deliverables. "Website refresh" is not a deliverable. "Homepage, six service pages, and a handover session" is.
- Missing client dependencies. Content, approvals, and access delays should be named in the timeline.
- No decision step. A proposal that ends with "let me know" is easy to postpone.
- Copying the same proposal every time. Reuse the structure, not the assumptions.
Final quality check
- The client's problem and desired outcome are stated in their language.
- Deliverables, scope boundaries, and review rounds are explicit.
- Timeline includes client dependencies and assumptions.
- Price, payment schedule, and what is included are easy to find.
- Terms are reviewed and appropriate for the project.
- There is one clear approval or next-step instruction.
- Placeholders, old client names, and inconsistent numbers are removed.
Use the Proposal Generator to create a structured draft you can edit and adapt. If you need the full client-acquisition set, the Proposal & Client Acquisition Toolkit includes proposal, scope, discovery, outreach, follow-up, and pricing documents.
Put this guide into practice
Build the first draft from your discovery notes. Use the free Proposal Generator to apply the steps in your browser. If you want editable templates around this workflow, the Freelance Proposal & Client Acquisition Toolkit includes proposal, scope, discovery, outreach, follow-up, and pricing templates for client work.