The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
An HVAC or appliance service company tracks three things in three places: customers in an office spreadsheet, jobs in a technician’s notebook, and the gap between them over the phone. The field side carries the harder problem. A boiler room or a lift shaft has no coverage, and an app that waits for a connection is useless in exactly the moment it is needed.
We built AlgoKlima as our own product to close both gaps at once. The phone in the technician’s hand holds its own copy of the job, and when signal comes back the two sides merge into one record. The product is live and we keep developing it.
We go through how the work runs today and what you expect from the software; the scope comes out of that.
We decide what the system is made of and where its information is kept.
We draw the screens and the flow before any code, and start building once you have approved them.
We write and hand over the software so another team could carry it on.
A technician opens and closes a job with no connection at all; the record lands in the phone's own queue and the app carries on.
When the connection returns, the queue drains in the order jobs were created, and two edits to one record pass through conflict resolution.
Warranty, maintenance and fault records sit under the device, so three units at one address stay separate and history follows a device that changes hands.
The office panel runs in a browser and the field app on a phone, and both read the same customer and device record. Which technician a job went to sits on that record too.
| Challenge | Result |
|---|---|
| A technician works in a boiler room or a lift shaft, where coverage ends | Technicians log their work where there is no coverage, with no waiting on the app |
| An app that waits for a connection stops the job it was meant to record | Queued records reach the office in the order they were created once signal returns |
| Three air conditioners at one address blur into a single customer file | Warranty and maintenance history travels with the device, not the address |
| The office panel and the field app can edit the same record minutes apart | Office and field work from one customer and device record, not two ledgers |
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
Our own product, still in development and not yet live. How long an appointment runs, what it is booked against and how bookings stack all differ by trade, so we are keeping those rules configurable inside the product instead of fixing them in code.
A single-page QR menu. The menu splits into sections and every section carries its own address, so the code on a table and the code in the window open the page at different points. Built with Vue 3, moving between sections costs no new page request. No ordering, payment or stock layer.
AlgoKlima is live. Write to us to ask what it covers or whether it fits your work.
