When is standard software the better choice?
Almost always, where a product covers most of the process. The rest usually costs less as configuration of that product than as an application of your own plus the running of it.
We check products, unused ERP modules and low-code before anything is built. Even when that argues against the job.
The first piece runs in real operation after a few weeks, not as a presentation after six months.
Repository, documentation and freely available dependencies. Run by us or by your IT.
What lives in a spreadsheet and one person's head today ends up in an application with tests. A holiday no longer stops the process.
Macros, four windows and an order of steps written down nowhere. It works until that person is on holiday.
Data is retyped by hand because there is no interface. E-invoicing forces the issue in Germany: receiving has been mandatory since 2025, sending follows in 2027 and 2028.
IHK Dresden: e-invoicing deadlines per the Federal Ministry of Finance77%
Customers, brokers and tradespeople ask for status and documents because there is no portal. Much between companies still runs without an interface.
Bitkom 2024: share of German companies that still faxCheck
We weigh products, unused modules of your ERP and low-code against your process. We only build what none of them covers.
Shift planning
Own application for absences and cover.build
Monthly plan and payroll export stay in the ERP.standard
Reports per site: review after three months in use.later
What we build
Usually what is missing is not a whole system but a piece in between. We build that, with or without AI.
Between ERP, shop and DMS, to legacy systems without an API, and for e-invoicing, which German businesses must be able to receive since 2025.
For customers, brokers, tradespeople or tenants: check status and documents themselves instead of calling.
Review screens and approvals around the AI, mobile capture with photos, planning and dispatch with no AI at all.
Build and hand over
We cut the process down to the piece that hurts most today and build it with the people who will use it. At the end, code, tests and documentation are yours.
How it runs today
Build the monthly plan for 14 sites.
Report an absence, find cover, call round one by one.first piece
Hand hours over to payroll.
Reports per site and month.later
Approaches
Every gap has several ways to close it, and building is rarely the first. We compare them on three questions: who owns the result, how tightly does it bind you to one vendor, and what does it cost over the years, not just at the start.
Our stack, run in Germany
Buy, run by the vendor
Make better use of what you have
The vendor extension framework
Such as Power Apps or Retool
What inviqon takes on
What your team takes on
Custom software
The systems are there and only the connection is missing? Then AI integration is enough.
If something should work inside your existing systems, that is AI agents. If the screen to review its work is missing, custom software comes in.
If the question only needs a figure or a report, we do not build an application. That is data and documents.
From the first call to a system in operation. Each phase stands on its own; none ties you to the next.
free
30 minutes. We work out where AI fits for you and whether an AI strategy is worth it.
€1,990
AI strategy for mid-sized companies: which of your processes suit AI, what the build costs and brings back, and which ones are not worth the effort.
from €5,000
AI pilot at a fixed price: one use case, fixed scope and acceptance criteria in writing up front. Built in your systems, tested with your data.
from 20% a year
Running AI systems: hosting in Germany, monitoring, model and prompt maintenance, ongoing measurement, and the next use case on the same foundation.
Frequent questions
The questions that almost always come up.
Almost always, where a product covers most of the process. The rest usually costs less as configuration of that product than as an application of your own plus the running of it.
Often the right choice for forms and simple processes, and we say so. The limit is reached when the logic ends up in scripts outside the platform, or the per-user licence eats the benefit. We check both before the decision, not after.
Yes. Many applications are forms, rules and interfaces. AI goes only where a judgement is needed.
You do. Source, repository and documentation transfer to you, with dependencies that are freely available. An application only we can run is a dependency we do not want to sell.
Then somebody else takes over. That is exactly what the documentation, a small technology choice and tests on the parts that carry weight are for. We build for the case where we are no longer involved.
With the smallest piece that is usable in daily work, and with the people who will use it. It runs in real operation after a few weeks. An application first shown after six months has been a guess for six months.
Like every building block: a fixed-price project per use case, with scope and acceptance criteria agreed in writing first. Afterwards we run it, or hand it over to your IT.
The next step
30 minutes, free and without obligation.