Reditus B2B Buyer Model | Section 6
The Multiple Decisions Embedded in a Single Purchase
Act or not. Build or buy. Which vendor. Each is evaluated separately against the same tolerance curve.
From the paper
By the time the vendor demos started, everyone assumed the company had already decided to move forward.
The problem had been acknowledged months earlier. Security gaps were real. Manual processes were brittle. The leadership team had agreed something needed to change. The question, as far as most people understood it, was which solution to pick.
Three vendors were invited in.
Each demo was thorough. Each addressed the core requirements. One stood out clearly on capability. Another on brand familiarity. The third on ease of implementation.
After the last demo, the CIO asked for reactions.
Product liked the most advanced platform. “It gives us room to grow,” she said.
Security preferred the familiar name. “I know how they operate. Fewer surprises.”
Operations was quieter. When pressed, he said, “All of these would help. But I’m not convinced we should be buying anything yet.”
The room paused.
The CIO frowned. “We’re past that,” he said. “We’ve agreed we need a solution.”
Operations didn’t push back. “I agree there’s a problem,” he said. “I’m not sure I agree this is the moment to introduce a vendor dependency.”
They moved on anyway.
In the following weeks, the conversation drifted.
Procurement asked detailed questions but never pushed for selection. Legal flagged contract language but didn’t block. Finance asked whether building something internally might be cheaper over time.
Eventually, someone said it out loud. “Could we just build a lightweight version ourselves?”
The idea took hold quickly.
Engineering liked the control. Security liked the familiarity. Finance liked the optics of investment rather than spend. Product worried about timelines but didn’t object.
The vendor evaluations slowed. Meetings were postponed. No one officially rejected any option.
From the outside, it looked messy.
Why evaluate vendors if you weren’t ready to act? Why act if you might just build? Why build if external tools were clearly better?
Inside the system, it felt orderly.
The decision to acknowledge the problem had been easy. The decision to act right now had been harder. The decision to buy externally felt riskier than building. And the decision to choose among vendors never quite mattered, because it sat downstream of decisions that hadn’t fully cleared.
No one changed their mind.
They just discovered, piece by piece, which decisions they could tolerate, and which ones they couldn’t.
The purchase didn’t fail.
It never made it past all of its decisions at the same time.
What appears from the outside as a single buying decision is, in practice, a set of distinct decisions evaluated at the same time.
These decisions are not always explicit, and they are not always resolved independently. But at any given moment, they are all evaluated against the same tolerance curve.
What differs is not the tolerance curve itself, but where each decision falls relative to it.
In complex B2B purchases, there are often up to three decisions embedded in a single purchase:
- Whether to act at all
- Whether to build internally or buy externally
- Which external option to choose
Not every purchase involves all three. But when they do exist, each decision is evaluated separately against the tolerance curve shaped by identity utility and selfish utility.
The decisions described here are not sequential gates. They are distinct positions evaluated within the same tolerance space.
The decision to act does not necessarily precede the decisions to build, buy, or select a vendor. It is evaluated simultaneously with them. In practice, the act / no-act distinction appears in two ways:
- as an embedded position within the tolerance space, like all other decisions
- and as the system-level outcome when no downstream configuration remains within tolerance
The Decision to Act or Not Act
Early in a process, this decision typically carries high personal risk and relatively low certainty about meaning. Taking action introduces new exposure, visibility, and accountability. Doing nothing preserves existing narratives, roles, and optionality.
As a result, the act versus not-act decision often falls outside an individual’s tolerance range, even when:
- the problem is acknowledged
- the value of a solution is accepted
- alternatives are evaluated seriously
When this decision remains outside tolerance, no downstream decision becomes possible, regardless of merit.
From the outside, this looks like indecision.
No-act can manifest in two distinct ways. First, as a deliberate position: doing nothing is actively chosen because taking action introduces intolerable consequence. Second, as system default: when no configuration of action falls within tolerance for enough individuals simultaneously, no-act emerges not as a choice but as the only possible outcome. From the outside, both look like indecision. Structurally, both are resolution.
The Decision to Build or Buy
If action becomes possible, a second decision may surface: whether to build internally or buy externally.
This decision occupies a different position in the same tolerance space.
Building internally often:
- scores higher on personal narratives of control, ownership, or self-reliance
- reduces dependence on external parties
- increases execution burden and long-term accountability
Buying externally often:
- reduces operational workload
- introduces vendor dependency and visibility
- concentrates responsibility for selection and outcome
For some individuals, building falls closer to their tolerance range than buying. For others, the reverse is true.
This explains why:
- “We’ll just build it” persists even when inefficient
- external solutions are explored but not selected
- build-versus-buy debates stall without resolution
The build/buy decision is not a subset of vendor selection. It is a separate position in the same tolerance space.
The Decision of Which Vendor to Choose
Vendor choice occupies its own position in the same identity-selfish utility space, shaped by:
- defensibility and reputation
- implementation risk and support burden
- reversibility and downside exposure
At this stage, differences between vendors are often small relative to the tolerance curve itself.
This explains why:
- safer vendors outperform better ones
- familiarity outweighs differentiation
- references matter more than features
- ROI parity fails to break ties
Vendor choice rarely maximizes upside. It minimizes regret within tolerance.
Apparent Inconsistency Across Decisions
Because all implied decisions are evaluated against the same tolerance curve, these patterns emerge:
a vendor appears attractive while action itself is not possible
buying feels acceptable while no specific vendor does
building is workable while buying is not
From the outside, these patterns appear inconsistent or irrational. Within the tolerance-curve model, they are structural. Each decision occupies a different position relative to the same curve.
The system is not selecting for maximum upside. It is selecting from among what remains viable.
Committee Effects Across Multiple Decisions
In a buying committee, each individual brings their own time-specific tolerance curve.
Each implied decision is evaluated separately by each person. Momentum depends on overlap that must exist across people and across decisions at the same time.
For a committee purchase to happen, at least one workable option at each decision layer must fall within tolerance for all relevant individuals simultaneously. If action is tolerable for some but not others, or if building works for some while only buying works for others, the system cannot converge.
Attempts to force convergence without changing who bears consequence do not move decisions closer to tolerance. They increase friction.
Implication
Complex buying behavior cannot be understood by treating purchases as single decisions.
They are layered decisions, each occupying a distinct position in the same tolerance space.
The decision to act is evaluated as an embedded position within tolerance space. When downstream decisions fail to remain within tolerance, no-act emerges as the system-level outcome.
Outcomes emerge not from persuasion or comparison, but from which decisions fall within tolerance for the right individuals at the same time.
The system is not indecisive. It is constrained.
FOUNDATIONAL PAPER
The Reditus B2B Buyer Model
Consequence, Power, and Decision Emergence in Complex B2B Buying. Read the complete paper by Craig T. Watkins.
Get in Touch
If what you’ve read here resonates, begin with a quick check on fit.
No pitch. No pressure. Just context.