Free beta for business data exploration
Connect your stack. Ask about your business. Explore the evidence behind metric changes.
Finite monthly allowance. No card. No automatic charges or paid conversion.
Correlation and timing help investigate a change; they do not prove its cause.
The Problem
CEO / FOUNDER
Business data is spread across too many tools.
You ask your team for a simple metric. Three people give you three different numbers from three different dashboards. None of them are current.
Cost of Inaction
Manual reconciliation takes time away from decisions
VP SALES
Forecasts need context from billing and support.
Your CRM says one thing. Billing says another. Support tickets paint a different picture entirely. By the time you see the pattern, the customer is gone.
Cost of Inaction
Disconnected signals make changes harder to investigate
HEAD OF OPS
Keeping integrations and reports current takes work.
You spend your days copying data between systems, building brittle automations, and explaining why the numbers do not match.
Cost of Inaction
Data quality matters as much as the dashboard
The Solution
Choose a supported connector and authorize access to your SaaS data. Setup and initial sync time depend on the tool, permissions and data volume.
Ask about supported business metrics in natural language. The query engine routes the request, and explanations use the metric history available for your analysis.
Review detected anomalies and morning briefs as synced data accumulates. Use the findings to decide what to investigate next.
Beta Connectivity
Choose an available connector in the app; catalog entries are not a support guarantee
Review permissions and authenticate with OAuth or an API key
Review mapped fields and metric coverage
Check sync status; history depends on source permissions and availability
Incremental syncs keep data fresh on a per-connector schedule
Connector setup depends on the source and permissions. Some sources require administrator access.
Review sync errors and reconnect when authorization expires. Automated recovery cannot fix every provider failure.
Start with an available adapter. Ask us about missing sources; custom integrations are not guaranteed.
Check what the source actually supplies. Missing metrics or history limit which questions can be answered.
Connector availability is not metric coverage. Review synced records, unsupported data and source permissions before relying on an answer.
Illustrative Product Preview
Sample data and interface illustration, not a customer result or measured prediction.
Morning Brief
Connected
Review support, usage and billing signals together. These sample observations suggest questions to investigate; they do not establish churn risk or its cause.
Support Response
+2.3 days avg
Usage Frequency
-34% last 30d
Invoice Status
2 overdue
Questions to Investigate
Science and Methodology
Pearson correlation compares date-aligned metric series.
Find metrics that move together. Correlation does not establish a cause.
PELT changepoint detection identifies shifts and compares their order.
A preceding change is a possible lead to investigate, not causal proof.
When enabled and data qualifies, compare changes with a statistical baseline.
Reporting boundaries are not verified interventions; these estimates remain observational.
Graph discovery is not connected to customer-facing explanations.
No live graph-derived causal answers are claimed.
Compare supported metric series from connected tools to find co-movement.
Explanations report their analysis tier and limitations. Statistical significance alone does not establish causation.
Z-score analysis flags statistical outliers for review.
The explanation engine reports insufficient data when the requested metric lacks history. Available data and method assumptions limit what an explanation can establish.
Security · Data Handling
Try a business question you can verify. Review the source evidence, tell us where the answer falls short, and help shape this free beta.
For Founders
Bring billing, CRM and support signals into one place to investigate changes. Start with the data you have, and review what it can and cannot tell you.
Use plain English to explore supported metrics across your connected tools. Review the available data and analysis behind the response.
Connect with a restricted API key to sync billing records. Recurring revenue normalization currently supports USD licensed, fixed per-unit prices; non-USD, mixed-currency, metered, tiered or incomplete prices are reported as unsupported. This is not accounting reconciliation or Stripe reporting parity.
Receive a summary of available metrics, detected anomalies and suggested follow-up questions. Delivery depends on your configuration and synced data.
Explore questions such as "Why did MRR change?" with correlation and temporal analysis. An observed pattern is a lead to investigate, not proof of a cause.
Pricing
No card or automatic charges. A finite monthly usage allowance covers queries, syncs, briefs and actions. Paid plans below are future reference, not beta obligations.
Free beta
$0
10,000 credits/monthUp to 3 connected sources
Free, non-paying beta. No card and no automatic paid conversion.
Founder — future plan
$0.10/metered operation
Metered, not free betaUp to 3 connected sources
Future paid offering, not available from a beta workspace. No automatic conversion.
Starter — future plan
$999/mo
10,000 credits/monthUp to 10 connected sources
Future paid offering, not available from a beta workspace. No automatic conversion.
Business — future plan
$2,499/mo
25,000 credits/monthUp to 20 connected sources
Future paid offering, not available from a beta workspace. No automatic conversion.
Enterprise — future plan
$4,999/mo
50,000 credits/monthNo plan connector cap
Future paid offering, not available from a beta workspace. No automatic conversion.