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.
ERP
Will you pay for the modules of a full ERP that you never open, or run your own chain from work order to invoice? We build the second: a part leaves stock the moment it is written to the order, and the invoice comes off that same record. Production planning and supply chain sit outside this scope.
ERP is the business software that closes the operations, stock and accounting records of a job on one chain. We keep the scope to those three flows and leave production planning, supply chain and consolidated finance out, because there is no work in our portfolio that would show them. At AlgoCar a work order opens, the part consumed is written to it and leaves stock, and the invoice comes off that same record.
At AlgoCar the chain holds together. A work order opens, the part consumed is written to it and leaves stock at that moment, and the invoice is raised from the same record. Nothing is entered a second time in a warehouse screen, and nobody hunts for the difference between two ledgers at month end. Servicing and repair spend accumulates under the plate and chassis record, so what a vehicle has cost in total is read from its own file and travels with it when the car is sold on.
At Resterm the chain starts on the sales side. A heating requirement goes into the engineering calculation, the product the calculation selects drops into the basket, and the basket attaches to a project and to that project’s customer. A quote line can be traced back to the input it came from, a chain we follow link by link in from product configurator to quote. The software was built on the manufacturer’s own product structure.
Neither system got a toolset of its own. Whatever holds a work order and whatever holds a quote line are built the same way, so whoever maintains one can find their way around the other. AlgoCar is our own product on top of that: we carry its upkeep ourselves, and new features are still going in.
The scope stops here. Production planning, supply chain and consolidated finance are not the work this portfolio describes, and if your search for an ERP turns on them we cannot give you a straight answer. If it turns on operations, stock and accounting, the whole of that scope sits in the two cases on this page.
Where the chain starts, and where it stops:
At AlgoCar a work order opens, the part consumed is written to it, and the invoice comes from that same record. The chain never splits across three programs.
A part leaves stock the moment it is written to the work order. No warehouse screen sits waiting for the same consumption to be keyed in again.
The trading and accounting side runs in the same system as the service record, so the two faces of a job are not reconciled after the fact.
At AlgoCar servicing and repair build up under the plate and chassis record, so what a vehicle has cost in total is read from its own file.
At Resterm you can trace a quote line back to the heating requirement that produced it.
The product the engineering calculation selects drops into the basket, the basket attaches to a project, and the project to its customer. The records stay on one chain.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
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.
A selection and quoting tool for an electric heater manufacturer. The user states a heating requirement instead of a part number; the software runs the engineering calculation, and the heater it picks becomes a line on the quote.
The word automation covers a factory line as readily as a piece of business software. What a business owner is asking about is narrower: one step leaving somebody's hands.
ERP stands for enterprise resource planning. Whether a business needs one, though, shows up somewhere else: in how many separate programs the record of a single job has to pass through today.
Asking the new system to print invoices gets you a PDF template. We cover who ends up retyping invoice numbers, what a work order does when nobody answers, and how to retry without sending twice.
When the person writing the quote is not the person who ran the calculation, the same data is typed twice and two prices appear. We trace a chain where every quote line reads back to its input.
A system that 'talks to the accounting program' is a handover point between two owners, not a module. Which records stay with you, why one way beats two, and where a correction lands.
Most of the time, no. If what has to close in one record is operations, stock and accounting, the scope on this page is the scope you need. AlgoCar carries those three on one chain: the work order opens, the part is written to it, the invoice comes off that record. Production planning, supply chain and HR are not on it, so if those decide your choice, we are not your team.
Because a separate program means keying the same movement twice. You end up looking at one record instead of hunting for the month-end gap between two. AlgoCar takes the part out of stock the moment it is written to the work order, and no warehouse screen waits for a second entry. If your warehouse and your service desk run on two programs today, the first thing we look at is which step triggers the stock movement.
We do not match them; both are written to the same work order. When you close a job, both faces of it close with it, and nothing is left waiting to be carried over to accounting at month end. AlgoCar runs the trading and accounting side in the same system as the service record, so the parts consumed and the invoice raised are read from one work order. If cost and revenue sit in two files for you today, we start by asking which record could carry both.
It does; the chain then starts from the output of the calculation. Your sales team enters the requirement rather than a product code, and the quote line comes out of the calculation. Resterm drops the heater the calculation selects straight into the basket, the basket attaches to a project and that project's customer, and no data is carried by hand between the technical choice and the commercial line. The heater selection case below follows that path from requirement to quote line.