Built for the company that outgrew the spreadsheet
Wealza is for the point where somebody finally asks what we own and who has it, and the honest answer is a spreadsheet nobody trusts.
Why it exists
Asset management software mostly comes in two shapes. There is enterprise software with a six-week rollout, a per-seat licence and a consultant. And there is a spreadsheet.
The companies in between — twenty to a few hundred people, with laptops and vans and tools worth more than anyone has added up — get the spreadsheet by default. It works until the first person leaves, and then it quietly stops being true while everyone carries on trusting it.
Wealza is the thing in between: set up in an afternoon, run from a phone in a corridor or a yard, and priced so that inviting everyone who touches the equipment costs nothing.
What we have decided
These are the choices that shaped the product, and the ones we would defend if you asked why it works the way it does.
The register has to be true, or it is worse than nothing
A spreadsheet that is 70% right is more dangerous than no spreadsheet, because people act on it. Everything here is built so the record changes at the moment the thing does — a scan at the point of handover, not a row typed later from memory.
History that cannot be edited
Check-outs and returns are written to an append-only ledger, and every field change records who made it. When an insurer or a departing employee raises a question months later, the answer is already on the record and nobody can have quietly tidied it.
Charge for assets, not for people
Per-seat pricing punishes you for inviting the people who would keep the data accurate. Members are unlimited on every plan, including the free one. The bill follows the size of the register instead.
Say what is not built
Offline scanning, maintenance schedules and per-department permissions are not finished. They are described that way on the pages that would otherwise imply otherwise, because a feature list that oversells is a support queue later.
Two locks on your data, never one
Every query filters by workspace, and the database independently refuses to return rows from another one. A single forgotten condition in the application is not allowed to be a breach. There is a test suite that tries to break it on every change.
Try it on your own register
Import your spreadsheet and see what it looks like when it is scanned rather than typed. Free for up to 50 assets.