Fly Labs
Ask FlyBot

Remote Collaboration and Team Presence

Teams working remotely or across locations struggle to stay connected, coordinate work, and understand who's available without constant status updates

YC GraveyardToolB2BSource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

A presence and availability layer for remote teams that replaces manual status updates with automatic context about who can actually work right now.

The pain

Remote workers interrupt each other constantly because they can't tell if someone is free. Teams use Slack status, calendar blocks, and direct messages to signal availability, but these decay quickly and require discipline. Managers lose visibility into team capacity. Async work gets blocked waiting for synchronous responses.

The gap

Slack, Teams, and calendar tools show presence poorly. Slack status is manual and stale. Calendar shows meetings but not focus time or timezone context. No tool aggregates signals (calendar, last activity, timezone, current task) into a reliable 'can I interrupt this person' indicator. The market has Slack status, Loom async video, and calendar tools, but nothing that solves the specific coordination problem of knowing availability without asking.

Build angle

Start by solving the narrow problem: a browser extension or Slack bot that shows real availability (calendar + last activity + timezone + user-set focus blocks) in a single glance. Don't build another communication tool. Integrate deeply with existing tools teams already use. Measure success by reduction in 'are you there?' messages and faster response times on async work.

Strengths

  • Real problem with daily friction for 50M+ remote workers
  • Existing tools (Slack, Teams, Google Calendar) have weak presence signals, clear gap to fill
  • Low switching cost if positioned as a layer on top of existing tools
  • Measurable outcome: fewer interruptions, faster async handoffs
  • YC has funded similar coordination tools (Twist, Notion) successfully

Risks

  • Presence tools are notoriously hard to monetize, Slack gives presence away free
  • Requires adoption across entire team to be useful; single-user install has no value
  • Privacy concerns: tracking activity and availability can feel invasive to employees
  • Incumbents (Microsoft, Google, Slack) can copy features in weeks if traction emerges
  • Problem may be cultural, not technical, some teams don't respect focus time regardless of tooling
  • Unclear if this is a $10M problem or a $100M problem; pricing model undefined

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Remote Collaboration and Team Presence”.

Open FlyBot