Asset Management software
The asset register and the building disagree, and the register is losing.
Assets move between people, sites and departments, get repaired, get cannibalised for parts, and eventually get thrown out by someone who did not know they were on the books. Then finance depreciates a machine that left the building two years ago, and the audit finds it.
What it replaces
- A fixed asset register in a spreadsheet that only finance touches and only at year end.
- Custody tracked by memory, so nobody can say who has the laptop, the meter or the drill.
- Maintenance history in the technician's notebook, lost when the technician leaves.
- Verification done as an annual scramble that reconciles by writing off whatever cannot be found.
What we build
The parts that make it a system.
Scoped to what you run. A module you do not need is not a discount we withhold — it is work nobody does.
Register, tagging and custody
One record per asset with a QR or barcode tag, current location and custodian, and a transfer flow with acknowledgement so custody is a fact rather than an assumption.
Maintenance and service history
Preventive schedules, breakdown work orders, parts and cost per asset, and a total cost of ownership figure that makes repair-versus-replace an evidenced decision.
Depreciation and financial view
Book value by the method your accountants use, revaluation and impairment, and a register that reconciles to the ledger rather than approximating it.
Audit, verification and disposal
Scan-based physical verification with variance reporting, warranty and AMC expiry alerting, and a disposal process with approval and evidence — including data-wiping sign-off for IT assets.
Where AI actually helps
And where it does not.
Little, honestly. Failure prediction needs instrumented assets and years of history — real on a fleet of machines, absent on a register of office equipment. What does help is extracting purchase and warranty data from invoices at onboarding, which is otherwise weeks of typing. We would rather build accurate custody tracking than a model with nothing to learn from.
Integrations
What it has to talk to.
A system that does not reach the ones you already run creates a second place to type things, which is the problem you started with.
- Accounting or ERP for the fixed asset ledger
- Barcode and QR scanning from a phone, so verification needs no special hardware
- Procurement, so an asset is created at purchase rather than at first audit
- IT asset discovery tools, where the estate is largely computers
The limits
What we do not do here.
Including, on several of these pages, telling you not to buy a build at all. That advice has cost us work. It has also stopped projects that would have failed in month three, which is cheaper for everyone.
- We do not supply asset tags, scanners or RFID hardware. We specify what works and integrate it.
- This is not a CMMS for a heavy manufacturing plant. Condition monitoring, PLC integration and reliability engineering are a different product class, and we will say so rather than stretch this one.
- A register that is wrong on day one stays wrong. The first physical verification is part of the project and it is manual work somebody has to do.
In practice
Where this shows up.
Education and healthcare institutions
Grant-funded and regulated assets have to be locatable and accounted for on demand, which makes verification the core requirement rather than depreciation.
Multi-site services businesses
Equipment moves between sites constantly, so custody and transfer records decide whether the register is worth anything.
How it runs
Fixed scope, fixed price, working software each sprint.
01
Discovery
A call, then a written read of the problem — what it costs today, what would have to be true for software to fix it, and whether we're the right people.
02
Proposal
Fixed scope, timeline and price. No open-ended discovery phase billed by the hour.
03
Build
Agile sprints with something running at the end of each one. You see progress in the product, not in a status deck.
04
Ship & support
Cloud deployment, production monitoring and a maintenance arrangement that starts before launch, not after the first incident.
Related
Systems that usually come up in the same conversation.
Most of these share data with each other. Where two are in scope we would rather build one system than two that sync.
Facility Management
Maintenance requests, planned servicing, vendors and compliance for the buildings and equipment you are responsible for.
Fleet Management
Vehicles, drivers, maintenance and fuel in one record — so cost per kilometre is a number rather than an argument.
Inventory Management
Stock numbers you can act on — because the system knows what is reserved, what is in transit and what was miscounted.
Tell us what your Asset Management system would have to handle.
Pick a time that suits you. Tell us the problem, and we'll tell you honestly whether we're the right people to solve it.