Web applications & internal tools
IfIf a workflow needs its own interface that no no-code kit can provide.
ThenA browser application tailored to the roles, data and steps of your business.
Services
What we build for your business.
Double data entry, approvals by e-mail, two systems that know nothing about each other: we build that away. Whether it turns into an automation, an interface or a web application of your own is decided by the workflow, not by a catalogue. How we go about it is described on the approach page.
Fixed price before we start · effort estimate before any commitment What we build
Five routes. Which one it is, your workflow tells you.
Each starts with a diagnosis. Only once it is clear where things get stuck do we decide together which route makes economic sense.
Automation
IfIf the rules are clear but people repeat them by hand every day.
ThenApprovals, documents, notifications and status changes run in the background.
Interfaces & APIs
IfIf data is carried between two systems via email or Excel.
ThenAn integration that connects systems directly and removes double entry.
Reports & dashboards
IfIf the decisive numbers only appear after hours in a spreadsheet.
ThenA dashboard or export that shows exactly the figures that matter.
Setting up existing software
IfIf an existing system fundamentally fits but was never properly rolled out.
ThenConfiguration, setup and targeted extension instead of a rebuild.
Real-world example
A door manufacturer has order confirmations checked by the mailbox.
Three clerks compared every supplier confirmation with the purchase order by hand, line by line, formatted differently by every supplier. Now a service reads the mailbox, finds the order, compares in a structured way and sends the clerks an e‑mail with the result.
Fixed price · about two months · goes live in autumn 2026- Connected to the existing mailbox, no new system
- Purchase order and confirmation as PDF or Excel, structured differently per supplier
- Learns new document variants itself, keeps running without us
With JMK
- Mailbox is read
- automatic
- Matching order found
- structured
- Comparison line by line
- minutes
- Report e‑mail with PDF
- Business
- Commercial doors, St. Pölten district
- Clerks
- 3
- Purchase orders
- 4–8 per week
- Target
- Minutes instead of hours
Support & further development
Launch isn’t the end.
We stay reachable, fix, adapt and keep developing, so the software grows with your needs instead of ageing. You reach the person who built the solution directly.
Maintenance & support
Bug fixes, updates and questions go straight to the development team. No anonymous ticket hotline.
Further development
New requirements are scoped, estimated and implemented in clear stages.
Handover & documentation
You receive documentation and all access at acceptance, and the source code on request at no extra charge. You may develop it further yourself or with another team (GTC § 7.3, § 7.5).
Custom vs. off-the-shelf software
Four questions we get asked first, often.
What is custom software?
Custom software is an application built for one specific business and its actual workflow, rather than for as broad a market as possible. It mirrors exactly the steps, rules and data that exist in your business, no more and no less.
What's the difference between custom software and off-the-shelf software?
Off-the-shelf software is built for many businesses at once: cheaper to start with, ready faster, but your workflow has to adapt to the software. Custom software is the other way round: more effort to build, but it fits the existing workflow exactly instead of the other way around.
What are examples of custom software?
For us, for example: a service that automatically matches order confirmations against purchase orders (see the door-manufacturer case), or JmkPOS, a point-of-sale system built specifically for club events rather than general retail. Neither would have been solvable with off-the-shelf software, or only with detours.
When is custom software worth it over off-the-shelf software?
When a standard solution either doesn't exist, forces your workflow to bend around it, or gets more expensive than a custom build once you add the modules you actually need. For recurring manual work with clear rules, custom software usually pays off quickly; for needs the market already covers tenfold, like accounting or e-mail, almost never.