Butter CMS Pricing Overview

1. Butter CMS requires minimum coding from developers in order to be integrated into existing projects. 2. The interface is straightforward and simple to use, so even non-technical people can manage information with no difficulty. 3. To meet the unique requirements of each user, Butter CMS provides a wide range of configuration choices. 4. Butter CMS was built with speed and dependability in mind, so material can be loaded and modified rapidly. 5. Butter CMS is a flexible content management system that offers reasonable price, making it a good option for new enterprises and those on a tight budget.

1. Butter CMS's limited feature set in comparison to other content management systems may not be sufficient for more complicated websites. 2. The insufficiency of third-party plugins for Butter CMS may restrict its capacity to meet certain needs. 3. As Butter CMS does not come equipped with its own analytics features, customers will need to rely on a third-party service for this purpose.

Butter CMS's user interface is straightforward, so even non-technical people may edit their website's content without much trouble. There's no longer a requirement for highly specialised technical expertise, which can be a significant time and money saver. Butter CMS is very adaptable because of the extensive configuration possibilities it provides. This paves the way for a more tailored and efficient website, which in turn may increase user involvement and yield better outcomes. With its flexible API, Butter CMS may be easily integrated with a broad variety of other systems, saving time and effort for developers. This has the potential to enhance the user experience, cut back on development expenses, and save time. Butter CMS is optimised for speed and reliability, so our site's content will load quickly and we have no trouble making updates. This has the potential to increase user retention and lower bounce rates. Cost-effectiveness: Butter CMS's tiered pricing structure makes it a feasible option for solopreneurs, non-profits, and other organisations with limited budgets. Users may reap the benefits of a robust and versatile platform without having to empty their financial accounts in the process.

Very responsive customer service. Butter CMS has made me feel like they value feedback and really want to help me succeed with their product. I asked a question, and they responded quickly, made some suggestions, and even arranged a Zoom meeting to discuss my needs in detail. They even decided to implement a feature that I requested, and kept communicating with me through the process. I've never experienced that from a company before. That service builds loyalty, because even if there's a bug or feature that doesn't exist, I have confidence that they will listen to me and try to help me find a solution.

The api is less complete than I was hoping for. (But that's getting better!)

I'm using it to store dynamic content for our app, so we can change lots of things w/o needing to do an app update. The UI is very simple and easy to coordinate with team members

The ability to publish, manage or update content without the help of our engineering team. Great documentation and customer support. Overall, great value at a great price.

Implementation is still a bit too technical for me to really say, with authority, that I dislike anything.

Removing the need for a WordPress blog and a redirect. Our ultimate goal was to gain the SEO benefits of having all keyword-rich content on our domain and Butter helped us do it with ease.

I've developed in nearly every legacy CMS from Umbraco to Wordpress and drupal to e-comm specific CMS's like Shopify and Magento... but once you go headless, it is so hard to go back. Before Butter I even dipped my toe in the water with Contentful and other legacy CMS that claim to have headless capability (looking at your Drupal) but I eventually settled on Butter. Butter has one of the cleanest and easy-to-use API's on the market and a good balance between price and functionality, without the bloat of the past (headless drupal). Butter also has SDK's available for a whole host of languages making it even quicker to get to market. While Contentful does have more features at the present time, but it has the cost to come with it. While Butter does cater to larger companies, they are also more accessible in terms of price points than several of their competitors (Contentful included). Update and Improvements are also coming on at a good steady pace.

- It would be nice to have some additional "pages" vs price points across all their plans... contentful offers 25k "objects" even on their free tier. - A plug-in or Marketplace of add-ins would be nice to extend the capability of the CMS on the backend. E.g. SEO plugins, writing assistants, DAM's or Dropbox for asset upload etc. - Would be nice to have proxied DNS for CDN locations for images/assets etc, to improve the appearance and make it easier to re-wrap Butter into API's of our product.

- easy separation of concerns between content, code, and design/templates. - marketer and developer-friendly.

As an engineering leader, I'm most concerned about the technical effort required to implement tools. Butter was dead-simple - set it up, grab the API key, and call their endpoints when needed.

The only tricky thing was a minor issue; we wanted to be able to filter/search all of our posts/content or grab all of the headers so we could display a "home page" for our blog, but they didn't have that ability at the time. It might have been implemented since, but it was performant enough to load all of our content simultaneously.

If you're looking for a simple, lightweight, cost-effective CRM for a small-medium size business, Butter is it. We tried a few others and they were either way too heavy/complicated or didn't have basic features.

They really make me feel valued as a customer. They work WITH you. It's not as though it's their way or the highway. They have amazing documentation for a variety of web frameworks (I'm using Gatsby).

The only downside I've experienced so far is that you need the Business Plan for Localizations but like I said previously they were willing to work with me to come to a solution. Also, having the ability to create some structure for all your Collections would be helpful.

I was initially only thinking of using them for my blog content but now all the static information for my entire site is hosted with them. What a great way to organize you content. Localization management is also a huge boon and it brings my site accessibility to a new level.

Before Butter, we were locked into a self-hosted solution that commanded regular updates, plugin management, and a learning curve for any new joiners within our team reading documentation to get up to speed. We have just completed a website redesign project with ButterCMS as its backbone, one major plus we noticed from the get-go is the fact collections make it really easy to share data across the content platform. Our website is based on a component architecture and that was easily replicated in Butter using the component library, this was further advanced by re-using collections and for us, this has meant colors, image sizes, and other re-usable elements can be shared so our content editors can create pages quickly. From a technical point of view, we were able to get up and running in a matter of minutes using the API documentation and the ButterClient, after finding our feet using collections we were able to build a scalable architecture based on a React app. Since our website is built around component design, we now have a bunch of styled-components that allow any new pages to be quickly built up and deployed in minutes. This is mirrored in ButterCMS and therefore allows our content editors to build pages, send us the link and within minutes the page is created and live.

One of the biggest issues we're facing right now is the speed of the backend dashboard, this may be due to the number of collections we're running in order to create re-use of content across the platform. With that said the time-savings we get from architecting our content in this way far outway the degradation in the admin. It would be nice to see an easier way to manage collections to help page load times increase when managing content on the platform. Our second biggest gripe could be again down to how we've architected our solution, but since our components are mirrored both in code and the Butter component library it has meant when content editors build pages they are utilizing the drag and drop interface for the type builder. This process has two issues: - The first being that once a component is created, it cannot be updated, you are required to first add the component to a new/existing page, remove it from the component library, add your new field and then save it as a new component. It would be great if components could be edited which leads to our next issue (which is also true of page type configurations as well). - Secondly, if you edit a component that has been used on a page to add/remove a field this is then not reflected across all components where this instance is used. It would be great if the component schema could be shared across the board and those instances were used listed on the update to confirm where the changes will take effect.

The main issues we solved using butter was to migrate away from the old age problem or developing our own in-house CMS or absorbing the cost of licensing, running, and training our team on a platform that changed regularly. With Butter we're able to use our own architecture, coding standards and share content across multiple platforms from a single source.

Adding content to whatever framework you want is extremely easy with ButterCMS. I am very impressed with this workflow, and will recommend ButterCMS in the future.

There are certain features that are missing that would be desireable, but Nikki from ButterCMS is extremely welcoming on any feature requests, so I feel assured that feedback is listened to and considered.

We were able to create a generalized PageType with a bunch of "components" (writeable data groupings) that can be added to a "page" at will. Through this, we created complementing React components that would render each of these page components and consumed them in a constructor that would then render them in the order added in ButterCMS. This allows us to create any page we want via Butter, and then it will immediately be added to our website.