Skip to content

Service 01 / 06

Custom software when off-the-shelf falls short.

Applications for processes no standard product maps cleanly. Built in Mainz, run where your data is allowed to live, and made for your team to take over.

01

When this fits

Four situations in which this service is the right answer.

  1. 01.1

    A workflow runs across three tools, two spreadsheets and one person who holds it all in their head.

  2. 01.2

    The standard product covers 80 percent, and the other 20 cost time every single day.

  3. 01.3

    A grown system carries the business, but nobody dares to touch it any more.

  4. 01.4

    You need an interface between systems that were never meant to talk.

02

How I work

Order and stance. The four steps themselves are under Process.

Before any code, I write the workflow down as it really runs today, including the exceptions no process diagram shows. The data model follows from that, and only then the application. Reverse that order and the software ends up fitting the tool rather than the business.

Delivery comes in short intervals against a running environment. You can open the current state yourself at any time and change the scope while that is still cheap.

Technically this usually means TypeScript, React or Next.js in the front, Node.js and PostgreSQL behind. These tools are common enough that another team can take them over without me. Where a different stack fits better, I say so.

03

What you get

What belongs to you at the end and lives in your accounts.

  1. 03.1

    An application with tests, reviews and a security check as part of the delivery

  2. 03.2

    Source code, infrastructure and documentation belong to you from day one

  3. 03.3

    A decision log: what was decided, and on what grounds

  4. 03.4

    Onboarding for your team, so the handover isn't a project of its own

04

When I advise against it

The cases where I advise against it, told to you before the engagement.

If a standard product maps your workflow to 95 percent, custom software is the more expensive answer. You hear that in the first assessment, not after the first sprint. Nor do I build an app whose only purpose is that an app exists.

05

Questions

What is usually asked about this service.

01What does custom software cost?

A number you can rely on comes after the clarification; anything before would be a guess. Beforehand I can give you the order of magnitude and tell you whether the project pays off against a standard product at all. That assessment is free.

02Can we develop the software ourselves later?

Yes, that is the point. Code, infrastructure and documentation are yours, the tools are widespread, and onboarding your team is part of the handover.

03Do you only work in Mainz?

The office is in Mainz and on-site meetings are common across the Rhine-Main region. Most of the work happens remotely, for companies across Germany and Europe.

07

Let's talk.

You get an honest first assessment — including the times I tell you not to do it.

Response time
The same working day.
Privacy
No cookies. No trackers. No banner.
Location
Mainz, DeutschlandMainz
Optional.
What should come into being, and what is in the way right now? A few sentences are enough.