Revolutionary Software
About Revolutionary Software, the company behind Revolutionary RMM.
We build Revolutionary RMM, a remote monitoring and management platform for managed service providers and internal IT teams. Our aim is simple to say and hard to do: show what the product does, show how you can check it, and say plainly where it stops.
Revolutionary IT is a separate MSP and our first design partner. It uses the product and tells us where it falls short. It does not build or own it.
Inside Revolutionary RMMCases
Open cases grouped by customer, each with an owner, a state and a device. Product capture with fictional customer names.
Who does what
Two companies. Clear roles.
The names are similar, so here is the plain version.
REVOLUTIONARY SOFTWARE
Builds and runs the product
Revolutionary Software designs, builds, hosts and supports Revolutionary RMM. When the product gets something wrong, that is ours to answer for.
REVOLUTIONARY IT
A separate MSP and our first design partner
Revolutionary IT is an independent managed service provider. It runs Revolutionary RMM in its own operations and brings real examples of where the work loses time.
Its feedback informs our priorities. It is a customer and a partner, not the builder.
Built from the work we know. Revolutionary RMM is shaped by the daily work of an MSP: understanding alerts, supporting customers, maintaining endpoints and keeping work moving. Much of that perspective comes from Revolutionary IT and from the design partners who join after it.
What we believe
Three principles we hold ourselves to.
They decide what we build next, and how we describe it on this site.
01
Verified outcomes over feature counts
An action is not an outcome. A script that exits zero is not proof the problem is fixed, so a case records how it closed: the condition cleared, a technician closed it by hand, or someone asserted the fix while the condition was still open.
An update that installed but still needs a restart is marked waiting for reboot instead of being deployed again.
02
Honest limits
Every capability page has a Limits box that says what the feature does not do yet. Our security page lists what we do not claim: no SOC 2 report, no independent penetration test, no contractual service level agreements and no contractual response time. Support is 24/7 and the founding team answers at any hour, which is not the same thing as a staffed operations center.
If one of those rules us out for you, we would rather you learn it here than after you have moved devices.
03
Integrate before rebuild
When a good tool already does the job, connecting to it comes before replacing it. Revolutionary RMM monitors and drives the antivirus that is actually running, Microsoft Defender or a third-party engine. Invoices go to the payment processor you already use.
The next integrations are chosen from the tools design partners actually run.
How we work
Evidence first, then the claim.
Features reach this site in the same order they reach you: built, checked, then described.
01
Describe what ships
Pages describe behavior that is in the product today. Work that is still being built is labeled as in development and lives on the roadmap, not in a feature list.
02
Check it independently
Important work is checked by someone other than the person who did it. Our launch-readiness items are being rechecked this way now, by a reviewer who did not do the work.
03
Publish the roadmap
The roadmap is public, split into now, next and later, and carries the date it was last reviewed. It shows direction, not delivery dates.
04
Listen to operators
Design partners bring real workflows. Their feedback shapes priorities. Not every request becomes a feature, and we do not attach delivery dates to requests.
Not in the product today: honest outcome metrics (time to owner, time to verified resolution, how often fixes hold), a written data governance statement, and recovery objectives proven by timed restore tests.
How to reach us
A person reads every message.
DEMO
See the product
Book a demo call and bring one workflow your team wants to improve. We will show how Revolutionary RMM handles it, including the limits.
QUESTIONS
Ask anything
Pricing, security questionnaires, platform support or fit. Send it through the contact form and we will answer plainly.
SECURITY
Report a vulnerability
Use the contact form and mark the message as a security report. Include the affected component and the steps to reproduce it.
Questions
Good to know.
Revolutionary Software. We design, build, host and support the product.
No. Revolutionary IT is a separate MSP and our first design partner. It uses the product and gives us feedback, and it does not build or own Revolutionary RMM.
Managed service providers who look after many customers, and internal IT teams who look after one organization. The same product serves both.
On the public roadmap. Items there are in development or planned, and none of them is promised for a date.
Next step
Bring us an everyday problem.
The most useful conversation starts with the work your team needs to do. Tell us the task, the tools involved and where it slows down.
