B2B Sales Motion: What Buyers Actually Expect in 2026

What actually changed in the B2B sales motion?

Buyer tolerance changed, not buyer demand. Anyone evaluating software today keeps three to seven alternatives open, reads comparison pages before the first conversation, and recognises a sales performance within two minutes. The sequence that worked for a decade stopped working, and the economy is not the reason.

The sequence is familiar: two weeks of waiting for a fifteen-minute call in which a junior rep asks ten to twenty questions a form could have asked. Then a handover to someone with a large slide deck. Then another week or two until a three-year contract proposal arrives — without anyone ever showing whether the product solves the buyer's actual use case.

Frank Piotraschke, CRO at octonomy and previously CRO at SoSafe and SVP Global Sales at Staffbase, explains in Manuel Hartmann's LinkedIn newsletter Diary Of A CRO why it held for so long: market power was concentrated enough that buyers had no way around the model. That concentration is gone. What remains is a buyer who can compare — and does.

From Manuel Hartmann's LinkedIn newsletter Diary Of A CRO, published in German. Every market statement and figure in it comes from Frank Piotraschke in conversation, not from SalesPlaybook — the full episode is available as a podcast.

Why does the first demo decide the deal?

Because it is now the first moment where a vendor can prove something instead of asserting it. Solve one real use case on real data in the first thirty minutes and you stay in the evaluation. Run a generic product tour and you are often out before procurement has learned the company name.

Piotraschke frames the shift as a change of governing question: it is no longer "why are we the cooler company", it is "how do we solve exactly this use case better than everyone else". That is not a matter of style. It moves the preparation work from the deck into data access — showing real data in a first demo means knowing beforehand which data.

Three practical consequences follow. The person in the meeting can operate the product, not only describe it. The use case is known before the call rather than being its subject. And the demo has a version that survives the buyer taking a detour.

How much competitive comparison belongs in your own sales conversation?

More than most sales organisations are comfortable with. The buyer runs the comparison either way; the only question is whether your arguments are in it. An openly presented comparison, use case by use case, is therefore not a risk — it is taking ownership of the framing.

Form matters. A comparison that talks the alternative down loses exactly the credibility it was meant to build. The durable version names what the other product is genuinely good at first, then the use case where yours carries further. A team that cannot write that line does not have a comparison problem, it has a positioning problem.

Piotraschke describes a dedicated comparison screen at octonomy that shows, use case by use case, where competing tools reach their limits. The relevant part is the granularity: task against task, not product against product.

What replaces seat-based pricing?

Not a different price list — a different calculation. The question on the other side of the table, in Piotraschke's account, is no longer what a seat costs but what the return case is and when it lands. Without an answer expressed in the buyer's own metrics, the conversation collapses into discounting.

The practical work is translation: calculate in the currency the counterpart actually manages. In customer service that is contact volume and handling time, in sales it is pipeline and conversion, in operations it is cycle time. Piotraschke draws the line between a vendor's model and one the customer controls — not the rep's spreadsheet, but the way the customer models and controls success themselves.

Outcome-linked components are the obvious option here, not a commitment. They work as a test on two or three deals, and they answer an uncomfortable question along the way: a product that cannot be sold on outcome rarely has a sales problem.

That is the shape of number a return case can carry: a figure tied to the buyer's own process, verifiable on a page they can open. A vendor who can name one does not need a conversation about seats.

Which metric shows whether the motion works?

Net revenue retention, calculated per cohort and per quarter. It measures whether existing customers spend more than they did a year ago — which is precisely what a solved problem produces and a sold expectation does not. New-logo numbers can hide a weak motion for months; a cohort's retention cannot.

Piotraschke describes the mechanism behind it: one customer, one use case running, and then the realisation that if this works, the next process could be automated too — the customer brings five, six, seven further use cases. That is the difference between expansion that grows out of usage and expansion that has to be negotiated.

The operating rule is uncomfortable but usable. If a cohort's retention sits below where it was, that is rarely a pricing problem. It is an adoption and impact problem, and adoption cannot be renegotiated in a contract — it is won or lost in the first demo.

Who does a sales team need in 2026?

People who can hold a real conversation. Piotraschke names what he screens out when building his team: reps who run through pitches, and reps who "qualify" instead of listening. What he keeps is the ability to sit at the table, listen, and pitch with humility — his framing, not a paraphrase.

This is not an argument against automation. It is the observation that trust has become the scarcest input in the market, because many buyers already carry a project that cost money and delivered nothing. Automation scales outreach; it does not manufacture trust. That is exactly why the few situations with a person actually present are worth more than they were.

For hiring, the question is not how many reps a team needs. It is how many of them can run a demo in which something is allowed to go wrong.

The two-week check

The five levers above can be tested individually, without launching a transformation programme. Work through them in this order — each answer is either evidenced or it is a task.

1. First demo: does it solve a real use case on real data inside thirty minutes? If not, which use case would it be?
2. Competition: is there a version of the comparison that names what the alternative is good at first? If not, write it.
3. Pricing: does a return case exist in the buyer's metrics rather than your own?
4. Retention: is net revenue retention reported per cohort and quarter at all? If not, the test number is missing.
5. Team: how many people can run a demo in which the buyer takes a detour?

Get stuck on one point and you have found the constraint. Get stuck on four and the problem is not sales performance — it is an unexamined process.