Funding
Funding not disclosed
Founders
Product
Problem
Engineering managers often miss early signs of overload, disengagement, or stalled work because they lack a way to monitor subtle patterns in asynchronous tools like Slack, GitHub, and calendars without invasive data collection.
Solution
Sonar continuously ingests only metadata—timestamps, PR events, and calendar activity—from a team’s communication and development tools. It analyzes these signals to identify patterns such as prolonged work hours, delayed code reviews, or missed meetings. Each weekday morning, managers receive a concise brief that highlights at‑risk individuals and provides a ready‑to‑use conversation starter. Employees have personal dashboards where they can view the collected metadata, see which signals were triggered, and control or delete their data, ensuring full transparency. The system is built to never access message or code content, never assign scores, and never share data with HR, focusing solely on prompting timely manager‑employee conversations.
Target Audience
Sonar is designed for engineering managers and team leads who oversee small to medium‑sized technical teams (typically 4–12 direct reports) and need an unobtrusive way to spot early signs of burnout or workflow bottlenecks.
Features
- Metadata‑only ingestion from Slack, GitHub, and calendar integrations; no message or code content is ever read
- Automated detection of 12 predefined work‑pattern signals (e.g., overload, stalled PRs, missed 1:1s)
- Daily manager brief delivered at 7 AM with highlighted at‑risk team members and suggested conversation openers
- Individual employee view (/me) showing collected events, fired signals, and one‑click controls to pause, export, or delete data
- Configurable retention (default 90 days) and per‑source opt‑out to respect privacy preferences
- Two pricing tiers (Manager and Executive) with flat base fees plus per‑person or per‑manager charges; free tier for up to 4 members
- No scoring, ranking, or HR‑facing features; the product is conversation‑first, not report‑first