Internal Business Apps

You get an app for the people doing the work, and the admin panel the office runs it from. Both sit on top of the system your company already uses, so nobody has to abandon the software the business runs on to get something better in the field.

Most business software was built for a desk. The work happens somewhere else: in a van, on a loading bay, in a customer’s hallway with a phone in one hand. That gap is usually filled with paper, phone calls and someone retyping it all in the evening. This is the work that closes it.

The app the staff carry

Built for one hand, in bad light, in a hurry. A driver, a warehouse worker or a service technician opens it and sees the next job, not a dashboard. They confirm what happened, add what the office needs to know, and move on.

That means the things a phone can do and a paper docket cannot: a photo of where the package was actually left, a note about the gate code for the next delivery, a barcode scan instead of typing a reference, a signature, a location and a timestamp attached to all of it. It also means working offline, because signal is not a promise you can make to someone in a basement or on a rural round.

The admin panel the office runs it from

The other half, and the half that usually decides whether the whole thing sticks. The office sees the same data as it happens: what is done, what is late, what came back with a problem, and the photo or note attached to it.

It is built around the question the office actually gets asked, which is where something is and why it has not arrived. One screen, one answer, instead of three systems and a call to the driver. We design it for the person who uses it eight hours a day, so the common actions are fast and the rare ones are still possible.

It fits the system you already run

Your existing software stays the source of truth. The app reads from it and writes back to it through whatever it exposes, and the data it cannot hold lives in a store beside it, linked by the reference number you already use.

We have built exactly this shape. Apartmanom pairs a host admin dashboard with a booking widget and issues real Hungarian invoices through the Billingo and Számlázz.hu APIs, live in a working business since June 2026. A medical education app we rebuilt had to run against the client’s own proprietary backend rather than a stock backend-as-a-service. The detail of that layer, including what to do when your system has no API, is on the backend development and integration page.

How we work

We start by watching the job as it is done today, because the paper form and the workaround in someone’s notebook are the real specification. Then we agree the full scope and a fixed price up front.

With an integration the discovery comes first: we look at what your system can actually expose before anyone quotes a number, because a price named before that is a guess. We deliver in reviewable stages, put it in front of the people who will use it early, and hand over clean, documented work you fully own.

What you get:

• A field app built for one hand, bad light and no signal
• Photo, note, barcode, signature, location and timestamp captured where the work happens
• An admin panel that answers the question the office actually gets asked
• A clean fit with the system you already run, rather than a replacement for it
• Fixed scope and fixed price, and a direct line to your builder