Case study · in production and in daily use
The whole company, one single application.
A metalwork supplier —aluminium profiles, fittings, fasteners— sells every day to hardware stores and workshops. This is how it works now that its whole operation fits inside one application built to measure.
in production · 2 services that never stop · 26 scheduled tasks
The starting point
one application · office, road and warehouse
Three places, three versions of the same figure.
The office, the road and the warehouse looked at different papers. Every handover by hand meant a wait and a possible error.
Office
Orders came in by phone and on paper, and someone typed them in.
The order a rep sends from the phone is already inside. Nobody types it again.
Road
The rep quoted from memory and confirmed on getting back.
Stock and price in real time, at the customer's counter, from the phone.
Warehouse
What was sold on the road was known late and picked the next day.
What was sold on the road turns up already picked for the warehouse. The same figure, without copying it.
What the application takes off your hands
The work nobody does any more.
Three concrete jobs that cost money every week, solved inside the same application. Real screens, in production.
The paperwork
Delivery notes read themselves.
Supplier paperwork came in on paper or PDF and someone typed it in, line by line.
The machine reads it and says how sure it is of the reading. One person confirms with a click; nobody types.
Try it right here
Confirmed. Nobody typed a thing.
The answers
It answers, and cites its source.
The answer was in an invoice or a signed agreement nobody could find in time.
Ask in plain words and it answers with the figure and where it comes from. Every answer shows its source.
What is said out loud
What is spoken gets written down.
An order dictated on the road or on the phone depended on someone's memory.
It is written down, with the time and with what the system understood. Nobody transcribes it.
The difference
a backup restored every week · reconciled every night
Delivered doesn't mean abandoned.
A lot of custom software dies after delivery. This one is watched every day, and the watching leaves a written record.
Every week
A real backup is restored, just to prove it can be.
Every week
Dependencies are checked against the public list of known vulnerabilities.
Every night
Data is reconciled against the source system.
Every morning
Automatic checks leave a record of whether they passed or failed.
- backup restored and verified
- in sync, up to date
- vulnerabilities: checked
- reconciled with the source
- backup restored and verified
- in sync, up to date
- vulnerabilities: checked
- reconciled with the source
- 2
- services that never stop
- 26
- scheduled tasks
verified on the machine
Your company doesn't sell profiles or fittings. That is exactly the point: custom software is built on your operation, not on someone else's.
Tell us about your working day.
20 minutes on your operation, no obligation. The call is taken by the engineering team.
in production · 2 services that never stop · 26 scheduled tasks
verified on the machine