Attio Reporting CRM RevOps Sales Operations

The CRM Reports That Actually Matter: What We Set Up in Attio After Every Implementation

The 8 reports we configure in every Attio workspace and why most teams are tracking the wrong metrics.

Nacho Lafuente

Nacho Lafuente

March 1, 2026

The CRM Reports That Actually Matter: What We Set Up in Attio After Every Implementation

Every CRM implementation we have ever audited has the same problem: too many reports that nobody looks at and not enough reports that actually change behavior.

Attio's reporting engine is built differently from what most teams are used to. It is not trying to be Tableau. It does not have 47 chart types and a drag-and-drop query builder. What it has is a focused set of report types that answer the questions revenue teams actually need answered, directly inside the tool they work in every day.

After setting up reporting in dozens of Attio workspaces, here is exactly what we configure and why.

The reports you do not need

Before we talk about what to build, here is what to skip.

1. Activity volume dashboards

"Emails sent per rep" and "calls made this week" sound useful. They are not.

Activity volume tells you nothing about activity quality. We have watched reps game these metrics in every CRM that tracks them.

Attio does not let you report on email or meeting volume, and that is actually a feature, not a limitation.

2. Vanity pipeline totals

A single number showing "$2.4M in pipeline" without stage distribution or aging is worse than useless. It creates false confidence.

A $2.4M pipeline with 80% stuck in the first stage is not a $2.4M pipeline. It is a $600K pipeline and a $1.4M wish list.

3. Forecast accuracy reports (in the CRM)

Attio does not have native forecasting, and we are fine with that.

Forecasting is a human judgment exercise that belongs in your weekly team meeting, not in an automated dashboard that produces false precision.

The 8 reports we configure every time

These are the reports we set up in every Attio implementation. They fit on a single dashboard and together give you a complete, actionable view of your revenue engine.

Report 1: Pipeline value by stage

Type: Insight report

What it measures: Sum of deal value (Currency attribute), grouped by pipeline Status

This is the most basic and most important view of your pipeline. You need to see where the money sits.

If 70% of your pipeline value is in the first two stages, you do not have a $2M pipeline. You have a $600K pipeline and a $1.4M wish list.

How we configure it in Attio:

  • Report type: Insight
  • Metric: Sum of your deal value Currency attribute
  • Group by: Status (your pipeline stage field)
  • Visualization: Bar chart
  • Sort order: Manual, ordered by pipeline sequence (not alphabetically)

Attio defaults to alphabetical sorting on Status attributes, so you need to reorder your Status options manually to match your actual pipeline flow.

Report 2: Stage conversion funnel

Type: Funnel report (requires Plus plan or higher)

What it measures: Percentage of deals that advance from each stage to the next

This tells you where deals die.

If your conversion from "Proposal Sent" to "Negotiation" is 30% but every other stage converts at 60%+, you have a proposal problem, not a pipeline problem.

How we configure it in Attio:

  • Report type: Funnel
  • Stages: Include only forward-moving stages (e.g. Qualified → Discovery → Proposal Sent → Negotiation → Closed Won)
  • Exclude: Stages like Paused, On Hold, or other non-linear statuses
  • Timeframe: Last 30–90 days depending on your sales cycle

We exclude non-progress stages to keep the funnel clean and focused on true progression.

Report 3: Time in stage by pipeline phase

Type: Time in Stage report (requires Pro plan)

What it measures: Average number of days deals spend in each stage

This is the report that usually pays for the Pro plan upgrade.

If your average deal takes 12 days in Discovery but 45 days in Legal Review, you know exactly where to focus. We have seen companies shave weeks off their sales cycle just by identifying the bottleneck stage and resourcing it properly.

How we configure it in Attio:

  • Report type: Time in Stage
  • Metric: Average days in stage (avoid Max/Min, which are noisy)
  • Group by: Status (pipeline stage)
  • Timeframe: Last 3–6 months for enough data
  • Target line: Set based on your historical average time to close
Pro-tip from 30+ implementations
Configure time-in-stage targets on your Kanban view too. Attio lets you set a target number of days per stage on the board itself, so cards visually flag when they are aging out. This gives reps a nudge without requiring them to check a dashboard.

Report 4: Monthly deals entering qualified stage

Type: Stage Changed report (requires Pro plan)

What it measures: Count of deals entering your qualification stage per month

This is your leading indicator.

Pipeline value is a lagging metric. The number of net-new qualified deals entering the pipe each month tells you whether next quarter will be good or bad before the revenue shows up.

How we configure it in Attio:

  • Report type: Stage Changed
  • Stage: Your first qualified stage (e.g. Qualified, Sales Accepted, or equivalent)
  • Metric: Count of deals entering that stage
  • Interval: Monthly
  • Compare: Toggle Compare to previous period on

Attio has a built-in compare toggle on Stage Changed reports so the trend is immediately visible.

Report 5: Pipeline by owner

Type: Insight report, segmented by owner

What it measures: Deal count or deal value grouped by stage, segmented by the assigned user

This answers: "Is the pipeline healthy across the team, or is one rep carrying everyone?"

We have audited workspaces where a single rep owned 70% of the qualified pipeline. That is not a pipeline. That is a single point of failure.

How we configure it in Attio:

  • Report type: Insight
  • Metric: Sum of deal value (or Count of deals for volume)
  • Group by: Status (pipeline stage)
  • Segment by: Owner (assigned user)
  • Visualization: Stacked bar chart, vertical orientation

Using Segment By color-codes each rep so you can see both total pipeline and individual contribution at a glance.

Report 6: Win rate over time

Type: Historical Values report (requires Pro plan)

What it measures: Count of deals in "Won" status over time, compared to total deals entering the pipeline

Attio does not calculate win rate as a native metric, so we approximate it with two reports side by side on the same dashboard:

  1. Deals Won per Month
  • Report type: Historical Values
  • Filter: Status = Won
  • Metric: Count of deals
  • Interval: Monthly
  1. Total Deals Created per Month
  • Report type: Stage Changed (or Historical Values if you track a "Created" status)
  • Filter: First stage in your pipeline (e.g. New, Inbound, Unqualified)
  • Metric: Count of deals entering that first stage
  • Interval: Monthly

The ratio of these two numbers is your win rate.

It is manual math, yes. But it is accurate and it trends over time.

Report 7: Revenue by source or segment

Type: Insight report, grouped by a custom Select attribute

What it measures: Sum of deal value grouped by whatever segmentation matters to your business

Examples:

  • Lead source
  • Industry
  • Company size
  • Geography
  • Product line or plan

This requires a custom attribute on your Deal or Company object.

Attio does not track lead source attribution natively, so you need to either:

  • Populate this manually
  • Use hidden form fields with UTM parameters
  • Or wire it through a third-party tool (forms, enrichment, or CDP)

How we configure it in Attio:

  • Create a custom Select attribute (e.g. Lead Source or Segment)
  • Report type: Insight
  • Metric: Sum of deal value
  • Group by: Your custom Select attribute
  • Filter: Only Qualified or Won deals, depending on what you want to analyze

The report itself is straightforward. The hard part is maintaining clean data in the source attribute.

We assign one person on the team as the data owner responsible for making sure every qualified deal has a source tagged.

When we got it wrong
For one logistics client, we created a Lead Source attribute with 23 options. Nobody used it because the options were too granular. We collapsed it to 6 broad categories (Inbound, Outbound, Referral, Partner, Event, Other) and adoption went from near-zero to 90% in a week. The best reporting attribute is the one your team will actually fill out.

Report 8: Connection strength distribution

Type: Insight report, grouped by Connection Strength attribute

What it measures: Count of People or Company records by Attio's built-in Connection Strength rating (No Connection through Very Strong)

This is the report most teams do not think to build, and it is one of the most revealing.

Attio automatically calculates a Connection Strength for every record based on your team's email and calendar activity.

If 80% of your key accounts show Weak or No Connection, your team is not actually talking to the people they think they are managing.

How we configure it in Attio:

  • Object: People or Companies, depending on your motion
  • Report type: Insight
  • Metric: Count of records
  • Group by: Connection Strength
  • Filter: Limit to specific lists, e.g.:
  • Active pipeline
  • Key accounts / strategic accounts
  • Current quarter target accounts

Filtering to the lists that matter keeps the report focused on relationships that actually impact revenue.

What Attio cannot do (and what to use instead)

We are honest about Attio's reporting limitations because hiding them helps nobody.

1. No cross-object reporting

You cannot join data across objects in one report.

If you need something like:

"Show me revenue by industry where the primary contact has title VP or above"

You need to:

  • Export to a spreadsheet, or
  • Push data to a warehouse / BI tool and model it there.

2. No email or meeting volume metrics

Attio shows activity on individual record timelines but cannot aggregate it into reports.

If you genuinely need "emails sent per rep per week," you will need to:

  • Pipe your data to a warehouse (e.g. BigQuery) via a connector tool like Portable, Hightouch, or Polytomic
  • Build the activity dashboards there

3. No native lead scoring

There is no out-of-the-box lead score field.

You can approximate it by:

  • Using AI Classify attributes to auto-tag records based on existing attributes
  • Or building workflow automations that calculate a score and write it to a Number attribute

4. No live formula fields

Attio's calculation blocks exist inside workflows, not as real-time formula attributes.

If you need something like:

Annual Contract Value = Monthly Price × 12

You must:

  • Create a workflow trigger (e.g. on record created/updated)
  • Use a calculation block to compute ACV
  • Write the result into a Number attribute

It works, but it is not the same as a Salesforce-style formula field that recalculates instantly on every change without a workflow.

5. Historical data does not import

If you migrated from another CRM, your Historical Values and Time in Stage reports start from the migration date.

They cannot look backwards into your old pipeline data.

For teams that outgrow Attio's native reporting, the path is:

  1. Export to a data warehouse (BigQuery or Snowflake) via the API or a connector tool
  2. Build dashboards in a BI tool like Looker, Tableau, or Metabase

The dashboard layout we use every time

We build a single "Revenue Operations" dashboard with these 8 reports arranged in 4 rows:

  • Row 1: Pipeline Value by Stage + Stage Conversion Funnel
  • Row 2: Time in Stage + Monthly Qualified Deals
  • Row 3: Pipeline by Owner + Win Rate pair (two reports side by side)
  • Row 4: Revenue by Source + Connection Strength

This fits on one screen. The entire revenue picture in a single view.

No clicking through tabs, no scrolling through 30 widgets. If a report does not fit on this one dashboard, it probably does not need to exist.

Pro-tip from 30+ implementations
Set this dashboard as a favorite so it appears pinned in the sidebar. Then make it the first thing you review in your Monday pipeline meeting. A dashboard nobody opens is a dashboard that does not exist.

The reporting habit nobody talks about

The reports themselves are the easy part. The hard part is building the habit.

We schedule a 15-minute standing meeting every Monday where the team opens this dashboard on a shared screen and walks through three questions:

  1. What changed in the pipeline this week?
  2. Which deals have been stuck in a stage too long?
  3. Where is the connection strength weakest on our highest-value deals?

If your team does this for 4 consecutive weeks, the CRM stops being a reporting tool and starts being the operating system for how deals get done.

Attio gives you the reporting engine. The data model, the dashboard, and the discipline are on you.

If you want someone who has set this up dozens of times to configure your workspace, book a reporting setup call.

Nacho Lafuente

Nacho Lafuente

March 1, 2026

Share