Proposal format: deciding length and section order

How long a proposal should be

The working answer is four to twelve pages of actual content. Below four, the document is doing quote work and probably should be a quote. Our guide on proposal vs. quote walks where that line sits. Above twelve, the writer is using length as a substitute for confidence in the case.

What counts as a "page" is worth pinning down. The cover page is a label; the "about us" appendix is back matter. The four-to-twelve range is about pages of substantive content.

Practitioner writing on this tilts compact. Kevin Brown at MIGHTY ALLY argues that "a page per section is plenty" and notes that "nobody has time to read 30 pages". Jonathan Stark, writing on the proposal shape he uses with consulting clients, describes a format where the cover letter is "always less than one page" and the project overview is "always less than one page". Long proposals feel thorough to the writer; they feel exhausting to the reader.

Section order is a question about what the client reads first

The conventional format puts the proposal executive summary first and the pricing section last. The convention is wrong, and applying it everywhere is what makes every "proposal format" page read the same.

The useful question is not "what is the canonical order." It is what does this client open to first.

Imagine a wedding photographer sending the same client a second-summer portrait proposal. The client knows the photographer's work; the client is opening the proposal to see if the price is in their range and what is included. A ten-page document that opens with a four-paragraph executive summary about creative vision is a format choice that fights the moment. The client wants the price on the first scroll and the deliverables underneath. A three-page document with pricing in the first half and a short scope of what is in and out is the right shape.

A brand studio writing a first proposal to a series-A startup that has never bought brand design is a different shape entirely. The client does not know what brand design costs, does not know what they are buying, and does not know whether the studio understands the problem. Leading with the pricing section is the wrong move because the client cannot evaluate the price without first understanding what is being proposed. The executive summary, framed as "what we think you are actually trying to solve," lands first, with the scope underneath. The pricing section sits in the middle, where the case has been made and the price can be read in context. For a solicited brief, the order is not the writer's to set: the brief states the sequence, and the format follows it. The solicited proposal template mirrors the client's structure; the unsolicited proposal template is the writer's to define.

Blair Enns, writing on the price conversation in proposals, makes the related point that the prospect "will not flip to the last page if he already knows what the price is." If the price has been discussed in the conversation that produced the proposal, the proposal's job is to confirm it, not to defer it. Brennan Dunn, writing on proposal craft, argues that listing requirements, deliverables, timelines, and budgets are "not solutions", and elsewhere sharpens it: the proposal should "focus on what needs to be achieved". The implication for section order is that the document should land on the problem-and-outcome page before the deliverables list, except where the client has already accepted the problem and is opening to compare prices.

The working order check for the proposal in front of you depends on who the client is, what the deal shape is, and what they will open to. A retainer consulting proposal that runs to the same client every quarter for the same scope can come in at three pages: a one-paragraph framing of what is renewing, the pricing for the next quarter, the scope confirmation, and the next-step block. A bespoke first-time deal runs longer because the case has to be made from scratch: problem framing first, scope and deliverables underneath, pricing in the middle. In each case the seven-section skeleton is still there; what changes is the order and the page allocation.

The proposal editor in ProposalKit.io ships with an examples drawer of full industry presets, and the section orders vary by industry on purpose. They are starting points the writer adjusts. The industry-specific format questions, from how to write a marketing proposal to how to write a web development proposal or a graphic design proposal, carry the same two decisions; the defaults shift by context and deal type.

The pricing section is the load-bearing page, regardless of where it sits

Wherever the pricing section sits in the section order, it is the page the format choice has to support. The format question for it is whether it can stand alone, scanned in twenty seconds, by a reader who hasn't read the rest of the document. That means structurally simple: a pricing table with line items and a total carries the work better than three pages of prose explaining the calculation. The price is what the price is. The scope of what is in and out for that price is named, not buried. Optional add-ons are named as optional. Jonathan Stark, writing on how he prices fixed-fee work, puts it plainly: "my proposal is a fixed-price quote".

The pricing decision itself, whether to charge fixed fee or hourly, how to package, how to think about retainers and value-based pricing, belongs to our guide on how to price a creative project proposal. Once the client accepts, the next artifact is the client contract.