Section 1
How executives actually read a proposal
An executive does not read your proposal front to back like a report card. They skim for the answer, decide whether the answer is plausible, and only then read the parts that support or threaten it. This is not laziness. It is triage, and every senior buyer does it. The military formalized the same habit as BLUF, "bottom line up front," precisely because leaders reading under time pressure need the conclusion before the context . When your recommendation sits on page five, you have forced a triage reader to do archaeology. Some buyers will dig. Most will skim, fail to find the point quickly, and file the proposal under "read later," which is where proposals go to die. The structure you chose to signal thoroughness instead signals that you have not done the buyer's thinking for them. A proposal is not a place to demonstrate effort. It is a place to make a decision easy. Consider a boutique data-analytics firm proposing a $9,000-per-month retainer. The old structure opens with a company overview, a summary of the discovery call, and a description of the analytics landscape. The buyer, a VP with forty minutes between meetings, skims two pages, sees nothing that tells them what to decide, and moves on. The board-structured version opens: "We recommend a three-month analytics retainer at $9,000 per month to fix the attribution gap costing you an estimated 18% of paid-acquisition efficiency. Here is why, what it includes, and what happens if you wait." The VP now knows the decision in ten seconds and reads on to test it.
Section 2
The Minto Pyramid, translated for a proposal
Barbara Minto, the first female MBA McKinsey hired, built the Pyramid Principle around one move: start with your answer, then support it with a small number of key arguments, each backed by evidence . The structure is a pyramid because the single recommendation sits at the top, three-ish supporting arguments sit below it, and the detailed proof sits below those. A reader can stop at any level and still have a coherent, complete-enough answer. Translated into a retainer proposal, the pyramid looks like this. The elegance is that this structure serves both reader types. The triage skimmer gets the answer and the three arguments and can decide. The thorough reader keeps going into the detail. A background-first proposal serves neither well, it makes the skimmer give up and the thorough reader wade.
Section 3
Writing the opening recommendation
The recommendation paragraph is the most important thing you will write, and it has four jobs, in order. It should name the specific move you recommend, the outcome it produces, the cost, and the cost of waiting. Four sentences, no throat-clearing. Here is the shape: "We recommend [specific engagement] to [close a specific gap], which we estimate is [costing X or blocking Y]. The engagement runs [duration and price]. The full rationale, scope, and proof are below. If this stays unaddressed through [their real deadline], the most likely outcome is [concrete consequence in their terms]." Notice what this does. It states the answer, ties it to the buyer's own stakes, prices it plainly, and names the cost of inaction, all before a single slide of background. The buyer who reads only this paragraph still knows exactly what you are proposing and why. Everything after it is defense of a claim the buyer has already seen, which is exactly how a board presentation works.
Section 4
The objection: "won't leading with price scare them off?"
The most common pushback is that opening with the recommendation, including the price, exposes the number before you have built value. The data cuts the other way. Gong's analysis found win rates are roughly 10% higher when pricing is discussed on the first call, and that the longer a rep waits to surface price, the lower the odds of winning . Buyers do not resent an early, clear number. They resent doing calculus to find one. The key is that leading with the recommendation is not leading with a naked price. It is leading with a priced recommendation tied to a quantified outcome. "$9,000 per month" lands badly on its own. "$9,000 per month to recover an estimated 18% of paid-acquisition efficiency" lands as a return calculation. The pyramid keeps the price and the value welded together at the top, which is precisely why it does not scare buyers, it frames them. The deeper mechanics of pricing conversations, and the phrases that quietly kill retainers, live in the ConvertOS playbook.
Section 5
When background still earns its place
The board-presentation rule is not a ban on context. It is a rule about sequence. Background still belongs in the proposal, it belongs after the recommendation, as support, not before it, as a warm-up. There is one honest exception. When a proposal has to survive being forwarded to someone who was not on the discovery call, a short "situation" framing near the top can orient that reader. Even then, it goes under the recommendation, not above it, and it stays to a few sentences. The failure mode to avoid is using background to hedge. Founders front-load context because stating the recommendation first feels exposed, there is nowhere to hide if the buyer disagrees. That exposure is the point. A recommendation you are willing to lead with is a recommendation you believe. A buyer can feel the difference between a firm that opens with a conviction and one that buries a suggestion under three pages of throat-clearing.
Section 6
The one-page test
Before you send any proposal, run this test. Cover everything below the first paragraph. Can a stranger read only that paragraph and correctly state what you are proposing, what it costs, and why it matters to the buyer? If yes, you have a board-structured proposal. If the answer requires reading further, your recommendation is buried and your best-qualified buyers, the busy ones, will never dig it out. A clean recommendation up front is also what makes a proposal easy to hand off into a systematized close instead of a document that stalls in an inbox.
Section 7
Key takeaways
• Executives triage-read: they skim for the answer, then read to test it. A recommendation buried under background is one most buyers never reach . • The Minto Pyramid works because a reader can stop at any level and still have a coherent answer, apex recommendation, three key arguments, then detail . • Lead with a priced recommendation tied to a quantified outcome. Gong found win rates roughly 10% higher when price is discussed early, so a clear early number helps rather than hurts . • Background belongs after the recommendation as support, never before it as a warm-up. Front-loading context usually means you are hedging. • Run the one-page test: if the first paragraph alone cannot convey what you propose, what it costs, and why, the recommendation is buried.