Analytics

Dashboards, reports, and the semantic layer under them — how HotCRM turns daily activity into insight.

Analytics

HotCRM Analytics turns your CRM activity into decisions. Three layers work together:

  • Dashboards — visual at-a-glance views for execs, managers, and reps.
  • Reports — detailed list-and-summary reports anyone can filter and export.
  • Cubes — the semantic layer underneath. In this app that layer is a set of datasets: HotCRM declares no cube of its own, and the analytics service compiles each dataset into its cube internally (ADR-0021).

What's included

LayerWhat it does
DashboardsFive ready-made dashboards — CRM Overview, Sales Performance, Sales Activity, Customer Service, Executive Overview
ReportsTen standard reports — four on deals, three on cases, one each on leads, accounts and churn
CubesNine datasets in src/datasets/, the layer both of the above bind by name

Two counts on that table used to read differently, and the difference is worth knowing before you go looking. There is no contract report — and none can be built, because src/datasets/ reads nine objects and crm_contract is not one of them, so nothing in analytics counts, sums or groups a contract. And no cube is named Sales, Pipeline, Service or Marketing — those four names exist nowhere in the app. Cubes says which datasets answer the first three and why the fourth has no data source at all.

What you get out of the box

The moment you have data in HotCRM, you have analytics. No setup required.

  • Live dashboards updated in near real-time.
  • Drill-down everywhere — click a chart segment, see the records behind it.
  • Role-aware totals — reps see their own numbers, managers see team rollups, execs see company-wide.
  • Export to Excel / CSV from any report.
  • Subscribe to schedule — get a dashboard PDF in your inbox every Monday morning.

How sharing applies to analytics

The same sharing rules that govern records also govern dashboards and reports:

  • A rep running Opportunities by Stage sees only their own deals.
  • A manager sees the rollup for their team.
  • An exec sees company-wide.

This means one dashboard works for the whole org — what each person sees depends on who they are.

Pipeline by Stage is not a report you can run, though the name is real twice over: it is the open-pipeline funnel tile that CRM Overview, Sales Performance and Executive Overview share (src/dashboards/shared-widgets.ts), and it is the title of the bar chart on the Opportunities by Stage report. Search the report library for it and you find nothing — see Reports.

Where to find things

In the HotCRM app the group is called Insights, and it holds five entries:

  • CRM Overview — the cross-functional dashboard.
  • Forecasts — the forecast records themselves.
  • Pipeline Coverage, Lead Inflow, SLA Performance — three reports pinned to the sidebar by name.

There is no Analytics group, and nothing in the sidebar is called Dashboards, Reports or Cubes. The other dashboards are pinned to the group that owns them — Sales Performance under Sales, Sales Activity under Activity, Service Overview under Service — and the rest of the report library is reached from the reports screen rather than from the nav. Quick tour lists the whole sidebar, group by group.

AI-powered insights

On this app's side, nothing connects the Copilot to a dataset. The six skills under src/skills/ name no dataset, no cube and no measure. The one that answers data questions, Live Data Access, is wired to the platform's object tools and is instructed to re-read the object's schema and aggregate over records — so a Copilot answer is computed from the objects, not read off a compiled cube.

That also sets what it can be asked. "What's driving the gap between commit and forecast?" has data behind it: Commit, Quota, Closed Won and Pipeline are all real figures on the forecast record, published as Commit, Quota, Closed and Pipeline on the Forecast Metrics dataset. "Why did East close 3 fewer deals than West last quarter?" and "Show me which products correlate with longer sales cycles" do not — no region is stored on a deal, no dataset reads line items, and the one duration the opportunity carries (Days in Current Stage) is a formula evaluated after the query, so nothing can aggregate it. Cubes lists the gaps one by one.

Whether the platform's own agent additionally reads the compiled cubes is a question about the runtime rather than about this app, so this page makes no claim about it in either direction; check it against your deployment. See Sales Skills for what the sales-side skills do.

Start here

  • Dashboards — the five built-in dashboards.
  • Reports — the ten standard reports.
  • Cubes — the nine datasets underneath, and what each can and cannot answer.

On this page