Pulsehearth

Small operators often discover a refund spike, conversion drop, delivery failure, or churn change only after manually opening several dashboards. The supplied research confirms two KPI products with anomaly, integration, correlation, planning, workspace, and refresh capabilities, but found neither the proposed passive posture nor the combination of voice briefing, plain-language root-cause hypotheses, and an ensemble baseline. Pulsehearth connects only authorized sources, preserves source time and freshness, builds metric definitions and historical bands, detects deviations, and assembles a daily briefing plus urgent alerts. An anomaly is not a cause: every explanation remains a ranked hypothesis tied to observed evidence, missing data, competing explanations, and operator review. Revenue, orders, payments, refunds, subscriptions, product events, campaigns, messages, support volume, and operational logs remain distinct rather than compressed into one health score. The original stage reports two verified APIs, not a verified production connector set. Each source still needs authentication, scope, rate-limit, retention, deletion, freshness, and reconciliation proof. The product never takes business action on its own, never treats data outage as customer behavior, and never shares cross-customer benchmarks without explicit participation and a sufficiently large privacy-preserving cohort.

A solo founder or owner-operator of a sub-$1M-ARR software, ecommerce, or digital-service business who already has several operational data sources but no dedicated analyst.