OutSystems Reviews

I use the solution since it is a low-code platform. I am more into the BFSI domain. Most of the projects that have dealt with revolve around the banking sector. I have used the product for web development and mobile applications. My company has worked on a mobile app for a bank's core processes. My company took care of the website part of the bank with the help of OutSystems. My company also operates with other clients who operate in the banking sector. My company has also dealt with the insurance domain and mutual funds.

The product's high price is an area of concern, where improvements are required. OutSystems should play around with the market or with its competitors. A lot of the clients feel that the license cost of OutSystems is way too high than the prices of its competitors.

In the future, I want OutSystems to offer support for which they should not charge any money from users. If a client is new to OutSystems and has taken a license for two or three years, I believe that the solution should provide free support for a year.

I have been using OutSystems for four years.

Stability-wise, I rate the solution an eight or nine out of ten.

When it comes to the scalability part and its impact on our organization's growth, I can say that the development and implementation timelines are minimalistic, which is something that is good. It is pretty easy to implement anything that a specific client wants with the help of OutSystems. It doesn't take years to implement something with OutSystems since such areas can be dealt with quickly.

From migration to adding internal applications is easy with the product. The platform is very adjustable based on the requirements. The customization levels offered by the product are good. It is possible to distribute the loads in OutSystems.

My company deals with around ten customers who use the product.

I have experience with high-code platforms like Java and Clutter.

The product's setup is more of a PnP procedure, making it an easy process. I feel that the setup process can be a bit complex at an architectural level.

The solution is deployed on an on-premises model.

The number of people required for the deployment and maintenance of the product depends on the product that is used. If a business entity has multiple business units, it takes a longer time to implement the product. In general, my company has a team of around 15 to 20 people to take care of the implementation process.

The clients who use OutSystems feel that it is a bit expensive.

There is a need to make yearly payments towards the licensing costs attached to OutSystems. It is an expensive product.

I don't see any differences between Java and Clutter or OutSystems since I use different products depending on the requirements of our company's clients. I don't get the clients to choose a particular platform, but my company recommends OutSystems. Not all of our company's clients prefer OutSystems.

The product's scalability is very good. The tool offers easy integration with multiple platforms.

The product's features and speeding up the application development process stem from the fact that the capabilities provided by the tool are not limited. The whole platform, user experience, and implementation time are good.

The interface of OutSystems has impacted our company's development workflow since it is very user-friendly. I rate the product's interface a four out of five.

Though OutSystems is an expensive product. If an organization wants better dynamics when it comes to a particular platform, I would recommend OutSystems to such companies.

In terms of user support and community engagement, I rate the tool a ten out of ten.

The value and positive impact experience from the use of the solution stems from the fact that it works very well when it comes to load balancing. The product is also easily configurable.

I rate the overall tool a nine out of ten.

OutSystems has use cases in the health care, accounting, banking, insurance, and automotive industries.

The most valuable features of OutSystems are the user interface, the flexibility to quickly integrate with almost anything in the system, and the ability to connect with databases.

The solution's testing framework needs to be improved, and the workflow should be slightly more mature. The solution should use generative AI capabilities.

I have been using OutSystems for nine years.

We haven’t faced any issues with the solution’s stability.

OutSystems is a scalable solution. The solution is auto-scalable regarding the number of users or the volume of data.

I have created an application which is being used by almost 2,00,000 users. That was done for some kind of enterprise wide application where it is being used across the globe. That's the maximum number of users I have created an application for.

The solution's technical support is quite useful, but it takes a good amount of time to get a solution from them. The technical support is not so quick and could be faster.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team. Depending on the size of the application, the solution's deployment hardly takes a few minutes.

With the solution, I have seen around 80% to 90% increase in the return on investment.

OutSystems is a very expensive solution, and it has to be cheaper. Users have to pay a yearly licensing fee for the solution.

I have used the solution for both web and mobile application development. In the healthcare domain, we used the solution to create a mobile application related to patient care. We also used the solution to create web applications, including banking and in-house enterprise applications.

It hardly takes around six resources, including developers, for a typical project which goes for around six months. I would recommend the solution to other users. I rate the solution a nine out of ten for user support and community engagement.

Since I've worked with the solution for nine years, I'm well aware of its visibility. I will promote the solution if the business needs align with what can be achieved with OutSystems.

Overall, I rate OutSystems an eight out of ten.

The primary use cases are mostly related to the rapid low-code framework. Currently, I'm working on a business use case where we need to create a responsive website that enhances the customer's experience.

OutSystems is a hybrid framework and supports my mobile and web application development needs. This means I don't have to write separate code for mobile applications. It adapts the UI and functionality, whether I'm developing for web or mobile interfaces. All I need to do is provide the layout during development.

The tool has enhanced my development speed through its prebuilt templates and drag-and-drop interface. Unlike legacy frameworks like C# and Java, OutSystems provides everything ready to use. You need to connect integrations and formats, which allows developers to develop their modules rapidly.

In the healthcare sector where I work, we handle clinical and non-clinical research involving study criteria and customer-responsive interfaces.

In one of our recent projects, which involves setting up appointment bookings for healthcare organizations like NHS and Canadian provincial health services, OutSystems plays a crucial role. The system monitors Outlook email criteria every five minutes to detect appointment requests. When a request is identified, OutSystems uses AI capabilities to determine if it's a new booking or a follow-up based on the email content.

Once categorized, the tool integrates with other systems, such as Salesforce.

The tool's weakness is its focus on the solution only. Other than that, it's pretty easy to use for both technical and non-technical people. However, the tool lags in automation. For instance, we've used Python for scraping and other automated tasks. So, I believe automation is an area where it could improve.

I have been working with the product for three and a half years. 

OutSystems servers are currently managed directly by the vendor. This setup makes scalability readily achievable because whenever we need to expand our operations to different locations, we can directly engage with the vendor who handles the tool. They can scale the infrastructure to meet our requirements. However, at this point, our focus isn't on scaling further because the configurations we've implemented for recent developments are adequate for targeting the Canadian and North American regions.

Technical support is good, especially for customers on the Gold tier like us. Typically, we receive responses within 24 hours, and their support team is very responsive.

Positive

Appian offers advantages in automation structures with its Appian RPA platform, formerly Jidoka. They have integrated this acquisition into their offerings as Appian RPA. Additionally, Appian has a well-established market presence. Appian holds a slight advantage over OutSystems, which entered the market approximately five years ago.

Our primary goal has been to enhance customer experience by deploying applications developed with OutSystems. The initial response from users has been positive, particularly in reducing previous backlogs. We've streamlined processes with the product, enabling rapid development, integration, and automation.

We haven't yet reached the stage of calculating ROI specifics. Typically, such evaluations are conducted either at the end of the fiscal year or three years.

The tool has its  own AI modules, but we've utilized our custom models. As we focus on specific regions like Canada and North America, we've developed dedicated forms and solutions. We've implemented our custom models using Python and Gen AI to extract data from emails and forms. OutSystems does offer its own AI capabilities.

Due to its fast development strategies and everything, I would recommend OutSystems over Appian. Appian is in a different space and has its own components and frameworks. 

I rate the overall product a seven out of ten. 

Wherever there's a mobile platform in use, there tends to be a fair amount of application activity as well. In these situations, we've observed that it's straightforward for us to integrate our systems, and this process is also highly consultative.

To illustrate a case, the customer initially had a private cloud, essentially a data center hosted within it. They needed a disaster recovery solution, which would involve using a public cloud. This situation led to some deployment challenges due to the hybrid nature of their setup.

However, once we implemented the solution for them, they were extremely satisfied. The process was not only effective but also quite speedy. To be more precise, we completed it in around 100 days, even though they initially requested it to be done in four months. They were very pleased with the efficiency of the implementation.

I'm genuinely content with the fact that all my goals and objectives have been successfully achieved in everything we've undertaken. As I mentioned previously, we found this especially valuable in terms of engagement for mobile apps. Surprisingly, we didn't encounter any notable challenges or areas where implementation was problematic. As a sales professional, I also received minimal customer feedback regarding any issues during meetings, which led me to believe that everything was going smoothly from a technical perspective. However, the initial setup can be made a little easier. 

I have been using OutSystems for the past four years.

It is stable.

Scalability proved to be an exceptionally beneficial feature. In one instance, we needed to transition from a single-tenant setup to a multi-tenant one, and we accomplished this seamlessly. The customers were also delighted with the outcome, as we successfully executed the shift from a single-tenant to a multi-tenant configuration.

I would rate it a nine out of ten.

It was outstanding. 

Positive

All options are equally commendable, but our system is notably budget-friendly. As a result, many customers are now making the switch to our platform. There are three key reasons behind this shift: our user-friendly interface, the stability of our solution, and its competitive pricing.

The initial setup is a little difficult.

Some of my clients come from government backgrounds, so they prefer on-premises deployment for their systems. However, in cases where there's no sensitive data involved, they are open to using cloud-based solutions. It's worth noting that the cloud adoption trend is still in progress, and we're gradually transitioning from on-premises to cloud-based systems. Looking ahead, I believe that in the next three to five years, cloud providers like AWS and other hyper-scale cloud platforms will play a significant role. They offer tremendous scalability and various features that make them highly valuable compared to other solutions. The deployment process takes almost ten to nine weeks for smaller applications to approximately not more than three months. Our current situation involves a mix of both on-premises and cloud deployments.

I would rate it five to six out of ten.

Two of my clients have implemented SpamTitan in their marketing and sales departments. They operate through a distribution channel, and this is where they utilize SpamTitan. They are exceptionally pleased with the results. Essentially, they deal with the delivery of products like milk, where customers place orders, and the products are delivered to their doorstep the next morning. Customers can easily place orders through their website, which is highly user-friendly. Interestingly, approximately eighty percent of transactions are now conducted through mobile devices, underscoring the system's convenience and efficiency. 

I would rate the solution a 10 out of 10. 

We have been actively following the below strategy for our application development:

• Core applications and systems (SaaS-based external products)
• Bespoke Applications (using Microsoft Azure and Dotnet Application development technologies and tools)
• Quick turnaround applications for web and mobile (Outsystems)
• Portal knowledge and corporate portals (WordPress, SharePoint, DocuWare)
• Cloud Platform (Azure and AWS)
• Support within two hours on the community portal
• Access to native functionalities (camera, geolocation, QR code reader, and access to file systems, address book, and device calendar)
• Supports custom branding
• Supports custom plugins
• Silk UI response framework
• Big focus on performance
• Best practice for CSS and JS
• Tested on several modern browsers and devices
• Support and community (52000+ members, 500+ projects, and two-hour response time)

The OutSystems platform has improved the quick turnaround for application development and deployment.

It provides for faster development and better software releases.

The solution helps reduce costs and gives us an efficient budget.

The ease of management is great.

The product has good reliability and has improved business continuity with increased resilience.

We have a lot of choices through open-source standards.

The product gives us better customer experiences.

There is access to native functionalities (including the camera, geolocation, QR code reader, and access file systems, address books, and device calendars).

It supports custom branding and custom plugins and has a Silk UI Response Framework.

There is a big focus on performance.

The product has best practices for CSS and JS.

It has been tested on several modern browsers and devices.

There is support and a good community (52000+ members across 500+ projects and a two-hour response time).

Below are the solution's most valuable features: 

• Device support (Android 4.0+, iOS 7+, Windows 8.1+)
• Access to native functionalities (camera, geolocation, QR code reader, access to file systems, address books, and device calendars)
• Custom branding
• Custom plugins 
• Silk UI Response Framework
• Performance
• Best practices for CSS and JS
• Tested on several modern browsers and devices
• Great support and strong community (52000+ members, 500+ projects, and a two-hour response time)
• Online developer training
• Integration Studio
• Service Studio
• Service Center
• Deployment services
• Faster development and better software releases
• Reduce costs/improves budget
• Ease of management
• Reliability/improved business continuity with resilience
• Choice through open-source standards
• Better customer experiences

Areas of improvement include:

• Offering workflow solutions
• Adding event-driven architecture
• Usage of PWA, Responsive, and SPA architecture for front-ends.
• Better documentation and deployment tools. The packaging features need to be standardized using DevOps.
  
• Vertical Tabs (there is a Vertical Tabs problem: Entities.Orientation)
• Data Grid improvements and UI improvements
• There are performance issues in table data using React
• They need to make improvements in various UI assets. 
• There should be automation of logs
• We have performance issues while fetching bulk data
• Need integration with core systems and integration with Outlook email

This is a no-code platform solution. We have been using this for the past five years. We've used it for building solutions for web applications and mobile applications. There is a quick turnaround for applications that need to be implemented and deployed for business.

The solution offers good stability.

There are good scalability options. However, scalability can improve.

The solution offers excellent customer support and responses can be expected within two hours from the community forum to help with resolution.

Positive

This is the first time we are using a no-code solution end-to-end.

The initial setup is straightforward. The process is good enough and elaborate documentation and help in community forums can help the process.

This was an in-house implementation from the development team.

ROI and TCO are great.

With the pressure to deliver new customer and employee digital experiences and having to adjust existing enterprise systems to cope with the market changes, 75% of app development would use low-code platforms. Outsystems has the highest ROI.

The setup cost, pricing, and licensing costs are competitive.

We have not evaluated any other options.

It is kind of used for reactive and web applications. We're also working on the mobile applications as well. I use it in a banking environment. 

I've been onboarded there and then I'm just doing the activities for both internet banking as well as mobile banking, handling both servers as well as the front end.

Currently, this banking application can consist of both mobile as well as internet banking. We have it for eight different countries. For mobile, we have eight different applications, and for internet banking, it is a single application, however, it'll support eight entities in eight countries including Bahrain, the UK, Iraq, et cetera.

Normally we use it in a banking setup. Usually, transfer payment and then the benefits pay gateway, are those kinds of integrations we are doing currently for mobile. The onboarding process we do, the login for that process, et cetera, offer good features. 

We have one feature called multiple payments where we're able to select multiple beneficiaries and we're able to create ad hoc beneficiaries. Ad hoc beneficiaries mean there's no need to add the benefits directly. We can enter the beneficiary upon the number and we can do the payment. We can add multiple beneficiaries in a single go and then we will do the validation. 

We have a back office application as well where we can configure based upon the user as well as based upon the segment. We can configure per day.

We're able to do transformations. We can do the validation before calling the API. Once validation is done, we will show the set of validation. Either it can be the OTP validation or it can be a token validation. Once that is done, we can call the final API, which calls the code banking system for doing the payments.

We've acquired a new bank and would like to integrate e-services into the offering. We'd like to be able to have an option for doing an activation directly from the internet banking area so that there is no need to contact the bank directly. Having e-services capabilities would be ideal. 

There are a lot of enhancements and new features coming.

Currently, in mobile applications, we don't have push notifications. We're hoping that will come in the new release. 

I've been using the solution for 3.5 years. 

It's stable enough. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. If I want to do any changes or anything, it has a one-click publish. There's no need to re-upload anything. We make changes, we expand, and it is a one-click deployment.

Currently, in Bahrain alone, there are 40,000 users on the app. We have the same for other countries as well. We have deployed more production for three entities - Bahrain, Egypt, and the UK. Currently, for the other three entities, it is in progress. We are planning to move those changes at the end of September.

We can add users as necessary. In LifeTime, we're able to handle user management. We're able to create a set of users and we can assign roles. It can be an admin role, like full control where it's able to do publishing, feedbacking, everything. We can receive a set of users and control access to certain areas. 

Technical support is very good. If there is any production issue or anything, we can raise the ticket and they're immediately helping. If there are any deployment changes that get affected, it means we have control of all directions also. Therefore, we can manage everything properly, without any effect, actually. Everything is completely handed down to OutSystems and it is more stable. If any deployment causes us an issue we can revert back to the older version and it'll work fine.

Before that, I used a server platform called Forti. It is similar to the OutSystems Platform. We were able to use mobile and web publications and able to create using that.

I worked on an AD platform as well. 

Comparatively, I'm able to see OutSystems is very easy to maintain and easily fulfills the business requirements. 

The deployment and process depends upon the model we are selecting. Normally consider if we are selecting big models, it'll take around 30 to 40 minutes for making a deployment to set up 15 applications. For example, if it is a mobile application, it means if we can select only the application, it will take a maximum of five to ten minutes for creating the solution and deploying in the UIT of production. For internet banking, we use Windows authentication, ID logins. For mobile banking, we used third-party APIs. We used common plugins for the camera location and everything. We integrated with Apple, Google, and Apple Wallet also.

Everything is completely handled in OutSystems, so we have a LifeTime available in OutSystems. Previously, we don't have LifeTime so we manually exported the solution and we deployed it in the UIT. With the help of LifeTime, we're able to see the versions and the differences. We can select the proper particular application and we can do the deployment. It is easy to maintain and easy to deploy as well.

For doing the deployments, any changes, are completely handled on our side.

I'm not sure how the licensing is set up. I don't handle that aspect.

However, I am able to see it s very costly as compared to other platforms. That said, we see the benefit of paying so much. They provide a lot of options. 

While we use version 11.10.20 for service, the service center for LifeTime is 11.0. Currently, we need to upgrade that. The upgrade plan is in progress. We have had to start recently.

I'd recommend the solution to others. 

I would rate it eight out of ten.

We use OutSystems for developing applications that are used by clients in Canada, USA, and Europe. OutSystems has been very effective for us in developing both web and mobile applications. It has reduced our development time by around 30 to 40 percent.

We've used features like batch processing timers, components, and integrations with other systems like SAP, which have accelerated our development process. In terms of productivity, we've seen a 30 percent reduction in screen design time and an additional 10 percent improvement when implementing client requirements. OutSystems' integration capabilities have significantly enhanced our app's functionality, making it quicker and easier to connect with other systems.

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.

I've been with OutSystems for about three and a half years now.

On a scale from one to ten, I'd rate the stability of OutSystems at nine.

In terms of scalability, I'd rate it at eight.

OutSystems' technical support has been very helpful and responsive.

Positive

Before OutSystems, I mainly worked with .NET and Android development.

Deployment with OutSystems has generally been straightforward, although we've encountered some challenges with UI development.

I'm mostly focused on development, but our DevOps and maintenance team consists of about five to six people.

The main benefits we've seen after implementing OutSystems include significant time savings, improved deployment processes, and convenient configuration settings in the service center.

As for licensing costs, I'm not directly involved in that aspect.

Overall, I'd rate OutSystems a nine out of ten.

The solution can be used to develop apps, websites, and core applications. We are working for an insurance company on an application to digitize hundreds of documents. We also work for a bank on an application to manage time and time sheets.

It is easy to develop things. It is much easier to develop applications with the product’s IDE.

OutSystems is creating a new platform on the cloud called ODC. The new version could be improved.

I have been using the solution for about five years.

The tool is quite stable. It depends on the way we use it.

Our clients are medium and large enterprises.

My team contacts support. The support responds quite well.

Positive

We have used some local platforms before.

The initial setup is straightforward. Normally, the solution is cloud-based, but it depends on the clients. For the setup of the platform, we must have a contract and license from OutSystems. The setup takes one to three weeks.

The return on investment is difficult to measure, but the time to market is much faster.

OutSystems has a lot of traction in Portugal. We are studying Mendix and Appian to see if they could be adequate in some cases. Some clients don't have the capacity to support OutSystems, or they might be using other tools. We want to adapt to other platforms and tools. Overall, I rate the product an eight out of ten.

I have used it for a company in Saudi Arabia. The application was mainly focused on transportation. The other application is a recent upgrade.

I love OutSystems because, as a manager and someone who has experience with various traditional development technologies (approximately 20 technologies), it provides a standard approach. Unlike other companies where there is no development standard, with OutSystems, we have our own standard. This makes it easier when transitioning between developers or onboarding new team members.

It's not easy to master OutSystems within the first month. Even if you have ten years of experience, like me, it will take about two to three months to explore everything. For example, customizing a header or integrating a video is not easy. 

Many people assume that mastering OutSystems is as simple as drag and drop, but for specific tasks, you need someone with development experience, preferably a senior or expert with over five years of experience. 

Sometimes it requires both skills, someone who knows how to develop and add script code or extensions to our system. However, there are also times when it is easy. Let's say around seventy percent of the time; it's easy. Customizing the user interface, aside from the header, is relatively straightforward, although I did encounter difficulties with the header. 

Another example is working with live video, which is also not easy.

I have been using OutSystems for one year.

It is very stable. I would rate the stability a nine out of ten. 

The scalability of OutSystems is not bad. I know someone who conducted a scalability test. They used SCC Solutions, a telecom company with a great team of developers. They encountered some issues compared to what OutSystems claimed. However, I believe you always need to have a package that can handle more users than OutSystems recommends. 

If they suggest an eight-gigahertz processor, you should go for a better specification. But overall, it's not a major problem. Just make sure to exceed the recommended specifications. OutSystems is widely used in many regions. It's extensively utilized in the UK and Australia, as I have experience working with these countries. However, in some countries, traffic and other factors can make it more challenging.

I did contact the customer service and support team, but they mostly provide general IT support.

I believe there is room for improvement in technical support. However, they are good and responsible in terms of providing documentation and guidance to help you.

I believe you would need someone who is already good in development or has a logical understanding of development. OutSystems has four layers: the timers and processes layer, the interface layer, the version layer, and the database layer. 

Sometimes, when you add a module from the first layer, it doesn't work because it needs to be compatible and supported by the OutSystems platform. Many components or modules from the first layer are often incomplete or non-functional when compared to the later layers. 

Therefore, you need to comprehend the logic and then integrate it. It's not always straightforward. There are challenges involved. 

If you don't have someone who is already skilled in development, most of the time, you won't succeed. I believe you need a certain level of intelligence to excel in OutSystems. You have to be intelligent, like in development. 

I've brought in many developers who weren't skilled in development and put them in our system. They excelled at all the traditional tasks but when I asked for any custom work, it took them around one month to finish.

The deployment process is very easy. It involves just one publish button. They call it the "one publish" button.

In our system, there are always many challenges in development. For example, you don't need an administrator or a developer because we have something called architecture AI. It can evaluate your application and determine if it follows the best practices or not. We already have a baseline of good practice cases or standards for our system, so we're not far from the best practices. There are certain things you can't do directly, like calling a server action. Instead, you need to use client actions. 

There are many perspectives like this that you need to consider. Otherwise, it won't work. For example, you can't simply drag and drop a client action inside a server action. 

I believe anyone would require about two to three months of training, and they would need to build their own application. The issue in our system is that sometimes developers are only skilled in either logic or UI. I think it's important to train people to be proficient in all aspects.

There is an annual cost of approximately 23k. So sometimes, you need to wait for a return on investment. It also requires skilled individuals who know how to utilize this technology and train others. Finding good developers isn't easy because most of the people who work with OutSystems come from Big Data or have multiple engineering backgrounds. We face difficulties in finding the right people, and I think this is a common issue across platforms. Nonetheless, I consider it a unique feature.

Overall, I would rate the solution an eight out of ten. I still believe in our system, despite some limitations in traditional development. There is always room for improvement. 

I think they are constantly making progress and adding new features. However, sometimes it's not easy to achieve customizations.

My client is the owner of the OutSystems platform, which we have utilized for various purposes, including an event app. This app tracks agendas, speakers, and registration for events.

The most valuable features of OutSystems are the user-friendly platform. The drag-and-drop feature is great. I have used other rapid application development tools before, but they were not as advanced as OutSystems. With the previous tools, I had to manually build certain features, but OutSystems does it automatically.

OutSystems has the ability to create algorithms based on the data requested. I can specify what data I need in natural language and the platform will build the algorithm for me. This is a great feature.

I like the OutSystems platform. I am working on integrating it with another platform using APIs, however, it has proven to be difficult. The main issue I am facing is obtaining authorization tokens as well as access and refresh tokens. It may be due to my lack of knowledge of APIs as it is new to me.

The documentation could improve. The reason I am having many problems with the APIs is that there is not a comprehensive piece of documentation that I can read that explains exactly how to do what I'm doing. I've tried the forum, I've tried the Forge, and downloading other components, trying to look at that. However, there isn't a good simple explanation of how to do it.

I have been using OutSystems for approximately a year and a half.

The platform is very stable, and I have not encountered any issues or crashes so far. I cannot speak to how it performs on more advanced tasks as I have not encountered any such scenarios yet.

OutSystems is a scalable platform.

I rate the scalability of OutSystems a nine out of ten.

I have not yet needed to reach out to the technical support team. I am currently attempting to troubleshoot the API integration on my own as per my agreement with the client. However, if I am unable to find a solution, technical support would be my next step.

The solution is expensive. The platform is not suitable for all of my clients. I work with labor unions and other smaller organizations that would not be able to afford the platform's current pricing model. It would be beneficial if there were a scaled-down version or a tiered pricing option that would allow me to build an app or a web app that is more cost-effective for my clients. Currently, the platform's pricing is too high for many of my clients, who would not be able to afford something in the $50,000 to $100,000 range.

I rate OutSystems a nine out of ten.