Services · Building block

Software for the gap no product fills.

Custom software where off-the-shelf software falls short: we build what is missing, with or without AI. The code is yours.

Shift_plan_final_v7.xlsmM. Weber only

Security warning: macros have been disabled.

=IF(COUNTIF(Absent!B:B,$A4)>0,VLOOKUP($A4,Pool!A:F,6,FALSE),"")

SiteMonTueWed
North HospitalKayaKayaLenz
West OfficesLenz#REF!Roth
Peters MotorsRothRoth#N/A
Park SchoolSommerSommerSommer
Report absenceNolte Cleaning Services
AbsenceA. Lenz, Tue 06:00, West Offices
Cover 1J. Roth, all clear
Cover 2M. Kaya, all clear
Cover 3T. Sommer, rest period ok
Ask
  • Standard first

    We check products, unused ERP modules and low-code before anything is built. Even when that argues against the job.

  • Usable within weeks

    The first piece runs in real operation after a few weeks, not as a presentation after six months.

  • The code is yours

    Repository, documentation and freely available dependencies. Run by us or by your IT.

  • No knowledge locked in macros

    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.

Where it gets stuck today.

  1. The spreadsheet only one person understands.

    Macros, four windows and an order of steps written down nowhere. It works until that person is on holiday.

  2. Two systems that do not know each other.

    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 Finance
  3. 77%

    Calling instead of looking it up.

    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 fax

Check

Standard first, then build.

We weigh products, unused modules of your ERP and low-code against your process. We only build what none of them covers.

Options for shift planningAssessment
  1. ERP HR moduleno absences per sitegap
  2. Rostering productno site clearancesgap
  3. Low-code formrest periods only by scriptlimit
  4. Own applicationcloses the gaprecommended
Recommendationto management

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

Interfaces, portals, apps.

Usually what is missing is not a whole system but a piece in between. We build that, with or without AI.

  • Interfaces

    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.

  • Portals

    For customers, brokers, tradespeople or tenants: check status and documents themselves instead of calling.

  • Apps and business applications

    Review screens and approvals around the AI, mobile capture with photos, planning and dispatch with no AI at all.

E-invoiceInbox
  1. FormatXRechnungread
  2. Vendor70412 in the ERPmatched
  3. OrderBE-40211found
Report damageTenant portal
FlatLindenstrasse 12, 2nd floor left
DamageWater stain on the ceiling
PhotoIMG_2214.jpg
StatusTradesperson booked, Thu 9:00
Send

Build and hand over

From the first piece to the handover.

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.

Shift planning processWorkshop

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

Report absenceWeek 3
EmployeeA. Lenz
SiteWest Offices
ShiftTue 06:00 to 10:00
Reasonsick
SuggestionJ. Roth, rest period respected
Ask
HandoverShift planning
  1. Repositoryin your accounthanded over
  2. Documentationlogic and operationscurrent
  3. Testsrest periods, payroll exportpassing
  4. Operationyour ITagreed

Approaches

Buy, configure or build.

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.

  • A web application built for you

    Our default

    Our stack, run in Germany

    Fits when
    standard software does not cover your process. We build in TypeScript with PostgreSQL, tested and documented, run in Germany or on your premises. Code and data are yours.
    Mind
    First we check whether standard software or configuration is enough; we build only the piece that is missing.
  • Off-the-shelf software or SaaS

    Buy, run by the vendor

    Fits when
    a product covers most of your process. Quick to roll out, operation and updates stay with the vendor.
    Mind
    Licence costs run per user for good; data and process follow the product, so check the export first.
  • Configure standard software

    Make better use of what you have

    Fits when
    your ERP, CRM or DMS already has the function, as an unused module, field or workflow. Often the cheapest way.
    Mind
    Document what was configured, otherwise the knowledge sits with one person.
  • Extend the ERP itself

    The vendor extension framework

    Fits when
    the gap sits close to the ERP. Vendors offer their own routes, for example SAP BTP or extensions for Microsoft Dynamics 365.
    Mind
    Bound to the vendor technology; extensions have to survive upgrades, kept apart from the core is better.
  • Low-code platform

    Such as Power Apps or Retool

    Fits when
    For internal forms, approvals and overviews on existing data, when you already hold licences and the requirements are modest.
    Mind
    The application only lives on the platform; check per-user licences and limits on complex logic early.

Tasks and limits.

What inviqon takes on

  • Interfaces between systems, including legacy systems without an API and e-invoicing
  • Portals for customers, brokers, tradespeople or tenants, with status and upload
  • Screens around the AI: review masks, approvals, mobile capture with photos
  • Business applications without AI, for planning, dispatch or costing
  • Automated tests for the parts that money or data depend on
  • A first piece in real operation within weeks; code and docs are yours

What your team takes on

  • Decides whether to build, even when we advise the standard
  • Checks anything binding before it goes out
  • On co-determined topics such as shift planning, the works council is at the table before the build
  • Not included: rebuilding a product that already exists
  • Not included: a fix for a process the business itself has not settled
  • Limit: not cheaper than a fitting standard, running, updates and security carry on

Custom software

Agents and automation work inside your systems, integration connects them. Custom software builds what is missing: the interface, the portal, the screen around the AI, or the application itself.

Which one when?

  • AI integration

    The systems are there and only the connection is missing? Then AI integration is enough.

  • AI agents

    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.

  • Data & documents

    If the question only needs a figure or a report, we do not build an application. That is data and documents.

The way there.

From the first call to a system in operation. Each phase stands on its own; none ties you to the next.

  1. Intro call

    free

    30 minutes. We work out where AI fits for you and whether an AI strategy is worth it.

  2. AI strategy

    €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.

  3. Pilot & implementation

    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.

  4. Operation & improvement

    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

Common questions about it.

The questions that almost always come up.

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.

What about low-code platforms?

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.

Do you build software without AI?

Yes. Many applications are forms, rules and interfaces. AI goes only where a judgement is needed.

Who owns the code?

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.

What happens to the software if we change supplier?

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.

How does a custom software project start?

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.

What does custom software cost?

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

Let us find out where AI pays off for you.

30 minutes, free and without obligation.