The tier decides what the system does. The band decides how many people work in it, counted in tens. Anyone who only reports a problem is free and unlimited on every plan — charging for those seats just means fewer problems get reported.
A seat is a technician, supervisor or administrator — someone who works in the system. Staff who only report problems through the request portal are not seats and are never counted. Every plan includes your own private database and daily backups. Getting your existing records across is included up to the allotted time for your plan; if your data needs more work than that, we will quote it before starting rather than after.
Most maintenance software is priced for an organization with a CMMS administrator, an IT department and a budget line for both. If you have six technicians, four buildings and nobody whose job this is, those systems cost more than the problem they solve.
There is no mandatory implementation package, no consultant you have to hire before the software will do anything, and no minimum term. You can be taking requests the week you sign up.
The same private database, the same daily backups, the same AI and the same support on the $149 plan as on the one above it. What changes between plans is how much of a maintenance department you run, not how seriously we take you.
This costs less because it is run lean, not because corners were cut in it. There is no sales floor to pay for and no enterprise pricing team deciding what your site is worth. You get told the number.
Being affordable is not the same as being behind. The newest tools reach a small shop first here, because there is nobody who has to approve them — the AI below went in the month it became possible, not the quarter after a committee agreed to it.
Most of what a maintenance department does is in the plans above. Some of it isn't, and the part that isn't is usually the part nobody else will touch. We build it with whatever the current tools make possible, rather than whatever the software happened to support ten years ago.
A compliance round, a key register, a tool crib, an inspection that still travels on a clipboard. If you can describe how it works today, it can be built to work the same way with a record behind it.
The board, the auditor or the district wants a number presented a particular way. We build the report to match the format you are asked for, rather than handing you an export to reshape by hand every quarter.
Records brought across from software nobody supports any more, a spreadsheet nobody trusts cleaned up before it goes in, or a connection to a system you already run so the same thing is not typed twice.
This is quoted against a written scope before it starts, so you know the cost while you are still deciding whether to do it. Tell us what you are trying to fix rather than what you think we build — the answer is sometimes that you do not need us for it.
Not a chatbot bolted to the front page. Six places where it does a job somebody was already doing badly at four in the afternoon. It stays off until you turn it on, and turning it on is one key pasted into settings.
A chat button on the dashboard and on the technician view. It knows your assets, your PM schedules and how the system works, and it will cite a code section when the question calls for one.
The headline, two or three sentences on where operations stand, three things worth doing today and anything about to escalate. Under two hundred words, written from last night's data rather than last month's.
Somebody types what is wrong in their own words. It comes back as a work order with a priority, a trade and a location already filled in, for you to correct rather than compose.
It reads what was actually described and says whether the priority fits. The gas smell filed as Routine and the flickering light filed as Emergency both get caught before they reach a queue.
What has been done to this unit, what keeps coming back, what it has cost. The answer without reading forty work orders to find it.
A technician facing equipment they have not seen before gets a sensible first few checks, in the order a person who knew the machine would do them.
$29/month per site, on any plan — all six, no per-message charge, no counting. Or bring your own API key and pay nothing to us: the cost is then yours, itemised and visible, and the same features run on it. Either way your work orders are never pooled with another customer's to train anything, and switching it off leaves everything else exactly as it was.
Yes. That is usually the first thing we do — your existing work orders, assets and history come across before you go live.
Your account goes read-only. You keep reading your history; you just cannot add to it. We do not lock you out of your own records.
Yes, any time, in a standard format. It is your data.
You move up a band. We would rather tell you that now than have you find it on an invoice — and if you are one or two over at renewal, talk to us.
No. The request portal is open to everyone on your staff on every plan, with no account and no seat.
Tell us how many buildings and technicians you have and we'll tell you straight.
Talk to us →