B Software development
Tools for processes that exist only at your place.
Off-the-shelf software covers eighty per cent. The remaining twenty cost your team hours every week. That is exactly where we start, with small applications instead of large projects.
We begin with the case, not with the technology: who does what, where the process breaks, which data sits where. After that comes a working slice through the entire application, before anything is built out.
That way you see early whether the direction is right and can steer the scope while doing so is still cheap. Whatever is finished goes into service, even if the rest is still missing.

B.1 Fields
- Interfaces
- Two systems that know nothing about each other, and a person copying data between them: that is the most common job that reaches us. We build the connection, including error handling and a log, so that it can be traced later on what actually happened.
- Automation
- Producing reports, collecting files, reconciling stock, watching deadlines. Whatever runs the same way every week afterwards runs by itself at night and only speaks up when something is wrong.
- Business applications
- When there is no suitable off-the-shelf software for your process: a lean application with a database, user permissions and reporting. Start small, grow it on real cases.
- Operation
- We operate what we build: in containers, with backups, monitoring and a tested way back. On request we hand over to your own IT instead, with documentation and a handover meeting.
B.2 Tooling
What we work with.
- Languages
- TypeScript and Python for most things, SQL for everything that involves data.
- Data
- PostgreSQL and MariaDB, plus file storage with clear permissions instead of network drives that grew over the years.
- Operations
- Docker on our own servers, a reverse proxy with automatic certificates, backups with restore tests.
- Handover
- Source code, documentation and credentials are yours from day one.
None of this is an end in itself. We pick what fits the problem and what another team can carry on with later.

A process that is costing you time?
Describe it in a few sentences. After one conversation it is usually possible to estimate whether automating it pays off, and from when.
Describe your case