A web design proposal should be short enough to read in one sitting — usually 2 to 5 pages. A small brochure site or landing page proposal can run 2 pages. A multi-page redesign or Shopify build with multiple deliverables can run 4 to 5 pages. If a proposal runs longer than that, it is usually padded with generic agency boilerplate instead of specifics about the client's project. Length is not the goal; every page should either answer a question the client already has or remove a reason to say no.
The short answer: 2–5 pages, depending on project size
Use this as a starting range, then adjust for the actual scope in front of you:
- 1 page — a single landing page, a small fix, or a repeat client who already knows how you work.
- 2–3 pages — a standard 5–8 page brochure site or a Shopify storefront with a stock theme.
- 4–5 pages — a redesign with content migration, a custom Shopify build, or a project with more than one phase.
Anything past 5 pages almost never gets read in full. A client scanning a proposal on their phone between meetings will skim the price and skip the rest if the document looks like a wall of text.
What determines length: scope, not formality
The proposal's length should track the scope, not how "official" you want it to look. A proposal for a 5-page brochure site does not need a table of contents, a company history section, or a page of boilerplate about your process. Those additions make the document feel padded rather than serious.
The right way to size a proposal is to write the scope of work first, then let the proposal length follow from it. If the scope has three deliverables and one round of revisions, the proposal should be short enough to reflect that. Our guide on how to write a scope of work for a website project covers how to break a project into deliverables that map directly onto proposal sections — once that list exists, the proposal mostly writes itself.
A one-page proposal for small, well-defined projects
For small, well-scoped work, one page is enough if it covers:
- What you're building (one sentence)
- What's included, as a short bulleted list
- Timeline (start date, delivery date)
- Price and payment terms
- What happens next (a signature line or a link to accept)
Example wording for a one-page landing page proposal:
Project: One landing page for [Client]'s spring product launch, built in Webflow, live by April 3.
Includes: One page (hero, three feature sections, testimonial block, contact form), mobile-responsive layout, one round of revisions, and a 30-minute walkthrough call before handoff.
Timeline: Draft delivered April 1, final files April 3.
Price: $1,800, due 50% to start and 50% on delivery.
Next step: Reply "approved" to this email or sign below, and I'll send the deposit invoice.
That is five sentences and a price line. Nothing about the company's history, no stock photography, no "why choose us" section. Clients approve proposals like this faster because there is nothing to get lost in.
A 4–5 page proposal for redesigns and multi-phase builds
Bigger projects genuinely need more pages, but the extra length should go to sections a small proposal doesn't need: a phased timeline, a breakdown of what's being migrated versus rebuilt, and pricing broken out by phase so the client can see where the budget goes. Our post on how to price a website redesign proposal goes through how to structure that phase-by-phase pricing so a longer proposal still reads clearly.
A 4–5 page redesign proposal typically breaks down as:
- Page 1: project summary and goals
- Page 2: scope, broken into phases (discovery, design, build, launch)
- Page 3: what's included per phase, plus what's explicitly excluded
- Page 4: timeline and pricing table
- Page 5: terms, next steps, signature
That structure gives the client enough detail to justify a larger budget internally, without turning the document into a sales brochure.
What to cut when a proposal is running long
If a draft is pushing past 5 pages, cut in this order:
- Agency bio and "our process" sections — the client is hiring you for this project, not reading your company history.
- Generic testimonials with no relevance to this project type — if you keep testimonials, use one that's specific to the same kind of work.
- Repeated scope language — if the same deliverable is described in the summary, the scope section, and the pricing table, say it once and reference it.
- Stock imagery and design flourishes — they add pages without adding information.
For the exact section order a lean proposal should follow, see our web design proposal template — it lays out which sections are load-bearing and which are optional.
What to add if a short proposal isn't converting
If a short proposal isn't landing, the fix is rarely "add more pages." It's usually one of these:
- The price has no context — add a one-line rationale ("priced for a 3-week turnaround with two revision rounds") rather than a bare number.
- The scope boundary is unclear — spell out what's excluded, not just what's included, so the client isn't guessing.
- There's no clear next step — end with exactly one action ("reply to approve" or "sign below"), not three options.
Adding clarity is different from adding pages. A proposal can go from 2 pages to 3 and convert better if that third page is a clean pricing table; it will convert worse if that third page is a paragraph about your design philosophy.
Checklist: sizing your next proposal
- Wrote the scope of work before drafting the proposal
- Matched proposal length to project size (1 page small, 4–5 pages for redesigns/multi-phase)
- Cut agency bio, generic testimonials, and repeated scope language
- Priced with a one-line rationale, not a bare number
- Ended with exactly one next step
If you'd rather start from a proposal that's already sized correctly for each project type, The Web Design Proposal Kit ($29) includes templates built to these lengths so you're not guessing what to cut.