Operations runs on small tools nobody prioritises, so they end up as spreadsheets: on 54 the same tool is a form, a list and a login, the records are written on the server instead of copied between files, and everything is downloadable.
Every company has a dozen of them — the leave request, the supplier list, the equipment log — and each one is a spreadsheet that **one person maintains and everyone depends on**. It works until two people edit it, or until that person is away.
Swipe to compare all columns →
| The spreadsheet | 54 | |
|---|---|---|
| Two people at once | Two copies drifting apart | Written on the server; one record, last write wins |
| Who filled this in | A guess from the column | The record carries who wrote it |
| A required field | Hope they read the note | Checked before the record is written |
| Sending a confirmation | Copy, paste, send | Mail from your own domain when it is submitted |
| Giving it to finance | Email the file around | Download it from the admin |
Written from each product's public documentation. Products change: check theirs before you decide. No prices here for the same reason.
Yes. Require a login and keep the records private.
Yes, files attached to a record.
Yes, from a mailbox on your own domain.
Yes, from the admin.
Yes, by saying it. Existing records keep what they had.
To build it, no. To decide what it should ask, yes — that part is the work.
It runs on your own domain, which is included.
The plan counts builds a day, not tools.
Then it matters that you can download the files and the data, which you can.
Every published version of the tool is kept.