SAP Fiori and UI5 apps your team actually wants to use.
Custom Fiori and UI5 applications, Fiori Elements and SAP UX modernisation — designed with the people who use them every day, and built by engineers who also ship React, TypeScript and Java backends. Which is why our SAP applications do not feel like SAP applications.
This is for you if…
- You run SAP, and the screens your people use every day slow them down.
- You need a Fiori or UI5 app that the standard apps do not cover.
- Your data lives in SAP, but the workflow around it lives in spreadsheets and email.
- You want the team that builds the app to also test, deploy and maintain it.
When we are not the right fit
We are not an SAP partner and hold no SAP certification. If formal partner status is a procurement requirement on your side, we are not the right fit — and we would rather say so now.
What we usually hear first
“Our people avoid the SAP system.”
That is a design problem, not a training problem. We research how the system is actually used and redesign the workflow around the people in it.
“Every report is a ticket to IT.”
Business users wait days for a number. We built a no-code query explorer on SAP HANA so analysts get it themselves, within their role’s permissions.
“SAP agencies build SAP-looking screens. Web agencies don’t understand SAP.”
We do both: Fiori design guidelines and OData on one side, modern frontend engineering and automated testing on the other.
“The data is in SAP, Excel and CSV exports at the same time.”
We consolidate it into one source the application can trust — the first step in our SAP-integrated workforce planning project.
What you get
Custom Fiori & UI5 applications
Fiori Elements where the standard floorplans fit, freestyle UI5 where they do not. Built to the Fiori design guidelines, tested with QUnit and Playwright, deployed through CI/CD like any other modern codebase.
SAP UX modernisation
User research with the people who work in the system daily, then workflows redesigned around them — including S/4HANA UX and the modernisation of legacy applications.
React & TypeScript inside SAP landscapes
Where UI5 is the wrong tool, we build in React and TypeScript and integrate cleanly over OData and REST. Our DIDI platform runs SAPUI5, React and OpenBridge components in the same product.
Backends and integration
Java and Spring Boot services, SAP CAP, OData, RFC and REST, SAP HANA and PostgreSQL — with OAuth 2.0, Keycloak and role-based access that follows your existing SAP security.
Technology
From first call to working software
Week 0
Free first consultation
About 30 minutes. You describe the app or the workflow; we tell you whether Fiori Elements, freestyle UI5 or React is the right tool — and whether we are the right team.
Weeks 1–2
Prototype and delivery plan
A clickable prototype following the Fiori design guidelines, an integration map and a scoped plan. The plan is yours whether or not you continue with us.
Weeks 3–6
First implementation scope
Two to four weeks of building against your SAP landscape, with automated tests and a CI/CD pipeline from the first commit.
Ongoing
Operate and extend
Security patches, dependency and UI5 updates, and new features — by the same people who built it.
Typical for a first scope. Larger platforms are planned after discovery, because a timeline before that would be guesswork.
Work that shows how we do it
Before you ask
- Are you an SAP partner?
- No. We hold no SAP partner status and no SAP certification, and we will not imply otherwise. What we have is a decade of shipped SAP Fiori and UI5 work and our own SAPUI5-based platform running in production.
- Fiori Elements or freestyle UI5 — which do we need?
- Fiori Elements when the app follows the standard floorplans — list report, object page, worklist — over well-annotated OData services: it is faster to build and inherits SAP’s own updates. Freestyle UI5 when the workflow does not fit those floorplans. React when the interface goes beyond what UI5 does well. We settle it in the prototype, not in the sales call.
- Can you modernise an existing SAP app instead of replacing it?
- Yes, and often. We start with an audit of the existing data models, integrations and manual steps, and with the people who use the app, before committing to any scope.
- Who maintains the app after go-live?
- We do, if you want us to: monitoring, security patches, dependency updates and new features, with direct access to the engineers who built it.
Tell us what you are trying to build.
A free first consultation of about 30 minutes, with the specialists who would deliver it — and an honest answer on whether we are the right fit.