Approach

Work first, then the technology.

Software that gets in the way is almost always software thought up too early. Someone chose a tool, an architecture, a screen — before it was clear how people spend their day. We reverse that order.

Monolithical works with smaller organisations: SMEs, associations, schools. Not because everything must be automated, but because the people who do the work deserve tools that help — and because a little support often does more than a large system.

The order

Listen to the process Who does what, where does it stall, where do people work around it? We talk to the people who do the work, not only to the brief. A sketch of the process says more than a wish list.
Choose what software is allowed to be Not every friction asks for something new. Sometimes the gain is a clearer website, a smaller tool, an existing off-the-shelf solution, or dropping a step. We say that out loud. Building is not the goal. A good solution is.
Make what keeps working If we build, we build for maintainability: server and frontend in one line, interfaces that follow the task, code you can still understand later — or have understood. We do that as experienced software engineers who, from that discipline, can use AI correctly: AI-assisted, so costs can stay low. Lasting is cheaper than starting over.
Give it back to the people Delivery is not a dump. We check whether the work has become lighter. If not, it is not done. Software succeeds when nobody has to complain about it.

Facilitate, do not dictate

A system must not become another boss. It may remind, order, hand over, speed up. It may not demand that the organisation fold itself around the software if that software does not know the practice.

That is why digitalisation advice starts with what you already do. We look for the smallest change that supports the work. That is thriftier — in budget and in attention — and it lasts longer.