We performed a comparison between OutSystems and ServiceNow based on real PeerSpot user reviews.
Find out in this report how the two Rapid Application Development Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The visual program of OutSystems is one of the major advantages of this solution."
"Once built, web/mobile components can be reused in all new developments. In addition, the OutSystems Forge is very useful. We can exchange components and even already-built applications, reducing costs to build specific solutions."
"We have no complaints surrounding both the scalability and stability of this solution."
"It is very stable."
"The product is mostly stable."
"OutSystems' low-cost approach has positively impacted our productivity, because we were able to develop faster with OutSystems, enabling us to implement many changes during our sprint."
"We can do the validation before calling the API."
"It is a stable solution."
"For change management, I find the CAB workbench very useful. I haven't seen any other solution that has a CAB workbench or advanced automated solutions for a change advisory board. ServiceNow also has the Workflow Engine which works very well and is very intuitive."
"We have found the service easy to use, although, we have ended up customising a lot of parameters."
"It's more about the ease of use of ServiceNow. Plus, everything is there in a single platform. If you need any additional functionality, you just need to enable the plugins without even installing anything on the servers"
"This solution is a single-storage for our user community to submit help desk tickets."
"The look and feel is a valuable benefit for adoption."
"If it is a high priority, they will respond very quickly. If it is a low priority issue, it might take some time, some three or four days. I would rate the technical support as a 10 out of 10."
"We consider the integration capabilities of the solution with other tools to be a valuable feature."
"It offers ready-built automation and simpler configuration for workflows."
"We had some lagging issues under high data loads, and the solution needed to be customized to improve this."
"While I can't speak to the market impact, as a developer, I've seen significant reductions in development time across different versions of our applications. One area for improvement would be the UI controls in Service Studio. Sometimes, controls don't appear in the IDE, requiring us to check them in the web browser instead. Overall, our experience with OutSystems has been positive, though improvements in UI development would be welcomed."
"Since we first started using OutSystems, they switched their language support from Java and .NET to .NET only, which was a bit of a surprise. Their language support could be better in this sense, although on our resource side it is now a bit more flexible."
"There is room for improvement in technical support."
"The new version could be improved."
"The installation is a bit tedious."
"The solution is costly."
"We'd like OutSystems to add stronger workflow-based automation similar to what Appian offers. It needs more workflow modeling and RPA features."
"if I consider from the IT operations management side, ServiceNow is pretty premature on some things, especially the discovery, while the other tools like Micro Focus and BMC Remedy, those that have been in the market for quite some time. ServiceNow is evolving itself in the discovery piece of the future."
"We don't have a huge amount of password reset requests, but the minimum package of resets that ServiceNow offers is much more than we need."
"The discovery of assets could be improved; right now they only allow for one domain."
"I would like to see more functionality in terms of custom workflows, not impacting the overall platform health."
"Where it could be improved is Discovery. This may sound odd since I just praised the value of ServiceNow Discovery, but improvements to its automatic detection, the breadth of devices, and the depth of devices covered, as well as keeping up with new technologies, are all essential."
"Data access is a bit difficult, where you sometimes wish you had a relational database for some queries. The flexibility of data access in general is a bit on the low end. Of course, there is flexibility in some ways, but when I need a certain combination of data for some report, it can become a challenge."
"Service mapping could be less complicated."
"For healthcare, which is a pretty audited environment, there are no concrete solutions for digital signatures, apart from our license with Adobe, so it requires orchestration."
OutSystems is ranked 3rd in Rapid Application Development Software with 46 reviews while ServiceNow is ranked 4th in Rapid Application Development Software with 212 reviews. OutSystems is rated 8.4, while ServiceNow is rated 8.4. The top reviewer of OutSystems writes "Useful natural speech to algorithm, reliable, and beneficial automatic task". On the other hand, the top reviewer of ServiceNow writes "A stable and scalable solution that has excellent features and is useful for collecting data and building KPIs". OutSystems is most compared with Microsoft Power Apps, Appian, Mendix, Oracle Application Express (APEX) and Pega BPM, whereas ServiceNow is most compared with BMC Helix ITSM, Microsoft Power Apps, Pega BPM, IBM Maximo and Moveworks. See our OutSystems vs. ServiceNow report.
See our list of best Rapid Application Development Software vendors.
We monitor all Rapid Application Development Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
The short answer is that OutSystems is far better for 2 main reasons. Firstly, with Service Now you are locked into that platform for good. The business model is to lock in and then keep pumping the annual fee up in the knowledge that you have little choice. If this was in a consumer market they would have been stopped years ago on antitrust grounds. I have experienced senior management in Service Now laughing at the customers' lock-in.
Secondly, with Service Now, once you move beyond the workflow design you are straight into the deep valley of Java scripting. There is nothing in between. Most customers realize the limitations of the graphical environment very quickly. They are then stuck with having a never-ending bill for consultant fees. Many SN partners use this as their prime source of 'new' business. They talk of stickiness, meaning they are embedded in the clients' system perpetually.
There are many other reasons. I might come back and give a fuller review. Let's just say there are several platforms that outperform Service Now technically and economically. Service Now is quite happy to have its customers stuck with 1990s technology with a slightly fluffy front end.
ServiceNow
Hello @Gerry Fitzpatrick,
'Customer Service Management' and 'IT Service Management' applications run on the same ServiceNow platform.
Whilst 'Customer Service' gives you the CRM capability (external facing), ITSM gives you the supporting framework (internal facing). The two work very well together. There is no need for you to invest in building custom apps. However, if you still want to build custom apps then the ServiceNow platform allows you to do that with a very good mobile SDK.
ServiceNow also has an App Store, which is a really good source to see what integrations and applications are available to purchase (some are free). This would help you get value from your investment in ServiceNow quicker.
Regards,
Farid