Reporting

Reports built from the same filters as everything else.

The most common reporting complaint isn’t a missing chart type. It’s that the dashboard says one number and the view says another, and nobody can explain which is right. That happens when the report builder is a separate query engine. Here it isn’t.

All platform capabilities

Query engine: Shared with views and segments
Drill-through to records: Yes
Historical stage data: From recorded events
Permissions: Row-level, enforced in the engine

Same filter, same answer

A report’s filter is the same definition your saved views use, so a metric can literally point at the view your team works from every morning. When the number on the dashboard looks wrong, you click through to the records behind it — the exact rows, not an approximation that was computed differently.

Pipeline metrics that come from recorded events

Conversion rate, velocity, time-in-stage, and win rate are derived from the timestamped stage-change events the pipeline already records. That means the history is real even if you restructured the pipeline last quarter, and you aren’t depending on a snapshot job that quietly stopped running.

Group and aggregate on any field, including related records
Drill from any figure straight to the underlying records
Scheduled reports delivered on the same durable engine as workflows
Row-level permissions applied, so a rep’s dashboard shows a rep’s data

Deliberately not the first thing we built

Worth being straight about the roadmap: reporting is a weekly surface, not a daily one, so it ships after the surfaces your team lives in every day. The engine it’s built on is the same one already running views and segments, which is why it arrives as configuration rather than as a second query language to learn.

FAQ

Reporting, in detail.

Why do dashboard numbers usually disagree with list views?

Because in most CRMs the report builder and the view builder are different engines with slightly different semantics around empty values, timezones, and related records. Sharing one engine is what removes the class of problem.

Can each rep see only their own numbers?

Yes. Permissions are applied by the query engine, so the same dashboard shows a rep their pipeline and a manager the whole team’s without you maintaining two versions.

Can I schedule a report to my inbox?

Yes — scheduled delivery runs on the same durable engine as workflows, so a missed schedule is a visible failure rather than a silent one.

Can I export the underlying data?

Yes, any report or view exports to CSV, and the same data is available through the API for your warehouse.