Most B2B proposals get sent, opened once, and forgotten. The book gives a three-step architecture for proposals that get returned-to and signed.1 The architecture treats the proposal as part of the sales conversation rather than as a separate document — it's engineered to make the prospect re-live what was surfaced in the engagement stage, and to make the operator's solution the natural next step rather than a separate decision.
The three rules2:
Rule 1: Never give a proposal without understanding their problems and their budget. "Live by this; there are no exceptions to this rule, even if you have a prospect who says, 'Can you just send me over a proposal with your pricing in it?'" Premature proposals are sent to prospects who haven't yet articulated their full situation; the proposal lands on insufficient context and produces no commitment. The corrective: when a prospect asks for a proposal too early, say "I'd be open to putting together a proposal for you. Now, to be frank, I'm not quite sure we could even help you yet. Could I ask a few questions about your situation to be able to put something together for you that might be useful? Would that be appropriate?"
Rule 2: Proposals should lay out 2-3 of the problems they told you about during engagement, plus 2-3 objectives they want to accomplish. The proposal restates the prospect's articulated problems and goals before introducing the operator's solution. The restating produces re-living of the pain (which keeps urgency alive) and re-articulating of the objectives (which keeps the operator's solution calibrated to actual goals).
Rule 3: Value of solving the problem must be at least 10× the cost of the offer. "For a company solving a problem that is costing them $15 million a year in lost revenue, a $250,000 solution will seem quite small to them if you are positioning it correctly." The 10× minimum is the threshold below which proposals don't get signed because the value-to-cost ratio isn't compelling enough.
The book adds a structural recommendation about proposal pricing3: every proposal should offer three options, not one.
The mechanism: the premium option's primary purpose isn't to be selected (though it sometimes is). Its primary purpose is to make the core offering look like a bargain by comparison. The premium-anchor produces favorable evaluation of the middle option even when the prospect was budget-resistant before the comparison.
This is one of the most-validated findings in pricing-research (anchoring effects, decoy effect — Ariely 2008). The book operationalizes the research into a specific proposal-structure.
The book adds a practical recommendation4: the proposal itself should be signable — function as a contract or agreement — so the prospect can move forward immediately rather than waiting for a separately-drafted contract.
The mechanism: each additional step between intent-to-buy and signed-commitment adds attrition. If the prospect has to wait a week for a contract, the deal can erode during the wait. If the proposal is signable, the commitment can happen the moment the prospect decides.
The book is explicit: "Remember, the more steps you add to the sales process, the more chance of it falling apart."
Another structural rule5: "Never, ever email the proposal over to the prospect before going through the presentation because if they don't like something in it, you are DOA. Why? Because you're not there to clarify or help them overcome any concerns!"
Email proposals get evaluated unilaterally; the operator can't address concerns in real time. The corrective: go over the proposal face-to-face (or Zoom or phone) so the operator can respond to questions as they arise. The proposal is presented, not delivered.
The architecture combines two principles: (1) proposals work best when they restate the prospect's own articulation (self-persuasion mechanism), and (2) the proposal-evaluation moment is itself part of the sales conversation rather than a separate step.
The 10× value-to-cost minimum is the operational threshold for the first principle to work — when value-to-cost ratio is below 10×, even well-restated proposals don't produce commitment because the math isn't compelling. When ratio is above 10×, the well-restated proposal produces commitment because the case is overwhelming.
Pairs with Three-Pillar Presentation Formula (the presentation architecture that delivers the proposal), Checking-for-Agreement Questions (the technique used throughout the proposal-presentation), and Three-Option Pricing Tier (the detailed sub-doctrine on the three-option mechanism).
A B2B SaaS operator preparing a proposal for a $250K annual contract. Old-model proposal: 30-page document delivered by email, opens with company-overview, includes feature-list and pricing. Prospect opens it once, scans the price, files it as "to-think-about." Deal stalls.
Three-step architecture proposal: 6-page document. Page 1 restates the prospect's 3 articulated problems (in their own language, with their numbers) and 3 articulated objectives. Pages 2-3 describe the solution as it specifically maps to those problems and objectives. Pages 4-5 provide the three-option pricing (basic / core / premium). Page 6 is the signable agreement. Operator schedules a 30-minute Zoom to walk through it together.
During the Zoom, the operator opens the document and walks through page 1 first — letting the prospect re-engage with their own articulated problems before any solution-content. By the time they get to pages 2-3, the solution is landing on re-activated emotional content. The pricing on pages 4-5 lands with the premium-anchor doing its work. Page 6 makes the commitment a single action.
Same product, same value-content, same price-point. Different architecture. The first version sits in inbox; the second gets signed.
You audit your last five proposals. For each, you ask: did it restate the prospect's articulated problems? Did the value-to-cost ratio reach 10×? Did you walk through it live or email it? Did it have three options? Was it signable?
Most operators discover they're missing 3-5 of these features per proposal. You commit for the next month to one discipline: every new proposal hits all five structural features. The first few feel uncomfortable because the new architecture takes more pre-call preparation. By proposal four or five, the architecture is your default and your close rate on proposal-stage deals has moved measurably.
The 10× value-to-cost threshold is practitioner-derived and roughly calibrated to enterprise B2B contexts. The threshold likely varies by industry and deal-shape. The three-option pricing recommendation has strong empirical support from behavioral-economics research (decoy effect, anchoring).
A tension: small-deal contexts (under $5K) may not need this much proposal-architecture. The investment in three-option pricing structures and live-walkthroughs is disproportionate for small deals. The book treats the architecture as universal; in practice it scales with deal-size.
Joint Acuff/Miner; the structural architecture reads more Acuff (consultancy/enterprise background). Cross-source with Hormozi: Hormozi's framing in Hypothetical Perfect Program Close uses different pricing-architecture (anti-guarantee takeaway rather than three-option). The two methodologies diverge on pricing-presentation; both converge on never-email-proposals.
The plain-sentence version: proposal-architecture as influence-mechanism appears across consultative-services professions (legal proposals, architecture proposals, design proposals). The methodology's specific rules are sales-domain instances of broader patterns.
Behavioral Mechanics — Anchoring and Decoy Effect in Pricing: Ariely's Predictably Irrational (2008) decoy-effect research provides the empirical foundation for three-option pricing. The methodology's structural recommendation is one of the cleanest commercial applications of the research.
Psychology — Restating as Therapeutic Confirmation: clinical literature on the value of restating-the-client's-articulation as a commitment-building mechanism. The proposal architecture's first rule (restate the problems and objectives) is the sales-domain application.
Creative Practice — Document Design and Reader Engagement: business-writing and document-design literature on engineering documents for engagement rather than passive-reception. The architecture's specific structural recommendations are one operationalization.
Sharpest Implication. Most operators treat proposals as documents to send rather than as conversational moves to engineer. The architecture inverts this — proposals become structured continuations of the sales conversation rather than separate decisions. The training investment is small (rewrite one proposal-template); the return is substantial improvement in proposal-stage conversion.
Generative Questions.