Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Springbot
Score 6.0 out of 10
N/A
Springbot aims to bring all the marketing capabilities large retailers have to small businesses at a fraction of the cost. Through Springbot, online stores will be able to leverage automated marketing on channels such as email, SMS, social and online ads. Business owners and marketers who find themselves wearing many hats can still send the right message at the right time with confidence. With an all-in-one marketing automation platform designed with ease of use in mind, business…
$199
for up to 5,000 subscribers (includes email marketing, social hub, reporting and dashboards, signup forms, automations, account management, support and onboarding. See website for additional package options.
Squarespace
Score 8.4 out of 10
N/A
Squarespace is a CMS platform that allows users to create a DIY blog, eCommerce store, and/or portfolio (visual art or music). Some Squarespace website and shop templates are industry or use case-specific, such as menu builders for restaurant sites.
$25
per month
Pricing
Drupal
Springbot
Squarespace
Editions & Modules
No answers on this topic
Platform Base Package
$199/month
for up to 5,000 subscribers (includes email marketing, social hub, reporting and dashboards, signup forms, automations, account management, support and onboarding. See website for additional package options.
Basic
$25
per month
Core
$36
per month
Plus
$56
per month
Advanced
$139
per month
Offerings
Pricing Offerings
Drupal
Springbot
Squarespace
Free Trial
No
Yes
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
See website for pricing calculator for additional pricing options.
I've used Squarespace and WordPress for other businesses, and Drupal was honestly selected due to cost. It does a good job of scaling across our organization - and many units have benefited from having a space to provide content. Squarespace is more modern, and WordPress may …
I inherited Drupal from a developer who made the website for our nonprofit many years ago. It was increasingly obvious that it wasn't a fit for our organization, which has multiple staff and volunteers who need to edit or update the website but don't have coding experience. Wix …
Drupal excels at allowing seasoned programmers to really get creative with marketing initiatives in terms of working with a theme and the core code. That being said, it is definitely much more challenging for average developers and front-end builders to use, especially at …
Drupal is certainly a more complex animal, comparatively. But its power lies in its flexibility, extensibility, and stability. And the API is fantastic. There's really nothing else like it.
Between these products, as a developer I would most likely go with Drupal unless I had a very specific reason to go with something else. To put it simply, Drupal is capable of anything that these other products can do. It may take a little longer to configure it in some cases, …
Drupal is highly customizable unlike WordPress and Joomla. It may take a longer time to set up but it works well for the needs of the organizations it is set up for.
Again, Squarespace is the best option for small businesses seeking an e-commerce solution. If you need more robust features, look to Drupal or WordPress, depending on site size. Weebly or Wix are solid options for basic sites, but I personally have had significant issues with …
WordPress is much more flexible and offers a much broader and deeper range of capabilities that Squarespace. However, setting up a WordPress site can be quite time consuming in comparison, and you must commit to spending time regularly - at least once a month - to updating …
SquareSpace is infinitely easier to use than any CMS I've used before. It's more reliable and saves a lot of time. I wouldn't recommend SquareSpace for large e-commerce sites or big government sites, but for small business, it's ideal.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Squarespace is one of the best solutions out there for building a website or web experience that looks good, has great functionality and is cost-effective, even for smaller businesses. Although most people in marketing will find most of the elements intuitive, if the creator is struggling with any of the functionality, there are many, many support options and other users who can offer assistance.
The demographic data was great. I could see how many males vs. females, ages, income, married, with or without children. It gave me a good idea of who my customers were.
Using their tracking URLs in all of our campaigns allowed us to get a better idea of what exactly was driving revenue.
Not only could I see top performing products, which I can do within Magento, I could also see top selling categories and colors.
I can pull a Coupon Usage report our of Magento, but Springbot gave me additional info like AOV and ROI on those codes.
Springbot also gave me a lot of info about our abandoned carts. It shows us which products are most abandoned along with views, conversion rates, etc.
Springbot gave us an Instagram Shop page that allowed us to curate social shares and then tie them to products on our site.
Stupid simple to use. I know very creative people who cannot code and this is probably the easiest ever platform for them!
Pretty website templates and great functionality with showing off portfolios.
They've already figured out what are the problems that non-coding people have when creating websites and they've figured out a simple solution for all of it.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
After our purchase, I let spring or know that I was currently too busy to implement the system and to put things on hold. They ignored this request and kept charging us a monthly fee without using any of their systems. I have only logged in once. Nothing has been set up. They can see that from their side.
After multiple emails back and forth their out was in the user agreement. I never asked for my money back only credit so I can regroup and when I have time get on to implant the systems. They tell me they don't do that.
They don't care about any of the customer's needs. They only care about charging you that monthly fee. Terrible bus plan. With enough bad feedback, they will suffer from such a narrow plan.
I wish we had actual information about the cons using the system. Unfortunately I was not given the opportunity to do unless I wanted to keep paying while not using the system.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
It's simple to use for someone who is really good with computers as well as those who are not. I've been using my personal squarespace for years and have also helped clients build a starting page which they are later able to manage theirselves.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
We have raved about Springbot's support because they always get back with us so quickly. Our rep, Jared has been phenomenal in helping us, always being available to chat with us and explaining some of the metrics with us so we can better understand. He completely handles our ads, checks on them, and lets us know when to update and why.
Help is available directly from the back end and uses full sentence searching to find answers to questions others may have asked before. With a ton of articles and support questions documents, it is very likely that your question has been answered. If not each page has the ability to open a direct email to support. Each case has a number and can be followed. Responses are often quick and have links and directions clearly stated
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
Squarespace was quicker to set up and more accessible to manipulate the theme, pictures, and content. The page layouts are more versatile and fluid. With WordPress, more time-consuming efforts go into making a template work the way you want it to (because of the lack of the drag-and-drop grids that Squarespace has).
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Springbot gave us a better idea of who our customer was. We just launched in January 2015 having been B2B previously. So we weren't really sure who we were marketing to.
I only paid $200/month for the service so I didn't waste a ton of money trying it out. They have a 30 day cancellation policy so I wasn't stuck in a year long contract.
It was a let down because I had such high hopes of everything it would allow me to do and see with one platform. Give them a couple more years and I think they will work out the kinks.
The cost is reasonably decent. My client says they spent about $20 a month or $240 a year. I asked her if she could add Google AdSense to her blog one day, and they believe they can. They said a custom site would cost them $3000-10,000 depending on who does it. And I agreed, but I found the website they created was on the lower end of that range.