MSP design partners

Shape an RMM around the work your team actually does.

We are inviting experienced MSP teams to share how their technicians monitor, triage and support client environments. Bring one real workflow and help us test how Revolutionary RMM can make that work clearer and easier to manage.

Start with a conversation; no preparation or platform change is required. If there is a fit, both sides agree on the pilot scope and terms in writing before a pilot begins.

One tap creates your workspace, and your design partner interest is recorded when you confirm your email. No card is needed to start. Then book a 30-minute discovery call.

Book a discovery call   ·  Prefer to talk first? Send a message   ·  See what you can help shape 

The invitation

Your everyday work should shape the tools you use.

Revolutionary RMM is being formed as its own Delaware corporation, separate from Revolutionary IT, the founders' MSP. Revolutionary IT is a related party and 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.

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.

Terms at a glance

The pilot terms, in plain numbers.

Everything below is also in writing before a pilot starts. Design partnering is optional: you can take the 14-day trial or buy RMM 1.0 at the standard price without it. Design partners sign up the same way, with no saved card, and accept the same terms and conditions and the same trial rules as every free-trial customer.

The 12-week pilot: scope and baseline before day 1, a week 4 gate before the second invoice, a week 12 decision held in week 11; invoices on days 1, 29 and 57 at the $1 rate, and the partner price from day 85 unless you cancelThe 12-week pilot: scope and baseline before day 1, a week 4 gate before the second invoice, a week 12 decision held in week 11; invoices on days 1, 29 and 57 at the $1 rate, and the partner price from day 85 unless you cancelThe 12-week pilot: scope and baseline before day 1, a week 4 gate before the second invoice, a week 12 decision held in week 11; invoices on days 1, 29 and 57 at the $1 rate, and the partner price from day 85 unless you cancel

01 / LENGTH

12 weeks from your start date

Measured from your own start date, not a shared cohort date. 12 weeks is 84 days.

02 / PILOT PRICE

$1 per device per month

During the 12 weeks, in three invoices billed in advance every 28 days. No card is needed to start. Each invoice counts the devices in your Pilot Schedule or the devices enrolled on its issue date, whichever is higher. Applicable sales tax is additional.

03 / AFTER THE PILOT

50 percent off for life

From day 85, unless you cancel, the first 100 paying design partners keep 50 percent off the standard rate for life, for as long as the subscription stays paid. On RMM 1.0 that is $2.50 per device instead of $5. A place counts once a partner has a signed participation agreement and a successfully paid first invoice, the $1 pilot invoice included; trials and unpaid workspaces never hold a place.

04 / EQUITY

0.1 percent each, nine in total

The first nine paying design partners to complete the 12-week pilot and pay their first invoice on the post-pilot plan each receive 0.1 percent equity, under a separate written equity agreement with the Delaware corporation being formed for Revolutionary RMM. A pilot invoice, an inquiry or a participation agreement does not earn it. Only a paying customer, at a minimum of $1 per device per month, earns or holds an equity place; an unpaid trial never does. Revolutionary IT, the founders' MSP, holds no discount or equity place.

05 / SUPPORT

A weekly 30-minute session

For design-partner pilots: 8AM - 6PM CST, Monday to Friday. Every request, including a critical alert, is acknowledged within four support hours and answered within one business day. We do not promise a resolution time.

06 / EXIT AND YOUR DATA

No fault, no penalty

Leave at any point. Access ends immediately, you get an export within five business days, active data is deleted within 30 days and backups within 90. Publicity of your name or results needs your separate written approval.

How a place is counted. A discount place is claimed when you have a signed participation agreement and a successfully paid first invoice, the $1 pilot invoice included; trials, unpaid workspaces and inquiries never hold one, and a place is kept only while the subscription stays paid. The nine equity places are counted separately, by the date of the first invoice paid after the pilot. We do not publish a count of places taken or left.

Where the product is today

Honest about what is live and what is planned.

A pilot covers what is shipped and listed in your written scope, with each capability's current limit stated first. We do not promise features, dates or results.

The patching screen from the founders' own MSP workspace: updates waiting for a reboot are not redeployed, and an update that failed three times stops retrying and says so. Client names are fictionalThe patching screen from the founders' own MSP workspace: updates waiting for a reboot are not redeployed, and an update that failed three times stops retrying and says so. Client names are fictionalThe patching screen from the founders' own MSP workspace: updates waiting for a reboot are not redeployed, and an update that failed three times stops retrying and says so. Client names are fictional

LIVE TODAY

RMM 1.0 at $5 per device per month

The daily device loop: enrollment, inventory, monitoring, remote sessions, scripts, patching and tickets. Its release acceptance as a whole is not yet established, which is why every pilot lists limits up front. See the roadmap →

PLANNED

SuperRMM 1.0 and 2.0

SuperRMM 1.0 is a planned $10 target and is not for sale yet. SuperRMM 2.0 pricing is to be announced. Native PSA, backup and endpoint-security engines are planned, not shipped. See pricing →

HOW WE MEASURE

Behavior, not logins

We compare your baseline with what happened: weekly active technicians, devices reporting, missed or noisy alerts, time to close, and our own support hours. A continuation shows willingness to pay, not a technical 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.

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, and you can end it at any point with no fault and no penalty. The numbers, including the $1 per device pilot price, the 50 percent lifetime discount for the first 100 paying design partners, the 0.1 percent equity for the first nine paying partners who complete the pilot and pay after it, and how a place is counted, are in the terms at a glance above. Design partnering is optional and is never required to use or buy the product.

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.

Please do not include client names, credentials, security details or confidential data in the form or the call booking. A general description of your device mix and one workflow is enough.

Send it through the contact form →

Already a design partner? Share your experience →

Is this a fit?

Five things that make a good design partner.

01

You can authorize the install

Someone on your team can approve installing the agent on a contained, noncritical client or site.

02

One workflow to improve

A real task where your current process creates friction, and the steps and tools around it.

03

A named technician

An owner and a technician who can join a weekly 30-minute session and use the product on real work.

04

A baseline you can capture

Time, steps, alert volume or missed alerts on your current tool, measured the same way at the end.

05

You will sign and pay the $1 invoice

A place is for paying customers, so the first invoice and a signed participation agreement come before anything else.

NOT A FIT YET IF

You need a planned feature on day one

If native PSA, a native backup or endpoint-security engine, or a staffed SOC is the deciding factor, tell us. We will say plainly whether to wait.

Inside the discovery deck

#deck

The 12 slides we present.

Our operating model, real product screens, the twelve-week pilot and its terms, with text for every slide.

Revolutionary RMM design partner discovery deck

The design partner discovery deck: the operating model, real product screens, the 12-week pilot and its terms. Every slide has a text transcript.

Download the PDF

Slide text
  1. Shape an RMM around the work your team actually does.

    DESIGN PARTNER DISCOVERY · 12-WEEK PILOT
    Shape an RMM around
    the work your team
    actually does.
    Built by Operators. For Operators.
    One real workflow, measured against your own baseline, with
    the scope and terms in writing before anything is installed.
    RevolutionaryRMM.com David Pitts and Thomas Coppedge, co-founders
    RECEIPT Real product screen, Revolutionary IT workspace (the founders' MSP), captured Oct 28 2026 and sanitized: client names are fictional.

  2. We built it for our own MSP, and we run it there every day.

    WHO WE ARE
    We built it for our own MSP, and we run it
    there every day.
    David Pitts and Thomas Coppedge run Revolutionary IT,
    a managed service provider in Dallas. We built
    Revolutionary RMM because we wanted a tool that ends
    every alert in a fix we can check.
    Revolutionary IT is a related party and our first design partner. It runs its own
    client devices on the product and tells us where it falls short. It holds no
    discount or equity place. Revolutionary RMM is being formed as its own
    Delaware corporation, separate from Revolutionary IT.
    57
    of 70 devices at Revolutionary IT
    enrolled in Revolutionary RMM today,
    growing (read-only count, Nov 2 2026)
    You talk to the builders
    Two founders, no sales team in between.
    No invented proof
    Our own use is related-party use, not
    customer evidence. We will not show you
    logos or quotes we do not have.
    What we ask of you is what we did ourselves: run one real workflow on it, and keep score.
    WHY US
    RECEIPT Owner decision 22: 70 devices under management at Revolutionary IT (owner-stated); 57 enrolled, read-only production count Nov 2 2026
    (related-party use). Relationship and corporation: owner decisions of 31 October 2026.

  3. Too many tabs, and the outage you hear about from the customer.

    THE WORK
    Too many tabs, and the outage you hear
    about from the customer.
    Tool sprawl
    Monitoring, PSA, remote
    access, documentation
    and security in separate
    tabs, each with its own
    version of the truth.
    PSA gaps
    Alerts that never
    become tickets, tickets
    that never reach the
    device, and time that
    never reaches the
    invoice.
    Patch chasing
    The same failed update
    every month, and a
    deploy called done
    before the device has
    rebooted.
    Remote access
    A session that drops on
    restart, or needs a
    second tool, while the
    user is waiting.
    Billing by hand
    Device counts
    reconciled per client at
    month end, from a
    different screen than the
    work.
    One question starts every call: which routine task takes more steps than it should?
    THE WORK
    RECEIPT The friction the founders lived running Revolutionary IT. PSA weight: an MSP owner's direct feedback, Sept 10 2026. No time-saving figure is
    claimed.

  4. Every alert should end in a fix you can check.

    THE OPERATING MODEL
    Every alert should end in a fix you can check.
    Alert Context Case Owner Action Verify Resolve
    revolutionary-it.revolutionaryrmm.com / alerts
    One alert in our own MSP: what changed on the device, the linked ticket, the owner and Resolve on
    one screen. Resolve is a deliberate step, not a script exit code.
    WHAT RAN
    An action record tells you what
    ran.
    WHAT CHANGED
    A later observation shows
    whether it worked.
    In the pilot, a fix counts only when it is still fixed
    seven days later.
    THE WORK
    RECEIPT Model as published on /partners/ (read Oct 31 2026). Seven-day rule: the RMM 1.0 outcome definition (owner decisions, 31 October 2026).
    Real product screen, Revolutionary IT workspace (the founders' MSP), captured Oct 28 2026 and sanitized: client names are fictional.

  5. Patching that tells you the truth.

    THE PRODUCT TODAY
    Patching that tells you the truth.
    IN RMM 1.0 TODAY
    revolutionary-it.revolutionaryrmm.com / patching
    1
    2
    3
    1 You choose the scope
    Deploy one patch per device, per client or to
    everyone, or exclude it.
    2 Waiting is not failing
    Updates installed and waiting for a reboot are not
    redeployed.
    3 It stops and says so
    After three failed installs an update stops retrying and
    is listed.
    THE PRODUCT
    RECEIPT Real product screen, Revolutionary IT workspace (the founders' MSP), captured Oct 28 2026 and sanitized: client names are fictional. Full
    RMM 1.0 release acceptance is not yet established; a pilot scope lists each capability's current limit.

  6. Tickets and remote sessions beside the device.

    THE PRODUCT TODAY
    Tickets and remote sessions beside the device.
    Tickets from alerts
    revolutionary-it.revolutionaryrmm.com / tickets
    A ticket raised from an alert carries the device name in its subject, so nobody hunts
    for it.
    Remote session
    remote session
    The real Remote Access viewer; the remote desktop is replaced with a placeholder
    for privacy. Sessions stay open through sign-out and restart.
    IN RMM 1.0 The service desk is the product's own. It is not a native PSA; that gap is on the next slide.
    THE PRODUCT
    RECEIPT Real product screen, Revolutionary IT workspace (the founders' MSP), captured Oct 28 2026 and sanitized: client names are fictional. Remote
    session behavior: /roadmap/ Shipped list, Oct 2026 (agent 0.4.79, Remote Access app 0.6.0).

  7. What a pilot covers today, and what it does not yet.

    HONEST SCOPE
    What a pilot covers today, and what it does not yet.
    IN A PILOT
    RMM 1.0
    $5 PER DEVICE PER MONTH
    Enrollment and inventory
    Monitoring, alerts and cases
    Patching
    Remote support
    Approved scripts
    Tickets and customer lifecycle
    PLANNED
    SuperRMM 1.0
    PLANNED $10 TARGET, NOT FOR SALE
    Discovery and topology
    Scoped APIs and events
    Human-reviewed AI triage
    One backup-health and one EDR
    connector
    Outcome dashboards
    PLANNED
    SuperRMM 2.0
    PRICING TO BE ANNOUNCED
    Native PSA
    Native backup and recovery
    Native UEM and EDR
    Enterprise scale and trust
    If PSA decides it for you, say so on the first call. We do not connect to your existing PSA today, and a native PSA is planned without a date.
    Better you hear it now than in week six.
    THE PRODUCT
    RECEIPT Scope and status as published on /roadmap/ and /pricing/ (read Oct 31 2026): RMM 1.0 is offered at $5 while its full release acceptance is not
    yet established; SuperRMM items are planned. Prices: owner decisions, 31 October 2026.

  8. Twelve weeks, one contained scope, two decisions.

    THE PILOT
    Twelve weeks, one contained scope, two decisions.
    1 2 3 5 6 7 8 9 10 12
    WEEKS 1 TO 4
    Install, first patch cycle
    Noncritical devices first. Your current tool stays on.
    WEEKS 5 TO 8
    Real work in the product
    Tickets, remote sessions and the workflow you
    chose.
    WEEKS 9 TO 12
    Repeat and compare
    A second patch cycle; the workflow measured as in
    week 0.
    BEFORE DAY 1
    Scope and baseline
    Written down before anything is installed.
    4
    WEEK 4 GATE
    Go, fix or stop
    Decided before the second invoice.
    11
    WEEK 11
    Your decision
    Continue, extend or offboard.
    12
    INVOICES, BILLED IN ADVANCE
    Day 1
    $1 rate, 28 days
    Day 29
    $1 rate, 28 days
    Day 57
    $1 rate, 28 days
    Day 85
    Partner price, unless you cancel
    THE PILOT
    RECEIPT Pilot length, exit and week-12 choices: /partners/. Billing (owner decisions, 31 October 2026): three 28-day invoices in advance at the $1 rate,
    then the partner price on day 85 unless you cancel; no card at signup. The week 4 gate and week 11 session are the program design.

  9. Success is counted in numbers you already track.

    HOW WE MEASURE
    Success is counted in numbers you already track.
    Hours per week
    spent on the one workflow you chose
    Days to patch
    from release to installed, on the scoped devices
    Alerts and tickets
    per 100 devices per week, and how many were
    noise
    Fixes that held
    share still fixed seven days later
    Devices reporting
    share checking in on schedule
    Our time you needed
    founder hours per week, from our own log
    BASELINE Week 0, your method → TARGET Week 0, in your words → WEEK 12 Same method, compared
    We measure; we do not promise a result. A missing number is recorded as unknown, never as zero.
    THE PILOT
    RECEIPT Measures follow the pilot plan and the /partners/ FAQ (evaluation measures, not promised improvements). Seven-day rule: RMM 1.0 outcome
    definition. No pilot result exists yet to cite.

  10. The terms, in four numbers.

    THE TERMS
    The terms, in four numbers.
    $1
    per device per month
    During the pilot. Three invoices,
    billed in advance every 28 days.
    84
    days, from your own start
    Twelve weeks. No shared cohort
    date. Leave at any point, no fault,
    no penalty.
    50%
    off, for life
    From day 85, for the first 100
    paying partners: RMM 1.0 at $2.50
    instead of $5.
    85
    the day the partner price
    starts
    Unless you cancel before then. We
    go through it with you in the week
    11 decision session.
    OPTIONAL
    You never need to join to buy RMM 1.0. No card is needed to start a pilot.
    PLACES AND EQUITY
    A discount place needs a signed agreement and a paid first invoice. The first
    nine partners to finish the pilot and pay their first invoice after it also receive
    0.1 percent equity each, by separate agreement.
    THE TERMS
    RECEIPT Program terms (owner decisions, 31 October 2026; /partners/ and /pricing/). Equity: 0.9% in total by separate written agreement with the
    Delaware corporation once it exists; separate from the investor round. Applicable sales tax is added.

  11. Both sides put something real in.

    BOTH SIDES
    Both sides put something real in.
    From you
    One workflow you want to improve, and how it runs today
    A contained, noncritical client or site, and authority to install there
    A named owner and a working technician
    A baseline in week 0, and candid feedback, including what did
    not help
    From us
    A written scope before anything is installed
    One 30-minute working session every week, with both founders
    Each capability's current limit, stated up front
    A yes, no or not now on every request, never a promised date
    SUPPORT
    8AM - 6PM CST, weekdays. Every request, including
    a critical alert, is acknowledged within four support
    hours and answered within one business day.
    YOUR NAME
    No use of your name, logo, quote or results without
    your separate written approval for each one.
    IF YOU LEAVE
    Access off at once. Export in 5 business days. Data
    deleted in 30 days, backups in 90.
    THE TERMS
    RECEIPT Support: program support terms (business hours; no resolution-time guarantee). Publicity and offboarding: design partner terms (Oct 21
    2026).

  12. Start with one workflow.

    NEXT STEP
    Start with one workflow.
    1
    30-minute call
    No preparation, nothing confidential.
    2
    Written scope
    Devices, people, baseline, measures.
    3
    Sign
    Participation agreement and pilot
    schedule.
    4
    Day 1
    Install, baseline check, first session.
    RevolutionaryRMM.com/partners
    Book: revolutionaryrmm.com/contact/#book-call
    David Pitts · Thomas Coppedge
    info@revolutionaryrmm.com · 877-373-7887
    11816 Inwood Rd #194, Dallas, TX 75244
    THE TERMS
    RECEIPT Agreements are with Revolutionary IT, LLC (business name Revolutionary Software) until the Delaware C corporation being formed for
    Revolutionary RMM is filed. Contact details as published on /contact/.

Program files

Read the terms before you book.

ONE-PAGER

The program on one page

The terms, what a pilot covers today and what is planned. Download the one-pager (PDF) →

PILOT PLAN

How the 12 weeks run

Week by week, the two decisions, and the numbers we measure. Download the pilot plan (PDF) →

AGREEMENT SUMMARY

What you sign and pay, and when

The participation agreement in plain words, with the billing schedule. Download the summary (PDF) →

FAQ

Straight answers

Places, equity, billing, support, data and what the product does today. Download the FAQ (PDF) →

THE FIRST CALL

30 minutes, no commitment

Book a time with the two founders, David Pitts and Thomas Coppedge. No confidential information is needed. Pick a time →

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. Design partners pay $1 per device per month during those twelve weeks, in three invoices billed in advance every 28 days, with no card needed to start. From day 85, unless they cancel, the first 100 paying design partners keep 50 percent off the standard rate for life. A discount place counts once a partner has a signed participation agreement and a successfully paid first invoice, the $1 pilot invoice included; trials and unpaid workspaces never hold a place, and a place is kept only while the subscription stays paid. The first nine paying design partners to complete the pilot and pay their first invoice on the post-pilot plan also receive 0.1 percent equity each, nine places in total, under a separate written equity agreement with the Delaware corporation being formed for Revolutionary RMM. An inquiry does not issue equity or reserve a place, and only a paying customer, at a minimum of $1 per device per month, can earn or hold an equity place. Revolutionary IT, our first design partner, holds no discount or equity place. Design partnering is optional and is never required to use or buy the product. Pilot scope, access, data handling and support are 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 the founders' MSP, a related party and our first design partner. Revolutionary RMM is being formed as its own Delaware C corporation, separate from Revolutionary IT; until then the product contract is with Revolutionary IT, LLC under the business name Revolutionary Software.

Bring us your toughest everyday workflow.

Tell us what your team manages and where the work gets stuck.