Tracking and automation systems
Systems that follow an institutional process end to end: forms, approval steps, authority schemes, deadlines and reporting. Built with service interfaces so that other systems can connect to them.
Solutions · Custom software
Systems designed around institutional processes
Software that follows a process from beginning to end, connects to existing systems through service interfaces and is designed for long-term operation. We apply the same working method here as in our own platforms.
Scope
What we build
Integration and service layers
A layer through which existing systems exchange data, so that the same record does not have to be entered in several places. Interface contracts are documented, and failures are reported rather than passing unnoticed.
Replacement of an end-of-life system
When a system can no longer be maintained, it is rebuilt without data loss. Migration follows a plan, and existing records keep their meaning in the new model.
Document and report automation
Official letters, certificates and periodic reports generated in bulk from the institution’s own templates, with values taken from the system rather than entered manually.
How we work
What stays constant across projects
- Process before software
- We start by documenting how the institution works today, down to who does what and how. The system is then designed on that basis rather than on assumptions.
- Configuration rather than code changes
- Approval steps, form fields and authority schemes remain configurable. When the institution changes, the software can be adjusted without developer involvement.
- Every decision recorded
- Who decided what, and when, is kept in an audit trail that cannot be altered afterwards. This allows a decision to be explained years later.
- Handover is part of the work
- Source code, deployment chain and documentation belong to the institution. Systems are built so that they can be operated independently of us.
Scope of advice
New software is not always the appropriate answer
Not every requirement calls for a new system. If the existing system can be repaired, extended or configured differently, we say so; that assessment falls under technology consulting rather than a development contract.
We prefer to decline a project that we consider unsuitable at the outset, rather than take it on and discover this later.
View technology consultingDescribe your process
We start by understanding how the institution works today. The shape of the solution follows from that.