A dashboard will answer almost anything you ask it, eighteen months back if you want. What it will not do is have the answer ready before the question arrives.
And the questions turn up at bad moments: by email from finance, in a meeting you are not in, six months later from someone reconstructing why a renewal went the way it did — why is this line going up?, can you prove what we were running in March?, does the mechanical team really need twelve seats? The data is already sitting in LiMon. What is missing is the document: the period picked, the numbers laid out, the argument made, dated, and in a file you can forward without opening anything.
LiMon writes it for you. These are the five it produces as documents. Open them, read them, and decide whether they say what you would need them to say.
Savings Report
Which licenses you are paying for and not using, what the pattern has been over the period, and what it would be worth to drop or redistribute them.
Written for: the renewal conversation, where a number has to be defended
Audit Defense Report
A dated compliance verdict with the deductions behind the score, denials separated into confirmed demand and noise, and a sealed evidence ledger that states plainly what it does not attest to.
Written for: whoever takes the call when the vendor's compliance team gets in touch
Estate Report
An overview of every application you monitor, in one document: the features behind each one, seat counts, expiry dates, and how much of it actually moves.
Written for: the manager who asks what we have, and forwards the answer upward
Application Report
One application in depth: which of its features are actually used, which have gone dormant long enough to harvest, who the power users are, and how demand differs by department and by site.
Written for: deciding what to renew, drop or harvest within a single product
Site Report
One location end to end: the applications served there, what expires and when, who the heaviest users are, and the hours of the day when the site runs out of headroom.
Written for: handing a site or regional lead the numbers for their own location
Chargeback
There is a sixth family, and it is deliberately not a PDF. Chargeback comes out as CSV, because its job is to be loaded into whatever finance already uses to recharge cost centres rather than read start to finish — a table for a process, where the other five are an argument for a person.
DejaVu, shipped with the Docker image, is the default report font. You can change it under Admin → Settings.
About the data
No real company, departments or users appear in these. The applications, servers, sites and people are synthetic. What is real is the report itself: the layout, the sections, the charts and the tables are what LiMon produces, unedited.
Why a document and not just the dashboard?
The dashboard is for investigating: filters, a period you can slide, drilling from a summary line into the sessions underneath. Every one of these reports has a live view behind it — the features page shows that side.
The document is for answering, and you do not assemble it — LiMon does, on demand or on a schedule: generate one the moment you are asked, or have it emailed monthly, quarterly or yearly so it is already there when the question arrives.
And what is written stays written. The database is not immutable: log imports, a decommissioned server, a data-loss incident. Reconstructing later why you decided what you decided is the hard part — which is why you kept the report.
Which editions include them
Intelligence Reports are available on both Standard and Professional, and they need active maintenance. The first year of maintenance is included with every platform purchase. If maintenance later lapses, monitoring carries on and these reports stop until it is renewed — the pricing page sets out what maintenance covers on each edition.