How to create a design proposal, step by step
A strong design proposal starts from a clear understanding of the client’s goals, then sets out the problem, proposed approach, scope and deliverables, process and timeline, team, pricing, assumptions and terms, and next steps. It is concise, tailored to the client, easy to compare and honest about what is and is not included.
Why proposals matter
For design studios and freelancers, the proposal is often where projects are won or lost. Clients may receive several proposals for the same brief, and they need to decide which partner understands their problem best, offers a credible plan and represents good value. A clear, tailored proposal makes that decision easier. A generic document full of services and boilerplate makes it harder.
A good proposal also protects both sides. By defining scope, deliverables, timeline, pricing and responsibilities, it reduces misunderstandings later. Our guide to hiring a UX design agency shows how clients typically evaluate proposals, which is useful context when writing one.
Before you write: understand the brief
- Clarify the business goals and how success will be measured
- Understand who the users are and what is known about them
- Ask about budget range, timeline and decision process
- Identify constraints such as technology, brand or regulation
- Learn who the stakeholders are and what each cares about
A short discovery call or workshop before writing often reveals the real problem behind the brief and lets you tailor the proposal.
A proven structure
| Section | What to include |
|---|---|
| Summary | The client’s goal and your recommended approach in a few sentences |
| Understanding the problem | Your interpretation of the challenge, users and goals |
| Approach | How you will solve it and why |
| Scope and deliverables | What you will produce, and what is not included |
| Process and timeline | Phases, milestones and review points |
| Team | Who will work on the project and their experience |
| Relevant work | Short examples of similar projects and results |
| Pricing | Costs by phase or deliverable, with payment terms |
| Assumptions and terms | Dependencies, responsibilities, ownership and changes |
| Next steps | How to approve and when work can start |
Lead with the client, not yourself
Many proposals open with pages about the agency. Clients care more about whether you understand their problem. Start with a short summary of their goal and your recommended approach, followed by your understanding of the challenge. Keep information about your studio brief and relevant, placing it later in the document.
Explaining your approach
Describe how you will solve the problem and why your approach fits this client. Explain the key activities, such as research with users, workshops with stakeholders, prototyping and testing, and how each one reduces risk or improves the outcome. Connect your approach to the client’s goals rather than listing generic steps. Showing a short example from a similar project can make the approach feel concrete. Our post on finding the right creative partner describes what clients look for.
Define scope and exclusions
Scope creep is one of the most common sources of conflict in design projects. Be specific about deliverables, such as the number of screens, rounds of revisions, research sessions or design system components. Equally important, list what is not included, such as copywriting, development, photography or extra languages. Explain how changes outside the scope will be handled.
- Deliverables: Specific outputs and quantities.
- Revisions: Number of review rounds included.
- Exclusions: Work not covered by the proposal.
- Change process: How new requests are estimated and approved.
Process and timeline
Describe your process in phases, such as discovery, design, testing and handoff, with milestones and client review points. A simple timeline helps clients plan and shows that you have thought through the work realistically. Our post on the UI/UX design process offers a typical structure.
Pricing clearly
Break pricing down by phase or deliverable so clients can see what they are paying for and adjust scope if needed. State whether prices are fixed, estimates or based on time and materials, and set out payment terms, such as a deposit and milestone payments. Offering options, for example a core package and an extended package, can help clients choose without starting negotiations from scratch.
Introducing the team
Clients want to know who will actually do the work. Name the key people, their roles and relevant experience, and explain how much of their time the project will receive. If senior people will lead strategy but others will handle production, say so clearly. Honest team information builds trust and avoids disappointment later.
Assumptions and terms
- Client responsibilities, such as providing content and timely feedback
- Ownership of designs and source files on payment
- Confidentiality and data handling
- What happens if timelines slip on either side
- Validity period of the proposal
Presenting the proposal
- Keep it concise: Aim for clarity over length.
- Make it scannable: Headings, tables and short paragraphs.
- Tailor every section: Avoid generic boilerplate.
- Walk the client through it: Present live where possible and answer questions.
- Follow up: Agree next steps and timing.
Common mistakes
- Opening with pages about your company
- Copying generic text between proposals
- Vague scope with no exclusions
- A single lump-sum price with no breakdown
- No clear next step or approval process
Frequently asked questions
How long should a design proposal be?
Long enough to explain the problem, approach, scope, timeline and price clearly, often around five to ten pages.
Should we include pricing options?
Offering two or three options can help clients choose a scope that fits their budget.
How do we avoid scope creep?
Define deliverables, revisions and exclusions clearly, and agree a process for handling changes.
Should we do free design work in a proposal?
Generally no. Share relevant past work and your thinking instead, and offer a paid discovery phase if needed.
How quickly should we send a proposal after a brief?
Usually within a week, after a discovery conversation, so it reflects the client’s needs while the project is still fresh.
Should proposals include case studies?
Include short, relevant examples with outcomes, linking to full case studies rather than adding long sections.