One page proposal: how to write one that actually gets read

You can spend an hour polishing a one page proposal, hit send, and watch it sink. I've done it more times than I'd like. The problem usually isn't the idea. It's that the page asks the buyer to do too much work, too fast.

A good one page proposal isn't a shrunken version of a long one. It's a different object. The reader needs the problem, the fix, the scope, the price and the next move in a single pass, which means the format lives or dies on layout and persuasion, not just brevity.

A one page proposal is a decision aid, not a summary

I've watched teams compress a ten-page deck into one PDF, send it with a hopeful subject line, then wait while the inbox stays quiet. The sender thinks they've saved the buyer time. The buyer opens a dense sheet that hides the ask, buries the value and makes the decision feel harder than it should.

A professional woman viewing a project proposal PDF file on her laptop screen in a modern office.

these sample sales proposals

what a one-pager is

One page sits at the very short end of the proposal spectrum. The usual rule of thumb, set out in this guide to proposal length, is that informal proposals stay at one or two pages, standard sales proposals run five to ten, and technical or government bids go well beyond that. The short format works when you already understand the buyer's needs, the scope is narrow, or the goal is quick clarity rather than exhaustive detail. If you're not sure what the format is for, what a one-pager is is the definition, and these sample sales proposals show the one-page version next to the longer ones.

A lot of one-pagers fail because they try to look complete instead of decisive. The reader ends up with something polite but not useful, and the deal drifts into vague replies and next-quarter purgatory.

If the page doesn't make the decision feel easier, it's too busy, even if it fits on one page.

The five blocks it actually needs

A one page proposal has to do the work of a longer document without looking cramped. That only happens if every block earns its place and the reader can move through the page without guessing what comes next. I write these as if the buyer is skimming it in a meeting, because they usually are.

Start with their problem, not your praise

The first block names the buyer's problem in plain language. Its job is to make the reader feel seen quickly and to show the page is about their situation, not your company's biography. The trap is vague benefits. "Improve efficiency" tells me nothing.

Something like "your sales team is sending proposals that take too long to review and don't show the next step" is specific enough to anchor the rest of the page. It's also the block you usually write last, because once the rest is clear the opening gets much sharper.

Put the solution in one pass

The second block says what you'll do. It has to answer what it is, why it matters and what result it creates without turning into a narrative. The trap is stuffing in every capability you have rather than the approach for this deal.

For a services engagement it might read "we'll redesign the proposal process so your team sends a shorter document with clear scope, cleaner pricing and a recorded explanation attached". That's an offer, not a brochure.

Scope, deliverables, timeline, investment

These do different jobs even when they sit together. Scope says what's in. Deliverables say what the buyer gets. Timeline says when it lands. Investment says what it costs and how the deal moves forward. The trap is fuzzy scope, because fuzzy scope becomes scope creep before the ink dries.

Block	Its job	Where it usually fails
Problem statement	Frames the buyer's pain in their words	Sounds generic or self-focused
Proposed solution	States the approach and the outcome	Lists services without a clear offer
Scope and deliverables	Defines what's included	Leaves room for scope creep
Timeline or milestones	Shows when work happens	A vague duration with no checkpoints
Investment and next step	Makes acceptance easy	Hides pricing or buries the close

Close with the ask, not a shrug

The final block tells the buyer exactly what to do next. If you want the meeting, the signature or the reply, say so. Don't bury it under qualifications or tuck it into a sentence that reads like an apology.

The first and last blocks matter most. Write them last, place them first and last on the page, and make sure they stand alone if someone only reads the top and bottom before a call.

Design it to read in thirty seconds

The strongest one page proposals I've seen look almost boring at first glance. That's a compliment. The page is doing its job without making the reader work for basic orientation.

Whitespace isn't decoration. Use proper margins, keep to a single column or a clean two-column split, and don't let blocks bleed into the edge. If the page feels squeezed, the reader assumes the thinking is squeezed too. Stick to three text sizes, one accent colour and one typeface family, and the page gets a calm rhythm that moves the eye towards the lines that matter.

None of this is decoration. Reducing the reader's cognitive load is the whole job, and the standard UX design principles apply to a page just as they do to a screen.

The most decision-critical line belongs in the top third. That might be the headline outcome, the price or the next step, depending on the deal. If the buyer has to hunt for the ask, you've lost half the battle already.

The two mistakes I see most are easy to spot. A logo bar across the top so the actual content starts halfway down, and pricing buried under a wall of qualifications so the reader has to work before they can judge the offer.

Then preview it properly. Save it as a PDF, open it in a viewer, look at it on a phone. If you can't name the ask in thirty seconds, the layout has failed, however good the words are.

Adding a walkthrough without breaking the format

A static PDF can do the job. A short recorded walkthrough often turns it into something the buyer actually spends time with. The trick is adding your voice without turning the proposal into a second deck. The page still has to carry the sale on its own.

The cleanest setup is a short screen walkthrough that follows the page top to bottom. Open with the problem, move through the solution, finish on pricing and the next step. Keep it conversational and strip the jargon. If it sounds like someone reading a pitch deck aloud, people stop watching.

The PDF stays the source of truth. The video gives context for the parts that need it. That pairing is what LiveDocument does: the walkthrough sits on the PDF or image itself, shared as one link, with clickable highlights that jump the video to the block the reader is looking at. It's not a proposal builder and it won't write the page for you, so everything above is still your job. If you want the mechanics, adding video to a PDF goes through the options, including the ones that aren't us.

Whatever tool you use, make the video easy to ignore. The buyer should be able to skip it, understand the proposal from the page alone, and come back to it if they want more context.

adding video to a PDF

LiveDocument

When one page hurts more than it helps

Short doesn't always mean respectful. Sometimes it means undercooked. A cramped one page proposal damages credibility when the buyer needs proof, context or process rather than a neat summary.

Enterprise work is the obvious case. If procurement, security review and legal redlines are part of the buying process, a single page feels thin unless it's clearly the front door to a fuller pack. Technical implementations are another bad fit when the buyer needs architecture diagrams, integration notes or compliance detail. Relationship-heavy work can suffer too: agency retainers and joint ventures often need a document that signals serious thought, not speed.

Use the short format when the buyer already knows the problem and needs the delta. Skip it when context has to be shown rather than asserted.

If the proposal has to persuade a stranger, explain a system or survive multiple reviewers, compressing it usually weakens the case. Known buyer, narrow scope, fast yes or no, the one-pager still has teeth.

Follow the behaviour, not the calendar

A one page proposal that gets opened but not finished is still a miss. The format only works when you pair it with some idea of what happened after you sent it.

If you're using a tracked link, let the behaviour shape the follow-up. Time on the pricing block may indicate the commercial fit is being weighed up, so answer the likely question about what's included. One open and no return may mean it never really landed, so confirm they can get at it before you send anything else. Neither signal tells you why, so use it to choose the question rather than to guess the answer.

Follow-up needs to happen while the page is fresh, and the cadence is its own subject. How to follow up after sending a proposal has the full version. Then compare the one-pager's acceptance rate, time to decision and revision count against your longer formats, and if it underperforms in a particular deal type, retire it there.

A short proposal earns its simplicity with evidence, not hope.

How to follow up after sending a proposal

Frequently asked questions

How long should a one page proposal be?

One page, genuinely, at a readable size. If you're shrinking the font to make it fit, you've got a two-page proposal pretending. Cut a block rather than the type size.

Should a one page proposal include pricing?

Yes. Hiding the price on a document whose whole point is a fast decision just adds a meeting. Put the investment in the lower third with the next step beside it, and add a line on what's excluded so the number doesn't get misread.

I built LiveDocument because I got tired of sending proposals that were read once, badly, on a phone. If that's a feeling you know, it's at livedocument.com.