You Built the Deck for Your Champion. Their CFO, CTO, and Procurement Team Are a Different Audience Entirely.

Your champion is not your buyer. They are your proxy — the person who will walk your deck into four meetings you will never attend, each populated by stakeholders who do not share their priorities, their context, or their reasons for caring.

The average B2B buying committee now has 11 members (Gartner, 2025). For enterprise deals above $250K ACV, that number climbs to 15-25 (GrowthSpree, 2026). Your champion loves the proposal. They are already sold. But before the deal moves, they have to convince the CFO that the ROI holds, the CTO that the integration won't break anything, procurement that the pricing and SLA terms are defensible, and legal that the data handling checks out. Every one of those conversations is a different deck — and they are all being run from the one you sent.

Most proposals are written for the person who received them. That is the wrong frame. The proposal is a brief your champion will use to sell internally, in rooms you cannot prepare them for because you did not build it to work in any room except the first.

The Committee Is Bigger Than You Think, and More Fragmented

The growth of the buying committee is not news — it has been climbing for a decade — but the 2026 data sharpens the problem. Forrester puts the average B2B buying group at 13 people. Every additional stakeholder added to a deal carries a 12-18% increased probability of a mid-cycle stall (GrowthSpree, 2026). Deals with 10 or more stakeholders close at an 18-30% win rate. Deals with 1-3 stakeholders close at 38-52%.

The math is stark: the committee size your deal requires is inversely correlated with your probability of winning it. And the primary mechanism by which more stakeholders kill deals is not disagreement — it is misalignment. Roughly 40% of deals stall on internal misalignment that the champion cannot resolve without materials specifically designed to address each audience's concerns.

The champion is your highest-leverage relationship, but only if you give them something to work with. Deals with an engaged, supported champion close at 38-52% win rates. Deals where the champion is engaged but under-equipped close materially lower — because they show up to the CFO's office with a deck built to impress a department head, not to make a financial case.

What the CFO Is Actually Reading

When the CFO opens your proposal, they are not reading it. They are scanning for three things: what this costs in year one, what it will cost in year three, and whether there is a credible ROI figure they can defend to their own boss. They will not excavate the case study appendix. They will not infer the business case from the product capabilities slide. If the financial logic is not explicit, readable in 90 seconds, and reconciled with a number they can put in a spreadsheet, they are done.

The CTO is reading for a different set of signals entirely. Their primary concern is integration risk — whether your product touches their stack in a way they will have to manage, explain, or apologize for later. They want to see your API documentation referenced, your uptime record, your security posture, and specifically whether you support SSO. The market positioning slide is irrelevant to them. The customer count is almost irrelevant. The technical architecture section you buried in the appendix is the first thing they will look for, and if it is not there they will ask.

Procurement entered the decision in 53% of B2B purchases from the first conversation, not the negotiation stage (Belkins, 2026). Their read is not about the product or the ROI. They are checking whether your pricing model is standard enough to fit their approval flow, whether your contract terms are compatible with their vendor policy, and whether there is an SLA they can point to when something goes wrong. A deck optimised for the economic sponsor reads, to procurement, as marketing material with no operational substance.

Legal is checking one thing: what your data handling looks like, who has access to what, and whether you have the certifications their company requires before signing off on any external data processor. A single slide on security compliance — the kind that actually names GDPR, SOC 2, and whatever vertical regulation applies — saves two weeks of back-and-forth. A deck that omits it generates an email chain your champion has to manage on your behalf.

The Champion's Problem Is Not Enthusiasm. It Is Translation.

Your champion cannot translate the proposal for each of these audiences, for a simple reason: it was not built to be translated. It was built to be sent. The narrative structure optimised for the initial evaluation does not restructure for a financial case. The product-led logic that won the technical evaluation does not reorder itself to lead with risk mitigation for legal. The case studies chosen for their strategic relevance do not swap themselves out for the compliance-focused customer reference procurement needs.

So the champion improvises. They add a note at the top of the email introducing the deck to the CFO. They extract two slides and paste them into a separate document for the CTO meeting. They flag three pages as "you can skip this" when they share with procurement. Each of these interventions is a point of failure — a place where the proposal's argument gets diluted, misrepresented, or simply lost.

And then the deal stalls, and nobody can explain exactly why, because from your side everything looked fine. The champion was engaged. The meetings happened. The follow-up emails went out. The problem is not that the champion failed to sell. It is that they were asked to be the translation layer for a document that was never designed to be translated.

One Core, Multiple Editions — Built Before You Send

The structural fix is not to build four separate decks. That is the approach that produces FINAL_v7_CFO_edit_2.pptx and costs twelve hours of senior time you do not have. The fix is to build one authoritative core and configure it, before you send, into the editions each audience actually needs.

The financial edition leads with business case and ROI. It buries the product detail and surfaces the numbers. The technical edition leads with architecture, security, and integration. It references the financial logic but does not make it the opening argument. The procurement edition leads with contract structure, SLA, and vendor qualification. The executive summary edition — the one the CEO or Managing Director will spend 90 seconds on — leads with strategic outcome and reference customers.

Each edition shares the same core claim, the same positioning, the same proof points. What changes is the order, the emphasis, and the sections made prominent versus sent to appendix. That is not customisation for its own sake. It is recognising that a proposal that tries to serve every reader equally serves none of them well.

The review step is identical regardless of edition: every version gets checked against your own knowledge before it leaves — claims verified, numbers reconciled, positioning confirmed accurate — because a tailored deck that contains an error is worse than a generic one. The champion who walks into the CFO meeting with a financial case that does not hold up has done more damage to the deal than the one who never made the financial case at all.

What Your Champion Needs to Walk Into Four Meetings

The practical version of this is not complicated. Before you send, identify who the deck will reach beyond the first conversation. In a mid-market deal, that is usually three audiences: the economic buyer, the technical evaluator, and procurement. In an enterprise deal, add legal and the executive sponsor.

For each, ask two questions: what does success look like to them, and what is the one thing that would make them block the deal? The answers tell you what to lead with, what to minimise, and what to add from your knowledge base that the initial draft omitted because it was not relevant to the champion.

Then build the editions — each from the same authoritative core, each reviewed before it leaves, each shipped as a living link so you know which edition each stakeholder actually opened and how long they spent on which section. That last part matters because the analytics tell you which audience is stuck, before they go dark.

The champion who wins the deal is not the one who is most enthusiastic. It is the one who shows up to four different rooms with something that speaks the language of the person already sitting there.

— The Lurio Team