Missing something? Then we build it.
Our tools exist because a customer had a requirement the standard had no answer for. If yours is not in the catalogue yet, that is not a rejection — it is the normal beginning.
Not every problem needs new software
Sometimes the answer is a tool, sometimes an interface — and sometimes simply a process that finally fits your company. We look at which of the four routes is the most economical in your case.
Extensions inside S/4HANA
Additional functionality where your users already work: custom transactions, extended standard screens, checks, analyses and automation — implemented cleanly through extension points so the next upgrade does not tear anything apart.
Interfaces and integration
Connecting S/4 to the world around it: third-party systems, portals, shops, machines, cloud services. Via RFC, JSON, REST, SOAP, files or events — whatever the counterpart supports and the process requires.
Adapting processes to your business
Frequently the best answer is not new software but a standard process tailored to your company — through customizing, control tables and supplementary logic. Less custom code means less maintenance.
Consulting and design
Before anything is built we clarify what the problem actually is. Process analysis, feasibility, effort, alternatives — and a design the business side understands too. On request we also take over test and change management.
Which area it is stuck in matters less than you think
Since 1994 our consultants and developers have worked in practically every corner of the SAP world. Whatever is open at your end, chances are we have solved it before.
How a project runs with us
1. A conversation about the problem. Not about the desired solution — about what actually gets stuck in daily work. That half hour often already decides whether this becomes a large or a small project.
2. Assessment and approach. We tell you what is possible, roughly what it costs and which alternatives exist — including when the cheapest alternative means we earn less.
3. Design and quotation. A design that business and IT can both read, with a fixed price or a solid effort estimate.
4. Implementation in your system. Built, documented and tested to the standards your Basis team requires — cleanly through extension points so upgrades keep working.
5. Operation. On request with a maintenance contract, further development along your releases and fixed contacts instead of rotating staff.
What customers want to know beforehand
What if no tool in the catalogue fits?
Then we build it. Most of our tools started exactly that way: from a requirement the S/4 standard had no answer for. Describe your case — the first assessment is free and without obligation.
Which SAP modules do you develop in?
Practically all of them: logistics (MM, SD, PP, WM, QM, PM), accounting (FI, CO), PLM and variant configuration, document management and archiving, HR-adjacent processes as well as the technical areas Basis, interfaces and authorisations.
Can existing SAP processes be adapted?
Yes. Often the better answer is not new software but a standard process tailored to your company — through customizing, extension points and supplementary logic that stays upgrade-safe.
How does such a project run?
First a conversation about the actual problem, then an assessment of effort and approach, then a design with a fixed price or a solid estimate. Development happens in your system, documented and tested — and afterwards we take over maintenance if you wish.
Does the solution stay upgrade-safe?
That is the standard we hold ourselves to. We work with the intended extension points rather than modifications and document what intervenes where. Where a change to the standard is unavoidable we say so beforehand — including what it means for later upgrades.
Tell us what is missing
No specification document needed, no preliminary project. One sentence about the problem is enough to start — we clarify the rest in conversation.