There are two reporting problems every MSP has. The first is internal: tracking configuration changes and documenting client environments. Liongard handles that. The second is external: communicating what you actually did to the clients who pay your invoices, in language they can understand, every single month. Almost no MSP solves the second one. That gap is what costs you renewals.
Tools like Liongard do their job. They detect configuration drifts, document environment changes, and surface technical inspection data that gives your team genuine visibility into client infrastructure. That is genuinely useful.
But clients don't read Liongard inspection reports. They are not written for a business owner sitting through a renewal conversation. They are written for the technician who needs to know that a firewall rule changed at 2:14 AM on a Wednesday.
So your team has all the data. It lives in your RMM, your PSA, your inspection tool. And the client receives none of it. Because nobody has translated it into a report that a non-technical stakeholder would actually open, read, and remember.
Nothing is the most common outcome. Month after month, the work happens, the documentation exists internally, and the client experiences your service as an invisible black box. At renewal time, they are not remembering twelve months of protection. They are remembering the one incident that bothered them.
These tools are not alternatives to each other. They solve different reporting problems. Here is what each one actually handles.
| Liongard | Roviret | |
|---|---|---|
| Network and config change detection | Yes | No |
| Environment documentation | Yes | No |
| Technical inspection reports | Yes | No |
| Client-facing monthly business reports | No | Yes |
| Executive summary in plain English | No | Yes |
| Automated delivery to clients | No | Yes |
| PSA data (tickets, SLAs, time logged) | No | Yes |
| Report branded to your MSP | No | Yes |
A Liongard inspection report sitting in your documentation platform does not reach the client. Neither does the ticket data in your PSA, the patch summary in your RMM, or the backup logs in your continuity tool. All of that exists. None of it reaches the person making the renewal decision.
A Roviret report in a client's inbox on the 5th of every month does reach them. It is written in plain English. It summarizes what happened, what your team did about it, and what the numbers mean. It arrives whether the client asks or not.
That consistency is what builds perceived value over time. Not better tools. Not more documentation. Just the act of telling clients what you did for them, regularly, in a format they can actually read.
"We had every metric documented internally. But when the renewal came up, the client said they didn't know what we did all year. We had the data. We just never sent it." — MSP owner, paraphrase from a Roviret onboarding call
We sign an NDA before any connection happens. Then we set up read-only API access to your PSA (ConnectWise Manage, Autotask, or Halo) and your RMM (NinjaRMM, Datto RMM, or N-able). We cannot create, modify, or delete anything in your systems. This step takes 3 to 5 days and requires nothing from your team beyond sharing the API credentials.
Your logo, your colors, your client names. We build a report format that looks like it came from your MSP, not a third-party service. We also map which data fields matter most for each client type so every report is relevant, not generic. This is included in the one-time setup fee.
On your schedule each month, the system pulls data from your PSA and RMM, generates a formatted PDF for every client, and queues them for delivery. You can review before they go out, or we send automatically. Either way, nobody on your team touches a spreadsheet or writes a summary. The 3.5 hours per client stays in your pocket.
Tell us your PSA and RMM. We build a fully formatted sample report in 48 hours. No system access needed for the sample.
No. Liongard does something Roviret does not: it detects configuration changes, documents client environments, and produces technical inspection data for your internal team. That is a different job from client-facing monthly reporting. If you are currently using Liongard for internal visibility, Roviret does not replace it. Roviret solves the second reporting problem: taking all that internal activity and communicating it to clients every month in plain English. Many MSPs will use both. They solve different things.
On the PSA side: ConnectWise Manage, Autotask, and Halo PSA. On the RMM side: NinjaRMM, Datto RMM, and N-able. These cover the large majority of US MSPs. If you are on a different stack, reach out. We evaluate new integrations based on demand and will tell you directly whether we can support it.
Each report has four sections. An executive summary in plain English, written for the business owner, not the IT contact. A service desk performance section covering tickets, response times, and SLA adherence with month-over-month context. A security and compliance section covering threats blocked, patches applied, and vulnerabilities resolved. And a backup and continuity section covering backup success rates and any failures with their resolutions. Everything is pulled from your PSA and RMM automatically. No manual input from your team.
BrightGauge and similar platforms give your team a tool to build reports. You configure the dashboards, maintain the data mappings, and manage the platform as your stack changes. Someone on your team still does the work. Roviret is a service that delivers finished reports. The distinction matters because the 70 hours a month your team spends on reporting are not saved by buying better software. They are saved by removing the task from your team entirely. We build the reports. We maintain the integrations. We handle delivery. Your team reviews or approves. That is all.