Scope Letter

What should a web design proposal include?

September 27, 2026 · Scope Letter

What should a web design proposal include?

A web design proposal should include the problem the client is trying to solve, the scope of work, the deliverables, the timeline, the price, the terms, and the next step. If you leave out any of those pieces, the client has to guess what they are buying, and guesswork slows decisions.

The shortest useful answer is this: your proposal needs enough detail to let a client compare options, understand your process, and approve the work without a lot of back-and-forth. Proposify’s web design template, for example, uses sections for an overview, scope of services, timeframe, pricing, terms, and sign-off. HoneyBook and Indy both show proposals as part of a larger client workflow that includes contracts, payments, and files, which is a good reminder that a proposal is not just a PDF. It is a decision document. Proposify, HoneyBook pricing, Indy pricing.

Why this question matters

Freelance web designers usually do not lose projects because they cannot design. They lose them because the proposal is vague.

A vague proposal creates avoidable questions:

If the proposal does not answer those questions, the client often delays, asks for revisions, or compares you on price alone.

The sections a web design proposal should include

1. A short summary of the client’s goal

Start by showing that you understood the project.

Write 3–5 sentences that say:

Example:

The current site is hard to update, the homepage does not make the offer clear, and the contact flow is not helping leads take the next step. This project will replace the old site with a cleaner brochure site that explains the service, builds trust, and makes inquiries easier.

This is not fluff. It tells the client you listened and gives the rest of the proposal context.

2. The scope of work

This is the most important section.

List the work in plain language. Be specific enough that someone could tell whether a request is in scope or out of scope.

A good scope section often includes:

Bad example:

Better example:

That version is easier to price and easier to approve.

3. Deliverables

Scope and deliverables are related, but not the same.

The scope says what work you will do. The deliverables say what the client will receive at the end.

Examples of deliverables:

If you hand off files, say so. If you only deliver the live site, say that instead. Clients should not have to ask what they can keep.

4. Timeline and milestones

A proposal should show how the project will move.

Use milestones such as:

You do not need a minute-by-minute schedule. You do need enough structure for the client to understand when decisions are due and what happens first.

Example:

If you know the client’s responsiveness affects timing, say that.

5. Price and payment terms

Do not hide the price in a paragraph.

Make the investment easy to find and easy to understand.

Include:

If you charge by phase, show each phase separately. If you offer optional add-ons, list them separately so the client can see the base project first.

Example:

Then state the payment schedule:

That gives the client a clear path from approval to payment.

6. Assumptions and exclusions

This section prevents scope creep.

Include what is not included, such as:

You do not need to sound defensive. Just be clear.

Example:

This proposal does not include copywriting, photo sourcing, or post-launch maintenance. Those services can be added if needed.

7. Revision policy

Clients need to know how feedback works.

State:

Example:

Two rounds of revisions are included for the homepage design. Additional rounds or new page requests will be quoted separately.

That line alone can save a lot of confusion later.

8. Terms and responsibilities

This is where you define the working relationship.

Include the basics:

You do not need to turn the proposal into a legal brief. But you do need enough terms to keep the project moving.

9. Proof or relevant examples

A short proposal is stronger when it includes a sample of past work, a process note, or a brief explanation of why your approach fits the client.

You do not need a long portfolio section.

A few lines can do the job:

Keep it relevant. A client reviewing a redesign proposal does not need to see every type of project you have ever done.

10. Clear next step

End with one action.

Examples:

If the client has to wonder what happens next, the proposal is not finished.

A simple order that works

If you want a straightforward structure, use this order:

  1. Client goal summary
  2. Why you are a fit
  3. Scope of work
  4. Deliverables
  5. Timeline
  6. Price
  7. Terms and exclusions
  8. Next step

That order moves from understanding the problem to approving the work.

What not to include

A web design proposal should not try to do everything.

Leave out:

The goal is clarity, not length.

A practical checklist before you send it

Before you send a proposal, check whether it answers these questions:

If the answer to any of those is unclear, revise the proposal before it goes out.

Sources and useful references

A better proposal is a clearer decision

For freelance web designers, the best proposal is the one that makes the client’s decision easier. That means fewer vague promises, more specifics, and one clean path to approval.

If you want help turning that structure into a reusable system, the next step is the Web Design Proposal Kit from Scope Letter.

Proposal systems for freelance web designersSee what we offer