Client rollouts
Every one of these projects started with a single sentence about what was not working - orders retyped in the evening, stock counted off a piece of paper, a service report taking a week to reach the office.
Below, we describe exactly what we built: a mobile app for people in the field, a browser panel for the office, and a connection to the ERP or CRM the company already had. Along with the decisions we made along the way, and the things we had to fix after launch.
Laser engraving
Orders, quoting and inventory in one panel instead of email threads. Stock is calculated from movements, and the dashboard shows which quotes turn into orders.
Electrical installations
Work orders are filled in on a phone right after the job, approved in an office panel, and exported to CSV. The paper form is no longer in use.
Car rental
The whole rental fleet lives in one Mac app: service intervals tracked in days and kilometres at once. The app works out car status, not a person.
In some of the projects on this list, the client saw a working version of the system before ordering anything and before paying anything at all.
Not screenshots, not slides - a panel you could open in a browser, click around in yourself, and check whether it actually looked right.
We do this on smaller projects, where building a demo is a cost we can take on ourselves. On a large rollout it would be too much work to do blind - there we start with a free workshop, a written-down scope, and a screen map instead.
Trust has to run both ways, and at the start it is us who has more to prove. When the scale of the project allows it, we would rather go first and show something working than try to convince anyone with promises.
They all follow the same path: where we started, what we built, and how the rollout went. The numbers at the end always say where they come from and what they are measured against - without that, a percentage on a page means nothing.
We also write about what did not work the first time and what we fixed after launch. That usually says more about working with us than a list of features does.
A system for a service company and one for a wholesaler are built from the same building blocks, just arranged differently. If you recognise any of these problems in your own business, a good starting point is typical use cases and the step-by-step process.
The first conversation is free, and ends with a joint decision on whether to start at all.