Starter
To get started. Unlimited licences, help centre with guides and training recordings, client portal, requests by email or form, online support and AI assistant.
Plans
Most maintenance software charges per licence, so growing gets expensive and people end up working under someone else's account. In GMAO CLOUD, licences are unlimited on all three plans.
In a CMMS, charging per user punishes the very thing that makes the system work. If every new technician costs more, the temptation is to share accounts; and as soon as three people sign in with the same user, the history stops being proof and per-technician reports stop meaning anything. That is why GMAO CLOUD's price does not depend on how many people use it: add your whole team, your clients and your subcontractors without doing the math before every sign-up.
The difference is not in the product features, but in the support and resources.
To get started. Unlimited licences, help centre with guides and training recordings, client portal, requests by email or form, online support and AI assistant.
Everything in Starter plus a recurring executive report on the service and the client portal, and on-demand follow-up meetings. For higher-volume operations.
Everything in Advanced plus priority support, a dedicated account manager, direct phone support and recurring meetings. For industrial and multi-service groups.
No product features are reserved for the most expensive plan.
No additional per-user cost, on any plan. Technicians, managers, clients and subcontractors.
The system with your identity, which matters when your clients log into their portal.
Public API and email integration included. ERP and CRM integrations are quoted separately depending on the case.
Access for your clients to open requests and follow their orders, from the first plan onward.
Your installation's data is hosted in a European region on all three plans.
Backups and product updates included, with no maintenance window to negotiate.
So you can get an idea before talking to us.
The main variable. It does not change what the product does, it changes how much we support you: reporting, meetings, priority and a dedicated account manager.
Each plan carries tiered processing and storage resources. A plant with a hundred thousand assets does not consume the same as a maintainer with five clients.
Connecting to your ERP or your CRM is quoted separately, because the actual work depends on what data travels and on the state of the other system.
Migrating an existing inventory, setting up preventive plans and training the team is not the same as starting from zero. It is assessed against your case.
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
Because a figure on a website is only useful if you can compare it to something equivalent, and in maintenance it almost never is: the same number can mean per user, per asset or per site, with or without implementation, with or without data migration. We'd rather look at your case and give you a price that holds up, and that you can genuinely compare with whatever else you are offered. What is clear from the start, and why we publish it, is that you will not pay per person using the system.
The monthly fee is the first thing people look at and almost never what makes the difference three years down the line. There are four things worth asking every time that rarely show up on the first page of a proposal. The first is the user model: if you pay per person, the cost grows exactly when the system starts working, because success means more people joining in. The second is what happens with product updates and whether they are billed separately. The third is the cost of setup and integrations, which usually outweighs the licence cost in the first year. And the fourth, the one most often forgotten: what happens to your data if you ever leave. A multi-year maintenance history is an asset with its own value, and a system you can't leave with your data in hand is a risk, however well it works while it lasts.
It helps to understand what the price depends on so you don't pay for what you don't need or fall short where it matters. What normally moves the needle is functional scope — which modules come into play —, the size of the operation and the integration work with what you already have. What shouldn't move it is how many people use it: if adding a site manager or a client so they can open their own requests carries a marginal cost, the system ends up used by fewer people than it should, and with that you lose exactly the benefit you paid for. That is why the useful conversation doesn't start with the fee but with what you want to solve and who is going to touch the system, which is what determines the other two.
Because the price depends on scope and publishing a bare figure misleads in both directions: to someone who needs little it looks expensive, and to someone who needs ERP integration it looks like everything is already included. We'd rather look at what you want to solve and give you a figure that holds up, which is also a twenty-minute conversation rather than a process.
It's one of the questions worth asking any vendor before signing, along with what happens to your data when you leave. We discuss it openly in the proposal: a client who stays because leaving is hard is not a satisfied client, and in the medium term it's not good business for us either.
It depends on the support plan, the size of your operation and whether there is integration or data migration involved. What doesn't depend on the price is how many people use it: licences are unlimited on all three plans. For a concrete number, the fastest route is a short demo on your case.
No. All plans include unlimited licences with no additional per-user cost, including technicians, managers, clients and subcontractors.
What changes between plans is the support — reporting, meetings, support priority, dedicated account manager — and the assigned resources, not the product's features.
In a European region, on all three plans, with backups and product updates included.
The public API and email integration are included. Connecting to a specific ERP or CRM is quoted separately, because the effort depends on what data needs to travel and on the state of the other system.
In a short demo we see what you actually need, and from that comes a quote that holds up.
Accessibility
Saved in this browser. Light or dark theme is set from the footer.