Software & mobile

Written for the work itself

If off-the-shelf software doesn't fit your workflow, there are two options: bend 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 it does the job up to a point. Then something comes up that the package never accounted for — a second warehouse, a different pricing rule, the field team's own form. From then on, work gets done by going around the program: Excel files, WhatsApp groups, notebooks kept by hand.

A system written from scratch removes that detour. You don't pick from a list of ready-made modules: it can be stock or service records, or a workflow that exists only in your business — whatever your work is, that's what gets built; you don't pay for modules you don't use. Permissions are set per person: who sees what and who can change what is clear from the start.

On mobile, iOS and Android aren't written as separate products. They come from a single codebase; a fix reaches both stores at the same time. The setup where two teams work to two schedules and the two apps drift apart over time never takes shape.

If part of the app needs to work offline — counting stock in the warehouse, a form in the field — the data is kept on the device and synced when the connection returns. No record is lost on a construction site or in a basement.

Process

01
We map the work
We watch a day of yours: which record is kept where, how many times each piece of information changes hands. The software comes from there, not from a ready-made list of modules.
02
We start small
Not everything at once: we build the part that eats up the most time first. While the team uses it, the rest takes shape around it.
03
We hand over
Old data is migrated, the team is trained, and both systems run side by side for a while in case we need to roll back. Then we pull the plug on the old one.

What we build with

We're never the first users of a newly released tool. We choose technologies that have stood for years, are well documented and can be maintained by others after us.

Accounts in your name

Server, domain and app store accounts are opened in your business's name and handed over to you free of charge when you leave maintenance. Transfer of the source code is set out in the contract.

Frequently asked questions

How much does a mobile app cost?

The price depends on how many screens the app has, features such as membership and payments, and whether it connects to an admin panel or your existing system. Because the iOS and Android versions come from a single codebase, you don't pay for two separate apps. In the first meeting we clarify the need and give you a firm quote.

Isn't off-the-shelf stock or bookkeeping software enough?

For some businesses it is. Off-the-shelf software is usually cheaper in the first year; after that, the cost depends on monthly fees that grow with the number of users and the hours spent working around the parts that don't fit you. In the meeting we put the two side by side and do the math; if off-the-shelf software is enough, we say so plainly.

Can you connect to accounting software such as Logo or Luca?

We can only tell you after running the necessary checks. We look at whether your software shares its data and which information can be transferred, then show you what can be connected and how the connection will work.

Is publishing an app on the App Store and Google Play paid?

Yes. Apple and Google charge fees for the developer accounts needed to publish apps; these costs belong to the stores. The accounts are opened in your name, and we run the upload process. Because Apple's review can take a few days, we plan the schedule around it.