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.
Pricing
Drupal
Springbot
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.
Offerings
Pricing Offerings
Drupal
Springbot
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
See website for pricing calculator for additional pricing options.
More Pricing Information
Community Pulse
Drupal
Springbot
Features
Drupal
Springbot
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Springbot
-
Ratings
Role-based user permissions
8.174 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Springbot
6.9
3 Ratings
8% below category average
API
7.264 Ratings
4.23 Ratings
Internationalization / multi-language
8.160 Ratings
00 Ratings
Role-based workflow & approvals
00 Ratings
8.21 Ratings
Customizability
00 Ratings
7.31 Ratings
Integration with Salesforce.com
00 Ratings
7.31 Ratings
Integration with Microsoft Dynamics CRM
00 Ratings
7.31 Ratings
Integration with SugarCRM
00 Ratings
7.31 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Springbot
-
Ratings
WYSIWYG editor
6.171 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
00 Ratings
Admin section
6.878 Ratings
00 Ratings
Page templates
5.577 Ratings
00 Ratings
Library of website themes
5.468 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
00 Ratings
Form generator
6.372 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Drupal
6.5
77 Ratings
13% below category average
Springbot
-
Ratings
Content taxonomy
6.971 Ratings
00 Ratings
SEO support
6.172 Ratings
00 Ratings
Bulk management
6.367 Ratings
00 Ratings
Availability / breadth of extensions
6.570 Ratings
00 Ratings
Community / comment management
6.569 Ratings
00 Ratings
Email & Online Marketing
Comparison of Email & Online Marketing features of Product A and Product B
Drupal
-
Ratings
Springbot
4.4
3 Ratings
54% below category average
WYSIWYG email editor
00 Ratings
4.03 Ratings
Dynamic content
00 Ratings
4.23 Ratings
Ability to test dynamic content
00 Ratings
2.72 Ratings
Landing pages
00 Ratings
8.21 Ratings
A/B testing
00 Ratings
4.23 Ratings
Mobile optimization
00 Ratings
4.03 Ratings
Email deliverability reporting
00 Ratings
4.03 Ratings
List management
00 Ratings
4.23 Ratings
Triggered drip sequences
00 Ratings
4.03 Ratings
Lead Management
Comparison of Lead Management features of Product A and Product B
Drupal
-
Ratings
Springbot
6.6
3 Ratings
17% below category average
Lead nurturing automation
00 Ratings
4.03 Ratings
Lead scoring and grading
00 Ratings
9.11 Ratings
Data quality management
00 Ratings
4.03 Ratings
Automated sales alerts and tasks
00 Ratings
9.11 Ratings
Campaign Management
Comparison of Campaign Management features of Product A and Product B
Drupal
-
Ratings
Springbot
5.2
3 Ratings
35% below category average
Calendaring
00 Ratings
4.03 Ratings
Event/webinar marketing
00 Ratings
6.41 Ratings
Social Media Marketing
Comparison of Social Media Marketing features of Product A and Product B
Drupal
-
Ratings
Springbot
2.7
2 Ratings
93% below category average
Social sharing and campaigns
00 Ratings
2.52 Ratings
Social profile integration
00 Ratings
3.02 Ratings
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
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.
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.
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.
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.
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.
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.