Walk into the QBR with the
number that renews the contract.
Your QBR deck shows tickets closed and patches applied. It does not show the dollars you returned to the client this quarter, the one slide that renews the contract. LumaTrack is the system of record for automation value, white-labeled per client: point a client's automations at it and it prices the technician time they save at cited labor rates, nets out the costs, and keeps a per-client ledger where a closed quarter never changes.
White-label · per client · evidence-graded so a client CFO can audit it.
| productivity 96 h returned × $42.50 loaded rate | $4,080 |
| cost avoidance 3 after-hours callouts auto-remediated × $850 | $2,550 |
| hard 1 redundant backup license retired (invoice) | $1,188 |
| Gross value returned | $7,818 |
| LumaTrack, per-run & build costs | −$612 |
| Net value returned · Q1 2026 | $7,206 |
Illustrative client report · methodology-true. Every figure on it drills down to its formula and runs.
QBR tools measure activity, and clients renew on outcomes.
Lifecycle dashboards, ticket trends, and roadmaps tell a client what you did. They rarely tell a client what it was worth, in dollars, in a form their finance team accepts. "We patched 1,750 endpoints" does not survive a budget review. "We returned $7,206 to your account this quarter, here is the math" does.
The slide that's missing
ScalePad ages your assets, BrightGauge trends your tickets, myITprocess runs the roadmap. None of them produces an auditable dollar-value-delivered number. That gap is where renewals turn.
Built by hand, every quarter
The ROI math that does get shown is a spreadsheet an engineer assembles the week before the meeting. Slow, inconsistent across account managers, and it reads as marketing rather than accounting.
Your own numbers, doubted
A figure the vendor produces about the vendor's own work is the first thing a skeptical client CFO discounts. Evidence that is neutral, graded, and conservative survives it.
One ingest pipe per client. The report builds itself.
Add the client, mint a key
Create a managed org for the client in one step. It gets its own logins, its own API key, and its own walled-off data. No other client can see it, and the client can't see your other accounts.
Point the automations at it
Your RMM patch jobs, backup checks, onboarding scripts, and SOAR stories already run. Each reports its runs with one call. Failures count too: they cost money and the ledger says so.
curl -X POST https://lumatrack.io/api/v1/runs \
-H "Authorization: Bearer lmt_acmedental_..." \
-d '{"automation": "rmm-patching", "status": "success"}'
Send the QBR report
Your brand, your color, your logo on a per-client value report. Share a no-login link for the review, or print it to PDF. Once a quarter closes it doesn't change, so the number a client saw in Q1 is the same in Q3.
A white-label value ledger for every client
Numbers finance will sign
Hard savings, cost avoidance, and returned time each stay in their own lane. Time saved is discounted by the conservatism factor a CFO would apply. Every figure carries an evidence grade and drills to its formula and runs.
Per-client, fully isolated
Each client is its own organization: own logins, own API keys, own automations, walled off from every other client and from you until you switch in to manage it.
Closed quarters stay closed
Once a quarter closes, its numbers stop moving. What a client saw last quarter holds, even after rates and assumptions change, which is what lets them audit the report instead of taking your word for it.
Value beyond labor
Deflected tickets, avoided downtime, dodged SLA penalties: model them as value streams, each in its own credibility lane, on top of the hours your automations return.
Losses become the business case
Track a client's recurring incidents (truck rolls, WAN outages, SLA misses), priced from measured evidence. The same ledger turns them into a board business case, then into the automation that closes them, carrying the measured baseline forward unchanged as the before-anchor.
Your brand on everything
Your name, color, and logo on every shared value report and QBR page. Send a no-login report link for the review, or revoke it the moment it should stop working. Branded client logins arrive with custom domains (on the roadmap).
The whole book at a glance
One consolidated view across every client: value delivered, hours returned, and run volume, with each client metered on its own plan. Switch into any client to manage it without leaving the console.
This is what the client sees, under your brand.
This is the live ledger for one client, headed by your name, with every dollar traceable to the runs and rates behind it, so nobody rebuilds a slide the night before the review. Closed quarters stay put, and an assumption change posts as its own entry instead of quietly moving the past.
Priced by the size of your book
The billing unit is the managed client, because the unit of value is the client QBR. Land cheap, expand as the book grows. Your client pays you far more than $25 a month for the service this report defends.
- 5 managed client organizations included, then $25/client / month
- Each client isolated: own logins, API keys, automations
- White-label, per-client value reports built for the QBR
- Team-grade limits per client: 50 automations, 500k runs / month
- Consolidated book-wide usage and value rollup
Start free, add clients when you're ready
Start on Free, switch on the MSP plan when your first client is live. Full pricing.
The work already happened.
Give the client the number that proves it.
5 managed clients included at $99/mo · white-label · evidence-graded · cancel anytime.
Want the structure without the product? Get the free QBR template.