OutSystems Reviews

We don't sell OutSystems as a separate solution. We sell it as a platform. And then you win a lot of solutions on top of it. So that can be a second process, it can be a middle phase, it can be a portal, it can be many things, but it is useful for small apps to complete ERP systems and everything in-between.

It supports implementing Agile at scale, as it enables working in an iterative way, and it is very fast. Time to value as a result has dropped significantly!

What I like most about this solution is that it does automatic dependency checking in enterprise environments, which means that the application will automatically test if it can work in the environment of the customer or not. Instead of only having to find it out when it is too late. Normally, if you build software, you test it and then you deploy it. In the real world, it sometimes happens that it does not work and then you quite often have to figure out why is it happening. So this step is completely taken away because OutSystems tests the functionality of the software against the existing systems in an automatic session and that is very valuable.

Something that can be improved is that I would like them to be a little more flexible in the area of containerization. They're currently running on Docker on Windows, but I think they should also support Docker on Linus too. Needs a little more effort.

I've worked with OutSystems for many years now - I've worked with it, I've implemented it, and we use it in our company too.

OutSystems is extremely stable. We are replacing complete back-end systems with it, and are in progress to go complete mainframe replacements with it.

You can go to huge back-ends with OutSystems - so it is definitely a scalable solution.

The technical support is quite good, although it could be better: it currently fluctuates a little depending on how busy they are. Also it depends on your contract (what level of support you have).

The initial setup is super simple and you can do it from your desktop. That is if you only want to implement the platform, but if you have a more complex enterprise setting, then it will be a little more complex and you will have to do some configuration, and up-front think about what functionality you expect to need (particularly if you chose to run on a native AWS or Azure environment so that you can make full use of all the functionality of those 2 CLoud environments. If you do not know exactly how the platform works and what it can do, you can implement certain things and redo a few things. But that's not a deficit. More power comes with more responsibility, l always say. 

That depends on the kind of solution you are building and at what speed: the more you build, the higher the ROI.

For a single application, it's too expensive, but that's also not what the OutSystems aims for. Personally I don't think that's the smart approach. Their model is really based on platform and not every customer is ready to adopt a platform at the start. So, as a result, they actually limit their own success and results at the moment. But that isn't a huge issue. If you look at the value of the platform, I think the pricing is fair.

We looked at multiple alternatives, including (but not limited to) Appian, Betty Blocks, Mendix, Kony , Pega etc. They all have their own stronger and weaker points, yet we chose OutSystems as it is the most suitable platform for an Enterprise environment. As we do end2end transformations, this is why we chose OutSystems.

I will rate OutSystems a nine out of ten because if you look at other solutions, they do not have the functionality, the scalability and the performance of OutSystems, even if their prices are lower. So if you need a platform for a large organization, OutSystems is the one. 

To make it the perfect solution, it needs improvement in the AI capability. I would say that it would be nice to augment the functionality for the citizen development even further and augment the cloud's platform controls so that you can more easily run in a hybrid cloud environment too. Next to better branching options.

A word of advice to others is that they should align the business and IT because many people look at it from a technical point of view. And that is another really smart thing to do because it is really about driving the value. Because I've seen customers that bought either mandates or OutSystems or any other platforms and a lot of them had difficulties in getting the value out of it. And the reason was because if the IT or individual departments don't know how to define the proper user requirements, and then it is too difficult to successfully deploy it. It is therefore very important for the business and IT team to work together because that is the most common mistake people make. 

Customer track and trace. We get information from SAP which is updated later by carriers (via EDI). The user interface is built in OutSystems.

Development timeframe and deliveries on sprints. Customers can check the progress on a weekly basis and provide adjustments and comments right away.

Agile development. I love that you save a lot of time on development and can focus on logic and business requirements.

Mobile apps need improvement.

No issues with stability.

No issues with scalability.

Technical support is a 10 out of 10.

We did not have a previous solution. We started the department using OutSystems with the goal of creating applications for our internal customers (departments and warehouse customers) to help their main businesses.

Setup was straightforward. I was not there at that time, but I know that it was very smooth. The developer at the time was trained by OutSystems and this helped with the first applications.

It is still very expensive, so small companies can’t generally afford it. We hope that this changes. Still, the time saving on development and delivery is worth the value.

Agile development is really worth it. Depending on the size of your department – and requirements – you don’t need a big development team. The same developer can take care of all steps: analysis, development, implementation, support.

For some of the business processes, we want the process owners to be able to set up their own flow-throughs, process flows, workflows, etc. They don't need to have any kind of prior coding experience. They should be able to establish workflows for their respective processes by just dragging and dropping elements as part of self service without relying on IT (where possible).

OutSystems has really brought about citizen developers in my organization without any real coding experience to be able to develop their own work slows in their area of work.

The flow editor is the most valuable feature. It is simple and intuitive, and it can guide you step-by-step.

From an ecosystem perspective, it has a highly integrated flow editor, user interface, and data logic behind it. It has a very connected local ecosystem.

One of the biggest areas for improvement is that every time an existing data element is modified, it creates a new data element. It doesn't really modify that particular data element. So, a user has to follow an extra step of removing the existing data element and bringing in the new and modified data element that is being added, which sort of goes into negative productivity.

I have been using this solution for about four and a half years.

OutSystems' tech support is very good. They're fairly responsive.

It is one of the good solutions available in the market. I would rate OutSystems an eight out of 10.

I am using OutSystems in internal workflow processes for approving expenses.

The solution has helped us, but it's no longer a strategic choice for us. We are not investing anymore in this platform. We realized the value of using OutSystems if you have an internal development capability. We've been using the solution mostly in outsourcing for development tasks, and it doesn't make much sense to us, to pay the amount for the solution for the capital gains to go to the external provider we use for the development.

If I have a large team of developers, eventually using the solution would make sense. That's not the case. In my business model for IT, I do not have any internal development capability. I'd rather do it without a rapid development platform because the savings go to the provider. It doesn't go to me. I have to pay for the ticket and then I have to pay additional costs for the development. It doesn't make any sense. It is a good solution and technology, it only does not fit our use case.

The most valuable feature of OutSystems with discipline and the development processes. Instead of each developer doing tasks on their own with their own approach, et cetera, the solution would help bring some organization to the development process. 

I have been using OutSystems for approximately five years.

We did not experience a time when the solution did not perform, the solution is stable.

I rate the stability of OutSystems an eight out of ten.

The solution can scale. However, the catch is the pricing has become more and more expensive in the last few years. Consumption is increasing, and the price has increased a lot.

We have approximately 200 users using this solution in my company.

The support is not provided by OutSystems themselves. It's the service vendors, the integrators. There is a shortage of skilled workers that are knowledgeable of the tweaks of the platform and the shortcuts that can increase the productivity of using it.

We are using ServiceNow and it's depicted as a container for OutSystems. It's not the same, but it has the capability of doing some type of rapid development, and we are using it more and more.

The largest obstacle currently associated with OutSystems is its high cost and limited availability of skilled personnel. Despite being a rapid application development platform, having a highly skilled individual familiar with the platform can be much more beneficial than an inexperienced individual. Because there is a shortage of people with the necessary OutSystems skills, utilizing the platform can become expensive. This makes little sense, considering that a rapid application development platform should be accessible to the average person. However, having a highly skilled individual can greatly increase productivity, making the cost worthwhile.

I rate the initial setup of OutSystems a four out of ten.

I have not seen a return on investment using OutSystems.

OutSystems is expensive, and they changed the pricing model in the last couple of years.  It's changing too much and it's becoming unstable. They are constantly shifting their prices based on users, courses, and other factors.

To ensure that we will be able to benefit from leveraging internal development capability, I would suggest using a tool, such as OutSystems. With this solution, it is possible to increase the average productivity of the existing team of developers. Even a small increase of two to three percent can lead to significant gains. However, if there is a limited number of developers, it may be difficult to realize substantial productivity gains from using OutSystems.

I rate OutSystems a seven out of ten.

We use it to help our clients generate certificates. They needed an app to help them record and have data. It allows them to take the certificate number, check if it is authentic and if the equipment that the ticket number is issued against is working perfectly.

The drag-and-drop feature is very valuable.

The tutorials for the solution should be updated.

We have been using this solution for about a month and are currently using version 11.

The solution is stable and doesn't require many server resources, so I don't think there are stability issues. They have enterprise and have been around for a long time. Some of the tutorials we use were created in 2014, and we still use them.

The initial setup was straightforward. Once we registered, we installed it and were able to start work immediately. It took approximately 24 hours to set up.

I rate the solution an eight out of ten. The solution is good but can be improved by updating the tutorials available. I advise people considering the product to ensure they have their data somewhere to generate a certificate. Additionally, I advise them to do their own research. The application makes life easier.

Our use case is mainly for the manual control systems.

There are about 20 developers using this solution in my company.

The scratch coding is useful. The solution is easy to understand.

React is very easy to use for an experienced software developer.

It's difficult to do the component version control. I would like them to add more studying materials.

I have been using this solution for about six months.

Some systems have over 1,000 end users. It's very stable for heavy duty operation.

It's scalable.

Technical support is good.

For one developer to use, the cost is around $5,000.

I would rate this solution 8 out of 10.

We use OutSystems for our customers in the banking and utility sectors. 

OutSystems is a low-code solution. Most features are drag-and-drop, so it's pretty easy to work with. It thus helps the organization by saving time for developers. 

The OutSystems Accelerator is the most valuable feature. 

There are very few resources available to learn OutSystems. If someone is utterly new to OutSystems and is trying to understand this technology by searching on platforms like YouTube, Udemy and Coursera, they won't find anything. It has negligible resources. 

In the next release of OutSystems, I would like to see a few more customizations in the front end. 

I have been using it for four months. 

I would rate the stability an eight out of ten. 

I would rate the scalability a nine out of ten.  

I would rate the technical support nine out of ten. 

Previously I was working on high-code solutions. Then I started using OutSystems low-code solution. 

The initial setup was straightforward. I would rate the ease of setup a ten out of ten. 

I would rate the pricing a five out of ten. There are no additional costs with the standard license. 

I would advise anyone wanting to use OutSystems to start learning early while pursuing a college degree. 

We are a team of ten Software Developers who use OutSystems in my company. We plan to increase the usage of OutSystems in the future. I would rate the overall product an eight out of ten. 

OutSystems could improve by being more like GitHub. It would be more helpful for us for division management and version control for our application.

I have been using OutSystems for approximately five years.

The scalability of OutSystems is very good, it scales automatically very useful for us.

We are satisfied with the support but it could be better. We are the product provider and sometimes we contact the support for our customers and we have to escalate our issue most of the time for the correct answer.

I rate the support from OutSystems a four out of five.

I would recommend this solution to others.

I rate OutSystems a nine out of ten.