Broadsign vs. Percussion CMS

Very suitable for large networks and projects requiring enhanced functionality. less suitable for small networks as the learning curve might be considerable.

Incentivized

Best suited for large organizations where everyone knows how to deal with Java in an increasingly Java unfriendly world. Said organization should be willing to pay a huge price for a piece of dinosaur technology

Incentivized

• Separate CMS environment publishes to remote server environment - great for security
• Highly scalable
• Full scale workflow allows for custom routing, approving, etc..

Incentivized

• One word: JAVA! We don't live in the 1990's anymore! An AJAX/DHTML environment seems a long time coming.
• Horrible end-user experience, learning curve. Our end users' inability to easily use the archaic, Java-based interface, means they send the web developer their content requests. This creates a huge bottleneck and completely defeats the purpose of a CMS.
• Image mangement and integration with content is aweful and time consuming. An image processing tool called ImedImage was developed for Percussion at one point, and left completely stagnant with very little support.
• Implementation is extremely complicated, given the complexity of the system. Sure, scalability is a good thing, but there is very little out-of-the box function. Don't expect to implement a site as quickly as with other CMS platforms.

Incentivized

We analyzed other solutions in 2008 but were convinced from the get go Broadsign would be a perfect fit for our needs in the long run. 15 years later our choice has been proven right.

Incentivized

No contest. I can't wait to get off of Percussion CMS.

Incentivized

• We are locked into Percussion CMS simply due to the expense and complexity of migrating to another solution (and the lack of time and budget to do so). I long for the day when I am no longer required to support Percussion CMS, to say the least.

Incentivized