services / software & mobile

Written for the work itself

If an off-the-shelf program does not fit your workflow there are two options: fit the workflow to the program, or write the program for the work. We do the second.

— what we build

Most businesses start with an off-the-shelf package and manage up to a point. Then something the package did not account for turns up — a second warehouse, a different pricing rule, the field team's own form. From there the work starts moving around the program: spreadsheets, chat groups, notebooks kept by hand.

A system written from scratch removes that detour. Stock, bookkeeping, accounts, field teams, service records — whichever is your business gets built; you do not pay for a module you do not have. Permissions are set per person: who sees what and who can change what is clear from the start.

On mobile, iOS and Android are not written as separate products. They come out of a single codebase; one fix goes to both stores at the same time. The arrangement where two teams work on two schedules and two apps drift apart never gets set up.

If part of the app has to work without internet — stocktaking in a warehouse, a form in the field — data is held on the device and synced when the connection returns. No record is lost on a building site or in a basement.

— scope

Mapping the workflow and the data model
Roles and permissions
Stock, accounts and bookkeeping modules
Field and service record flows
iOS and Android app — a single codebase
Offline working and syncing
Data exchange with your existing system
Reporting and export
App Store and Google Play release process
Six months of support after release

— process

We map the work
We watch one of your days: which record is kept where, how many times each piece of information changes hands. The software comes out of that, not out of a ready-made module list.
We start with a small piece
Not all of it at once — we build the part that eats the most time first. The rest takes shape while the team is already using it.
We hand over
Old data is migrated, the team is trained, and both systems run together for a while in case you need to go back. Then we pull the plug on the old one.

What we build it with

We are not the first user of a tool that has just come out. We choose technologies that have stood for years, that are documented, and that can be maintained after us.

Who owns the code

You do. You have repository access from the start and everything is handed over on delivery. Nothing is held back to keep you tied to us.

— frequently asked

Is buying an off-the-shelf program not cheaper?

Usually in the first year. After that it depends on the monthly fee that grows with your user count and the hours spent working around the parts that do not fit you. In the conversation we put the two side by side and actually calculate it; if an off-the-shelf package is enough, we say that too.

Can it talk to our existing accounting program?

If the program has a connection point open to the outside, yes. If not, we set up regular transfers over files. We settle which one is possible in the first conversation.

How does the app get into the stores?

The publishing accounts are opened in your name and we run the process. Review on the Apple side can take a few days; the schedule accounts for that.

Where is our data kept?

On a server opened in your name. The admin panel is closed to the outside, access is logged, backups are daily. You decide whether the server sits with you or with us.

— other services