CRM with reporting: formula reports and dashboards that actually work

Every CRM claims to have reporting. In practice, “reporting” splits into two very different categories: pre-built dashboards you cannot modify, and a report builder that lets ops leads write formula-based reports with custom metrics. The gap between the two is the difference between a tool that works for your business and a tool whose reports your team re-does in a spreadsheet.

This post covers what good CRM reporting requires, where generic CRMs fall short, and the patterns that produce reports your team actually uses.

Why reporting is where most CRMs disappoint

Three structural reasons CRM reporting underperforms expectations:

1. The pre-built reports do not match your actual metrics

Every CRM ships with “Pipeline by Stage” and “Deals Closed This Quarter” and “Lead Conversion Rate.” Fine for a demo. Useless for a RevOps lead who needs “Weighted pipeline coverage for Q3 by rep and segment, filtered to deals in Negotiation older than 45 days, with a ratio to quota attainment.”

The real reports a sales ops team runs are custom to the business. If the CRM only offers pre-built reports, those custom reports move to a spreadsheet. The CRM becomes a data entry tool whose data is re-queried from somewhere else.

2. Formula-based metrics are gated behind higher tiers

The ability to write a formula like “SUM(deals.amount) WHERE deals.stage = ‘Negotiation’ AND deals.age > 45” with ratio metrics (conversion rates, attainment percentages, period-over-period comparisons) is often gated behind Enterprise tiers. Teams at Series A that need this capability either pay for Enterprise or build it in a spreadsheet.

3. Cross-object reporting is weak

Reports that need to pull from multiple objects (Deals + Projects + Marketing campaigns + Support tickets) are harder than they should be in most CRMs. The data lives in different tables with different relationships, and the report builder cannot join them cleanly without SQL knowledge.

What good reporting requires

Six capabilities separate real CRM reporting from marketing claims:

1. Formula-based custom metrics

The ability to write calculated metrics (ratios, conversion rates, period comparisons) in the report builder itself without pre-computed fields. “Win rate by segment,” “deal velocity by stage,” “forecast coverage ratio” should all be writable as formulas.

2. Cross-object joins

Reports that pull from multiple objects via lookups. “Deals grouped by Account industry, filtered to Accounts with open support tickets” requires joining Deals to Accounts to Tickets. The report builder has to handle this without SQL.

3. Grouping and aggregation at multiple levels

Group by rep, then by stage, with subtotals. Group by region, then by rep, then by month. Flexible grouping with aggregation at each level is table stakes for serious analysis.

4. Scheduled delivery

Reports that email or Slack themselves on a schedule. The weekly pipeline review happens whether or not someone opens the CRM to pull the report.

5. Drill-down from aggregate to detail

Dashboards show aggregate numbers. Click into the number and see the underlying records. If the dashboard is just a chart with no drill-down, it is a static image.

6. Export to CSV / Excel for ad-hoc analysis

For the questions the report builder cannot answer directly, you need to export clean data to Excel. Every report should support one-click export to CSV.

Where generic CRMs fall short

HubSpot

Reporting improves with each tier. Starter reporting is pre-built; Professional unlocks custom report builder; Enterprise unlocks custom formulas and more sophisticated cross-object reporting. Teams needing serious reporting often find themselves pushed to Enterprise.

Pipedrive

Reporting is clean but shallow. Fine for pipeline-focused analysis; limited for teams needing custom metrics or complex cross-object joins.

Salesforce

Powerful reporting, especially with Tableau (formerly Einstein Analytics) on top. The complexity cost is significant; serious reporting typically requires admin or RevOps expertise to configure.

Zoho

Capable reporting with a formula layer. Interface is dated but functional. Reports pre-built for standard use cases.

Monday CRM

Reporting is dashboard-first with limited formula support. Fine for teams tracking standard metrics; limited for teams needing custom calculated fields.

How Strkr handles reporting

Strkr’s formula-based reports are available on every paid tier at no gated-feature upcharge. Any paid user can build a custom report with:

• Formula-based metrics. Full access to the formula engine (30+ functions, cross-object references via lookups up to three levels deep).
• Cross-object joins. Report primary object plus related objects via lookup fields. Group, filter, and aggregate across the joined dataset.
• Grouping at multiple levels with subtotals at each level.
• Scheduled delivery via email, Slack, or Teams. Fires on a cron-style schedule.
• Drill-down from aggregate charts to the underlying records.
• CSV export on every report.

Reports are built in a visual builder; no SQL required. The same formula engine that powers custom fields and custom objects powers report metrics, which means a formula written on a custom field can be re-used in a report.

The design target: a sales ops lead at Series A should be able to produce every report their team needs without a RevOps analyst, admin certification, or a spreadsheet workaround.

The reports teams build in month 1

Based on what new Strkr customers typically build:

1. Weighted pipeline coverage by rep, segment, and quarter. Ratio of weighted pipeline to quota.
2. Deal velocity by stage. How many days deals spend at each stage, grouped by segment.
3. Win rate by segment, by rep, by competitor. With historical trend lines.
4. Forecast attainment accuracy. Submitted forecast vs actual, per rep, per quarter.
5. Pipeline health flags. Count of deals that are stuck (dwell time > 2x median), stale (no activity in 14+ days), or at-risk (AI probability < 20%).
6. Lead-to-deal conversion by source. Which lead sources produce the deals that close.
7. Account health score distribution. For SaaS teams tracking retention and expansion.
8. Project profitability (if using the Projects module). Billable hours vs budget per project.

All of those are formula-based reports built in the visual builder, scheduled to deliver weekly or monthly to the relevant stakeholders.

When reporting is still not enough

A few cases where a CRM report alone is not the right answer:

1. Multi-source reporting across non-CRM systems. If your reporting needs to join CRM data with product usage, financial data, and marketing attribution across multiple source systems, a BI tool (Tableau, Looker, Metabase) with the CRM as one data source is the right pattern.
2. Executive dashboards for the whole company. The CFO wants a single dashboard spanning sales, product, finance, and ops. CRM reporting is one input; the BI tool is the destination.
3. Longitudinal analysis across years of history. CRM reports work well for current state and recent history. Long time-series analysis (seasonality, cohort behavior over 24+ months) is better suited to a BI tool with time-partitioned data.

For most sales ops reporting, the CRM is where the reports should live. For broader analytics, pipe the CRM data to a BI tool.

Related reading: How to choose a CRM: a practical buying framework walks through the broader buying question.

Conclusion

Good CRM reporting means formula-based custom metrics, cross-object joins, scheduled delivery, drill-down, and CSV export, all available on every paid tier. The CRMs that gate these behind Enterprise tiers push teams to spreadsheet workarounds; the ones that include them produce reports teams actually use.

Pick a CRM where the reporting is a first-class feature on every tier, not a premium upsell.