Curata's content marketing platform (Curata CMP) enables more efficient content creation with greater impact on pipeline. According to the vendor, this solution enables users to:
Analyze marketing and sales pipeline impact: Instantly access content metrics such as leads generated/touched and sales opportunities generated/touched by gated, un-gated and off-site content. Streamline content production: An easy to use editorial calendar to keep your team on the same page and…
$699
per Instance (no seat limits)
Paligo
Score 9.9 out of 10
N/A
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
N/A
Pricing
Curata
Paligo
Editions & Modules
Curata Software
$699
per Instance (no seat limits)
No answers on this topic
Offerings
Pricing Offerings
Curata
Paligo
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
We have 2 solutions:
- Curata CCS content curation software
- Curata CMP content marketing platform (e.g., editorial calendar, analytics engine)
I liked Curata, but it depends on the use case of how it will be used as to how effective it is for someone. If you are trying to curate content it works great. Had I not been so put off by the issue mentioned earlier I would have given more effort to learn the CMS, so I am not sure how effective it really is.
Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.
Curata is great at curating in content that is relevant to our audience. It is easy to add many different sources to the feed from all around the web and we've really seen Curata "learn" what we see as the most relevant.
The microsite we got as part of our Curata subscription is really fantastic. It's very customizable and we've been able to really craft it to suit our needs. There are so many different options available and our Curata rep has been really great with helping us cater each piece to our vision while making helpful suggestions along the way in terms of best practices. Plus, the word processor for publishing blog posts is so easy to use and I've had no issues with it so far unlike many other CMS platforms I've worked with. The Curata microsite is actually going to be replacing our current blog very soon - we love it that much!
I've had a great experience with customer service from Curata. Our rep is responsive and helpful and really good about not just answering our concerns but also providing feedback on our processes and giving advice for how we can improve.
Search capabilities within the curated content feed are fabulous. This is one area where I found other solutions to be lacking when we were going through the sales process, but Curata really succeeds here. It's extremely easy to find exactly what you're looking for in your content feed.
The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
The amount of CSS/JS required to customize a site's appearance can be cumbersome
Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
For all of the features we loved when we signed on like the microsite and search capabilities and also their customer service, we will very likely renew with Curata. We also really like the evolution we have seen of the solution, just recently a new integration with Marketo (also a vendor of ours) was announced which will be very beneficial to us in optimizing our email newsletters
Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.
All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly
The main difference that made me choose Curata over Percolate is that it is not complex. Curata is easier to set up, to use, and to manage. It does not involve any complicated configuration to get the content and data you need. Curata technical support is amazing, to say the least. I am not an expert in the technical stuff, but I feel assured their team can help me out when I have an issue
We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.
I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)
