Senior Project Engineer at a tech vendor with 10,001+ employees
Real User
Top 20
Dec 30, 2025
Moving forward, every organization needs to have Adobe Experience Manager license wherein the work can be done in a shorter period of time and achieve a lot of things with this tool. It is advised to have up-to-date information on Adobe because there are many updates available that can achieve more while developing and enhancing sites. Keeping up-to-date with Adobe's official sites is necessary. This review has a rating of five out of five.
If your org is considering Adobe Experience Manager, the first thing I’d say is: don’t buy it just because it’s “enterprise” or because Adobe sold you the vision.
AEM works really well when you actually need it. Multiple sites or regions, strict approval workflows, large content teams, personalization, and long-term digital scale. That’s where teams like NetEffect usually see it pay off.
A few practical tips:
Get your content model and workflows right before implementation. Fixing this later is painful.
Use Core Components as much as possible. Over-customization is where costs spiral.
Make sure you have internal ownership. AEM isn’t a set-it-and-forget-it CMS.
Think long-term. AEM is a platform decision, not a short-term website refresh.
How would I rate it?
For the right use case: 8/10. It’s powerful, flexible, and reliable at scale.
For smaller teams or simpler sites: 4/10. It’s usually more than you need.
Bottom line: AEM can be a great investment, but only if your complexity justifies it. Otherwise, simpler CMS options will serve you better.
I do not have much experience with pricing, setup cost, and licensing. I have been working in my current field for almost six years. I find this interview too long and it should be shorter to make it more brief. I gave Adobe Experience Manager a rating of seven out of ten.
Senior Technical Program Manager /Senior Lead Solution Architech- Product Technology & Gen AI at a insurance company with 10,001+ employees
Real User
Top 10
Oct 24, 2025
I have been working with Adobe Experience Manager and other technologies including SaaS-based developments, apps, and web within the last 12 months. Adobe Experience Manager is primarily customized development, which we handle internally, occasionally seeking Adobe's assistance for specific products or solutions used for IAM development purposes. We run sanity suits daily across multiple platforms seeking segmentation, using custom tools and harvesting for testing purposes. We implement content strategy through our internal portal. We have a matrix portal providing complete updates and a dashboard for tracking. We monitor the number of URLs being published, workflow progress, dispatcher status, and issue resolution frameworks. A monitoring framework has been implemented to oversee these aspects. I rate Adobe Experience Manager a nine out of ten.
Digital Asset Specialist at a retailer with 10,001+ employees
Real User
Top 20
Aug 25, 2025
My company has a partnership with Adobe with engineers and sales representatives assigned to a beauty products corporation. I would recommend it to large companies with a big budget, and I would recommend it to digital asset managers with experience in Adobe Experience Manager because it would be good for their career. On a scale of one to ten, I would rate Adobe Experience Manager an eight.
For any investment, it's important to understand what you want to do and what your targets are. The system should fit into your IT environment and also align with your business strategy. This makes your implementation smoother and more successful. I'd rate the solution eight out of ten.
For web applications with frequently changing content where business people need to make modifications without technical knowledge, Adobe Experience Manager offers significant advantages. I'd rate the solution nine out of ten.
It's easy to use, but it requires knowledge of data structure, data modeling, and SQL coding. Familiarity with the relationships of the data set is also helpful. I would recommend using it. If you have an online, offline, and multi-store business, a multi-city level of business, like a global banking business, Adobe is a good platform. You can utilize it, and once you use AEP, it will be helpful. You can centralize the data from batch data and any digital assets as well. Overall, I would rate it a ten out of ten.
Before using it, you should have some hands-on experience. Someone should show you a two-day demo of what a developer actually does, how exactly do we use it? If you understand how to use it, then it can be beneficial for development as well. Understanding how to use it allows to explain to clients the use cases where Experience Manager is effective. It is easy to learn. You don't need to be an advanced Java developer. With basic Java knowledge and about 15 days to a month of AEM training, including a week or two of hands-on experience, you should be good to go. Overall, I would rate the solution an eight out of ten, especially considering AEM as a Cloud Service. The best part is the seamless integration with other products. Everything is connected. In my current company, we just started using Adobe Target, and the integration with Experience Manager is very smooth. This, combined with how easy it is to manage digital marketing and publish content, is why I give it that rating. Development happens once, but maintenance is ongoing, and AEM makes maintenance simple.
Ux designer & content strategist at Eni gas e luce
Real User
Dec 21, 2023
A team of three or four developers is needed for the solution's deployment and maintenance. Users must set up a team with all the professionals they need to use the product and create their website. Overall, I rate Adobe Experience Manager an eight out of ten.
I use the solution’s online version licenses. Adobe Experience Manager is deployed on-cloud in our organization. People could use Adobe Experience Manager if pricing is not a challenge for them. Before using Adobe Experience Manager, people can start with free tools like Inkscape, Pencil, or Sketch. Overall, I rate Adobe Experience Manager an eight out of ten.
Senior Technical Consultant at FinXL IT Professional Services
Real User
Oct 12, 2022
Because of the improvement needed with the client-side framework and because page loading takes time, I rate Adobe Experience Manager at seven out of ten.
Adobe Experience Manager requires maintenance, but the client side takes care of it. Even during the deployment, the client joined the call, and any needed improvements will be made from the client side, for example, migrating from one server to another. Hence, the maintenance of Adobe Experience Manager is the client's responsibility. My company has one project on Adobe Experience Manager, with a team of forty people working on different parts. My advice to anyone planning to implement Adobe Experience Manager is that it has a broad scope in terms of usage, so I recommend that you learn about the solution before implementing it, especially if you have a lot of clients for it. My company has a partnership with Adobe. I'd rate Adobe Experience Manager as ten out of ten.
Chief Technology Architect at a tech services company with 1,001-5,000 employees
Real User
Aug 4, 2020
Adobe is a more expensive solution than, say, Liferay. But we don't like the portal approach in Liferay, it's quite old. We've worked on our portal CMS since 2010, so it's been over 10 years. In Liferay, the core is still based on portal frameworks which is a disadvantage because we know that to develop something with that model is quite expensive. In general, our employees are more familiar with Adobe and have more confidence using that solution. I would rate this solution an eight out of 10.
Adobe Communique 5 (Adobe CQ5), currently manifested as Adobe Experience Manager (AEM), is a web-based content management system which is developed to help businesses in offering high-end digital experience to their customers.
Moving forward, every organization needs to have Adobe Experience Manager license wherein the work can be done in a shorter period of time and achieve a lot of things with this tool. It is advised to have up-to-date information on Adobe because there are many updates available that can achieve more while developing and enhancing sites. Keeping up-to-date with Adobe's official sites is necessary. This review has a rating of five out of five.
If your org is considering Adobe Experience Manager, the first thing I’d say is: don’t buy it just because it’s “enterprise” or because Adobe sold you the vision.
AEM works really well when you actually need it. Multiple sites or regions, strict approval workflows, large content teams, personalization, and long-term digital scale. That’s where teams like NetEffect usually see it pay off.
A few practical tips:
Get your content model and workflows right before implementation. Fixing this later is painful.
Use Core Components as much as possible. Over-customization is where costs spiral.
Make sure you have internal ownership. AEM isn’t a set-it-and-forget-it CMS.
Think long-term. AEM is a platform decision, not a short-term website refresh.
How would I rate it?
For the right use case: 8/10. It’s powerful, flexible, and reliable at scale.
For smaller teams or simpler sites: 4/10. It’s usually more than you need.
Bottom line: AEM can be a great investment, but only if your complexity justifies it. Otherwise, simpler CMS options will serve you better.
I do not have much experience with pricing, setup cost, and licensing. I have been working in my current field for almost six years. I find this interview too long and it should be shorter to make it more brief. I gave Adobe Experience Manager a rating of seven out of ten.
I have been working with Adobe Experience Manager and other technologies including SaaS-based developments, apps, and web within the last 12 months. Adobe Experience Manager is primarily customized development, which we handle internally, occasionally seeking Adobe's assistance for specific products or solutions used for IAM development purposes. We run sanity suits daily across multiple platforms seeking segmentation, using custom tools and harvesting for testing purposes. We implement content strategy through our internal portal. We have a matrix portal providing complete updates and a dashboard for tracking. We monitor the number of URLs being published, workflow progress, dispatcher status, and issue resolution frameworks. A monitoring framework has been implemented to oversee these aspects. I rate Adobe Experience Manager a nine out of ten.
My company has a partnership with Adobe with engineers and sales representatives assigned to a beauty products corporation. I would recommend it to large companies with a big budget, and I would recommend it to digital asset managers with experience in Adobe Experience Manager because it would be good for their career. On a scale of one to ten, I would rate Adobe Experience Manager an eight.
We are using version 6.5 or higher of Adobe Experience Manager. Overall, I would rate this solution 7 out of 10.
For any investment, it's important to understand what you want to do and what your targets are. The system should fit into your IT environment and also align with your business strategy. This makes your implementation smoother and more successful. I'd rate the solution eight out of ten.
For web applications with frequently changing content where business people need to make modifications without technical knowledge, Adobe Experience Manager offers significant advantages. I'd rate the solution nine out of ten.
Maintenance depends on the volume of the work. Overall, I rate the solution a nine out of ten.
It's easy to use, but it requires knowledge of data structure, data modeling, and SQL coding. Familiarity with the relationships of the data set is also helpful. I would recommend using it. If you have an online, offline, and multi-store business, a multi-city level of business, like a global banking business, Adobe is a good platform. You can utilize it, and once you use AEP, it will be helpful. You can centralize the data from batch data and any digital assets as well. Overall, I would rate it a ten out of ten.
Before using it, you should have some hands-on experience. Someone should show you a two-day demo of what a developer actually does, how exactly do we use it? If you understand how to use it, then it can be beneficial for development as well. Understanding how to use it allows to explain to clients the use cases where Experience Manager is effective. It is easy to learn. You don't need to be an advanced Java developer. With basic Java knowledge and about 15 days to a month of AEM training, including a week or two of hands-on experience, you should be good to go. Overall, I would rate the solution an eight out of ten, especially considering AEM as a Cloud Service. The best part is the seamless integration with other products. Everything is connected. In my current company, we just started using Adobe Target, and the integration with Experience Manager is very smooth. This, combined with how easy it is to manage digital marketing and publish content, is why I give it that rating. Development happens once, but maintenance is ongoing, and AEM makes maintenance simple.
A team of three or four developers is needed for the solution's deployment and maintenance. Users must set up a team with all the professionals they need to use the product and create their website. Overall, I rate Adobe Experience Manager an eight out of ten.
I use the solution’s online version licenses. Adobe Experience Manager is deployed on-cloud in our organization. People could use Adobe Experience Manager if pricing is not a challenge for them. Before using Adobe Experience Manager, people can start with free tools like Inkscape, Pencil, or Sketch. Overall, I rate Adobe Experience Manager an eight out of ten.
Because of the improvement needed with the client-side framework and because page loading takes time, I rate Adobe Experience Manager at seven out of ten.
Adobe Experience Manager requires maintenance, but the client side takes care of it. Even during the deployment, the client joined the call, and any needed improvements will be made from the client side, for example, migrating from one server to another. Hence, the maintenance of Adobe Experience Manager is the client's responsibility. My company has one project on Adobe Experience Manager, with a team of forty people working on different parts. My advice to anyone planning to implement Adobe Experience Manager is that it has a broad scope in terms of usage, so I recommend that you learn about the solution before implementing it, especially if you have a lot of clients for it. My company has a partnership with Adobe. I'd rate Adobe Experience Manager as ten out of ten.
Adobe is a more expensive solution than, say, Liferay. But we don't like the portal approach in Liferay, it's quite old. We've worked on our portal CMS since 2010, so it's been over 10 years. In Liferay, the core is still based on portal frameworks which is a disadvantage because we know that to develop something with that model is quite expensive. In general, our employees are more familiar with Adobe and have more confidence using that solution. I would rate this solution an eight out of 10.