Proposition: how to win a complex B2B deal once procurement takes over

You can run a near-perfect engagement for nine months - secure an executive sponsor, co-create the solution with the people who will actually use it, build genuine consensus - and still lose the deal in the three weeks it takes to turn all of that into a proposal. The work does not fail gradually. It changes character almost overnight, the moment the customer's budget is approved.

That moment is the start of Step 3 of our methodology - Proposition - and it is where more good deals quietly die than at any other stage. Not because the solution was wrong, but because the seller kept playing a collaborative game after the rules had switched to a competitive one. The people who had been thinking out loud with you go formal. A procurement function you have never met starts setting the terms. And the document you submit is scored against criteria you may not have written. Winning here rests on three things you mostly earned earlier: budget intelligence, requirements mastery, and the relationship leverage to use both.

When budget is approved, the deal changes hands

Up to this point, the engagement has been a conversation. Both sides explored the problem, shaped the options, and built shared ownership of an outcome. The approval of a budget ends that phase abruptly. What was a partnership becomes a competitive evaluation - frequently run by people whose explicit job is to introduce alternatives, apply pressure, and protect the organisation from a bad commitment.

I describe the shift to workshop groups in three lines: precision replaces flexibility, compliance replaces creativity, and competition replaces collaboration. The proposal that wins is no longer the most imaginative one. It is the one that fits the funding reality exactly, meets every stated requirement, and gives your supporters something they can defend in a room you are not allowed into.

The buyer experiences this shift as strain, not relief. Gartner's research on the B2B buying journey finds that 77% of buyers describe their most recent purchase as very complex or difficult, with a buying group of six to ten people - sometimes more - spanning as many as four functions, and "managing information from multiple sources" rated as their single hardest task.¹ In 2025, Gartner went further: 74% of B2B buying teams showed unhealthy conflict during the decision process.² By the time your proposal lands, it is not being read by a unified customer. It is being dropped into an internal argument.

Picture a CISO at a regulated financial-services firm. She may genuinely want your platform - but the procurement lead beside her is measured on the discount he extracts, legal is measured on the liability it removes, and finance is measured on whether it fits this year's number. Same logo, four scorecards. A proposal written for the CISO alone loses to one written for all four.

Budget intelligence: fit the funding reality, not your price list

Budget intelligence is knowing where the money actually sits before you price anything: how much, under whose authority, on what fiscal calendar, and whether it is classed as capital or operating expenditure. None of that is discoverable in the RFP. It is earned back in Step 1, when executive sponsorship gives you access to how the customer's finances really work.

The seller who skips this prices to their own list and hopes. The seller with budget intelligence prices to the reality - structuring the commercial so it clears the approval threshold that genuinely exists, lands in the right budget line, and matches the timing of when funds are actually released. In capital-heavy industries such as industrial automation and energy infrastructure, a proposal that ignores the capex approval cycle can be technically the strongest in the field and still stall for two quarters, waiting on a committee that meets four times a year. Precision here is not pedantry. It is the difference between a deal that closes this year and one that does not.

Requirements mastery: compliance is the price of being read at all

Requirements mastery is the unglamorous half of the proposition: meeting every stated criterion, in the format demanded, on time. At the proposal stage, creativity is a liability before it is an asset. Miss a mandatory requirement - a certification, an SLA, a data-residency clause - and a strong solution is filtered out before anyone weighs its merits. Compliance buys you the right to be evaluated at all.

This is where many otherwise excellent sellers lose, because they treat the requirements document as a formality to be answered rather than a scorecard to be beaten line by line. In a cybersecurity RFP, the mandatory section - certifications held, breach-notification timelines, sub-processor disclosures - is not the boring part. It is the gate. Clear it cleanly and completely and you have earned the right to compete on everything that actually differentiates you.

Relationship leverage: the requirements were written before the RFP

Here is the part the methodology insists on and most sales training ignores: by the time a requirements document is published, the deal is usually half-decided. Someone shaped those requirements. If it was not you, it may well have been a competitor - quietly, months earlier, while you were still admiring your own discovery notes.

By the time the requirements are written, the deal is half-decided. The only question is whether you were in the room when they were written.

Relationship leverage is what the first two steps were for. Because you earned executive sponsorship and co-created the solution, you know who authored which criterion and why - which requirements are genuine needs, which carry a competitor's fingerprints, and which are negotiable. That intelligence lets you map your proposal to the real priorities sitting underneath the formal ones, and to arm your supporters with the specific points they need to defend your case when procurement pushes back. A seller without that leverage is responding to a document. A seller with it is continuing a campaign. It is the natural extension of co-creating the solution instead of pitching it - the proposition is simply the moment that co-created work has to become legible to everyone who was not part of building it.

The real job is to close the information gap

Underneath budget, requirements, and relationships sits the obstacle that decides most complex deals: the buyer's own uncertainty. Customers do not buy from the supplier with the best product. They buy from the one who makes them most confident they are making a defensible decision - and they reach that confidence with very little of your help. Across an entire purchase, Gartner finds buyers spend only about 17% of their time with all potential suppliers combined; any single vendor gets a sliver of that.¹

So the proposal has to do work in your absence. Gartner's research on "sense making" is blunt about the stakes: sellers who help buyers cut through conflicting information close high-quality, low-regret deals around 80% of the time, while buyers drowning in too much or contradictory information are 153% less likely to land a decision they do not later regret.³ A winning proposition is not a feature inventory. It is a sense-making instrument - it tells the buying group what matters, in what order, and why, so a champion can carry the argument into rooms you will never enter.

Consider an enterprise SaaS deal in its final weeks. Your champion - a VP of Operations - believes in the platform, but she is not the one who signs. When the proposal reaches the steering committee she has perhaps ten minutes to defend it against a cheaper alternative she has never seen. A response that buries the decisive points in forty pages leaves her improvising. One that hands her three clear reasons this option carries the least risk lets her win the room on your behalf. The difference is not the quality of the product. It is whether the proposition was built to be carried by someone else.

This is also why the proposition has to be aligned internally on your own side before it ever goes out. A commitment your technical, delivery, and finance teams have not signed off on is not a stronger proposal - it is a closing problem you have scheduled for later. The methodology's bias is to build to last: promise only what the whole organisation can deliver, so the deal you win survives implementation rather than unravelling in it.

The proposition is won upstream

If you arrive at Step 3 needing the proposal itself to do the persuading, you are already behind. A great proposition rarely changes a mind; it ratifies a decision the earlier steps have been quietly building toward. That is the uncomfortable, useful truth of the proposal stage - the work that wins it mostly happened before procurement ever got involved.

The practical test for any complex deal in flight: when the requirements are published, will you recognise your own fingerprints on them? If yes, the proposition is yours to lose. If no, the proposal stage is where you will discover how much ground you gave away earlier - and Step 3 will feel less like a conclusion than an ambush. The 4steps2win methodology exists to make sure it is the former.