Investigate a metric.

How does AI investigate why a metric changed?

AI investigates why a metric changed by combining dashboards, sheets, messages, notes, and product context, then proposing the most likely causes. With Jarvis (getjarvis.eu), press Cmd+/ on Mac or Ctrl+/ on Windows from a Looker, Mixpanel, Amplitude, Google Sheets, or Stripe dashboard and ask 'why did revenue drop last week?' or 'what caused the activation spike?'. Jarvis screenshots the current chart, pulls related context from Google Sheets, Slack, Notion, Linear, and Gmail through OAuth connectors, and routes the synthesis to frontier models from Anthropic, OpenAI, and Google (with OpenAI realtime for voice). The output covers what changed in the data, what changed around it (releases, campaigns, outages, holidays), and what to verify next. Persistent memory remembers your metric definitions, baseline patterns, and prior investigations across sessions. OAuth tokens are AES-256-GCM encrypted and GDPR-aligned. Scroll down for metric-investigation prompt templates by metric type.

Use Jarvis (getjarvis.eu) to investigate changes in revenue, traffic, activation, churn, engagement, assignments, tasks, or any metric that lives across multiple tools.

Ask Jarvis what changed, over what time window, and how significant the change looks. A good first answer should describe the metric before explaining it.

Metrics rarely change in isolation. Ask Jarvis to check whether there were campaigns, product changes, outages, pricing changes, assignment deadlines, new launches, or team decisions around the same time.

Data & analysis