What is a Web Design Proposal?
A web design proposal is a formal document presented by a web designer or design agency to a prospective client that outlines the design services being offered, the creative and UX approach, the scope and deliverables, the project timeline, and the pricing. It is the primary document used to win new web design clients and define the parameters of the design engagement before development or implementation begins.
Web design proposals are submitted for new website designs, website redesigns, landing page design, web application UI design, and e-commerce design projects. They are presented by solo freelance designers, design-focused agencies, and full-service web studios alike.
A web design proposal must accomplish two things simultaneously: it must convince the client that you understand their business and design goals, and it must demonstrate that you have a structured, professional approach to delivering the project on time and within scope. Web design projects are notorious for scope creep, delayed approvals, and unclear handoff expectations — a well-written proposal prevents all three by defining scope, process, and responsibilities from the start.
What to Include in a Web Design Proposal
Project Understanding and Goals
Summarize your understanding of the client's website objectives: what the site must accomplish for the business, who the target audience is, and what the current site's shortcomings are (if redesigning). Referencing specific details from your client discovery conversation demonstrates attentiveness and establishes your proposal as customized, not templated.
Design Approach and Style Direction
Describe your creative and UX design approach — the aesthetic direction, the user experience principles, and the design system you will create. Reference comparable websites or design styles that align with the client's brand. For redesign projects, note specific improvements to navigation, visual hierarchy, or mobile experience you are planning to address.
Project Scope
Define the site's structure:
- Number of unique page templates
- Pages to be designed (homepage, about, services, product pages, contact, blog, etc.)
- Responsive design: desktop, tablet, and mobile breakpoints
- Custom components: navigation menus, hero sections, pricing tables, forms, galleries
- Any interactive or animated elements
- Accessibility standards (WCAG compliance level if applicable)
Deliverables
Specify exactly what you will hand off:
- Figma, Sketch, or Adobe XD design files
- Number of included design concepts (initial directions)
- Revision rounds for each deliverable
- Design system documentation (style guide, component library)
- Any development handoff specs or annotations
Timeline
Present the project phases: discovery, wireframes, visual design concepts, design development, client reviews, revisions, and final handoff. Assign durations to each phase and identify client-dependent milestones (approval windows) that affect the schedule.
Investment
State your design fee broken down by phase if the project is large. Include the deposit, payment schedule, and your rate for revisions beyond the included rounds or scope additions.
How to Write a Professional Web Design Proposal
Include wireframe or visual references. Even rough wireframe sketches showing your proposed site structure, or a mood board with comparable design styles, make the proposal dramatically more persuasive. Clients can visualize what they are buying, which accelerates approval.
Define the page count explicitly. "A new website" is not a scope. List every page to be designed. Scope creep in web design almost always originates from pages, templates, or components that were not listed and then assumed to be included.
Specify the handoff format and recipient. Who will implement the designs — a developer, a CMS platform, or the client themselves using a no-code tool? The handoff format and level of annotation required depends entirely on this answer. Address it proactively.
Describe your revision management process. Define how feedback is collected (consolidated document, Figma comments, video annotation), how revision rounds work, and what happens when client feedback requires design changes that go beyond the included revision scope.
Web Design Proposal Best Practices
Separate design from development. If you offer both design and development, price them as separate line items. Clients who are comparing only design quotes need to see design pricing distinctly, and clients who already have a developer need to know what they are paying for.
Define content responsibility. Web design timelines frequently stall because clients have not prepared their copy, images, or brand assets. Include a content responsibility matrix in your proposal: what you will produce, what the client must provide, and by when.
Include a design system deliverable. Delivering a documented design system — color variables, typography scale, component library — protects your design intent through development and gives the client an asset they can use for future work.
Reference your development handoff process. If you use Figma with developer mode or hand off annotated spec documents, describe this briefly. Clients and developers both appreciate knowing that the handoff has been thought through.
Common Mistakes to Avoid
No page count. Scope creep in web design projects almost always comes from pages and features that were not defined upfront. List every page explicitly.
Not addressing content dependency. If the client provides no content and you write no copy, state this clearly. A beautiful design populated with placeholder text will not function as a real website.
Unlimited revisions. Open-ended revision language in web design is extremely costly. Define a specific number of rounds, what constitutes a round, and your rate for additional revisions.
Confusing design handoff with a live website. Many clients assume a web design project results in a live website. If your scope ends at design handoff, state this explicitly and reference who will implement the designs.