Executive Dashboards and Reporting

The problem

Quarterly business review week arrives and somebody exports tickets to a spreadsheet, somebody else pulls invoices, and a third person reconciles the two by hand the night before. The deck that comes out of it is a snapshot nobody can reproduce a month later, and the one number the client asks about — “what was our SLA attainment, really?” — turns out to be a formula in a cell.

The tooling is often worse than the spreadsheet. Dashboards show a confident green 100% for a client whose tickets were never measured, a $0 balance to somebody who simply was not allowed to see the balance, and an “estimated MRR” nobody can tie back to what was actually billed. A number you cannot trace is a number you cannot put in front of a client.

What Solidlio does about it

Two surfaces, one source of truth. Executive dashboards aggregate live over every organization you work across — your own service desk included, and every client you co-manage — and separate that reach from your book of business, so workload and client count are never silently conflated. Reports are artifacts: you queue one, a worker aggregates and renders it, and you download a file that still says the same thing in six months. And where there is no data, the product says so: an unmeasured SLA reads “No data”, not a green 100%; a figure your role cannot see reads ”—”, not $0.

Capabilities

Built for MSPs and their clients

An MSP dashboard is not one big pile of everyone’s data, and a client’s dashboard is not a cut-down copy of the MSP’s. Each side gets the aggregate that belongs to it.

Two structural guarantees fall out of this. An MSP’s own service desk always counts toward its own workload — bringing on a first client does not make the in-house desk appear out of nowhere. And a second MSP brought in to co-manage a client sees that client’s work immediately, without taking over the billing relationship.

How it works

1. Open the executive dashboard and pick a window — today, 7, 30 or 90 days. Tiles, SLA rings, escalation trends, client health and asset health load in one request.
2. Spot the thing worth explaining — an SLA rate that moved, a client whose breach count is climbing, receivables drifting past due.
3. Generate the report behind it. Pick the type, the date range, the clients and the format; add charts if it is going in a deck.
4. The worker renders it out of band. Your request returns immediately with a pending row; the library polls and the row advances on its own.
5. Download the artifact. The account and, for financial reports, the role are re-checked at that moment and the bytes are streamed to you.
6. Attach it. The file is fixed. Re-running the same range next quarter produces a comparable document, not a differently-shaped one.

Compliance and audit

• Every report records who ran it, when, over what range, and over which client organizations — and the file’s row count, so an empty report is distinguishable from a broken one.
• Scope is resolved at generation time from the report’s own account. A report queued before a client was detached cannot widen back into that client afterwards, and a request body can never widen scope beyond the account.
• Financial reports are gated on generation and again on download. A report is account-wide and stays in the shared library, so the second check is what stops a technician retrieving an administrator’s margin analysis.
• Report files are not addressable. There is no public or signed blob URL; every download passes the account check and streams through the API.
• A failed report says why. Generation failures are recorded on the row with a readable reason. No report is left silently pending, and none is marked complete with no file behind it.
• Truncation is declared. A table capped at 5,000 rows says so inside the artifact, in every format.

Editions

The report library and the organization executive dashboard carry no plan gate — every report type, format and option is available on every tier, including Free. The cross-client roll-up is the gated capability.

MSP tiers shown. Customer tiers map as Free / Essentials / Professional → Business (operational roll-up) → Enterprise (financial roll-up).