You open your dashboard Monday morning. Leads are down 22% week-over-week. The chart is right there — a clean line dipping south.

Now what?

The dashboard told you what happened. It's not going to tell you why. And it's definitely not going to tell you what to do about it.

That gap — between "what happened" and "what should I do" — is where most teams stall. The dashboard creates the question. Answering it requires a completely different kind of work.

The dashboard's job

Dashboards are good at one thing: showing you the current state of your metrics. They're monitoring tools. They watch numbers and surface changes. GA4 shows you traffic. Shopify shows you revenue. HubSpot shows you pipeline.

They do this well. The problem isn't that dashboards are bad. The problem is that people expect them to do something they were never designed to do: explain.

When your CMO asks "why did leads drop?" the dashboard shows the drop. That's it. The why requires investigation — pulling data from multiple sources, isolating variables, testing hypotheses, ruling out confounding factors.

That's analysis. Dashboards don't analyze. They display.

The investigation gap

Here's what the "why did leads drop" investigation actually looks like in practice:

Export lead data from HubSpot
Export campaign spend from Google Ads and Meta
Export traffic data from GA4
Open Google Sheets
Manually align the date ranges
Build a pivot table comparing channels
Eyeball the data for correlations
Maybe make a chart
Realize you need to normalize for seasonality, give up, or call the analyst

Steps 1-4 take an hour. Steps 5-8 take another hour. Step 9 costs $75-200/hour and a three-day turnaround.

The dashboard that surfaced the question took 2 seconds to load. The answer took half a day.

What analysis looks like

Same scenario. Leads dropped 22%. You upload your HubSpot export, Google Ads spend data, and GA4 traffic to heyanna. You ask Anna: "Why did leads drop this week?"

Anna correlates the datasets by date. She finds it:

"Leads dropped 22% WoW. The primary driver is a 100% reduction in Google Search spend — the campaign was paused on Tuesday. Search was responsible for 41% of lead volume over the prior 8 weeks. Paid social and organic remained flat, confirming this is a channel-specific issue, not a market-wide trend."

Then she goes further:

"Based on the strong historical relationship between search spend and lead volume (R² = 0.87), restarting the campaign at 80% of the previous budget should recover approximately 89% of the lost volume within two weeks."

Lead Volume Drop

-22%

Cause

Paused Search

Projected Recovery

89%

at 80% budget

That's not a metric on a dashboard. That's a recommendation backed by evidence. It names the cause, quantifies the impact, and suggests a specific action with a projected outcome.

When something moves on your dashboard, export the relevant data and ask Anna "why did [metric] change?" She'll cross-reference datasets and isolate the driver — often in under five minutes.

Dashboards monitor. Analysis explains.

The distinction matters because teams often invest in better dashboards when what they actually need is better analysis.

More charts don't help you understand why churn spiked. A prettier Looker dashboard doesn't tell you which product to discontinue. Real-time data doesn't matter if nobody knows what to do with it.

What you need	Dashboard	Analysis
"What's our conversion rate?"	Yes	Overkill
"Why did conversion drop last week?"	Shows the drop	Explains the cause
"Should we increase ad spend on Meta?"	Shows current ROAS	Calculates historical elasticity and projects ROI
"Which customer segment is most profitable?"	Maybe, if pre-built	Cross-references revenue, acquisition cost, and retention
"What should I tell the board?"	Gives you charts	Gives you a narrative with evidence

The left column is what most people actually need. The right two columns show why one tool can't serve both purposes.

The tools you already have

This isn't about replacing your dashboards. GA4 is fine for tracking traffic. Shopify analytics is fine for monitoring daily revenue. HubSpot is fine for pipeline visibility.

The problem is the moment between seeing the number and understanding it. That moment is where you export a CSV, open a spreadsheet, and start the investigation that your dashboard can't do for you.

That export-to-spreadsheet workflow is what Anna replaces. Not the dashboard itself — the manual investigation that follows every time a dashboard raises a question you can't answer by zooming in on the chart.

A real workflow

Here's how this works in practice for a marketing manager who uses GA4, Google Ads, and HubSpot:

Monday morning: Dashboard shows leads down 22%. You export three CSVs — one from each platform.

Monday, 10 minutes later: Upload all three to heyanna. Ask Anna: "What caused the lead drop? Compare across channels and campaigns."

Monday, 15 minutes later: Anna's report shows the paused search campaign, quantifies the impact, and recommends restarting at 80% budget. You share the report link with your CMO.

Monday, 15 minutes and 30 seconds later: Your CMO has the answer, the evidence, and a recommendation. Compare that to the alternative: half a day in spreadsheets, a rough analysis you're not confident in, and a Slack message that says "I think it might be the search campaign pause, but I'm still digging into it."

The real question

Your dashboards are fine. Keep them. They do what they were built to do.

The question is: what happens after the dashboard raises a question? If the answer is "I spend two hours in a spreadsheet" or "I ask the data team and wait three days" or "I just go with my gut" — that's the gap.

Anna fills the gap. Not by replacing your monitoring tools, but by doing the work that comes after. Real situations are often messier — Anna handles multiple contributing factors and flags when the picture isn't clean.

This applies equally to Looker, Tableau, or Power BI — the gap isn't about chart sophistication, it's about who investigates when the chart raises a question.

Start with your data.