Clarizen is not a generic light tool for simply task scheduling and contact management. It is a serious project management software done by project managers for project managers.

It profoundly covers all aspects of project management, very customisable, with advanced reporting and custom fields.

There is always a room for improvement, Clarizen is relatively a new product that needs to build an ecosystem around it. That includes more integrations with other cloud services, 3rd party products in its marketPlace, and faster customer support.

One single platform where both project information and customer information meet, thanks to the Salesforce.com integration. This enables salespeople to keep a real-time view on margins and project progress, without them needing to ask a project manager for a status update or a meeting. The information is right there, up to date and accurate.

You need to make a solid business case and build a real plan to get the budget approved. Most companies have a lot of tools and some work together with others and... but none beat Clarizen if you ask me - it is a "one-stop" to get all information. So do the math to show you can save money by centralizing the tools, and that you can lower the time spent on managing different solutions. It helps if you show dashboards: management likes dashboards (and numbers). Clarizen was not so easy to explain to the whole team, it is a very complete solution. So we decided to "drip-feed" it to the teams.

Biggest benefit is "one source of truth".

The ease of use that comes from being a SaaS solution has been the strongest feature. In addition, because it is web-based, some of the configuration can be done using CSS, which does not take a lot of programmatic experience to implement.

As a PPM, there are still gaps (as of this writing) in some basic PPM functionality. The most glaring to me is the lack of Capacity Planning functionality. It can handle Resource Allocation, and Resource Loading, but if you are looking for a way to forecast out what your expected capacity for future work is, you can only do it through heavy configuration. As for configuration, it has pros and cons, but one of the more challenging limitations is in changing a custom field. If, for example, you decide that the data type on a field must be changed from string to number, you cannot simply change the data type. You must create a new field with the correct data type, find all the configuration instances where that field exists (in, for example, custom actions you've programmed Clarizen to take) and replace them, then delete the old field. It's a very clunky process. The last big con we have found is that there is no archiving of data. If you want to archive your data, you must dump everything out into a EDW of some sort. This is doubtlessly to keep the database slim, but that means that the system is always an "As Is" system, and you lose the ability to analyze trends.

Good. It was a disaster switching to Redbooth, and it was a major upgrade from Basecamp. Maybe it was too big of a jump for a smaller organization.

It's like the rolls royce of project management systems. Super powerful and hard to really throw stones at the functionality.

The biggest learning curve because it has specific ways that it manages workflows. It's great. But you need a dedicated team member to just learn and train people on it.