Formal procurement processes rest on a single premise: that a sufficiently rigorous evaluation framework leaves no room for emotion or impression to creep in. That's why RFPs stretch to dozens of pages, why every line item carries its own weight, and why some organizations bring in outside auditors to oversee vendor selection. It's also the reasoning behind years of advice urging B2B negotiators to lead with numbers over relationships, with specs over narrative.

A research team from the University of Melbourne and WHU – Otto Beisheim School of Management set out to test how well that premise actually holds up. They ran two negotiation simulations with 622 B2B sales and procurement professionals. Participants were asked to judge whether statements made by their counterpart in the negotiation were true or false. Half received the statements as plain claims. The other half received the same content wrapped in a narrative.

Without a story, the experts distinguished fact from fiction reasonably well. Once a story entered the picture, that distinction blurred to a statistically significant degree. Neither years of experience nor dedicated negotiation training made anyone immune.

The Story Moves Outside the Process

RFP scorecards get filled in with numbers: price competitiveness, on-time delivery rate, technical fit. These line items end up in meeting minutes and go through formal sign-off. But in real negotiations, the outcome is often tilted well before that scorecard is ever filled out.

What a sales rep brings to a pitch meeting is never just a spec sheet. Why this project needs to happen now, how other organizations with similar problems solved them, what lessons came out of past failures — none of this fits into any evaluation line item, but all of it lodges itself in the minds of the people sitting at the table.

This pattern isn't unfamiliar in Korean B2B settings either. It has long been common practice to fill out every required item in a bid proposal while, in the presentation itself, unpacking stories about the company's past projects or difficulties a team member personally worked through. Research now confirms that this goes beyond relationship management — it has a real effect on the judgment process itself.

What the 622-person experiment shows is that this happens regardless of professional experience. The instinct that says "I've been doing this a long time, so it's different for me" comes with no guarantee once the data is in.

How Stories Shape Judgment

In front of a story with clear causality, a protagonist, and a satisfying resolution, the brain sets down a large share of the resources it would otherwise spend verifying facts. This isn't a flaw that makes people easy to manipulate. It's closer to an evolved way of using cognitive resources efficiently in an environment flooded with information — narrative form simply speeds up how the brain processes information into patterns.

That property of narrative works in reverse at the negotiation table. Verification loosens when people hear a compelling story not because their expertise is low, but because of a cognitive mechanism that fires regardless of expertise.

In the 622-person experiment, the information participants received was identical whether or not it came wrapped in a story. Only the packaging changed. And yet when the packaging changed, judgment changed with it. What makes this experiment uncomfortable is that it shows no scorecard, however finely engineered, can control how the evaluator actually processes the information.

If experience isn't a shield, what is? That question is the homework this study leaves behind.

What Changes When a Quote Includes Context

Picture a solo entrepreneur or freelancer submitting a quote to a client. Two quotes describe the identical deliverable, the identical timeline, and the identical price.

One is a list of line items and rates: 20 hours of planning, 30 hours of design, 5 hours of review, total due. It's clear, but it gives the client nothing to contextualize it with.

The other carries background: the type of problem this client ran into before, which steps were added to this engagement to prevent it from happening again, what threw off the timeline on a similar project and how this one is being handled differently. Next to each rate sits a one-line explanation of why that time is needed.

If a client reviews both quotes on the same day, professional judgment doesn't necessarily land on the first one. That's what the research suggests — and it's a pattern that shows up again and again in real negotiations.

How Narrative Framing Changes QuoteEvaluationItemized QuoteLists unit price, quantity, and totalJudgment converges on price aloneDisagreements go straight to pricenegotiationContext-Rich QuoteIncludes background, scope, andconstraintsAdds judgment layers beyond priceRoom remains to reconcile disagreements

A context-rich quote doesn't automatically justify a higher rate. If the context doesn't match the actual work, the gap surfaces after delivery. A story only holds up for as long as its content is true. That's why a context-rich quote lasts only when it functions as an honest account of the work, not a sales technique.

For people like solo PMs or content directors who make their living from repeat business rather than one-off contracts, this distinction matters. Even if a story lands in a single negotiation, if the delivered work falls short of what was described, the next negotiation gets harder to come by. Conversely, when the context laid out in a quote is borne out by the actual delivery, price isn't what stays with the client.

The Question Negotiators Should Ask in the Face of a Compelling Narrative

There's one habit procurement staff or solo PMs can build when listening to a vendor's pitch: noticing the moment a narrative starts to feel compelling.

The sense that "this story really lands" is normally read as a positive signal. But in a negotiation context, it can be read as a warning that verification is slowing down. Slipping in one question right when that sense arises is a practical countermeasure.

What would have to be true for this story to hold up?

If a sales rep says, for instance, "We completed three similar projects ahead of schedule," the premise the story rests on is that those three projects are similar enough to this one. Pin down concretely how similar they actually are, and the story moves back into the territory of a verifiable fact.

This isn't a proposal to shut stories out. Information that includes context still conveys things that price or specs alone can't. But once you're aware that a compelling narrative can cloud judgment, you process the same story differently.

If the formal evaluation process doesn't block the story, a question can fill that role. Asking "what would have to be true for this story to hold up" is the most realistic countermeasure available.

Stories carry weight in negotiation precisely because negotiation was never made of numbers alone. That value works best when both the person telling the story and the person hearing it know what it is. It's also why the salespeople who manage relationships honestly over the long run are the ones who keep winning repeat business. When context turns out not to match fact, the gap surfaces once the deal is done.