Freedom CMS vs Basecamp

• Hosting and maintenance is taken care of. Due to it being proprietary software, everything is built to work together.
• Simple to use. Basic functionality for websites is built in without having to dig through thousands of potential options.
• Development is straightforward...no backend languages required. So if someone wants a unique layout for a portfolio, it's very simple to add a new content type and build the new layout using basic html and css.

Read full review

• Task management - It is very easy to add, organize and discuss tasks within Basecamp's interface.
• The "Campfire" function is great for communicating when you just have a quick question for someone on the team.
• Notifications - Basecamp lets you decide how often and about what you'd like to be notified. The ability to respond to messages in Basecamp directly via email saves a lot of time.

Read full review

• Their preview setup for reviewing page changes prior to pushing them live is not good. You basically have to push things live to see how they will look, then go back and tweak it, while the changes in progress are live on the site. They need a sandbox, or a better preview feature within the backend so you dont have to keep pushing changes live to test out functionality.
• Integration with outside tools is non existent. Instead of trying to force people to use their modules or features it would make much more sense to more easily integrate with leading tools in niche spaces.
• The UI is pretty old. It could use a big refresh. Things like drag and drop builders and functionality should be standard these days. This is also a plus for non tech savvy users as it keeps their page structures to what works without letting people tinker. But if you want to tinker and be a higher end user Freedom isn't the best bet.

Read full review

• High Learning Curve. It's true that it can be easy to use, but to use well and effectively takes some time to learn. It's recommended to have an agreed-upon system in your team of what tools to use and when.
• Notification Overload. If people aren't careful they could send a notification to everyone when only a couple people were meant to be prompted. And since emails are sent by default, you could have your mailbox overloaded with unnecessary updates. This is where it takes a bit of training in your team to have an agreed-upon system.
• Lack of organization with Archived Projects. I will often need to reference an archived project to make a new one, but there is only a list of archived projects in alphabetical order, with no way to organize by archive date, or even search.

Read full review

• This was the first CMS we had at our company so hard to say positive or negative impact.
• Prior to this CMS there was a static site that html files had to be ftp to a company to have the site updated. So from that standpoint it made updating the site much less expensive.
• Compared to a tool like Wordpress this is much more secure and easier to manage, but since we outsource that portion of it to the company that built the site we dont realize those gains.

Read full review

• It has saved me time when having to get the same message out to multiple restaurants
• It has helped us make smarter operational decisions because we can all collaborate on an answer in a shorter amount of time (instead of calling a meeting!!!)
• The calendar function allows us to plot out our marketing agenda for the month and add/change it together as needed. The chef will post his recipe, the managers will cost it out, the social media manager will post pictures on it, and ultimately we will get that information out on an info sheet to the staff by printing the page.

Read full review