SAP SuccessFactors Reviews

Compared to other on-premise solutions, the first advantage of SAP SuccessFactors is that it is a SaaS-based solution. It means that everything is managed on the cloud. HR applications contain confidential and sensitive information, and SAP SuccessFactors has better security measures than other solutions available.

I have only used the Employee Center component of SAP SuccessFactors, and it has worked fine for me.

There is an area of improvement in integrating SuccessFactors with different platforms. There are other HR solutions, such as Mercer and Oracle, that companies are using, so integrating SuccessFactors with these products would be good. Oracle and other HR solutions are present in the market, so we can offer the customers the option to continue using their old HR system but integrated with SAP SuccessFactors.

I have been working with SAP SuccessFactors for almost three months.

The new version is quite stable. I would rate it an eight out of ten.

It is quite scalable. We can also do customization. It's flexible. We had around seven to eight customers on SuccessFactors with different modules.

The initial setup is straightforward. For deployment, if we are going for just one module, it takes around three to four months.

The deployment procedures are being handled efficiently by our technical team. Two to three people should be enough for the deployment and maintenance. One should be the administrator, and the rest should be specific to the module consultant.

Our clients used a yearly subscription model. I have not seen customers complaining about the price of SuccessFactors because of the benefits they are getting. It's more about the value than the cost, and the cost of SAP SuccessFactors is reasonable.

I advise the customers to proceed with SAP SuccessFactors if they're using traditional solutions.

Overall, I would rate the solution an eight out of ten.

We use SAP SuccessFactors for our performance management, goal setting, performance evaluation, and employee confirmation, e.g. employee letters. We also use it as an employee self-service tool for personal data updates, life cycle events, and learning management.

It's the performance management feature that I find most valuable in this product. As for the product itself, I like its flexibility and configurability. It can handle different types of performance management from one organization to another, and this is one of its best features.

What needs to be improved in this product is the user experience. In general, for SAP products including SuccessFactors, the user experience is not so great, particularly the whole user interface. A lot of new age products beat them on that.

While SAP products are great from functionality and feature standpoints, the whole user experience element is always lacking. That's one area SAP should focus on.

There are other areas where we have not liked SuccessFactors. For example, as a recruitment solution, it's not great for onboarding and exit. Two years ago, we decided to use a different product for recruitment, onboarding, and exit. We're no longer using SAP SuccessFactors for those activities.

I've been using this solution for 10 years.

This solution is extremely stable.

I found this solution absolutely scalable.

SAP has implementation partners, so the technical support is given by the implementation partner. We have not contacted SAP for support, but as far as SuccessFactors is concerned, any product level support and response is very good. It's very well-structured and well-governed. They have a knowledge-rich library that you could always go to. There's also some forums where you can go and ask questions and get answers to your problems. The ecosystem itself is quite strong, including their responses as far as support is concerned.

The decision on which solution to use happened between 2010 to 2011. When we made the decision, it was not with SAP. SuccessFactors was a different organization.

During that time, the reason for moving to SuccessFactors was because we were looking for a SaaS-based product in performance management and there was nothing better than SAP SuccessFactors then.

If I look at the last three, four, or five years, and why we have stayed with SuccessFactors and continued with it, it was because of global scalability. We are a global organization. When you are an India-based company and headquartered in India, the only options you have are Oracle and SuccessFactors.

Performance and talent are the main focus areas for us and even today, SuccessFactors is much better in performance management and talent modules than Oracle, so we've stayed on. The other reason for staying with this solution is change management. Why change unless something is significantly better?

I wasn't there during the setup, but I don't think the setup was complex because there were a few things we've implemented and implementation of those weren't complex.

We have a yearly license for this solution. Any additional costs we pay to the implementation partner, to the support partner, but not to SAP.

This solution is a SaaS. It is deployed on the cloud.

I might have gone to your site out of curiosity, but we already have SAP SuccessFactors. We are using SAP SuccessFactors.

We have 7,500 users for this solution in our organization. We don't need much staff for its maintenance. We are using SAP SuccessFactors extensively. As for plans for increasing its usage, we definitely want to if the business and our headcount grows: We will use it for more users. As of now, no plans of increasing usage of this solution.

My advice to anybody implementing this product is to first have a SaaS mindset. It's a SaaS product, so you can't have an on-premise mindset of "I'll give whatever requirements and the product should do it." Having a SaaS mindset is my first advice.

My second advice is to keep in mind that these products give recommended practices based on which the product is built. If you could tweak your processes to embrace the recommended practices by SuccessFactors, then your chances of becoming successful, or embracing the product is going to be much higher.

My third advice is to stay with SAP SuccessFactors and use all the modules together. For example, there are modules for recruitment or onboarding where you may have certain functionalities missing, but if you could keep as many HR processes on the same product integrated, then the employee experience is going to be much better, compared to trying to use SuccessFactors for a particular purpose, then another product for performance, another product for learning, etc. It's better if you could be on an integrated solution, so your user experience and your adoption at the end of the day will be much better.

I would give this product an eight out of ten rating.

The primary use case is for the company's human resources.

There is room for improvement in licensing model. It is very expensive.

It is a stable solution. 

It is a scalable solution. Approximately 1,000 users are currently using SAP SuccessFactors.

The initial setup is complicated. 

The IT department mainly handles the deployment and implementation.

It is expensive. I would rate it a two out of ten. 

Overall, I would rate the solution a five out of ten. 

I primarily use this product for employee management. This includes an objective assessment of money made, creating performance reviews, and recruiting new employees and management.

It has improved my organization by enabling us to efficiently manage our personnel.

The features that I have found most valuable are the ability to set and review goals, and the ability to manage performance in general.

In terms of what needs improvement, in Employee Central, one of the features that I think SuccessFactors really lacks is the ability to view the time off of all employees at an organizational level. We have had instances where some of our clients wanted a version where at a glance, we can have an HR analytics that shows who is on leave, or has been on leave and when. You have that at a team level and at a peer level, but you don't have it at an organizational level. When you have to put together an agreement on leave with your client this is very lacking.

Also, it would be helpful if they could improve its ability to localize the product to Nigeria.

I have been using this solution since early 2017.

I think it's a stable solution. We have not had any issues with its deployment or use. It's been stable, so I don't know if there are any issues because we haven't had any challenges around it. 

My impression of SuccessFactors is that it is quite scalable. For example, we have clients who have slightly above 800 employees who are using it. We have clients that have over 1000 users using this. I also read online a few months back about a Russian bank that uses SuccessFactors with about 75,000 employees. It's the same product. All you need to do is to get different licenses.

If we had any issues that we were unable to resolve, we can always receive support from SAP. We raise an incident with them, and they respond depending on your priority. If you put priority one, it's almost an instant response. They reach out to you within an hour. On that call they asses the true priority level. If it's something we have to resolve as soon as possible, they will. While if it's something that is less of a priority, they will change the priority to something lower. But what I find is that at the end of the day, you always get a very good response from SAP.

Actually I haven't used a different solution.

The initial setup is straightforward because there are templates and best practices. We can just click on the button from the online center, deploy it into the system, and it sets it up for us.

The time it takes to deploy depends on the requirements and it depends on the number of modes that you deploy. As long as you have clear requirements from the client, it can take between three and four months. It doesn’t take too much time to deploy as long as you have clear requirements.

I work for a partner. I did the deployment with some of my team members.  

Before choosing SuccessFactors, we compared other industry solutions, including Microsoft. But Microsoft's HR product is really not top line in this part of the world.

I think the advice I'd give is that it's a nice solution. It's easy to deploy. It's so easy to use. You really don't need to know much about coding or be a highly technical team to be able to use it. It’s very easy to use. For example, for the traditional ERP that SAP had before, you had to be instructed to work with it. This one is really straightforward.

The tool's most valuable feature is document generation. 

SAP SuccessFactors needs to improve the LMS and performance management. 

I have been using the product for ten years. 

I rate SAP SuccessFactors' stability an eight out of ten. 

I rate the tool's scalability a ten out of ten. My company has 250 users. 

Customer support does not provide answers to my questions at times. 

Neutral

I decided to use SAP SuccessFactors due to its UI, usability and smart features. 

I rate the product's installation a ten out of ten. It took six months to complete. We did the deployment according to the SAP activation process. We relied on 10 people to handle the deployment. 

I rate the tool's pricing a seven to eight out of ten. 

You'll need to conduct a deep assessment before you implement it. I rate the solution an eight out of ten. 

SuccessFactors is primarily used for employment engagement (e.g. payroll and claims) and to manage HR-related information.

SuccessFactors' best features are talent management and HR Analytics.

SuccessFactors' experience management is not so user-friendly - the launch through the initial dashboard is okay, but when you do a deep dive into certain applications or specific scenarios, the navigation needs to be improved. In the next release, SuccessFactors should include better integrations and reusable plugins. 

SuccessFactors is stable.

SuccessFactors' technical support is responsive.

Neutral

From a technical perspective, the initial setup is straightforward because SAP is engaged in the implementation. But from the customer's point of view, it's a little challenging because it's a new platform, so it requires some training before it can be used. That means that while the roadmap of implementation is six to eight months, there is an additional four to five months of user training.

I'd advise anybody thinking of implementing SuccessFactors to know their target audience and the kind of features they're trying to provide. I would rate SuccessFactors eight out of ten.

We use the private deployment model of this solution. 

It was much easier than the previous system. It made things a lot easier and operations much smoother.

The best models we used were the Goal Management and Performance Management. They were the most useful. We use three modules in our company, the Goal Management and Performance, the Talent Acquisition, and there's the LMS, the training. The best features that were working well for us was the Goal Management and Performance Management. They were the most valuable to our organization.

They should improve the reports. We had a problem with the reporting. If we compare it to Oracle products, Oracle has much more comprehensive and a better reporting system all in all. They really should work on the reports and making it more user-friendly. There's room for more customization in the reporting. This is the feedback I received, that the main edge that all Oracle products have is the reporting system, which is the main reason why I'm using the system in the first place.

In the next release, I would like for them to make the system have a slot for regular, back and forth feedback. It should have a feedback form on the system. 

It is stable. We haven't had any problems. 

Scalability is good. We can easily expand it. We were able to integrate it with a couple of our systems.

We were not happy with their after-sales support. Whenever we had an issue it was really difficult to get in touch with them. There was a problem with asking them about a feature or other things. They weren't as responsive as we would have hoped. During the installation of the system, they replied 24/7. However, after we deployed the system, it was not that easy to get a response.

We previously used Oracle. We switched because SAP is much more user-friendly. We weren't using Taleo or Fusion, we were using Oracle Basic. SAP was user-friendly for our employees.

The initial setup was straightforward. SAP was really supportive during this time.

We used a consultant for the deployment and they were very supportive during the time. 

I would advise someone considering this solution that they need to really look into their requirements and be very specific regarding the requirements when getting their orientation on the system and creating the requirement documents. They really need to to be very specific and very detailed in their requirements. Make sure to understand all the features and capabilities of the system.

I would rate it a seven out of ten. 

The tool allows us to consolidate many review processes into one process. We had a lot of processes and everybody was doing their own thing. This tool has streamlined that succession management process.

We have multiple offices in different countries. This solution allowed us to consolidate all that data together without having to send spreadsheets and emails.

There are opportunities in every piece of software. It's not 100%. It's hard to find developers. That's the only problem we really have with this solution. It's hard to find people who can manage it.

In terms of stability, so far so good.

It's our first year of implementation and we haven't had any scalability issues yet.

We have used technical support. I would rate their support as average. They are not as fast as we want them to be. They help us with backend technical interfacing between other systems. We're taking data from other systems and pushing it in.

We didn’t have a previous solution. We have lots of employees and we're growing very fast. Selecting this solution was something that needed to happen.

I was not involved in setting it up. I was involved with the data integrations, which were very complex. They have a set of web services and connections to them. The libraries were not up-to-date and this contributed to the complexity.

Start with a small implementation first and then work from there.

When looking for a vendor, the cost is the most important factor. The next factor is scalability. We want to be able to grow with the product.