Platform.sh vs. Salesforce Lightning Platform

In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.

Incentivized

We use Salesforce Lightning Platform in everyday business as sales coordinators. By using this tool, we are able to send new requests to clients and communicate regarding pending proposals in real-time. This also tool holds many of our client accounts where we are able to monitor their sales and revenue.

• As this is a PaaS it mitigates the complexities of a Cloud infrastructure like Acquia
• We are easily able to integrate our sites with different technologies like Python and Rest
• Helps us in providing Continuous Development cloud deployment hosting solution

Incentivized

• Reporting and Dashboards are thorough and can show a wealth of important data to inform and scale processes. It's helpful in a high volume sales cycle to be able to quickly identify weak points in performance and productivity so that adjustments can be made.
• Highly customizable. We are able to customize just about everything which allows us to track very specific things and in theory create better efficiency.
• Parent/Child account hierarchy exists which is helpful.
• Contact records can be associated with multiple accounts and opportunities. This, in theory, should minimize duplicates and mismanagement of contacts.
• Console helps a lot with data nesting. Having a fairly comprehensive look at an account without searching through various tabs and sections speeds up an otherwise cumbersome platform.

Incentivized

• Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
• As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
• During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.

Incentivized

• Can be cumbersome: takes multiple clicks to get where you need to go
• Lightning is slower than original Salesforce, and it is very noticeable
• The UI change means sometimes I can't find what I need, so I have to switch back to the Classic version to find it

Incentivized

It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.

Incentivized

Salesforce's support is top-notch. They have subject-matter experts that are accessible at all times to address needs as they come up. They let you know in advance when there are system updates and enhancements so that you are prepared for upcoming changes. I've never had an issue that wasn't addressed immediately when reaching out for support.

Incentivized

In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.

Incentivized

We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.

Incentivized

• Continuous development for sites in build has been fluid
• Platform.sh is really cost effective when comparing to AWS or Acquia Cloud
• On the other side, lack of server side support demands a big learning curve from its users in my opinion.

Incentivized

• Better visibility of Accounts and Contacts interactions makes it easier to maintain during employee transitions.
• Tracking of current jobs and relating them to past jobs is very useful.
• More efficient use of Sales Reps time.
• Sales Managers have good visibility into how their people are working.

Incentivized