A Proposal Is an Argument, Not a Document
If you could swap the client's name on your last proposal and it would still make sense, you wrote a quote, not a proposal.
A funded health-tech startup once shared two proposals side by side from firms competing for the same engagement. One opened with a paragraph about the agency's history and awards. The other opened with a single sentence restating, almost word for word, something the founder had said in their first call — a specific worry about credibility with clinical partners that they hadn't expected a design firm to have picked up on. The founder didn't finish reading the first proposal. The second one is the one they signed.
Nothing else about the two documents was radically different. The difference was what each one proved about whether the conversation before it had actually mattered.
The test that exposes most proposals
Here's a fast way to check whether a proposal is actually doing its job: could the client's name be swapped for a different client's name, in a different industry, and would the document still basically make sense? If yes, it isn't a proposal — it's a quote with a cover page. It describes services and prices, the same way it would for anyone.
Most proposals fail this test, not because the firms writing them are careless, but because a proposal is usually treated as the last administrative step before work begins — a summary of what was discussed, formatted nicely. That framing produces documents that are accurate and forgettable in equal measure.
What an argument actually does
An argument opens differently: it restates the specific gap the client described, in language close to how they described it, before anything else. It explains what that gap actually costs — tied to whatever is genuinely at stake for that client, whether that's a raise, a market entry, or a competitive threat — before proposing anything. Only after establishing what's true and what it costs does it lay out an approach, and it explains explicitly why that approach fits this situation rather than a cheaper, more generic alternative the client might otherwise default to.
The investment appears only after all of that has been established — not because pricing should be hidden, but because a number means something different once the size of the problem has been made concrete, versus being presented as a line item against an abstract scope of work.
Why this decides more than the pitch does
A pitch happens in a room, live, with the benefit of tone, body language, and the ability to read the moment. A proposal happens alone, on a screen, days later, often shared internally with people who weren't in the original conversation at all. It has to do all the persuasive work the pitch did, without any of the advantages. If the proposal doesn't carry the same specificity and conviction as the room did, whatever momentum the pitch built starts leaking out immediately.
This matters most in exactly the situations where the stakes are highest — a proposal that will get forwarded to a board, a proposal competing directly against two or three others that all showed up in the same room. The proposal isn't a recap of the pitch. For everyone who wasn't in that room, the proposal is the entire pitch.
What to check before sending the next one
Before a proposal goes out, it's worth asking one question honestly: does the first paragraph prove we understood something specific about this client, or does it prove we know how to write a proposal? Only one of those actually reads as trustworthy to someone deciding whether to hand over a meaningful amount of money and trust.
