Business applications
Software for processes that no standard product covers — or where the standard product would have to be bent so far that nobody could update it afterwards.
Service area 2
Software Development
We do not only advise, we build. And we stay once the software is running — that is when the interesting questions start.
Handover is not the end
The most common reason custom software fails in mid-sized companies is not poor code. It is the moment after go-live: the supplier is gone, the documentation describes a state from three changes ago, and the one person who understood the system now works somewhere else.
So we work the other way round. Operability, maintainability and the ability to hand over are not afterthoughts but requirements from day one. That does not make development more expensive — it merely moves part of the effort forward, to where it is cheaper.
What we build ranges from business applications through interfaces between systems that would rather not speak to each other, to pattern recognition. Proven fields are recruiting, transport and logistics, financial services and manufacturing.
What we build
Individually commissionable. Taking over an existing system is also possible.
Interfaces and data flows
Two systems holding the same data and knowing nothing of each other: the classic case in a grown mid-sized company. We connect them rather than inventing a third place to store things.
Native apps for iOS and Android
Through to release on the App Store and Play Store. We have taken an app through review and therefore know signing, guidelines and update cycles from practice rather than from documentation.
Pattern recognition
Finding what stands out in large volumes of data — deviations in processes, clusters, relationships that nobody notices in day-to-day work.
Operation and maintenance
Monitoring, updates, fault resolution, further development. With agreed response times and a named contact.
Working with your team
If you have your own developers, we do not replace them. We supplement them where capacity or specialist knowledge is missing — and hand back once the gap is closed.
How we develop
Without methodological religion. What counts is that you see something running early and regularly.
-
Clarify requirements
Understanding comes before coding. Who uses it, what for, and how will we know it works? This phase is skipped most often and is the most expensive to make up later.
-
Slicing and effort
We cut the undertaking into pieces that are individually usable and cost them. You see what the first working piece costs — not only the whole.
-
Build in steps
Something that runs every two to three weeks. That lets you correct direction while it is still cheap.
-
Commissioning and operation
Rollout, user training, handover of documentation — and then ongoing operation, if you do not want to take that on yourself.
You have a requirement but no developer?
Describe what should be built. In the first conversation we will tell you whether we are the right people and roughly what to expect.