Good content can still lose in a bad layout. If a reader can't find the price, can't tell where the plan starts or gives up halfway through a wall of text, the work underneath never gets its chance. A clear business proposal layout gives every reader a path through the document, even the ones with five minutes to spare.
Start with the order
Here's the order we'd use for most big deals. A cover with the client's name and the outcome. An executive summary on one page. The client's situation, in their words. The plan. The timeline. The price, with options if you have them. Proof, placed next to the claims it backs up. The team. Terms and next steps. Appendices for everything else.
That order follows the questions a buyer asks, in roughly the order they ask them.
One idea per page
Each page or screen should do one job. A page that covers the timeline, the team and three risks at once makes the reader do the sorting. Split it up. More pages that each say one thing read faster than fewer pages that say five.
Headlines that say something
Section titles like "Our Approach" and "Timeline" tell the reader what kind of content is coming. Headlines that state the point tell them what you're saying. "Live in six weeks, with no downtime" is a headline someone remembers. Keep the section label small and the point big.
Make the price easy to find
Readers go to the price early. Put it where they expect it, give it a page of its own and link to it from the summary. Our guide to presenting pricing in a proposal covers how to frame it.
Use visuals that carry information
A timeline drawn as a timeline. A rollout drawn as phases. A comparison laid out as a simple table. Visuals earn their place when they explain something faster than words would. Stock photos of handshakes don't explain anything.
Give the type room
Big, readable type. Generous margins. Short paragraphs. Two typefaces at most. A single column on a phone. None of this is fancy, and all of it makes a long document feel shorter.
Build for how it'll be read
The same proposal gets read on a laptop by your champion, on a phone by an executive and on paper by procurement. A live web proposal with a matching PDF covers all three. The web version lets readers jump to the section they care about, and the PDF keeps the same order for the file.
A business proposal layout, page by page
Here's how that order plays out on a typical big deal, using a made-up software rollout.
The cover shows the client's name and one line on the outcome, like "Every site on one system by June." The summary page states the problem, the plan, the price and the next step. The situation page uses the client's own words from discovery. The plan runs three or four pages, one per phase, each with a simple diagram. The timeline gets a page to itself. Pricing gets a page with the options side by side. Proof sits inside the plan pages, next to the claims. The team page shows the four people the client will work with. The last page covers terms and the date to sign. Everything else, from the full service agreement to security documents, goes in the appendix.
A finance reader can go from the summary straight to pricing. An operations reader can go straight to the plan. Nobody has to read the whole thing to find their part. That's the same idea behind writing for a B2B buying committee.
Common layout problems we see
The most common one is a proposal that follows the seller's org chart. A section from sales, a section from product, a section from support, each in a different voice. The buyer has to stitch it together.
The second is dense pages. Full-width paragraphs in small type, with no headings to break them up. People skip them.
The third is a price spread across several places, with a setup fee in one section and a monthly fee in another. Pull it into one place.
Layout for the web version and the PDF
The order stays the same in both versions. What changes is how a reader moves through it. In a web proposal, a short menu lets each reader jump to their section, and the summary links straight to pricing and the plan. Sections can open and close, so long detail stays out of the way until someone wants it. Diagrams can be interactive, like a timeline that shows each phase when you tap it.
The PDF is the version that gets printed, filed and forwarded to procurement, so it has to work on its own. Use page numbers, a short table of contents and the same section names as the web version. That way, when someone in a meeting says "the pricing page," everyone finds the same thing in whichever version they opened.
Questions we hear about proposal layout
How long should a business proposal be?
Long enough to answer every reader's questions, and no longer. Use the appendix for detail only some readers need, and keep the main proposal tight.
Should a proposal be portrait or landscape?
For a PDF that'll be printed or read on a laptop, either works. Landscape suits diagrams and side-by-side pricing. A web proposal should adapt to the screen, so a phone gets a single column.
The short version
Follow the buyer's questions in order. One idea per page, headlines that make a point, a price that's easy to find and visuals that explain something. Then make sure it reads well on every screen it'll be opened on.
If you want a layout built around one big deal, see the work or start a proposal.
