How many shoppers already run a system for the job?
It depends on what they are buying. Among buyers in Alium’s interviews who were shopping for a category when interviewed, about 19 in 20 email-platform shoppers and nearly nine in ten ecommerce-platform shoppers already run a system for that job. About three in ten CDP shoppers and under four in ten PIM shoppers do. For marketing mix models it is about one in seven, and for AI-visibility tools fewer than one in ten. These shares say who already has a system, not how many of those shoppers go on to replace it rather than add a tool beside it, extend it or drop the evaluation. The difference matters because an incumbent brings migration, contract and integration questions, while a first purchase means justifying the capability and deciding which workflows it takes over.
Three terms do the work on this page. A company is shopping when it was evaluating software in that category at the time of its interview. An existing-system shopper already runs a dedicated system for the job: a vendor’s product, one the company built, or one an agency operates for it. A first-time category shopper has no dedicated system, and the work is done by hand, in spreadsheets, or in software bought for another purpose. Within a category the two groups do not overlap. An existing-system shopper may mean to replace, supplement or extend what it runs, so an incumbent is not evidence of a replacement. A company shopping for several categories appears in each, and the shares are not adoption, churn or market shares.
Share of interviewed shoppers in each category, January 2024 through November 2026, who already used a dedicated system for that function: a commercial product, an internal build or an agency-operated system. The rest had no dedicated system, though they may do the work by other means. Each row covers several dozen to a couple of hundred shoppers; read the distance between the ends rather than the exact figures. The categories in between were not classified at the same detail, so they carry no figure and read as directional. None of these figures is a count of confirmed replacements.
At one end, nearly every shopper already has an incumbent. Nearly every company shopping for an email platform already sends email from one, and most companies shopping for an ecommerce platform already sell on one, a few of them on a site they built themselves. For these buyers the question is not whether to have the category. It is whether to replace or expand what they run, and what a move would cost. What drives those moves is covered in why companies switch email platforms and why brands replatform their ecommerce stack.
At the other end, most shoppers have no dedicated system. Among buyers interviewed since January 2024, AI-visibility tools appear mostly as first-time evaluations, with about 7% already running a dedicated product, and a marketing mix model is mostly a first dedicated purchase, though some shoppers run an internal or agency model. Both describe companies shopping now, not how widely the categories are adopted. Customer data and product information fall between the extremes: established categories in which most interviewed shoppers do not yet run a dedicated system. That does not mean they lack customer data or product information processes; those run on other tools and workflows, covered below. What is a CDP found the same thing from inside the category, with first-time CDP shoppers outnumbering those who already run one; the comparison with other categories is what shows how unusual that is.
Does a homegrown system count as an existing tool?
Yes. A dedicated system the company built counts as an existing system even though nothing was bought, and if it is later replaced it raises the same migration questions as leaving a vendor: the data and workflows to move, who maintains the old system through the transition, and how the new one’s results are checked against it. It matters most in two categories. About one PIM shopper in eight runs a system the company built itself, and in marketing mix models several of the few shoppers who already have a model built it in-house or have an agency run it. Both sit in the existing-system group even when they are buying their first commercial product.
Buyers talk about these systems much as they talk about a vendor they are ready to leave. A senior ecommerce director at an apparel retailer says of its product information system: “For PIM, we have an internally built solution.” It works, the director says, but “it is an okay system, but it is also not an industry standard tool.” A digital engineering director at a large US retailer weighed finishing its own build against buying: “we already have some half-built solution, but to have the complete capabilities, right, it takes more effort to build everything and more cost to maintain as well.”
The comparison question follows them too. A senior insights director at a large financial services company, piloting a vendor’s mix model against the one the team had built over the years, puts it plainly: “how do we compare the two?” And a marketing technology director at a financial technology company rates its in-house customer data setup “hardly one or two.” For how often companies move in each direction between building and buying, see build or buy.
What do first-time buyers use today?
Buying a first dedicated system does not mean starting from nothing. In these interviews the new system takes over a job something else was doing, and what that is differs by category.
| Shopping for | Systems the company built | What shoppers without a dedicated system use instead | Already runs one |
|---|---|---|---|
| Email platform | A few | Too few shoppers without one to describe | 96% |
| Ecommerce platform | About 1 shopper in 14 runs a site it built | Too few shoppers without one to describe | 86% |
| PIM | About 1 shopper in 8 | Spreadsheets, the commerce platform, manual onboarding steps | 38% |
| CDP | A few | The email platform’s profiles, the CRM, lists pulled from the data warehouse | 29% |
| Marketing mix model | Several of the few with a model built it or have an agency run it | Last-click, the ad platforms’ own reporting, experiments run with the platforms | 14% |
| AI visibility | None seen | The SEO program, sometimes run through an agency | 7% |
For customer data, the stand-in is another platform. Several CDP shoppers describe using an email platform’s profiles as a light CDP, or pulling lists straight from the data warehouse; one consumer brand that wants a CDP finds the customer data features in its email platform fall short. What is a CDP covers which alternatives buyers weigh first, and does your ESP replace a CDP covers where that arrangement runs out.
For AI visibility, the starting point is the SEO program. For first-time AI-visibility shoppers, the job sits in existing SEO work today rather than in a dedicated platform waiting to be replaced. About a quarter of AI-visibility shoppers name an SEO tool in their stack, and among those who answered whether the new category would complement or replace their SEO work, most said complement. These are expectations stated during an evaluation, not a finished adoption or proof that the two stay separate. A growth marketing leader at a restaurant and food brand: “I think it would complement it. I don’t think traditional SEO is completely going away.”
The counter-current: a first purchase for the company is not always a first for the buyer
A company buying its first dedicated CDP may have a buyer who has run one elsewhere, and a company without one today may have run one before. A growth marketing director at a media publisher that is now shopping for one says, “I previously worked with them in my last couple of businesses.” Another company is not using a CDP today but had one in the past. First here means the company has no dedicated system now, not that it is the buyer’s first experience or the company’s first exposure. Which tools buyers carry between jobs is covered in do marketing tools follow people to their next company?
Why the difference matters to a buyer
Existing-system shoppers and first-time buyers often face different questions. A confirmed replacement can mean migrating data and workflows, coordinating integrations and handling the contract. A first deployment may need a stronger business case, new staffing or processes, and proof that it beats the current workaround. The interviews illustrate the difference, but not every existing-system evaluation ends in a migration, and first purchases can have firm deadlines too.
A confirmed replacement often means migrating around an established system. The incumbent comes with integrations and a contract. Where a renewal or termination date constrains the decision, it can set the schedule; buyers with more room still face moving the data and the risk of the transition.
The migration is also what makes leadership hesitate. A senior CRM director at a global subscription food company, a year into pushing for a new email platform, says “any consideration, change, and migration is such an investment” that leadership is asking whether it will cost more than working within the platform they have. A DTC gifting brand puts its email move behind an easier SMS move because the platform it has run for nine years is “just intertwined into everything that we do,” which would make leaving it “a beast of a migration.” A DTC home and apparel brand weighing a new commerce platform is still “evaluating what it would take to make the transition, the costs involved, the external parties that we would need to contract with.”
A first purchase often begins with a business case rather than a migration plan. The work is explaining why current processes fall short, securing resources and deciding who will operate the system. Without an incumbent contract or another outside deadline, it can sit in budget discussions for a long time.
Readiness is part of the case. The chief digital officer of a consumer brand shopping for its first CDP says “we have to also be ready internally to operate it.” A sales and marketing vice president at an online retailer calls a mix model “a newer thing for us,” at a company that places a lot of value on last-click attribution, so anything new “has to really be grounded in experiments.” And a digital commerce leader at a global consumer-goods company starts its first AI-visibility evaluation by measuring where its brands stand: “This is such a new space for us.”
Want a review of your own stack?
Get my review →What this means for your evaluation
Our recommendations, drawn from these accounts rather than from a standard process buyers describe. Start with the actual starting point: a vendor’s system, one you built, one an agency runs, or none. If a system exists, settle whether you mean to replace it, add a platform beside it or extend it. The category’s proportions are context, not a verdict on your company: an email-platform shopper can be buying a first, and a PIM shopper may be retiring a build.
- If you are replacing a vendor’s product, map its integrations, data, workflows and downstream dependencies before you compare vendors, since that is the work the move has to carry. Confirm the renewal date, notice period, termination terms and any overlap you will need, and cost migration, testing, training, disruption and parallel running next to the licence. Where a contract date applies, plan backwards from it, as the head of CRM above did, rather than assuming every replacement finishes at renewal.
- If you are replacing something you built or an agency runs, treat it as a production dependency: who maintains it, what data and logic it holds, which outputs must stay comparable and how the replacement will be validated. For an internal mix model, compare the new model’s assumptions and results with the existing one rather than assuming the vendor’s is better, which is the question the financial services buyer above was asking.
- If you are adding a second system or extending the one you have, define the new capability and what the existing platform keeps doing. Test whether the two must share data, audiences, workflows or reporting, and whether running both duplicates cost or creates conflicting records. Adding software is a different project from retiring an incumbent.
- If you are buying a first, define the problem and today’s workaround before the shortlist, since the fashion director above describes getting budget by proving the problem. Name who will own the platform, the internal skills it needs and what measurable improvement would justify it. Then compare vendors with what you use today, whether spreadsheets, manual steps, email-platform profiles, last-click reporting or the SEO workflow, not with an empty stack.
- Whatever the purchase, set decision milestones. Without an incumbent contract, decide when the business case, the evaluation, budget approval and the implementation decision should be done; otherwise a first purchase can sit across several budget cycles, as the CDP example above shows.
For the evaluation itself, how software buyers find vendors covers how shortlists form, and the category pages carry the detail: what PIM buyers wish they’d known, what MMM buyers wish they’d known and what is answer engine optimization.
What not to read into this
Four inferences go further than the data. The first is that a low share means a category is unpopular or a high one that it is saturated: the shares describe the buyers shopping for each category, not how many companies use it. The second is that every buyer who already runs a system is replacing it. The analysis identifies whether a dedicated system was in use; it does not separate confirmed replacements from additions, expansions or evaluations that never end in a purchase. The third is that first-time buyers have no way of doing the job today; in the interviews many do it with a spreadsheet or a tool bought for something else, which is why those are counted as having no dedicated system. The fourth is that the categories in between sit at an exact point: they were placed from vendor products alone, which misses homegrown systems, so read them as leaning one way rather than as figures.
Common questions
Do most software buyers already have a system, or are they buying their first?
It depends on the category. In Alium's interviews about 19 in 20 buyers shopping for an email platform already run one, and nearly nine in ten shopping for an ecommerce platform do. About three in ten CDP shoppers and under four in ten PIM shoppers already run a dedicated system, and fewer than one in six shopping for a marketing mix model or an AI-visibility tool do. These are shares of buyers who were shopping when interviewed, not of all companies, and already having a system does not mean the buyer has decided to replace it.
Does a homegrown system count as an existing tool?
Yes. A dedicated system the company built counts as an existing system even though nothing was bought, and if it is later replaced it raises the same migration questions as leaving a vendor. It matters most for product information and marketing mix models: about one PIM shopper in eight runs a system the company built itself, and several marketing-mix shoppers already run an in-house or agency-run model, so they count as existing-system shoppers even when buying their first commercial product. A spreadsheet, or a tool bought for something else that also does the job, is not counted as a dedicated system.
Do companies shopping for a CDP already have one?
Mostly not. In these interviews about three in ten buyers shopping for a customer data platform already run one, counting the few that built their own. The rest have no dedicated CDP, in several cases while an email platform’s profiles, a CRM or the data warehouse covers part of the job. Nearly every email-platform shopper, by contrast, already runs an email platform.
How is replacing software different from buying it for the first time?
Buyers moving off an incumbent often talk about contract end dates, migration effort and what the old system is wired into. Buyers making a first purchase talk about building the case for budget, proving the problem, and whether the team is ready to run it. Not every evaluation of an existing system ends in a migration, and a first purchase can have a firm deadline too. Our recommendation, not a practice buyers describe, is to plan a replacement around its contract terms with migration, testing and any overlap costed alongside the licence, and to build a first purchase around a written problem, a named owner, the workaround it has to beat and a date for each decision.
Are companies buying AI visibility or answer engine optimization tools for the first time?
Almost all of them. Fewer than one in ten buyers shopping for an AI-visibility or answer-engine tool in these interviews already run a dedicated one. That describes companies shopping now, not how widely the category is adopted. Asked whether the new category will complement or replace their SEO work, most of those who answered say complement, at least for now.
Related reading: build or buy, on which systems move in-house and which move to vendors; what is a CDP; why companies switch email platforms; why brands replatform their ecommerce stack; and email platform migration timelines.
A tech stack review, powered by the buyers who've been there
What matters most to you, a shortlist for your stack, and the next steps to take — built from hundreds of verified buyer interviews.
Get my stack reviewFree · no password · your answers are anonymized before they inform research like this.