Reports hub
The owner's numbers on one page: revenue by month, pipeline value by stage, lead sources, field-job status, and event attendance — every panel a view over endpoints the app already calls, charted with the dependency-free kit BarChart, and every panel exports its rows as CSV (money verbatim).
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: GET /fin/revenue, /crm/pipeline, /crm/leads, /ops/jobs, /events.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Always on for analytics-permitted roles.
- Who can use it
- ord.analytics.read for the nav seat; each panel inherits its own domain's read permission (the API is the wall).
- The API behind it
GET /fin/revenue, /crm/pipeline, /crm/leads, /ops/jobs, /events- Where it lives
- /reports
See it in context
Revenue intelligence — the full walkthrough, step by step: Pipeline health, job margins, forecasts — the numbers, from the system of record.
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.