Crownpeak is a great CMS
Use Cases and Deployment Scope
We implement the websites of our customers with Crownpeak DXM. Our clients move to Crownpeak DXM because with their existing CMS they are not able to manage the customer experience and their systems are not flexible and agile. We do a full implementation of their websites: UI/UX Design, Front End Development, Back End Development, SEO, Tagging, Content Migration, and Testing. For example, a recent client wanted to move their 7 different websites (all having 60+ locales) from AEM to Crownpeak DXM. The reason was that AEM is very costly, it takes a lot of time to implement a change, is difficult to maintain, is not flexible, is not agile and AEM resources on the market are expensive. Crownpeak on the other hand is very flexible, agile, less costly (compared to AEM), very secure, easy to maintain, and has a good performance overall.
Pros
- Less time to market
- Easy to maintain
- Flexible
- Secure
- Good performance
Cons
- Better developer experience
- More technical documentation
- Instead of relying on 3rd party personalization (eg Dynamic Yield) invest in improving their own personalization capabilities
Likelihood to Recommend
Well suited for clients who want to move to a flexible and easy to maintain CMS. Not well suited for small and medium enterprises.
