Concept
What is Requirement Based Evaluation?
Requirement-Based Evaluation is the process of narrowing a set of vendors by applying the buyer's specific requirements, one after another, and keeping only the vendors that credibly satisfy each one.
How it works
A buyer states or implies requirements. Each requirement is applied to the current set; vendors that do not visibly satisfy it are dropped. Because requirements are applied in sequence, the surviving set, and the leader, can change at every step.
Why it matters
Requirements are the invariant of commercial evaluation. Tools and surfaces change, but buyers always narrow by requirements. Understanding which requirements decide your category is how you learn where you are eliminated.
Limitations
What it does not do.
Knowing the requirements is not the same as satisfying them, and satisfying them is not the same as being credited with them. An evaluator has to be able to associate you with a requirement through evidence. Requirement-based evaluation explains where you are tested; evidence strategy addresses whether you pass.
The deeper question
Being found is not the same as being chosen.
Requirement-based evaluation is the how of commercial evaluation. It is the mechanism the research studies directly: which requirement removes you, and whether that repeats.
It is not a checklist you self-assess. It is what an evaluator applies to you, which is why it has to be observed rather than assumed.
Where it fits in the commercial evaluation lifecycle
Requirement-based evaluation is the requirement-evaluation stage, the center of the lifecycle. It sits between recommendation and validation and is where recommendation survivability, vendor elimination, and frontrunner movement all play out.
This is the commercial evaluation lifecycle: how a buyer’s evaluation unfolds. The Upstream Zero measurement workflow is how the company observes, diagnoses, acts on, and measures that lifecycle.
Commercial outcomes
Where this touches the business.
The commercial logic is direct: requirements decide the shortlist, and the shortlist decides the deals you are in. Surviving the requirements that matter in your category is what keeps you in contention for pipeline and win rates. Upstream Zero identifies those requirements and measures whether your position on them moves; it does not promise a downstream number.
Go deeper
Research components
How the work is done
Common questions
- Who defines the requirements?
- The buyer, explicitly or implicitly, and the evaluator interprets them. That interpretation can vary, which is why requirement interpretation is studied as its own research component.
- How do we know which requirements eliminate us?
- By observing a category run through realistic requirement sequences and recording where you drop out. That is what a Commercial Evaluation Audit produces.