MSP reporting software built for your clients.

Deepwell is client reporting that sits above the tools your MSP already runs. Build a report once. It pulls from every tool you connect and runs for each client with that client’s own data, under your brand.

Your tools each report on their own slice, in their own format, for a technician. MSP reporting software turns what they already know into one report a client can read. Deepwell is that layer. It is not a PSA or an RMM and replaces neither. It connects to the systems you have and delivers the finished report under your brand.

Rebuild my report

Which kind of reporting are you looking for?

The term gets used for very different things. This is where Deepwell sits.

Built into your PSA or RMM

Native reports

Each tool reports on its own data, in its own shape. Made by the tool, about the tool.

BI and dashboards

Internal dashboards

Gauges and KPIs across your tools. Made for running the MSP.

Deepwell

Client-facing reporting

One report across every connected system, run for each client and delivered under your brand. Made for the client.

What should an MSP client report include?

What you did for the client, what changed, and what needs a decision. A Deepwell report puts that on one page, in plain language, from every system you connect, with a note from a person at the end.

A delivered monthly service report, with the middle charts cut away: a plain-language summary, requests opened and resolved by week with an annotation marking a new site onboarding, tiles for time to resolve, SLA, devices covered and backup success, then automated fixes, threats open, a for-your-attention note, and a signed note from the account manager
  1. Your brand. The client sees your name, on your domain.
  2. A summary in plain language. Drafted from the figures and held for your review when you want the last word.
  3. Annotations. Mark what happened on a chart, so a busy week reads as a busy week and not a bad one.
  4. Speed the client can feel. Time to resolve and SLA, with the previous period beside them. Read from the PSA every month, so the trend is there without anyone pulling it.
  5. Coverage, not counts. Devices protected and backups checked, from the security and backup tools onto the same page as the requests. A gap shows while it is still small.
  6. Work they never saw. Automated fixes, counted apart from the requests the client raised. The quiet work has no ticket, so nothing else reports it.
  7. A note signed by a person. What needs their decision, from your account manager.

In the docs Walk through the example cross-system reportHow reports are built

Three reports, one set of connections.

Not every client needs the same report. Deepwell builds all three from the same connected tools, each under your brand.

A Monthly Service Report in one MSP’s brand: a blue starburst masthead, a plain-language summary, and requests opened and resolved by week
Monthly Service Report The narrative kind. The figures, what changed, and a note signed by a person. For every client, every month.
A Security & Backup Review in another MSP’s brand: a black and orange masthead, a summary, threats by classification, and tiles for threats detected, devices secured, and backup success
Security & Backup Review The record. Scheduled and delivered unsigned, for the client who wants the month on file.
A Quarterly Business Review in a third MSP’s brand: a burgundy and gold masthead, a summary of the quarter, and a chart of tickets by week
Quarterly Business Review The quarter in one document, for the client big enough to sit down over it.

In the docs Run, schedule, and deliver reportsConnections and integrations

Built once. Delivered under your name.

Your brand and your domain

Clients open reports on a report portal in your brand color, on your own domain, with Microsoft sign-in.

In the docs White label and custom domain

Built once, reused per client

Map each client once to its records in the systems you connect. Every run after that gets the right client from every system, on the schedule you set.

In the docs Organizations and mapping

Their data stays theirs

Data from your connected systems belongs to you and your clients. Deepwell uses it to build and deliver your reports and for nothing else. What a client keeps after a report is delivered is your policy, not ours.

In the docs Privacy Policy

Questions MSPs ask.

What is MSP reporting software?

Software that turns the data in an MSP’s tools into reports for the client. It is different from the dashboards inside a PSA or RMM, which report on one tool for the team that runs it.

Is Deepwell a PSA or RMM?

No. Deepwell reads from the systems you already run and produces the client report. It does not replace any of them.

Can Deepwell work with the tools I already use?

ConnectWise PSA, Acronis, and SentinelOne have built-in connections. Any other system with a REST API connects through a custom connection. You can set one up yourself, or talk to us and we’ll help.

What should an MSP client report include?

What you did, what it changed, and what needs a decision, drawn from every system you connect and written in the client’s language rather than the tool’s. A short summary up front, with the figures behind it.

Can reports use my brand and domain?

Yes. Put the report portal on your own domain and set your brand color, and delivered reports open there in your color.

Start with one report.

Send us a report you deliver to a client today. We’ll rebuild it in Deepwell for free and walk you through it next to the original.

Rebuild my report