There are a lot of cheaper options in the market, such as Dropbox. It camouflages itself as an enterprise management solution, but it is not. Enterprise content management is not about storing files. It's more about collaboration, workflows, version management, and security. It is where solutions like Dropbox fail.

At times, customers have a perception that they can do the same thing with Dropbox and wonder why they must invest so much in Documentum. Here, the value gap or communication is lost. We communicate the value of the solution to the customer. There is scope for reducing the cost to some extent. We cannot always expect organizations to have a minimum of 250 users.

For licensing, we can also look at organizations with 50 members. It's an entry point for us if they see value in it. We can always leverage other OpenText products.

OpenText Documentum has announced a new licensing model, which could be more expensive. We have a perpetual license, and I will see how that will work with the new licensing model.

Regarding pricing, although I'm not directly involved, I've heard from my manager that the pricing has improved significantly. The price is considered affordable now.

It falls in line with a lot of things that are out there on the market. There is nothing extraordinary in terms of great or bad.

OpenText Documentum's pricing is good.

Documentum's pricing is reasonable compared to some competitors like Palo Alto. However, there may be additional costs for support that need to be considered.

The price of Documentum could be lower. It's quite high compared to its competitors.

Governments organizations don't pay an annual cloud subscription licensing fee, most licenses for government organizations are perpetual.

Licensing according to organization scale. Captiva software in case of backlog archiving.

I'm not an expert on this but from what I know, the pricing and licensing model is strange and I'm not sure how well it is controlled. For example, paying by user capability (consumer, contributor, coordinator) makes sense when the user application is Webtop. But we can have a WDK solution or any other web-based solution where the user capability is completely irrelevant.

It is quite an expensive product. The price is very high.