A proposal is not a sales brochure. It is a working agreement in plain language, and its job is to remove doubt before work begins. When a client can see what will be done, how it will happen, when each stage is due, and what happens if plans change, saying yes feels easier. When those details are missing, even a strong portfolio cannot carry the conversation, because the client is being asked to trust a process they cannot picture.
Start with the problem, not the portfolio
Open by describing the problem in the client's own terms. Show that you understand what the design must do, who it is for, and what success looks like in practical terms. A short summary of goals, audience, and constraints is worth more than pages of past work, because it proves you listened. Keep examples brief and relevant, and explain why each one matters for this project rather than listing everything you have ever made. If the brief is vague, say so kindly and propose a short discovery step before final scope is fixed, so neither side builds on guesswork.
Make scope, process, and timeline concrete
Scope should name the deliverables, the formats supplied, and anything the client must provide, such as text, images, or approvals. Process should explain the stages in order, from research and early concepts through refinement and final delivery, and name who approves each stage. A timeline should give realistic dates for each stage, including time for client review, rather than a single final deadline. This is also the place to describe the fee structure in general terms, such as payment in stages tied to agreed milestones, without turning the proposal into a long price list. Revision rounds should be named here too, and you can read more about keeping revision rounds fair and manageable before you promise them.
Write terms that protect both sides
Terms are not a sign of distrust. They are how two busy people agree on ownership, usage, payment timing, and what happens when a project pauses or ends early. State who owns the final files, what the client may use them for, and when files are handed over. Explain how late changes are handled, how feedback is collected, and how long the proposal itself remains valid. Use plain words, not legal jargon, and keep the section short enough that a client will actually read it.
End with a simple next step: a reply, a short call, or a signed acceptance, plus the date work could begin. A proposal that is clear, honest, and easy to act on sets the tone for the whole working relationship. For a related view on fees, see how to approach design fees with confidence, and for the longer view, read about planning the move from solo work to a small team.