Hybrid meeting engagement tracker for team leads

When part of a team is in a conference room and part is on video, the people running the meeting lose track of who's actually participating. One complaint captures it well: 'managing engagement between in-person and remote groups takes some practice.' That's a polite way of saying that remote attendees get ignored, in-room attendees talk over each other, and the person running the meeting has no signal about who's checked out.

This gap persists for a structural reason: conferencing vendors optimize for connection quality and feature completeness, not for meeting facilitation. They can tell you if someone's microphone is muted. They can't tell you that the three remote participants haven't spoken in 40 minutes while two in-room voices have dominated the call. Facilitation is a human problem, and vendors treat it as out of scope.

What meeting leads actually need is a lightweight dashboard — visible only to the host — that tracks participation signals in real time: who has spoken, for how long, how often, and who hasn't spoken at all. Not a transcript, not an AI summary after the fact, but a live view during the meeting that lets the host redirect attention before the remote participants fully disengage. Current tools either offer nothing, or offer post-meeting analytics that are useless in the moment.

This is a recurring business problem for anyone who runs regular hybrid standups, project reviews, or client calls. The cost isn't always visible — it shows up as remote employees feeling excluded, decisions made without their input, and eventually attrition. Teams that run hybrid meetings three or four times a week have this problem constantly, and no amount of 'best practices' guidance fixes it without a live signal to act on.

What to build

Build a host-only overlay that sits on top of any video call (via a browser extension capturing the active tab's audio track with user permission) and displays a live participation heat map — per participant, showing speaking time and last-spoke timestamp — updating in real time so the host can see and act on imbalances before the meeting ends.

Where to start

Start with teams already using a conferencing vendor that offers a developer SDK with speaker identification (such as Amazon Chime's media capture pipeline), targeting engineering managers at mid-size remote-first companies who already instrument their team health and are comfortable granting microphone permissions to a browser tool.

The hard part

Accessing per-participant audio separation in a running video call without a native SDK integration is technically constrained — most browsers don't expose individual speaker streams from a conferencing tab, so the product may need to require a dedicated app or a conferencing vendor's SDK integration rather than a universal overlay, which limits early distribution.

How it makes money

Monthly subscription per host seat, with a free solo tier (one host, unlimited meetings) that converts when a team lead wants to share the dashboard with co-facilitators or export participation reports to their 1:1 notes.