OutSystems

I use OutSystems to develop mainly B2B Applications. I have used it in Banking, insurance, utilities, etc.

I am a consultant and have been used platform in three large companies and two small ones. Three of those industries are insurance companies and others are communication companies. We have helped to build main web portals with different kind of transactional modules to allow companies' clients to perform online procedures/transactions/processes by themselves. We have integrated with AD and web services (soap and rest). Development is fast if requirements are well defined but even when those are not, changes are faster than doing them using other programming languages or IDEs.

It is being used as the strategic tool to manage all financial processes.

We use OutSystems for all kinds of internal business processes, where a full fledged externally exposed user interface is not required. Most of them are monitoring related, like invoice or payments overviews. But we also use it as a service layer, where the OutSystems application contains API's. OutSystems provides a way to implement a business solution in a seriously fast way.

It is being used by our department to build applications that the entire organization uses to cover our retail stores in sales. It's also used for the life of our product since it is designed to production; for SAP integration, to book flights, serve the POS, and some other utilities that cover company needs.

OutSystems is being used by most of the company. It is the core technology. OutSystems helps us create in-house solutions as well as solutions tailored to our customers' needs.

OutSystems is actually being used across the whole organization. From the very start, we wanted to implement a web application that could support all business needs in our company from the very start (consultation, quotation, etc, all the way to worker reported hours and validation). In the end, we wanted our whole business to go through this application.

We use OutSystems as an addition to our SAP systems. We especially do web and app development in OutSystems with a connection to our SAP environment. The connection is both ways. The developments we've done have met their goals, and we were able to speed up the arrival and departure of the barge handling (inland waterway) process by about 40%.
The event manager we built in OutSystems was a big success, as we could extend the SAP functionality but also improved the process tremendously.
On other terminals, SAP is not used, but Navision. Our goal is to have our external web sides integrated with SAP in Navision. At this moment it's a big challenge.

OutSystems is being used by Meivcore's IT department to develop an industry solution to modernize and make Meivcore's data and processes digital. Meivcore's core business is industrial maintenance and everything was done in paper. This had a lot of impact on the productivity in the company because they wasted a lot of time filling forms and checking data on paper. With the solution that we developed, we managed to make the workload a lot easier and helped with productivity and general happiness with our employees.

Low-Code technology from OutSystems is the main technology used by my organization. With it we help companies from different industries evolve their digital transformation journey, helping to create solutions that enhance the different usability experiences, both B2B and B2C.

We use it for specific user groups within our organization. The objective is for it to be used across the entire organization by creating a fully integrated Customer Portal.
At the moment, we use it for our drivers, for maintenance repairs, and for a select group of our customers. We have at the moment a fully functioning OutSystems applications within our company.

We have multiple applications. Serving citys, and housing companies in the Netherlands. Our software excels at matching houses to people with very complex rules. We serve 15 different areas in the Netherlands with over 400 customers in the housing industry. Our matching software makes available houses visible on the website currently used by over 1 million people from the Netherlands each month.

It is used as the core of our service-layer infrastructure across the whole organization. It is sending data from source to destination systems.

It started small and now is used more throughout the complete organization, and with our customers and partners. It solves the need in time to market, and adapts to the changing environment. We are currently at the point of deciding to go full speed with OutSystems and build several components covering complete business processes and replacing legacy and technical debt systems.

Currently it is only used by a selection of people because we are exploring the features and fit with the business cases. We now only focus on fast to solve problems so we can build some expertise and confidence in the business. The first use is well received so we have a start.

Right now we use it for prototyping. With this prototyping we do user research. We are working on using this product company-wide. The idea is that other departments can use it for app development or for internal communication.

It's being used by our developers to build our new backend housing software. Ths is done by 3 Agile Scrum teams.

We are using OutSystems as a strategic platform within our organization.

The following processes are managed within this system:

• Ecommerce / Mobile app
• Price calculation (sales and purchase)
• Aftersales

It is used in the mother company and in one of the daughter companies. They are both based in the Netherlands. In our case - at the mother company - we are developing a mobile app that is spread in more than 11 countries.

• Driving innovation, building applications and services to address our customer's needs
• Integration of internal applications
• ERP modernization
• Operational efficiency and process automation/improvement
• Custom applications which replace off-the-shelf solutions with are not extensively used (reduce licensing costs)

We currently use OutSystems company wide, with the ambition to make it the core of our IT landscape. Over time we learned that OutSystems can be used for almost all business problems/questions.

It is used to create service by service solutions for all use cases, and to replace legacy software and none digital processes. We have a team of 6 devs supported by UX, support, architects, and BAs, in 3 workstreams to produce all these solutions.

We've rebuilt our backend in OutSystems. The old backend was a 15-year legacy system that has been rebuilt and perfected in less than 2 years. OutSystems gave us a good overview of what to do and showed us where we could improve our code since it gives you a very good visual insight.

OutSystems is being used by an in-house scrum team. They are developing a new program that is used by employees and clients of the NGO. In the future, an app might be developed for clients.

We use OutSystems mostly for internal application development. Mostly administrative applications, but also applications that can be accessed from the outside. For example, applications that we use to promote our company at company-drinks and job markets. We use it, especially so that we can put together applications very quickly in an easy manner.