Section 1
Key takeaways
• The deal you lose isn't usually to a competitor. 40–60% of the average rep's pipeline dies to "no decision," and most of that is indecision and fear, not a rival vendor . • A forwardable case must make doing nothing feel expensive and doing something feel safe, because 56% of no-decision losses are pure indecision, not buyers who are happy with the status quo . • Brevity isn't dumbing the case down. It's the literal price of circulation: a typical B2B purchase runs through a buying team of about 10 people, and the document has to survive being forwarded to people you'll never meet . • Buyers reward a case framed around their goals, not your features. 86% of business buyers are more likely to buy when a company understands their goals, yet 59% say most reps never take the time to find out . • Strip the branding. A white page in plain black text, in the committee's own vocabulary, reads like internal advocacy. A polished vendor deck reads like bias.
Section 2
Why does "no decision" beat your best competitor?
Founders build the business case as if the contest is them versus an alternative vendor. So they over-index on differentiation: why we're better, faster, more proven. But the data says you're fighting the wrong opponent. 40–60% of the average salesperson's pipeline is lost to "no decision", not to competitors . The deal doesn't go to someone else. It goes nowhere. The buyer agrees you're good, agrees the problem is real, and then... stalls. Forecasting actively hides this: one CSO Insights dataset found 58% of forecasted deals end in no decision, and 71% of those had a firm close date logged in the CRM . These were deals reps swore were closing. They evaporated. Here's the part that should change how you write the document. Of those no-decision losses, the split isn't what you'd assume. Only 44% are genuine status-quo losses, buyers who looked at the change and decided they were fine as they are. The other 56% are pure indecision: buyers who wanted to move and froze . That finding comes from the Jolt Effect research, built on an analysis of more than 2.5 million sales conversations, so it's not a hunch, it's a pattern at scale. Read those two numbers together and the job of the page rewrites itself. You're not out-arguing a rival. For the 44%, you have to make the status quo feel expensive. For the 56%, you have to make the decision feel safe. A page that only stacks up value, more upside, more features, bigger ROI, speaks to neither. It adds reasons to want it without removing the reasons to freeze. If your stalled deals frustrate you, it's worth getting precise about why they stall; the discovery work in how to qualify out the deals that will never close is the upstream half of this same problem.
Section 3
The document isn't read by the person you sold
Picture the actual mechanics. You ran a strong call. Your champion is sold. Now they have to take what's in their head, and your deck, and get a budget holder they report to, plus two or three peers, to agree. You are not in that room. That room is crowded. A typical B2B purchase involves a buying team of about 10 people, and 86% of B2B purchases stall somewhere during the buying process . Ten people, each with their own read on risk, none of whom heard your pitch. Your champion becomes your proxy, and the only artifact that travels with them is the document. If that document needs them present to make sense, it doesn't travel. It sits in a tab until the quarter closes. This is why length is a strategic variable, not a stylistic one. Every slide you add raises the summarization tax your champion has to pay before they forward it. A one-pager has a tax of roughly zero: they forward it as-is. A 20-slide deck demands that your champion become a copywriter, distill your argument into three sentences in an email body, and stake their internal credibility on a summary you didn't write. Most won't. They'll say "let me find time to put something together", and that's where the deal goes to die. The mechanics of multi-stakeholder buying are the same problem ConvertOS frames as selling to the committee, not the contact; the one-pager is the artifact that makes that possible.
Section 4
Why the unbranded memo gets forwarded
There's a counterintuitive move here that operators miss. The instinct is to make the document look impressive, logo, brand colors, a designed cover. That instinct is working against you. Buyers don't circulate polished vendor decks internally, because branding signals bias. A CFO who receives a glossy seller-designed deck knows immediately it was built to sell them something, and discounts it accordingly. But a white page, in black text, written in the buying team's own vocabulary, reads like internal advocacy, like something a colleague wrote, not something a vendor sent. That's the document that gets forwarded, because forwarding it doesn't cost your champion any credibility. They're not passing along a sales asset; they're passing along their own reasoning, which you happened to draft for them. One head of go-to-market frames the test bluntly: "Assume that the CFO has no idea what this is and doesn't care what it is. Why does it matter to them?" . That's the lens for every line. Not "what do we want to say," but "what does a skeptical, time-poor finance person need to see to approve this without a meeting." The teams who build these for sellers set a hard rule on the same page: the case should take no more than five minutes to read . Five minutes is the budget. Everything has to fit inside it. And the framing has to be the buyer's, not yours. 86% of business buyers are more likely to buy when a company understands their goals, but 59% say most reps don't take the time to understand them . The one-pager is where you prove you did. If it opens with your product, you've already lost the room. If it opens with their problem, in their words, dated and specific to their account, you've earned the next four minutes. This is the same positioning discipline that runs through StoryOS, leading with the buyer's problem, not your capability.
Section 5
The BGA framework: The Forwardable Five
One page. Five blocks. Written as if your champion wrote it. Here's the structure, in order, with what goes in each and how to keep it honest. 1. Problem, in their language, dated, specific to the account. Two to four sentences. State the problem as the buying team would state it internally, not as your category describes it. Anchor it in time and specifics: "Since Q1, support response time has climbed from 4 hours to 19, and three enterprise renewals flagged it in their QBRs." Avoid your product name entirely in this block. Rule of thumb: if your champion read this paragraph aloud in a leadership meeting, would heads nod in recognition before you'd said a word about a solution? If not, you've written your problem, not theirs. 2. Cost of Inaction, quantify the status quo before you present the alternative. This is the block most founders skip, and it's the one that does the heavy lifting. Put a number on doing nothing. Not a fantasy number, a defensible one, built from the buyer's own figures. "At the current churn rate, three at-risk accounts represent £180,000 in ARR over the next two renewal cycles." If you can't get a clean number, go qualitative but concrete: "Every month this persists, the same fire-drill consumes roughly a day of two senior managers' time." You're directly targeting the 44% who'd otherwise default to "we're fine", and making the status quo, not your invoice, the thing that costs money. Put this before the proposed outcome so the reader feels the weight of the present before you offer the exit. 3. Proposed Outcome, the after-state, in their metrics. Describe where they end up, measured the way they measure. Not "our platform automates X." Instead: "Response time back under 4 hours, the three flagged accounts off the at-risk list, two senior managers' time returned to roadmap work." Keep it to the two or three metrics the budget holder actually tracks. If a metric wouldn't appear in their board deck, it doesn't belong here. 4. ROI, one honest number, not a fantasy model. Resist the 14-variable spreadsheet. A CFO discounts an ROI model the instant it looks engineered to produce a big number. Give one clear, conservative figure with its basis stated in a single line: "≈£180,000 in protected ARR against a £36,000 annual cost, roughly 5:1 in year one, before any new-revenue upside." State your assumptions plainly. An honest 3:1 you can defend beats a fantasy 12:1 that invites the finance team to tear apart your math, and once they're in teardown mode, you've handed the indecisive 56% a reason to delay. One number, stated like a peer would state it. 5. Risk Reversal, the antidote to the 56% who freeze. This is the block that addresses indecision directly, and almost no founder includes it on the page. Name the thing that lets a nervous buyer say yes without betting their reputation: a paid pilot, a 60-day opt-out, a success-based first phase, a named rollback plan. "Start with one team for 60 days; if response time hasn't moved by day 45, we stop and you owe nothing further." You're not discounting. You're shrinking the size of the decision until it's safe to make. Given that more than half of lost deals die from fear rather than disagreement , this block often moves more deals than the ROI block above it. The full menu of pilot and guarantee structures lives in the risk-reversal patterns guide. Govern it all with one gate: the Forward Test Five blocks, one page, five-minute read. Then run it through a single question before it leaves your hands: Would your champion paste this into an email to their CFO and hit send, without editing a word? If yes, it's a business case. If they'd need to soften the tone, cut the branding, translate the jargon, or rewrite a line in their own voice, it's a sales asset wearing a business case costume, and it won't get forwarded. Edit until the answer is an unhesitating yes. A practical proxy: read it back imagining you're a CFO who has never heard of you and doesn't care who you are . If any line only makes sense because you were in the room, cut or rewrite it. A worked example. A managed-IT services firm kept losing renewals-expansion deals to "we'll revisit next quarter." Their old case was an 18-slide deck. The rebuilt one-pager read, in full: Problem, "Since the March outage, three of your sites have had no monitored failover; the last incident took 6 hours to resolve." Cost of inaction, "A repeat at your largest site is ~£22k in lost production per day, based on your own Q1 incident log." Proposed outcome, "Sub-30-minute failover across all sites; zero unmonitored locations." ROI, "£14k/year cost against one avoided incident-day of £22k, pays for itself on the first prevented outage." Risk reversal, "90-day rollout; if monitored failover isn't live across all sites by day 90, the quarter is free." It fit on one page, named no products in the problem block, and used the client's own incident numbers. The champion forwarded it verbatim. That's the whole point. If you want the fill-in-the-blank version of all five blocks plus the Forward Test checklist, it's in the Template Pack, and the deeper buying-committee playbook is in the StoryOS playbook.
Section 6
You're running The Forwardable Five right when…
You're running it right when your champion forwards the document the same day, unedited, and you find out because the CFO replies directly with a question about the pilot terms, not about your features. When the page names the buyer's problem before it names your product. When the cost-of-inaction number comes from their data, not your imagination, and you'd defend it line by line in front of their finance team. When the ROI is one conservative figure a skeptic can't easily dismantle. When the risk-reversal block is specific enough that a nervous buyer can see exactly how to say yes without betting their job. And when you could strip every logo and brand color off the page and it would read like an internal memo a colleague wrote. If the document still needs you in the room to make sense, you haven't built a business case yet, you've built a leave-behind, and leave-behinds get left behind.