Insight

Reports

Six cross-module analytics lenses with period and currency filters, and export.

Updated 2026-06-238 sections3 min readFor the marketing team

1In one sentence#

The Reports module is LumosCRM's cross-module analytics centre — a single screen that pulls revenue, service operations, client, vendor, and event data from across the whole CRM into clear charts and tables you can filter by period and currency, and export.

It answers the leadership questions: "How are we doing — on money, on service, on clients, on suppliers, on events?"

2Who it's for#

RoleWhat they get
Leadership & ownersA consolidated view of business performance across every module.
FinanceRevenue and receivables analytics by period and currency.
OperationsService throughput and SLA performance.
Account & vendor managersClient and vendor breakdowns to guide where to focus.

3The core idea: six lenses on one business#

Reports is organised as six tabs, each a different lens on the same underlying data:

TabWhat it showsGrouped by
OverviewA consolidated snapshot across the business.Client tier
RevenueBilling and income performance.Client tier
Service OpsRequest/service throughput and operational performance.Client tier
ClientsClient-base breakdowns and contribution.Client tier
VendorsSupplier activity and standing.Vendor status
EventsEvent volume and mix.Event category

Every tab respects a shared time period and currency filter, so the whole picture stays consistent and comparable — and because mixing currencies is meaningless, money is always scoped to a chosen currency.

4Capabilities at a glance#

CapabilityWhat it means
Six analytics tabsOverview, Revenue, Service Ops, Clients, Vendors, Events.
Period filterLook at any time window.
Currency scopingAll monetary figures scope to a chosen currency.
Charts & tablesClean visualisations (rendered crisply, no heavy dependencies) plus ranked tables.
ExportExport any tab's data (CSV) for spreadsheets and board packs.
Permission-gatedViewing and exporting are separately controlled.
Fast & efficientEach figure is computed with bounded, optimised queries — built to stay quick at scale.

5The screen#

A single Reports page with a tab bar (the six lenses), a period selector, and a currency selector in the header. Selecting a tab loads its charts and ranked tables; the data is grouped by the tab's natural dimension (tier, status, or category). An Export action downloads the active tab's figures.

Money is computed in minor units and presented in whole currency units, and figures are produced with single, bounded queries per widget (aggregates rather than row-by-row loops), so the page stays responsive even on large datasets.

6Security & access control#

  • Two permissions: reports.record.view to see the analytics, and reports.record.export additionally required to export.
  • Scoped data: analytics respect the same per-user data-scoping rules as the rest of the CRM, so a self-scoped user's numbers reflect only the records they're entitled to see.

7Use cases & scenarios#

Use case A — The monthly board pack#

The owner sets the period to last month and currency to EUR, reviews the Revenue and Service Ops tabs, and exports each to drop straight into the board deck.

Use case B — Where's the revenue coming from?#

On the Clients tab, leadership sees contribution broken down by tier and confirms that Founding and Elite clients drive the bulk of revenue — informing where to invest relationship effort.

Use case C — Supplier health#

The Vendors tab, grouped by status, shows how much activity flows through active versus prospecting suppliers.

8Glossary#

TermMeaning
Tab / lensOne of the six analytics views (Overview, Revenue, Service Ops, Clients, Vendors, Events).
PeriodThe time window the report covers.
Currency scopingRestricting money figures to one currency so they're comparable.
ExportDownloading a tab's data (CSV).

This document describes the Reports module as currently built: six analytics tabs with period and currency filters and per-tab export, viewing/exporting gated by permission and bounded by per-user data scope.