Adobe Experience Manager

if main concern is licensing cost, it is best to take the open source route (WordPress or Drupal), because you don't need to pay any license fee for using these software. As others might have stated, Adobe Experience Manager license fee could be costly and that doesn't even include development costs.

In WordPress ecosystem, plugin and theme developers are competing with each other to provide the best free plugins or themes for public use. Further, developers can provide support or more features added to plugins or themes when you pay a small fee for license.

The downside, although rarely happens, when there are conflicting themes/plugins it can cause your site to break. Another problem, when it comes to security, most often that you are at the pity of themes/plugins developers.

In Drupal ecosystem, its developers hold the famous principle, "not to reinvent the wheel" which is the reason why you won't find as many modules or themes. Drupal developers rarely competing with each other but instead they (even non-programmers) will work together to improve existing themes or modules. Obviously one module will not meet everyone's criteria, therefore in Drupal they have 'hooks'. A Drupal 'hook' can extend Drupal core's or module's functionality to meet your requirements.

I would tend to use Drupal but I think it is only a matter of preference. I admit that building on WordPress is easier while building on Drupal will require a lot of research and experience.

Word pres will be faster easier and cheaper than the other two. I have used all three. AEM is usually 250,000 for the license and about 3x that for the implementation. And that would still not include e commerce functions. Drupal we my favorite several versions ago but it is not backwards compatible with the shipping extension. Upgrades are terrible. And they have stopped focusing on the little sites only the big enterprise sites more of a competitor to AEM. Training on Drupal and AEM are also a lot more.

I hiiiighly recommend Segment. It's so incredibly fast an easy for a front-end developer to add - you can literally have it implemented in ~15 mins, and then you just tag the events you want to track, push the data to whatever tool you want.

One of the awesome things is that you can implement other tools (e.g. Intercom) through Segment with no additional coding - just add them in the Segment console. I use Mixpanel for product analytics, and Segment has flawlessly managed the data at a tiny cost.

Please don't do AEM - they're behind on features and cost more. I can't comment on Tealium but I've heard good things.

As for explaining DMP and CDP, I'd tell them that one is a generic term for how you manage your company's data broadly, and will consist of multiple ETL tools (usually this is term is used in relation to just marketing). CDP, because it's a much more narrow subset, provides specialised, simplified tooling that focuses on the way users interact with your software product. As a BI leader, I would recommend leadership start with something smaller like CDP, demonstrate success, then expand and build out your DMP over time.

Obviously, it will not be possible to advice here with little or no knowledge on the business needs. Every tool has it's pros and cons, and largely depends on specific needs. I can add few on Adobe Experience Manager (tool i've been working on for over 5 years): 1. AEM is an expensive tool (also consulting, dev teams come at high price) 2. Adobe is pushing a lot towards moving AEM into cloud. Most of your work will be on Adobe Cloud, though there maybe very few exceptions for some customers to have on-premise implementations. 3. There will be a steep learning curve. 4. Some of the advantages are that it is a very mature platform. You can get great resources and help on it. 5. Think in long term for this.. to realize TCO will take a while and will need Leadership to push/weigh-in/support. 6. There will be lot of custom development (not a lot of AEM's out-of-the-box is useful). 7. Development teams can find examples, help and resources. 8. The entire stack is built on open-source, so other than paying Adobe license fees no need to pay additional software license expenses.