Where off-the-shelf software ends, we begin.
Data carried by hand from one program to the next. Systems that do not talk to each other. Software that covers most of your work and leaves you the rest. We build that rest — and we set it up and keep it running.
If any of these sound familiar, you are in the right place.
You move information by hand from one program to another.
Export, fix, import. Every time. And sooner or later someone forgets.
Your software covers most of the job — the rest you do by hand.
For that rest there is a separate file, a separate list, a separate person.
Two systems do not talk to each other.
You enter the same information twice, and eventually the two stop matching.
How we solve it
Three typical situations — and where off-the-shelf software runs out in each.
Holding up at peak times
Load was uneven across the year: campaign weeks, enrolment periods and month-end closing multiplied usage, while in between the system sat almost idle. We built the application around that rhythm — fast at the peak, without burning resources in quiet periods.
Why off-the-shelf did not fit: packages that can carry this load are priced with their full feature set and for peak capacity — a few weeks of peak would have meant paying a full year’s licence. Having only the part you need built comes out considerably cheaper than renting hundreds of features you never touch.
Removing the manual step in between
Information between two programs was exported, corrected and re-imported every single time. We took out the interim file and the person carrying it; the systems are now connected directly.
Why off-the-shelf did not fit: neither program knew the other’s data model, and the conversion rules in between were specific to the business.
Connecting hardware to the web
The device on the bench measures — but the reading was written on paper and typed in later. We wrote a bridge between the device and the web application; the reading lands directly in the record.
Why off-the-shelf did not fit: no ready-made product knows that device’s protocol. This connection only exists if someone writes it.
What we build
Not a list of services — the kinds of systems we deliver.
Six kinds
Internal operations software
The software your team works in every day: workflows, permissions, records, approvals.
Customer portals
The outward face where your customers see their own data, orders and documents.
Mobile applications
In the field, at the bench, on the move — not at a desk.
Integration & automation
Connecting systems that do not talk; turning manual work into a process.
Device & hardware bridges
Scales, scanners, meters — connecting physical devices to software.
Data & reporting
Bringing scattered data together and making it decidable.
What sets us apart
We build it, set it up and run it.
Custom software is not finished on launch day: operating systems, libraries and connected services keep changing, and the application needs regular care. A support contract makes that care predictable — updates, security patches, monitoring and technical support you can reach whenever you need it.
You can rent the infrastructure from us as well: your application runs on our rental servers together with backup, monitoring and mail infrastructure. If you prefer your own servers, we set it up and maintain it there.
How we work
The biggest worry with custom software: an unclear budget and a project with no end. Our answer is these four steps.
1.0
Discovery
Short and paid. The output — a process map, a scope and a budget range — is yours. Even if you do not continue with us.
2.0
Prototype
A working first version. You see the screens with real data; we discuss scope by using it, not by reading a document.
3.0
Delivery in stages
Each stage is usable on its own. The project is not finished one day — it is in use from the first stage.
4.0
Operation
Servers, backup, updates, monitoring. It stays with us or moves to you — your call.
Starting budgets
In numbers
Blog
Notes from the systems we have built and run.
The first post is on its way.
Let us start with a discovery.
Tell us, we will listen. Discovery is short and paid; at the end you hold the process map, scope and budget range. If we conclude that an off-the-shelf tool would do the job, we will say so just as plainly.
DARFA · Berlin
We use your details only to answer this enquiry and never pass them to third parties.