The problem we started from
It is February. A furnace breaks down at a house one of your crew worked in eighteen months ago. The record of that visit is out there somewhere: in a text thread, in a camera roll, on a paper invoice in a truck, and in one person’s head. None of it is with you at the front door. So the job starts from nothing. The same questions, the same checks, the same hour of work. You bill for it again, or you take the loss.
The software that was supposed to fix this mostly did not fix it. It was built for offices that have a dispatcher and desks. It was priced for companies that can afford them. And it stops working in the exact places the work happens. So tradespeople kept using paper.
We built the opposite: an app that keeps a record for every address you work at. Every visit, photo, quote, invoice and note is attached to the property, and it opens at the front door whether or not there is a signal.
How we build
Four rules we never break
These are not nice words on a poster. Each one limits how we write the software, every day. And a computer checks each one automatically. We do not just trust a person to notice.
No signal is normal here. It is not a fault
Mechanical rooms, basements, crawlspaces and half the rural service area have no usable signal. So the app saves your work on the phone first, and sends it to the server afterwards. It keeps a list of what still has to go, and that list survives if you close the app, if the phone shuts it down, or if you leave it in a parking garage for a day. Your work is saved before anything is sent anywhere.
The app has its own database on the phone and its own list of what to send, not a short-lived copy of what is on our server.
Money is counted in whole cents, never in fractions
Every amount is stored as a whole number of cents, and every tax rate as a whole number of hundredths of a percent. We round once, on purpose, at the point the rule says to round. We do not round quietly, a fraction at a time, across a hundred small sums.
An automatic test reads the live database and fails if any column named as money is set up to hold anything but whole numbers.
One business can never see another business
Every record is stamped with the business that owns it, and every request to the database is limited to the business that asked. Underneath that, the database keeps the same wall up itself, with its own rule on every table. Both walls have to fail at once before anything leaks.
An automatic test reads the live database and fails by name on any table of business records that is missing its rule.
The history can only be added to, never changed
History lines and payments are never edited and never deleted. To fix a mistake, we add a new line that cancels the old one, so the story of a job still reads clearly years later. That matters when people disagree about what was agreed, and about when it was agreed.
The database blocks it automatically. It is not just a rule we ask people to follow.
Company details
The company you have your agreement with, and where to send mail.
- Company name
- Omni Data Tech Inc.
- Office address
- 3601 Highway 7 East, Suite 1006, Markham, Ontario, L3R 0M3, Canada
- Law that applies
- Ontario, Canada · courts of Toronto
- Product
- ZEUS
- Markets
- Canada
- Contact
- [email protected]
We explain how we protect the data you put in on the security page, and the agreements themselves are in legal.
Build 66753de · v6.9.19 ·
ZEUS