Drupal vs. Planhat

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.

Incentivized

For someone working in the Customer Success team, Planhat is a must-have software. All your client-level data can be easily managed, stored, and reviewed at any point in time by Planhat. It also helps the management and the leadership team better see each account and its usage. It also helps in identifying potentially risky customers and taking the required actions to engage and retain the account. It also gets integrated easily with other meeting recording tools wherein the summary from the tool gets easily synced with Planhat

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Reporting - you can set up filters with boolean criteria to give you insight into everything you need to know.
• Playbooks - these are very good for less-experienced CSM's who need a step-by-step guide on how to deal with different stages of the customer lifecycle. More experienced CSM's may not need the playbooks.
• Usage data for customers - there's a wide range of charts in Planhat that tell the story of client consumption.

Incentivized

• 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.

Incentivized

• Allow for cc'ing of AEs or others within the same organization from the messaging center. When I went to send a message from within Planhat, I had to manually type out the AE's email address every time if I wanted them cc'd.
• The fonts were funky if I went to add text into an existing email template. For example, if I added in an extra sentence or paragraph, in Outlook on the recipient's end, the font was different despite looking the same within Planhat. Gmail was all consistent, Outlook was showing a different font.

Incentivized

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.

Incentivized

It takes a while to learn Planhat even for experienced users. It has limitations in terms of what data you can present where, but its important to set internal guides outside Planhat as well so everybody working collaborative. But as CSM Planhat is a great- and critical tool which I use daily to optimise my work schedule and customer interaction with various topics.

Incentivized

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.

Incentivized

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.

Incentivized

The support team couldn't be better. They are quick to respond, very helpful, and thorough. Our CS manager was always happy to schedule calls to go through specific feature queries and she ensured we had a smooth and quick setup.

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%

Incentivized

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.

Incentivized

I was not the person involved in choosing Planhat, but it seems to me that Planhat is much better suited to an account management style role, whereas Hubspot is closer to a sales CRM instead. In my position, Planhat is better suited as it is more graphical, more flexible, and easier to find information on.

Incentivized

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.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• Planhat has, for the first time, given us a 360-degree view of all our customers and access to all the different types of communication we have with them across different departments and functions.
• The ability to automate workflows, tasks, and assign playbooks to the various phases of our customer lifecycle has aligned all our departments.