A definition you can quote, the three categories including the personal one nobody writes down, an illustrative weighted example, and how to surface criteria before they harden.
Free Forever • No Credit Card Required
Quick answer
Decision criteria are the standards a buyer will use to judge the options in front of them. They describe not what a product must do, but how everything the buyer knows will be weighed when a choice is finally made.
The distinction from requirements matters. A requirements list is a set of capabilities. Criteria include those capabilities and also cost, risk, implementation effort, trust in the supplier, and what each person involved needs from the decision personally.
Does it do the job? Does it work with what is already in place? Does it meet the organisation's standards for security, data handling, and reliability? These are the criteria most often written down, and consequently the ones sellers over-index on.
What changes if we buy this? What does it cost in total, including the work of adopting it? What happens if it fails? How long before it pays for itself? These are the criteria the economic buyer cares about and the ones most likely to be missing from a technical evaluation.
Rarely written down, frequently decisive. Does this make my work easier or harder? Can I defend this choice if it goes wrong? Do I trust these people to make me look competent? Buyers are choosing what to advocate internally as well as what to purchase, and a supplier who ignores that is competing on two thirds of the board.
These weights and ratings are invented to demonstrate the arithmetic and are not benchmarks.
A buyer sets four criteria with weights totalling one hundred: fit with existing systems 35, total cost over three years 25, implementation effort 25, and supplier support 15. Each option is rated out of five on each criterion.
A supplier is rated 4 on fit, 3 on cost, 5 on implementation effort, and 4 on support. The weighted total is (35 × 4) + (25 × 3) + (25 × 5) + (15 × 4) = 140 + 75 + 125 + 60 = 400. Dividing by the maximum rating of 5 normalises this to 80 out of 100.
Note what the arithmetic reveals. This supplier is the most expensive of the options and still scores well, because implementation effort carries the same weight as cost and they are rated highest on it. A seller who knew only that price mattered would have discounted unnecessarily. A seller who knew the weights would have spent the conversation on implementation, which is exactly where their advantage lay.
Formal criteria appear in tender documents, scorecards, and requirement matrices. They are visible, comparable, and often assembled from a template or from whichever supplier spoke to the buyer first.
Informal criteria live in conversation and in the room where the decision is actually made. They include how responsive each supplier was during the evaluation, who seemed to understand the problem, and which option the team would rather work with. In evaluations of any length, the informal criteria frequently outweigh the formal ones, which is why a supplier can win every line of a scorecard and lose.
The direct question, what will matter most when you compare the options, produces a partial and usually generic answer. The useful questions are indirect.
What would justify paying more than the cheapest option? What would make an otherwise strong option unacceptable? What went wrong the last time you bought something like this? Who else has to be comfortable, and what will they be looking at? Each of these surfaces operative criteria rather than stated ones.
Ask again at each stage. Long evaluations acquire new participants, and new participants bring criteria that were not on anybody's list in week one.
Answering every requirement and losing is the classic outcome. The requirements document describes the minimum; the criteria describe the choice.
A scorecard written before you were involved will reflect whoever was involved first. The remedy is earlier engagement in future deals, and in the current one, asking which criteria are genuinely essential and which were added for completeness.
Price is easy for a buyer to say and rarely decides alone. It is frequently the polite version of a concern about value, risk, or confidence that has not been articulated.
A perfectly rational business case can lose to the option that a manager is comfortable defending. Nobody will tell you this directly, and it happens constantly.
Persuading a buyer to specify something only you offer wins deals and produces customers who discover later that the specification served the supplier. It is also the fastest way to lose a reference.
A well-run evaluation from the seller's side has criteria recorded in the buyer's own words, relative weights understood at least approximately, personal criteria identified for the two or three people who matter most, and a proposal written against those criteria rather than against a feature list. The criteria have been reconfirmed at least once.
A poorly run one has a requirements document, an assumption that price decides, no knowledge of what individuals need personally, and a post-loss review in which the buyer names a factor the seller had never considered.
| Term | What it describes | Real distinction |
|---|---|---|
| Decision criteria | How options will be weighed against each other | Includes cost, risk, trust, and personal factors |
| Requirements | Capabilities the solution must provide | A minimum bar, not a basis for choosing |
| Decision process | Who evaluates, in what order, by when | Concerns mechanics rather than judgement |
| Paper process | The contractual path from yes to signature | Starts after the decision has been made |
| Compelling event | Why a decision must happen by a date | Explains timing, not preference between options |
Keep the criteria on the opportunity in the buyer's own words, with their relative importance and the date they were last confirmed. Proposals can then be reviewed against what the buyer said mattered rather than against what the seller assumed, and a shift in criteria during a long evaluation becomes visible while there is still time to respond to it.
Continue with what a CRM is, lead management software, sales automation, CRM for small business, CRM alternatives, and product features.
Every team in this space loses revenue to the same recurring gaps. Here is what they cost you and how HelloGrowthCRM closes each one.
The proposal answered every requirement and lost anyway.
Requirements are not criteria. The buyer weighed the options on factors that were never in the requirements document, often including implementation effort, internal support, and who they trusted. Ask directly what will matter most when they compare, and ask again later, because the answer changes as the evaluation progresses.Criteria asked, not assumed
A scorecard arrived that appeared written for a competitor.
Criteria set before you arrived usually reflect whoever spoke to the buyer first. Engage earlier next time. In the current deal, the realistic move is to ask which criteria are genuinely essential and which were included for completeness, since most scorecards contain both and buyers will usually say which is which.Engage before criteria harden
Everyone says price is the deciding factor, and the cheapest option keeps losing.
Stated criteria and operative criteria differ. Price is easy to say and rarely decides alone. Ask what would justify paying more, and what would make a cheaper option unacceptable. The answers reveal the criteria doing the actual work, which are usually about risk, effort, and confidence in delivery.Stated versus operative criteria
The criteria changed halfway through and nobody told the seller.
Long evaluations acquire new participants with new concerns. Reconfirm the criteria at each significant stage, particularly after anyone new joins the committee. Treating a list gathered in week one as fixed for a six-month evaluation is how sellers end up answering questions the buyer stopped caring about.Criteria reconfirmed by stage
AI-powered CRM with the features you need to close more deals.
Common questions about using HelloGrowthCRM in your industry.
Join small businesses that close more deals with HelloGrowthCRM.
Free Forever • No Credit Card Required
Free Forever • No Credit Card Required
Prefer email? Write to sales@hellogrowthcrm.com