What to Include in a Web Design Proposal (and What to Leave Out)

A proposal is a filter as much as a pitch

A good proposal does two jobs. It persuades the client that you understand their problem, and it sets boundaries so both sides know what will and will not be delivered. Most project disputes trace back to a proposal that was too vague about the second job.

Aim for something short enough to read in ten minutes and specific enough to be attached to a contract.

Start with the client's problem

Open with two or three sentences that restate the client's goal in their own words: what is not working now, and what success looks like. This shows you listened and gives you something measurable to point to later, such as "increase enquiry form submissions" or "reduce checkout abandonment".

Scope and deliverables

This is the most important section. Be concrete about what is included:

• The number and type of pages or templates, for example "8 pages: home, about, services, 3 service detail pages, contact, blog index".
• The design deliverables, such as desktop and mobile layouts, and a style guide.
• The technical stack and any integrations, such as a CMS, email tool, or payment provider.
• Content responsibilities: who writes the copy, who supplies images.
• Post-launch items such as training, analytics setup, and a support window.

Explicitly list what is out of scope

Write down what is not included: additional page templates, copywriting, photography, ongoing SEO work, hosting fees. Stating exclusions is not defensive, it is clarity. When the client later asks for something on the list, you can quote a change order calmly instead of arguing.

Timeline and revision policy

Break the project into phases with dates: discovery, design, development, review, launch. Note that the timeline depends on the client providing feedback and content on time, and say what happens if they are late.

Limit revisions in writing, for instance "two rounds of consolidated feedback per design phase". Consolidated feedback from one person is the single most effective way to keep a project on schedule.

Pricing that is easy to approve

Show the total price, the payment schedule, and what each payment triggers. Itemising by phase is usually better than a single number, because it helps the client see where the value is and lets them adjust scope rather than negotiate your rate.

Include an expiry date, such as "valid for 30 days", so prices and availability are not held open indefinitely.

Next steps

End with one clear action: sign here, pay the deposit, book a kickoff call. A proposal without a next step tends to sit unanswered in an inbox.