Paligo is a component content management system (CCMS) that helps teams manage complex technical documentation through structured authoring, content reuse, and controlled publishing.
$4,800
per year per seat
Pendo.io
Score 8.4 out of 10
N/A
Pendo.io is a product engagement platform with features for in-app analytics, surveys and feedback, and guidance.
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.
Pendo.io is useful in generating great dashboards that present user analytics in the best possible view that could be used for analysis & derive key insights on what could be done if there's a feature that's not being recognized by end users or if there are any pain points where users are struggling more around a workflow which is technically not that difficult. Pendo.io also can be used to create impactful guides where intercatoin of a user with the Guide can be created in less steps & have relevant information about that workflow that the user is completing. Pendo.io's resource center can act as a one stop hub to present any sidewide updates which could be information of Prod releases, New KB Articles, Register to any event, & much more. Segments can be created in as many variation as one can. In fact, Segments are the ruling property or feature that works so handy, which reduces a lot of iterative work.
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
Preview is problematic if the Pendo.io user doesn't have access to the target environment or application where the guide is going to display
It would be ideal to have a gallery of thumbnail images of previously used guides to select from, either to pull a screen capture or to use as a template. It's cumbersome to go to the guides, find the one you want, click on Preview, etc.
We have had an excellent experience with Pendo. When we've had questions or concerns, Pendo is very quick to respond and communicate with us. We have experienced top-notch customer support and customer engagement. We have actually modeled some of our implementation and product processes after Pendo's examples.
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.
It is intuitive for core tasks like tracking feature usage, building Guides, and viewing dashboards. The interface is clean and well structured, making it easy for product managers and operational teams to get value quickly without heavy technical support. However, there is a noticeable learning curve when setting up advanced custom events, reports, or integrations, which can take some time and internal knowledge-sharing to master.
Every time I have logged into Pendo, the service has been available for me to use. The page has never been down when I am trying to get info from there.
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
They've been great anytime that we have needed help with something. They also have some really great help articles. We're able to figure most things out through their articles, but when we've had to call in they've been very helpful and we haven't had any problems. I'd highly recommend working with them.
The training schedule was well thought out and tailored to meet our needs. Chantelle stayed with us through the whole implementation and made sure that we were good to go.
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 have just very superficial experience with Google Analytics but I do believe that Pendo.io is a much much better tool in pretty much all aspects of it. It has a ton more features and capabilities and even for the capabilities where there is overlap, Pendo seems to come out ahead easily. There are aspects that Pendo could improve for sure such as what metadata it captures from the users; an example of this is screen resolution which Google Analytics captures but Pendo does not.
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. :)
Reducing development time with in-app guides and resource center, with product management being able to agilely create guides in real time, this could be as much as 1 full time developer in savings.
Reducing business time scoping "rock fetches" than are proven to be invaluable based on analytics, each time 1 single piece of analtical data saves around ~20 hours across multiple resources.
Increasing user satisfaction with in-app guides and resource center
Increasing usage of key features through targetted messaging, those key features either drive costs ou of our business or add value to customers business.
