The pain is the licence
The platform has done its job: the applications run and the organisation leans on them. But the bill grows with every user and every renewal, and the code is not yours. Anyone who wants to leave first needs to know exactly what is running and what it costs to rebuild. That is exactly what the assessment gives you.
On top of that, developers for such a platform are in short supply, and because of the knowledge required and the licence you cannot let business users develop themselves.
The pain with OutSystems
With OutSystems the licence grows in two ways. The first is the number of users: every employee, customer or supplier who logs in counts, so an application that succeeds becomes more expensive by itself. The second is the size of the application: you pay per component, so per screen, per table and per integration.
Because with OutSystems you cannot create tables at runtime, every integration needs fixed tables for staging data. With an integration to, for example, an ERP such as SAP that weighs heavily: the OData services of such a system can only be used to a limited extent from the platform, so even more data ends up on the low-code platform. More users and more tables mean a higher licence, without a single extra feature.
The pain with Mendix
With Mendix you pay a fixed amount for the platform and, on top of that, per user. The platform fee comes in two flavours: one application or unlimited applications. Anyone who starts with one application and wants a second therefore takes a large step in the licence at once.
The users are the second pain. Internal and external users both count, and a portal for customers or suppliers in particular makes the number rise quickly. Mendix users themselves name that as the point where costs get out of hand. The result is the same as with OutSystems: the licence grows with the success of the application, not with what it delivers to you.
How the assessment works
-
Inventory (1 week)
Which applications run, how business-critical they are, how many users, which integrations. We look along in your environment; you do not need to prepare anything.
-
Verdict per application
Keep, rebuild or retire. One recommendation per application, with the reason.
-
The sums
What you pay now, what the replacement costs and when it pays back. In plain language, on one page.
-
Your choice
You decide. Even if you do nothing, you know exactly where you stand.
What you get
- A report with, per application: keep, rebuild or retire.
- The sums: licence today, cost of replacement, payback period.
- A proposal for the first step, at a fixed price.
- Software that is yours afterwards: your own code, your own database, no licence per user.
How we replace
We have bundled the best of low-code in FlightDeck. You develop with AI instead of a graphical interface. Without the high licence costs and without the technical limitations, but with the robustness and security these platforms offer. Business users can develop with it too. And many times faster.
We rebuild into full-stack software in .NET, with AI-driven development: as structured as low-code, but in code that belongs to you. Read how that works in our articles on OutSystems, the exit plan and the cost of low-code platforms.