MSP design partners
Built by operators. Shaped by your experience.
Tell us where your team loses time, which alerts deserve attention, and what technicians need before they act. Help shape Revolutionary RMM around the work you do every day.
Start with a conversation. No preparation is required, and you do not need to replace your current RMM to take part in the discussion.
The invitation
Your everyday work should shape the tools you use.
Revolutionary Software builds Revolutionary RMM. Revolutionary IT, a separate MSP, is our first design partner. We are inviting more experienced operators to bring a real workflow and help us improve how alerts are prioritized, how context is presented, how work is assigned, and how responses are recorded.
01 / WHO
You know the work.
MSP owners, founders and technical leads who understand the systems and customers they support. Technicians are welcome in the working sessions that follow.
02 / WHAT
Bring one real task.
An investigation, an update or a support workflow where your current process creates friction.
03 / HOW
Show us what happens.
The concrete steps, the missing information and the result you needed. Specific examples are more useful than a feature wish list.
The operating model we are evaluating together
From the first alert to a resolution you can check.
A case holds the related issue, the work, the owner and the evidence together. This is the model we want partners to pressure-test against their own workflows.
01
Alert
Something needs attention on a device or service.
02
Context
The device, its customer and its recent history, in one place.
03
Case
Related alerts and work gather into one record instead of scattered tickets.
04
Owner
One person is responsible for the next step.
05
Action
A permitted response: a script, a remote session, a patch or a ticket.
06
Verification
A later observation shows whether the intended state was reached.
07
Resolution
The case closes, and the record says how: recovery that was observed, or a close someone recorded by hand.
An action record tells you what ran. A follow-up observation shows whether it worked. We want your help deciding what evidence your team needs to trust the result.
What your experience can shape
Five places where operator judgment matters most.
01
Alert prioritization
Which signals deserve attention first, and which are noise?
02
Device and customer context
What must a technician know before acting?
03
Ticket creation and ownership
How should work reach the right person, and stay with them?
04
Remediation
What makes a response practical and controlled?
05
Documentation
What should the next technician and the customer be able to understand?
Shared expectations
Useful on both sides.
WHAT IS INCLUDED
From us
A walkthrough of the capabilities that matter to your workflow, including their current limits.
Direct conversations with the people building the product, and a place to discuss your feedback and the decisions it informs.
If both sides choose a pilot, a written scope before anything is installed: the environment, the enabled capabilities, the people involved, support, success measures and exit terms.
WHAT YOU CONTRIBUTE
From you
One workflow your team wants to improve, and how it runs today.
Your approximate device mix, and the tools and integrations you need to keep.
Candid, specific feedback from the people doing the work, including what did not help.
Feedback informs our priorities. Not every suggestion becomes a feature, and we do not attach delivery dates to requests.
Agree on the scope. Measure the work. Decide with evidence.
A practical path, one step at a time.
01
Share your perspective
Talk with us about your team's workflows and the friction you want to remove. No preparation is needed for this conversation.
02
Explore the fit
Together we identify which areas would benefit from deeper feedback or evaluation.
03
Agree on the scope
If both sides choose a pilot, we define it separately: the environment, enabled capabilities, people, responsibilities, baseline and success measures.
04
Decide with evidence
A design-partner pilot runs twelve weeks, measured from your own start date rather than from a shared cohort date. At twelve weeks you review what you observed against the baseline, then continue, extend or offboard under the terms you agreed. If you continue with us after the design partner period, you keep 50 percent off for life.
The introductory conversation carries no commitment. A pilot is a separate agreement with its own responsibilities on both sides, and you can end it at any point with no fault and no penalty.
A question to bring
Which routine task takes more steps than it should?
A patch that needs chasing, an alert with no clear owner, a password nobody can find. Tell us the task, the tools involved and where it slows down. That is the most useful place to start.
Before you begin
Clear expectations from the start.
No. We start by discussing fit. Pilot scope, timing, access, data handling, support, pricing and exit arrangements are agreed separately, and only if both sides want to go further.
Yes. If you continue with us after the design partner period, you keep 50 percent off for life. Everything else about a pilot, its scope, timing, access, data handling and support, is agreed with you separately.
Not to talk with us. Any parallel use, installation or data exchange during a pilot is checked against your environment and written into the agreed scope first.
We agree on a baseline and a small set of measures, such as technician steps, alert quality, agent reliability, missing context, and the evidence needed to close the selected work. These are evaluation measures, not promised improvements.
We discuss specific examples and how they affect our priorities. Not every suggestion becomes a committed feature. Any use of your name, logo or results needs your separate permission.
Whoever decides how your team works, usually an owner or technical lead. Technicians who live with the workflow every day are welcome in later working sessions.
Revolutionary IT is a separate MSP and our first design partner. Revolutionary Software builds and runs Revolutionary RMM.
Bring us your toughest everyday workflow.
Tell us what your team manages and where the work gets stuck.
