For engineering managers · Metadata only · Free up to 4

Know who needs you,
before they have to ask.

Every Monday morning: the two or three people on your team who need a conversation that week — and the specific reason behind each one. Reads Slack, GitHub, and Calendar metadata. Never message contents.

Get started See a sample brief ↓

Free for the first 12 · No card · Direct line to the founder

[Sonar] Sun, Jun 28 — 3 items need attention

From brief@sonar.so · To you@yourco.com

Morning. Three of your eight reports need a conversation today.

Overloaded·Marcus R.
Past 11pm six nights this week. Threads unresolved.
Gone quiet·Devon P.
No commits, PRs, or messages for 8 days. No PTO marked.
Invisible carrier·Sam P.
Reviewing 70% of team's PRs. Unblocking 4 others quietly.
Attention gap·You
4-min reply to Marcus, 47-min to Devon. 30-day trend.

Metadata only · Never reads messages · Delivered weekday mornings

Synthetic example · real format

Metadata only · No HR exports · GDPR & CCPA

Your team sees everything Sonar collected about them →

Synthetic example · names are initials

Manager Intelligence Brief0600Z · Team: 8

Weekday morning · 7:00 AMExample

The Brief

Three people need a conversation.
One pattern is worth recognizing.

Plain English. No surveys. No dashboards.

01S-01
Overloaded
Marcus R.
Online past 11pm six nights running. Threads sitting longer than typical.
read →
02S-02
Gone quiet
Devon P.
No PRs, commits, or messages in eight business days. No PTO marked.
read →
03S-03
Stalled
Alex R.
PR open nine days. Two reviewers assigned, no response yet.
read →
04S-04
Attention gap
You
4-min reply to Marcus, 47-min to Devon. 30-day trend. Worth thinking about.
read →

Delivered every weekday · your morningGet started →

The dashboard has the detail behind every line. Click any signal to see the pattern Sonar saw, and one good question to open the conversation.

The problem

By the time you noticed, it was already week seven.

Burnout, disengagement, and quiet quitting almost never happen overnight. The signal was on the wire for weeks. The manager just didn’t have a way to read it.

Week 1

"All good. Sarah's a star."

Manager's check-in

Week 3 · Sonar flags

Pattern detected early.

Manager hasn't noticed yet

Week 7

"Wait — Sarah just gave notice?"

Too late to act

Schematic · one engineer, eight weeks · Sonar flags at week three

For your team

Each person on your team gets the same view you do, with four buttons that work without asking you. Pause, export, delete, push back.

See what your team sees →

① Listen

Sonar reads work patterns, never message text.

Slack, GitHub, and calendar — and more. We see timestamps, PR events, and meeting patterns. Never what anyone wrote or said.

① Slack inbound14:32:08 UTC

Marcus R.#chan-7e4f

Body redacted before write

② Metadata extractedSHA-256 hashed

Timestamp: 14:32:08
Channel id: #chan-7e4f
Author: marcus-r
Char count: 184
Reactions: 3
Thread reply: yes
Response time: ▲ 47 min · up from 11 min

③ Morning brief7:00 AM local

Overloaded · 6 weeks

Marcus Rivera

Online past 11pm most nights for six weeks. Threads sitting longer than typical. Worth five minutes of your morning.

One opener: “What would actually take pressure off this week?”

Same data path Sonar runs in production · metadata only

Synthetic example · names changed

② Triage

The brief above lands every weekday morning. Before you open Slack.

Three to five names. One signal per person. One line of evidence. One question to open the conversation with. Not a dashboard you log into. Not a feed you scroll.

③ Act

The brief names the person. The dashboard shows you everything.

Click through and you see the full signal: what changed, when it changed, how long the pattern has been building, and one question to open the conversation with. The live signals feed updates continuously — not just when a brief lands.

Signal detail · Overloaded

Example · Senior engineer

Marcus Rivera · Senior EngineerExample

Overloaded · running 6 weeks

Working hours up. Throughput holding. Recovery time gone.

Sonar started flagging this six weeks ago and the trend has steepened. None of the four signals below are urgent on their own. Together, they describe someone running out of slack.

Evidence

Hours
Active past 11pm on 14 of the last 21 nights — up from 4 of the prior 21.
Response time
Answering team threads in 47 minutes on average — up from 11 minutes three weeks ago.
PR load
Open PRs sitting at 9 (typical: 3). Two have been waiting for review for 6+ days.
Calendar
Two of the last three 1:1s with peers were skipped. No declined-meeting reasons given.

One way to open

“You’ve been working late most nights for a few weeks now — what would actually take pressure off this week?”

Sonar suggests one opener per signal. You can copy it, edit it, or ignore it. The conversation is still yours.

Mark handledSnooze 1 weekNot actually a patternMarcus can see this view at any time

④ Tune

Your team sees what Sonar collected about them. No surprises.

When you install Sonar, every person on your team gets their own page: what was collected, which signals fired about them, and buttons to pause or delete their data. No surprises. No hidden admin view. Nothing goes to HR.

See the page your team gets →

sonarwork.com/me

Logged in as you

Your data on Sonar.

Everything Sonar has on you. Same data your manager sees, four buttons that always work.

Collected this week

Slack metadata: 142 events
GitHub events: 38 events
Calendar shape: 19 events
Message text read: 0

Signals fired about you

Rising · 2 weeksin this morning’s brief

Your controls

No emailing your admin. No support ticket. Click and it happens.

“Sonar started as an internal tool I wrote because I kept watching teammates burn out, check out, or get passed over while their managers—good managers—learned about it weeks too late.”

— Yash, founder · About Sonar

The contract

We will never read message text, score your team, or recommend firing.

Sonar reads metadata — timestamps, PR events, calendar shape. Never message text. Never an HR export. Never a leaderboard. We point at patterns; the conversation is still yours to have.

Read the full security posture →

Ready when you are

A quieter morning, starting in your inbox.

Connect three tools. Sonar listens for two weeks. Then every weekday morning, the brief lands.

Get your Monday brief See the signals

No card · Cancel any time

Know who needs you,before they have to ask.

Three people need a conversation.One pattern is worth recognizing.