Proposal Skeleton That Is Shorter

Most proposals are structured as an argument that you are qualified. That argument was already settled — they asked you for a proposal, which means somewhere in the previous conversation they decided you were plausible.

What is still open is whether to spend the money now, and whether the person who wants to spend it can defend that choice to somebody who was never in the room.

Why this exists

A proposal’s real job is to be forwardable. It gets sent to a manager, a finance partner, a committee — people with no memory of your call and no patience for your methodology. If page one does not stand on its own for a reader who was in none of the conversations, the document has failed, however good pages two through nine are.

So the test is mechanical, and you can run it in a minute. Hand page one to someone who knows nothing about the work. If they cannot tell you what the problem is, what will be different, what it costs and when it starts, rewrite it. This catches the most common defect immediately: a first page that opens by summarizing the company you are writing to, which tells the forwarded reader nothing they do not already know and tells the sender you had a slow start.

Length is a signal, not a virtue. A short proposal after a long conversation reads as clarity. A short proposal after a thin conversation reads as carelessness, and the fix for that is more discovery, not more pages.

How to use it

Start with the problem in their words. Quote the sentence they actually said, with the date beside it. Not paraphrased into your framing — the literal sentence. If you cannot quote them, you have not listened closely enough to write the proposal yet, and the right move is to ask for another call rather than write around the gap.

Then state what will be true when it is done, in terms you could photograph, count or switch off. “Improved visibility” fails that test. “The Monday report is produced without anyone opening a spreadsheet” passes, and it also tells the forwarded reader what they are buying.

Put the exclusions on page one, beside the price. Three to five lines, and they should be the things this particular reader would otherwise assume were included. A proposal with no exclusions reads as one that has not been thought about, and it guarantees the conversation happens later, when it is expensive.

If you offer options, make them differ in scope, not in polish. Three tiers of the same deliverable at three prices is a pricing device, and anyone who has read a few proposals recognizes it as one. Two usually works better: the smallest version that is genuinely useful, with an explicit line about what it does not do, and the full version with what it adds.

Put the section about you last, and hold it to a paragraph. Cut it entirely when the conversation has already covered it.

Where it goes wrong

This shape loses badly against a scored request for proposal. If there is a rubric awarding points for methodology, team biographies and references, write to the rubric, in the rubric’s order, using the rubric’s words. Elegance earns nothing there. Work out which document you are writing before you start writing it.

It is also wrong for a first approach to a large organization where nobody knows who you are yet. There, evidence of having done the work before is load-bearing, and two pages reads as thin. The structure still holds; the section about you simply moves up and grows.

And no proposal repairs a bad fit. If you are writing paragraphs to make the work sound like something you would want to do, the honest version of this document is a short note declining it and suggesting who else to ask.