Do buyers rate software they inherited lower?

Modestly, among buyers who say how a tool came to them. When a buyer says a tool was in place before they arrived, they rate it about 0.4 of a point below what other buyers give the same product; when they say they chose it, about 0.4 above. Part of the inherited gap is associated with buyers who rate other tools lower too. The positive gap for tools buyers chose remains after that adjustment.

Based on verified interviews with the marketing, ecommerce, CRM and data leaders who take over software stacks and decide what to keep, at DTC and enterprise brands. Buyers are anonymized before publication; vendor names and views are reported as given. No vendor paid to appear or could edit this page.

−0.4
How far below the same product’s average from other buyers a tool is rated when the buyer says they inherited it.
+0.4
How far above that average a tool is rated when the buyer says they chose it or brought it in themselves.
3 in 4
Of the subset of interviews describing both an inherited and a chosen tool, the share in which the chosen tool rates higher against its own product’s average.

Do buyers rate inherited software lower?

Yes, among buyers who explicitly describe how they came to use the software. Across Alium’s buyer interviews, a tool the buyer says was already in place when they arrived is rated about 0.4 below the average other interviewed buyers give the same product. A tool the buyer says they picked is rated about 0.4 above it. Comparing each rating with the same product reduces the chance that the gap comes from inherited stacks holding different products; it does not establish that inheriting a tool causes a lower rating, or that choosing one causes a higher one. The plainest version comes from a performance marketing lead describing their web analytics tool: “I didn’t choose it. It was there before I joined the company, and we just had to work with it.”

Three terms carry the page, and they do not overlap. A tool is inherited when the buyer explicitly says it was in place, or already chosen, before they joined the company or took over the function, including tools that arrived with an acquisition. It is chosen when the buyer explicitly says they selected it, introduced it or helped choose it at their current company. Everything else is no statement: the interview does not establish who chose the tool. That covers more than nine in ten of the ratings, and the group can hold both inherited and chosen software whose owners never said so. Each rating is compared with the average other buyers give the same product. The no-statement group’s gap is about zero, which does not make its owners neutral or show that who chose a tool makes no difference there. The findings describe the buyers who disclosed how they came to a product.

How big is the gap, and which tools does it sit in?

The two associations are similar in size and opposite in direction, chosen about 0.4 above and inherited about 0.4 below, which puts the two groups’ average product-adjusted ratings roughly three-quarters of a point apart. That is a comparison between groups, not how much one person’s rating would change had they chosen the tool rather than inherited it. Inherited ratings are not uniformly low: 56% of them fall below their product’s average, against 44% of ratings with no statement. The gap comes from a shift across the whole spread of inherited ratings rather than from every inherited tool disappointing.

Chosen Inherited or no statement 95% interval

Each value is the average difference between a buyer’s rating and the average the same product receives in other interviews, leaving out the buyer’s own, on the ten-point rating scale. The vertical line is zero: no difference. The ranges are 95% intervals, resampled by interview; a range that crosses zero does not distinguish the group from zero. The kinds of tool are editorial groupings and several are small, so read the direction rather than a precise ranking.

The association is clearest for inherited email, SMS and lifecycle platforms and inherited commerce platforms. Email, SMS and lifecycle sits about 0.6 below the same products’ averages; ecommerce platforms sit about 0.5 below, with about seven in ten inherited ones rated below their product’s average. Content management and DAM, customer data and CRM are negative too, but none can be distinguished from zero. Inherited analytics and BI tools sit about 0.1 below, almost no gap. These show where the association is stronger in these interviews, not that a kind of tool is inherently more vulnerable, and not every difference between kinds of tool is itself significant.

The inherited gap holds on both sides of a 1,000-employee line: about half a point under it and about a third of a point above it. It points the same way in every year of interviews. The chosen gap is less even. At companies of 1,000 employees and above it is about 0.6 and distinguishable from zero; at smaller companies it is lower and cannot be distinguished from zero, which is not proof that choosing a tool has no relationship with its rating there.

The products on each side are largely the same. The tools buyers most often describe as inherited are among the most widely rated platforms in these interviews, and most of them are also among the tools buyers most often say they chose. That is what makes the comparison within a product possible, and it is why the page publishes no gap for any single product: split that finely, each one rests on too few ratings to read.

Five of the platforms buyers most often describe as inherited, with each platform’s average rating from all interviewed buyers. The page publishes no inherited or chosen figure for any single product.
Platform Avg rating Inherited or chosen
Klaviyo 7.7 Also the platform buyers most often say they chose themselves.
Shopify 8.1 Often described as chosen too.
Salesforce Marketing Cloud 6.8 Described as inherited more often than as chosen.
HubSpot 7.4 Described as inherited more often than as chosen.
Attentive 7.8 Described as chosen about as often as inherited.
That's the average buyer. How does your stack measure up?A free, peer-powered read of your tech stack, with a shortlist and your next steps.
Get my stack read →

Is it the tool, or the person rating it?

Part of the difference appears to be associated with the rater. Buyers who describe an inherited tool also rate their other tools, the ones with no statement attached, about 0.2 below those products’ averages. After accounting for each buyer’s general rating level, the inherited gap narrows to about 0.2 below, while the chosen gap stays about 0.4 above, so the association with choosing holds up better under this adjustment than the one with inheriting. The adjustment does not establish why either gap exists: expectations, fit, responsibility for the implementation and what buyers choose to disclose can all still play a part.

Choosers may be defending their choice. It is a possible explanation and the interviews cannot rule it out: a buyer who signed a contract has a reason to rate it well. Ownership can be very direct. Describing an email-rendering tool they bought themselves, one CRM and martech lead says: “So literally I just swiped my credit card and got it.” Another possible explanation fits just as well, which is that a buyer who chose a tool chose it for their own needs and set it up the way they wanted. Nothing here separates the two.

Inherited products may be associated with older deployments, but access to the latest release does not remove the gap. On multi-tenant software, where every customer runs the same current release, inherited ratings are still about half a point below the same products’ averages. That weakens the outdated-release explanation without ruling out what a release does not reset: configuration, enabled features, integrations, contracts and the age of the implementation. The few products buyers explicitly describe as old, legacy or being retired rate much lower; set them aside and the gap is about 0.3. Because those descriptions come from the buyers, this does not fully separate a tool’s age or quality from how respondents characterise their software. An SEO manager who likes their headless CMS puts it this way: “our particular setup is pretty complex, which can make it more manual and difficult for my team to do updates, but that’s not a fault of the product.”

Buyers may also say inherited more readily when they are unhappy. A dissatisfied buyer may be more inclined to mention that a tool came with the job, and a satisfied one may never say who chose it. That would widen the measured inherited gap without inheritance itself mattering. The interviews cannot say how much, since the classification depends on what buyers volunteered and most ratings carry none.

The counter-current: many inherited tools rate well, and some are kept on merit

More than four in ten inherited ratings sit above their product’s average, and some buyers describe the tool winning them over. “I just inherited that tech, but I’ve been pleasantly surprised by it,” says one ecommerce and CRM director of a digital asset manager. An IT security leader explains why an identity tool survived the arrival of a new team when most did not: “It’s one of the few tools that was here when I got here that’s still around. And it’s just because they’re really good.” A handful of buyers describe formally re-evaluating a tool they inherited and keeping it; one product marketer says the company reviews every vendor each year, and that they are among the stakeholders arguing the incumbent still fits.

What this means if you have inherited a stack

How should a new leader evaluate software already in place before deciding whether to keep or replace it? Our recommendations, not practices buyers describe, follow from the observed differences, but the interviews do not establish that any individual leader is biased against an inherited tool, or that a low score identifies the cause of dissatisfaction.

  1. Treat your first assessment as provisional, not automatically too negative. The average association does not say how you will rate your own tool. Write down which problems you have experienced directly, which capabilities you have tested and which complaints predate you, and reassess once you understand the implementation and its history.
  2. Compare with other buyers of the same product, not your last company, then investigate the differences. A lower score can reflect configuration, integrations, data quality, staffing, contract terms or a genuine mismatch. Benchmarking raises questions; it does not show that the implementation is more likely at fault than the product.
  3. Check whether the existing implementation can meet your requirements before committing to replace it. Look at configuration, integrations, data, staffing and support. One marketing leader says they would have rated their CMS lower on arrival, when nobody internally worked on it, and moved the score up once a designer and developers were dedicated to it. That is one case, and it does not mean every poorly rated incumbent can be fixed economically.
  4. Put the incumbent through the same evaluation as any replacement. Score it against the same requirements, at the same price point, rather than letting it lose by default. A familiar tool from your last job is a candidate too, not the answer; see do marketing tools follow people.
  5. Use the findings by kind of tool as context, not a rule. The gap is more pronounced here for email, SMS and lifecycle platforms and for ecommerce platforms than for analytics and BI, but the groups differ in size and uncertainty. Judge whether a problem is real by its business impact, your requirements and the alternatives, not by adjusting anyone’s judgement for the kind of tool.
  6. Use the contract timeline to structure the review. Renewal dates, notice periods, termination terms and migration requirements set when a change can happen; use the time before them to test the incumbent, compare alternatives and estimate switching costs. An urgent security, compliance or operational problem can justify acting sooner.

Want your own stack read the same way?

Get mine →

What not to read into this

Four inferences go further than the data. That inheriting a tool makes it worse: the comparison sets one buyer’s rating against other buyers of the same product, so it is a difference between two groups of buyers, not a before-and-after or a causal effect. That any product named here rates badly: the same products appear on both sides, and the page publishes no inherited or chosen figure for any product. That a tool with no statement is owned neutrally: most interviews simply do not say who chose a tool, and the no-statement group mixes inherited and chosen tools whose owners never mentioned it. That a low-rated inherited tool will be, or should be, replaced: the interviews show the rating, not what happened next, and plenty of inherited tools stay on merit.

For which tools new leaders bring with them, see do marketing tools follow people to their next company; for how ratings move with company size, does company size change how buyers rate software; and for why email platforms, the inherited tools with the clearest gap, get replaced, why companies switch email platforms.

Common questions

Do people rate software they inherited lower than software they chose?

Yes, by a modest amount, among buyers who explicitly describe how they came to use the software. In Alium’s buyer interviews, a tool the buyer says was in place before they arrived is rated about 0.4 of a point below the average other buyers give the same product, and a tool the buyer says they chose is rated about 0.4 above it. Comparing with the same product reduces the chance that inherited stacks simply hold different products, but it does not show that inheriting a tool causes a lower rating. Part of the inherited gap is associated with the rater: the same buyers also rate their other tools a little below average.

Why do buyers rate tools they chose higher?

The interviews do not settle why. One possible explanation is that people who chose a tool defend the choice; another is that a buyer who picked a tool picked it for their own needs and set it up the way they wanted. The data cannot separate the two. What it does show is that the positive gap for chosen tools, about 0.4 of a point above the product’s average, remains after allowing for how generously each buyer rates their other tools.

Are inherited tools rated lower because they are older versions?

Access to the latest release does not remove the gap. On multi-tenant software, where every customer runs the same current release, inherited ratings are still about half a point below the same products’ averages. Tools that buyers explicitly describe as old, legacy or being replaced do rate far lower, but they are few, and setting them aside leaves the gap at about 0.3 of a point. That weakens the outdated-release explanation without ruling out what a buyer inherits along with the licence: configuration, enabled features, integrations, contracts and the age of the implementation.

Which inherited tools get the lowest ratings?

By kind of tool, inherited email, SMS and lifecycle platforms show the clearest gap, about 0.6 of a point below the same products’ averages, followed by ecommerce platforms at about 0.5, with about seven in ten of them rated below their product’s average. Inherited analytics and BI tools show almost no gap. CRM, content management and customer-data tools are negative too, but their gaps cannot be told apart from zero. These show where the association is stronger in these interviews, not that a kind of tool is inherently more vulnerable to it.

Should a new marketing leader replace the tools they inherited?

Not on first impressions alone. Our recommendation, not a practice buyers describe, is to treat your first assessment of an inherited tool as provisional, compare your experience with what other buyers of the same product report, investigate the differences, and check whether the existing implementation can meet your requirements before deciding. Some buyers describe re-evaluating an inherited tool and keeping it because it held up.

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 read

Free · no password · your answers are anonymized before they inform research like this.

Want to come back to this?We'll email you a link to this page, so it's easy to find later or forward to your team.
Methodology. Alium conducts verified interviews with software buyers — the people who select and operate these platforms. For this page, every passage in which a buyer talked about who chose one of the tools they rated was read and classified by hand as inherited, chosen by the buyer, or neither; most ratings carry no such passage and count as neither. Each rating is compared with the average rating the same product receives in every other interview, leaving out the rater’s own interview, for products with at least eight other ratings, with duplicate product records combined; comparing within a product reduces the effect of product mix but does not establish cause. The ranges in the figure are 95% intervals from a bootstrap that resamples interviews rather than individual ratings, since one buyer often describes several inherited tools. Kinds of tool, the multi-tenant software grouping and the 1,000-employee line (drawn from the buyer’s company record) are editorial groupings. Buyer identities are verified at interview time and anonymized before publication; vendor names are reported as given. No vendor paid to appear or was able to edit this page.