Does the reason a tool was chosen predict how buyers rate it?
Partly, though these interviews show an association rather than a test of prediction. Buyers who recall choosing a tool for its capabilities or ease of use rate it about a quarter of a point above the average other buyers give the same product. Those who cite price or reputation rate close to that average. Those whose tool was already in place, or chosen elsewhere in the organization, rate it about a quarter of a point below. The clearest line is not cheap against expensive; it runs between answers that name a functional reason and answers where the respondent did not take part in choosing. Reasons overlap, and the results cannot say whether participation, fit, satisfaction or an after-the-fact explanation accounts for the differences. A marketing leader at a large consumer brand describes the reputation-only version plainly: “Strictly based on reputation. We didn’t do any kind of real evaluation.”
Many interviews ask why a tool the buyer uses was originally chosen, and the answers here are the ones tied to a tool the buyer also rated. A reason is what the respondent recalled at the interview, not a reason recorded at the time of purchase. Current satisfaction can shape how a buyer explains an earlier decision, and some answers describe decisions made before the respondent joined or by another team. So the page shows how recalled reasons relate to current ratings, not whether a rationale would have predicted the rating before the tool was implemented. Answers often carry several reasons, more than half of them two or more, so every figure counts a reason whenever it is mentioned, and the groups overlap. Each rating is compared with the average other buyers give the same product, so a gap describes a tool against its own product, not one product against another.
The answers spread unevenly. About half name a capability: a specific feature, scale, flexibility or fit for a use case. About three in ten say the tool fits the rest of the stack, and about one in five names ease of use. Reputation (the market leader, the industry standard, a name everyone uses) comes up in about one answer in six, and price in about one in seven. About one in five says someone else made the call. The vendor’s team, its support or account management, comes up in only about one answer in twenty-five. Those buyers rate about four-tenths of a point above their product’s average, the largest positive difference among the reasons in the chart, with a wide interval running from under two-tenths to about seven-tenths. The group is small and the reason was recalled after using the product, so this describes these answers; it is not evidence that choosing for support brings the biggest benefit.
Each value is the average difference between the respondent’s rating and the rating other interviewed buyers give the same product, leaving out the respondent’s own interview, on the ten-point rating scale. The vertical line is zero, the peer average. Rows overlap, because one answer can cite several reasons; the two hollow rows include only price or reputation answers with no capability or ease-of-use reason, and the reputation one also leaves out answers calling the tool the best. The 95% intervals, resampled by company, show the uncertainty in each group’s difference; comparing two groups needs the uncertainty in their difference, not just whether each interval crosses zero. Decided elsewhere means a parent company, IT, procurement or leadership chose the tool while the buyer was there.
| Reason the buyer gave | Share of answers | Gap from product average | Rated above it |
|---|---|---|---|
| Capabilities | 50% | +0.26 | 60% |
| Fits the existing stack | 29% | +0.17 | 59% |
| Ease of use | 20% | +0.25 | 60% |
| Reputation or market leader | 16% | 0.00 | 55% |
| Price | 14% | +0.12 | 59% |
| In place before the buyer arrived | 13% | −0.25 | 45% |
| Decided elsewhere in the company | 9% | −0.26 | 50% |
| The vendor’s team | 4% | +0.43 | 63% |
Is it risky to choose software on price?
Not clearly, on this evidence. A tool whose buyer names price among the reasons rates about a tenth of a point above its product’s average, a gap that cannot be told apart from zero. Capability answers sit somewhat higher, but the difference between the two groups cannot be told apart from zero either, so the figures alone do not show that one rationale produces better outcomes. Price is rarely the only reason: most buyers who mention it name a capability or ease of use in the same breath. One ecommerce marketer explains an ad-testing tool that way: “It’s really cheap, it’s very easy to use.” Those combined answers rate about two-tenths above the product’s average.
Price without a functional reason is less conclusive. Answers that give price with no capability or ease-of-use reason beside it show a negative estimated difference from the product’s average, and the handful naming price as the only reason sit lower still, but both rest on limited observations, with intervals that include no difference at all. An early choice at a direct-to-consumer brand is typical of the shape: “we actually just got a good deal on the price.” The data does not show that choosing mainly on price leads to lower ratings, and the small observed difference between price-led and capability-led choices is not proof that the two are equally good bets.
Is the market leader a safe choice?
Choosing a familiar or widely adopted product is not associated with a rating difference in either direction here. Buyers who cite reputation, market leadership or industry-standard status rate the tool about level with other buyers of the same product, within about a sixth of a point either way. That does not show that choosing the leader is safe, that the product met the buyer’s needs, or that it beat the alternatives; it shows only that reputation-led buyers carry no clear premium or penalty against other users of the same product. Buyers who cite capabilities rate about a quarter of a point above the peer average, against about zero for reputation, and the estimated difference between the two groups stays clear of zero. Reasons overlap and were recalled after the fact, so this does not show that evaluating capabilities causes higher satisfaction.
The weaker form is reputation as the whole story. When the answer gives reputation and no capability, ease-of-use or best-tool reason, the estimated difference is about two-tenths below the product’s average, but the interval includes zero, so the gap is not established. Answers like these may point to a choice driven mainly by familiarity, like the reputation-only quote above, but they do not prove the buyer skipped all assessment.
The platforms most often chosen on reputation are the most widely rated ones in these interviews: Salesforce, Google Analytics, Klaviyo and Shopify head the list. Because each rating is set against its own product’s average, a reputation pick at the average says nothing about whether those platforms rate well or badly overall; it says the buyers who picked them for their name are about as satisfied as everyone else who uses them. How buyers find vendors in the first place, including the role of peers and analysts, is covered in how software buyers actually find vendors.
What happens when someone else made the call?
Buyers who say the tool was in place when they joined rate it about a quarter of a point below its peer average. Buyers who say the choice was made elsewhere, by a parent company, IT, procurement or leadership, show a similar difference. The two circumstances are distinct: an inherited tool predates the respondent, while a central selection may have happened during their tenure. The interviews do not consistently record whether the respondent was consulted, how much influence their team had, or whether the tool met the organization’s broader needs. In these two groups, fewer than half of ratings sit above their product’s average; in the remaining answers, where no one else is said to have made the choice, about six in ten do, and the average gap between the two is about four-tenths of a point. That is a difference in reported ratings and circumstances, not evidence that giving users final authority would produce the same improvement. A marketing leader at a healthcare company sums up the second kind in one sentence: “It was a corporate decision at a global scale.”
The inherited half of this is the subject of do buyers rate software they inherited lower, which measures it across every passage where a buyer said who chose a tool rather than only this question, and finds that part of the inherited gap goes with the rater, who scores other tools lower too. The decided-elsewhere half is new here, and it is concentrated at companies of 1,000 employees or more, where most central decisions in these interviews sit; below that line there is little observed difference, on a small base. It holds after allowing for how each buyer rates their other tools.
Several explanations fit, and the interviews cannot isolate them. A centrally chosen tool may put other teams’ needs first. A buyer who helped choose a tool may defend the decision, while one who inherited it may judge it more critically. Differences in roles, circumstances or implementation histories could also contribute. The analysis cannot tell whether less participation lowers satisfaction, whether dissatisfied buyers emphasize their lack of involvement, or whether both reflect something else.
The counter-current: buyers who call their own tool the best
A small group of answers gives no concrete criterion beyond calling the product the best available: it was the best tool on the market. Those buyers rate about half a point above their product’s average, the largest gap on the page, but it is hard to read as a purchasing rationale. Calling a product the best after using it may simply express current satisfaction, so the page keeps that verdict apart from reputation and does not treat it as a predictor.
Want your own stack read the same way?
Get mine →What this means before you sign
Our recommendations are implications of these associations, not practices buyers describe and not proven ways to raise satisfaction. The analysis compares current ratings with reasons recalled after selection, so it cannot show which criteria would have predicted better results before implementation. Five questions follow from it.
- Can you identify the capabilities and workflows that matter to your team? Buyers who recall a functional or ease-of-use reason tend to rate above their product’s average. That does not prove that stating requirements raises satisfaction, but it supports making them explicit: name the essential jobs, test them with representative users, and record whether each candidate does them before choosing.
- Is price a deciding criterion, and what trade-offs come with it? Buyers who cite price show no clear rating penalty, which does not make every cheaper option the right one. Compare total cost, functionality, integration, service and the effort to run the tool, and check that a lower price does not give up one of the essential jobs.
- Is familiarity replacing a product evaluation? Reputation-led buyers rate close to their product’s average, which shows neither safety nor superior performance. Compare the leader with relevant alternatives on your actual requirements, and look for evidence from customers with similar needs.
- Who will operate the tool, and have their needs been evaluated? Centrally selected and inherited tools are associated with lower ratings here, for reasons the data cannot pin down. Involving the daily users in setting requirements and in hands-on testing can surface workflow and implementation problems before the final selection, even when approval sits elsewhere.
- Will you document the decision and revisit it after implementation? Record the requirements, alternatives, expected benefits, costs and reasons at the time of purchase. At implementation reviews and at renewal, compare those expectations with how the tool has actually performed, rather than relying on an explanation that may shift with satisfaction.
What not to read into this
Five inferences go further than the data. That choosing for capabilities causes satisfaction: reasons were recalled after the fact, and a satisfied buyer may remember a choice in terms of what works, so the direction can run from the rating to the reason. That price or reputation are bad reasons: neither is associated with a rating below the product’s average; they are simply not associated with a higher one. That market leaders are mediocre: every gap is measured against the product’s own average, so the page says nothing about whether one product rates above another. That buyers had a single reason: more than half gave several, and the figures count every reason mentioned, so the groups overlap. That these shares describe the market: they are shares of interview answers about tools buyers rated, not a share of purchases, a churn rate or a market share.
For how ratings move when a buyer inherited the tool, see do buyers rate software they inherited lower; for whether modules bought as part of a suite rate lower than standalone tools, suite or specialist; and for how buyers build a shortlist, how software buyers actually find vendors.
Common questions
Does the reason you chose software predict how satisfied you will be?
Partly, as an association rather than a tested prediction. In these buyer interviews, a buyer who recalls choosing a tool for what it does or how easy it is to use rates it about a quarter of a point above the average other buyers give the same product. A buyer who cites price or reputation rates it close to that average. A tool someone else chose, whether before the buyer arrived or elsewhere in the organization, rates about a quarter of a point below it. These are reasons recalled at the interview, not recorded at purchase, so the pattern links recalled reasons with current ratings; it is not evidence that a reason predicts later satisfaction or causes a rating.
Are software tools chosen on price rated lower?
Not in these interviews. A tool whose buyer names price among the reasons for choosing it rates at about the same level as other buyers of that product, slightly above if anything, and the difference from tools chosen for their capabilities cannot be distinguished from zero. Price usually arrives with another reason. When price comes with no capability or ease-of-use reason, the figure dips below the product’s average, but on a small base and with a range wide enough that it does not establish a penalty either.
Is choosing the market leader a safe bet?
These interviews cannot show that it is. A tool chosen because it was the market leader, the industry standard or well known rates about level with what that product’s other buyers report, within about a sixth of a point either way: no clear premium and no clear penalty. That does not show the leader met the buyer’s needs or beat the alternatives. Buyers who cite capabilities rate about a quarter of a point higher than buyers who cite reputation, a difference that can be told apart from zero, and when reputation is the whole story, with no capability reason given, the figure leans below the product’s average, though not by an amount that can be told apart from zero.
Why do tools that someone else chose get rated lower?
The interviews do not settle why. Tools that were in place before the buyer arrived, and tools decided by a parent company, IT, procurement or leadership while the buyer was there, both rate about a quarter of a point below the same products’ averages. A centrally chosen tool may put another team’s needs first. A buyer who helped choose a tool may defend it, while one who inherited it may judge it more critically. The interviews do not consistently record whether the buyer was consulted, and the data cannot separate these explanations.
What should I check before choosing software on price or reputation?
Our recommendation, not a practice buyers describe, is to make sure a capability reason sits beside the commercial one. Buyers who cite price or reputation show no clear premium or penalty here, which says nothing about whether a given choice will meet your needs. Write down the jobs the tool must do for your team, test them with the people who will use it daily, and compare the cheaper option or the market leader with alternatives on those requirements.
Your stack, read by the buyers who've run it
Peer-powered: built from hundreds of verified buyer interviews, and fitted to the tools you already run. You get a shortlist for your stack and your next steps.
Get my stack readFree · no password · your answers are anonymized before they inform research like this.