Operations software
Orders, jobs, quotes, stock, production planning. Interfaces designed for people who use them eight hours a day.
Services · 03
Custom software for business processes
When a company bends the way it works around a rigid management system, the cost doesn't appear on the invoice. It appears in the hours spent copying data and in the information nobody has updated.
Two platforms built around one process
We don't start from the code. We start from the step that today lives in a spreadsheet, and from the person who fills it in every day.
- monthsnot weeks: software is built in phases
- 5working days for the proposal after process mapping
- 30days of support after delivery
When bespoke is the right call
Not always. New software makes sense when the process is already stable and the tool is the problem, not when the process is still being defined.
- The spreadsheet stopped being enoughShared data, several people writing into it, versions drifting apart, and nobody knows which one is correct.
- The system needs too many steps outside itselfEvery operation ends in a separate file or a message: the right number exists, just not in one place.
- The vendor's portal doesn't adaptCustomers ask for order status and documents, and the answer is still "I'll email it to you".
- The process is a competitive advantageIf the way you work sets you apart, standardising it onto a generic product means becoming like everyone else.
What we build
Client portals
Private area with documents, job status, payments and requests. It reduces phone calls and makes traceable what today is only spoken.
Dashboards and reports
Numbers that today get rebuilt at the end of the month: margins, lead times, workload, deadlines. Calculated once and always current.
Integrations and APIs
Connections with the management system, accounting, couriers, payments and external services. If a system has no API, we look at alternatives before forcing a compromise.
How we proceed
Internal software is designed by looking at the people who will use it. That is why the first phase doesn't happen in a meeting room: it happens at the workstation.
Mapping
We observe the process as it runs today and collect the edge cases: the ones that break standard systems, and the ones that rarely make it into a specification.
Prototype
The main screens before the code, tried out with the people who will use them. Fixing here costs an hour; fixing later costs a week.
Releases in pieces
The essential features go into use early, the rest follows. Software used from the first week collects feedback no initial analysis predicts.
Maintenance
Updates, backups, monitoring and changes over time, with a direct channel and response times agreed in advance.
Frequently asked questions
How much does custom software cost?
It depends on how many processes are involved and on the integrations. A first usable module typically takes a few weeks of work; the proposal is written after the mapping, never before.
Can we start with one module and widen it later?
Yes, and it is the way we recommend. You start from the process that creates the most friction, put it into use, and measure the time saved. The following features are decided with data in hand.
Does the software stay ours?
The code and the data belong to the client, with access to the repository and the ability to export the data in open formats. There is no lock-in that forces you to stay with us in order to keep working.
Close to this service
Automation and AI
If the problem is solved by connecting the systems you already have, instead of writing new software.
Website design
When you need a public front door to the process, and not only an internal tool.
Industries
What changes when the software has to live alongside a craft workshop or a professional practice.
Describe the step you repeat every day
Often it is enough to describe a single repetitive operation to understand whether what pays off is an automation, a software module, or neither.