Do companies have too much software?
About a third say they do, and most of those say something is missing too. Many Alium interviews ask one standard question about the stack as a whole: do you have all the technology you need to be successful, are there gaps, do you have too much tech? Of the buyers answering that version, 51% name only a gap, 22% name both a gap and too much, 14% say too much and nothing missing, and 13% say the stack is about right. The four groups do not overlap. The two that include too much come to about 36%, and about six in ten of those buyers also name a gap; across all four groups, about three-quarters identify something missing. These are perceptions reported in an interview, not independent assessments of usage or spend. Each share is of answers to the stack question, and a buyer may be describing their own team's or division's tools rather than the whole organization's. As the next section shows, the shares also differ with how the question is put.
The top row is every answer to the question when it offered both directions: whether the buyer has all the technology they need, whether there are gaps, and whether they have too much tech. The bottom row is a random sample of answers when the question asked only about having what they need or about gaps. Each answer is read in full and put in one group. Too much on the right adds the two dark segments. Both rows rest on well over a hundred answers, and shares are rounded.
What the four answers mean
Each answer is put in exactly one group, from what the buyer says about their own stack. The groups do not overlap.
- A gap only
- The buyer names something lacking and nothing extra. The gap can be a tool, a capability, or the people and integration needed to use what they have.
- Both a gap and too much
- The buyer names an excess somewhere and a gap somewhere else, often in the same breath. A hedged excess, such as maybe a little too much, counts.
- Too much only
- The buyer describes more than they need: too many tools or vendors, tools that do the same job, tools paid for and not used, or a wish to cut or simplify. They name no gap.
- About right
- The buyer says they have what they need, with no specific gap or excess. A general there is always something new still counts as about right.
The four overall groups are shares of answers to the relevant version of the question, one classified answer per interview. The shares of gap types and excess types further down use the subsets named in those sections. An interview is not necessarily a unique company, since some companies were interviewed more than once, and none of these shares is the percentage of all companies with excess or gaps. The people Alium interviews are marketing, ecommerce, data and technology leaders, more of them at companies with 1,000 or more employees than below.
Does the way you ask change the answer?
The answers differ substantially between the two wordings. When the question explicitly offers too much tech, about 36% of buyers describe an excess. When it asks only whether they have what they need or where the gaps are, about 10% raise an excess on their own. That difference of about 26 points is between two observed groups of interviews, not a randomized estimate of what the wording itself does. The biggest shift is in the gap-only group, about 51% against 76%. The share saying the stack is about right stays similar, at 13% against 14%.
The comparison suggests that mentioning excess changes which problems buyers report more than it changes how many say the stack is adequate. One plausible reading, ours rather than something buyers say, is that a buyer with overlap in one area and a gap in another emphasizes the gap when asked only about gaps, and describes both when invited to. The interviews do not show that the same buyers would have answered differently under the other wording.
The two wordings were asked in different interviews, not assigned at random. The difference appears within both company-size groups, under 1,000 employees and 1,000 or more, and within each interview year from 2024 to 2026. That makes company size or timing alone a less likely explanation. It does not rule out differences in who was asked, the context of the interview, how the question was put on the day, or other factors. Neither wording is neutral: one may prompt answers buyers would not have given, and the other may hold back answers they would have.
How this fits with the great consolidation. The great consolidation finds about one buyer in ten raising consolidation unprompted, a share steady since 2023. That is a different measure, of buyers bringing it up anywhere in an interview, and this page does not contradict it. When this question leaves too much out, the share who raise an excess anyway is also about one in ten. Asked directly, about three times as many describe one, and most of those also name a gap. These are different kinds of evidence: the consolidation analysis counts buyers who raised consolidation anywhere in an interview without being asked, the gaps-only question records excess raised without being offered, and the both-ways question records excess after it was offered. None of them establishes how many companies overspend or are actively cutting tools. Separately, about one in six answers to the both-ways question mention a consolidation or clean-up effort underway or planned. That is a reported activity or intention, not the same as perceiving excess, and it does not show that any tool has been retired.
What gaps do buyers name?
About three-quarters of buyers asked both ways name a gap, and about one in five of those does not say what it is (we definitely have gaps). The shares below classify the answers that identify a specific gap, each one once: a kind of tool they do not have, making existing technology work, a better version of a tool they have, or more than one of these. They are the buyer's stated problem, not an assessment of what to buy.
| Gap classification | Share | What it looks like |
|---|---|---|
| A kind of tool they do not have | 43% | No loyalty platform, no attribution model, no enterprise AI tool |
| Making what they own work: connecting it, using it fully, having the people to run it | 28% | The tools exist but do not talk to each other, or nobody has time to run them |
| A better version of a tool they have | 18% | A platform that works but not well enough, or costs too much effort to manage |
| More than one of these | 11% |
A missing kind of tool is the largest group, and the areas named most often are customer data and personalization, measurement and attribution, and AI. For how often buyers already in the market are buying a first tool rather than replacing one, see replacing or buying first.
About 28% of the specifically described gaps are mainly about making existing technology work: connecting systems, getting the team to adopt tools, or having enough skilled people. These buyers are not mainly naming a missing category. Some may still need implementation services, integration technology or more spending, but the interviews do not show that another primary platform is the fix. A CRM leader at a consumer brand answers the question this way: “I actually do think I have enough technology.” The limit is elsewhere: “the challenge for me is really the team,” with too few experienced people to set tools up and monitor them.
What does too much mean?
Among the buyers who describe too much in some form, about four in ten describe general software or vendor sprawl without naming duplicate capabilities. About a third describe tools doing overlapping jobs, and roughly one in six describe products they pay for and do not use. The rest do not say which. These groups classify each buyer's main concern, not verified duplication or measured license waste, and a company can have several of these problems even when its answer sits in one group. A separate finding cuts across the groups: about 15% of all answers to the both-ways question describe tools or features the buyer believes are underused, framed either as too much or as a problem getting value from what they own. That broader measure is not the same as the smaller excess group describing paid-for tools they do not use.
An ecommerce director at an outdoor-equipment manufacturer puts the overlap case most sharply: “we are over-resourced and under-leveraged.” The detail is duplication, “we have a lot of duplication in multiple systems, and that duplication is causing extra work,” and this buyer's plan is to cut first and look for gaps after.
The counter-current: too much and not enough describe the same stack
The answer the question seems built to separate is the one buyers give most when offered the choice. Six in ten of the buyers who describe too much also name a gap. An ecommerce VP at a specialty apparel brand: “I think we have too much tech in some areas, and I don't think we have enough in other areas.” A restaurant group's marketing director is re-evaluating where to consolidate and adds: “I don't know if it's too much. It just might not be what's right.” For many buyers, too much is about particular parts of the stack rather than every category.
Company size. Buyers at companies with 1,000 or more employees describe too much somewhat more often than those at smaller ones, about four in ten against three in ten, and less often say the stack is about right. That is suggestive, but the sample does not establish that larger companies generally have more sprawl. For how the stack itself differs by size, see how company size shapes the stack.
Want your own stack read the same way?
Get mine →What this means if you are reviewing your stack
These recommendations are ours: implications of the buyer answers, not a validated audit process that interviewees describe. The large difference between the two wordings suggests that asking only about missing capabilities may miss overlap or underuse. A useful review asks about both directions explicitly, then checks the problems people report against actual usage, cost and capability data:
- Where are we missing capabilities, and where might we have more than we need? Ask both explicitly, and give stakeholders room to raise problems in different parts of the stack. The interviews show excess is reported more often when the question mentions it, but not what any one person would say under the other wording, so follow up and check against usage data.
- Does each gap need a missing capability, a replacement for an inadequate tool, or better use of software we own? Classify it before choosing a fix. A missing capability might mean a purchase, an inadequate product a replacement, and an integration, adoption or staffing problem operational work or services. Each has different costs, owners and risks.
- Could software we already own meet the need? Check existing capabilities, licenses, integrations and usage before buying another platform. If the function exists but is not deployed or adopted, find out why and what fixing it would cost; a new purchase may run into the same implementation problem.
- Is the perceived excess duplicated functionality, underuse, or vendor-management load? Confirm overlap by comparing what each tool actually does and what depends on it. Verify underuse through usage and license records. For vendor sprawl, weigh the administrative load against the value of specialist capabilities. These are different problems with different decisions, and none of them means automatic consolidation.
- Who owns the decision, and when can changes happen? Identify the business owner, technical owner, budget authority and contract dates, and confirm whether the aim is lower cost, more capability, simpler integrations or changed responsibilities. A tool kept for one important function may still earn its cost, and overlapping tools become candidates for consolidation only once their dependencies are understood; why buyers keep software they rate poorly covers the reasons buyers give for keeping one.
What not to read into this
That a third of companies have too much software. The shares are what buyers said in answer to one question in an interview, not a count of tools or an audit of spending. A buyer can describe too much where an audit would find little waste, and the reverse.
That one wording gives the true answer. The gaps-only wording is not the honest baseline, and the both-ways wording is not inflated. One may hold back answers and the other may prompt them. The two were asked in different interviews, and the checks above make company size and timing unlikely explanations, but they do not cover every difference between the groups asked.
That this contradicts the one in ten who raise consolidation unprompted. That figure counts buyers bringing it up anywhere in an interview without being asked. This page counts answers to a question that offers it. The two measure different things, and the unasked share here is close to it.
That every reported gap is a missing product or a vendor failure. Some gaps describe missing capabilities; others describe integration, adoption or staffing problems with tools the buyer already owns. A buyer saying two systems do not talk to each other is describing the implementation, not necessarily a limit of either product. The interviews identify perceived problems, not which remedy fixes them.
That larger companies have more excess. The difference by company size points that way but is within what chance could produce in a sample this size.
Common questions
Do companies have too much software?
About a third say so, and most of them also say something is missing. When Alium asks buyers whether they have all the technology they need, whether there are gaps, and whether they have too much, about 36% describe too much in some form: about 14% too much and nothing missing, and about 22% too much in some areas and a gap in others. About half name only a gap, and about one in eight say they have what they need. This is what buyers say in an interview, not an audit of their stacks.
What gaps do companies have in their tech stack?
About three-quarters of buyers name one. Of the gaps buyers describe specifically, about four in ten are a kind of tool they do not have at all, most often for customer data and personalization, measurement and attribution, or AI. About 28% are mainly about making technology they already own work: connecting it, getting the team to adopt it, or having enough skilled people to run it. About one in five is a better version of a tool they already have. The rest mix more than one kind.
Does asking about too much tech change the answer?
The answers differ substantially between the two wordings. When the question offers too much tech as an option, about 36% of buyers describe an excess. When it asks only about gaps, about 10% raise one on their own, and the share naming only a gap is about three in four rather than about half. The share saying their stack is about right stays similar, at 13% against 14%. The two wordings were asked in different interviews rather than assigned at random, so this is a difference between observed groups, not a measured effect of the wording. It appears at both smaller and larger companies and in each year from 2024 to 2026.
How many companies are consolidating their tech stack?
It depends on how you ask. Across Alium's interviews about one buyer in ten raises consolidation unprompted, a share that has held steady since 2023. Asked directly whether they have too much tech, about a third describe too much in some form, and most of those also name a gap. Separately, about one in six answers to that question mention a consolidation or clean-up effort underway or planned, which is a stated activity or intention rather than evidence that tools were retired. None of these figures establishes how many companies are actually cutting tools.
How should you review your stack for gaps and overlap?
Our recommendation, not a practice buyers describe, is to ask about gaps and excess explicitly, because answers differed a lot between the two wordings, and then check what people report against usage, cost and capability data. For each gap, decide whether it needs a new capability, a replacement, or better use of tools you already own, since those have different costs and owners. For each excess, separate overlap, underuse and vendor load, and check usage and contract dates before cutting. Before buying to fill a gap, check whether something you already pay for could do the job.
For the buyers who raise consolidation on their own and where the cut tools go, see the great consolidation; for why a poorly rated tool stays, why buyers keep software they rate poorly; for first purchases against replacements, replacing or buying first; and for how the stack changes with company size, how company size shapes the stack.
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.